When adding a new mailbox from an existing MH folder, Claws does not seem to take heed of existing .mh_sequences files. All the messages in the folder show up as new. if one visits the folder in Claws, then the "unseen" sequence is set to match what Claws was showing. I haven't tried yet replying to a message in such a folder, but I surmise I'll see the same behavior: Existing sequence completely ignored, status generated within Claws reflected in .mh_sequences later. This makes porting one's mail from another client harder than it could be. On a related note, it could probably be useful to read these sequences on startup, to allow scripts and other tools to change message states, but that may be more dangerous and seems of less immediate value.
Created attachment 1811 [details] A new import script from KMail to Claws, preserving status The attached km2cl.py script is an improvement over the existing kmail-mailbox2claws-mail.pl -- it generates also the .mh_sequences and .claws_mark files which hold the unread and replied flags for the messages in the mailboxes. I'm not sure if there are standards here about how much output these scripts should give and how they should behave. This script makes progress reports as it chugs along. If there are standards, I'll happily change it to oblige.