Le 31/08/2025 à 17:06, Viktor Dukhovni via mailop a écrit :
Actually, this is reasonable, I do the same on my submission server.
The XBL and SBL are not the PBL. While vast swaths of dynamic consumer
IP space are PBL listed, they are rarely XBL or SBL listed.
I can see the point when running your own server for your own use.
But for a service provider, it seems a bit extreme to block customers
who have the bad luck of sharing an IP (either by dynamic assignment or
CGNAT) with someone infected by spam-sending malware. Because these
customers have no actionable way to prevent the IP they're currently
connecting from to be listed again.
I would assume a service provider as big as Gandi has more efficient way
of filtering out log noise and preventing brute force attack that
outright blocking their own customers.
I've instructed my customer to reboot their router, so they've been
assigned another IP address for now, and problem solved... until next
time they get handed an address that's been polluted by someone else...
And I did double check that my customer isn't the one infected with the
spam-sending malware. And as precaution, their router has always been
configured to block outgoing connections to port 25.
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
