A bug report would seem like a reasonable thing to me.
Loren
----- Original Message -----
From: "Matthew Goodman" <[EMAIL PROTECTED]>
To: <users@spamassassin.apache.org>
Sent: Sunday, January 13, 2008 7:40 PM
Subject: RE: Problem with handle_user
Well that certainly does address the origin of the handle_user functions.
I
reviewed the link you sent regarding the previous bug but I have to be
honest when I say it doesn't shed any light on the situation whatsoever.
The last guy that had the problem on the mailing list stopped posting
after
you told him that the problem he was experiencing should have happened in
3.2.3 as well. I can attest that his situation and mine may be different,
but the result is the same. Most certainly without a doubt 3.2.3 = no
problem 3.2.4 = problem.
Now those bugfixes may have fixed something (and my configs merely are
working-around a broken codebase) but at the end of the day, per-user
configs are not working with my setup and 3.2.4
Wish I knew where to go from here, although I suppose a bug report could
be
filed. Especially given that there is more than one occurrence of this
problem, and that a downgrade completely fixes it.
-----Original Message-----
From: Matt Kettler [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 13, 2008 4:24 PM
To: Matthew Goodman
Cc: users@spamassassin.apache.org
Subject: Re: Problem with handle_user
Matthew Goodman wrote:
A downgrade to SpamAssassin 3.2.3 returns functionality with per-user
settings immediately. Any notes on what handle_user does and whether this
is
a new function of 3.2.4?
It's not new. In fact, it was introduced into spamd somewhere between SA
1.3 (October 2001) and SA 1.5 (December 2001) and has remained ever since.
handle_user is simply a function that handles setuid'ing the spamd
process to the specified userid.
Well, technically, there isn't a single "handle_user" anymore.. there's
many of them:
sub handle_user_setuid_basic {
sub handle_user_set_user_prefs {
sub handle_user_sql {
sub handle_user_ldap {
sub handle_user_setuid_with_sql {
sub handle_user_setuid_with_ldap {
The message you posted appears in 4 different spots in the spamd code.
handle_user_setuid_basic contains it twice and
handle_user_setuid_with_sql and handle_user_setuid_with_ldap each
contain it once.
There's been some change in this area of the code. Those changes appear
to have been made as a part of this bugfix:
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5611
Not sure if it's related, but seems likely.
I'd like to find out more about handle_user as it seems to be specific to
3.2.4
Thanks
