diff options
author | Guilhem Moulin <guilhem@fripost.org> | 2014-07-09 23:28:21 +0200 |
---|---|---|
committer | Guilhem Moulin <guilhem@fripost.org> | 2015-06-07 02:52:52 +0200 |
commit | c71f1cf51e7f6e8f43b5f7afb1d8a2012fd83259 (patch) | |
tree | d406b62dcf18c1c70ba9d75db4487e183f7cb9b0 /roles/common/tasks/fail2ban.yml | |
parent | 19b5b582ef0cb02d490ad4c0a99e73c81fc27393 (diff) |
Use $virtual_alias_domains not $virtual_mailbox_domains.
Quoting postconf(5):
smtpd_reject_unlisted_recipient (default: yes)
Request that the Postfix SMTP server rejects mail for unknown recipient
addresses, even when no explicit reject_unlisted_recipient access
restriction is specified. This prevents the Postfix queue from filling
up with undeliverable MAILER-DAEMON messages.
An address is always considered "known" when it matches a virtual(5)
alias or a canonical(5) mapping.
[…]
* The recipient domain matches $virtual_alias_domains but the recipient
is not listed in $virtual_alias_maps.
* The recipient domain matches $virtual_mailbox_domains but the
recipient is not listed in $virtual_mailbox_maps, and
$virtual_mailbox_maps is not null.
Since we alias everything under special, "invalid", domains (mda.f.o and
mailman.f.o), our $virtual_mailbox_maps was null, which led to
reject_unlisted_recipient not being triggered for say, "noone@fripost.org".
However, replacing $virtual_mailbox_domains with $virtual_alias_domains fits
into the second point above.
Diffstat (limited to 'roles/common/tasks/fail2ban.yml')
0 files changed, 0 insertions, 0 deletions