Server responded with 'NO'
Sebastian at SSpaeth.de
Mon Aug 15 12:09:13 BST 2011
On Mon, 15 Aug 2011 06:48:45 -0400, Dave Abrahams <dave at boostpro.com> wrote:
> on Mon Aug 15 2011, Sebastian Spaeth <Sebastian-AT-SSpaeth.de> wrote:
> > On Sun, 14 Aug 2011 22:29:25 -0400, Dave Abrahams <dave at boostpro.com> wrote:
> >> --8<---------------cut here---------------start------------->8---
> >> imap.gmail.com handler: DEBUG[imap]: 15:52.46 imap.gmail.com handler NO response: Some messages could not be FETCHed (Failure)
> >> Copy message 71049 from [Gmail]/All Mail: WARNING: ERROR attempting to copy message 71049 for account BoostPro:Traceback (most recent call last):
> >> File "/Library/Python/2.6/site-packages/offlineimap/folder/Base.py", line 250, in copymessageto
> >> message = self.getmessage(uid)
> >> File "/Library/Python/2.6/site-packages/offlineimap/folder/IMAP.py", line 215, in getmessage
> >> raise OfflineImapError(reason, severity)
> >> OfflineImapError: IMAP server 'BoostProRemote' responded with 'NO' to fetching message UID '71049'
> >> --8<---------------cut here---------------end--------------->8---
> >> Oddly, when I run with imap debugging logged to a file, offlineimap
> >> continues after the error, but if I simply invoke "offlineimap," this
> >> failure causes offlineimap to stop/exit/crash.
> > Thanks for the log. You get a "NO Some messages could not be fetched"
> > From the Gmail server, which is a mysterious message on their end that
> > they refuse to send you one of your messages. Not much we can do about
> > this.
> > But our behavior is buggy and your log and report helped me to find some
> > bugs on our end. Skipping single message failures worked in
> > single-thread mode (which is turned on using debug) but not in the
> > normal multi-threaded mode.
> > This is because I was catching exceptions of newly started threads, but
> > python doesn't bubble exceptions up to the parent thread, it immediately
> > aborts! The following patches fix this behavior and simply skip the
> > failing message (logging an error).
> > I recommend applying those patches as this makes skipping messages work
> > correctly.
> Thanks for your work! I tried applying these to master, but:
> $ git --no-pager am /tmp/m1
> Applying: Fix error handling in folder.Base.copymessageto()
> /Users/dave/src/offlineimap/.git/rebase-apply/patch:78: trailing whitespace.
> error: patch failed: offlineimap/folder/Base.py:17
> error: offlineimap/folder/Base.py: patch does not apply
> Patch failed at 0001 Fix error handling in folder.Base.copymessageto()
> When you have resolved this problem run "git am --resolved".
> If you would prefer to skip this patch, instead run "git am --skip".
> To restore the original branch and stop patching run "git am --abort".
> git exited abnormally with code 1.
Uhh, yes. I based those patches on the next branch, so they should apply
to this one.
You can get the branch as branch pending/FixMESSAGEthrowing at
git://github.com/spaetz/offlineimap.git if you want those already
applied. I hope it will go into the mainline next branch soon though.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the OfflineIMAP-project