On Wed, Jan 21, 2004 at 05:21:24PM +0200, Sheldon Hearn wrote:
> On (2004/01/21 15:19), Calum Mackay wrote:
>
> > >However, my filter uses the first X-Spam-Score header it sees. If
> > >a spammer sends me mail with an X-Spam-Score that says the message
> > >isn't spam, my filter believes that, because it readds the spammer's
> > >X-Spam-Score header before it reads the one my server added.
> >
> > You could try using a more custom header for your score; e.g:
> > X-$primary_hostname-Spam-Score, and refererence this in your filter, and
> > in your analysis.
>
> Yes. If I don't find a cleaner way to do what I want, that'll be the
> next best thing.
>
> However, since this will be used in a large number of installations,
> any header name I generate can be "figured out" and then abused.
>
man spamassassin shows
-d, --remove-markup Remove spam reports from a message
Could combining this with other options help?
Maybe this this not possible in the spamc/spamd scenario.
--
Some days it's just not worth chewing through the restraints...
Mark Foster <mark@???>
http://mark.foster.cc/
