[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How aggressively to reject Pipelining errors?



Carl S. Gutekunst <csg@xxxxxxxxxxx> wrote:
>
> At the moment, I'm only performing this check after the STARTTLS command. But
> that got me to wondering: would it be wise/unwise to check after other
> commands, e.g., EHLO, DATA, or AUTH? RFC 2920 is silent on the topic of what
> the server may do if the client violates the rules.

Exim does fairly aggressive synchronization checks by default and has done
for many years. It does not cause interop problems in my experience.

See the "pipelining_advertise_hosts", "smtp_enforce_sync", and
"smtp_max_synprot_errors" options at
http://exim.org/exim-html-current/doc/html/spec_html/ch14.html

(sorry, the options don't have individual anchors)

Tony.
-- 
f.anthony.n.finch  <dot@xxxxxxxx>  http://dotat.at/
Lundy, Fastnet, Irish Sea: Northwest backing west 5 to 7, decreasing 4 for a
time. Moderate or rough, but very rough in Fastnet at first. Squally showers,
rain later. Good, occasionally moderate.