second call on sa doesn't add x-spam-flag

[Johannes Rumpf <ru...@fbihome.de>]

Hi @all,

i'm runing xfilter "spamassassin" in my procmail rules. Thats the second 
time the server runs spamassassin. First with spamd with an other points 
and bayes filter, second via xfilter. The mails are detected correctly 
as spam, but there are no x-spam* in the mail-header so i can't move the 
spam-mail in my spam-folder via procmail-rules.

Any Ideas?

cheerio Joe

Re: second call on sa doesn't add x-spam-flag

[Johannes Rumpf <ru...@fbihome.de>]

> At 02:22 PM 10/15/2004, Johannes Rumpf wrote:
> 
>> i'm runing xfilter "spamassassin" in my procmail rules. Thats the 
>> second time the server runs spamassassin. First with spamd with an 
>> other points and bayes filter, second via xfilter. The mails are 
>> detected correctly as spam, but there are no x-spam* in the 
>> mail-header so i can't move the spam-mail in my spam-folder via 
>> procmail-rules.
> 
> 
> Why are you using xfilter when calling SA? SA is already a mail-pipe 
> designed to be called directly from procmail.
> 

Hi Matt,

it is called directly in the mail-pipe. But it's calling the general 
spamassassin config for all users. But i like to habe a more stronger 
config and haven't got the control over the overall mail-process. 'cause 
just have an user on the system.

Joe

Re: second call on sa doesn't add x-spam-flag

[Matt Kettler <mk...@evi-inc.com>]

At 02:22 PM 10/15/2004, Johannes Rumpf wrote:
>i'm runing xfilter "spamassassin" in my procmail rules. Thats the second 
>time the server runs spamassassin. First with spamd with an other points 
>and bayes filter, second via xfilter. The mails are detected correctly as 
>spam, but there are no x-spam* in the mail-header so i can't move the 
>spam-mail in my spam-folder via procmail-rules.

Why are you using xfilter when calling SA? SA is already a mail-pipe 
designed to be called directly from procmail.