Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of erh@swapsimple.com designates
 66.225.208.96 as permitted sender)
Date: Mon, 1 May 2006 22:56:16 -0500
From: Eric Haszlakiewicz <erh@swapsimple.com>
To: Mark Thomas <markt@apache.org>
Cc: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Easy Tomcat Linux/Unix Platform
Message-ID: <20060502035616.GA2755@poe.swapsimple.com>
References: <4454C3C5.4050002@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4454C3C5.4050002@apache.org>
User-Agent: Mutt/1.4.2.1i

On Sun, Apr 30, 2006 at 10:03:49AM -0400, Mark Thomas wrote:
> When starting a new thread (ie sending a message to the list about a
> new topic) please do not reply to an existing message and change the
> subject line. To many of the list archiving services and mail clients
> used by list subscribers this  makes your new message appear as part
> of the old thread. This makes it harder for other users to find
> relevant information when searching the lists.
> 
> This is known as thread hijacking and is that is frowned
> upon on this list. Frequent offenders will be removed from the list.
> It should also be noted that many list subscribers automatically
> ignore any messages that hijack another thread.
> 
> The correct procedure is to create a new message with a new subject.
> This will start a new thread.

	What would be really nice is if the digest emails included the
In-Reply-To header on the individual pieces, so my mail software
could actually piece together the threads in the correct way.
Right now all it has to go on is the subject, which doesn't always work.

eric

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org