>>LOGFINALACTION ON
That could be useful.
In the next release, the final action will appear (by number) if LOGLEVEL
HIGH is used.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail
> >XOUTHEADER X-Spam-Final-Action: %FINALACTION%
>
> I'm not sure where this would be useful?
True, my bad. I read the line above that and didn't clearly read the rest.
>>LOGFINALACTION ON
That could be useful.
However, in our case since all actions are taken by weight, In the logs I
would j
-
From: R. Scott Perry [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 20, 2002 11:21 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Feature request - final action
>XOUTHEADER X-Spam-Final-Action: %FINALACTION%
I'm not sure where this would be useful?
For example, if an E
XOUTHEADER X-Spam-Final-Action: %FINALACTION%
I'm not sure where this would be useful?
For example, if an E-mail is deleted, you'll never see that header. It
will only say HOLD for E-mails that are in the \Imail\spool\spam
directory. If the WARN action was used, an X-RBL-Warning: header
> LOGFINALACTION ON
>
> And with an accompanying variable, e.g. %FINALACTION% which could be used
> thusly:
>
> XOUTHEADER X-Spam-Final-Action: %FINALACTION%
I second that motion. :))
John Tolmachoff MCSE, CSSA
IT Manager, Network Engineer
RelianceSoft, Inc.
Fullerton, CA 92835
www.reliances
I have a feature request. With v1.65 of Declude JunkMail, the manual's list
of action precedences, my logs and my message headers have all the necessary
data for me to construct the post-facto reporting of what happened to a
given message. But it also means that I have to build into my reporting,
