Mailing List Archive

[Bug 7819] bayes is using usernames case-sensitive
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7819

--- Comment #3 from Benny Pedersen <me@junc.eu> ---
could this gets highter priortet ?

while its fixed in fuglu, its not yet in spamd/spamc

--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7819] bayes is using usernames case-sensitive [ In reply to ]
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7819

Benny Pedersen <me@junc.eu> changed:

What |Removed |Added
----------------------------------------------------------------------------
Component|Plugins |spamc/spamd

--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7819] bayes is using usernames case-sensitive [ In reply to ]
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7819

Bill Cole <billcole@apache.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |billcole@apache.org
Severity|normal |enhancement
Priority|P2 |P4

--- Comment #4 from Bill Cole <billcole@apache.org> ---
I'm a bit confused by the "Component" change. If this is a Bayes issue as
stated in the bug title, the "Component" should stay "Plugins" because that is
how Bayes is implemented. The only way I can see that "spamc/spamd" would be
correct is if you're not referring to Bayes at all, but to the per-user
configuration (including Bayes DB) support in spamc/spamd. In either case, this
is NOT A BUG but rather an enhancement request and I think it should be
optional and non-default, because usernames (and virtual usernames) can be
case-sensitive.

(In reply to Benny Pedersen from comment #2)
>is the problem only postgresql then ?
I would think that if you are using a RDBMS you could fix this on the DB side
by making the relevant field case-insensitive. In MySQL that's the default, in
PostgreSQL it requires that the column type be CITEXT rather than TEXT. See
https://www.postgresql.org/docs/current/citext.html for details.


(In reply to Benny Pedersen from comment #3)
> could this gets highter priortet ?
I do not expect so. It would require substantial effort to "fix" and the
behavior is a non-bug.

As RW says, local parts can be case-sensitive (with the exception of
"postmaster") so it isn't formally wrong to treat 'fOo' and 'Foo' as different
tokens. In fact it would be formally *wrong* to arbitrarily case-squash tokens
just because they happen to be usernames. Not having examined the code for
Bayes tokenization I cannot be certain, but I would expect that detection of
usernames per se is not done. It would break an assumption of the "Naive Bayes"
model of using simple classifiers that are stripped of context.

Patches welcome, of course. In my opinion, adding the behavior change for Bayes
local-part tokens or per-user config usernames should be optional and
non-default.

--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7819] bayes is using usernames case-sensitive [ In reply to ]
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7819

Giovanni Bechis <giovanni@paclan.it> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |giovanni@paclan.it

--- Comment #5 from Giovanni Bechis <giovanni@paclan.it> ---
Created attachment 5711
--> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5711&action=edit
Untested patch to have case insensitive usernames

Untested patch to have case insensitive usernames on Postgresql as well.

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