Re: lost track of X messages / socket error

[Oswald B. <osw...@gm...>]

On Fri, Oct 28, 2022 at 03:32:44PM +0100, Edd Barrett wrote:
>I'm not sure how much context you need. I'm hesitant to post the whole 
>log as
>it contains things about my mailboxes in it.
>
i need the full log. in fact, of two consecutive runs, as this is an 
inter-run problem. you can limit it on the command line to the affected 
mailbox, and send me the log in private.

>...
>Oct 28 15:17:08 MTE5NTI0NiAwMDAwMCBuIAowMDIxMTk1Nzk4IDAwMDAwIG4gCjAwMjExOTYxNjIgMDAwMDAg
>Oct 28 15:17:08 biAKdHJhaWxlcgo8PCAvU2l6ZSAzMTYgL1Jvb3QgMTkyIDAgUiAvSW5mbyAzMTUgMCBSIC9J
>Oct 28 15:17:08 RCBbIDwwM2RhNGFhMDQ3YmU4NWNkOTgzZDE1ODg3OGJmNDY4ZT4KPDAzZGE0YWEwNDdiZTg1
>Oct 28 15:17:08 Y2Q5ODNkMTU4ODc4YmY0NjhlPiBdID4+CnN0YXJ0eHJlZgoyMTE5NjM5NAolJUVPRgo=
>Oct 28 15:17:08 
>Oct 28 15:17:08 --ybR7w8Lo12h+exFG--
>Oct 28 15:17:08 >>>>>>>>>
>Oct 28 15:17:09 (1 in progress) >>> 10 UID FETCH 110231 (BODY.PEEK[])
>Oct 28 15:17:36 (2 in progress) >>> 11 UID FETCH 110283 (BODY.PEEK[])
>Oct 28 15:17:36 (3 in progress) >>> 12 UID FETCH 110284 (BODY.PEEK[])
>Oct 28 15:17:56 Socket error on imap.gmail.com (74.125.140.109:993): timeout.
>```
>
that may mean that less data is uploaded than the server expects (which 
is specified in {braces} in the APPEND command).
to check this, you need to verify the size of the sent block (the part 
between the >>>>>>>>> lines). the output must be raw (redirected, not 
copied from the terminal), and you must use a tool that can work with 
the raw file without corrupting it - probably a hex editor like okteta 
would be best.
if the hypothesis holds up, the number of missing bytes should be 
compared with the number of lines in the block.