[Users] [Bug 3290] New: Cache problems with folders whose names are purely numeric

[noreply at thewildbeast.co.uk]

http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3290

            Bug ID: 3290
           Summary: Cache problems with folders whose names are purely
                    numeric
    Classification: Unclassified
           Product: Claws Mail
           Version: 3.9.3
          Hardware: PC
               URL: https://bugs.debian.org/540785
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Folders/IMAP
          Assignee: users at lists.claws-mail.org
          Reporter: mones at users.sourceforge.net

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,

-- 
You are receiving this mail because:
You are the assignee for the bug.