PlanetsCentral

Stefan, could you please add the missing DNS entries for planetscentral.com -- without SPF / DMARC a lot of email providers (e.g. Gmail, etc) will treat emails from a domain without these entries as "more suspicious" and tend to send the emails to spam. Which quite likely explains (at least in part) the fair number of new players who sign up for a game, but never start playing because when the game actually starts they never see the email(s) because they got lost in spam. I know, it happened to me too my first game here.

https://mxtoolbox.com/domain/planetscentral.com/

Just for the record: I saw this post, but I'd like to understand what I'm doing so I'll have to research a little here.

--Stefan

Another element to this equation.

For the last month or so I've been intermittently getting Gmail's "Suspicious link This link leads to an untrusted site. Are you sure you want to proceed?" warning for PlanetsCentral emails.

Google is apparently happier when you authenticate domain ownership in their Postmaster Tools, which is a simple matter of adding a TXT record to the DNS.

Google is apparently happier when you authenticate domain ownership in their Postmaster Tools, which is a simple matter of adding a TXT record to the DNS.

OK, I finally added a SPF record, I hope this didn't break anything.

However, I wonder what exactly I authorize by adding that Postmaster Tools entry? All it confirms that the guy who controls the DNS records can use a Google web page?

(...ok, and it probably proves that the guy who controls the DNS records is the same one who logged in to youtube with this browser 10 years ago...)

I also changed the mails to use "https" instead of "http" links a few weeks ago; from what I read, "http" will also deduce a few points in the trustworthiness rating.

--Stefan

OK, I finally added a SPF record, I hope this didn't break anything.
I also changed the mails to use "https" instead of "http"
I wonder what exactly I authorize by adding that Postmaster Tools entry?

Thanks Stefan!

This morning's turns showed up nicely, and for the first time in years didn't get autoflagged as "not-important". Thank you for the change to HTTPS as well, that's virtually essential these days.

Authentication-Results: mx.google.com; spf=pass (google.com: domain of admin@planetscentral.com designates 85.214.218.199 as permitted sender) smtp.mailfrom=admin@planetscentral.com
Received-SPF: pass (google.com: domain of admin@planetscentral.com designates 85.214.218.199 as permitted sender) client-ip=85.214.218.199;

The main purpose of the Google DNS entry is to authenticate your Google account to the domain so that you can track email delivery reports using Google Postmaster Tools. It's not terribly useful for ultra-low volume mailers, it's more designed for tracking how thousands+ of Gmail recipients are receiving your emails, but if it adds a (tiny) benefit to the deliverability to Gmail recipients it seems worthwhile for me.

streu in Re: planetscentral.com domai...:

OK, I finally added a SPF record, I hope this didn't break anything.
I also changed the mails to use "https" instead of "http"
I wonder what exactly I authorize by adding that Postmaster Tools entry?

This morning's turns showed up nicely, and for the first time in years didn't get autoflagged as "not-important". Thank you for the change to HTTPS as well, that's virtually essential these days.

Thanks for verifying (and for keeping insistent).

The main purpose of the Google DNS entry is to authenticate your Google account to the domain so that you can track email delivery reports using Google Postmaster Tools. It's not terribly useful for ultra-low volume mailers, it's more designed for tracking how thousands+ of Gmail recipients are receiving your emails, but if it adds a (tiny) benefit to the deliverability to Gmail recipients it seems worthwhile for me.

OK, so it's more a monitoring thing, not a "you need to have a Gmail account to be able to mail to Gmail" thing. That makes sense.

--Stefan