On Wed, Jan 01, 2020 at 01:57:14AM +0100, Oswald Buddenhagen wrote:
On Tue, Dec 31, 2019 at 03:09:40PM -0600, Peter John Hartman wrote:I can't see anything with -D on that screams at me. Any help towards debugging this would be great. Thanks in advance,mbsync won't try to propagate messages it has already seen, so you'd need to start out with a fresh replica to see anything useful in the debug log.(well, you can also hack the sync state files, zeroing out MaxPulledUid - that shouldn't do anything bad, but if it doesn't work, the log won't be exactly representative, either.)
Thanks for the quick reply. I tried to 0 it out, and get a warning on message UID 35711. I tried deleting the whole thing and re-syncing it and I get the exact same thing (about 12,000 messages on server not sync'd, no obvious warning). Quick question (a bit naive, so I apologise in advance): How do I determine which message on the server (GMAIL in this case) corresponds to message UID 35711?
In any case, a touch stumped. Will keep digging. The oddity is that offlineimap grabbed all the messages, but mbsync somehow fails to grab about 12,000 messages.
Thanks again, and thanks again in advance
signature.asc
Description: PGP signature
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
