Your message dated Mon, 3 Mar 2008 01:22:19 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#217906: Follow up on Debian #217906
has caused the Debian Bug report #217906,
regarding offlineimap: The return of the empty uid!
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.)
--
217906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=217906
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: offlineimap
Version: 4.0.1
Severity: important
I just recently upgraded to 4.0.1 and have seen this problem a few
times; usually, IIRC, it resolves itself, but this time, it's not
going away. Fortunately, "twisted-python" comes after "inbox", and i
can still get new messages. :-)
Syncing Mail/twisted-python: IMAP -> Maildir
Copy message -1 Maildir[twisted-python] -> IMAP[Mail/twisted-python],
LocalStatus[twisted-python]
Copy message -7 Maildir[twisted-python] -> IMAP[Mail/twisted-python],
LocalStatus[twisted-python]
Copy message -6 Maildir[twisted-python] -> IMAP[Mail/twisted-python],
LocalStatus[twisted-python]
Thread 'New msg sync from twisted-python' terminated with exception:
Traceback (most recent call last):
File "/usr/lib/python2.2/site-packages/offlineimap/threadutil.py", line 153,
in run
Thread.run(self)
File "/usr/lib/python2.2/threading.py", line 402, in run
apply(self.__target, self.__args, self.__kwargs)
File "/usr/lib/python2.2/site-packages/offlineimap/folder/Base.py", line 207,
in syncmessagesto_neguid_msg
successuid = tryappend.savemessage(uid, message, flags)
File "/usr/lib/python2.2/site-packages/offlineimap/folder/IMAP.py", line 231,
in savemessage
headervalue)
File "/usr/lib/python2.2/site-packages/offlineimap/folder/IMAP.py", line 167,
in savemessage_searchforheader
return long(matchinguids[0])
ValueError: invalid literal for long():
... a lot of debug info about the uploading of these messages,
followed by (this is my guess at what's relevant):
imap: savemessage: new content length is 10556
imap: savemessage: first attempt to get new UID
imap: savemessage_searchforheader called for
X-OfflineIMAP-x1362141038-7261646978746d-4d61696c2f747769737465642d707974686f6e:
1067309561-0633700411492
imap: savemessage_searchforheader got initial matchinguids: ''
imap: savemessage_searchforheader: matchinguids now ['']
imap: savemessage: first attempt to get new UID failed. Going to run a NOOP
and try again.
imap: savemessage_searchforheader called for
X-OfflineIMAP-x1362141038-7261646978746d-4d61696c2f747769737465642d707974686f6e:
1067309561-0633700411492
imap: savemessage_searchforheader got initial matchinguids: ''
imap: savemessage_searchforheader: matchinguids now ['']
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux toshi 2.4.20-1-686 #1 Sat Mar 22 13:16:21 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages offlineimap depends on:
ii python2.2 2.2.3-2.1 An interactive high-level object-o
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Mar 03, 2008 at 10:39:55AM -0500, Christopher Armstrong wrote:
> On Mon, Mar 3, 2008 at 1:05 AM, John Goerzen <[EMAIL PROTECTED]> wrote:
> > tags 217906 unreproducible moreinfo
> > thanks
> >
> > Hi Christopher,
>
> Hi John! been a while :-)
Yeah :-) Sorry about that...
> > I'm following up on some old OfflineIMAP bugs. I found your bug
> > report at #217906 that I had trouble reproducing. Are you still seing
> > that, and if so, with what OfflineIMAP version?
>
> I'm not still seeing it, but then, I'm not using offlineimap any more.
> I can't remember if I ever fixed that particular bug - I may have
> actually switched to a different IMAP server in the end. Sorry!
OK. In that case, I'll go ahead and mark this closed.
-- John
--- End Message ---
