Ever since updating to isync-1.5.0, my Yahoo! email account no longer syncs the Inbox and I get this error: IMAP error: cannot use unqualified 'Inbox'. Did you mean INBOX?Error: channel yahoo: far side box Inbox cannot be opened. Reproducible: Always Steps to Reproduce: .mbsyncrc: IMAPAccount yahoo Host imap.mail.yahoo.com User username SSLType IMAPS CertificateFile /etc/ssl/certs/ca-bundle.crt PipelineDepth 5 Timeout 300 IMAPStore yahoo-remote Account yahoo MaildirStore yahoo-local Path ~/Mail/yahoo/ Inbox ~/Mail/yahoo/Inbox SubFolders Verbatim Channel yahoo Master :yahoo-remote: Slave :yahoo-local: Patterns * $ mbsync -V yahoo:Inbox Actual Results: $ mbsync -V -l yahoo | grep Inbox Inbox $ mbsync -V yahoo:Inbox Reading configuration file /home/username/.mbsyncrc Notice: SSLType is deprecated. Use TLSType instead. Notice: SSLVersions is deprecated. Use TLSVersions instead. Notice: Master/Slave are deprecated; use Far/Near instead. Channel yahoo Opening far side store yahoo-remote... Resolving imap.mail.yahoo.com... Opening near side store yahoo-local... Connecting to imap.mail.yahoo.com (67.195.176.151:993)... Connection is now encrypted Logging in... Authenticating with SASL mechanism PLAIN... Opening far side box Inbox... IMAP error: cannot use unqualified 'Inbox'. Did you mean INBOX?Opening near side box Inbox... Warning: channel yahoo: far side box Inbox cannot be opened and near side box Inbox is not empty. Processed 1 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. Expected Results: Inbox should synchronize.
1.5.0 is in testing. Please comment on the update: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1507e7def5
isync-1.5.0-1.fc39 x86_64 is broken. isync-1.4.4-6.fc39.x86_64 works correctly. Comments added to all fedora version updates.
Thanks Hmm, comments in https://bugzilla.redhat.com/show_bug.cgi?id=2302132 suggest that 1.5.0 fixes issues.
There is a recent upstream bug (https://sourceforge.net/p/isync/bugs/78/). This issue could be related.
I haven't tried applying this patch yet, but it looks like it may fix my issue and it was committed after 1.5.0 was tagged for release: https://www.mail-archive.com/isync-devel@lists.sourceforge.net/msg04319.html
There are several fixes that were committed right after 1.5.0 was released. I tested applying "fix-IMAP-INBOX-case-normalization" alone and it fixes my issue. I also tested applying all of these which seem like good fixes to have. I'll prepare a pull request. https://sourceforge.net/p/isync/isync/ci/8c781d4fb55f1dae47dab0388e7e3d40170b7d21/log/?path= 0001-fix-initial-build-from-git.patch 0002-fix-IMAP-INBOX-case-normalization.patch 0003-add-missing-trailing-newlines-in-error-calls.patch 0004-fix-typos.patch 0005-improve-reporting-of-failure-to-open-previously-pres.patch 0006-fix-implicit-listing-of-Maildir-INBOX-under-Path.patch
FEDORA-2024-e5d7e52985 (isync-1.5.0-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-e5d7e52985
FEDORA-2024-e5d7e52985 (isync-1.5.0-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-bfb8f42d46 (isync-1.5.0-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-bfb8f42d46
FEDORA-2024-bfb8f42d46 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-bfb8f42d46` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-bfb8f42d46 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
isync-1.5.0-2 has been working well for me. Can you please push this update to F39 and F40 as well? Thanks.
FEDORA-2024-bfb8f42d46 (isync-1.5.0-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.