Great Circle Associates Majordomo-Users
(June 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Need help with Majordomo
From: Rich Pieri <rich . pieri @ prescienttech . com>
Date: 27 Jun 1997 14:40:05 -0400
To: majordomo-users @ greatcircle . com
In-reply-to: bob@intelenet.net's message of "Fri, 27 Jun 1997 10:18:54 -0700"
Mail-copies-to: never
References: <199706271718.KAA15189@ns.intelenet.net>

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "BM" == Bob Myers <bob@intelenet.net> writes:

BM> I don't understand Rich's comment about breaking mail programs that
BM> sort by message headers.  Messages could still be sorted, but they'd
BM> also be broken down by the mailing list.  What's broken about that?

In a perfect world there would be none.  The problem is that some mail
clients do odd things with Subject lines, such as the German version of
Exchange using "Aw:" instead of "Re:".  So, the person responsible for the
code that inserts the tags has a choice: either keep up with all the
brain-damaged mail clients and constantly update his leader regular
expressions, or say the hell with it and scan for the existance of the tag
string.  Each results in misplaced tags for different reasons; the former
will cause unnecessary tags to be added to the Subject header, the latter
can cause tags that should be added not to be if an instance of that string
occours somewhere else in the header -- not uncommon for topical mailing
lists.

To wit, you can get a subject that looks like this:

	Mj Re[3]: Mj Aw: Re: Mj Need help with Mj

or like this:

	Re: Need help with Mj

when both "should" look like this:

	Re: Mj Need help with Mj

The former case will break "subject threading" (not really threading
because References headers are not being used) of subjects because the tag
string looks like the "top" of a thread when the message is not.  The
latter completely fails to "fit" with other "Mj" list articles after
subject sorting.  Either way, the type of confusion that subject tag
strings are supposed to prevent not only cause them but exacerbate them.

Besides, modification of Originator headers is verboten by RFC 822.

-----BEGIN PGP SIGNATURE-----
Version: 4.0 Business Edition
Charset: noconv

iQCVAwUBM7QJA56VRH7BJMxHAQHRuwP/XJX/qxsz/cHq7LFysxAA0dej/VnFGhFS
pXFfTvYiLwUfGYD7O+svbtmZtHTxz12HLMQ5A4U2MIeo4+p7wPZ41jfkV1hoC+tM
z51KE0Q+NR3Bti9LIUMGwGLi1V9d+bf2LK8VasX8DzxnamaxFdFUpRep9ZMc6Q4/
5I/2fW5Ly6w=
=/Oju
-----END PGP SIGNATURE-----

-- 
Rich Pieri <rich.pieri@prescienttech.com> | Do not taunt Happy Fun Ball.
Prescient Technologies, Inc.              | 
A Stone & Webster Company                 | 
I speak for myself, not PTI or SWEC       | 


References:
Indexed By Date Previous: Re: Need help with Majordomo
From: "Lazlo Nibble" <lazlo@swcp.com>
Next: Real Easy Question, Tough-to-Find Answer...
From: James Cayz <cayz@lib.de.us>
Indexed By Thread Previous: Re: Need help with Majordomo
From: bob@intelenet.net (Bob Myers)
Next: Re: Need help with Majordomo
From: Monika Adamczyk <monika@omg.org>

Google
 
Search Internet Search www.greatcircle.com