On 8/15/2013 9:38 AM, Matus UHLAR - fantomas wrote:
On 14.08.13 15:20, Ted Mittelstaedt wrote:
I am using spamass-milter to process received mail.
do you use "-u user" option? spamas-milter uses that user's config when the
mail goes to multiple recipients. Isn't that user by any chance the one in
all_spam_to list?
None of the users have individual configs, this is a mailserver
that does not store configuration data on a per-user basis, thus that
option does not apply.
I guess if you don't specify the -u option, user "nobody" is used.
actually it's user root. It's a potato/potahto argument as to whether
to modify local.cf or a config in the root user, the end result is a
single global config.
If the option was supposed to process BCC also why wasn't it called
all_spam_to_both_to_and_bcc?
I strongly doubt that any spam software does use Bcc:
Bcc: is for MTAs that need to specify envelope users that do not go to the
headers.
spamass-milter isn't a spam software it is a milter that calls spam
software. As David and John already discussed the way this appears to
be happening is that spamass-milter is parsing the users in the BCC:
header (which as you stated, shouldn't exist in an incoming email - but
it does - since that email is a piece of spam generated by some spammers
program) and passing those to spamassassin, which is seeing that one of
those users is listed in the all_spam_to configuration, and assigning
a -100 score, which is then essentially invalidating spamassassin's scoring.
Or, something like that - if I'm understanding the discussion properly.
Ted
