I'm using Maildir. mutt -R against folder A makes no mods as expected. mutt -f against folder A moves new msgs to cur with no mods as expected. But mutt -f against A, operation of tagging messages and 'C'opying them to some other folder B causes Content-Length headers to be added to each message.
mutt didn't need that header to operate well in the original folder. In general, can't think of any reason to modify any Maildir message on disk and view this as tainting the msgs with unecessary and un-asked-for mods. And it breaks external indexes of security/archive crypto hashes. I'm not referring to the msg filename (maildir spec) or its location (as instructed), just the content of the msg file itself. And it also appears to be lying by preserving the msg file modification time when it adds this header. [1] Why does mutt do this? What else is being surreptitiously modified during mutt operation? I'd like to ticket it. [1] Of course it should preserve the msg file mod time when merely copying or moving messages.
