I self-host my e-mail. I realize that this immediately sets me up
minimally as a particular kind of masochist.
I've been trying to roll my email from what is these days Rackspace
hosted IP to Hostinger. Part of this has involved getting my server
practices up to appropriate snuff for SPF (I've done it for ages), and
getting DKIM and DMARC deployed. Thus far, everything had seemed to be
looking good using various external mail validation tools.
Except gmail.
Stuff from my new IPv4 address is getting through fine. So, I've done
the relevant dances for SPF, DKIM, DMARC, reverse DNS, etc.
Stuff from my new IPv6 address is hitting an invisible validation wall
in Gmail. The form is:
<hidden-test-user@xxxxxxxxx>: host
gmail-smtp-in.l.google.com[2607:f8b0:4023:2009::1b] said: 550-5.7.1
[your ipv6 address] The IP you're using to send mail is not 550-5.7.1
authorized to send email directly to our servers. Please use the SMTP
550-5.7.1 relay at your service provider instead. For more information, go
to 550 5.7.1https://support.google.com/mail/?p=NotAuthorizedError
d9443c01a7336-241cebec304si250494705ad.384 - gsmtp (in reply to end of DATA
command)
While I have strong opinions about the current mega mail providers,
they're inappropriate here. The short form is since my hosted domain is
what I do IETF work on, and far too many people have moved to
IETF-specific inboxes on gmail, I have to deal with it.
So, my apologies for the use of the ietf@ list as a NOC of last support,
but if anyone has suggestions on how to remediate such things, I'm happy
to take your advice.
And yes, I realize the easy answer is to just make my server IPv4-only.
That's rather shameful given that this is for IETF work.
-- Jeff
