Package: offlineimap
Version: 4.0.14
Severity: normal
Hello.
Today I got following frmo offlineimap:
Thread 'Copy message 19532 from INBOX.Junk' terminated with exception:
Traceback (most recent call last):
File "/var/lib/python-support/python2.4/offlineimap/threadutil.py",
line 153, in run
Thread.run(self)
File "threading.py", line 422, in run
self.__target(*self.__args, **self.__kwargs)
File "/var/lib/python-support/python2.4/offlineimap/folder/Base.py",
line 276, in copymessageto
newuid = object.savemessage(uid, message, flags)
File
"/var/lib/python-support/python2.4/offlineimap/folder/UIDMaps.py", line
156, in savemessage
newluid = self._mb.savemessage(self, -1, content, flags)
File "/var/lib/python-support/python2.4/offlineimap/folder/IMAP.py",
line 228, in savemessage
date, content)[0] == 'OK')
AssertionError
I've tried to debug this a little and found that this bug is caused by
imap server refusing invalid date:
imap: 58:17.22 > DGBA29 APPEND INBOX.Junk () "31-Nov-2006 10:53:17
+0300" {5048}
imap: 58:17.22 < DGBA29 NO Error in IMAP command received by server.
After manually removing several spam messages that claimed to be written on
Nov 31, this error disappeared.
I consider this to be bug on offlineimap. Since imap server may refuse
invalid date (I use courier imap), offlineimap should sanitize it (e.g.
replace Nov 31 by Dec 1).
Btw, #390406 may be caused by the same issue.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-1-k7
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages offlineimap depends on:
ii python 2.4.3-11 An interactive high-level object-o
ii python-support 0.5.4 automated rebuilding support for p
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]