Re[2]: How to catch all messages in a filter - was - Re: Move old messages

2000-01-14 Thread Alex Sanyukovitch
Hello Thomas, Friday, January 14, 2000, 1:46:12 PM, you wrote: OZ Maybe it's a bug, but I don't think that it should be corrected OZ until we have a legal way to filter all messages. AS I can't understand this logic... How did you found it? TF Makes sense to me: If there is .NOT.(''),

Re[2]: How to catch all messages in a filter - was - Re: Move old messages

2000-01-14 Thread Alex Sanyukovitch
Hello Thomas, Friday, January 14, 2000, 7:34:32 PM, you wrote: TF Makes sense to me: If there is .NOT.(''), meaning if there is not TF nothing i.e. anything (anything at all), the filter should catch it. AS Lookagain: 'NOT' belongs to "Presence", so .NOT.('') means that AS there is no

Re[2]: How to catch all messages in a filter - was - Re: Move old messages

2000-01-13 Thread tracer
Hello Steve Lamb, On Thu, 13 Jan 2000 08:18:23 -0800 GMT your local time, which was Thursday, January 13, 2000, 11:18:23 PM (GMT+0700) my local time, Steve Lamb wrote: Better way - use @ character and search for it in the message headers. 100% guaranteed. Steve Acrually e is better. @

Re[2]: How to catch all messages in a filter - was - Re: Move old messages

2000-01-13 Thread Alex Sanyukovitch
Hello Steve, Thursday, January 13, 2000, 7:52:29 PM, you wrote: Not really. I do remove all "Received:" fields (and others like "X-List-Command:", "X-MSMail-Priority:", "X-Resent-To:", etc.) from my mail, because it takes too much space (sometimes more that half of message). So

Re[2]: How to catch all messages in a filter - was - Re: Move old messages

2000-01-13 Thread Alex Sanyukovitch
Hello Steve, Thursday, January 13, 2000, 8:49:59 PM, you wrote: SL Thursday, January 13, 2000, 10:34:43 AM, Alex wrote: SL This is your choice and does not invalidate the fact that messages, as SL they come in, do have those headers and thus that letter. Sorry, but it does mean! All