Wireless Forums

Reply
Posted Aug 24, 2012
9:36:42 AM
View profile
SMS Message being blocked/filtered using SMTP by AT&T?

We have an automated process that uses Google SMTP server to send text messages for alerts when our systems are down.

 

The text messages are still being sent by Google mail but are not reaching our phones. I have verified that the messages are being received by co-workers using Verizon. I have also verified that I can use the Google account directly to send myself an SMS from my email account.

 

Here is the full message information from Google mail (as SMTP server). It looks like it is successfully sent to AT&T but I never get the SMS message.

 

Return-Path: <intellireal.external@gmail.com>
Received: from ir19.intellireal.com ([66.179.186.101])
by mx.google.com with ESMTPS id c6sm9406965obd.22.2012.08.24.07.35.20
(version=SSLv3 cipher=OTHER);
Fri, 24 Aug 2012 07:35:20 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:35:20 -0600 (MDT)
From: intellireal.external@gmail.com
To: xxxxxxx <720XXXXXXX@txt.att.net>
Message-ID: <729780291.71345818920612.JavaMail.hyperic@ir19.intellireal.com>
Subject: [HQ] !! - Test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 2

 

 

Here is an example of directly using Google mail and I successfully receive the SMS message. The only real difference I see is the Message-ID.

 

 

MIME-Version: 1.0
Received: by 10.59.1.33 with HTTP; Fri, 24 Aug 2012 07:25:24 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:25:24 -0600
Delivered-To: intellireal.external@gmail.com
Message-ID: <CACWBJL_aS-6H2Nx9uMsW7j9n=zULhnNGcc6nn=ag52Gr7buc4w@mail.gmail.com>
Subject: Test 123
From: intellireal support <intellireal.external@gmail.com>
To: 720XXXXXXX@txt.att.net
Content-Type: multipart/alternative; boundary=047d7b6dc24e31870904c803bf3b

--047d7b6dc24e31870904c803bf3b
Content-Type: text/plain; charset=ISO-8859-1

 

--047d7b6dc24e31870904c803bf3b
Content-Type: text/html; charset=ISO-8859-1

<br>

--047d7b6dc24e31870904c803bf3b--

 

 

Any help would be greatly appreciated.

 

Franz

We have an automated process that uses Google SMTP server to send text messages for alerts when our systems are down.

 

The text messages are still being sent by Google mail but are not reaching our phones. I have verified that the messages are being received by co-workers using Verizon. I have also verified that I can use the Google account directly to send myself an SMS from my email account.

 

Here is the full message information from Google mail (as SMTP server). It looks like it is successfully sent to AT&T but I never get the SMS message.

 

Return-Path: <intellireal.external@gmail.com>
Received: from ir19.intellireal.com ([66.179.186.101])
by mx.google.com with ESMTPS id c6sm9406965obd.22.2012.08.24.07.35.20
(version=SSLv3 cipher=OTHER);
Fri, 24 Aug 2012 07:35:20 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:35:20 -0600 (MDT)
From: intellireal.external@gmail.com
To: xxxxxxx <720XXXXXXX@txt.att.net>
Message-ID: <729780291.71345818920612.JavaMail.hyperic@ir19.intellireal.com>
Subject: [HQ] !! - Test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 2

 

 

Here is an example of directly using Google mail and I successfully receive the SMS message. The only real difference I see is the Message-ID.

 

 

MIME-Version: 1.0
Received: by 10.59.1.33 with HTTP; Fri, 24 Aug 2012 07:25:24 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:25:24 -0600
Delivered-To: intellireal.external@gmail.com
Message-ID: <CACWBJL_aS-6H2Nx9uMsW7j9n=zULhnNGcc6nn=ag52Gr7buc4w@mail.gmail.com>
Subject: Test 123
From: intellireal support <intellireal.external@gmail.com>
To: 720XXXXXXX@txt.att.net
Content-Type: multipart/alternative; boundary=047d7b6dc24e31870904c803bf3b

