[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SMTP problem

On Tue, Feb 11, 2003 at 03:09:54PM +0000, Simon Brock wrote:
> We run various zmailer versions here and all are having problem 
> talking to one mailer.  I do not know what the destination is (yet) 
> but here is what it does (with the names changed):
> 220 xxxx.yyy.co.uk ESMTP service
> EHLO mailman.widearea.co.uk
> 250-xxxx.yyy.co.uk talking to mailman.widearea.co.uk ([])
> 250-SIZE 0
> 250-DSN
> 250-AUTH
> 250 8BITMIME
> MAIL From:<shb@widearea.co.uk> BODY=8BITMIME SIZE=525
> 250 2.0.0 shb@widearea.co.uk OK
> RCPT To:<wwww@zzzz.co.uk> NOTIFY=FAILURE ORCPT=rfc822;wwww@zzzz.co.uk
> 550 5.7.1 Bad recipient format -- possible relay attempt
> I can make two further observations:
> -- if I talk directly to the server and say this:
> RCPT To:<wwww@zzzz.co.uk> NOTIFY=FAILURE ORCPT=rfc822;
> it is happy

Hmm..  Yes, possibly that is valid syntax, I don't now have time
to parse thru  RFC 1891/3461  to verify that.

> -- looking in our log files, the only mailer which I can see which 
> puts something after the ';' is zmailer.  Is that true and can it be 
> disabled.

That is  DSN  (Delivery Status Notification) extension's ORCPT
parameter. (RFC 1891/3461 will explain more.)

Previously I have seen "transparent" firewalls that mutilate
through-flowing protocol e.g. by changing the ";" to a space
(or something), which then causes all manner of "fun".

You could ask the remote side system, if they are running
a Cisco PIX with MAILGUARD enabled.

Further examples:

I have begun to route email to some destinations to channel
"smtp77", which is "forced plain non-extended rfc-821, no matter
of EHLO reports various capabilities" -- that apparently helps
to some sites.

> Regards,
> Simon.
/Matti Aarnio	<mea@nic.funet.fi>
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi