empty body and "has incomplete header"

[<me...@re...>]

Hello list,

I have migrated from offlineimap to mbsync and my experiences have been
good so far. Ran into a hang after suspend/resume, probably due to a
longish timeout. Anyway, messages with empty bodies seem to offend
mbsync as it keeps complaining about "incomplete header". Mindlessly
commenting out a couple of lines makes it download those messages.
Someone who actually understands what the code does (inspite of the
cryptic variable names) may be able to say what gets broken by such a
rough treatment.

diff --git a/src/sync.c b/src/sync.c
index 5633fbf..d918e13 100644
--- a/src/sync.c
+++ b/src/sync.c
@@ -336,12 +336,12 @@ msg_fetched( int sts, void *aux )
 						goto nloop;
 					}
 				}
-				/* invalid message */
-				warn( "Warning: message %d from %s has incomplete header.\n",
-				      vars->msg->uid, str_ms[1-t] );
-				free( fmap );
-				vars->cb( SYNC_NOGOOD, 0, vars );
-				return;
+				/* /\* invalid message *\/ */
+				/* warn( "Warning: message %d from %s has incomplete header.\n", */
+				/*       vars->msg->uid, str_ms[1-t] ); */
+				/* free( fmap ); */
+				/* vars->cb( SYNC_NOGOOD, 0, vars ); */
+				/* return; */
 			  oke:
 				extra += 8 + TUIDL + 1 + (tcr && (!scr || hcrs));
 			}

Cheers,
Gabor Melis

[I'm not subscribed to the list, please keep me among the recipients.]