Hi!

I'm a spamprobe user that is in a new environment -- I'm actually
entirely happy with spamprobe, but I'm super interested in some of the
shared classification grouping abilities in dspam.

This probably isn't needed, but I want to explain my setup here to
justify what I'm trying to make dspam do.  :)

I'm using FreeBSD and jails, with a postgres dspam backend.  The host
runs the dspam daemon, postgres, and clamav.  I'm trying to keep all the
'server' stuff on the host, then run dspamc in filter mode (--stdout)
from all the jailed machines.  (Qmail default delivery to procmail.)

So far, so good.  All of this setup works like magic - no wasted
resources, as all the client jails use the same host daemons, and the
dspamc instances are all sharing the same dspam 'server'.

I trained from my spamprobe corpus, and am already getting a great
success rate on filtering, so I'm not really concerned with dspam
"vs" spamprobe - it seems like dspam will work out great.


Okay, now to my problem.  Namespacing!  As it sits right now, virt
users are auto created on the first message tokenization.  They are
created simply with their username - not [EMAIL PROTECTED]  This could
potentially cause collisions between users on different jails.  As
example, '[EMAIL PROTECTED]' is a different person than '[EMAIL PROTECTED]',
but both still want to use the virt user 'mike'.

So - I'd like to have the default procmail delivery use the --user flag,
and set it to [EMAIL PROTECTED]  Of course, I can't do that without
adding all of the potential users to the Trust list, which seems like a
bad idea.  So they get added with the plain jame username anyway.

Is there a way to say:  "Everything coming in from this particular
dspamc has a jail1.com namespace?" -- either via a --user flag somewhere
(remember, qmail has already switched to the user's uid at this point)
or via a dspam.conf client setting?

Hints/tips/ideas/rtfms all happily accepted - thanks all.

-Mahlon

--
Mahlon E. Smith  
[EMAIL PROTECTED] | http://www.martini.nu/

Attachment: pgpweFxJ0onNv.pgp
Description: PGP signature

Reply via email to