On 1/2/15 13:35, Paul McCall wrote:
Seth, is it /possible/ that that is an issue with his client that would
cause that result?
How does the rest of the thread look?
I don't think it's him, threading is still broken since the Message-ID,
References, and In-Reply-To headers are still coming across as a mixed
bag of random.
My message was:
Message-ID:
<0000014aac891658-2f8983aa-3868-492a-a54e-bc346f07a88d-000...@email.amazonses.com>
Your response had:
References:
<0000014aac80139f-0a0965b9-fad8-4aef-bedb-b381a6bcf84f-000...@email.amazonses.com>
<0000014aac891840-edbb201c-e004-4b6b-a2cd-a5a46b6b052b-000...@email.amazonses.com>
In-Reply-To:
<0000014aac891840-edbb201c-e004-4b6b-a2cd-a5a46b6b052b-000...@email.amazonses.com>
Which is incorrect if you were indeed replying to my message. Of course
this is only what I see; if SES is changing headers vs. what was
submitted by the sender I can't see that.
The WISPA lists work fine and enough people on here are also over there
posting without breaking threading, so for that reason I find it
unlikely to be a client problem.
~Seth
