SMS Delivery Issues

[josephtd]

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.

[vzw_customer_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.

[vzw_customer_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?

[#10]

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.