On Mon, Dec 18, 2023 at 05:40:49PM -0500, Wietse Venema wrote:
> > - Postfix 3.8.1, 3.7.6, 3.6.10 and 3.5.20 include the same supporting
> > code as 3.9 snapshots, but the "smtpd_forbid_unauth_pipelining"
> > parameter defaults to "no".
>
> Indeed, setting "smtpd_forbid_unauth_pipelining = yes" prevents
> Postfix from accepting a smuggled message after it has allowed a
> malformed end-of-data.
>
> This has the potential to break mail from poorly-implemented clients,
> just like a stricter enforcement of <CR><LF> line boundaries would.
To be more precise: just like it could break a potentially *different*
set of poorly-implemented clients. My instinct is that fewer clients
would be broken by strict enforcement of pipelining than by strict
<CRLF> enforcement, but that's a guess, and it behooves each site to
determine their own situation.
For now, enforcement of pipelining is actually available, while
enforcement of <CRLF> vs. <LF> is still only a hypothetical.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
