Is it possible to install Bitdefender on top of Spamassassin in IPSC3? I used the Perfect Debian 8 tutorial (https://www.howtoforge.com/tutorial/perfect-server-debian-8-jessie-apache-bind-dovecot-ispconfig-3/) I'm still getting a lot of spam on a server that's been running for almost a year. Thanks!
You should ask the Bitdefender support on how to integrate their software into amavisd. Which spam tag 2 level do you use in the policy and which spam kill level? Which dns blacklists did you add?
Till, thanks for the quick reply! Here are the tag levels from the headers: X-Virus-Scanned: Debian amavisd-new at mail.domain.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=3.2 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, NO_RELAYS=-0.001] autolearn=no autolearn_force=no Here are the DNS blacklists from the Postfix config (main.cf): smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, reject_rbl_client sbl.spamhaus.org, reject_rbl_client cbl.abuseat.org, reject_rbl_client dul.dnsbl.sorbs.net, permit smtpd_error_sleep_time = 1s smtpd_soft_error_limit = 10 smtpd_hard_error_limit = 20
Which headers do you use in the policy? The headers from the mail shows that your bayes database (the self-learning filter) has learnt something wrong, you might have to reset it. Currently it does the opposite of spam filtering, it whitelists spam by assigning a negative score.
I use the NORMAL policy...and only altered the tag levels to start tagging at -999 and Spamtag2level is changed to 3.2. Nothing else was changed. To clear the filter, I just run ...right?
