RFC: Zimbra generates In-Reply-To incorrectly?

[Baylink]

I've just gotten my installation running finally (in my Copious Free Time) and hit my first *major* snag:

It appears that Z (or the webclient, whichever is pertinent) generates improper In-Reply-To headers. I will deal with the fact that it doesn't thread *inbound* mail on them later, that only affects me... but rewriting them breaks the RFC -- and threading for everyone else -- and has to be dealt with first.

I replied to a message from a Yahoogroups (irony is great, isn't it? :-) mailing list with this Message-ID:

<9423743.1221407307773.JavaMail.root@elwamui-milano.atl.sa.earthlink.net>

And the copy of my message which the mailing list sent me back had an In-Reply-To header of this:

In-Reply-To: <31469464.491221407842912.JavaMail.root@benjamin.v icimarketing.com>

Any ideas, folks? Could this be caused by a misconfiguration, or should I open a ticket on it?

[dkarp]

Never seen this before and can't repro. My first guess is that your mailing list provider may be incorrectly rewriting the In-Reply-To header. Look at mail sent to the list by another user around the same time and see if there's similar rewriting going on.

[Baylink]

This list has been well-behaved in the past.

I will attempt to reproduce with several of my lists, and see, but as I noted, the provider is *yahoogroups*. Not Fat Jack's Cancer Clinic and Mailing Lists. :-)

[Baylink]

There's a possibility this happened because I was in Conversation mode at the time; I've turned it off for now, because I don't like the way it displays in addition to not liking the way it threads, and this test came out ok.

I'll try a reply to a list again tonight with Conversation mode back on and see what happens.