Thread: Wow, Verizon wireless = suck!
06-22-2009, 11:02 AM #1
Wow, Verizon wireless = suck!
Well, it would appear that I'm going through yet another network in the next couple of days, because I just can't deal with these VZW idiots any more. The story:
I have an application that checks servers, sends text (using [email protected]) when down, etc. Typically it will send me a few texts a day, maybe 10-20 max.
Up until recently, I've had no problem at all with it, the phone works, the app works, everything is hunky dory. That is, until recently.
Now, when sending mail (through primary server), their mailserver immediately closes the connection. No header sent, no welcome message, it's just :
[[email protected] ~]: telnet vzw server 25 Trying ipaddress... Connected to vzw server (ip). Escape character is '^]'. 554 txslspamp2.vtext.com Connection closed by foreign host. [Load: 0.35] [Time: 09:51:52] [[email protected] ~]:
[[email protected] ~]: telnet vzw server 25 Trying ipaddress... Connected to vzw server (ip). Escape character is '^]'. 220 txslspamp1.vtext.com ESMTP ^] telnet> q Connection closed. [Load: 0.08] [Time: 09:52:37] [[email protected] ~]:
I looked this ip up on multiple RBL's, nothing found there. It's a clean ip address:
ipaddress NOT Listed in blackholes.five-ten-sg.com
ipaddress NOT Listed in zen.spamhaus.org
ipaddress NOT Listed in bl.spamcop.net
ipaddress NOT Listed in list.dsbl.org
ipaddress NOT Listed in recent.spam.dnsbl.sorbs.net
ipaddress NOT Listed in combined.rbl.msrbl.net
ipaddress NOT Listed in block.rhs.mailpolice.com
ipaddress NOT Listed in hil.habeas.com
ipaddress NOT Listed in psbl.surriel.com
ipaddress NOT Listed in combined.njabl.org
Anyways, back to the story. Obviously, I've checked out the error myself, and done extensive testing to verify that the error isn't something I can resolve myself.
A couple of months ago, I suddenly started seeing the need for a secondary mail server, because of the above error. I called them, gave them very specific details (as I've done here), the server hostname, the ip address, the email address this was being sent from, everything! Still, this problem exists. They try passing the error off as:
I'm sorry sir, but we do not support bulk mailing applications
I'm sorry, sir, but we do not support @vtext.com addresses
It took me going through 10 different people today, telling the story 10 different times, all with the same old texted, scripted BS.. What's worse? They were in the U.S. !!!
Oy vey, it looks like it's time to find yet another cell service provider, one that actually listens when customers speak!
06-22-2009, 11:12 AM #2Disabled
- Join Date
- Sep 2005
- A box
Wow, that's pretty shabby. I'd had pretty good experiences with Verizon except for one time after being a customer for 3 years I was late on the bill, and they wouldn't turn the service back even after the cheque was post marked when it was suppose to, but apparently they take 10-15 days to process a regular non electronic cheque....would have been nice to know ~.~
I'm currently very happy with ATT and my new iPhone.
It could be worse however, you could have T-Mobile....
06-22-2009, 11:25 AM #3
Yeah, I told them very clearly that I'm going to be stopping by the local AT&T store here, if it's not fixed by tomorrow AM (or in Columbus this week) because I'm going to be relying rather heavily on that NOT failing. As it is, I'm using a backup server to send mail and can't have the problems that I'm having right now.
The last person I talked to called me back, asking for information I had given her twice now. My GOD these people are just completely clueless!
My original thought was to pick up an i-phone from AT&T, but they're going to be sold out of those I'm sure (I don't care whether it's a fuzzy S series or not, I just want a damn i-phone ). How do you like the text messaging capabilities, and is the delivery time reasonable?
06-22-2009, 11:35 AM #4Disabled
- Join Date
- Sep 2005
- A box
Still waiting patiently for MMS, apparently ATT didn't want to have all of their servers explode on the launch day of the 3Gs, so they are waiting till a little later this summer to release the MMS capabilities, followed by tethering for the iPhone later this year.
Apple, also worried of its servers exploding, is "slowly" rolling out push notification on apps as to not put to much of a strain on their servers as well...
Both ATT and Apple are playing it extremely careful this year..
But yes, point being, pickup the iPhone, if you can look past a handful of really really small bugs in the latest OS (3.0), then you will be wowed with an amazing device. I switched from Verizon and a BlackBerry Storm. That think was a piece of junk. I'm thinking of using it as a door stop.
06-22-2009, 01:22 PM #5Cultivated in California
- Join Date
- Aug 2008
- San Francisco
You were probably blacklisted in their internal RBL. Also, there is a possibility that for some reasons one of these buttons may of been checked some how. See screenshot below. You may want to try sending from multiple servers to prevent this problem in the future.
As far as AT&T, think about it. About 40 million or near IPhones on the network all sending MMS's and or tethering at the same time. That would overload and crash their network. Hopefully AT&T does activate MMS without the mod soon.
06-22-2009, 01:25 PM #6
If you're not already on there, you might want to hop on NANOG and ask nicely for one of their engineers to check on it. My experience with VZW has always been pretty positive, but not as a customer.
06-22-2009, 01:29 PM #7Web Hosting Master
- Join Date
- Dec 2000
- The Woodlands, Tx
I'd say they are certainly bs'ing you. I just did a quick write of the following code on a box and tested it, I got it just fine on my Verizon BB 8330.
#!/usr/bin/perl use Time::localtime; open (OUT,"|/usr/sbin/sendmail -t"); print OUT "From: xxxxxxxxxx\@vtext.com\n"; print(OUT "Date: ".ctime()."\n"); print(OUT "To: xxxxxxxxxx\@vtext.com\n"); print(OUT "Subject:\n"); print(OUT "\n"); print(OUT "Test\n"); print(OUT "\n\n"); close(OUT);
06-22-2009, 01:45 PM #8Retired Moderator
- Join Date
- Oct 2002
[email protected], send to [email protected] instead, and have that server just forward the message as-is to vtext.com. It was silly, but I could never get anywhere with T-Mobile or the pager company. Both gave me the same issues you had.
The pager company eventually offered me the ability to create a single address on their end that forwarded to an entire group. I don't know if Verizon would be savvy enough to offer that solution. Another solution might be to use POP3 or IMAP and have those phones check an offsite mail server for the alerts. But it'd be silly to make you go through that much work for something they can "fix" on their end.If you have to operate your company behind the scenes or under a fake name, maybe it's time to leave the industry and start something fresh.
06-22-2009, 02:15 PM #9
They just called me back and basically tried to say the same crap they've been saying for months now (turns out the first support issue was raised in June). I'm done waiting on the idiots over there. At some point, you HAVE to stop waiting and take action.
I've been looking for a reason to grab an i-phone. I've heard very poor things about AT&T's texting capabilities, I will have to see if it's really as bad as I'm told it is. I'm sure that the i-phone has some sort of email capability if nothing else, something that can be checked regularly (like every 60 seconds ) if nothing else.
This is just getting bad. I've only BEEN with VZW for a year and a half, and up until now, it's been smooth sailing. Uggh.
06-22-2009, 03:27 PM #10WHT Content Curator
- Join Date
- Nov 2007
- Dallas, TX
I hear your frustration, linux-tech. Internal RBLs can be a pain to deal with, especially when they won't acknowledge the entry formally. :-/
06-24-2009, 02:19 AM #11New Member
- Join Date
- Jun 2009
I used to work at Verizon as an engineer in their network operation center... sometimes issues come as a result of the continuing, relentless growth of their network.
Bit of advice, and this isn't just for Verizon, it goes for any service provider you may be dealing with. If the person on the other end of the phone isn't making sense, isn't giving you the answer you need or is saying they aren't able to help in some way... hang up, and call back to get another rep on the phone. From my experience, you may have to repeat this process up to three times ;-)
By Neil V in forum Computers and PeripheralsReplies: 4Last Post: 07-16-2007, 12:34 AM
By -GWS- in forum Web Hosting LoungeReplies: 4Last Post: 05-31-2006, 01:44 PM
By null in forum Web Hosting LoungeReplies: 0Last Post: 01-16-2004, 02:55 PM
By DiskDrive in forum Web Hosting LoungeReplies: 0Last Post: 11-28-2003, 02:11 PM
By Frosty in forum Web Hosting LoungeReplies: 34Last Post: 07-30-2003, 09:56 AM