imapsync / imapsync/imapsync

"Could not fetch_hash 9 msgs: 17 BAD Command Argument Error. 11" from Office 365 source

Open
#239 6 comments 0 reactions 1 assignee View on GitHub

@gilleslamiral is already working on this.

Since Oct 13, 2020.

Argument Error. 11 Labels Office365
Dominant language
Shell
Stars
4.2k
Forks
531
PR merge metrics
No merged PRs in 30d

Description

Hi, first of all many thanks for this great piece of software!
I'm trying to copy from Office365 to Gmail, but I have an issue on source mailbox: on every folder i get

Could not fetch_hash xxx msgs: xxx BAD Command Argument Error. 11

I already tried --maxsize and --maxlinelength with no luck.
This is the debug log (trying to sync only 1 folder for debug)

Here is imapsync 1.998 on host ip-10-10-54-3, a linux system with 0.1/0.5 free GiB of RAM
with Perl 5.16.3 and Mail::IMAPClient 3.34
Transfer started at Sat Oct 10 00:48:34 2020

Command line used, run by /usr/bin/perl:
/root/imapsync --office1 ...  --synclabels --resynclabels 
...
found data between fetch headers: 16 OK FETCH completed.
Host1: parsing headers of folder [Archivio] took 0.181915044784546 s
Host1: getting flags idate and sizes of folder [Archivio]
Sending: 17 UID FETCH 7:13,15:16 (FLAGS INTERNALDATE RFC822.SIZE X-GM-LABELS)
Sent 70 bytes
Read: 	17 BAD Command Argument Error. 11
...
Host1: folder Archivio : Could not fetch_hash 9 msgs: 17 BAD Command Argument Error. 11
...
This imapsync is up to date. ( local 1.998 >= official 1.977 )( Use --noreleasecheck to avoid this release check. )
Homepage: https://imapsync.lamiral.info/
++++ Listing 1 errors encountered during the sync ( avoid this listing with --noerrorsdump ).
Err 1/1: Host1: folder Archivio : Could not fetch_hash 9 msgs: 17 BAD Command Argument Error. 11
The most frequent error is ERR_UNCLASSIFIED

Many many thanks
Michele

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.