Postfix 3.7. That is not old. My question was to rule out exim with broken tls. You already answered.
IP reputation so toxic Gmail treats me like a war criminal
I'm on a GreenCloudVPS Tokyo box and I don't run mail at all, but I checked my IP on VirusTotal after reading annexbi's post. Two detections as "malicious" from 2022, nothing recent. So the history is there even if you're not using it for mail.
Same but different, I check virustotal also, my HostHatch IP have 5 detection, 2021, 2022, 2023, someone use for "free gift card" maybe, now I use Amazon SES, 0.10 per 1000 email, I cry but I sleep
I run 18 VMs and not one touches port 25 directly. All relay through my employer's Sophos gateway. The IP reputation game is why I keep a NUC in Bratislava just for mail relay to my personal domains. Overkill? Yes. Works? Also yes.
Protection racket is right and the worst part is there's no alternative. You can't opt out of email. It's not like I can tell my clients "sorry, use Signal instead."
Polish company I worked for before had /24 from RIPE directly, not through hoster. Still had problems with Microsoft. They use a composite score from multiple feeds including their own internal telemetry from Outlook.com signups. You will never see that data. We gave up after 8 months and moved to Office 365 for outbound.
Has anyone actually succeeded with a warm-up from a toxic IP? I mean real success, not "it got better after I switched to SES and came back 2 years later."
Ssl34: No. I tried the warm-up for 3 months. 10, 20, 50 emails per day as blubhyper suggested. Gmail went from immediate 550 to... delayed 550. Microsoft stayed "access denied" the entire time. The IP reputation does not decay linearly. It's not a credit score. It's a blacklist with extra steps.
(the warm-up myth (it presumes a functional reputation curve (there isn't one (it's a step function with hysteresis))) (you're either trusted (or you're not (and "not" has no gradations (except "maybe (no)")))) (the 10/20/50 progression is cargo cult (it makes you feel busy (while the provider's ML model says "nope (still nope (forever nope)"))))
Following.