Address extension +spam propagated during message forwarding
When "Forward messages" is enabled and a spam message is received the address extension
+spam is propagated to the forward address.
The remote mail server may not accept address extensions:
<firstname.lastname@example.org> (expanded from <email@example.com>): host mail.external.com[18.104.22.168] said: 550 unknown recipient address firstname.lastname@example.org (in reply to RCPT TO command)
email@example.com is known to exist.
address extensions must not be appended to forward addresses.
NethServer::MailServer (getVirtualMailboxDomain): removed vmail.nh internal domain suffix. Refs #1844
Removed NethServer::MailServer::getVirtualMailboxDomain() method calls. Refs #1844
NethServer::MailServer (getMailboxAliases): Expand virtual addresses to a local account name Mail forwards must be implemented through local(8) daemon. Refs #1844
/etc/postfix/aliases template: 30forwards fragment delivers messages to aliases defined by user's MailForward* props. Refs #1844
/etc/postfix/virtual template (15amavis_accounts): refactored code using global $mailServer variable. Refs #1844
NethServer::MailServer (getMailboxForwards): fixed MailForwardKeepMessageCopy check logic. Refs #1844
#1 Updated by Davide Principi over 6 years ago
When a message is classified as SPAM the
+spam extension is appended to the recipient's local address part.
Postfix keeps the extension during subsequent address-rewritings (see propagate_unmatched_extensions parameter).
Another mechanism must be implemented to expand forward address for virtual domains.