That sounds accurate, yes. Apache SpamAssassin is a program AND an
API. When it's used like an API, it's very flexible.
On 9/9/2018 1:08 PM, thatvolvonut wrote:
> OK, I think I get it now. If I wanted to use spamassassin natively, I'd need
> to ditch spamass-milter (a standalone application sep
OK, I think I get it now. If I wanted to use spamassassin natively, I'd need to
ditch spamass-milter (a standalone application separate from spamassassin) and
find another solution, like a true spamd/spamc setup that postfix would pass
messages to after they're received. As-is, with spamass-milt
On 9/9/2018 11:51 AM, thatvolvonut wrote:
> Good catch - I guess I didn't look over that file close enough. I removed the
> flag and ran a `systemctl restart spamass-milter` and my subjects are getting
> tagged now! However, SpamAssassin is still failing to add the custom 'Score'
> header I've
Good catch - I guess I didn't look over that file close enough. I removed the
flag and ran a `systemctl restart spamass-milter` and my subjects are getting
tagged now! However, SpamAssassin is still failing to add the custom 'Score'
header I've specified in my config.
If I'm understanding it co
I'm not a spamass-milter but google helps
you are using -m switch with spamass-milter which as per docs: "Disables
modification of the 'Subject:' and 'Content-Type:' headers and message
body."
more details from spamass-milter man page
On 09/09/2018 03:34 PM, thatvolvonut wrote:
Boiler
Boilerplate Info:
Platform: Ubuntu 16.04.5 LTS
SpamAssassin Version: 3.4.1
Invocation: spamd (`systemctl enable spamassassin`) (see below for details)
Hi all -
I'm having an issue where SpamAssassin appears not to be tagging emails it
identifies as spam. It has no problem recognizing and setting
