------- 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=495
Summary: Failure of callout/random
Product: Exim
Version: N/A
Platform: Other
OS/Version: All
Status: NEW
Severity: wishlist
Priority: high
Component: ACLs
AssignedTo: ph10@???
ReportedBy: grin@???
QAContact: exim-dev@???
It seems that protocol failure on random check is fatal eventually:
2007-04-13 06:46:43 H=(msu.edu) [204.9.147.230] sender verify defer for
<***@msu.edu>: response to "RSET" from lb.mail.msu.edu [35.9.75.15] was:
connection dropped
Connection drops on "RCPT TO:<blah.blah-7673647374-testing@???>"
(invalid rcpt).
It defers, then obviously it fails after a while. These hosts drop the
connection immediately on an invalid recipient, while accepting valid ones.
I would do "callout/defer_does_what_it_have_to,random/defer_ok", if I could. So
exim would try random check, it fails with protocol error, then it would go on
checking the sender, which would succeed. I'd say in that case exim should do
what defer_ok does normally: go on but do not cache the result.
Checking my maillog this behaviour starts to spread (which is unfortunate but
understandable).
--
Configure bugmail:
http://www.exim.org/bugzilla/userprefs.cgi?tab=email
