Filter for crashing emails

[Kris Sorem Sr]

On Sun, 18 Jun 2000 22:49:08 -0300 (ADT), Trevor Smith wrote:

>>As stated in the help file (and my experience) the above filter actions
>>will cause the filtered message to be marked as read and moved to the
>>trash folder. That's it. Move and Delete are mutually exclusive. Each will
>
>Negative. I have been using the above successfully for a LONG time.
>Move and delete are not mutually exclusive here. If I delete from any
>folder other than the Trash, the message is moved to the trash. If I
>delete from the Trash, the message is removed from my hard drive.
>
>Where in the Help does it contradict this?

Help=>Help Index=>Filter Settings=>Table of Allowable Actions
On this page it states in red lettering:
 "     Warning: It is important to note that if the 
       message is moved, all further filtering will STOP 
       at that point.  No more actions will be 
       performed and no more filters will be run on 
       the message."

My understanding of this /warning message/ is that move is the final
action performed.

On the same page it states in red lettering:
"      Warning: It is important to note that if the 
       message is deleted, all further filtering will 
       STOP at that point. No more actions will be 
       performed and no more filters will be run on 
       the message."

My understanding of this /warning message/ is that delete is the final
action performed.

>
>Possibly if "true deletes" is checked the behaviour is different...

I do not have "true deletes" set. I have 0 days set to remove messages
from trash at shutdown. This permits recovery if necessary.
>
>>cause any subsequent filter actions and any subsequent filters to not be
>>executed. 5c and 5d will not occur. Moving the message to the trash folder
>
>Again, this is not the behaviour I see here. The above filter worked
>exactly as I claimed when I tested it. It did mark the message read,
>it did move the message to the Trash folder, it did then remove it
>from my hard drive and it finally notified me that the filter had
>'found a message'.

My comments are based upon experience with ICSL in prior PMMail versions.
Since the Help File was not changed, I did not test the current version
prior to making my comments.
>
>However, you are right, further filters don't seem to work after this
>filter.
>
>>is the same as deleting the message with "Perform True Deletes" not set.
>>5a isn't really needed since the trash folder icon will change back when
>>the message is actually deleted. I prefer to know that my trash folder
>>contains messages I haven't really read.
>
>That is a valid concern. However, my filter was designed to remove
>messages from the system, not leave them in the Trash so your Trash
>icon shouldn't have been set if my filter worked.
>
>There are some issues (with PMMail/2 at least) with the flashing of
>the minimized status window (which is supposed to alert users to
>unread mail). This is the reason why I set the status to 'read'. If
>you want the message to remain in the trash, then leaving the status
>'unread' makes sense.

The minimized status window broke in a prior version and hasn't been
resolved. I reported to Southsoft but received no solution. I get a black
bar which previously identified the program running. The bar flashes white
then black when new mail is received. I ceased using the setting.

>
>>The message will not necessarily be  irretrievably deleted. Your filter as
>>written will cause PMMail to delete the message according to the time
>>frame for emptying the trash folder set in Account Settings...,
>>Preferences page.
>
>Again, this is incorrect. I have just repeatedly tested it and
>definitely does work as I claimed.

Again, my comments are based upon prior ICSL version experience and the
Help File.

>
>Messages which are only "deleted" by a filter are moved to my Trash
>folder.
>
>Messages which are both 'moved' to Trash and then "deleted" by a
>filter are removed from my system. No errors occur. Further filter
>actions do indeed occur.
>
>Furthermore, if you check mail from the minimized status bar, and you
>do *NOT* set the status to "read" before moving the message to the
>Trash and then deleting it, the status bar will flash and claim that
>the account has unread messages but 
>when you maximize, of course, there will be no messages to read.

It does not perform that way on my system with the /current/ ICSL version.
I tried move,inform user, set status, then delete with the minimize status
bar active. It did not flash. If, however, set status is not preformed
prior to delete then the minimized status bar will flash.
>
>Again, I do not have true deletes checked.

Again, neither do I.
>
>Can you confirm or deny this?

I can confirm by testing the /current/  ICSL version that it /does not/
perform according to the Help File and prior ICSL versions. If the
/current/ filter contains move and/or delete subsequent actions are
completed but no additional filtering occurs. You can delete and then move
(if true deletes not set). Blueprint Software Works should be informed of
this difference. Filter action /does not/ STOP at the point of a move or
delete. It does remove the message from the system /only/ because the
Trash folder is uniquely different from other folders. Your actions could
be performed in any order with delete being the last action.
>
>Here is the test filter I am using to prove this (on my system at
>least). I am testing with this as the ONLY filter I have active for
>this account.
>
>1. enabled
>2. incoming
>3. simple
>4. search subject: for "test email for trevor"
>5. move message to Trash
>6. delete message (local copy)
>7. inform user

Tested and confirmed that all actions of the /current/ filter are
performed regardless of order. This /is/ different from prior ICSL
versions and in contradiction to the Help File.

--
JMO, 
/s/~Kris
-------------------------------+---------------------------------------------