On Thu, Oct 15, 2020 at 12:44 PM PGNet Dev <pgnet....@gmail.com> wrote:
> On 10/15/20 8:19 AM, Ian Evans wrote: > > > Is there a more efficient, memory stingy, faster milter way to run > spamassassin, clamav, etc, or would you recommend sticking with amavis? > > > > very much personal choice. each comes with it's challenges. > for any set of choices, you'll get the usual assortment of pundits > telling you why it's Bad(tm). > > > i'm not a fan of 'swiss army knife' apps that try to be all things to all > people; i prefer the option to rip out & swap individual pieces if/as > needed. > > having _had_ that^ same stack, i first rm'd amavis > . > > > now, i've got: > > inbound: > > postscreen > > spf-engine (policy service) > > pre-q milters: > > opendkim > opendmarc > milter-regex > clamav-milter > spamassassin-milter (https://lib.rs/crates/spamassassin-milter) > > outbound: > > opendkim > > > for inbound, i'd like to replace opendkim/opendmarc with > fastmail/authentication_milter -- > -- but the project devs aren't terribly responsive. not clear yet whether > it's as bad as 'Trusted Domain Project' opendkim/opendmarc ... > > for outbound, i'd again like to get rid of opendkim. but, so far, i've > found no good packaged options that fit my needs. > > DIY with Mail::DKIM is a pain, but doable, and on my "I'll get around to > it eventually" list. > > atm -- although it all still _feels_ a bit fragile -- this current setup > is working well enough. > > certainly lighter-weight than b4, and for me simpler to configure/manage. > > my $0.02. > thanks to everyone for the suggestions. some food for thought. have a great weekend,
