And this behavior definitivly changed from 3.4.1 to 3.6.{3,4}.
FWIW, yes. we did do a _lot_ of work on references and in-reply-to between 3.4.1 and 3.6. But most of it was to get _more correct_ header info.
Looking at a random message coming off of our 3.6.3+devel instance, I see this:
In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-Id: <[EMAIL PROTECTED]>
Precedence: bulk
X-Rt-Loop-Prevention: bestpractical.com
And things thread just fine.
Jesse
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
