Normally, breaking and linking threads is a no-brainer. I do these all of the time, and I am satisfied. I have two (2) simple messages: From helpdesk@xxxxxxxxxxxxxxxxxxxxxx Wed Jan 14 10:31:01 2004 From: Support <helpdesk@xxxxxxxxxxxxxxxxxxxxxx> To: mds@xxxxxxxxxxx Date: Wed, 14 Jan 2004 16:33:00 +0000 Subject: TEST #1 Message-ID: 1073710002-7884@mimetools Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Thank you for your Technical Support Inquiry. From helpdesk@xxxxxxxxxxxxxxxxxxxxxx Fri Jan 16 05:41:32 2004 From: Support <helpdesk@xxxxxxxxxxxxxxxxxxxxxx> To: mds@xxxxxxxxxxx Date: Fri, 16 Jan 2004 11:40:45 +0000 Subject: TEST #2 Message-ID: 1073710002-12669@mimetools Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello Mike , Now, suppose that I want to link TEST #2 to TEST #1. I receive this error, and the link fails: No Message-ID: header available to link thread Clearly, each message contains a Message-ID header, so this message provides me with few clues to establish root cause. Nevertheless, I think that this has something to do with the _format_ of the Message-ID's; but, what are Mutt's requirements in this regard? What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --
Attachment:
signature.asc
Description: Digital signature