[sam] Re: [cvs] commit: sam whitelist.php sam/docs CHANGES sam/lib SAM.php sam/lib/Driver sql.php sam/templates/menu menu.inc sam/templates/whitelist body.inc

[Marc G. Fournier]

On Tue, 18 Jun 2002, Chuck Hagenbuch wrote:

> Quoting Chris Bowlby <excalibur@hub.org>:
>
> >   Also re-fixed and issue with SAM where the username was being set to t
> >   he full email address, this prevented Spam Assassin from seeing anything
> >   that was configured for a particular user. For the moment, I am
> >   stripping out the '@domain_name.com' portion and using the resulting
> >   username for username setting. This enabled Spam Assassin to once again
> >   see the preference.
>
> You need to stop assuming this at the driver level, and define a hook
> function so that people have a user-defined function to get the
> SpamAssassin (it's one word, not two, btw) username. It's not necessarily
> created by stripping @domain.com, and a lot of Horde setups won't _have_
> @domain.com on the username.

'K, you'll have to enlight me on this one ... what do you mean by the
SpamAssassin username is not necessarily created by stripping @domain.com?
I thought it was always *just* the username component, and it ignored the
domain ... or am I mis-understanding what you are saying here?

As for 'alot of horde setups' ... my guess is that chris is doing a split
based on @, with the user component being on the left, domain on the right
... so if there is no @, then it won't make a difference ...

but, again, I'm first to admit I may/am porbably misunderstanding what you
are saying here :9