3 ms·

I've not really had those issues. A temporary block a few times, but that gets resolved. FWIW, with mox, I prefer not to rely on blocklists (centralized!). Inc

by mjl- 4y ago

I've not really had those issues. A temporary block a few times, but that gets resolved. FWIW, with mox, I prefer not to rely on blocklists (centralized!). Incoming mail is first checked with reputation of the sender. This reputation is only per account. So one accounts junk-classification doesn't affect another accounts. Only for new senders, and without conclusive signals, would a DNSBL be used. The result is that you can keep communicating with folks you've been communicating with for years, even if their IP is on a blocklist. I wonder if the large providers are doing something like this as well. I suspect many mail servers use a DNSBL early in an SMTP session.

apocalyptic0n3 4y ago
Big providers, especially Microsoft, have become extremely heavy handed the last year or so. Now, if a single IP address in a /24 is sending spam, Microsoft will just block the entire /24. And we've had so much difficulty getting Microsoft to walk back that block and not reinstate it later on that we've completely given up providing any type of email service (whether that be day-to-day email needs or transactional emails). I've spent hours on calls with Microsoft support trying to remedy this and it's just impossible once it happens (and I've had it happen multiple times to multiple IPs and had multiple MS techs confirm this is what is happening)