[Full-Disclosure] Re: Announcing new security mailing list
From: martin f krafft (full-disclosure@lists.netsys.com)
Date: 07/13/02
- Next message: martin f krafft: "[Full-Disclosure] ALERT!!! ALERT!!! ALERT!!! ALERT!!! ALERT!!! ALERT!!! ALERT!!!"
- Previous message: Matthew Murphy: "[Full-Disclosure] Three BadBlue Vulnerabilities"
- In reply to: Ron DuFresne: "[Full-Disclosure] Re: Announcing new security mailing list"
- Next in thread: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Reply: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Reply: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Reply: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Reply: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: full-disclosure@lists.netsys.com (martin f krafft) Date: Sat, 13 Jul 2002 18:53:56 +0200
--LQksG6bCIzRHxTLp
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
also sprach Ron DuFresne <dufresne@winternet.com> [2002.07.11.2010 +0200]:
> > BTW, spewing "[full-disclosure]" into the subject line is a very annoyi=
ng
> > thing for a list to do.
> >
>=20
> Actually, it makes it quite easy for procmail recipies and certain mail
> readers to filter and categorize the messages.
there are many other headers one may use. e.g., i use:
=20
* ^List-Id:.*full-disclosure\.lists\.netsys\.com
i do consider [Full-Disclosure] in the subject line rather annoying
because it wastes valuable subject space. good mailing lists have
subject lines that allow the pre-elimination of anything that doesn't
concern one. especially if it's high traffic, this is something more
than necessary. i vote to take the subject prefix off.
it would also be nice to have received headers cut off when the
listprocessor starts its job on such a public mailing list.
--=20
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
=20
wind catches lily,
scattering petals to the ground.
segmentation fault.
--LQksG6bCIzRHxTLp
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj0wWyQACgkQIgvIgzMMSnWBowCgkCq3EoYmvZrBV8Paqy8qqW6E
FaIAoL0xHG8MxhiKQYyvA2WIZMA/7nR6
=w5iN
-----END PGP SIGNATURE-----
--LQksG6bCIzRHxTLp--
- Next message: martin f krafft: "[Full-Disclosure] ALERT!!! ALERT!!! ALERT!!! ALERT!!! ALERT!!! ALERT!!! ALERT!!!"
- Previous message: Matthew Murphy: "[Full-Disclosure] Three BadBlue Vulnerabilities"
- In reply to: Ron DuFresne: "[Full-Disclosure] Re: Announcing new security mailing list"
- Next in thread: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Reply: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Reply: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Reply: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Reply: V K: "[Full-Disclosure] Re: Announcing new security mailing list"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|