Date: Fri, 12 Jun 1998 23:02:30 -0500 From: Dan Nelson <dnelson@emsphone.com> To: greeves <sysadmin@mfn.org>, "'FreeBSD Questions'" <freebsd-questions@FreeBSD.ORG> Subject: Re: [FBSD-Q] Type header??? Message-ID: <19980612230230.A10098@emsphone.com> In-Reply-To: <01BD9650.8535FD60@dhcp7_ppp07.mfn.org>; from "greeves" on Fri Jun 12 22:22:00 GMT 1998 References: <01BD9650.8535FD60@dhcp7_ppp07.mfn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 12), greeves said: > subscribe send a notation header to sort on. For instance, If I send > a posting to NT Security about a new port attack, and put "New Port > Attack" in the subject line of my post, it will arrive from the > listserv like this: > > [NTSEC] New Port Attack > > Obviously, using the subject this way allows people (often me as > well, depending on what area of the shop I'm working in that day) who > can't filter automatically by sender or relay points to scan the > subjects quickly, and thereby determine if the mails can wait, or > whether a given email may be customer related. I dislike mailinglists messing with my subject header. It wastes 7 (in your example) characters in the subject and screws up replies (I've seen Re: [mysql] Re: [mysql] Re: [mysql] in one list) and list crossposts. What's wrong with installing Procmail and filtering on "Sender:"?, or bugging the author of your email package to allow filtering on arbitrary headers? -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980612230230.A10098>