Mailing List Archive: [Bug 469] Synch not enfored during predata ACL

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

http://www.exim.org/bugzilla/show_bug.cgi?id=469

------- Comment #1 from holmgren@lysator.liu.se 2007-02-14 12:39 -------
On Tuesday 13 February 2007 15:14, exim-users@lists.grepular.com wrote:
> I have a delay in the predata acl. It doesn't seem to cause
> synchronization errors when I *think* it should. Is this a bug?

I think you're correct. AFAICT from the code, Exim doesn't check that the
input buffer is empty before issuing the 354 response. It seems like a
sensible thing to do, and quoting RFC 2821 §3.3, "message data MUST NOT be
sent unless a 354 reply is received".

--
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

http://www.exim.org/bugzilla/show_bug.cgi?id=469

ph10@hermes.cam.ac.uk changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED

------- Comment #2 from ph10@hermes.cam.ac.uk 2007-02-20 16:01 -------
Previously, all the sync checks happened immediately after a command was read.
Thus, it would have checked when it read DATA. This is fine when there are no
delays, but delays change things. I have now put in an additional check just
before it sends the 354, and similarly for HELO and for MAIL and RCPT when
pipelining is not advertised. The code is committed.

--
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email

--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##