On Wednesday 22 April 2009 8:04:09 pm Doug Laidlaw wrote:
> On Wednesday 22 April 2009 7:42:18 pm Hugo Monteiro wrote:
> > Doug Laidlaw wrote:
> > > I am new to dspam. Mine is a simple workstation, not a server. I
> > > have tried white-listing, but find that it causes more problems than it
> > > solves. I have been running SpamAssassin, but it seems powerless to
> > > filter any of the current crop of porn/Viagra spam, although it does
> > > seem effective for the "I am So-and-So" kind from Nigeria.
> > >
> > > I am using the single user setup of dspam from
> > > http://splodge.fluff.org/docs/single-user-dspam, updated and running as
> > > a directory tree under $HOME. I use getmail to do the retrieving, then
> > > send it to dspam as an external filter. Individual filtering is
> > > abysmal, worse than SpamAssassin, but this may need training - a lot of
> > > it. Normal text emails, with nothing obvious about them, get a spam
> > > rating of 70% with SpamAssassin, and 100% from dspam.
> > >
> > > Why can I not tell dspam that a message is or is not spam BEFORE the
> > > run? SpamAssassin does. It has separate runs of identified spam and
> > > non-spam. With dspam, I have to let it make all the mistakes then fix
> > > them - a much bigger job. If I swapped the two databases, the result
> > > would be closer to the truth.
> > >
> > > But my main problem is getting the user to be passed by dspam. I have
> > > the following in my .getmailrc:
> > >
> > > [filter]
> > > type = Filter_external
> > > path = /home/doug/bin/dspam
> > > arguments = --user doug --deliver-spam
> > >
> > >
> > > The docs for getmail say that reinjection is unnecessary. Yet dspam
> > > consistently says that it doesn't know what user to run for.
> > >
> > > Any suggestions?
> >
> > Put
> >
> > Trust doug
> >
> > in your dspam.conf file.
> >
> > Regards,
> >
> > Hugo Monteiro.
>
> Sorry. I have already done that. At the moment, I am not using dspam,
> because the mails go nowhere, and disappear. I will do another test and
> post exact error messages.
>
> Doug.
I have just run another test. I had the wrong syntax for my .getmailrc, but
dspam still doesn't like it. dspam's debug and message logs weren't updated,
but I saw the following in a terminal:
msg 1/1 (2836 bytes), filter error (filter Filter_external dspam
(allow_root_commands="False", arguments="('--user doug', '--deliver-spam')",
command="dspam", exitcodes_drop="('99', '100')", exitcodes_keep="('0',)",
group="None", ignore_stderr="False", path="/home/doug/bin/dspam",
unixfrom="False", user="None") returned 1 (24482: [04/22/2009 21:48:52]
Unable to determine the destination user
24482: [04/22/2009 21:48:52] DSPAM agent misconfigured: aborting)
)
The first part of my dspam.conf follows:
## $Id: dspam.conf.in,v 1.82 2006/06/23 03:11:31 jonz Exp $
## dspam.conf -- DSPAM configuration file
##
#
# DSPAM Home: Specifies the base directory to be used for DSPAM storage
#
Home /home/doug/var/dspam
#
# StorageDriver: Specifies the storage driver backend (library) to use.
# You'll only need to set this if you are using dynamic storage driver plugins
# from a binary distribution. The default build statically links the storage
# driver (when only one is specified at configure time), overriding this
# setting, which only comes into play if multiple storage drivers are
specified
# at configure time. When using dynamic linking, be sure to include the path
# to the library if necessary, and some systems may use an extension other
# than .so (e.g. OSX uses .dylib).
#
# Options include:
#
# libmysql_drv.so libpgsql_drv.so libsqlite_drv.so
# libsqlite3_drv.so libhash_drv.so
#
# IMPORTANT: Switching storage drivers requires more than merely changing
# this option. If you do not wish to lose all of your data, you will need to
# migrate it to the new backend before making this change.
#
StorageDriver /home/doug/lib/libmysql_drv.so
#
# Trusted Delivery Agent: Specifies the local delivery agent DSPAM should call
# when delivering mail as a trusted user. Use %u to specify the user DSPAM is
# processing mail for. It is generally a good idea to allow the MTA to specify
# the pass-through arguments at run-time, but they may also be specified here.
#
# Most operating system defaults:
#TrustedDeliveryAgent "/usr/bin/procmail" # Linux
#TrustedDeliveryAgent "/usr/bin/mail" # Solaris
#TrustedDeliveryAgent "/usr/libexec/mail.local" # FreeBSD
#TrustedDeliveryAgent "/usr/bin/procmail" # Cygwin
#
# Other popular configurations:
#TrustedDeliveryAgent "/usr/cyrus/bin/deliver" # Cyrus
#TrustedDeliveryAgent "/bin/maildrop" # Maildrop
#TrustedDeliveryAgent "/usr/local/sbin/exim -oMr spam-scanned" # Exim
#
TrustedDeliveryAgent "/usr/bin/procmail"
#
# Untrusted Delivery Agent: Specifies the local delivery agent and arguments
# DSPAM should use when delivering mail and running in untrusted user mode.
# Because DSPAM will not allow pass-through arguments to be specified to
# untrusted users, all arguments should be specified here. Use %u to specify
# the user DSPAM is processing mail for. This configuration parameter is only
# necessary if you plan on allowing untrusted processing.
#
UntrustedDeliveryAgent "/usr/bin/procmail -d %u"
#
I have just noticed that it still refers to procmail, not getrmail. I
couldn't get it to work with procmail either, and the error message suggests
that the MDA isn't the issue - yet.
For "Trusted Users" I have:-
#
# Trusted Users: Only the users specified below will be allowed to perform
# administrative functions in DSPAM such as setting the active user and
# accessing tools. All other users attempting to run DSPAM will be restricted;
# their uids will be forced to match the active username and they will not be
# able to specify delivery agent privileges or use tools.
#
Trust root
Trust mail
Trust mailnull
Trust smmsp
Trust daemon
Trust doug
#Trust nobody
#Trust majordomo
Doug.
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user
