I'm experencing Message-ID munging problems with the 20060704a-1bpo1 version of crm114 from backports.org. Unfortuntately, I'm experiencing something more serious: rather than merely Message-IDs with a comment added I'm seeing some messages come through with a second Message-Id field added which contains only a comment.
This appears to happen because other programs are generating a field called Message-ID while CRM114 is trying to munge a field called Message-Id. This upsets at least mutt (which looks like it will accept either capitalisation), causing it to think that the Message-ID contains only a comment. The mungmail_add_cache_info() function in unstable looks to be identical, although I have not checked to see if mungmail_add_comment has changed. I feel mutt is being reasonable here: it's being liberal in what it accepts and getting confused because crm114 is being liberal in what it generates. As the bug log notes the problem would be avoided if crm114 were to avoid generating a null message ID but crm114 may also wish to consider trying to munge both upper and lower case variants of the field. Due to the threading problems it causes this bug should probably be of a higher severity and resolved before etch. -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
signature.asc
Description: Digital signature
