Re: Cannot Receive Some Emails

From: N. Miller (nsm_at_blackhole.aosake.net)
Date: 02/04/04


Date: Tue, 3 Feb 2004 23:34:14 -0800

In article <#Te6jqr6DHA.2576@TK2MSFTNGP11.phx.gbl>, jogor@bigpond.net.au
says...
> I am having to me what is a peculiar problem.
>
> I am a member of the local Senior Group here and when the Newsletter is sent
> out, it is returned undelivered to the sender, this occurs if he sends it
> through OE, but if he sends it through Netscape then it comes through OK.
>
> Out of about 600 members, this is only happening to about 8 of us. For
> information I have attached an email I received from the coordinator today.
>
> Joe,
>
> Just for the hell of it, I tried to send you a test message vie OE on my own
> PC rather than the LTS laptop. It, too, was returned with an error 550
> recipient unknown message. However there are no problems sending with
> Netscape. There has to be something in the difference in the way that the
> two programs encode the email. The sender's address (dsmitch@trump.net.au vs
> linkingseniors@bigpond.com) obviously doesn't have any bearing.
> Screwy :-(
>
>
> I have contacted my ISP and they say there is no problem.
>
> Can anyone assist please?

Yes and no. As you guessed, there is a difference in the way that MS Outlook
Express and Netscape Mail encodes the SMTP messages; as shown below:

Using the MS Outlook Express 6 MUA:

> Received: from unknown (HELO megumi) (...%pacbell.net@67.116.51.103 with login)
Added by MSOE ^^^^^^^^^^^^^^^^^
> by smtp810.mail.sc5.yahoo.com with SMTP; 4 Feb 2004 06:56:07 -0000
> Message-ID: <000901c3eaeb$eaefbce0$6466a8c0@aosake.net>
> Date: Tue, 3 Feb 2004 22:55:42 -0800
> X-Mailer: Microsoft Outlook Express 6.00.2800.1158
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

Using the Netscape MUA:

> Received: from unknown (HELO pacbell.net) (...%pacbell.net@67.116.51.103 with plain)
Added by Netscape ^^^^^^^^^^^^^^^^^^^^^^
> by smtp804.mail.sc5.yahoo.com with SMTP; 4 Feb 2004 06:51:08 -0000
> Message-ID: <40209649.9010303@pacbell.net>
> Date: Tue, 03 Feb 2004 22:50:49 -0800
> User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

If "smtp8xx.mail.sc5.yahoo.com" was expecting the HELO string to match a
'legal' (for the domain; yahoo.com in this case) FQDN, then it would reject
the first case because 'megumi' is not a legal FQDN.

It might reject the second case because 'pacbell.net' != 'yahoo.com';
however, SBC has a contract with Yahoo! for yahoo.com servers to handle SBC
customer email. Pacbell.net is a legal SBC domain, so it shouldn't be
rejected by the yahoo.com server.

I don't really see why your ISP mail server would behave like that, but you
might want do try using a troubleshooting log and post the results, or show
them to your ISP; or both.

First go to Tools > Options, the "Maintenance" tab, and put a check mark in
the box near the bottom labeled, "Mail". Now, send a message using the email
addresses which fail. After the failure, reset the "Maintenance" menu to
clear boxes.

You should find a file in the same folder as the .dbx folders. Look for
"smtp.log". It should show the SMTP transaction in detail; something like
this:

SMTP: 23:18:40 [rx] 220-aosake.net ESMTP server ready.
SMTP: 23:18:40 [rx] 220-<SMTP server banner>.
SMTP: 23:18:40 [tx] HELO megumi
SMTP: 23:18:40 [rx] 250 aosake.net Hello, megumi.
SMTP: 23:18:40 [tx] MAIL FROM: <email address>
SMTP: 23:18:40 [rx] 250 Sender OK - send RCPTs.
SMTP: 23:18:40 [tx] RCPT TO: <email address>
SMTP: 23:18:40 [rx] 553 We do not relay without RFC2554 authentication.
SMTP: 23:18:40 [tx] QUIT
SMTP: 23:18:40 [rx] 221 aosake.net Service closing channel.

I'd like to see what you get, just to see why the error happens.

-- 
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


Relevant Pages

  • Re: Adding DNS records to stroseparish.local
    ... I know SBC has been bought by At&t but their smtp server at least ... restarted the routing and smtp services and tried sending email out. ... the Server Management Console and choosing either Smart Host or DNS ...
    (microsoft.public.windows.server.sbs)
  • RE: SMTP Server remote queue length alert
    ... Thank you for posting in the SBS newsgroup. ... automatically creates a SMTP connector for outgoing messages. ... bridgehead defines the Exchange server which can use this SMTP connector to ... What method is used to send outgoing email (DNS route or ISP ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange, BadMail Folder
    ... always growing after you have removed files from folder and unplug server ... Furthermore,Please refer to the following KB article to clean up the SMTP ... click SmallBusiness SMTP Connector under ... them in a single queue for the SmallBusiness SMTP Connector or for the one ...
    (microsoft.public.windows.server.sbs)
  • RE: SMTP error (only from Outlook)
    ... This issue appeared on specify user or all SMTP clients? ... If yes, in Exchange System ... Is there any local bridgehead server listed in "Local ... to over three dozen open relay block lists. ...
    (microsoft.public.windows.server.sbs)
  • RE: Email messages stuck in unreachable destination queue
    ... you configure sharing an SMTP address space in Exchange Server 2003 thru ... it seems like you do not block the open SMTP relaying ... on the Exchange server. ... To check the properties for the SmallBusiness SMTP Connector, ...
    (microsoft.public.windows.server.sbs)