Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[BLU] Re: [BLU]



David Kramer wrote:
> > Could this be solved by putting [BLU] at the *end* of the subject
> > line, so that mail filters have the text they need to match, no
> > fewer characters from the real subject line are displayed, and in most
> > cases (when the subject is shorter than their subject field) the [BLU]
> > identifier shows up for people to see too?
> 
> I don't see the point.  As discussed, almost any MUA, and certainly
> procmail, is capable of filtering on the existing headers.  

Actually, from the discussion on the mailing list, it seemed like many
people on the list were reading mail with software which didn't have
that functionality.  I understand that software exists which does, but
several people said that their MUAs only filtered on a few headers,
incl. the subject line.

There's probably no benefit to you (or to me), but it sounded like
there would be for others.  And if there's no real down side, why not?


> The point was that some of us don't want yet another folder to look
> for new mail in, yet want the BLU mail to stand out from the rest of
> /var/spool/mail/$USER.  That's why I have procmail put that in the
> subject of incoming BLU mail.

Presumably you'd still be able to do what you wanted with procmail.


--grg
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org