Your message dated Tue, 18 Nov 2008 20:16:23 -0600
with message-id <[EMAIL PROTECTED]>
and subject line FW: Mail delivery failed: returning message to sender
has caused the Debian Bug report #506073,
regarding offlineimap: Invalid date crashes OfflineIMAP
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
506073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506073
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
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



--- End Message ---
--- Begin Message ---
------ This is a copy of the message, including all the headers. ------

Date: Tue, 18 Nov 2008 19:44:09 -0600
From: John Goerzen <[EMAIL PROTECTED]>
To: "Chris D. Sloan" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: Bug#506073: offlineimap: Invalid date crashes OfflineIMAP


Chris D. Sloan wrote:
> Doesn't this mean that any spammer can DOS offlineIMAP just by sending
> an invalid date?  Or am I missing something?

We're not talking about the Date: header in a mail.  This is an internal
date stored by your IMAP server.  Usually it is a timestamp of when the
IMAP server first processed a message, though if memory serves, this is
a bit vague.

Actually, indeed it is both vague and specific, heh.  from RFC3501:

2.3.3.  Internal Date Message Attribute

   The internal date and time of the message on the server.  This
   is not the date and time in the [RFC-2822] header, but rather a
   date and time which reflects when the message was received.  In
   the case of messages delivered via [SMTP], this SHOULD be the
   date and time of final delivery of the message as defined by
   [SMTP].  In the case of messages delivered by the IMAP4rev1 COPY
   command, this SHOULD be the internal date and time of the source
   message.  In the case of messages delivered by the IMAP4rev1
   APPEND command, this SHOULD be the date and time as specified in
   the APPEND command description.  All other cases are
   implementation defined.

I don't recall seeing this problem before.  If you are seeing it a lot,
and not just caused by a misconfiguration on the mail server, I suppose
it would warrant a workaround.

-- John


----- End forwarded message -----

-- 
John Goerzen
Author, Foundations of Python Network Programming
http://www.amazon.com/exec/obidos/tg/detail/-/1590593715


--- End Message ---

Reply via email to