------- 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=245
------- Comment #1 from anomie@??? 2006-11-08 02:19 -------
Created an attachment (id=29)
--> (
http://www.exim.org/bugzilla/attachment.cgi?id=29&action=view)
Patch to allow message modifiers on accept statements
Hopefully this is close enough to the Right Way. 'message' will be recognized
for acceptance of acl_smtp_connect, acl_smtp_helo, acl_smtp_mail,
acl_smtp_rcpt, acl_smtp_predata, acl_smtp_data, and acl_smtp_etrn. All allow
for overriding the SMTP code as deny messages do since 4.63. acl_smtp_auth,
acl_smtp_expn, acl_smtp_mailauth, acl_smtp_mime, acl_smtp_starttls, and
acl_smtp_vrfy all do further processing after the ACL returns, which sets the
resonse code. acl_smtp_quit already had support for message modifiers (although
it didn't handle multiline responses well at all).
A message modifier on acl_smtp_connect will override smtp_banner.
A message modifier on acl_smtp_helo is limited to one line, and thus cannot
affect the EHLO keywords. The grammar in RFC 2821 only seems to allow one line
before the keywords.
accept with endpass as it currently exists is handled as it is currently
handled: the message modifier is used when the statement denies, and acceptance
uses the default message. I've altered endpass to optionally take an argument
("endpass = text"); when this is used, the message modifier is used for
acceptance and the endpass text is used for denial.
--
Configure bugmail:
http://www.exim.org/bugzilla/userprefs.cgi?tab=email
