Ok after doing some tests with spamassassin and
looking at the configuration more closely I realize
that the spamassassin headers shouldn't be in there
anyways as it looks like the filter runs the text
against spamassassin and when spamassassin prints out
the modified email with spam headers to stdout, grep
searches that output for the X-Spam-Status: header to
see if it was spam, and if it was it injects the
X-OTRS-Queue: spam header. However, that X-OTRS-Queue
header isn't being put into the emails. How would I
find out where the problem lies, as I don't know if it
is giving the emails to spamassassin properly, or if
the queue header isn't being injected properly or
what? Anyone have any ideas on how to figure this
out?
--Matthew Shapiro
--- [EMAIL PROTECTED] wrote:
> Erm it's still isn't filtering at all. I changed
> the
> spelling error (now it's exactly what it shows
> below,
> copy/pasted) and I got a piece of spam 53 minutes
> ago
> that doesn't have any of the spamassassin headers in
> it. Why isn't otrs running spamassassin? The otrs
> logs don't tell me a thing.
>
> --Matthew Shapiro
>
>
> > # Job Name: 5-Spam
> > # (Move spam to spam queue
> >
> $Self->{'PostMaster::PreFilterModule'}->{'5-Spam'}
> =
> > {
> >
> > Module =>
> > 'Kernel::System::PostMaster::Filter::CMD',
> > CMD =>
> > '/opt/spamassassin-301/bin/spamassassin
> > | grep -i "X-Spam-Status: yes"',
> > Set => { 'X-OTRS-Queue' => 'spam',
> > },
> > };
> >
>
> _______________________________________________
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe:
> http://lists.otrs.org/cgi-bin/listinfo/otrs
> Support oder Consulting f�r Ihr OTRS System?
> => http://www.otrs.de/
>
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support oder Consulting f�r Ihr OTRS System?
=> http://www.otrs.de/
