-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manual mailadress add to Blacklist #103
Comments
@WASDIT For now, this is not something modoboa supports. |
@tonioo any possible solution to block it? anywhere in the Database or somewhere else? |
There are different methods to do that, and at different levels (postfix, amavis or on a per-user basis using sieve). What do you want to do exactly? |
i use in a company of a customer modoboa, and one User in the company, got mails/spams from a Domain which he dont want, for example spam@spam.com he want to block this mail/domain that he not received mails anymore from them. |
Ok, so the best way to do this is to tell this user to create a filter to reject message coming from this address and/or domain. |
Can i do this from the admin area? or from where? |
The user can create its filter alone, the top right menu contains a filters entry. |
New to Modoboa, but looking for these things myself. For completeness, I am using the method from my old setup with a helo access check against hash:/etc/postfix/helo-access In /etc/postfix/main.cf, add the following;
then create a file
and add your blacklist as follows;
If you are getting false-positives on badly configured servers, you can change REJECT to OK to allow it through before it is denied service from a misconfigured helo/hostname/DNS. Then finally
Update for 2020:It appears this is not working. The helo restrictions are not being enforced by postfix and all the spam mer friendly domains (e.g. *.in.net) are filling up user inboxes. Now... feature request... |
Hello, how can i add manual a Mailadress or Domain to Blacklist?
The mail is not in the Quarantine.
BR
The text was updated successfully, but these errors were encountered: