At 8:14 AM -0500 9/23/02, NetHead  imposed structure on a stream of 
electrons, yielding:
>Well, here is yet another episode in the saga of our e-mail and its
>"blockage".
>
>I attempted to sent an e-mail to the isp which is hosting our european
>subsidiary. Since they share the same mail exchanger, we have had similar
>problems sending mail to them. I sent another test message to them and
>got back this error:
>
>-----begin error snippet-----
>
>>  Return-Path: <>
>
>>  Subject: Undeliverable mail: E-mail status
>
>>  From: [EMAIL PROTECTED]
>
>>  To: [EMAIL PROTECTED]
>
>>  Date: Fri, 20 Sep 2002 08:33:25 -0500
>
>>  Message-Id: <[EMAIL PROTECTED]>

That's a SIMS  Message-ID.  It indicates that a SIMS server created 
the bounce mail.

>
>>  X-Mailer: Stalker Internet Mail Server 1.8b9d14

Yep.

>
>>  MIME-Version: 1.0
>
>>  Content-Type: multipart/report; report-type=delivery-status;
>
>>  boundary="_=receipt=_=32682=_"
>
>>
>
>>  Failed to deliver your message to [EMAIL PROTECTED]:
>
>>  SMTP: Address rejected by host
>
>>  Host 'legend.co.uk' says:
>
>>  554 <[EMAIL PROTECTED]>: Recipient address rejected: Relay access denied

That means exactly what it says.


>>  Reporting-MTA: dns; pecandeluxe.com

That means that the error message was seen by the MTA  on a machine 
believing itself to be named pecandeluxe.com.



>
>>  Final-Recipient: rfc822; [EMAIL PROTECTED]
>
>>  Action: failed
>
>>  Status: 5.0.0
>
>>
>
>>  Received: from [192.168.1.108] ([192.168.1.108] verified)
>
>>    by pecandeluxe.com (Stalker SMTP Server 1.8b9d14)
>
>>    with SMTP id S.0000032528 for <[EMAIL PROTECTED]>; Thu, 19 Sep 2002
>
>>  16:36:27 -0500
>
>>  Subject: E-mail status
>
>>  Date: Thu, 19 Sep 2002 16:36:24 -0500
>
>>  x-sender: [EMAIL PROTECTED]
>
>>  x-mailer: Claris Emailer 2.0v3, January 22, 1998
>
>>  From: Doug Starkey <[EMAIL PROTECTED]>
>
>>  To: "Darren Spink" <[EMAIL PROTECTED]>
>
>>  Mime-Version: 1.0
>
>>  Content-Type: text/plain; charset="US-ASCII"
>
>>
>-----end error snippet-----
>
>Now, my interpretation of this is that Legend's mailserver rejected the
>mail because it saw it as a relay. It DOES say, "Host 'legend.co.uk'
>says"...

You are correct.


>but here is the response I got from Legend (when forwarding this error
>via a different account):
>-----begin quote-----
>From:  [EMAIL PROTECTED]
>To:    [EMAIL PROTECTED]
>Hi Doug,
>
>
>
>An error from our servers would give a "553" not "554". The error seems
>to
>
>have  been generated by:
>
>
>
>Reporting-MTA: dns; pecandeluxe.com
>
>
>
>(MTA - mail transfer agent?)
>

Wrong. Check this out:

toaster# telnet legend.co.uk 25
Trying 212.69.224.224...
Connected to legend.co.uk.
Escape character is '^]'.
220 www.legend.co.uk ESMTP Postfix (Release-20010228) (Linux-Mandrake)
MAIL FROM:<[EMAIL PROTECTED]>
250 Ok
RCPT TO:<[EMAIL PROTECTED]>
554 <[EMAIL PROTECTED]>: Recipient address rejected: Relay access denied
quit
221 Bye
Connection closed by foreign host.


That's a 554 from legend.co.uk for an attempt to send mail to [EMAIL PROTECTED]


HOEWEVER, something odd is happening, because...


toaster# host legend.co.uk
legend.co.uk has address 212.69.224.224
legend.co.uk mail is handled (pri=20) by mx.legend.co.uk
toaster#  host mx.legend.co.uk
mx.legend.co.uk has address 212.69.225.52
toaster# telnet 212.69.225.52 25
Trying 212.69.225.52...
Connected to mx.legend.co.uk.
Escape character is '^]'.
220 Legend Internet SMTP Service (smtp.mail.legend.net.uk) #3 ESMTP
ehlo sc1.scconsult.com
250-Legend Internet SMTP Service (smtp.mail.legend.net.uk) #3
250-PIPELINING
250 8BITMIME
MAIL FROM:<[EMAIL PROTECTED]>
250 ok
RCPT TO:<[EMAIL PROTECTED]>
250 ok
rset
250 flushed
quit
221 Legend Internet SMTP Service (smtp.mail.legend.net.uk) #3
Connection closed by foreign host.



So legend.co.uk is a machine that  doesn't handle mail for addresses 
@legend.co.uk.  The machine mx.legend.co.uk DOES, and it doesn't seem 
to mind accepting mail for [EMAIL PROTECTED]


>-----end quote-----
>Now, my reading of a "554" is that somewhere, a server thinks I'm
>relaying. Presumably my mail server, right? But why would my mail server
>think I'm relaying? I've gone over my configuration. I have all ips on my
>network listed in the client-hosts. I have "Relay for Clients Only"
>checked, I have "Verify Return-Path" checked, I do not use an RBL, but DO
>have my own internal blacklist.
>
>Is it possible this my isp is somehow detecting my e-mail as a "relay"
>attempt and then blocking it?

No.

The unanswered question is why SIMS was trying to use the A record 
for legend.co.uk and not the MX record. Using the A record, you get a 
machine that seems willing to accept mail for [EMAIL PROTECTED]

The SIMS logs might provide a hint as to why it fell back to using 
the A record. That is something it should not do, even if the address 
of the MX record is inaccessible. If there is an MX record but that 
machine can't be reached, the A record should not be treated as a 
potential mail exchanger. That strikes me as a SIMS bug, most likely.

Of course this does not solve your problem: you seem incapable of 
contacting 212.69.225.52 from your SIMS machine. Have you tried a 
traceroute?

-- 
Bill Cole
[EMAIL PROTECTED]


#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>

Reply via email to