Re: Threads and &
Hi,
* Kyle Wheeler wrote:
> That's what I figured. I suppose another way of putting it is: since
> it's entirely possible to receive a message that does not have a
> Message-ID header (e.g. an email server that obeys RFCs 821 and 2821
> but not 5821... particularly since only 821 has received the STD
> designation, this is something that should be planned for), the
> question becomes: what should mutt do when asked to link one such
> message to another? Even if the answer is not "alter the parent
> message to give it an ID" (because that's too hard, or whatever), the
> answer (at least in the short term) should probably include "display
> an appropriate and intelligent error message". Mutt should most
> certainly NOT "pretend" to link the messages, only to have them
> unlinked again the next time the mailbox is opened.
I think I'll go with the warning for now. This use-case IMHO is so rare
that we simply issue a warning and can leave it up to the user to fix
it. The manual has a section on thread editing, so documentation for
this can be added, too.
Rocco