Smart Host for AT&T U-verse
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Mike Roe
Can you post a undeliverable text with important info cleared
ASKER
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
Ourserver.domain.local ([fe80::3b8:6284:c31d:5bc2
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/vNObi
Disposition-Notification-T
Date: Wed, 22 Jan 2014 15:37:09 +0000
Message-ID: <9E3393AC8EBB604C878FA06D8
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_9E3393AC8EB
MIME-Version: 1.0
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
Ourserver.domain.local ([fe80::3b8:6284:c31d:5bc2
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/vNObi
Disposition-Notification-T
Date: Wed, 22 Jan 2014 15:37:09 +0000
Message-ID: <9E3393AC8EBB604C878FA06D8
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_9E3393AC8EB
MIME-Version: 1.0
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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:5
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:5
Original message headers:
Received: from Ourserver.server.local ([fe80::3b8:6284:c31d:5bc2
Ourserver.server.local ([fe80::3b8:6284:c31d:5bc2
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/YUCT72elYAbGc
Date: Mon, 27 Jan 2014 18:00:50 +0000
Message-ID: <9E3393AC8EBB604C878FA06D8
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2602:301:7772:6020:2d31:c
Content-Type: multipart/alternative;
boundary="_000_9E3393AC8EB
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.
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:5
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:5
Original message headers:
Received: from Ourserver.server.local ([fe80::3b8:6284:c31d:5bc2
Ourserver.server.local ([fe80::3b8:6284:c31d:5bc2
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/YUCT72elYAbGc
Date: Mon, 27 Jan 2014 18:00:50 +0000
Message-ID: <9E3393AC8EBB604C878FA06D8
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2602:301:7772:6020:2d31:c
Content-Type: multipart/alternative;
boundary="_000_9E3393AC8EB
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all the assistance
ASKER
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.