spamassassin not lethal anymore

[Kurt Buff]

On Thu, Jan 12, 2017 at 1:58 PM, Russell L. Carter <rcarter at pinyon.org> wrote:
<snip>
> I had hoped I wouldn't need to do a deep dive on state-of-the-art
> spam killing, but it's 2017 and the game has gotten tougher.
>
> Thanks for these suggestions.  I'm implementing greylisting, pyzor,
> razor, and the above client_recipient_restrictions.  dcc I don't
> quite understand yet.
>
> I think I'll phase this stuff in, with greylisting first, and see
> what happens to the spam flow for each step.  I am a little wary
> of putting even more chunks of perl and python into the critical
> path.
>
> Thanks a lot for the help, everyone.
>
> Russell
> (I just had a sad laugh recalling that I used to set up a mail server
>  in 1995 using sendmail... and nothing else but exmh as the client)

One other suggestion - I set this up years ago, but was forced to
retire it in favor of a Barracuda appliance, which does basically the
same thing - security/maia. It worked very well for our 250 users, and
was pretty easy to administer.

It might be overkill for your situation - it's meant as a spam filter
for an organization, but the pkg-descr is below

     Maia Mailguard is a web-based interface and management system based on the
     popular amavisd-new e-mail scanner and SpamAssassin. Written in
Perl and PHP,
     Maia Mailguard gives end-users control over how their mail is processed by
     virus scanners and spam filters, while giving mail administrators the power
     to configure site-wide defaults and limits.

     WWW: http://www.maiamailguard.com/


Kurt