?
Solved

Smart Host for AT&T U-verse

Posted on 2014-01-24
8
Medium Priority
?
1,167 Views
Last Modified: 2014-02-04
We are running SBS2011 with Exchange 2010.  We moved to AT&T U-verse from AT&T DSL.  Before the switch, we were using a SmartHost with AT&T DSL to send messages.  With the SmartHost, we did not have any issues sending to various domains or clients.  After the switch, some messages are being rejected to some clients.  The SmartHost had resolved this problem when we installed the new server several years ago.  I contacted AT&T U-verse to get SmartHost settings for U-verse.  I was told I could talk with Tech360 for a fee to see if they could help with the problem.  I was told they may be able to help with the problem.

Port 25 has been opened but that did not resolve the problem.  We found references to this in EE and on the web.

We are looking for information to configure a SmartHost for U-verse.  Our inbound is working fine.  Some of the outbound is being delivered but we need to resolve the undeliverables.  Any assistnce will be appreciated.
0
Comment
Question by:Barnett Computers
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
8 Comments
 
LVL 11

Assisted Solution

by:epichero22
epichero22 earned 1000 total points
ID: 39807056
If some outbound is being delivered, then what's different about those denied outbound packets?  I'm guessing that they're trying to leave on ports that have been closed or their destination is closed to said ports.  

Find out what ports your applications need to use and check the firewall to see if they're open or not.  You mentioned Tech360; what did they say?
0
 
LVL 9

Expert Comment

by:Mike Roe
ID: 39807140
Can you post a undeliverable text with important info cleared
0
 
LVL 1

Author Comment

by:Barnett Computers
ID: 39807788
Thanks for the replies.  We have not contacted Tech360.  Wanted to see if the EE team would have a solution before paying for an answer that may not be there.  My manager will contact AT&T again about the support we were promised for moving to U-verse before agreeing to a paid solution.

According to our research and contact with AT&T, only port 25 is used for incoming and outbound messages.  Firewall is open for this port.

The text shown below was from a failed delivery.  
---------------------------------------------------------------------------------------------------------
Delivery has failed to these recipients or groups:

sentto@receiver.org (sentto@receiver.org)
The recipient's e-mail system isn't accepting messages now. Please try resending this message later or contact the recipient directly.

Diagnostic information for administrators:

Generating server: Ourserver.domain.local

sentto@receiver.org
#550 4.3.2 QUEUE.Admin; message deleted by administrative action ##

Original message headers:

Received: from Ourserver.domain.local ([fe80::3b8:6284:c31d:5bc2]) by
 Ourserver.domain.local ([fe80::3b8:6284:c31d:5bc2%11]) with mapi id
 14.01.0438.000; Wed, 22 Jan 2014 10:37:09 -0500
From: Sender.name <sender@sender.com>
To: "sentto@receiver.org" <sentto@receiver.org>
Subject: FW: MESSAGE-E-Verify
Thread-Topic: MESSAGE-E-Verify
Thread-Index: Ac8NTDPb9JFprhzTRnut/vNObiA7SwKOr64g
Disposition-Notification-To: Sender.name <sender@sender.com>
Date: Wed, 22 Jan 2014 15:37:09 +0000
Message-ID: <9E3393AC8EBB604C878FA06D887AC71C3E4D5828@Ourserver.domain.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.3.121]
Content-Type: multipart/mixed;
      boundary="_004_9E3393AC8EBB604C878FA06D887AC71C3E4D5828BNCSERVER01bncl_"
MIME-Version: 1.0
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
LVL 9

Assisted Solution

by:Mike Roe
Mike Roe earned 1000 total points
ID: 39813309
I would try to send out on different port like 465

25 is usually blocked by servers all over the world not just AT&T even thought you say it is opened for you.

Mike
0
 
LVL 1

Author Comment

by:Barnett Computers
ID: 39813422
This is another reject message sent to a different client. This was sent to an e-mail domain hosted by Google.  

Admitting I do not fully understand the technical side of e-mail - my background is more with application software than network - how would we check the PTR records?  I have seen a reference to PTR during our research.  Could this issue be with DNS since we changed our I.P. address?  

--------------------------------------------------------------------------------------------------------------------------
mx.google.com rejected your message to the following e-mail addresses:

sentto@domain.org (sentto@domain.org)

mx.google.com gave this error:
[2602:301:7772:6020:b1ae:58a:702a:84da] Our system has detected that this message does not meet IPv6 sending guidelines regarding PTR records and authentication. Please review https://support.google.com/mail/?p=ipv6_authentication_error for more information. qp3si15227713bkb.245 - gsmtp

Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.

Diagnostic information for administrators:

Generating server: Ourserver.server.local

sentto@domain.org
mx.google.com #550-5.7.1 [2602:301:7772:6020:b1ae:58a:702a:84da] Our system has detected that 550-5.7.1 this message does not meet IPv6 sending guidelines regarding PTR 550-5.7.1 records and authentication. Please review 550-5.7.1 https://support.google.com/mail/?p=ipv6_authentication_error for more 550 5.7.1 information. qp3si15227713bkb.245 - gsmtp ##

Original message headers:

Received: from Ourserver.server.local ([fe80::3b8:6284:c31d:5bc2]) by
 Ourserver.server.local ([fe80::3b8:6284:c31d:5bc2%11]) with mapi id
 14.01.0438.000; Mon, 27 Jan 2014 13:00:52 -0500
From: User name <sentfrom@domain.com>
To: "sentto@domain.org" <sentto@domain.org>
Subject: FW: Report from The Customer Account
Thread-Topic: Report from The Customer Account
Thread-Index: Ac8biFqLplaF/YUCT72elYAbGcy8rAAAP7wHAAAvUTAAAE9HwA==
Date: Mon, 27 Jan 2014 18:00:50 +0000
Message-ID: <9E3393AC8EBB604C878FA06D887AC71C3E4E72F4@Ourserver.server.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2602:301:7772:6020:2d31:cda2:d1b5:5fe3]
Content-Type: multipart/alternative;
      boundary="_000_9E3393AC8EBB604C878FA06D887AC71C3E4E72F4BNCSERVER01bncl_"
MIME-Version: 1.0
-------------------------------------------------------------------------------------------------------------------------------

Can you suggest utilities or programs that could be used to troubleshoot if this is a DNS/PTR issue?

Thanks for your help.
0
 
LVL 1

Accepted Solution

by:
Barnett Computers earned 0 total points
ID: 39820886
After working with two different AT&T U-verse support techs over the past two days plus another I.T. support friend, we were able to determine our problem was related to incorrect reverse DNS and PTR records due to the change in our external fixed I.P.  Once we got these records corrected, most of our e-mail sending issues were resolved.  We still have a few isolated issues that we are working on that may be not related.

I learned that the I.P. address we get thru whatsmyip.com or similar websites is considered a "sticky" I.P. and not the fixed I.P. used in DNS.  This had caused a problem when trying to identify the I.P. address that would be used for rDNS.  

It was also determined that AT&T U-verse does not have a SmartHost like AT&T DSL.
0
 
LVL 1

Author Comment

by:Barnett Computers
ID: 39820904
Thanks for all the assistance
0
 
LVL 1

Author Closing Comment

by:Barnett Computers
ID: 39831972
Thanks for the replies on this issue.  Your comments provided items we should check or reverify during this process.  E-mail problems, especially those related to possible DNS issues, are not always easy to identify and resolve.  Your replies were appreciated.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
New style of hardware planning for Microsoft Exchange server.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Suggested Courses
Course of the Month8 days, 14 hours left to enroll

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question