RE: can't send to yahoo.com
- From: "luke levis" <luke.levis@xxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Thu, 12 Aug 2004 11:52:01 -0400
here's an interesting twist.. our network is connected by a frame relay
connection and our mail server in our philly office can send to yahoo, and aol,
etc. just fine but our mailserver here can't
-----Original Message-----
From: Lara, Greg [mailto:GLara@xxxxxxx]
Sent: Thursday, August 12, 2004 11:47 AM
To: [ExchangeList]
Subject: [exchangelist] RE: can't send to yahoo.com
http://www.MSExchange.org/
Luke, it could be a dns issue as Chris mentioned, but the www.dnsreport.com
report for your domain indicated that you're an open relay. I don't know if
Yahoo rejects based on that, but I wouldn't be surprised, given the volume
of UCE they must process.
Greg Lara
----------------------------------------------------------------------------
---------------------------
This e-mail message may contain privileged, confidential and/or proprietary
information intended only for the person(s) named. If you are not the
intended recipient, please destroy this message, and any attachments, and
notify the sender by return e-mail. If you are not the intended
recipient(s), or the employee or agent responsible for delivering the
message to the intended recipient(s), you are hereby notified that any
dissemination, disclosure or copying of this communication is strictly
prohibited.
----------------------------------------------------------------------------
---------------------------
-----Original Message-----
From: luke levis [mailto:luke.levis@xxxxxxxxxx]
Sent: Thursday, August 12, 2004 11:00 AM
To: [ExchangeList]
Subject: [exchangelist] RE: can't send to yahoo.com
http://www.MSExchange.org/
ok this is an email I got back this morning from one I sent yesterday
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipients has been delayed.
llevis@xxxxxxxxx
and here is the SMTP header
Microsoft Mail Internet Headers Version 2.0
From: postmaster@xxxxxxxxxx
To: luke.levis@xxxxxxxxxx
Date: Thu, 12 Aug 2004 02:46:13 -0400
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="9B095B5ADSN=_01C47A59CCF46D600002C8B7scmail01.smginc."
X-DSNContext: 7ce717b1 - 1418 - 00000004 - C00402D1
Message-ID: <ednHM3SOl00010dea@xxxxxxxxxxxxxxxxxxx>
Subject: Delivery Status Notification (Delay)
--9B095B5ADSN=_01C47A59CCF46D600002C8B7scmail01.smginc.
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01C47A59CCF46D600002C8B7scmail01.smginc.
Content-Type: message/delivery-status
--9B095B5ADSN=_01C47A59CCF46D600002C8B7scmail01.smginc.
Content-Type: message/rfc822
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C47FD2.EF4F88E1"
Subject:
Date: Wed, 11 Aug 2004 14:42:20 -0400
Message-ID: <EE6665357CA2004B9F78AF6936D147400ADAC9@xxxxxxxxxxxxxxxxxx>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Index: AcR/0u9aiup+2KBSQjm1gxHJjKD5vg==
From: "luke levis" <luke.levis@xxxxxxxxxx>
To: <llevis@xxxxxxxxx>
------_=_NextPart_001_01C47FD2.EF4F88E1
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
------_=_NextPart_001_01C47FD2.EF4F88E1
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
------_=_NextPart_001_01C47FD2.EF4F88E1--
--9B095B5ADSN=_01C47A59CCF46D600002C8B7scmail01.smginc.--
-----Original Message-----
From: Lara, Greg [mailto:GLara@xxxxxxx]
Sent: Thursday, August 12, 2004 10:17 AM
To: [ExchangeList]
Subject: [exchangelist] RE: can't send to yahoo.com
http://www.MSExchange.org/
Thanks Al, I appreciate your thorough answer.
RFC 821 is pretty loose in terms of the semantic requirements of the SMTP
"conversation," and your explanation clarifies very well why. I guess a
discussion of the SMTP protocol is outside the realm of this list, but I'll
let it suffice to say that until the more recent RFCs (such as 2505) carry
more weight with software developers and administrators, or until a better
protocol is developed, UCE will continue to plague us.
Greg Lara
----------------------------------------------------------------------------
---------------------------
This e-mail message may contain privileged, confidential and/or proprietary
information intended only for the person(s) named. If you are not the
intended recipient, please destroy this message, and any attachments, and
notify the sender by return e-mail. If you are not the intended
recipient(s), or the employee or agent responsible for delivering the
message to the intended recipient(s), you are hereby notified that any
dissemination, disclosure or copying of this communication is strictly
prohibited.
----------------------------------------------------------------------------
---------------------------
-----Original Message-----
From: Mulnick, Al [mailto:Al.Mulnick@xxxxxxxxxx]
Sent: Thursday, August 12, 2004 9:34 AM
To: [ExchangeList]
Subject: [exchangelist] RE: can't send to yahoo.com
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
luke.levis@xxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
Other related posts:
