[Users] [Bug 3212] New: When msgnum matches a sub-folder name, fetch fails
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Sun Jun 15 04:14:14 CEST 2014
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3212
Bug ID: 3212
Summary: When msgnum matches a sub-folder name, fetch fails
Classification: Unclassified
Product: Claws Mail
Version: other
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Folders/IMAP
Assignee: users at lists.claws-mail.org
Reporter: jer at gentoo.org
** (claws-mail:9482): WARNING **: [02:47:27] IMAP error on *****: FETCH error
(claws-mail:9482): Claws-Mail-WARNING **: can't fetch message 2011
(claws-mail:9482): Claws-Mail-WARNING **: can't get message file path.
This happened because the message in question resided in an IMAP folder that
contained two sub-folders: 2011 and 2012[1].
And indeed, the other message I failed to retrieve had msgnum = 2012:
** (claws-mail:9482): WARNING **: [02:47:36] IMAP error on *****: FETCH error
(claws-mail:9482): Claws-Mail-WARNING **: can't fetch message 2012
(claws-mail:9482): Claws-Mail-WARNING **: can't get message file path.
After renaming the two offending IMAP folders, the imapcache was able to store
two files named "2011" and "2012" along with the renamed folders.
I think this namespace collision should be fixed by changing the file naming
scheme. Working around the problem by copying the message or renaming the
folder isn't something I'd want to often do, and as you might understand I have
many IMAP folders named after years.
[1] Those are years - I store messages in those that I received in those
years, respectively. I wouldn't think it's unlikely someone names IMAP folders
after the year they received the messages they store in those folders, so I'm
probably not alone.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list