--047d7b6dc24e31870904c803bf3b
Content-Type: text/plain; charset=ISO-8859-1

 

--047d7b6dc24e31870904c803bf3b
Content-Type: text/html; charset=ISO-8859-1

<br>

--047d7b6dc24e31870904c803bf3b--

 

 

Any help would be greatly appreciated.

 

Franz

SMS Message being blocked/filtered using SMTP by AT&T?

1,393 views
8 replies
(0) Me too
(0) Me too
Post reply
Cancel
Submit
Replies
(8)
0
(0)
  • Rate this reply
View profile
Oct 17, 2012 9:50:14 AM
0
(0)
Contributor
Did you ever find a solution to this problem. We are having the same problem.
Did you ever find a solution to this problem. We are having the same problem.

Re: SMS Message being blocked/filtered using SMTP by AT&T?

2 of 9 (1,141 Views)
0
(0)
  • Rate this reply
View profile
Oct 17, 2012 10:05:53 AM
0
(0)
Contributor

Unfortunately no. We ended up having to use Verizon.

Unfortunately no. We ended up having to use Verizon.

Re: SMS Message being blocked/filtered using SMTP by AT&T?

3 of 9 (1,136 Views)
0
(0)
  • Rate this reply
View profile
Oct 17, 2012 11:12:41 AM
0
(0)
Contributor
Well I guess that is a solution of sorts :-) thanks for replying
Well I guess that is a solution of sorts :-) thanks for replying

Re: SMS Message being blocked/filtered using SMTP by AT&T?

4 of 9 (1,125 Views)
0
(0)
  • Rate this reply
View profile
Oct 17, 2012 2:34:43 PM
0
(0)
Expert

fgarsombke wrote:

We have an automated process that uses Google SMTP server to send text messages for alerts when our systems are down.

 

The text messages are still being sent by Google mail but are not reaching our phones. I have verified that the messages are being received by co-workers using Verizon. I have also verified that I can use the Google account directly to send myself an SMS from my email account.

 

Here is the full message information from Google mail (as SMTP server). It looks like it is successfully sent to AT&T but I never get the SMS message.

 

Return-Path: <intellireal.external@gmail.com>
Received: from ir19.intellireal.com ([66.179.186.101])
by mx.google.com with ESMTPS id c6sm9406965obd.22.2012.08.24.07.35.20
(version=SSLv3 cipher=OTHER);
Fri, 24 Aug 2012 07:35:20 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:35:20 -0600 (MDT)
From: intellireal.external@gmail.com
To: xxxxxxx <720XXXXXXX@txt.att.net>
Message-ID: <729780291.71345818920612.JavaMail.hyperic@ir19.intellireal.com>
Subject: [HQ] !! - Test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 2

 

 

Here is an example of directly using Google mail and I successfully receive the SMS message. The only real difference I see is the Message-ID.

 

 

MIME-Version: 1.0
Received: by 10.59.1.33 with HTTP; Fri, 24 Aug 2012 07:25:24 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:25:24 -0600
Delivered-To: intellireal.external@gmail.com
Message-ID: <CACWBJL_aS-6H2Nx9uMsW7j9n=zULhnNGcc6nn=ag52Gr7buc4w@mail.gmail.com>
Subject: Test 123
From: intellireal support <intellireal.external@gmail.com>
To: 720XXXXXXX@txt.att.net
Content-Type: multipart/alternative; boundary=047d7b6dc24e31870904c803bf3b

--047d7b6dc24e31870904c803bf3b
Content-Type: text/plain; charset=ISO-8859-1

 

--047d7b6dc24e31870904c803bf3b
Content-Type: text/html; charset=ISO-8859-1

<br>

--047d7b6dc24e31870904c803bf3b--

 

 

Any help would be greatly appreciated.

 

Franz



the bolded underline section is the problem, text message sent via email have to be in plan text, yours is set to html. Compae it to the Content-Type: in the email tha works you see it is text/plain char_set: UTF-8


fgarsombke wrote:

