Thanks so much, everyone, for the help so far. Hopefully I can get to
the bottom of this with everyone's spam reports. I seem to have
identified two problems:
1) When sending email through lists.sr.ht, my mail fails DKIM. This is
not because srht's own DKIM fails (it works) but my own DKIM fails.
However, when I am sending directly, that very same DKIM configuration
on my server passes. I have no clue yet what is causing this but will
investigate.

2) Even on "direct" emails to GMail domains, which claim that I am
passing DMARC, DKIM, and SPF, I still get put in spam.

Kalyan

On Tue Dec 21, 2021 at 10:51 PM PST, Miguel Bernabeu wrote:
> Migadu here also identifies you as spam:
>
> X-Migadu-Spam-Score: 6.00
> X-Spam: Yes
> Authentication-Results: aspmx1.migadu.com; dkim=pass
> header.d=lists.sr.ht header.s=srht header.b=cUPC2BOb; dkim=fail
> ("headers rsa verify failed") header.d=coderkalyan.com header.s=default
> header.b=e51XeYqY; dmarc=fail reason="SPF not aligned (relaxed), DKIM
> not aligned (relaxed)" header.from=coderkalyan.com (policy=quarantine);
> spf=pass (aspmx1.migadu.com: domain of lists@sr.ht designates
> 173.195.146.151 as permitted sender) smtp.mailfrom=lists@sr.ht
>
> It would seem both the SPF and DKIM checks fail. In my short experience

On Tue Dec 21, 2021 at 4:17 PM PST, Sebastian LaVine wrote:
> On Tue Dec 21, 2021 at 6:54 PM EST, Kalyan Sriram wrote:
> > Hello all,
> > For the past year, I've been self hosting email (using postfix + dovecot
> > on a Vultr VPS) - both as an educational exercise and a chance to get
> > away from Google - which is tied to my domain, coderkalyan.com. However,
> > when I first set it up, I was unable to get GMail to not put me in spam,
> > so I decided to go with Amazon SES as an SMTP proxy so I could rest
> > assured my email was being delivered.
> >
> > Recently, I came across the [maddy](https://maddy.email) email client
> > and have been using it for the past couple of weeks. I decided that
> > since I had to rip out my existing DNS configuration and redo it, I'd
> > take the opportunity to try to remove AWS from my workflow However,

On Tue Dec 21, 2021 at 4:15 PM PST, Noelle Leigh wrote:

> Interestingly, your message got sent to my spam folder (Fastmail).
Weird. Fastmail appears to use SpamAssassin, which is tested by
mail-tester.com and other sites and I haven't had any issues from it
before.
>
> Here's the X-Spam-* headers that it contained:
>
> X-Spam-known-sender: no
> X-Spam-sender-reputation: 0 (email; expectedauth)
> X-Spam-score: 8.2
> X-Spam-hits: DMARC_LIST_OVERRIDE_QUARANTINE 0.5,
> HEADER_FROM_DIFFERENT_DOMAINS 0.25,

Hello all,
For the past year, I've been self hosting email (using postfix + dovecot
on a Vultr VPS) - both as an educational exercise and a chance to get
away from Google - which is tied to my domain, coderkalyan.com. However,
when I first set it up, I was unable to get GMail to not put me in spam,
so I decided to go with Amazon SES as an SMTP proxy so I could rest
assured my email was being delivered.

Recently, I came across the [maddy](https://maddy.email) email client
and have been using it for the past couple of weeks. I decided that
since I had to rip out my existing DNS configuration and redo it, I'd
take the opportunity to try to remove AWS from my workflow However,
despite multiple days of googling and trying, I'm unable to get gmail to
accept my messages into primary inbox. Even with all the usual anti-spam

Hello,

This is a test to check that DKIM policies are working correctly for
sr.ht.

Kalyan

---
Don't merge this of course!
 src/SUMMARY.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/SUMMARY.md b/src/SUMMARY.md
index 77f2ed0..fdc90b9 100644
--- a/src/SUMMARY.md
+++ b/src/SUMMARY.md
@@ -1,5 +1,6 @@
 # Summary
 
+# Made a useless change
 - [Introduction](README.md)
[message trimmed]

On Wed Dec 15, 2021 at 6:32 AM PST, Hubert Hirtz wrote:
> On 15/12/2021 03:53, Kalyan Sriram wrote:
> > Improve show buffer numbers on "/buffer" command. Checks completion
> > against list of commands to avoid ambigious "/b" matching ("BUFFER" v.
> > "BAN"). Matches uppercase and mixed case i.e. "/BU" or "/bU".
>
> I see, thanks for the patch. While I don't use neither buffer numbers
> nor /buffer myself, I expect typing "/b <number>" be the common
> practice, and this patch breaks it? What do you think?

Yes, typing /b is the common practice but unfortunately doesn't
currently work since the "BAN" command was introduced. /b brings up the
numbers, but once the user presses enter, the command complains saying
"b" is ambigious. Hence I thought this would be the least intrusive way

Improve show buffer numbers on "/buffer" command. Checks completion
against list of commands to avoid ambigious "/b" matching ("BUFFER" v.
"BAN"). Matches uppercase and mixed case i.e. "/BU" or "/bU".
---
 window.go | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/window.go b/window.go
index 82941a1..87e4be4 100644
--- a/window.go
+++ b/window.go
@@ -83,7 +83,15 @@ func (app *App) setBufferNumbers() {
 		}
 	}
[message trimmed]

---
 app.go         |  1 +
 completions.go | 20 ++++++++++++++++++++
 2 files changed, 21 insertions(+)

diff --git a/app.go b/app.go
index 1144560..4706536 100644
--- a/app.go
+++ b/app.go
@@ -938,6 +938,7 @@ func (app *App) completions(cursorIdx int, text []rune) []ui.Completion {
 		cs = app.completionsChannelMembers(cs, cursorIdx, text)
 	}
 	cs = app.completionsMsg(cs, cursorIdx, text)
+	cs = app.completionsCommands(cs, cursorIdx, text)
[message trimmed]