[X] ... the documentation does not mention anything about my problem
[X] ... there are no open or closed issues that are related to my problem
Description
Postfix configuration at the moment is such that check_policy_service comes after permit_mynetworks. The effect is that all mail from local networks is forwarded without checking if, e.g., an alias is activated or not. This is especially problematic when Addy is receiving mail forwarded from a Postfix relay in the same network (e.g., another mail server container on the same host).
Expected behaviour
All mail should be going through the policy service, even if it comes from local networks.
Actual behaviour
If mail comes from local network (e.g., a Postfix relay in the same network), then Addy delivers the email without going through policy checks.
Steps to reproduce
Create Addy instance that is receiving mail from another Postfix server in the same network
Create an alias and deactivate it
Send email to deactivated alias
(mail is delivered even though alias is deactivated)
Support guidelines
I've found a bug and checked that ...
Description
Postfix configuration at the moment is such that
check_policy_service
comes afterpermit_mynetworks
. The effect is that all mail from local networks is forwarded without checking if, e.g., an alias is activated or not. This is especially problematic when Addy is receiving mail forwarded from a Postfix relay in the same network (e.g., another mail server container on the same host).Expected behaviour
All mail should be going through the policy service, even if it comes from local networks.
Actual behaviour
If mail comes from local network (e.g., a Postfix relay in the same network), then Addy delivers the email without going through policy checks.
Steps to reproduce
Docker info
Docker Compose config
No response
Logs
Additional info
Bug is fixed simply by reordering the two in
smtpd_recipient_restrictions
.