On 08 Dec 2020, at 08:36, Benoit Panizzon <benoit.paniz...@imp.ch> wrote:
> Adding the list back to CC as I believe this is an interesting topic
> many have pondered over.
Forgot to fix the reply to on this list for some reason. Fixed now.
> Yes, I see that is states 'per user' but I still don't see, how that
> 'bayes user' is being set on a per recipient base.
>
> On the email platform there is ONE config file for spamassassin. So if I
> set the user with:
>
> bayes_sql_override_username someusername
>
> That is the username under which the bayes data is being stored for all
> recipients (thousands of mailboxes on a big ISP mailserver)
It can be. It can also be, for example, %u (It may be more complicated than
that). Or perhaps sa_username_maps?
> How do I tell SpamAssassin to pass the recipient to the bayes
> filter while scanning an email?
Through the SQL query, IIRC.
--
Nothing like grilling a kosher dog over human hair to bring out the
subtle flavors.
