Re: [Mailsync-list] managing damaged headers?

[Bill K. <wke...@ho...>]

>>Hi all,  (is anyone around?)
>According to the mailing list archive the last message was 4 days before...

Ok, ya got me.  I'm a bit rushed and things aren't going smoothly with this 
transition.

>Try the debug and verbose switches of mailsync (mailsync --help), they 
>should give you quite some information about which message if being 
>processed.

Yes, that has helped.  It at least shows the message subjects (-m and -M) 
and that helped me narrow down where the main problems were.  I pulled up a 
hex editor on one of the mailboxes and found some hex chars where they 
didn't belong.  Lots of them, mainly clogged up the 2nd line of many 
messages.

grep -P '\x13\x42'

To see a list of them I used:

grep -l -R -P '\x13\x42' ~/mail

>I'd try some half-automated search/replace such as load the mailbox into a 
>text editor, find out what's wrong and let the editor half-automatically 
>fix it (I'd use vim's "record/replay" functionality to achieve that)

Yep, some quick redirection into tmp files, just to have a safe fallback 
without resorting to the tar backups, and a good number of the seriously bad 
headers are fixed.  Still having some import woes but at least more of the 
mail is making it across.

>Even harder than mailsync's? /me is astonished

Gotta love it.  The c-client docs for remote mail folders is really a pain 
in the ass to figure out.  Bits and pieces of it's syntax are spread all 
over the docs and source.  I've managed to get most of it figured out 
though.

Thanks!

-Bill Kearney