Looks fine to me On Fri, Jan 2, 2015 at 3:13 PM, Dennis Burgess <[email protected]> wrote:
> :D > > > > Dennis Burgess, CTO, Link Technologies, Inc. > > [email protected] – 314-735-0270 – www.linktechs.net > > > > *From:* Af [mailto:[email protected]] *On Behalf Of *That One Guy > *Sent:* Friday, January 02, 2015 3:57 PM > *To:* [email protected] > *Subject:* Re: [AFMUG] is this thing on? > > > > Im so happy > > > > On Fri, Jan 2, 2015 at 3:50 PM, Seth Mattinen <[email protected]> wrote: > > 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 > > > > > > -- > > All parts should go together without forcing. You must remember that the > parts you are reassembling were disassembled by you. Therefore, if you > can't get them together again, there must be a reason. By all means, do not > use a hammer. -- IBM maintenance manual, 1925 >
