BitDefender with ISPConfig3

Discussion in 'HOWTO-Related Questions' started by bschultz, Aug 17, 2016.

  1. bschultz

    bschultz Member

  2. till

    till Super Moderator Staff Member ISPConfig Developer

    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?
  3. bschultz

    bschultz Member

    Till, thanks for the quick reply!

    Here are the tag levels from the headers:

    X-Virus-Scanned: Debian amavisd-new at
    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 (

    smtpd_recipient_restrictions =
    check_recipient_access mysql:/etc/postfix/,
    smtpd_error_sleep_time = 1s
    smtpd_soft_error_limit = 10
    smtpd_hard_error_limit = 20
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    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.
  5. bschultz

    bschultz Member

    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
  6. bschultz

    bschultz Member

    One more is it whitelisting when I have autolearn forced to no?


Share This Page