Fetchmail delivers to non-existing email addresses
Fetchmail allow to choose the destination of the emails that it fetches but shows a list of users instead of available email addresses.
If there isn't a email address like username@domain the messages aren't delivered
Jun 9 09:53:31 [err] reading message firstname.lastname@example.org@mail.domain.com:79 of 517 (2736 octets) (log message incomplete) Jun 9 09:53:31 [err] SMTP error: 550 5.1.1 <email@example.com>: Recipient address rejected: User unknown in virtual mailbox table Jun 9 09:53:31 [err] mail from MAILER-DAEMON@serv01.domain.com bounced to firstname.lastname@example.org Jun 9 09:53:32 [err] can't even send to fetchmail!
#1 Updated by Giacomo Sanchietti almost 6 years ago
- Status changed from NEW to TRIAGED
- Assignee set to Davide Principi
- Target version set to v6.5
- % Done changed from 0 to 20
The real bug is that a chosen account from the interface should be mapped to its own aliases inside fetchmail configuration.
As a workaround, create a mail account with the same name as the account.
#3 Updated by Davide Principi almost 6 years ago
- Subject changed from Fetchmail allows to choose users instead of available email addresses to Fetchmail delivers to non-existing email addresses
- Status changed from ON_DEV to MODIFIED
- Assignee deleted (
- % Done changed from 30 to 60
The modified version should fix the problem. Moreover an account with no mail addresses associated is skipped in configuration and a warning is sent to /var/log/messages during daemon startup.
#8 Updated by Davide Principi almost 6 years ago
Filippo Carletti wrote:
The interface should offer to map external accounts to internal email addresses, not internal user or groups, because there's no guarantee that a user or group have an associated email address.
You're right: the email address could not be there, and result to a "silent fail". The warning message is not enough. Think the modified version as a workaround more than a real fix.
Anyway I would prefer to deliver messages directly to user's mailbox, avoiding additional level of indirections and mail-forwarding.
A possible alternative way is talking directly to amavis on port 10024, bypassing the mail recipient restrictions, and SMTP AUTH.
#10 Updated by Giacomo Sanchietti almost 6 years ago
I'd like to have the possibility to choose if a mailbox should or shouldn't be checked for antivirus/antispam.Something like a
enabled, mail will be sent to amavis port
disabled, mail will be delivered using a mda (see
-moption on fetchmail manual)
#13 Updated by Stefano Fancello almost 6 years ago
- Status changed from ON_QA to VERIFIED
- Assignee deleted (
- % Done changed from 70 to 90
on nethserver-fetchmail-1.0.3-1.ns6.noarch, got this on log:
# tail /var/log/fetchmail.log Jul 3 18:40:13 [err] impossibile anche inviare a fetchmail. Jul 3 18:40:13 [info] non eliminato Jul 3 18:40:13 [err] lettura del messaggio email@example.com in corso: 4 di 5093 (459 ottetti nell'intestazione) (messaggio di registro incompleto) Jul 3 18:40:13 [err] Errore SMTP: 550 5.1.1 <firstname.lastname@example.org>: Recipient address rejected: User unknown in virtual mailbox table Jul 3 18:40:13 [err] impossibile anche inviare a fetchmail. Jul 3 18:40:13 [info] non eliminato
on nethserver-fetchmail-1.0.3-3.0git942e8bf4.ns6.noarch mail are sent to user inbox