We have an automated process that uses Google SMTP server to send text messages for alerts when our systems are down.

 

The text messages are still being sent by Google mail but are not reaching our phones. I have verified that the messages are being received by co-workers using Verizon. I have also verified that I can use the Google account directly to send myself an SMS from my email account.

 

Here is the full message information from Google mail (as SMTP server). It looks like it is successfully sent to AT&T but I never get the SMS message.

 

Return-Path: <intellireal.external@gmail.com>
Received: from ir19.intellireal.com ([66.179.186.101])
by mx.google.com with ESMTPS id c6sm9406965obd.22.2012.08.24.07.35.20
(version=SSLv3 cipher=OTHER);
Fri, 24 Aug 2012 07:35:20 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:35:20 -0600 (MDT)
From: intellireal.external@gmail.com
To: xxxxxxx <720XXXXXXX@txt.att.net>
Message-ID: <729780291.71345818920612.JavaMail.hyperic@ir19.intellireal.com>
Subject: [HQ] !! - Test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 2

 

 

Here is an example of directly using Google mail and I successfully receive the SMS message. The only real difference I see is the Message-ID.

 

 

MIME-Version: 1.0
Received: by 10.59.1.33 with HTTP; Fri, 24 Aug 2012 07:25:24 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:25:24 -0600
Delivered-To: intellireal.external@gmail.com
Message-ID: <CACWBJL_aS-6H2Nx9uMsW7j9n=zULhnNGcc6nn=ag52Gr7buc4w@mail.gmail.com>
Subject: Test 123
From: intellireal support <intellireal.external@gmail.com>
To: 720XXXXXXX@txt.att.net
Content-Type: multipart/alternative; boundary=047d7b6dc24e31870904c803bf3b

--047d7b6dc24e31870904c803bf3b
Content-Type: text/plain; charset=ISO-8859-1

 

--047d7b6dc24e31870904c803bf3b
Content-Type: text/html; charset=ISO-8859-1

<br>

--047d7b6dc24e31870904c803bf3b--

 

 

Any help would be greatly appreciated.

 

Franz



the bolded underline section is the problem, text message sent via email have to be in plan text, yours is set to html. Compae it to the Content-Type: in the email tha works you see it is text/plain char_set: UTF-8

Re: SMS Message being blocked/filtered using SMTP by AT&T?

5 of 9 (1,113 Views)
0
(0)
  • Rate this reply
View profile
Oct 17, 2012 3:47:07 PM
0
(0)
Contributor

Thanks for taking your time to answer this question. I just tried another test and made sure the content type was indeed TEXT and it did not work. My Verizon phone got the message just fine, my AT&T phone did not :smileysad:

Thanks for taking your time to answer this question. I just tried another test and made sure the content type was indeed TEXT and it did not work. My Verizon phone got the message just fine, my AT&T phone did not :smileysad:

Re: SMS Message being blocked/filtered using SMTP by AT&T?

6 of 9 (1,103 Views)
0
(0)
  • Rate this reply
View profile
Oct 18, 2012 6:51:32 AM
0
(0)
Employee

wingrider01 wrote:

fgarsombke wrote:

We have an automated process that uses Google SMTP server to send text messages for alerts when our systems are down.

 

The text messages are still being sent by Google mail but are not reaching our phones. I have verified that the messages are being received by co-workers using Verizon. I have also verified that I can use the Google account directly to send myself an SMS from my email account.

 

Here is the full message information from Google mail (as SMTP server). It looks like it is successfully sent to AT&T but I never get the SMS message.

 

Return-Path: <intellireal.external@gmail.com>
Received: from ir19.intellireal.com ([66.179.186.101])
by mx.google.com with ESMTPS id c6sm9406965obd.22.2012.08.24.07.35.20
(version=SSLv3 cipher=OTHER);
Fri, 24 Aug 2012 07:35:20 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:35:20 -0600 (MDT)
From: intellireal.external@gmail.com
To: xxxxxxx <720XXXXXXX@txt.att.net>
Message-ID: <729780291.71345818920612.JavaMail.hyperic@ir19.intellireal.com>
Subject: [HQ] !! - Test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 2

 

 

