Gmail Classifying TWN Emails as Spam

[marlowe]

Multiple users have reported gmail tagging TWN emails as spam. The following was provided by an affected user

"*Authentication & Identification *

To ensure that Gmail can identify you:

• Use a consistent IP address to send bulk mail.
• Keep valid reverse DNS records for the IP address(es) from which you send mail, pointing to your domain.
• Use the same address in the 'From:' header on every bulk mail you send.

We also recommend the following:

• Sign messages with DKIM <​http://www.dkim.org/>. We do not authenticate messages signed with keys using fewer than 1024 bits.
• Publish an SPF record <​https://support.google.com/a/answer/33786>.
• Publish a DMARC policy <​http://www.dmarc.org/>.

Learn more <​https://support.google.com/mail/answer/180707> about email authentication."

[marlowe]

SPF record appears in order.

"Received-SPF: pass (antagonism.org: SPF record at tahoe-lafs.org designates 74.207.252.227 as permitted sender)" and "SPF_HELO_PASS" from SpamAssassin?

As does reverse DNS,

"nslookup 74.207.252.227 Server: 127.0.1.1 Address: 127.0.1.1#53

Non-authoritative answer: 227.252.207.74.in-addr.arpa name = tahoe-lafs.org."

We do not do DKIM. We should look into this.

[marlowe]

If we implement option_from_is_list and DKIM signing as recommended here, ​http://serverfault.com/questions/340584/mailman-from-spoofing, this should resolve all the criteria listed above.

[warner]

We should also look at the ​trac mailing lists: I think the root cause here might be spammy ticket/comments (which were then mailed to subscribers of tahoe-lafs-trac-stream). We seem to have fixed the comment spam problem for now, but our IP probably got a bad reputation while those messages were going out.

Zooko told me he's seeing spam sent to tahoe-dev-owner, which then gets forwarded to him and a few other people who admin/moderate that list.

[marlowe]

Brian,

Let's set up a time next week where we can work on this together.

Cheers, Patrick