You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@spamassassin.apache.org on 2023/05/08 07:53:01 UTC

[Bug 8126] New: unable to manage global WL / BL

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

            Bug ID: 8126
           Summary: unable to manage global WL / BL
           Product: Spamassassin
           Version: 4.0.0
          Hardware: PC
                OS: FreeBSD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: spamassassin
          Assignee: dev@spamassassin.apache.org
          Reporter: martin@waschbuesch.de
  Target Milestone: Undefined

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)
txrep_user2global_ratio is set to 5.

Now, txrep itself is working and adds rows to the table both with the specific
user's id and 0 as the "global" id.

However, if - as root - I run this:

spamassassin --add-addr-to-welcomelist=somedomain.tld,spf

the username being used for the purpose of txrep is not '0'.
Also, no entries whatsoever are being added to (or modified) in the txrep table
using this command.

To make matters worse:
The spamassassin command does not (like sa-learn or spamc) allow overriding the
username.
spamc on the other hand cannot be used to issue for the
--add-addr-to-welcomelist functionality.

At the moment, this seems to me to prevent me from managing the global WL or
BL.

I guess I must be missing something? Does all this work as intended?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: [Bug 8126] New: unable to manage global WL / BL

Posted by Benny Pedersen <me...@junc.eu>.
bugzilla-daemon@spamassassin.apache.org skrev den 2023-05-08 09:53:

> 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)

this field is not bool :)

but users real email@example.com

when its set to @GLOBAL its global users settings for this in sql

back to the problem is spamassassin dont know virtual alias in postfix, 
so only virtual mailbox addresses works with sql user prefs

roundcube have partly solved it to be possible to just set user indent 
to the alias, and then use saprefs in roundcube to whitelist/blacklist, 
this works for me :)

i just hope developpers would add the virtual alias to virtual mailbox 
maps direct without need to use special indent as a workaround in 
roundcube

hope its the same problem you have ?

[Bug 8126] unable to manage global WL / BL

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8126

martin@waschbuesch.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin@waschbuesch.de

--- Comment #2 from martin@waschbuesch.de ---
(In reply to Bill Cole from comment #1)
> Also note: SpamAssassin refuses to run as 'root' in some circumstances. If
> your users do not have unique UIDs, you should use an unprivileged account
> for managing per-user databases.

I am not sure I managed to convey what the problem is, so let me rephrase:

Ignore what I said about numbers. It does not matter anyway as tried with uuids
and it does not change a thing.

txrep itself works. Per user-stuff works.
Entries are added in the database for individual users and for the 'global'
reputation. It is all virtual users anyway, there are no system users involved
anywhere.

The txrep table is filled exactly how I would expect and it matches the
documentation just fine.

As soon as I want to manage either individual or global blocklists or
welcomelists, though, none of this works.

I am unable to modify global welcomelists / blocklists using
spamassassin --add-addr-to-welcomelist=somedomain.tld,spf

Running that command will NEITHER produce error / warning output NOR modify the
txrep database table in any way.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 8126] unable to manage global WL / BL

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8126

Bill Cole <bi...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |billcole@apache.org
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Bill Cole <bi...@apache.org> ---
user_awl_sql_override_username is a username. It is NOT a number, unless you
have users who have numbers as their usernames…  Please review the
documentation for its possible values and usage. 

Also note: SpamAssassin refuses to run as 'root' in some circumstances. If your
users do not have unique UIDs, you should use an unprivileged account for
managing per-user databases.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 8126] unable to manage global WL / BL

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8126

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |apache@hege.li
         Resolution|INVALID                     |---

--- Comment #3 from Henrik Krohns <ap...@hege.li> ---
(In reply to martin from comment #0)
>
> To make matters worse:
> The spamassassin command does not (like sa-learn or spamc) allow overriding
> the username.
> spamc on the other hand cannot be used to issue for the
> --add-addr-to-welcomelist functionality.

Looks enough reason alone to keep this bug open.

I just copy pasted the -u option from sa-learn to spamassassin:

Sending        trunk/lib/spamassassin-run.pod
Sending        trunk/spamassassin.raw
Transmitting file data ..done
Committing transaction...
Committed revision 1909738.

-- 
You are receiving this mail because:
You are the assignee for the bug.