This is a test of email sending from mx2.coderkalyan.com.

Hello,

This is a test from the new mail server.

Kalyan

Hello,

This is a test with the new mail server, mx2.coderkalyan.com, running on
Hetzner cloud.

Kalyan

Hello,

This is a test of the new mail server, mx2.coderkalyan.com.

Kalyan

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

How are DKIM/DMARC/SPF looking when going through a mailing list?

Kalyan

Does this go through correctly?

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,