[TriLUG] more spamassassin, procmail, damaged 'from' line and beyond

[Jon Carnes]

Use the "X-Spam-Level:" line to filter the mail.  The line will have a
number of asterisks on it equal to the Spam level that was detected.  So
you can set the /dev/null option for when there are 12 or more *'s on
the line and if it makes it past that filter then check for 7 or more to
move it into the mailbox "caughtspam".

Good Luck - Jon Carnes 

On Tue, 2003-04-15 at 16:46, Turnpike Man wrote:
> Thanks to Jeremy's latest input, and the archived discussions from everyone, I
> have achieved SpamAssassinator status!!  WOOO!!  I am able to send myself test
> messages and the ones get in that I want and even the ones I send from myself
> which are loaded with BS spam jargon fall away into "caughtspam".
> 
> Now I have a few questions.  I suppose all spams get appended to that
> caughtspam file, such that if there is a false-positive, I'll find it in there.
>  Otherwise, could I make this change to .procmailrc :
> 
> From:
> :0:
> * ^X-Spam-Status: Yes 
> caughtspam
> 
> To:
> :0:
> * ^X-Spam-Status: Yes 
> /dev/null
> 
> With that change, no longer would messages accumulate in caughtspam, but they
> would literally disappear, right??
> 
> Along these same lines, can I setup SA such that something between 5-10 pts is
> a maybe, get's labeled and goes to my Inbox and anything above 10 pts is
> automatically sent to /dev/null??  That would be great if it could be done that
> way.  I'm going to try to decipher the SA usage FAQ, but if anyone would like
> to enlighten me, that would be great!
> 
> Thanks!
> David M.
> 
> --- Jeremy Portzer <jeremyp at pobox.com> wrote:
> > On Thu, 2003-04-10 at 12:02, Turnpike Man wrote:
> > > Is procmail even required to have SA working with sendmail?  Why,
> > > why not?
> > 
> > There are ways to install spamassassin "site-wide" that don't involve
> > procmail, such as the "spamasssassin-milter" system.  But using procmail
> > is actually the easiest, despite the unreadability of procmail recipes.
> > :-)
> >  
> > > My current ~/.procmailrc file is as follows, and when in place, none of my
> > mail
> > > gets delivered, it just vanishes as far as I know.  Was this because of the
> > F
> > > in the From line or some other possible issue?  Have I not called
> > spamassassin
> > > correctly?  These were RPM installs.  (to be perfectly honest, I don't know
> > > exactly what all of these lines mean either, I'll put #comment on them):
> > > 
> > > -------------------------------
> > > PMDIR=$HOME/procmail   #no/kinda
> > > LOGFILE=$PMDIR/log     #no/kinda
> > 
> > This will put a logfile for procmail in ~/procmail/log .  You might want
> > to make sure that ~/procmail/ directory exists first!  This is very
> > handy because you should be able to look at the log file and see what
> > exactly procmail is doing.
> > 
> > > VERBOSE=no             #yes/kinda
> > 
> > You might consider changing that to yes until you get everything setup
> > the way you like it.
> > 
> > > MAILDIR=$HOME/mail     #yes
> > > 
> > > :0fw
> > > | spamassassin -P
> > > #I see this everywhere, supposed to point to bin??
> > 
> > This should be something like:
> > :0fw
> > | /usr/bin/spamassassin
> > 
> > There is no argument/option to spamassassin needed, and you should
> > include the full path.
> > 
> > > :0:
> > > * ^X-Spam-Status: Yes 
> > > caughtspam
> > > #I see this everywhere, seems the norm, I kinda get it, if spam, put
> > > #in caughtspam folder?
> > > -------------------------------
> > 
> > Right, that's the idea.
> > 
> > See for example http://spamassassin.org/dist/procmailrc.example
> > (It has the workaround for the procmail bug if you need it.  The example
> > also shows the use of lockfiles for the call to |spamassassin, but that
> > isn't actually needed since it's calling a filter, not writing to a
> > mailbox.)
> > 
> > Hope this helps,
> > Jeremy
> > 
> > -- 
> > /=====================================================================\
> > | Jeremy Portzer       jeremyp at pobox.com       trilug.org/~jeremy     |
> > | GPG Fingerprint: 712D 77C7 AB2D 2130 989F  E135 6F9F F7BC CC1A 7B92 |
> > \=====================================================================/
> > 
> 
> > ATTACHMENT part 2 application/pgp-signature name=signature.asc
> 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo
> http://search.yahoo.com
> _______________________________________________
> TriLUG mailing list
>     http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ:
>     http://www.trilug.org/faq/TriLUG-faq.html