R: R: R: R: R: Question about SQL-based AWL
> -----Messaggio originale-----[color=blue]
> Da: Luca Bertoncello [mailto:firstname.lastname@example.org]
> "Giampaolo Tomassoni" <email@example.com> schrieb:
> > Luca, I'm meaning this behavior should be enforced only by turning[/color]
> > user_awl_sql_override_username switch on, and then the SQL 'username'[/color]
> > would be filled with the username to be used to connect to the sql[/color]
> db, as[color=green]
> > opposed to the current SA user.
> > Actually, when user_awl_sql_override_username is off, you should get[/color]
> > per-user AWL in which the sql 'username' column is filled with the[/color]
> > SA user. Unfortunately, PersistentAddrList caches the SA username at
> > startup, which is when the SA username is the one of the user[/color]
> starting SA[color=green]
> > (nobody in your case). It seems to me that this caching defeats any[/color]
> > to change the AWL username later.
> > You can't obtain a per-user AWL by tweaking[/color]
> > then...[/color]
> Does it mean, that it is not possible to have a per-user-AWL if I use
> the SpamAssassin-Daemon?[/color]
Right, that's what I meant.
FWIK, every and each SA-powered daemon do create a fresh SA instance at
startup, then use it to inspect mail directed to different users by first
"tweaking" the current user in SA. Since PersistentAddrList caches the user
at startup, this tweaking can't work to AWL...
> Luca Bertoncello