-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 22 Sep 2001 20:14:26 +0530, Raj [R] wrote these words of wisdom: I had meant to comment on this and somehow forgot. Anyway, better late than never. :-) ... JA>> b) Create two incoming filters at the top of the filter list. The JA>> first one should find the large message notifications and *not* JA>> continue to process with other filters. The second filter should JA>> work on all messages. It should "Delete mail from server" and JA>> "Continue processing with other filters." R> I am a little lost... can you elucidate further on the logic of the R> filter. As soon as a message is matched with a particular filter rule, by default, the message is no longer processed with other filter rules. This means that no other filter rules further down the filter list are applied to the message even though there may be string matches in other filter rules. We wish to delete all messages from the server except messages that exceed a certain size. We therefore set the size limit in the account options where TB! will send an alert message containing the large message headers. We set up a filter to catch these alert messages and place this filter at the beginning of the list. These notification messages will therefore not be processed by the second filter. The second filter rule tells TB! to delete the matching message from the server. This action is carried out on the next mail check. This filter with the search string set to 'e' and 'Kludges' will match every single message it examines. It will not get to examine and match the large message notifications because these are matched and removed from further processing by the first filter rule. We also wish all the rest of messages to be processed by the remaining filter rules so for this second rule, we have to enable the option 'continue processing with other filters.' This in effect breaks TB!'s default filtering behaviour which is to stop filter rule matching as soon as a match is found. The large message notification messages aren't processed by the filter to delete messages from the server so the large messages are spared from deletion. You may then examine them at leisure with the message dispatcher and delete them manually, or in TB!'s account options set messages to be deleted after a defined period of time. R> I am also not sure how *not* continue to process other filters R> work... Never used that option. As I explained before and will do again for clarity: TB!'s default behaviour is to stop matching filter rules with a message as soon as a matching filter is found. A match attempt is made sequentially, starting from the topmost filter and working downwards. It's important that this concept is grasped since this is the same approached used by most other filtering systems and understanding this will make you able to do complex filtering impeccably. Nothing beats an example: Say you wish to apply flag a group of messages that you also wish to move to different folders. You already have filter rules defined to move these messages to their respective folders. You also have found a string that's common to all these messages. What you can do is to create a filter rule, placing it above the ones you created to move these messages to their respective folders. Make the source and destination folders the inbox. Define the common string as the search criterion. Define the action you wish to apply which is flagging the message in this instance, and then enable 'continue processing with other filter rules.' Without this final vital setting enabled, the messages will no longer be processed once this common filter is applied. They'll simply remain in the inbox flagged and not be moved to their respective folders. - -- �Allie C Martin �� List Moderator (and fellow end-user) PGP public key: http://pgpkey.ac-martin.com __________________________________________________________ MUA: The Bat! 1.54 Beta/9 [OS: Windows 2000 Service Pack 2] _ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6a (Win32) Comment: Sealed for security. iEYEARECAAYFAjuuLGgACgkQV8nrYCsHF+LI8ACg+L7Lg5iA48ZydKV0v/WuK1e2 e4sAnir3GKhHKKDMmoMqJy7md1jH82zt =YAm7 -----END PGP SIGNATURE----- -- ________________________________________________________ Archives : http://tbudl.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] TBTech List: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Latest Vers: 1.53d
