Bug 307930 - Duplicated new email from MS 2007 Exchange server accessed as IMAP
Summary: Duplicated new email from MS 2007 Exchange server accessed as IMAP
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.9
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-10-05 15:42 UTC by Chris
Modified: 2018-10-27 04:07 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2012-10-05 15:42:57 UTC
On Kmail/Akonadi start-up each morning an IMAP account hosted on an MS 2007 Exchange server loads duplicate copies of new email to KMAIL.  The only way to stop this is to access server side subscriptions and deactivate the inbox.  Then using webmail access to the Exchange server delete the new duplicated emails leaving one email as read.  Go back to KMAIL and server side subscriptions and reactivating the inbox.  The rest of the day if Akonadi is not stopped and started again the problem does not recur.

Reproducible: Always

Steps to Reproduce:
1.initial Open of Kmail at start of work day
Actual Results:  
Receive multiple duplicated copies of new emails.

Expected Results:  
only one copy of new emails in Kmail

Only loaded on copy of the new email.  I have followed directions for creating imp.log files and per the instructions at techbase.kde.org/Projects/PIM/Akonadi?Debug_IMAP  can forward those to a developer.

The severity of this problem to me is high only because of the time involved in deleting the duplicated emails.  If I don't stop the inbox I have obtained over 4,000 duplications of emails.  It is a waste of time that can and should be spent more productively.
Comment 1 Kevin Ottens 2013-11-16 07:31:35 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 2 Christian Mollekopf 2013-11-24 19:48:56 UTC
Does this still apply to >= 4.11.3?
Comment 3 Chris 2014-05-19 18:56:45 UTC
Sorry for the delay.  This was 4.13.0.  It has been a issue in almost every version.
Comment 4 Andrew Crouthamel 2018-09-25 03:45:38 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 5 Andrew Crouthamel 2018-10-27 04:07:08 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!