My emails are hosted in Linode. I believe there is no need to block linode outright for several reasons:
1) In the past, it was possible for spammers to automatically buy linode servers, boot them, install their spam software and start spamming. All via the linode developers API. This is no longer possible, all accounts have port 25 blocked by default and require manual intervention to get it open. 2) In the past, their abuse@ email address wasn't very... hmm responsive. But since two years ago, they provide nearly instant human support. When I email them about bad connections from their network, they are quick to respond and to kill any rogue accounts. This mailing list is the only place I have problems delivering emails. Everything else (ibm/redhat/microsoft/apple/amazon/google/etc) works fine without blocks. On Wed, 6 Jan 2021 07:58:35 +0100 Hans-Martin Mosner via mailop <mailop@mailop.org> wrote: > I can't tell you why cloudmark is blocking Linode, only why I do: > > Statistically, almost every one of the e-mails received here coming from > their servers was spam - I don't know whether > the Linode servers were compromised or regularly rented by the spam senders. > I don't return a 550 error but 450 (unless > other spam signs are present) so I have an opportunity to whitelist if it > seems reasonable, but initially mail from your > site would be rejected, too. _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop