![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Somewhere in the past days or weeks, Google started either bouncing email without a DKIM signature or is silently filing it as spam. (DKIM: DomainKeys Identified Mail, an anti-spoofing measure.)
If you receive email at a domain you registered, there is a good chance that recipients who use Google Mail are not receiving it. You'll need to ensure that you're getting a DKIM "pass" result that matches your domain name.
For example, I use Fastmail. GMail was indicating "DKIM PASS from messagingengine.com" (that's Fastmail's actual mail service) but was still rejecting my mail. Once I added the DNS records that Fastmail indicating I needed to add in their settings page for my domain, I instead started getting "DKIM PASS from [my actual domain]" and my mail started getting through.
(While DKIM is a reasonable tool and it's fine that Google is using this as part of their spam check, I suspect they're doing this strict version to try to solidify their position by further freezing out other mail providers.)
If you receive email at a domain you registered, there is a good chance that recipients who use Google Mail are not receiving it. You'll need to ensure that you're getting a DKIM "pass" result that matches your domain name.
For example, I use Fastmail. GMail was indicating "DKIM PASS from messagingengine.com" (that's Fastmail's actual mail service) but was still rejecting my mail. Once I added the DNS records that Fastmail indicating I needed to add in their settings page for my domain, I instead started getting "DKIM PASS from [my actual domain]" and my mail started getting through.
(While DKIM is a reasonable tool and it's fine that Google is using this as part of their spam check, I suspect they're doing this strict version to try to solidify their position by further freezing out other mail providers.)
no subject
Date: 2022-03-28 11:11 pm (UTC)Damn gmail!
no subject
Date: 2022-03-29 09:04 pm (UTC)no subject
Date: 2022-03-29 11:59 pm (UTC)1. Go to https://www.appmaildev.com/en/dkim and click the "Next Step" button at the top
2. It will give you an email address. Send an email to that address from the domain you want to check
3. It will then give you a report. Find the DKIM section and expand it. Two things need to be true: It needs to say "PASS" in the summary of that section, and the big blob of text that starts with "DKIM-Signature" needs to contain "d=example.com" (if your mail is blah@example.com). If it contains something else like d=dreamhost.com, that's something that Google will frown at.
Chances are decent that Dreamhost is handling DKIM correctly -- if they control your DNS records (e.g. if you registered the domain through them) then they have the ability to set everything up correctly. And maybe they have!
If your domain name itself is managed elsewhere (with A and MX records pointing to Dreamhost) then it is likely *not* set up for DKIM.
no subject
Date: 2022-03-30 03:40 pm (UTC)i'll go run this lil' email test now. thank you!
no subject
Date: 2022-03-30 04:49 pm (UTC)no subject
Date: 2022-03-30 01:25 am (UTC)...but the gold standard is still to send an email and check if the receiving server sees valid DKIM. :-)
(I'd also be happy to help out and take a look more directly if none of the above helps.)
no subject
Date: 2022-05-08 05:18 am (UTC)Thanks for the info!