Net::IMAP thread deadlock bug about larch HOT 5 CLOSED

Please ignore this bugreport.
The error occured while the source server was slow to respond, today I don't have this error.

from larch.

Unfortunately, this is a bug in Ruby's Net::IMAP library that Larch has no control over. Glad to hear you eventually got past it, though.

from larch.

FYI I didn't really give a complete picture regarding the error, I'm sorry about that.

Here's what happened:

• I ran the migration using larch
• it failed/stopped with the errormessage in the above bug report
• I re-ran larch 3 times, and it always stopped at the same message (slightly different debug output afaic remember)
• I used Thunderbird to manually, via IMAP, move the last message in the debug output
• Manual move worked
• Re-ran, and now the migration ran to completion
  (emails: 16436, folders: 354, mailbox transferred/size: 928MB)

The single message that blocked the migration, had a weird (dingbat looking) character in the subject.

from larch.

Yep. If Net::IMAP's response parser gets into an unexpected state due to a malformed or otherwise unanticipated response, it can cause a deadlock like this. Skipping the offending message or moving it out of the way with another mail client can get things moving again.

from larch.

Is it possible to scan the source mailbox beforehand, for these kinds of malformed messages, i.e. can we detect them somehow ?

The previous migration took 8 hours, and I would like to not monitor it, rather manually move malformed emails beforehand.

from larch.