Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gmail blocks some mailman messages #111

Open
LukasFreeze opened this issue Dec 18, 2016 · 6 comments
Open

Gmail blocks some mailman messages #111

LukasFreeze opened this issue Dec 18, 2016 · 6 comments

Comments

@LukasFreeze
Copy link
Member

With more users in our various mailing lists fewer and fewer messages are falsely classified as "spam", but a major problem persists: Gmail blocks some eMails that it considers suspicious entirely and the addressees can not see them or teach it that it was not in fact spam.

It's likely that I have provoked this when switching all previous newsletter subscribers to the new list, but adhering to Gmail's bulk sender guidelines more closely might solve this issue.

@LukasFreeze
Copy link
Member Author

It starts with "authentication & identification": as far as I know, we do have consistent "from:" addresses but several IPs from which Mailman will send. The third advice is to "Keep valid reverse DNS records for the IP address(es) from which you send mail, pointing to your domain" which is not entirely clear to me yet.

@emka
Copy link
Member

emka commented Dec 18, 2016

We have correct reverse DNS entries for IPv4 and IPv6.

What we do not have is SPF and DMARC records, if anyone knows these well enough please contact me.

@emka
Copy link
Member

emka commented Dec 18, 2016

I think our SPF record should look like this:

v=spf1 ip4:78.47.161.102 ip6:2a01:4f8:c17:1e51::2 -all

Can anyone confirm?

@LukasFreeze
Copy link
Member Author

I don't have any experience of course, but from the Google support page I understand it should rather be

v=spf1 include:_spf.google.com ip4:78.47.161.102 ip6:2a01:4f8:c17:1e51::2 ~all

They say "-all" may cause delivery problems.

@emka
Copy link
Member

emka commented Dec 18, 2016

_spf.google.com is for sites hosted on Google servers. I added

v=spf1 ip4:78.47.161.102 ip6:2a01:4f8:c17:1e51::2 ~all

please let me know if anything fails.

@emka
Copy link
Member

emka commented Dec 18, 2016

We are also missing valid DKIM signatures, probably not solved yet for mailman.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants