Matt Decker wrote:
I'm migrating my qmail toaster from a site wide spamassassin setup to
a per user (MySQL based) setup. The problem I had with this was that
simscan doesn't know the final main account delivery email address for
forwards and domain aliases. This is also a problem when email has
multiple recipients because it doesn't know which address to use when
calling for the userprefs AND bayes in MySQL. The end result is that
if you use bayes in this setup and someone has several alias accounts,
those alias accounts will end up in bayes as well instead of
everything just going into one main email address/account. Also
whitelisting via userprefs will only work when mail is sent to the
main email address and not aliases.
This makes bayes and userprefs in a per user MySQL environment
unusable with simscan.
So I found a solution that works. But I'm not sure if there are
negative implications in doing this (i.e. Performance issues, dropped
emails, etc).
I changed the following to get a per user MySQL Spamassassin setup
working correctly:
1. I disabled spam scanning via simcontrol file
(/var/qmail/control/simcontrol - spam=no)
2. Created a .qmail file in my account folder
(/home/vpopmail/domains/somedomain.com/someuser/) that contains the
following:
|/usr/bin/spamc -u [EMAIL PROTECTED] | /var/qmail/bin/preline
/usr/bin/maildrop -A 'Content-Filter: maildrop-toaster'
/etc/mail/mailfilter
So it feeds the message through the spamc client and then into the
mailfilter script which puts my spam in my spam folder.
It seems to work great. I just wonder once I put it into production
with over 100 domains how well it will work. I know I'll have to
write some scripts to update everyone's .qmail file, but that is fine
as long as I know it will work under a load.
Any thoughts or advice?
The mailfilter script is now back into the main distribution. You just
have to turn it on by compiling maildrop-toaster and qmailadmin-toaster
(it will give each user the "Spam detection" check box in QMail-Admin
they can turn on/off":
rpmbuild --rebuild --with cnt40 --define 'spambox 1'
qmailadmin-toaster-*.src.rpm
Might make things a little easier for you, since the user can select the
check box which will in turn edit the .qmail file file and create a box
called "Spam".
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
