Great Circle Associates List-Managers
(July 2002)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Header fields (Was: Re: Please prune this list!)
From: JC Dill <inet-list @ vo . cnchost . com>
Date: Sat, 06 Jul 2002 11:50:09 -0700
To: list-managers <list-managers @ greatcircle . com>
In-reply-to: <16161.1025975301@kanga.nu>
References: <Message from Charlie Summers <charlie@lofcom.com><v03130306b94cbe6ba6ef@[192.168.123.10]><5.0.0.25.2.20020706005508.0344a4b0@pop3.vo.cnchost.com><B94BEB09.46960%chuqui@plaidworks.com><v03130306b94cbe6ba6ef@[192.168.123.10]>

On 10:08 AM 7/6/02, J C Lawrence wrote:

 >One practice I'd like to see more of is lists publishing filtering
 >instructions for themselves.  Even better though would be MUAs that
 >_BY_DEFAULT_ create list-specific folders and filter mail into them
 >whenever they see List-ID:, X-Mailing-List:, etc headers.

Eudora actually comes close.  Select a group of messages from a list and 
then select "special, make filter".  Eudora looks for a common header and 
then creates what it believes is the desired filter.  When I selected a 
group of messages from this list, it offered to make a filter that:

A) acts on "incoming" email and when "manually" filtering
B) filtering on "any recipient" contains: list-managers@greatcircle.com 
(list-managers)
C) transferring messages to a new folder named: list-managers (which Eudora 
will then create)
D) skipping the rest of the filters in the list




Follow-Ups:
References:
Indexed By Date Previous: Re: identifying list mail by any appearance in the headers
From: JC Dill <inet-list@vo.cnchost.com>
Next: Re: identifying list mail by any appearance in the headers
From: J C Lawrence <claw@kanga.nu>
Indexed By Thread Previous: Re: Header fields (Was: Re: Please prune this list!)
From: J C Lawrence <claw@kanga.nu>
Next: Re: Header fields (Was: Re: Please prune this list!)
From: J C Lawrence <claw@kanga.nu>

Google
 
Search Internet Search www.greatcircle.com