On Sat, Jul 13, 2019 at 03:11:39PM +0200, Oswald Buddenhagen wrote:
On Fri, Jul 12, 2019 at 07:44:36AM -0400, synflower--- via isync-devel wrote:
M: * 56 EXISTS
M: >>> 17 UID FETCH * (UID)
M: 17 OK UID FETCH done
oh, interesting, this has the same trigger as
https://sourceforge.net/p/isync/bugs/48/
please reveal the imap greeting line (initial server response) from the
log, and the actual server dns if it is a custom server implementation
and not internal.
that the slave mailbox is messed up due to this is definitely a bug in
mbsync; i'll have to investigate it properly.
I don't understand what you mean by "actual server DNS if it is a custom
server implementation and not internal."
It may be useful to note that the issue going from "intermittent and
resolvable" to "permanent and not resolvable" coincided with the mail
provider being taken over / changing their name / something or other (I
don't know detais).
Here is the IMAP greeting section:
Connection is now encrypted
M: * OK [CAPABILITY IMAP4rev1 ID LITERAL+] IMAP4rev1 MYHOST Ready
Logging in...
M: >>> 1 LOGIN <user> <pass>
M: 1 OK [CAPABILITY IMAP4rev1 ID LITERAL+ IDLE QUOTA NAMESPACE SORT UIDPLUS
UNSELECT] Welcome myacco...@myhost.com
M: >>> 2 NAMESPACE^M
M: * NAMESPACE (("" "/")) NIL NIL
M: 2 OK NAMESPACE done
M: [ 1] Callback enter connect_store, sts=0
pattern '*' (effective '*'): Path, no INBOX
M: [ 4] Enter list_store, flags=2
M: >>> 3 LIST "" "*"^M
M: [ 4] Leave list_store
M: [ 1] Callback leave connect_store
M: * LIST () "/" "inbox"
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
