From: Matthias Andree (madt.e-technik.uni-dortmund.de)
Date: Thu Jan 12 2006 - 06:41:02 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Mezei Zoltán <mezei.zoltantelefor.hu> writes:

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

...

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

Looks like some "firewall" or packet filtering jams the communication so
your client doesn't see your 354 message as Postfix uses it. This is a
gross defect on the client side, the RFC string isn't fixed except for
the leading "354 " part and the CRLF at the end.

What is in the RFC examples are just that, examples. Postfix could just
as well print

354 Bring 'em on!

or more aggressively

354 Du hast doofe Ohren!

or just

354 OK

and be in compliance with the RFC (although not with common rules of
politeness, it's a mild insult of the reader's ears. Deemed it
appropriate here.)

Postfix's original message is just being polite to the reader.

--
Matthias Andree

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]