On Friday 17 Feb 2006 19:41, Noel Sanchez wrote:
> Thanks for the advice Bob. I've spent more time reading the docs like I
> should've to begin with. From what I've read, if I let my users know to
> forward all spam they receive into their email to an email that I
> created, say [EMAIL PROTECTED], I can use "sa-learn --spam
> /home/vpopmail/domains/furniture-homegallery.com/3/spam/Maildir/cur so
> that it "learns" what spam is. Question, won't it think that the spam is
> actually my users forwarding the spam instead of the actual spam being
> forwarded to it? If they forward the email to [EMAIL PROTECTED], I think
> it'll learn to ban my users at my domain instead. Am I doing this wrong?

Not sure, I'm using one Spamassassin 'learn' facility for everyone, not one 
per domain or one per email account. I don't think sa cares about the 
recipient, can't imagine why it would. AFAICT sa does not scale down very 
well, works better on large throughput setups.

Squirrelmail has a spam-button plugin which I configured to send (bounce) the 
selected mail to a dedicated account which is scanned at regular intervals 
with a cron job (similar to Dennis Erickson's post here)

Apparently forwarding mail mangles the headers (from an sa-learn analysis 
point of view). I've had a similar problem when customers have forwarded 
problem mail to me, I can't see what happened, the original headers are lost.

I could not get the plugin to run sa-learn directly, probably a permissions 
problem but I have not persued it as doing them in bulk is a lot less CPU 
intensive than running sa-learn once for each mail.

This combined with a .SPAM folder to reroute those already identified by 
simscan via a maildrop filter seems to be doing the trick.

What I haven't figured out is how to use a maildrop filter *and* TMDA ;-)


>
> Thanks
>
>
>
> -----Original Message-----
> From: Bob Hutchinson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 16, 2006 2:04 PM
> To: toaster@shupp.org
> Subject: Re: [toaster] spamassassin
>
> On Thursday 16 Feb 2006 19:52, Noel Sanchez wrote:
> > Hello All. I have used the toaster without the "options" installed for
> > quite some time, very happy with it. Now, my users have been getting
> > many spam emails. So, I installed ALL "options" per the toaster. Very
> > easy to do, thanks to Bill. Question, now that I have installed it,
>
> what
>
> > now? I sent a spam email from outside into my mail server.
>
> Spamassassin
>
> > recognizes it and puts it on my squirrelmails inbox and marks it as
> > spam. That's great, but I isn't the point of simscan is to drop it
> > automatically? I'd like to NOT receive ANY spam in my inbox. Maybe
>
> sent
>
> > to a spam folder or drop it altogether. And if it doesn't put it in my
> > inbox, where will it go? What if it marks an important email as spam
> > when in fact it isn't? I'm only trying to understand how this works.
>
> I'd
>
> > like for the spam to NOT show up in my squirrelmail inbox at all if
> > possible and maybe be sent automatically to a spam folder that I
>
> create
>
> > inside of squirrelmail or in outlook for my outlook users. Did I not
> > config properly?
> >
> > Thanks
>
> install maildrop
>
> put something like this in .qmail file for the user
>
> |/usr/local/bin/maildrop
>
> /home/vpopmail/domains/domain.name/mailfilter-spam
>
> here is a mailfilter. it is generic, so it works for any user
> ps. maildrop is picky, so no empty lines/comments in the if statement
> ;-)
>
> import EXT
> import HOST
>
> VPOPBIN="/home/vpopmail/bin"
> QMAILDIRMAKE="/var/qmail/bin/maildirmake"
>
> MAILDIRQUOTA=`$VPOPBIN/vuserinfo -q [EMAIL PROTECTED]
> VUSERDIR=`$VPOPBIN/vuserinfo -d [EMAIL PROTECTED]
> VMAILDIR="$VUSERDIR/Maildir"
> SPAMDIR="$VUSERDIR/Maildir/.SPAM"
>
> if (/^X-Spam-Flag: *YES/)
> {
>         `test -d $SPAMDIR`
>         if( $RETURNCODE == 1 )
>         {
>                 `$QMAILDIRMAKE $SPAMDIR;chown -R vpopmail.vchkpw
> $SPAMDIR`
>         }
>         to $SPAMDIR/
> }
> else
> {
>         to $VMAILDIR/
> }
>
> you might need to use courier-imap's maildirmake (if that is what you're
>
> using). I found that I had to use it where version 4.xx is installed, to
>
> create some ACL support files.
>
> HTH

-- 
-----------------
Bob Hutchinson
Midwales dot com
-----------------

Reply via email to