Hi Dan,

Milters are the glue that change the email.  SpamAssassin is just giving
data back to the milter.

I believe you will find that X-Spam-Status header is being built by
spamass-milter not by spamassasin.  You need to change the milter code to
keep track of the user and add it to the X-Spam-Status line in the
spamass-milter.cpp

Regards,
KAM
--.
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Fri, Jan 15, 2021 at 5:31 PM Dan Mahoney (Gushi) <d...@prime.gushi.org>
wrote:

> All,
>
> For dumb reasons, we at the day job are using spamass-milter, which
> doesn't seem to let SpamAssassin add any extra X-Spam-Foo:  message tags
> beyond stock (I have a github issue open on this, which seems to be
> where a fork is being maintained).
>
> However, in order to work around this, I've added more tags to the
> X-Spam-Status tag locally.  Which is useful because it also lets me grep
> my maillogs for those things.
>
> What I can't find, and it feels like it should be a thing, is the
> *username* for the tag.  That is to say, the username that's being used to
> find the user-prefs (in our case, with spamd, it's just %u, we don't have
> the user/domain stuff set up).
>
> This *feels* like something a quick .pm file should be able to add rather
> than having to modify spamassassin core (and in fact, the tokens for
> username, mailbox and domain *are* available for the bayes_sql_query, but
> for some reason aren't exposed as tags that can be used in the report
> header.  Which feels somehow deliberate.)
>
> Would this be easy to do?
>
> It would also mean I could easily glean per-user/per-rule-hit reporting
> from my maillogs with a simple grep, rather than having to cross-correlate
> the mta logs from the spamd ones.  This feels like a win.
>
> -Dan
>
> --
>
>
> --------Dan Mahoney--------
> Techie,  Sysadmin,  WebGeek
> Gushi on efnet/undernet IRC
> FB:  fb.com/DanielMahoneyIV
> LI:   linkedin.com/in/gushi
> Site:  http://www.gushi.org
> ---------------------------
>
>

Reply via email to