Slashdot Mirror
Verizon's Aggressive New Spam Filter Causing Problems
aviancarrier writes "Verizon DSL has turned on a very aggressive spam filter that is blocking lots of long-time legitimate emails. Emails get bounced with an error: 'XX@verizon.net: host relay.verizon.net[206.46.232.11] said: 550 Email from your Email Service Provider 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.' That whitelist web page lets you request one address at a time to be whitelisted with no guarantee for their response time to process it. I have tested multiple email sources and only one got through. As a VZ customer, I just spent 28 minutes on a call to tech support, eventually got a supervisor who knows nothing about the new spam feature, and would only agree to email a manager who doesn't work weekends about it. I warned her that VZ has a public relations problem but she was too clueless to understand." Many users have submitted this problem so it seems to be a pretty far reaching problem. There is also a discussion going on over at Google about this problem.
I went to the referenced URL and it sure looks to me like, using the
ISP form, you can request multiple domains and multiple IP addrs in a
single request.
Also, the discussion over at Google currently has a whopping 6 entries.
Much ado about nothing?
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
Here's a trick for Verizon Online phone service: Call up, listen to menu items, then say -nothing-. Don't ask for an operator, don't enter in your phone number: just chill for about two minutes while the prompts repeat. In under three minutes, you'll be transfered to a live operator.
I ran a bulk-sending system (legitimate!) to email Frontier Airline's frequent flyer members, and Verizon was the biggest single problem getting mail through. I don't think I ever did get them to accept our runs at all.
The big thing they already had in place was that they want to connect back on port 25 to the sending system AND make sure it responds initially with the same name it's using to send mail out. Not a bad thing overall, I suppose, but I can see how it would block quite a few messages from providers that use separate sending servers from their receiving servers. I finally had to set up SMTPFWDD on both outgoing servers to accept connections and silently drop any emails they get, that helped, but I think they still rate-limited heavily.
I'd say if you depend on getting your email, Verizon's not a good ISP to use.
Verizon is a spam sewer itself.
r izon.net
http://www.spamhaus.org/sbl/listings.lasso?isp=ve
Sometime this morning two of my email addresses got whitelisted and could get through again to Verizon Online. Earlier in the morning I received form emails from Verizon's whitelist group saying they have attempted to contact the blocked company/domain.
Regarding the person who accused me of being a spammer: No. Just a husband trying to email my wife's VZ account.
Regarding the "lashing" out at the customer service supervisor: I was trying to get her to help her own company out. The fact that she was not told anything about a new level of spam filtering nor had (she claims) a way to contact a manager on a weekend about a PR problem may be a standard problem for that level of supervisor, but I wanted to give her a way to be a hero internally and stop a PR problem from getting worse.
Seems like it.
I used to send all my email out of my own mailserver, out of my home firewall/router/"box-in-a-closet" machine.
Recently -- like within the last six months or so, I've noticed an alarming number of domains that aren't receiving my emails. And no, I haven't been blackholed or otherwise put on anyone's shit list, nor am I running an open relay. The mailserver is perfectly well-behaved, standards compliant, and only relays from within my home LAN.
I also don't mass-mail or do any other sort of sketchy activity, I just always liked having my own mailserver and never having to worry about when my ISPs (or Google's, or my web hosting providers') was going to flake out on me. But it's becoming nearly impractical to do. I'm never sure if an email that I sent out has actually gotten through, or if it's just been silently eaten by some spam filter somewhere.
The worst offender that I've found so far is Comcast; I haven't been able to get any messages through at all to Comcast subscribers, and they don't provide back any sort of acknowledgment that a message has been blocked. Every time I send anything to them, it's firing a shot into the darkness.
I hate spam as much as anybody else (probably more than some); I'm in favor of using some of those Federal "computer crimes" laws -- the ones that have harsher penalties for electronically violating a system than if you walked in and stole it in person -- against spammers. See what 20 years of pound-me-in-the-ass prison followed by another 10 or 15 of no-computer probation (and consequent unemployment) does for their attitude. Or there are the always popular vigilante death squads, I could find a warm place in my heart for them, too. Either of those would be preferable to the current patchwork system of blacklists, whitelists, greylists, RBLs, and unilateral policies on the part of ISPs that break up the nature of the network.
Sending an email shouldn't be like tossing a message in a bottle into the ocean, but that's how it's getting to be with some ISPs.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Most of the people in her position are, in fact, employed by an outsourced call center - likely either in Canada or in Dallas/Ft. Worth; At best, they are the people who managed to make people /feel/ /better/ (not necessarily solve the problem) and get them to hang up quickly - over a period of nine months to a year, and are then bumped to a level II tech.
/at verizon/ and when the offer letter turned up, told them "No, I have ethics" - after they illegally told several of my co-workers that they could not be hired because of a non-existent no-hire agreement, and they all took other job offers, at lower rates. Not to mention the European "spam blackhole" which ate everything from Europe, period - no explanations and the whitelisting process never actually worked.
I worked at one of these outsourcers. Most of the intelligent & ethical tech pros there were diligently finding other employment as fast as they could. I interviewed for a position
The upshot is: The tech you talk to on the phone has few or no options for actually solving your problems, it is actually contrary to his job interest to invest time in solving your problems, and the supervisors also have no power and are the ones most proficient in convincing people quickly that there is no problem, no jabba yo wadda.
And I have little option but to remain Anonymous Coward - Verizon & the outsourcers have really dim views of people being critical of their lack of ethics.