You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm testing your image and got an unexpected behaviour.
Note: example.org is not the real domain I'm using. With that domain, some MX record failures come around. But with a proper DNS configuration of the real domain, the example works like explained.
Running the relay in a device with 10.0.0.100 IP address:
The postfix configuration was a bit too permissive with `mynetworks`.
This commit:
- adds `reject` at the end of `*restrictions` list
- adds tests for this feature
Hi! I'm testing your image and got an unexpected behaviour.
Running the relay in a device with 10.0.0.100 IP address:
docker run --rm --name postfix \ -e "ALLOWED_SENDER_DOMAINS=example.org" \ -e POSTFIX_mynetworks=192.168.0.0/16 \ -p 587:587 \ boky/postfix:v2.0.1
And then, sending an email from a local device with 10.0.0.103 IP address:
Accepts connection and sends email, but only 192.168.0.0/16 was allowed. So this shouldn't be possible.
I'm using
POSTFIX_smtpd_client_restrictions=permit_mynetworks,reject
as a workaround, and works like expected:docker run --rm --name postfix \ -e "ALLOWED_SENDER_DOMAINS=example.org" \ -e POSTFIX_mynetworks=192.168.0.0/16 \ -e POSTFIX_smtpd_client_restrictions=permit_mynetworks,reject \ -p 587:587 \ boky/postfix:v2.0.1
Maybe this
smtpd_client_restrictions=permit_mynetworks,reject
should be set by default in postfix configuration? Thanks!The text was updated successfully, but these errors were encountered: