DSPAM has built- in support for Clam. AV. But proper usage of built- in postfix restrictions are really the best first- line defense. I decided to skip greylisting (used postgrey in the past) because it requires you to keep a whitelist of misbehaving servers (or trust its database). For that reason I also decided against reject. The downside is that you need to pay attention to your logs and whitelist misbehaving (but legit) servers as soon as you notice them, or your users will probably complain. Implementing SMTP AUTH (in my opinion most easily by using the dovecot auth provider) helps to make sure that submission is handled properly (together with a strict smarthost (mynetworks) list/policy). My suggestion when setting up postfix is to have a clear plan of what you want to achieve (figure out if you want local or virtual delivery, what type of antivirus/spam system and how to do delivery+filtering). Start with an empty main. The distribution very often come with defaults that capture the distributors idea of a mail system, and it doesn't always reflect your views, opinions and policies (they might differ). Remember to do all of this on a system without users so that you can experiment in peace. I was able to implement all of this with precompiled packages on Ubuntu 9. FAQ CloudServer AnleitungenSpam- und Virenschutz mit Postfix (Debian). ANTI-SPAM-SA code loaded.How to Add Antivirus and Spam Protection to Postfix Mail Server with ClamAV and SpamAssassin – Part 3. Experts Exchange > Questions > Best settings for antispam / Postfix Want to. I use postfix 1.1.11 on a debian server. Installing and Configuring Postfix on Debian. Install postfix (this will remove exim since there can't be two mail systems). Postfix + SpamAssassin + ClamAV + Procmail on Debian. SpamAssassin on Debian and Ubuntu runs as root which is NOT a good. Postfix spam protection with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |