I'm still trying to come up with an easy to implement way
to give us more control over conflicting final actions.
Specifically, I have several tests set to HOLD or DELETE
(in fact, the vast majority of incoming
mail) - however, a small number of them escaped detection by
Sniffer or
Maybe one solution would be to set up an action that for instance would
ROUTETO NULL, so that you could use this in place of DELETE and still get
the COPYTO function to work?
Actually, you can get DELETE and COPYTO to work. In this case, the DELETE
action isn't really desired -- you just want
Therefore, how about we allow a filter command to selectively reset pending
action, e.g.:
RESETACTIONDELETE
RESETACTIONHOLD
The problem here is that Declude JunkMail doesn't determine the actions
until after the tests are run, and the recipient information is looked
at.
Regards
Andy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Fisher
Sent: Tuesday, June 08, 2004 06:16 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Feature Suggestion - More control over
final action
Regarding Message Sniffer. It's more
Scott,
Although I don't have this specific need, I could see use from it at
some point in time as if you want to place an E-mail in an account
somewhere, you can't HOLD or DELETE it.
Maybe one solution would be to set up an action that for instance would
ROUTETO NULL, so that you could use
