Bug#968089: exim4-config: bad order of message in require ACL
Slavko
linux at slavino.sk
Sat Aug 8 12:10:56 BST 2020
Package: exim4-config
Version: 4.94-7
Recently, the message directives was placed on end of ACL, which is
right for deny, but not for require. Current implementation:
require
domains = +local_domains : +relay_to_domains
message = relay not permitted
If this ACL verb is in action, will result in:
-> RCPT TO:<slavko at example.org>
<** 550 Administrative prohibition
This happens, because the message directive is not reached, if domains
condition is not true. For require verb, the message have to be before
conditions to apply:
require
message = relay not permitted
domains = +local_domains : +relay_to_domains
Now the result is:
-> RCPT TO:<slavko at example.org>
<** 550 relay not permitted
BTW: really tested on backports package...
regards
--
Slavko
http://slavino.sk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: Digitálny podpis OpenPGP
URL: <http://alioth-lists.debian.net/pipermail/pkg-exim4-maintainers/attachments/20200808/cd0a7653/attachment.sig>
More information about the Pkg-exim4-maintainers
mailing list