On 1/2/20 9:38 AM, Oswald Buddenhagen wrote:
the message from mbsync is still the same one, right?
make sure there isn't whitespace in that "empty" line and that the
line endings are consistent (imap wants CRLF, but the on-disk storage
might be LF-only, too). use an editor with proper visualization or a
hexdump.
You had it exactly right; there was whitespace on that line.
Fixing this turned out to be harder than I thought. In case somebody
else experiences this and finds this in the archives, let me explain
what I did:
Dovecot keeps track of the size of the message in its uid map file. And
for reasons beyond my understanding, the filenames themselves include
the size. There's a Dovecot script to fix that, but it would only fix
filenames, not the uid map. So to get this to work, I had to:
1.
Shut down dovecot
2.
Move the suspicious messages into a new maildir
3.
Fix their content using vi with :set list
4.
Use the script http://dovecot.org/tools/maildir-size-fix.pl to fix
the filenames
5.
Start up dovecot
6.
Using my mail client, look in the old folder to force Dovecot to update
7.
Look in the new folder
8.
Drag the messages back to the old folder
This is a little ridiculous, but since it's a few dozen messages from
2005, I'm just going to pretend this never happened.
Thanks again for your help and for the great tool, Oswald. I'm very
excited that I might be able to finally stop running my own mailserver!
William
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