Here is an example of directly using Google mail and I successfully receive the SMS message. The only real difference I see is the Message-ID.

 

 

MIME-Version: 1.0
Received: by 10.59.1.33 with HTTP; Fri, 24 Aug 2012 07:25:24 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:25:24 -0600
Delivered-To: intellireal.external@gmail.com
Message-ID: <CACWBJL_aS-6H2Nx9uMsW7j9n=zULhnNGcc6nn=ag52Gr7buc4w@mail.gmail.com>
Subject: Test 123
From: intellireal support <intellireal.external@gmail.com>
To: 720XXXXXXX@txt.att.net
Content-Type: multipart/alternative; boundary=047d7b6dc24e31870904c803bf3b

--047d7b6dc24e31870904c803bf3b
Content-Type: text/plain; charset=ISO-8859-1

 

--047d7b6dc24e31870904c803bf3b
Content-Type: text/html; charset=ISO-8859-1

<br>

--047d7b6dc24e31870904c803bf3b--

 

 

Any help would be greatly appreciated.

 

Franz



the bolded underline section is the problem, text message sent via email have to be in plan text, yours is set to html. Compae it to the Content-Type: in the email tha works you see it is text/plain char_set: UTF-8


Except the bolded one is the message that he did receive. I don't think that's the issue. How about the To: line? On the one he didn't recieve:

To: xxxxxxx <720XXXXXXX@txt.att.net>

On the one he did receive:

To: 720XXXXXXX@txt.att.net

 

On the one not received, why is the destination address in <>? Might that be preventing it from actually being delivered?

 


wingrider01 wrote:

fgarsombke wrote:

We have an automated process that uses Google SMTP server to send text messages for alerts when our systems are down.

 

The text messages are still being sent by Google mail but are not reaching our phones. I have verified that the messages are being received by co-workers using Verizon. I have also verified that I can use the Google account directly to send myself an SMS from my email account.

 

Here is the full message information from Google mail (as SMTP server). It looks like it is successfully sent to AT&T but I never get the SMS message.

 

Return-Path: <intellireal.external@gmail.com>
Received: from ir19.intellireal.com ([66.179.186.101])
by mx.google.com with ESMTPS id c6sm9406965obd.22.2012.08.24.07.35.20
(version=SSLv3 cipher=OTHER);
Fri, 24 Aug 2012 07:35:20 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:35:20 -0600 (MDT)
From: intellireal.external@gmail.com
To: xxxxxxx <720XXXXXXX@txt.att.net>
Message-ID: <729780291.71345818920612.JavaMail.hyperic@ir19.intellireal.com>
Subject: [HQ] !! - Test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 2

 

 

Here is an example of directly using Google mail and I successfully receive the SMS message. The only real difference I see is the Message-ID.

 

 

MIME-Version: 1.0
Received: by 10.59.1.33 with HTTP; Fri, 24 Aug 2012 07:25:24 -0700 (PDT)
Date: Fri, 24 Aug 2012 08:25:24 -0600
Delivered-To: intellireal.external@gmail.com
Message-ID: <CACWBJL_aS-6H2Nx9uMsW7j9n=zULhnNGcc6nn=ag52Gr7buc4w@mail.gmail.com>
Subject: Test 123
From: intellireal support <intellireal.external@gmail.com>
To: 720XXXXXXX@txt.att.net
Content-Type: multipart/alternative; boundary=047d7b6dc24e31870904c803bf3b

--047d7b6dc24e31870904c803bf3b
Content-Type: text/plain; charset=ISO-8859-1

 

--047d7b6dc24e31870904c803bf3b
Content-Type: text/html; charset=ISO-8859-1

<br>

--047d7b6dc24e31870904c803bf3b--

 

 

Any help would be greatly appreciated.

 

Franz



