spamassassin has a huge set of configuration files, on my system it
looks in these three places, plus at a user config file:
/usr/share/spamassassin/
/var/lib/spamassassin/3.002005/updates_spamassassin_org/
/etc/mail/spamassassin
Nevertheless, none of the headers defined by add_header in any of
On 2011-07-13 at 10:14 -0700, David Mathog wrote:
Nevertheless, none of the headers defined by add_header in any of
those many configuration files actually show up in the messages.
Instead the only headers created are those defined in exim.conf in this
section:
SpamAssassin's added headers
On Wed, Jul 13, 2011 at 10:14 AM, David Mathog mat...@caltech.edu wrote:
Nevertheless, none of the headers defined by add_header in any of
those many configuration files actually show up in the messages.
Exim parses the response and stuffs the values into variables. It's
up to you to decide
Phil Pennock wrote:
SpamAssassin's added headers rely upon the message itself being
transported through SA, modified by it, before delivery.
By contrast, Exim is asking spamd to take a look at the message and
report back on it; spamd doesn't get to modify the message at all.
OK. Based
On 2011-07-14 at 08:54 -0700, David Mathog wrote:
I don't have a grasp on the relative benefits of doing the spam checking
in these two different ways, beyond the observation that the sa-exim one
ends up with the headers spamassassin is configured to add. Since there
is usually no free lunch,
