Re: Analysis of an MSN rejection.

• Previous message: ace: "Re: "mark all" in ng's takes aaages....."
• In reply to: PA Bear: "Re: Analysis of an MSN rejection."
• Messages sorted by: [ date ] [ thread ]

Date: Wed, 29 Dec 2004 00:29:32 -0800

In article <OC3NZeH7EHA.2016@TK2MSFTNGP15.phx.gbl>, PA Bear says...

> A very cursory glance at all you posted suggests she was trying to send a
> message using an account other than one associated with her ISP (e.g.,
> sending from normansmother@yahoo.com whilst connected to pacbel).

That is the problem with cursory glances; they are often incorrect. She was
using her ISP account email address on the correct ISP connection, through a
designated ISP mail server. None of the servers which she is authorized to
use rejected her email. It was during the transaction between her ISP's MTA
and the destination MX that the delivery failure occurred. The foreign MX
refused to accept the message from her ISP's mail server, thus her ISP's
mail server generated the bounce.

MUA (MSOE6) > local SMTP server (aosake.net)...authorized and delivered.
Local MTA (aosake.net) > ISP MTA (yahoo.com)...authorized and delivered.
ISP MTA (yahoo.com) > MX (msn.com)...refused at the destination.

Since when does the msn.com MX think that an attempt to send email to an
msn.com user from an ISP's properly designated MTA consist of a relay
attempt? The msn.com server was not being asked to relay a non-msn.com email
to a non-msn.com destination! The source email domain was authorized to use
the server attempting the delivery to an msn.com user through an msn.com MX
server.

Yes, yahoo.com servers do relay for pacbell.net accounts; the servers are
listed here:

http://help.sbcglobal.net/article.php?item=287

There are a total of nine email account domain names for SBC Global
customers. Those SBC customers with SBC Yahoo! DSL (or Dial-Up) Service are
given specific yahoo.com SMTP servers to use. Those servers are SMTP AUTH
servers, and they will accept authorized SBC customer logins from non-SBC IP
addresses; except in the case I cited, the IP address was assigned by SBC
Global.

The same message was recovered from the "Sent Items" folder, and resent with
no changes. The second try at sending went through. Nothing in the routing
from the MUA up to (but not including) the msn.com MX server was changed.
Whatever happened, it was at the msn.com MX server.

-- 
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

• Previous message: ace: "Re: "mark all" in ng's takes aaages....."
• In reply to: PA Bear: "Re: Analysis of an MSN rejection."
• Messages sorted by: [ date ] [ thread ]