This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: [META] Other mailing list ideas
- From: carlo at astra dot ph
- To: cygwin at cygwin dot com
- Cc:
- Date: Mon, 15 Dec 2003 22:40:47 -0800
- Subject: RE: [META] Other mailing list ideas
This is a great idea! Although I am only a simple subscriber
to this mailing list, I would gladly celebrate with the proposition.
The EOF stuff would save a considerable amount of space in the
archives.
Thanks!
Best Regards,
Carlo
------
Carlo Florendo
Astra Philippines Inc.
www.hq.astra.ph
--- Original Message ---
Christopher Faylor
Mon, 15 Dec 2003 22:52:55 -0500
------------------
I'm toying with the idea of having the mailing list software
munge
certain types of mailing list addresses in the body of a message
as it comes in, before it is archived or sent out.
The patterns I'd look for are something like:
aaaspam@sourceware.org writes:
munged to
aaaspam writes:
<aaaspam@sourceware.org> writes:
munged to
aaaspam writes:
Albert A. Aspam <aaaspam@sourceware.org> writes:
munged to
Albert A. Aspam writes:
>.*aaaspam@sourceware.org
munged to
>.*aaaspam
From: Albert A. Spam <aaaspam@sourceware.org>
munged to
From: Albert A. Spam
From: <aaaspam@sourceware.org>
munged to
From: aaaspam
etc.
Any objections to this? This should leave email addresses in
signatures
and in ChangeLogs alone while catching the majority of the abuses,
I think.
We'd also talked a while ago about adding something like a --EOF--
flag
which could be put in a message to cause the mailing list software
to
ignore everything after that point. This would allow the opt-in
removal
of those multi-line disclaimers that everyone loves.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/