Receiving bounce back when sending to some email address
I have a user that seems to always get these error messages when sending to a domain:
-----Original Message-----
From: MAILER-DAEMON@n12.bullet.m
[mailto:MAILER-DAEMON@n12.
Sent: Wednesday, March 26, 2008 12:02 PM
To: eantolin@lendscape.com
Subject: failure notice
Sorry, we were unable to deliver your message to the following address.
<jchrealestate@sbcglobal.n
Message expired for domain sbcglobal.net
--- Below this line is a copy of the message.
Received: from [68.142.200.227] by n12.bullet.mail.mud.yahoo.
24 Mar 2008 17:06:54 -0000
Received: from [68.142.201.71] by t8.bullet.mud.yahoo.com with NNFMP; 25 Mar
2008 00:12:59 -0000
Received: from [127.0.0.1] by omp423.mail.mud.yahoo.com with NNFMP; 25 Mar
2008 00:12:59 -0000
X-Yahoo-Newman-Id: 284282.1363.bm@omp423.mail
Message-ID: <284282.1363.bm@omp423.mai
Received: (qmail 67241 invoked from network); 25 Mar 2008 00:12:58 -0000
Received: from unknown (HELO EdwilOffice) (kp87mariners@75.62.107.17
login)
by smtp114.plus.mail.sp1.yaho
X-YMail-OSG:
AIvTzRoVM1nCWLurgT84QhY8hD
X-Yahoo-Newman-Property: ymail-3
From: "Edwil Antolin" <eantolin@lendscape.com>
To: "'Joji Holzwarth'" <jchrealestate@sbcglobal.n
Cc: "'William S. Velasco'" <wsvelasco@gmail.com>
Subject: update
Date: Mon, 24 Mar 2008 17:18:58 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AciODdFacnXkW6UTSGqlyREx9L
This is a multi-part message in MIME format.
------=_NextPart_000_0253_
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding:
Does anybody know what could be causing this? He's on my Exchange 2003 server, but since he's a remote user, he uses POP3 for his incoming, and his own ISP for his SMTP server. I'm not having any other issues with any other users.
-----Original Message-----
From: MAILER-DAEMON@n12.bullet.m
[mailto:MAILER-DAEMON@n12.
Sent: Wednesday, March 26, 2008 12:02 PM
To: eantolin@lendscape.com
Subject: failure notice
Sorry, we were unable to deliver your message to the following address.
<jchrealestate@sbcglobal.n
Message expired for domain sbcglobal.net
--- Below this line is a copy of the message.
Received: from [68.142.200.227] by n12.bullet.mail.mud.yahoo.
24 Mar 2008 17:06:54 -0000
Received: from [68.142.201.71] by t8.bullet.mud.yahoo.com with NNFMP; 25 Mar
2008 00:12:59 -0000
Received: from [127.0.0.1] by omp423.mail.mud.yahoo.com with NNFMP; 25 Mar
2008 00:12:59 -0000
X-Yahoo-Newman-Id: 284282.1363.bm@omp423.mail
Message-ID: <284282.1363.bm@omp423.mai
Received: (qmail 67241 invoked from network); 25 Mar 2008 00:12:58 -0000
Received: from unknown (HELO EdwilOffice) (kp87mariners@75.62.107.17
login)
by smtp114.plus.mail.sp1.yaho
X-YMail-OSG:
AIvTzRoVM1nCWLurgT84QhY8hD
X-Yahoo-Newman-Property: ymail-3
From: "Edwil Antolin" <eantolin@lendscape.com>
To: "'Joji Holzwarth'" <jchrealestate@sbcglobal.n
Cc: "'William S. Velasco'" <wsvelasco@gmail.com>
Subject: update
Date: Mon, 24 Mar 2008 17:18:58 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AciODdFacnXkW6UTSGqlyREx9L
This is a multi-part message in MIME format.
------=_NextPart_000_0253_
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding:
Does anybody know what could be causing this? He's on my Exchange 2003 server, but since he's a remote user, he uses POP3 for his incoming, and his own ISP for his SMTP server. I'm not having any other issues with any other users.
abhaigh
where does the mx record for that domain point to?
ASKER
which domain???? his incoming mail server: mail.lendscape.com points to 209.77.206.10
sbcglobal.net
that's the domain that is generating the error, not lendscape
that's the domain that is generating the error, not lendscape
ASKER
E-mail Tester results for sbcglobal.net
Email link to resultsGenerated by www.DNSstuff.com
Getting MX record for sbcglobal.net (from local DNS server, may be cached)... Got it!
Host Preference IP(s) [Country] sbcmx6.prodigy.net. 10 207.115.36.20 [US] sbcmx7.prodigy.net. 10 207.115.37.21 [US] sbcmx8.prodigy.net. 10 207.115.36.22 [US] sbcmx9.prodigy.net. 10 207.115.37.23 [US] sbcmx1.prodigy.net. 10 207.115.21.20 [US] sbcmx2.prodigy.net. 10 207.115.20.21 [US] sbcmx3.prodigy.net. 10 207.115.21.22 [US] sbcmx4.prodigy.net. 10 207.115.20.23 [US] sbcmx5.prodigy.net. 10 207.115.21.24 [US] --------------------------
Step 1: Try connecting to all of these (in a random order, per RFC1123 5.3.4):
sbcmx6.prodigy.net. - 207.115.36.20
sbcmx7.prodigy.net. - 207.115.37.21
sbcmx8.prodigy.net. - 207.115.36.22
sbcmx9.prodigy.net. - 207.115.37.23
sbcmx1.prodigy.net. - 207.115.21.20
sbcmx2.prodigy.net. - 207.115.20.21
sbcmx3.prodigy.net. - 207.115.21.22
sbcmx4.prodigy.net. - 207.115.20.23
sbcmx5.prodigy.net. - 207.115.21.24
Step 2: If still unsuccessful, queue the E-mail for later delivery.
Note: if you enter an entire E-mail address (such as postmaster@sbcglobal.net),
to each mailserver to ensure that they are live and accept mail to the sbcglobal.net domain.NOTE: This tool does NOT attempt to determine if an E-mail address exists!
Email link to resultsGenerated by www.DNSstuff.com
Getting MX record for sbcglobal.net (from local DNS server, may be cached)... Got it!
Host Preference IP(s) [Country] sbcmx6.prodigy.net. 10 207.115.36.20 [US] sbcmx7.prodigy.net. 10 207.115.37.21 [US] sbcmx8.prodigy.net. 10 207.115.36.22 [US] sbcmx9.prodigy.net. 10 207.115.37.23 [US] sbcmx1.prodigy.net. 10 207.115.21.20 [US] sbcmx2.prodigy.net. 10 207.115.20.21 [US] sbcmx3.prodigy.net. 10 207.115.21.22 [US] sbcmx4.prodigy.net. 10 207.115.20.23 [US] sbcmx5.prodigy.net. 10 207.115.21.24 [US] --------------------------
Step 1: Try connecting to all of these (in a random order, per RFC1123 5.3.4):
sbcmx6.prodigy.net. - 207.115.36.20
sbcmx7.prodigy.net. - 207.115.37.21
sbcmx8.prodigy.net. - 207.115.36.22
sbcmx9.prodigy.net. - 207.115.37.23
sbcmx1.prodigy.net. - 207.115.21.20
sbcmx2.prodigy.net. - 207.115.20.21
sbcmx3.prodigy.net. - 207.115.21.22
sbcmx4.prodigy.net. - 207.115.20.23
sbcmx5.prodigy.net. - 207.115.21.24
Step 2: If still unsuccessful, queue the E-mail for later delivery.
Note: if you enter an entire E-mail address (such as postmaster@sbcglobal.net),
to each mailserver to ensure that they are live and accept mail to the sbcglobal.net domain.NOTE: This tool does NOT attempt to determine if an E-mail address exists!
well - all I can say is that, going by the header information, yahoo's mail servers are having issues sendingto that domain
From: MAILER-DAEMON@n12.bullet.m
though why that piece of mail is getting stuck there is a mystery
From: MAILER-DAEMON@n12.bullet.m
though why that piece of mail is getting stuck there is a mystery
ASKER
i agree.... his ISP at his office is SBC/AT&T so he's using them as his SMTP server. I'm thinking it could be that he's maybe not using SSL on the SMTP side. I vaguely remember AT&T say something about them changing to SSL, but I can't remember.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.