Ah, the joys of self-hosting mail these days. You take pains to set everything up meticulously -- SPF, DKIM, DMARC, ARC... and then your server gets immediately blocklisted just because it's "newly observed IP."

Abusix, what a shitshow.

@monsieuricon "high volumes" How much traffic do you carry?

@hakona only the Linux Kernel Mailing List, nothing too huge. ;)

@monsieuricon I was under the impression that "warming up the email address" was just some mumbojumbo from the sales people... Adding some different twist, like a fresh/cold IP address weirds me out even more o_0

• Newly Observed IP sending SMTP traffic
...
• Newly Observed IP with SMTP port open
• Newly Observed IP getting observed
• Newly Observed IP which weren't observed directly but which existence is theoretically possible and probable thus predicted and blocklisted

@monsieuricon

@monsieuricon@social.kernel.org I have a conspiracy theory that all these anti-spam/anti-abuse organizations turned into venal bastards helping Big Tech to get rid of private independent mail servers long time ago.
Sounds like, y'know, a conspiracy theory but seems fucking legit.

@monsieuricon Just use Exchange Online, I'm sure that's not a problem at all... :D

@K. Ryabitsev 🍁

Abusix

Read the name carefully

@shuro @monsieuricon Newly Observed IP lost quantum superposition

@monsieuricon But the more someone posts such pics, more people are scared to host own mail servers, less servers pop up into existance, more suspicious become those, that are starting. For those blacklisting firms.

Just a thought.

@Revertron or maybe more people will stop to use these blacklisting services :)

I support the corporate mailserver at work and these keep pissing me off. I mean we are pretty much okay - we are high-reputation domain, we don't send unsolicited mail at all, all basic checks are in place, our daily mail volume is around 10K messages. Mostly it works just fine.

Yet every now and then I run into some delivery problems because someone is using some "cloud blocklist" which suddenly blocklists us for some weird reason like "triple reverse resolve isn't passed" or "Sending IP certificate doesn't match the origin domain" or "IP belongs to private AS in Russia" or "IP digits summed together produce the same result as Hitler's birthday" - and then the owner of the remote system thinks it is us who should fix that, not them to stop using some bullshit service.

I even run into "antispam biocklists" which request money for delisting. "We blocked you because we don't like you but you can pay us $30 to prove you are not a spammer" - and yes, some people use these.

@monsieuricon

@shuro @monsieuricon 😱😱😱