On Sat, 16 Nov 2019 at 16:25:15 +0100, Jonas Smedegaard wrote: > jonas@auryn:~$ interimap --config debian --repair --debug INBOX.olpc 2>&1 | > grep -Fw 97 > […] > local(INBOX.olpc): WARNING: No match for modified remote UID 97. Downloading > again. > remote(INBOX.olpc): C: 000004 UID FETCH 97 (MODSEQ FLAGS INTERNALDATE > BODY.PEEK[] ENVELOPE)
I'm suprised grep didn't match the server response for that command. Do
you have anything at all between
remote(INBOX.olpc): C: 000004 UID FETCH 97 (MODSEQ FLAGS INTERNALDATE
BODY.PEEK[] ENVELOPE)
and
remote(INBOX.olpc): S: 000004 OK Fetch completed
> UID FETCH 97 BODY.PEEK[]
> * 97 FETCH (BODY[] {6520}
> […])
> UID OK Fetch completed (0.132 + 0.000 + 0.131 secs).
Oh my bad, seems I typoed the IMAP command I gave you; that message is
sequence number #97 not UID 97. It's a ‘FETCH’ command with tag ‘UID’,
while I wanted to send an ‘UID FETCH’ command with tag $foo, like what's
being found in the debug output above.
Please try again prefixing the command with ‘b ’ (or any other tag):
b UID FETCH 97 BODY.PEEK[]
The server response should be
* $SEQ FETCH (UID 97 BODY[] $BODY)
b OK Fetch completed
Where $SEQ is the sequence number (not necessarily 97) and $BODY is a
literal ‘{3}\r\nfoo’, quoted string ‘"bar"’, or NIL. “UID 97” is
required to be present somewhere in the server response.
> Seems like this _isn't_ a zero-length message.
Message with sequence number #97 is likely not be the one we're looking
for. (In your debug output I can see that UID 97 had sequence number
#3396 at the time.)
I appreciate the assistance in debugging. Thanks!
--
Guilhem.
signature.asc
Description: PGP signature
