Tag Info

New answers tagged

0

I had a similar issue with response time, until I found out that the SpamAssassin database requires some minimal ongoing maintenance. Are you issuing sa-learn --force-expire on a daily basis? It could be that a lack of maintenance has made the database unweildy and it needs to be "trimmed up a bit". Try placing it in a daily cron job and see if the ...


2

SpamAssassin comes with sa-learn out of the box (not to be confused with the sa-learn-cyrus you mentioned). It comes with two learning modes, ham and spam. It would take a very, very simple script to walk through each user's mailbox, doing a "ham" pass at first, and a second walk-through for "spam". Something (roughly) like: #!/bin/bash # change these ...


1

I wrote my own script using doveadm search to read training mails from certain IMAP folders in my own account. The usual disclaimers apply, it is not pretty but works for me. You will also have to remove the crm114 mailtrainer.crm call at the end. Edit: I realized my script also uses crm114 feature (a cache dir of all processed messages in ...


6

We mitigated the same issue by using an outside vendor as our e-mail gateway (in our case, Exchange Online Protection but there's many other comparable services). We then configured all our e-mail sending services to use that as the smarthost. Now, all our outgoing messages are associated with the reputation of the external e-mail gateway. Because of that, ...


1

Spamassasin primary purpose is classifying email (spam or not). To handle quarantine vault, you can use additional package such as amavis, maia or SAQ. For more info, please check official documentation


15

I'm looking forward to seeing other answers to this question, but my feeling is that if you're catching compromised mail accounts after only 40 spams have got through, you're doing really well. I'm not sure I could detect similar abuse so quickly, and the prospect worries me. But I'm appalled that seven sets of credentials were stolen in the past week ...


2

As root, execute the cpanel script that will identify the spamassassin path for you. /usr/local/cpanel/bin/get_spamassassin_bin_location Running CentOS 6.5 my executable is located here: /usr/local/cpanel/3rdparty/perl/514/bin/spamassassin You can also get a lot of good information about where spamassassin "stuff" lives by running locate ...


0

Using perltidy on files w/ invalid syntax may yield even more broken output files. Also perltidy doesn't overwrite the source file unless told to. Did you try to do an perl -c /etc/amavisd.conf ? If this also yields this error you'll have to double check to config file syntax and get somebody to double check it for you. If this file is fine, then there ...


1

This question is quite old. But for people like myself who stumble across it. Amavisd-New has this option: $final_spam_destiny = D_DISCARD; So just change the above default to: $final_spam_destiny = D_BOUNCE; And all email which is considered fail spam will bounce instead of being discarded. However keep in mind if it fails hard it's more ...



Top 50 recent answers are included