On 6/9/20 5:40 AM, Marvin Renich wrote: >> https://savannah.nongnu.org/projects/spamass-milt/ >> https://github.com/mpaperno/spampd >> https://gitlab.com/glts/spamassassin-milter >> >> anyone have any current experience with any of these? > > I also use the first one (Debian package spamass-milter) along with > milter-greylist (only greylisting messages with a spam score in the > lower end of the "positive" range to avoid rejecting false > positives from spamassassin while not greylisting clearly legitimate > email).
in some testing, i found the idea of a 'modern' rust implementation in spamassassin-milter initially appealing. simply could not manage to get it talking to a spamd backend. spampd worked well enough, when listening on tcp host:port. listening on socket, i couldn't get past postfix permissions issues, despite similar setup to other policy daemons in use. that makes me a bit antsy. as does not using 'native', up-to-date spamd. spamass-milter, despite being the 'dustiest' of the bunch, works without issue. set up like other milters, it's a simple drop-in to postfix config. uses native spamc+spamd, and my local configs as intended. as it seems widely in-use, and appears to work well enough i'll take the 'risk' with, now, a working postfix setup that includes clamav-milter + clamd spamass-milter + spamd and all traces of amavisd removed, mail's flowing smoothly. and, noticeably faster, with less resource use. now, to get learning, headers, etc cleaned up the way i like them ... thx 4 the input!
