I’ve been using MIAB for years with hardly any problems. All of a sudden I can’t email my mum or my sister from any of my MIAB domains. They both have @talk21.com email addresses and when I email them I get
Feb 2 14:53:38 box postfix/smtp[2206]: 8FE8BFC0AF: to=<my-sister@talk21.com>, relay=mx.bt.prod.cloud.openwave.ai[65.20.50.207]:25, delay=1.2, delays=0.19/0.09/0.5/0.46, dsn=5.0.0, status=bounced (host mx.bt.prod.cloud.openwave.ai[65.20.50.207] said: 554 Message rejected on 2025/02/02 14:53:38 GMT, policy (3.2.1.1) ID (679D5121007376AF) - Your message looks like SPAM or has been reported as SPAM (in reply to end of DATA command))
The lines preceding this in the logs are a standard postfix handshake with the remote server and offer no clues.
I am not having any problems sending email to anyone else. So this looks like a “them problem” but I’d like to be certain.
Your message looks like SPAM or has been reported as SPAM
It looks like their provider is using openwave.ai either to host their email directly or as a spam management service. Your emails are being actively rejected. You should make sure your IP isn’t blacklisted. If it is, start figuring out why and work to fix that. If you’re not on any blacklists, you’ll have to get in contact with the admins at either talk21.com or openwave.ai and figure out how to get removed from the blacklist.
It turns out that it isn’t my IP address that’s blacklisted, it’s the entire 209.97.187.152/20 subnet that belongs to Digital Ocean. It’s blacklisted by " UCEPROTECTL3 Blacklist" which appears to be a scam organisation who say they won’t remove you directly but if you complain to DO or if you make “donation” they might remove you.
I’ll have to move my mum + sister to a different provider.
I’m also on Digital Ocean. I’ve spent years building and maintaining a pristine reputation for my IP (which sends very little mail) and I’ve given up trying to keep up with all of the services arbitrarily blocking it. I switched to an external SMTP provider last year and haven’t looked back.
Depending on your volume, there are providers out there you can sign up for and use for free.
I’m using SMTP2GO as a relayhost in postfix, which permits 1000 messages per month on the free tier. That means I send messages to my MiaB as usual and those messages are routed to smtp2go’s service by postfix.
Note that you’ll need to make changes to postfix’s main.cf which will not survive an update - you’ll need to save a copy of your main.cf and replace it after upgrading MiaB.
After creating an account with smtp2go, do the following:
Add the relayhost. Update the following config items in /etc/postfix/main.cf: relayhost = [mail.smtp2go.com]:465 smtp_tls_security_level=encrypt
Add the following config items to the bottom of main.cf:
Thanks. My question was more “who are you using that won’t be subjected to this arbitrary blocking” but the instructions are a bonus for anyone else in this situation.