I've got a mostly working system w/ squirrelmail + spamassassin and users
being able to modify settings in spamassassin through squirrelmail
(spamassassin grabs it's configuration data from spamassassin).
I have vpopmail set with spamhandling controlled through
/var/lib/vpopmail/etc/mailfilter
Myron Davis [EMAIL PROTECTED] wrote:
The above script grabs all custom filter settings dropped by
spamassassin and works fine, EXCEPT in the following circumstances:
you have a catchall and you send a message to the catchall, then it
executes the script except $EXT (and also possibly $HOST is
I currently have spamassassin set up to grab all users info from sql, and
I have not had any problems with spamassassin and user preference files,
except I did have the problem with vpopmail earlier for non-existent
users.
As you can see in my mailfilter script that I step right past that problem
Myron Davis [EMAIL PROTECTED] wrote:
VHOME=`/var/lib/vpopmail/bin/vuserinfo -d [EMAIL PROTECTED]
VPOP=$VHOME/Maildir/
if ( no such user =~ /$VHOME/:d )
{
VDOMHOME=`/var/lib/vpopmail/bin/vdominfo -d $HOST`
VPOP3=`cat $VDOMHOME/.qmail-default | cut -f4 -d' '`
VPOP=$VPOP3/Maildir/
EXT=`echo
I have solved my own problem, the following script enables maildrop and
vpopmail to properly process catchall accounts.
It was really simple actually all I needed to do was generate a brand new
$VHOME (and $EXT and $HOST) based on the scripts sleuthing so maildrop
could read it properly from