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

Recommendation: Create SPF record for the new server (maybe after it becomes webwork.maa.org) #10

Open
taniwallach opened this issue Feb 12, 2020 · 0 comments

Comments

@taniwallach
Copy link
Member

Some mails from the new server are being rejected as potential spam.

SPF records help prevent spam, and the SPF records are checked by many popular email systems (ex. Gmail) when the decide whether to accept an email or not.

So is having a reverse DNS entry.

This probably is worth doing only once after the new site becomes webwork.maa.org.


Google and many other systems are in a battle against spam, and multiple technologies were created and adopted over time to try to reduce spam, including SPF and DKIM. The old webwork server already has a SPF record, but as I mentioned in some prior recent correspondence - test1.webwork.maa.org does not.

One issue which may be impacting the "spam reputation" of webwork.maa.org is the manner in which it sends mails in the name of the original authors.


Among the advice Google gives at https://support.google.com/mail/answer/81126 to try to prevent message being detected as spam are:

  1. Set up valid reverse DNS records of your IP addresses that point to your domain.
  2. Don’t impersonate another domain or sender without permission. This practice is called spoofing, and it can cause Gmail to categorize the messages as spam.
  3. Publish an SPF record for your domain. SPF prevents spammers from sending unauthorized messages that appear to be from your domain.

It also recommends DKIM (and DMARC) which are harder to set up.

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

No branches or pull requests

1 participant