bbs.spamgourmet.com

Well, it happened again! Last time (which was a few years ago) it happened twice in one month, each time getting fixed after some days.

Just like last time SPF does get shown as PASSED.
How do we know for sure our outgoing messages don't arrive to people's spam folders 100% of the time?

lwc wrote:I think Spamgourmet should use this time to put DKIM and DMARC records ASAP.

Years later, ASAP still didn't happen...

In any case I reported it as a feedback to Gmail and will wait a bit before creating a filter to override it.

Just for general info there's a ticket related to this in GitHub and if there are helpful comments on getting this done and/or related proposed code fixes that's the place to link to them.

It's happening again!!! And this time it's worse than ever before because SPF fails in the headers.

michaeldlr wrote:Just for general info there's a ticket related to this in GitHub and if there are helpful comments on getting this done and/or related proposed code fixes that's the place to link to them.

Can you please add spf to the subject of this ticket?

I see SPF started failing (in 3 different headers) in October 25th.

Example of headers (look for the word none):

Code: Select all

ARC-Authentication-Results: i=1; mx.google.com;
       spf=none (google.com: gourmet8.spamgourmet.com does not designate permitted sender hosts) smtp.helo=gourmet8.spamgourmet.com
Return-Path: <>
Received: from gourmet8.spamgourmet.com (gourmet.spamgourmet.com. [216.75.62.102])
        by mx.google.com with ESMTPS id a13-20020a02ac0d000000b00363b8d051f8si2014425jao.5.2022.10.24.22.10.35
        for <[censored]>
        (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
        Mon, 24 Oct 2022 22:10:35 -0700 (PDT)
Received-SPF: none (google.com: gourmet8.spamgourmet.com does not designate permitted sender hosts) client-ip=216.75.62.102;
Authentication-Results: mx.google.com;
       spf=none (google.com: gourmet8.spamgourmet.com does not designate permitted sender hosts) smtp.helo=gourmet8.spamgourmet.com

We believe that we have now fixed SPF. Mail from spamgourmet actually arrives from the server addresses (e.g. gourmet7.spamgourmet.com), up until now Google has been guessing that. For some reason google stopped that and marked what used to work as an SPF failure. Josiah has updated the DNS so that there are records for each individual host and now "it works for me".

Please report success or failure.

michaeldlr wrote:Please report success or failure.

Thanks for the quick response, I confirm it looks fixed!

In fact, I don't know how you pulled it off but you upgraded it from how it was before the new problem (at least as far as I could look) because:

1. The general score (above the headers) was upgraded from NONE to PASS.
2. The headers themselves were upgraded from best guess to permitted sender.

Now let's maybe it's time to also add DKIM and DMARC.

The main thing is that Josiah created SPF records for each of the server names rather than just one for the overall spamgourmet.com domain. We guess that what happened before is that Google's approach to guessing domains changed and stopped working for some unknown reason.