OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: 534 messages

From: mouss (usebsdfree.fr)
Date: Thu Jan 12 2006 - 15:35:38 CST


Mezei Zoltán a écrit :
> Hi,
>
> I've just finished setting up a new postfix mail server.
>
> However when receiving mail from some mail servers, they just wasn't
> delivered. I finally solved the problem, and here is the description, it
> may be useful.
>
> The SMTP chat begun correctly, EHLO, MAIL FROM and RCPT TO was sent and
> answered. After that postfix received DATA and answered
>
> "354 End data with <CR><LF>.<CR><LF>"
>
> No answers came after that, and the TCP package was repeated many times,
> before the 5 mins timeout exceeded. After that the DATA transfer ended
> without success.
>
> The postfix logs didn't say any other useful info, neither did
> tcpdump/tethereal.
>
> I looked at the documentation and found in the faq that it should be a
> cisco pix problem or an MTU problem - neither solution mentioned there
> helped.
>
> After hours of trying I found out that changing the 354 message to:
>
> "354 Start mail input; end with <CRLF>.<CRLF>"
>
> solves the problem. This is the exact recommendation from the RFC. I
> _know_ that it is a recommendation and it doesn't mean that you have to
> use the exact same string.
>
> I tried to contact the sysadmin of the other side. The domain belonged
> to a Hungarian bank, so he wasn't allowed to provide information about
> their system (proxies, mail servers) but assured me that I was right:
> they check for the exact same string that appears in the second quote.
>
> Is it maybe possible to implement a feature in postfix to allow
> changeable 354 (and other SMTP) messages? I know the problem isn't in
> postfix but in the other mail system, but this change won't ruin
> anything and would help some people. I lack the C programming knowledge
> to implement this feature.
>

while we are in, I also want postfix to be modified to support my new
MTA which only accepts mail sent to
        <forward-path> [ SP <rcpt-parameters> ] <CRLF>
which I copied directly from the RFC. any other rcpt is rejected.

come on... bug-ward compatibility brought more problems than solutions.