Re: list behavior

Kevin Cosgrove <[email protected]>
Newsgroups gmane.mail.exmh.user
Message-ID <[email protected]>

[email protected] said:

> Hopefully nobody will do that.  I *HATE* lists that prepend garbage
> to the subject (unfortunately, Yahoo doesn't have a way to turn that
> off on their lists/groups).
> 
> If you personally want the tag, you can probably alter the subject
> via filters or just sort into different boxes/folders.  There are
> plenty of headers to filter on (List-*, Reply-To, X-Loop, etc). 


On 7 September 2006 at 10:50, Chris Garrigues <[email protected]> wrote:

> > From:  Kevin Cosgrove <[email protected]>
> > Date:  Thu, 07 Sep 2006 08:35:57 -0700
> > Is there any way to get this list to prepend something like 
> > [exmh-users] to the subject line when sending out messages?
> > *Every* other list I'm on does that, and it's really useful.
> 
> I think the idea is that if you're using exmh you're using
> tools which are smart enough to filter on less annoying
> headers than the subject line.  Try filtering on "List-id:" or
> "Sender:".

It seems that I'm alone so far in my desire for a visual clue as to 
where the message came from.  I'd rather not have to interact with 
exmh as much as to filter manually, e.g. pick, or automaticly drop 
messages into various folders and then read my mail in a plethora of 
folders.  It's faster for me to just scan the FTOC to see what spam 
made it through 3 levels of spam filtering to get to my inbox.  List 
identification on the subject line helps me to do that.

The filtering suggestion was a good one.  I set up a procmail recipe 
that looks for the list-id and prepends [exmh-users] to my subject 
lines.  Now *I* can have the behavior I want without inconveniencing 
anyone else.  Pretty cool.  FWIW, here's the procmail recipe:

:0fw
* ^List-id: Discussion list for EXMH users <exmh-users.redhat.com>
| /usr/bin/perl -pe 's/^Subject:/Subject: [exmh-users]/'

Cheers...


--
Kevin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.