vfx9as:
[ Charset ISO-8859-1 unsupported, converting... ]
> (10/11/22 01:33), Wietse Venema wrote:
> > vfx9as:
> >> 2010/11/21 Wietse Venema <wie...@porcupine.org>:
> >>> vfx9as:
> >>>> In 980 characters or more lines as it will split 1 postfix, and long
> >>>> lines to fill in
> >>>> Line characters sent so I do not think 980 RFC violation.
> >>>
> >>> Please read RFC 5322 Section 2.2.3. Long Header Fields
> >>
> >> "Body" problem
> >> No headers
> >
> > In that case, please consider reading up on the quoted-printable
> > (or base64) encoding: RFC 2045, RFC 2046, and related material.
> >
> > If you want to maximize the chances of email delivery, then you
> > need to send lines less than an 80-column punchcard wide.
> >
> > If you insist on staying just a few bytes under the protocol limit,
> > then you are inviting trouble. I agree that such trouble should not
> > exist, but that is the world we have today.
> >
> > Wietse
>
> The increase in the number of characters is not.
The Postfix smtp_line_length_limit feature is not a mail formatting
feature: it is not expected to play nice with DKIM signatures
(not with the local MTA's own signature, and not with the signature
from some up-stream system.
Instead, purpose of the limit is to ensure that mail will not be
dropped by some borked mail system or firewall.
If you want to play with mail, please send well-formatted email,
that's text <80 and use encapsulation as defined by RFCs. These
things exist for a purpose.
Wietse
