Bug 3290 - Cache problems with folders whose names are purely numeric
Summary: Cache problems with folders whose names are purely numeric
Status: RESOLVED DUPLICATE of bug 3212
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Folders/IMAP (show other bugs)
Version: 3.9.3
Hardware: PC Linux
: P3 normal
Assignee: users
URL: https://bugs.debian.org/540785
Depends on:
Blocks:
 
Reported: 2014-09-25 12:24 UTC by Ricardo Mones
Modified: 2014-09-25 20:07 UTC (History)
0 users

See Also:


Attachments

Description Ricardo Mones 2014-09-25 12:24:50 UTC
An old one which has finally got some feedback recently.

Quoting original reporter:
-------
In my IMAP cache, I have lots of mails, whose filenames are just the
UID of the message on the server. On the server, I have split folders to
archive previous years' messages:

  + Bugzilla
     + 2007
     + 2008
     + 2009

This seems to fail with the on-disk IMAP cache, because it can't allow
both a message and a folder called "2009". This causes cache
inconsistency problems, where I can no longer access any mail in the
2009 folder.

Looking at IMAP logs, the server is happy with the transfer, then it
fails to write the file locally, gives up, and displays its usual "this
message is not available" error:

 This message can't be displayed.
 This is probably due to a network error.

 Use 'View Log' in the Tools menu for more information.

The IMAP log window claims:

 ...
 [11:56:07] IMAP4> 14221 SELECT "Bugzilla.2009.M01" 
 [11:56:07] IMAP4< * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) 
 [11:56:07] IMAP4< * OK [PERMANENTFLAGS (\Answered \Flagged \Draft
 \Deleted \Seen \*)]   
 ...
 [11:56:18] IMAP4> 14232 UID FETCH 301 BODY.PEEK[] 
 [11:56:18] IMAP4< [FETCH data - 2617 bytes]
 ** IMAP error on imap.my.company: FETCH error


If I rename the folder to "Y2009" then it works correctly.
-------

Thanks in advance,
Comment 1 Colin Leroy 2014-09-25 20:07:10 UTC
Hi,

I think that's bug #3212, which, incidentally, I fixed it GIT ;)

*** This bug has been marked as a duplicate of bug 3212 ***

Note You need to log in before you can comment on or make changes to this bug.