Bug 339185

Summary:	cannot retrieve MS Exchange Calendar items: "Retrieval using the IMAP4 protocol failed for the following message:"<msgid>
Product:	[Applications] kmail2	Reporter:	Jason Vas Dias <jason.vas.dias>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	4.13.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jason Vas Dias 2014-09-18 17:32:19 UTC

Unfortunately my company email account is hosted by MS-Office365  ( outlook.office365.com ) .
I have this defined as a KMail "Receiving" IMAP account, and it works OK for normal mail - but I'm having problems with other message types, eg. Calendar notification messages .

I can see no entries in the 'Calendar' IMAP account sub-folder except these error messages - here is an example:
<quote>
Subject: Retrieval using the IMAP4 protocol failed for the following message:4
From: 	
To:	"jason.vas.dias@REDACTED.com" <jason.vas.dias@REDACTED.com>
Date:	Unknown
The server couldn't retrieve the following message:

Subject: "REDACTED "
From: "REDACTED" ("/O=EXCHANGELABS/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=0CFA1B03EE0F458BB01229EB4EF576B5-REDACTED")
Sent date: 8/12/2014 12:00:59 PM

The message hasn't been deleted. You might be able to view it using either Outlook or Outlook Web App. You can also contact the sender to find out what the message says.
</quote>

Is kmail meant to support MS-Exchange functionality ? 
I thought nowadays it was, which is why I'm using KMail instead of Evolution .
If it is, it is evidently having problems .  I'd prefer not to have to switch back
to Evolution just because of this issue.

Is there likely to be any fix forthcoming for this, or do I need to use Evolution / OWA to get 
MS-Exchange Calendar messages?

Thanks for an otherwise problem-free mail client experience, a great improvement on previous versions.
Regards, Jason

Comment 1 Jason Vas Dias 2014-12-01 11:04:04 UTC

wow! Inspired by the extent of  the interest in  & progress on this issue to ammend it somewhat:
Please support using the OpenChange client library in kmail / libkdepim to enable access to exchange
 calendar:
              http://www.openchange.org
It looks like I can set up a cron-job to periodically download the calendar folder with 
the openchangeclient command and then write a script to add the messages to the local
mbox queue .  Couldn't support for doing this internally within kmail be added ?

Comment 2 Jason Vas Dias 2015-01-04 17:43:13 UTC

I've been using kmail since @ 2002+ , (from emacs mail, before it could handle SSL / TLS ), 
 but have now decided to switch back to emacs gnus , since although it does not handle 
 Calendar messages either, it also supports imaps + starttls and is alot easier and nicer to use than kmail -
 particularly in rendering HTML with w3 and displaying embedded images automatically,  while not
 downloading external references (without having to click to enable HTML display) , and in not 
 busy-waiting, hogging CPU, and using alot of storage .  Sorry, kmail has lost this user.  
Guess you can now file this bug under "dont care" .

Comment 3 Denis Kurz 2017-06-23 19:57:07 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 4 Denis Kurz 2018-01-31 16:53:07 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.