–Am Dienstag, 20. Mai 2003 21:39 Uhr -0400 schrieb "Daniel E. Eisenbud"
This is a good start, but it’s broken in a number of ways. It defaults
to the wronge message-id for in-reply-to and it randomly mangles the
order of the references.
To make this really useful, it would help to have a message-id
permanently attached to replies and comments that are generated by the
web UI as well as ones submitted by email. Jesse, would you accept an
improved threading patch that did that?
yes I saw this, just after (successful testing and sending the patch. I
have now running a version here, which do
a) correct in-reply-to’s depending on if the message is relayed (a
notification for an incoming message) or if it is originated by RT.
b) preserves the order of references (I did not know that MUAs rely on
Already the original patch adds a reference to the message of the first
transaction of a ticket.
As other pointed out, there are some deficiences, I cannot cope with:
A) there may be arbitrary many notifications to one message, which only see
part of the recipients. To have real threading, message ids of all
notifications must be created prior sending any notification.
B) Messages created in the Web do not have any message id. This is not
really bad, since they are never sent by email (only notifications are
sent), but adding a reference to the first transaction fails, if it is a
web created ticket, and so does some threading on them.
I will later this day send my improved patch, so you might to start working
on the new one, or you may start from scratch.