Message Threading was Re: list etiquitte

--=-jK6dR4Q1QebkhxDZJO3U
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2003-09-26 at 10:00, ted@gould.cx wrote:

> I really don't get why this bothers people. It bothers me more when the
> subject line of the message doesn't describe the message. If a
> conversation strays, the subject line should move with it. Any correctly
> coded mail client (on both ends) will continue to keep up with the
> threading of the discussion through changes in the subject line. I just
> don't see it as an issue. (And probably by me doing this is why you're
> writing this message ;)

It bothers them because their mail client relies somehow on the message
subject to do threading instead of using the correct identifiers within
the source of the message. I understand their gripe, but I tend to
agree 100% with you. Good subject lines are better than crappy ones. :)

However, they could gripe about what I do. When I want to send a new
message to PLUG. I generally will open an existing one and change the
subject and send. This is bad etiquette, but its my way of protesting
the hideous domain name we refuse to address=20
PLUG-discuss@lists.plug.phoenix.az.us is just nasty. ;)

--=20
Derek Neighbors
GNU Enterprise
http://www.gnuenterprise.org
derek@gnue.org

Was I helpful? Let others know:
http://svcs.affero.net/rm.php?r=3Ddneighbo

--=-jK6dR4Q1QebkhxDZJO3U
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/dH15Hb99+vQX/88RAhrIAJ9AOJLZ29Bs9DcssEgxI9fgqrRvJgCfYLMR
M+Vrgy2jGsLQ8tkfGAb/dF4=
=Ln2H
-----END PGP SIGNATURE-----

--=-jK6dR4Q1QebkhxDZJO3U--