Child Item

Site Totals

61262 Questions Answered 267 Categories

SMS Delivery Issues

I am having a number of issues receiving SMS messages sent as emails from a service my company offers. A number of our customers are complaining that they no longer can receive SMS notifications on their Verizon wireless devices. As a Verizon customer I recently tested as well and sure enough, the messages do not get delivered.

After doing some research, it is very clear that Verizon's mail servers are refusing to talk our outbound mail server. This is new behavior and we need it rectified. Unfortunately, trying to reach out to Verizon Customer Service via twitter has yielded silly questions about what device I am using.

Please help.

Comments

Verizon_Support

josephtd

I definitely want to make sure you can recieve your messages for work! I'm sorry this has stopped working for you. When did this start happening? We do need to know the make/model of your device so we can find the best steps to work on resolving this with your device. Please let us know the details!

RuthW_VZW

Follow us on twitter @VZWSupport

josephtd

I've got a Lumia Icon. This isn't a device issue though. I can see in the email server logs that your infrastructure (mail server) is refusing the connection. Looks like some sort of block list or similar.

Verizon_Support

Let's get to the bottom of this! May I ask what address is being used as the destination on your phone?

Thank you,

YaleK_VZW

Follow us on Twitter @VZWsupport

josephtd

number@vtext.com

josephtd

And here's the logs. I shortened my phone number to 214

Jul 28 09:44:34 dewars postfix/cleanup[28373]: 53D3518944: message-id=<519272406.1805.1406558677279.JavaMail.flytecomm@govmessenger2.flytecomm.com>

Jul 28 09:44:34 dewars postfix/qmgr[4323]: 53D3518944: from=<notifications@flytecomm.com>, size=650, nrcpt=1 (queue active)

Jul 28 09:44:34 dewars postfix/smtpd[28369]: disconnect from unknown[192.168.138.71]

Jul 28 09:44:34 dewars postfix/error[28425]: 53D3518944: to=<214@vtext.com>, relay=none, delay=0.01, delays=0.01/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host smtp-bb.vtext.com[69.78.128.213] refused to talk to me: 554 njbrspamp10.vtext.com)

Jul 28 09:45:14 dewars postfix/smtpd[28369]: connect from govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:14 dewars postfix/smtpd[28369]: D14E518946: client=govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:14 dewars postfix/cleanup[28373]: D14E518946: message-id=<88277747.1806.1406558717794.JavaMail.flytecomm@govmessenger2.flytecomm.com>

Jul 28 09:45:14 dewars postfix/qmgr[4323]: D14E518946: from=<notifications@flytecomm.com>, size=669, nrcpt=1 (queue active)

Jul 28 09:45:14 dewars postfix/smtpd[28369]: disconnect from govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:14 dewars postfix/smtpd[28369]: connect from govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:14 dewars postfix/smtpd[28369]: D6D5918947: client=govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:14 dewars postfix/cleanup[28373]: D6D5918947: message-id=<763050748.1807.1406558717816.JavaMail.flytecomm@govmessenger2.flytecomm.com>

Jul 28 09:45:14 dewars postfix/qmgr[4323]: D6D5918947: from=<notifications@flytecomm.com>, size=628, nrcpt=1 (queue active)

Jul 28 09:45:14 dewars postfix/smtpd[28369]: disconnect from govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:14 dewars postfix/smtpd[28369]: connect from govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:14 dewars postfix/smtpd[28369]: DBDC718948: client=govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:14 dewars postfix/cleanup[28373]: DBDC718948: message-id=<630718322.1808.1406558717837.JavaMail.flytecomm@govmessenger2.flytecomm.com>

Jul 28 09:45:14 dewars postfix/qmgr[4323]: DBDC718948: from=<notifications@flytecomm.com>, size=628, nrcpt=1 (queue active)

Jul 28 09:45:14 dewars postfix/smtpd[28369]: disconnect from govmessenger2.flytecomm.com[192.168.138.71]

Jul 28 09:45:15 dewars postfix/smtp[28550]: D6D5918947: host smtp-bb.vtext.com[69.78.128.213] refused to talk to me: 554 njbrspamp3.vtext.com

Jul 28 09:45:35 dewars postfix/smtp[28549]: D14E518946: host smtp-bb.vtext.com[69.78.128.213] refused to talk to me: 554 njbrspamp3.vtext.com

SuzyQ

Try using ph#@vzwpix.com - if the message is longer than 140 characters, or has special formatting or other oddities, it may be interpreted as MMS, rather then SMS. Sending to vzwpix.com endures that it comes through as MMS.

