Bug 710701 - Unknown IMAP4 command: 'selectedfolder'
Summary: Unknown IMAP4 command: 'selectedfolder'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: offlineimap
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Höger
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-04 06:09 UTC by Dr. Tilmann Bubeck
Modified: 2013-02-13 12:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 12:59:12 UTC
Type: ---


Attachments (Terms of Use)
patch to fix problem based upong offlineimap 6.3.3 (427 bytes, patch)
2011-06-04 06:09 UTC, Dr. Tilmann Bubeck
no flags Details | Diff

Description Dr. Tilmann Bubeck 2011-06-04 06:09:04 UTC
Created attachment 502954 [details]
patch to fix problem based upong offlineimap 6.3.3

Description of problem:
The following error occurs "Unknown IMAP4 command: 'selectedfolder'" when running offlineimap.


Version-Release number of selected component (if applicable):
offlineimap-6.3.3-1.fc15.noarch
dovecot-2.0.13-1.fc15.i686

How reproducible:
Every time I synchronize my mailbox, but probably not for all users.

Steps to Reproduce:
1. start offlineimap against my mailbox or a simliar one.
2. see error
3.
  
Actual results:
Unknown IMAP4 command: 'selectedfolder'

Expected results:
no error

Additional info:
A fix is available at https://github.com/marvinthepa/offlineimap/commit/9e1ebcc06d982d6cfaf595bef809d5124da00ac4
which I ported to the new offlineimap version and attached. For me it fixes the problem.

Comment 1 Mark Wielaard 2011-06-29 21:03:25 UTC
Thanks, that patch works perfectly.

Comment 2 Anton Arapov 2011-10-17 08:20:07 UTC
Same issue in F16. Patch fixed problem for me.

Comment 3 Mark Wielaard 2011-11-13 15:06:23 UTC
Still an issue with offlineimap-6.3.3-1.fc16.noarch. Same workaround from comment #1 works.

Comment 4 Christoph Höger 2011-11-13 20:32:02 UTC
Could you please try the latest update?

Comment 5 Mark Wielaard 2011-11-14 10:45:26 UTC
Tried yum --enablerepo=updates-testing install offlineimap to install offlineimap-6.3.4-1.fc16.noarch which worked out of the box without any need for tweaking. Thanks!

Comment 6 Anton Arapov 2011-11-14 13:49:21 UTC
Works for me.

Comment 7 Fedora End Of Life 2013-01-16 12:38:33 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-13 12:59:15 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.