------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1283 Summary: when Exim itself is is bad trouble: why `is is'? Product: Exim Version: 4.80 Platform: Other URL: http://exim.org/exim-html- current/doc/html/spec_html/ch42.html#SECTNOTQUITACL OS/Version: All Status: NEW Severity: bug Priority: low Component: Documentation AssignedTo: [email protected] ReportedBy: [email protected] CC: [email protected] I am not sure weather it should be: 1. is in bad trouble 2. is in a bad trouble 3. is in bad troubles 4. something else --- a/spec.txt 2012-08-16 01:07:02.289604339 +0300 +++ b/spec.txt 2012-08-16 01:06:46.000000000 +0300 @@ -24422,7 +24422,7 @@ connection is closed. In these special c ---------------------- The not-QUIT ACL, specified by acl_smtp_notquit, is run in most cases when an -SMTP session ends without sending QUIT. However, when Exim itself is is bad +SMTP session ends without sending QUIT. However, when Exim itself is in bad trouble, such as being unable to write to its log files, this ACL is not run, because it might try to do things (such as write to log files) that make the situation even worse. -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