the bolded underline section is the problem, text message sent via email have to be in plan text, yours is set to html. Compae it to the Content-Type: in the email tha works you see it is text/plain char_set: UTF-8


Except the bolded one is the message that he did receive. I don't think that's the issue. How about the To: line? On the one he didn't recieve:

To: xxxxxxx <720XXXXXXX@txt.att.net>

On the one he did receive:

To: 720XXXXXXX@txt.att.net

 

On the one not received, why is the destination address in <>? Might that be preventing it from actually being delivered?

 

*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: SMS Message being blocked/filtered using SMTP by AT&T?

7 of 9 (1,059 Views)
0
(0)
  • Rate this reply
View profile
Apr 11, 2014 5:00:18 PM
0
(0)
Teacher

wingrider01's post is irrelevant; nothing to do with html. AT&T is arbitrarily blocking SMTP; same problem here; upon testing I was impressed by their filtering; no matter what was the server that directly interfaced with AT&T's (google SMTP or O365) even if one of the flagged IPs or FQDN hosts is mentioned in the SMTP chain -- they will block it.

 

Changing that IP or FQND with temporary fake values fixes the problem. But that's not a fix, come on. What, if any, is AT&T's process to dispute? We don't have hookups on the inside of AT&T and front-end support peons are useless.

 

Any help will be appreciated. And NO and IPs are not black listed. AT&T just decided to block them???

 

 

wingrider01's post is irrelevant; nothing to do with html. AT&T is arbitrarily blocking SMTP; same problem here; upon testing I was impressed by their filtering; no matter what was the server that directly interfaced with AT&T's (google SMTP or O365) even if one of the flagged IPs or FQDN hosts is mentioned in the SMTP chain -- they will block it.

 

Changing that IP or FQND with temporary fake values fixes the problem. But that's not a fix, come on. What, if any, is AT&T's process to dispute? We don't have hookups on the inside of AT&T and front-end support peons are useless.

 

Any help will be appreciated. And NO and IPs are not black listed. AT&T just decided to block them???

 

 

Re: SMS Message being blocked/filtered using SMTP by AT&T?

8 of 9 (240 Views)
0
(0)
  • Rate this reply
View profile
Apr 11, 2014 6:21:05 PM
0
(0)
Expert

bbiandov wrote:

wingrider01's post is irrelevant; nothing to do with html. AT&T is arbitrarily blocking SMTP; same problem here; upon testing I was impressed by their filtering; no matter what was the server that directly interfaced with AT&T's (google SMTP or O365) even if one of the flagged IPs or FQDN hosts is mentioned in the SMTP chain -- they will block it.

 

Changing that IP or FQND with temporary fake values fixes the problem. But that's not a fix, come on. What, if any, is AT&T's process to dispute? We don't have hookups on the inside of AT&T and front-end support peons are useless.

 

Any help will be appreciated. And NO and IPs are not black listed. AT&T just decided to block them???

 

 


nice necormancer, the thread is close to 2 years old, if you take the time to review the actual RFC that is the basis for the desing of the protocal you will see the answer


bbiandov wrote:

wingrider01's post is irrelevant; nothing to do with html. AT&T is arbitrarily blocking SMTP; same problem here; upon testing I was impressed by their filtering; no matter what was the server that directly interfaced with AT&T's (google SMTP or O365) even if one of the flagged IPs or FQDN hosts is mentioned in the SMTP chain -- they will block it.

 

Changing that IP or FQND with temporary fake values fixes the problem. But that's not a fix, come on. What, if any, is AT&T's process to dispute? We don't have hookups on the inside of AT&T and front-end support peons are useless.

 

Any help will be appreciated. And NO and IPs are not black listed. AT&T just decided to block them???

 

 


nice necormancer, the thread is close to 2 years old, if you take the time to review the actual RFC that is the basis for the desing of the protocal you will see the answer

Re: SMS Message being blocked/filtered using SMTP by AT&T?

9 of 9 (232 Views)
Share this post
Share this post