Tet's Journal: Yaaay Verizon!

So Verizon have apparently decided to block incoming mail from my primary SMTP server:

<<< 571 Email from xxx.xxx.xxx.xxx is currently blocked by Verizon Online's anti-spam system. The email sender or Email Service Provider may visit http://www.verizon.net/whitelist and request removal of the block.

Now the IP in question is mine. It's a static IP. It has never been used to send spam. My guess is that they've just randomly blocked a larger range that happens to include my /28. Ho hum. I suppose that just means people on Verizon will have to do without my words of wisdom. It serves them right for choosing to use a moronic ISP. On the other hand, it also means that my girlfriend can't get in touch with their customers if they happen to be on Verizon, which is more of a problem :-( I hate large ISPs who are so inept that their attempts to protect their customers results in splash damage like this. Sadly, it seems to be a feature, once they get beyond a certain size.

Moo

[Chacham]

Too bad. I often wonder why they don't just cut service from any ip address that sends spam until it is fixed. If the compo is compromised, that's a good thing anyway. OK, maybe not a full cut. Maybe a phased cut, whatever. If the major players did this together...

wishful thinking guess. Perhaps they just prefer short-term gains.

Advocatus Diabolicus

[Arker]

Without knowing the full facts, I'm tempted to give them the benefit of the doubt. If they have been reporting spam coming from addresses on your subnet, and your ISP has been informed and told them to eff off, or replied only with silence or inaction, then the case could be made it's your ISP, not them, who is responsible for your block, and them you should be complaining to.

Of course this is Verizon we are talking about. More likely they are just being idiots.

Re:

[Tet]

Sort of. I'd guessed it was something along those lines -- someone spamming, and so they'd blocked an entire subnet either through ineptitude or because my upstream wasn't being helpful. But no, I was wrong. It seems they think I have a dynamic IP address. I don't. I have a static allocation, and the machine is sat in a datacentre, rather than being on the end of a cable/ADSL line. So far, they've ignored my mail telling them that. Sigh.