mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 09:26:00 +03:00
[GH-ISSUE #1197] Mail for non-existing users is not rejected during SMTP dialog #977
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#977
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @helgew on GitHub (Jul 27, 2017).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1197
Impacted versions
Current behavior
After removing a user who received a lot of spam, messages for the now deleted user are still processed for spam and quarantined.
Expected behavior
Mail for non-existing users should be rejected outright.
@tonioo commented on GitHub (Jul 28, 2017):
@helgew Actually, it is a normal behaviour if you installed Modoboa using the installer. Spam detection comes after postscreen and before postfix verifies if recipient exists. (see http://www.postfix.org/SMTPD_PROXY_README.html)
@helgew commented on GitHub (Jul 28, 2017):
I see. Would you have any advice on how to configure
smtpd_reject_unlisted_recipientso that it would work with the virtual recipients configured via modoboa? My understanding is thatsmtpd_reject_unlisted_recipientkicks in during the SMTP dialogue.@tonioo commented on GitHub (Aug 9, 2017):
I think it'd work, but after postscreen and amavis checks (which is not a bad thing, think about a ddos using fake addresses). Have you tried to activate this setting?
@tonioo commented on GitHub (Sep 15, 2017):
Inactive thread => close.