Oooh, Intriguing. Keep me in the loop!
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Mon, Mar 15, 2021 at 1:37 AM Dan Mahoney wrote:
>
>
> On Mar 14, 2021, at 9:45 PM, Kevin A. McGrail
> On Mar 14, 2021, at 9:45 PM, Kevin A. McGrail wrote:
>
> Well, SpamAssMilter *must* be capturing the data from spamc and creating that
> header. If you look at the cpp, it's building it. You could change the
> Milter to create a header called X-ImaMilter and use any data you want.
No
Well, SpamAssMilter *must* be capturing the data from spamc and creating
that header. If you look at the cpp, it's building it. You could change
the Milter to create a header called X-ImaMilter and use any data you want.
But it looks like signal_user_changed sets self->{username} in spamd so if
> On Mar 13, 2021, at 7:51 PM, Kevin A. McGrail wrote:
>
> 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
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
