Bug 252831

Summary:	Akonadi does not work properly with Domino IMAP server
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Andreas Karrenbauer <andreas.karrenbauer>
Component:	IMAP resource	Assignee:	Christian Mollekopf <chrigi_1>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kdepim-bugs, vkrause
Priority:	NOR	Keywords:	triaged
Version:	1.4.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andreas Karrenbauer 2010-09-30 09:54:27 UTC

Version:           1.4.0 (using Devel) 
OS:                Linux

Modified flags, e.g. such as "seen", are not stored on the server

akonadiconsole reports lots of errors like

AgentBase(akonadi_imap_resource_2): Store failed, server replied: A000130 BAD UID command is invalid in this state 


Reproducible: Always

Steps to Reproduce:
1. Restart Akonadi server with akonadiconsole
2. Run KMail2
3. Messages that have been read are marked as unseen again
4. Click on a message
5. akonadiconsole reports said error message
6. Close KMail2 and goto step 1 always gives the same results

Actual Results:  
Messages flags are not modified on IMAP server (checked with webinterface of the server)

Expected Results:  
Messages are marked as seen on the server

OS: Linux (x86_64) release 2.6.34.7-0.3-default
Compiler: gcc

Comment 1 Kevin Ottens 2010-09-30 10:00:22 UTC

OK, I'll need to see what happens *before* the error hit. So I'd need to see the IMAP traffic happening.

Could you please do something like that in a terminal:
 * export KIMAP_LOGFILE=imap.log
 * akonadictl restart

Then try to change the flags again. It should generate imap.log* files which contain the IMAP traffic so that I can take a peek at what's going wrong.

Thanks in advance.

Comment 2 Andreas Karrenbauer 2010-09-30 12:26:51 UTC

Hi,

is it possible to make this output more fine grained? I've got an other 
(working) IMAP resource which are mixed in the log.

Before I sent the complete log I have to browse it first to check that I don't 
leak confidential information. But I've already discovered a strange sequence:

C: A000033 SELECT "nbox"
S: A000033 NO SELECT failure, cannot select mailbox: Folder not found in IMAP 
name space
C: A000034 UID STORE 6144 FLAGS (\Seen)
S: A000034 BAD UID command is invalid in this state

Obviously the I of Inbox is missing.

Best regards

Andreas

On Thursday 30 September 2010 10:00:26 Kevin Ottens wrote:
> https://bugs.kde.org/show_bug.cgi?id=252831
> 
> 
> Kevin Ottens <ervin@kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|                            |WAITINGFORINFO
> 
> 
> 
> 
> --- Comment #1 from Kevin Ottens <ervin kde org>  2010-09-30 10:00:22 ---
> OK, I'll need to see what happens *before* the error hit. So I'd need to see
> the IMAP traffic happening.
> 
> Could you please do something like that in a terminal:
>  * export KIMAP_LOGFILE=imap.log
>  * akonadictl restart
> 
> Then try to change the flags again. It should generate imap.log* files which
> contain the IMAP traffic so that I can take a peek at what's going wrong.
> 
> Thanks in advance.

Comment 3 Kevin Ottens 2010-10-04 08:02:16 UTC

I kind of assumed you were running trunk, but the partial information you provided so far make me think that maybe it's not the case. Which version of kdepim and kdepimlibs are you running?

Also, it sounds like a database issue, did you create this IMAP resource much earlier (4.4 times) and then upgraded later on? If that's the case recreating the resource might just fix your issue.

Comment 4 Andreas Karrenbauer 2010-11-26 11:38:31 UTC

I've used an opensuse package. Now, since KDE 4.6 beta 1 is available for 
opensuse 11.3, the bug seems to be gone as far as I can tell from one day of 
testing.

On Monday 04 October 2010 08:02:20 Kevin Ottens wrote:
> https://bugs.kde.org/show_bug.cgi?id=252831
> 
> 
> 
> 
> 
> --- Comment #3 from Kevin Ottens <ervin kde org>  2010-10-04 08:02:16 ---
> I kind of assumed you were running trunk, but the partial information you
> provided so far make me think that maybe it's not the case. Which version of
> kdepim and kdepimlibs are you running?
> 
> Also, it sounds like a database issue, did you create this IMAP resource
> much earlier (4.4 times) and then upgraded later on? If that's the case
> recreating the resource might just fix your issue.

Comment 5 Kevin Ottens 2013-11-16 07:27:45 UTC

The IMAP resource has a new maintainer, reassigning to him.

Comment 6 Andrew Crouthamel 2018-09-25 03:39:55 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Andrew Crouthamel 2018-10-27 03:40:07 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!