[Bug 8396] unable to manage global WL / BL

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=3D8396

--- Comment #1 from Bill Cole <[email protected]> ---
(In reply to Sohail from comment #0)
> +++ This bug was initially created as a clone of Bug #8126 +++
>=20
> We have txrep and user preferences in a database.
> In local.cf, I set user_awl_sql_override_username to 0 (we use user's ids=
 in
> the database)

user_awl_sql_override_username is supposed to be a username, not a number.=
=20

> txrep_user2global_ratio is set to 5.
>=20
> Now, txrep itself is working and adds rows to the table both with the
> specific user's id and 0 as the "global" id.
>=20
> However, if - as root - I run this:
>=20
> spamassassin --add-addr-to-welcomelist=3Dsomedomain.tld,spf
>=20
> the username being used for the purpose of txrep is not '0'.

'0' is not a valid username

> Also, no entries whatsoever are being added to (or modified) in the txrep
> table using this command.

Try the -u option, as documented in the spamassassin-run man page.=20

> To make matters worse:
> The spamassassin command does not (like sa-learn or spamc) allow overridi=
ng
> the username.

Try the -u option, as documented in the spamassassin-run man page.=20

> spamc on the other hand cannot be used to issue for the
> --add-addr-to-welcomelist functionality.
>=20
> At the moment, this seems to me to prevent me from managing the global WL=
 or
> BL.
>=20
> I guess I must be missing something? Does all this work as intended?

I am not sure whether you missed it or thought it was inapplicable, but the=
 bug
you cloned this one from includes the mention of user_awl_sql_override_user=
name
not being a number and the addition of the -u option to the spamassassin
script.=20

As far as I can tell, this is a duplicate of bug #8126, but perhaps I'm mis=
sing
something in your description which actually differentiates it. I'm not clo=
sing
this as a duplicate because presumably you saw some distinction that escapes
me.

--=20
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.=