In my testing, it seems that local users are allowed to send mail to invalid local recipients and Exim will accept it and bounce it later. It looks like this behavior probably changed in v54, and continues through v56.
However, this change really doesn't work for me since I have a local spam filter proxy sitting in front of Exim. Internet -> port 25 (filter) -> port 2525 (exim). So the new result is that all incoming mail with invalid recipients is now seen as local by Exim and ends up filling my mail queue with frozen bounces to external mail servers.
Previously, I used the Only-verify-recipient option (/etc/trustedmailhosts) to put my local ips and hostnames into so all Exim spam checks/rate limiting/etc would be bypassed for my spam filter proxy, except for recipient verification. This is no longer how it works though!
I did a quick diff compare of an old exim.conf backup, and the current one, and didn't see any particularly obvious config changes that would affect that. But I would assume that the routing is now different to make this change for local users.
Can anyone shed any light into the newer config changes that affect this area? And if I can possibly override them so I can get the old behavior for rejecting invalid recipients for everyone back?
However, this change really doesn't work for me since I have a local spam filter proxy sitting in front of Exim. Internet -> port 25 (filter) -> port 2525 (exim). So the new result is that all incoming mail with invalid recipients is now seen as local by Exim and ends up filling my mail queue with frozen bounces to external mail servers.
Previously, I used the Only-verify-recipient option (/etc/trustedmailhosts) to put my local ips and hostnames into so all Exim spam checks/rate limiting/etc would be bypassed for my spam filter proxy, except for recipient verification. This is no longer how it works though!
I did a quick diff compare of an old exim.conf backup, and the current one, and didn't see any particularly obvious config changes that would affect that. But I would assume that the routing is now different to make this change for local users.
Can anyone shed any light into the newer config changes that affect this area? And if I can possibly override them so I can get the old behavior for rejecting invalid recipients for everyone back?