Postfix supports 8bit Data, with lines of 998 between CRLF, as
defined inhttps://datatracker.ietf.org/doc/html/rfc2045#section-2.8
Therefore, Postfix announces 8BITMIME in EHLO.
Postfix does not support Binary Data, as defined in
https://datatracker.ietf.org/doc/html/rfc2045#section-2.9 Binary
Therefore, Postfix does not announce BINARYMIME in EHLO.
Systems that do not announce BINARYMIME in EHLO can receive only
content with lines of 998 between CRLF.
Only systems that anounce BINARYMIME in EHLO can receive content
that is not lines of 998 between CRLF.
Your last two statements are exactly the crux of the matter, and I don't
see them justified, yet. RFC2045 cannot tie its Binary Data to
BINARYMIME, because RFC2045 does not know about RFC3030. RFC2045 just
tells us that Binary Data must be transmitted by a binary-capable
transport. RFC2045 does not say that this needs to be announced by a
specifically named EHLO keyword defined by a specifically numbered RFC.
In my opinion, BDAT itself could already be meant to signal support for
binary payload, as the name most probably stands for Binary DATa.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
