in case of error, isync tries to create already existing boxes
mailbox synchronizer
Brought to you by:
ossi
It can't recognize remote folder already exist
▶ mbsync -a
Notice: SSLType is deprecated. Use TLSType instead.
IMAP command 'CREATE "INBOX"' returned an error: CREATE Folder exist
IMAP command 'CREATE "&V4NXPpCuTvY-"' returned an error: CREATE Folder exist
IMAP command 'CREATE "&XfJSIJZk-"' returned an error: CREATE Folder exist
IMAP command 'CREATE "&XfJT0ZAB-"' returned an error: CREATE Folder exist
IMAP command 'CREATE "&dcVr0mWHTvZZOQ-"' returned an error: CREATE Folder exist
IMAP command 'CREATE "&g0l6P3ux-"' returned an error: CREATE Folder exist
Processed 6 box(es) in 1 channel(s),
pulled 0 new message(s) and 0 flag update(s),
expunged 0 message(s) from near side,
pushed 0 new message(s) and 0 flag update(s),
expunged 0 message(s) from far side.
▶ ls
病毒文件夹 草稿箱 垃圾邮件 已发送 已删除 INBOX
here is my configuration
IMAPStore wanshiwen@yeah.net-remote
Host imap.yeah.net
Port 993
User wanshiwen@yeah.net
PassCmd "pass wanshiwen@yeah.net"
AuthMechs LOGIN
SSLType IMAPS
CertificateFile /etc/ssl/certs/ca-certificates.crt
MaildirStore wanshiwen@yeah.net-local
Subfolders Verbatim
Path /home/ploki/.local/share/mail/wanshiwen@yeah.net/
Inbox /home/ploki/.local/share/mail/wanshiwen@yeah.net/INBOX
Channel wanshiwen@yeah.net
Expunge Both
Far :wanshiwen@yeah.net-remote:
Near :wanshiwen@yeah.net-local:
Patterns * !"[Gmail]/All Mail"
Create Both
SyncState *
MaxMessages 0
ExpireUnread no
please attach (or mail me) a log from
mbsync -a -D
.I find this is the problem of the mail service provider, sorry for waste your time.
yeah, looks like it. but on the upside, you found a real bug in the error handling: isync should not try to create the boxes.
Diff:
if you can still provoke the server problem, you may give the attached patch a try to see whether it improves the error handling.
After
git apply 0001-don-t-try-to-create-already-existing-boxes.patch
ine70c300f7446ba6ec1259f459a0f0e1d2d592ed9
, I try tombsync -aD
, thenthanks for testing. this looks about right.
The same problem exists here. #73
“NO SELECT Unsafe Login. Please contact kefu@188.com for help”
fixed in master in commit 84194a7a.