# Oh well, that does it:
"Remote SMTP connections are blocked. It must be an address on the server."
That's the word from the host. Looks like I'm going to have to drop OnMail.
- Disconnect custom domain from OnMail ✔️
- Reconfigure DNS including MX records & SPF ✔️
- Test email ❌
For some reason I can send mail out okay but can't receive to the .blog address. Checks complain that the server is incorrectly configured but I can't see what for the life of me.
Looks like I'm going back to support.
Comments
# We're part of the way there. I can both send and receive mails now but emails generated by code refuse to send to external domains. Kind of messes up the whole subscription thing.
# The outgoing spam filters on the new host are being over zealous. Speaking to support it appears they are often triggered by too many URLs and also don't appear to like various special characters at the start of a line - even taking out the permalinks.
I did a test muse-letter and that worked - probably because it's a lot more text - but it's just not liking a list of posts.
# I think I've reached a workaround, I don't really like what I've had to do but test mails are now getting through at least.
Out of curiosity, I went to OnMail's support pages and searched for 'DNS' — no results. Seriously?? I'm not surprised you're having trouble, if they can't even be arsed to put that information on their site.
To be fair, they give you that info when you go to connect a domain and it was all working... on the old host.