On 02/09/2009 01:03 AM, Harold Fuchs wrote: > > Can the new TB or SM filter on the *content* of the header as well as on its > "type"?
Yes of course. Same as the email filter. A header filter wouldn't be very effective if it couldn't filter on the content of the header... > > Headers have types (don't know the official name): "Reply To", "Delivered > To" etc. and each type can take any of several values. For example, the > "Reply To" header can take a (list of) e-mail address(s) as its value. The > "Delivered To" header can take as a value "moderator for .." among other > things. And so on. > > The *mail* module of the existing TB can handle user-specified types and > values. The *news* module can only handle a few built-in types but can > handle values for the types it knows about. > > Can the new SM not handle types and values in both news and mail? > Yes. As mentioned, the problem is that OOo places two identical headers in the msg. The filter detects the first Delivered-To and find no 'moderator' in the content, so it goes on to the next filter in the list. So there are two bugs here: 1. OOo can put 'Delivered-To:moderator...' first, or modify the header name in exmlm. 2. SeaMonkey 2.x/Thunderbird 3.x should be able to filter on multiple headers (similar to multiple 'X-Originating-IP' headers in an email). If you'd like to give TB 3.x a spin to see how it filters this list (have to stay on topic for OOo :-), you can download and try: <http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/> SeaMonkey: <http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
