Bug #1844
Address extension +spam propagated during message forwarding
| Status: | CLOSED | Start date: | 04/04/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | 04/05/2013 | |
| Assignee: | - | % Done: | 100% | |
| Category: | nethserver-mail-server | |||
| Target version: | v6.4-beta1 | |||
| Security class: | Resolution: | |||
| Affected version: | v6.4-alpha2 | NEEDINFO: |
Description
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:
<john+spam@external.com> (expanded from <users+spam@example.com>): host
mail.external.com[1.2.3.4] said: 550 unknown recipient address
john+spam@external.com (in reply to RCPT TO command)
..while john@external.com is known to exist.
Expected behaviour:
address extensions must not be appended to forward addresses.
Subtasks
Related issues
Associated revisions
NethServer::MailServer (getVirtualMailboxDomain): removed vmail.nh internal domain suffix. Refs #1844
Removed NethServer::MailServer::getVirtualMailboxDomain() method calls. Refs #1844
NethServer::MailServer (getMailboxes): removed obsolete function. 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
History
#1
Updated by Davide Principi over 8 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.
#2
Updated by Davide Principi over 8 years ago
- Due date set to 04/04/2013
- Status changed from NEW to ON_DEV
- Start date set to 04/04/2013
- % Done changed from 0 to 20
#3
Updated by Davide Principi over 8 years ago
- % Done changed from 20 to 80
- Parent task set to #1846
#4
Updated by Davide Principi over 8 years ago
- Parent task deleted (
#1846)
#5
Updated by Davide Principi over 8 years ago
- % Done changed from 80 to 0
- Estimated time deleted (
2.00)
Fixing this bug by implementing delivery through local(8) daemon leaded to .forward files support. See subtask #1846.
#6
Updated by Davide Principi over 8 years ago
- Status changed from ON_DEV to MODIFIED
#7
Updated by Davide Principi about 8 years ago
- Status changed from MODIFIED to CLOSED