josephtd

For the heck of it, I tried that, but the issue is obviously infrastructure related. Verizon Wireless has opted to block inbound connections from our mail server when it attempts to deliver the messages. From what I have read online this automatically happens when a certain (unknown) threshold of messages are delivered from one source. While I appreciate the difficulties in fighting spam, this is pretty much insane and needs to be rectified.

It would be one thing if this was the default action and there was a clearly defined approach for having the appropriate personnel look at it, but since I having to go through a message board to get even the least bit of interest from VZW, I'd say the execution is somewhat flawed.

josephtd

So I guess Verizon just doesn't care?

unknown

I don't want to burst your bubble. The sending is more than likely being listed as SPAM (UCE) there are block lists in place to stop this type of spamming to Verizon's and other carriers customers.

The RBL is justified. Verizon adheres to the no spam allowed on their networks or through it policy via Spamhaus and other block lists.

So Verizon does care. That is why they block the senders domains.

The Spamhaus Project - Wikipedia, the free encyclopedia

Unless Mr. Lindford releases your domain servers address or your upstream ISP you will not get any of your mail through.

and rightfully so.

josephtd

Clearly they do not. There has been no response and no action.

You have no idea what spam or UCE is....

I just love smug internet experts.

unknown

Yeah I know nothing about it. do a Google search on elector[at]my-deja.com

I have been getting spammer off the net for more years you knew what a computer was.

Belong to SPAML and if you visit the email and newsgroup spam groups I am listed there as well.

I detest spam and spammers.

And call Verizon or better yet put your DNS in the SPAMHAUS site and see if it has been listed.

Verizon does not allow spam being sent to their customers.

It is that simple.

Unsolicited Commercial Email (UCE)

SPAM is any email not initiated by the owner of that email address. That you personally have permission to send email to. Or as meat product by Hormel.

josephtd

You don't know anything about me, so your claim is pretty amusing, but is indicative of your problem solving skills. I hope you feel better about yourself by trying to belittle others that might be a tad more versed in the goings on in the world than you are.

I am trying to send messages to my phone. Some of my customers are trying to send messages to their phones regarding alerts for things like the arrivals of air ambulance flights, etc. THESE ARE USER INITIATED. So while I appreciate that your life revolves around everything that doesn't work as it should is SPAM - you are incorrect and your repeated attempts to classify something inaccurately makes you look a bit silly.

Furthermore, the sending mail server is on NO BLACKLIST real-time or otherwise. This includes the joke that is known as SPAMHAUS - that stopped being actually useful about 10 years ago.

So no, my friend, it is not that simple.

Unsolicited Commercial Email (UCE)

SPAM is any email not initiated by the owner of that email address. That you personally have permission to send email to. Or as meat product by Hormel."

And this situation fails all of these tests.

And yea, you seem like a great guy.

http://www.motherboardpoint.com/threads/troll-and-criminal-alert-elector-my-deja-com.54812/

unknown

You see the person I had a flame war with for 5 years was indeed a troll poster.

I did not accuse you of trolling I was telling you to check the RBL and Spamhaus is still the site ISP 's use.

Mr. Lindfords credibility is beyond reproach.

I listed that address just to show I had actively fought spam and spammers. It was to show you I knew the subject of which I spoke.

It was a thought of why the notices were not getting through. Many times Verizon and other ISP's believe it to be spam. I cannot say for certain.

You could do a tracert, or DNS lookup to see if there is other issues.

again Good Luck

unknown

Joseph I just read your post again. The notifications are to SMS.

Now lets get away from email. They are two different animals.

Verizon has a text reporting system where a user can report it as unwanted and Verizon blocks the text messages from going out over their network.

Just like email but easier to report.

Spam Controls FAQs | Verizon Wireless

it can be done automatically by Verizon Wireless or a customer can do it on their own.

I don't think if you and others want the text alerts Verizon is going to release the domain from sending to anyone.

Someone had to have reported it.

Sorry for the confusion I was reading your initial problem as email sent not as email sent to SMS texts.

josephtd

And lastly, there isn't wrong other than at Verizon. The logs above show exactly what the problem is. This server sends mail to hosts all over the net.

Seems pretty clear to me that anytime you hit a threshold of messages sent Verizon flags you as someone they can extort money from to restore delivery. This company sucks. For insane amount of money they want from their service, the experience should at least be premium.

unknown

Did you read my last reply?

You may very well be caught in the reported as unwanted sms/txt

in which case it does get blocked.

I apologize for the misunderstanding. The web link explains it better than I can.

Good Luck

Child Item