Re: [cobalt-users] SpamAssassin forwarding mailbox

["VFastlink Support Team" <support@xxxxxxxxxxxxx>]

----- Original Message ----- 
From: "Jeff Lasman" <blists@xxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Friday, April 09, 2004 12:01 AM
Subject: Re: [cobalt-users] SpamAssassin forwarding mailbox


> On Wednesday 07 April 2004 09:47 am, VFastlink Support Team wrote:
>
> >   Does anyone have any ideas on creating a forwarding mailbox for
> > SPAM?  We would like to forward all SPAM to a mailbox so that
> > SpamAssassin can learn from the mail deposited there.  The problem is
> > that SpamAssassin takes the headers into account so it would be
> > learning that we are potential spammers and not the originating
> > emails.  There is a script posted on SpamAssassin's Wiki pages but it
> > doesn't work too well.  Have any of you come up with a good plan to
> > tackle this problem?
>
> Instead of forwarding, use procmail to sort it into a mailbox based on
> the number of asterisks in the X-Spam header.
>
> Jeff
> -- 
> Jeff Lasman, nobaloney.net, P. O. Box 52672, Riverside, CA  92517 US
> Professional Internet Services & Support / Consulting / Colocation
> Our blists address used on lists is for list email only
> Phone +1 909 324-9706, or see: "http://www.nobaloney.net/contactus.html";
>
> _____________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>

Thanks for the suggestion.  I guess I didn't explain myself well though.
SpamAssassin has the ability to "learn" from a mailbox.  You can tell it to
search through a paticular mailbox and recognize everything in it as SPAM.
What we are trying to do is setup a mailbox that we can forward our SPAM
that gets through the filter.  As SPAM is received, we would like to forward
to this mailbox and then run a cron job to tell SpamAssassin to "learn" the
SPAM that resides there.  The problem is that when you forward an eamil, the
header contains this forward information.  SpamAssassin uses the header
information as part of it's criteria.  We were hoping someone had made a
script that would strip out that extra header information from the mal and
then run the SpamAssassin command.  There is a sample one on the
SpamAssassin site, but it doesn't work very well.