Package: offlineimap
Version: 6.0.0
Severity: important

OfflineIMAP crashes with the following messages:

        Syncing junk: IMAP -> Maildir
        Thread 'Folder sync account[junk]' terminated with exception:
        Traceback (most recent call last):
          File "/var/lib/python-support/python2.5/offlineimap/threadutil.py", 
line 153, in run
            Thread.run(self)
          File "/usr/lib/python2.5/threading.py", line 446, in run
            self.__target(*self.__args, **self.__kwargs)
          File "/var/lib/python-support/python2.5/offlineimap/accounts.py", 
line 229, in syncfolder
            remotefolder.cachemessagelist()
          File "/var/lib/python-support/python2.5/offlineimap/folder/IMAP.py", 
line 153, in cachemessagelist
            rtime = imaplibutil.Internaldate2epoch(messagestr)
          File "/var/lib/python-support/python2.5/offlineimap/imaplibutil.py", 
line 206, in Internaldate2epoch
            return time.mktime(tt)
        OverflowError: mktime argument out of range
        
        Last 50 debug messages logged for Folder sync sx[junk] prior to 
exception:

followed by a whole bunch of messages (I presume 50) which appear to
be in groups of four.  The last grouping is:

        imap: imapsplit() called with input: FLAGS (\Seen) UID 4799
        INTERNALDATE "19-Jan-2038 11:14:07 -0800"
        imap: imapsplit() returning: ['FLAGS', '(\\Seen)', 'UID',
        '4799', 'INTERNALDATE', '"19-Jan-2038 11:14:07 -0800"']
        imap: options2hash called with input: ['FLAGS', '(\\Seen)',
        'UID', '4799', 'INTERNALDATE', '"19-Jan-2038 11:14:07 -0800"']
        imap: options2hash returning: {'INTERNALDATE': '"19-Jan-2038
        11:14:07 -0800"', 'FLAGS': '(\\Seen)', 'UID': '4799'}


This first manifested after a system upgrade from stable, so I believe
that the version of both OfflineIMAP and python have changed.  If I
understand the messages, it is crashing because a message on the IMAP
server (an exchange server) has an invalid date.

The first time I hit this message, it was for a local message which
did, in fact, have an invalid date, so I removed that file.  Then it
hit another file, so I nuked all the files and metadata and did a full
redownload.  This worked swimmingly for thousands of messages until
the message above.  The local copy of that folder is empty, so I know
it's an issue with the message on the server, not in the local file
system.  I tried to use a different IMAP client to find the message in
question, but none of the visible date fields seemed to correspond.  I
suspect that means that it's server meta data or something, but I
don't really know.




-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'stable'), (700, 'unstable'), (500, 
'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=POSIX (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages offlineimap depends on:
ii  python                        2.5.2-3    An interactive high-level object-o
ii  python-support                0.8.4      automated rebuilding support for P

offlineimap recommends no packages.

Versions of packages offlineimap suggests:
pn  python-kerberos               <none>     (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to