Bug 259574 - conflict resolution box appears a lot
Summary: conflict resolution box appears a lot
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.9.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 260800 274973 275760 276991 277749 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-12-12 08:05 UTC by Marc Cousin
Modified: 2015-05-03 11:22 UTC (History)
36 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Conflict resolution box after applying filter (26.40 KB, image/png)
2010-12-23 20:31 UTC, Christian Esken
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Cousin 2010-12-12 08:05:54 UTC
Version:           SVN trunk (KDE 4) (using KDE 4.5.85) 
OS:                Linux

I can't really find a test case for now, as it doesn't occur all the time, but I get a lot of conflict resolution dialog boxes with kmail, at least when I try to modify a few mails in one go.

For instance, marking 3 or 4 mails as read at the same time (select the 4 of them, then right click and mark as read) triggers a bunch of conflict resolution boxes. The first of them displaying messages showing 'left' with nothing, and 'right' with 'SEEN'. Then a few of them displaying almost identical contents for mails (that's very hard to verify, as left and right columns in this conflict resolution box aren't of the same size, by the way).

This occurs on an IMAP account (dovecot server). I didn't try on other type of accounts.

It occured also when removing duplicates from a box. The whole conflict resolution went crazy (I had to kill kmail, after more than a hundred conflict resolution messages).

Reproducible: Sometimes

Steps to Reproduce:
Mark a few messages as read in one go, or remove duplicates seems to trigger the bug (if there are duplicates, I guess).

Tested only on IMAP (disconnected or not doesn't seem to make a difference).

Actual Results:  
Get flooded with conflict resolution boxes.

Expected Results:  
Not get flooded with conflict resolution boxes, as there should be no conflict.

This bug makes using kmail almost impossible for now on my systems.
Comment 1 Marc Cousin 2010-12-12 10:06:34 UTC
I think I'm getting a better view of what's happening:

When I mark a mail as 'read', it isn't marked as read in the UI (it doesn't change color). If I let it that way, at what I guess to be the next refresh, I get a series of conflict messages.

By the way, I forgot to mention that in order to be sure it wasn't because of a bad migration from 4.5, I destroyed all the files I thought were relevant in my home directory : any *akonadi* in my home, any *kmail* in .kde4, any *mail* in .kde4 (through find path -name *akonadi* -exec rm -rf {} \;).

So this occurs with a fresh install, I guess (or I have forgotten files).
Comment 2 Laurent Montel 2010-12-12 14:19:11 UTC
kmail 2
Comment 3 Rolf Eike Beer 2010-12-14 16:46:05 UTC
Same happens for me (4.6 beta2). Looks like it happens only the first time I open a folder. And all the message windows (like 30 or so) seem to be for the same mail,
Comment 4 Rolf Eike Beer 2010-12-14 20:18:32 UTC
Happened again. For me it looks like:

-the popup always shows the same message
-it happens on unread messages that are GPG-signed
Comment 5 Marc Cousin 2010-12-14 20:23:22 UTC
It happens on all unread messages, as far as I'm concerned. There is no correlation with GPG-signed emails at all.
Comment 6 Christian Esken 2010-12-23 20:25:07 UTC
I can acknowledge this. It doesn't have to do with GPG-signed. It happens on all kind of status changes, e.g. also when you apply a filter on a message and it gets moved to a new folder due to the filter rule.
Comment 7 Christian Esken 2010-12-23 20:31:32 UTC
Created attachment 55192 [details]
Conflict resolution box after applying filter

The filter moves the message and marks it as read.
Comment 8 simon 2011-02-02 23:28:48 UTC
actually i have no idea why its shown in this situation: when i read a mail with my android, go to kmail (shown as unread), click on it -> conflict.

the question is why it just not silently syncs with the imap and knows that it was read before
Comment 9 Allen Winter 2011-04-16 16:13:01 UTC
Here's another situation where the conflict dialog happen a lot:

On machineA I have kmail1 configured to download messages from my POP3 account
On machineB I have kmail2 configured to leave messages from that same POP3 account on the server

Then with kmail2 I get a ton of conflicts on messages from the POP3 account.

I'm making this bug a showstopper for the kdepim4.6 release
Comment 10 Thomas Capricelli 2011-06-14 13:11:54 UTC
Hi. i'm getting flooded too, using kde 4.6.4
The kmail version is 4.6.0(gentoo version) or 2.1.0(as displayed in about box).

Reading all comments, i think i should provide the following details about my configuration:
* i use imap, not disconnected
* this is the only computer connected to this imap account
* i dont use kmail-based filtering/bogofilter/whatever.
* 99% of the mails triggering the problem are not pgp signed or crypted
* i do use spamassassin on the server, so i have lines like X-Spam-Level: and such

And my problem: each time i delete a mail, i got not one, but two 'update conflict' resolution box. The first one show modification time (00:00:00 on the left), Attribute and MDNStateAttribute. The second one show lot of text that look like headers+contents from mail.
Comment 11 Thomas McGuire 2011-06-14 13:31:47 UTC
*** Bug 260800 has been marked as a duplicate of this bug. ***
Comment 12 Hussam Al-Tayeb 2011-06-14 18:33:36 UTC
For me, this happens when I use bogofilter for spam filtering.
it offers two emails. one with the x-bogosomething and one without it.
Comment 13 Arne Babenhauserheide 2011-06-15 00:29:30 UTC
This happens a lot for me, too - much more, since I updated from VCS version to 4.6.4 - and it disturbs my workflow a lot, even while I’m in other programs.

I understand that conflicts might be hard (if not impossible) to avoid in a concurrent system, but I don’t really look at the messages myself but just click them away. So I’d need a way to say “always keep both”. 

Means: Just make sure I don’t lose data, and otherwise don’t disturb me. 

Besides: I use bogofilter, too.
Comment 14 eric 2011-06-21 01:45:30 UTC
Here the conflict resolution box complains a lot about 2 e-mails which only differs in the modification time.

The left e-mail has a modification time that is the same as the localtime on my system and the right e-mail has a modification time that is my localtime minus 2 hours (looks like a different timezone). Sometimes, I've seen it only once, the difference is 2 hours plus or minus 1 second (I don't remember plus or minus).

Example:
Left:  2011-06-21 01:26:17
Right: 2011-06-20 23:26:17

PS.: My timezone is UTC+2 (UTC+1+DST)
PS2.: I download my e-mails from a POP3-server
PS3.: E-mails are filtered by the filter-feature provided by kmail2
Comment 15 Hussam Al-Tayeb 2011-06-26 12:41:05 UTC
(In reply to comment #14)
> Here the conflict resolution box complains a lot about 2 e-mails which only
> differs in the modification time.
> 
> The left e-mail has a modification time that is the same as the localtime on my
> system and the right e-mail has a modification time that is my localtime minus
> 2 hours (looks like a different timezone). Sometimes, I've seen it only once,
> the difference is 2 hours plus or minus 1 second (I don't remember plus or
> minus).
> 
> Example:
> Left:  2011-06-21 01:26:17
> Right: 2011-06-20 23:26:17
> 

Is the time difference because of the filtering?
time 1: when email was sent.
time 2: when email was downloaded and filtered?
Comment 16 Hussam Al-Tayeb 2011-06-26 12:42:48 UTC
sorry, I mean timezone instead of time. Sender's timezone and timezone on machine where it was downloaded/filtered.
Comment 17 eric 2011-06-28 10:35:42 UTC
(In reply to comment #15)
> Is the time difference because of the filtering?
> time 1: when email was sent.
> time 2: when email was downloaded and filtered?

Maybe there is a conflict between before and after filtering, because almost all e-mails are filtered. Sometimes I add a new header and sometimes the e-mail is moved to a different folder.
time 1: is not the time when the e-mail was sent, 
        it is the time of the appearance of the conflict resolution box.
time 2: is the exact same time as time 1 (sometimes 1s later) but 2 hours earlier.

It looks like something is respecting the timezone setting of my system, at this moment UTC+2 (UTC+1+DST), and something else is using UTC.
Comment 18 Thomas Capricelli 2011-07-12 13:13:07 UTC
i've fixed my own problem by changing the following setting : misc/"mark selected message as read after".
It was checked, and the delay was '5 sec'. Now, it is still checked, but with the default value of '0'.

I still have the 'conflict resolution box' from times to times, but it's really rare now. kmail is now almost usable.

Hope this helps.
Comment 19 Andre Woebbeking 2011-07-12 20:42:38 UTC
My workaround is to deactivate the spam filters. After that change I didn't see the 'conflict resolution box' again.
Comment 20 Hussam Al-Tayeb 2011-07-12 20:46:42 UTC
(In reply to comment #19)
> My workaround is to deactivate the spam filters. After that change I didn't see
> the 'conflict resolution box' again.
Yes, that helped me a lot too. But now I still get conflicts in emails that reach my inbox instead of being filtered to different folders.
Comment 21 Bernd Buschinski 2011-07-26 12:22:02 UTC
I moved all my mails from "Kmail folders" to "Local folders" and deleted the "kmail folders", since then the conflict dialog didn't appear again.
And I have the spamfilter enabled, bogofilter. I am not sure if this is a real fix or something else was at fault, but no more conflict dialogs for me, woohoo :)

btw I think "Kmail folders" where created by the migration from kmail1 to kmail2
btw2: be careful if you try this(moving all your mails) too, using kmail2 Version 2.1.96 and kde 4.7rc2 I had a cup of crashes and kontact sometimes eat my all my ram until it crashed
Comment 22 Hussam Al-Tayeb 2011-08-15 00:11:51 UTC
So if I understand correctly, there is more than one reason/bug which makes us see this behavior?

Any instructions from the developers for what we users can do to capture some information we can submit when bug happens (i.e. conflict window shows)?
Comment 23 Franz Trischberger 2011-08-27 18:17:49 UTC
Same here since update to 4.7.0. I can trigger it with deleting several Mails.
I even could make kontact freeze taking 100%CPU (deleting 8 Mails with pressingdel 8 times). I had to kill kontact. (I am using kmail embedded into kontact).
It is not possible to clean up these IMAP-Accounts, deleting is a great amount of work, as one either waits for each delete being finished successfully, or clicking away all thos conflict resulution boxes :/

It would be nice, if someone could tell us, how to give neccessary information to the devs. I don't know who is the bad boy here - akonadi-server? imap-resource? kmail? And how to debug this?
Comment 24 Andre Woebbeking 2011-08-27 18:36:39 UTC
I also had problems with KMail from 4.7.0 but thanks to Montel Laurent for fixing many bugs (and of course other people too), 4.7.1 will work much better.

One tip: don't use mixexmaildir resource (it's slow and uses much RAM).
Comment 25 Hussam Al-Tayeb 2011-08-27 18:45:01 UTC
I still get conflics with anything that reaches inbox without getting filtered to a specific folder like Inbox/Bugs/KDE
using 4.7 branch
Comment 26 Hussam Al-Tayeb 2011-08-27 18:46:59 UTC
(In reply to comment #24)
> I also had problems with KMail from 4.7.0 but thanks to Montel Laurent for
> fixing many bugs (and of course other people too), 4.7.1 will work much better.
> 
> One tip: don't use mixexmaildir resource (it's slow and uses much RAM).

What is mixexmaildir?
Comment 27 Andrew Gaydenko 2011-09-04 04:15:31 UTC
At my case the resolution dialog even frequently hangs forcing me to terminate kmail at all. I'm not sure it is another bug or this one. Has anybody the same behavior?
Comment 28 Jonathan Marten 2011-09-04 06:42:49 UTC
For conflict resolution box (as a result of filtering) locking up the GUI, see bug 281085.
Comment 29 Dave Brain 2011-09-04 07:21:52 UTC
Comment #27 Yes, I see this behaviour and I'm running 4.7.0 on archlinux
Comment 30 Andrew Gaydenko 2011-09-04 08:21:57 UTC
@Dave Brain

I have moved to (and voted for) bug 281085 in accordance with Jonathan Marten information.
Comment 31 Andrew Gaydenko 2011-09-10 05:36:55 UTC
(In reply to comment #24)
> I also had problems with KMail from 4.7.0 but thanks to Montel Laurent for
> fixing many bugs (and of course other people too), 4.7.1 will work much better.
> 
> One tip: don't use mixexmaildir resource (it's slow and uses much RAM).

Do you mean you have not messages doubling as a result of broken filtering any more with 4.7.1? 

I still have the doubling with 4.7.1, and haven't found a workaround at my case (POP3 accounts only and predefined Local Folders). Has anybody found?
Comment 32 Andre Woebbeking 2011-09-10 11:18:50 UTC
(In reply to comment #26)

> > One tip: don't use mixexmaildir resource (it's slow and uses much RAM).
> 
> What is mixexmaildir?

That are folders which contains mails in maildir AND mbox format.
Comment 33 Andre Woebbeking 2011-09-10 11:21:38 UTC
(In reply to comment #31)

> Do you mean you have not messages doubling as a result of broken filtering any
> more with 4.7.1? 

I thought so but now I see that I only disabled the spam filters, sorry :-(
Comment 34 Tom Chiverton 2011-09-26 17:31:52 UTC
I see this all the time. This is the only client accessing my IMAP server at any given time. How can there be a conflict, and why do I care ?

The dialogue marks in red:

Modification Time:
26/09/2011 18:21:29

26/09/2011 17:28:40
Flags:
\SEEN


Ubuntu 11.11 beta 2.
Comment 35 Hussam Al-Tayeb 2011-10-10 07:51:52 UTC
I stopped getting the conflict resolution message in kmail 4.7.2 and akonadi 1.6.2
Comment 36 Andrew Gaydenko 2011-10-10 07:55:08 UTC
I don't get the dialog with 4.7.2 also.. Probably because a filtering just doesn't work :-)

https://bugs.kde.org/show_bug.cgi?id=283548
Comment 37 Franz Trischberger 2011-10-14 07:42:51 UTC
I had the same impression first, it really seemed fixed. But after one of those many internet connection losses, that i get here, i got it again. It was only one box, and it came after deleting many mails. I think the connection was lost during the mail was about to get deleted.
But this seems to be the considered use case for the conflict resolution box, so all is fine. I can mark several dozens of mails, delete, and no box appearing anymore :) Or just pressing "del" as often and as fast as i want.

The only thing: Though the mail gets deleted, akonadi passes the downloaded mail to nepomuk for indexing (entirely without any use to me), which slows down things a bit and triggers CPU-load without any reason. But thats just another bug (?) :)
Comment 38 Tom Chiverton 2011-10-14 18:42:19 UTC
Happens less with the release 4.7.2 / Ubuntu 11.10 version.
Comment 39 Hussam Al-Tayeb 2011-12-30 00:16:03 UTC
getting conflicts again in kmail 4.8rc1
Comment 40 Mario Santagiuliana 2012-01-11 08:24:26 UTC
Same problem on Fedora 16:
$ rpm -q kdepim
kdepim-4.7.4-1.fc16.x86_64
Comment 41 Shai 2012-01-25 11:54:58 UTC
Same here on Kubuntu Oneiric:
kmail 4:4.7.4+git111222-0ubuntu0.1

As far as I'm concerned, this should be marked critical; "cannot use spam filtering" is almost exactly equal to "cannot use kmail".

Also, looking at Comment #9 - not being able to leave on server is a showstopper.

Also, looking at Comment #9 - bug was not a showstopeer for 4.6 or 4.7 -- maybe finally make it one for 4.8?

Also, I may be able to help; any pointers?

Thanks,
Shai.
Comment 42 Kevin Gilbert 2012-03-07 20:15:36 UTC
Is anything happening with this bug? There has been no feedback from the developers giving the impression that this is being ignored.

In my case, I get the dialog box on just about every message I open. And if that message has lengthy attachments, the whole KMail system stalls until the dialog box appears - this can be for up to a minute.

For me, this should be top of the Most Hated Bugs list as it makes KMail close to unusable.
Comment 43 Andrew Gaydenko 2012-03-08 00:25:25 UTC
For me with 4.8 the dialog has appeared few times only (3-4 times). I use Arch Linux which follows closely to upstream releases. Just yesterday have upgraded to 4.8.1 and have not any statistics for this version yet.
Comment 44 Kevin Gilbert 2012-03-08 00:34:59 UTC
FYI: Running fully up-to-date Fedora 16 w/ KMail 4.7.4
Comment 45 Simon Reed 2012-04-12 11:29:10 UTC
I am getting this with:
Xubuntu 11.10
KMail which reports itself as "Version 4.7.3 Using KDE Development Platform 4.7.4 (4.7.4)"
Package: kmail 4:4.7.4+git111222-0ubuntu0.1

An email downloaded using POP3 caused the "Conflict Resolution" pop-up.
I have no specific filters to handle this email, although I do have bogofilter installed.
The only difference between the two identical emails is:
---------------------------------
Modification Time:
12/04/2012 10:58:22

12/04/2012 10:58:27
Flags:


\SEEN
---------------------------------
Comment 46 Graeme Hewson 2012-05-03 13:28:19 UTC
I'm seeing this a few times a week on a busy POP3 account using 4.8.2 with Kubuntu 12.04.

The emails are not the same, and I don't know why I'm even being given the choice -- I always click "Keep both".
Comment 47 Hussam Al-Tayeb 2012-06-20 09:37:00 UTC
it's happening a lot again in kde 4.8.4 when an email is passed through spam filter but not filtered to go to a specific folder (other than the Inbox folder).
Comment 48 Graeme Hewson 2012-06-20 09:54:10 UTC
I see it happen often when receiving mail in threads I've marked as Ignore and when doing Bogomail filtering.

Ironically, I don't even want to do Bogomail filtering on the busy account (with the ignored threads), but due to bug 285802 I have to have filtering on all accounts or none (see my comment 6 there).
Comment 49 George L. Emigh 2012-08-28 00:19:12 UTC
KDE 4.9.0
Gentoo

Using Spamassassin (spamd) I get this 65% of the time, left one is usually after spamd touched it and the right one is before spamd touched it as evidenced by the changes in the headers and sometimes subject line.

It would be nice to never see that again, but really anoying is it hiding behind other windows and not getting noticed until after I've already futzed with kmail wondering what is up now...

Thanks in advance.
Comment 50 George L. Emigh 2012-09-05 00:03:48 UTC
KDE 4.9.1
Gentoo

The conflict resolution box still appears a lot in 4.9.1...

Thanks in advance.
Comment 51 George L. Emigh 2012-09-05 00:13:22 UTC
I'm seeing a trend.

I use spamassassin (spamd) and the conflict resolution box appears on messages that a subsequent filter moves the message into a different folder.

The one on the left is after spamassassin has modified it, when I click accept trhe left one, then the message(s) are moved in the destination folder for messages.

Don't know if that helps any.

Thanks in advance.
Comment 52 George L. Emigh 2012-09-07 20:57:36 UTC
In addition to what I mentioned in comments 49,50 and 51.

Seems to also be limited to messages that are to be moved into a Folder (mailing list) that contain a lot of messages.

I have one folder that contains 12700+ and another with 6700+ messages and it seems to be limited to those particular messages.

Thanks in advance.
Comment 53 Thomas Fischer 2012-09-11 14:20:36 UTC
I can confirm this problem on ArchLinux, using KMail/Kontact that comes along KDE 4.9.1 (most recent stable as of writing). The ArchLinux installation is brand new (inside a virtual machine) and has therefore no legacy configuration files. No fancy mail setup (e.g. using SpamAssassin) has been set up. The IMAP server is UW-IMAP 2007b~dfsg-4+lenny3, the mailbox contains just about 10 mails.
The conflict resolution box appears when marking several mails as read (KMail is configured to *not* mark mails as read automatically when clicking on them in the list, but only when the user performs the "Mark mail as read" action) and immediately thereafter selecting/clicking on one of those mails in the list.
My guess is that the status change from Unread to Read is not yet transferred to the mail server, but the clicking on the mail triggers fetching the mail from the server. Thus, both versions differ when one is read (the local one) and the other is unread (the newly fetched one).

As a step towards fixing this bug, I would like to see the difference between both mails visualized better. A previous comment remarked the different widths of both emails in the conflict box, which makes it hard to spot the actual difference. Is using the widget from Kompare or KDiff3 an option? For developers (and for bug reports), the difference should be provided in a "diff"-like format.
Comment 54 András Manţia 2012-10-13 22:22:04 UTC
*** Bug 274973 has been marked as a duplicate of this bug. ***
Comment 55 András Manţia 2012-10-13 22:22:41 UTC
*** Bug 275760 has been marked as a duplicate of this bug. ***
Comment 56 András Manţia 2012-10-13 22:23:02 UTC
*** Bug 276991 has been marked as a duplicate of this bug. ***
Comment 57 András Manţia 2012-10-13 22:23:24 UTC
*** Bug 277749 has been marked as a duplicate of this bug. ***
Comment 58 András Manţia 2012-10-13 22:25:04 UTC
Git commit 21d7ebcfa071653ee7a7c184d45b344fd3bb8586 by Andras Mantia.
Committed on 14/10/2012 at 00:25.
Pushed by amantia into branch 'master'.

Disable revision check(conflict checking) if only flags were changed.
That is not very important and can be triggered relatively easily with reading mails while a filter is active.

For the bugs where I CC'd, please see if you can still reproduce it (the change affects
only when marking manually conflicted with marking the mail by a filter).
Related: bug 286048


FIXED-IN: 4.10

M  +1    -0    mailfilteragent/filtermanager.cpp

http://commits.kde.org/kdepim/21d7ebcfa071653ee7a7c184d45b344fd3bb8586
Comment 59 András Manţia 2012-10-13 22:25:55 UTC
Git commit a2adaa32fec765995b7241a7fb00c5876c82f842 by Andras Mantia.
Committed on 14/10/2012 at 00:25.
Pushed by amantia into branch 'KDE/4.9'.

Disable revision check(conflict checking) if only flags were changed.
That is not very important and can be triggered relatively easily with reading mails while a filter is active.

For the bugs where I CC'd, please see if you can still reproduce it (the change affects
only when marking manually conflicted with marking the mail by a filter).
Related: bug 286048

FIXED-IN: 4.9.3
(cherry picked from commit 21d7ebcfa071653ee7a7c184d45b344fd3bb8586)

M  +1    -0    mailfilteragent/filtermanager.cpp

http://commits.kde.org/kdepim/a2adaa32fec765995b7241a7fb00c5876c82f842
Comment 60 Hussam Al-Tayeb 2012-10-14 11:06:41 UTC
I still get conflicts. I looked up a website on google where I can send myself test emails.
I get conflict and I choose to keep both mails:
First one is:

X-Virus-Flag: no
Return-Path: <nobody@server.hosting2all.com>
Delivered-To: hussam@visp.net.lb
Received: by hosting.visp.net.lb (Postfix, from userid 65534) id 79F694891EA; Sun, 14 Oct 2012 14:00:16 +0300 (EEST)
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on vmail
X-Spam-Level: *
X-Spam-Status: No, score=1.3 required=5.0 tests=RDNS_NONE autolearn=disabled version=3.3.2
X-Greylist: greylisting inactive for hussam@visp.net.lb in SQLgrey-1.7.6
Received: from server.hosting2all.com (unknown [174.133.115.194]) by hosting.visp.net.lb (Postfix) with ESMTP id EBD37487B31 for <hussam@visp.net.lb>; Sun, 14 Oct 2012 14:00:12 +0300 (EEST)
Received: from nobody by server.hosting2all.com with local (Exim 4.80) (envelope-from <nobody@server.hosting2all.com>) id 1TNLvU-0007tg-AR for hussam@visp.net.lb; Sun, 14 Oct 2012 06:00:08 -0500
To: hussam@visp.net.lb
Subject: hi, this is a test mail.
From: Free Email Service <info@send-email.org>
X-Mailer: PHP/5.3.9
Message-ID: <E1TNLvU-0007tg-AR@server.hosting2all.com>
Date: Sun, 14 Oct 2012 06:00:08 -0500
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.hosting2all.com
X-AntiAbuse: Original Domain - visp.net.lb
X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12]
X-AntiAbuse: Sender Address Domain - server.hosting2all.com
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.513766, version=1.2.2
MIME-Version: 1.0

his is a test mail

Second one is:

Return-Path: <nobody@server.hosting2all.com>
Delivered-To: hussam@visp.net.lb
Received: by hosting.visp.net.lb (Postfix, from userid 65534)
	id 79F694891EA; Sun, 14 Oct 2012 14:00:16 +0300 (EEST)
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on vmail
X-Spam-Level: *
X-Spam-Status: No, score=1.3 required=5.0 tests=RDNS_NONE autolearn=disabled
	version=3.3.2
X-Greylist: greylisting inactive for hussam@visp.net.lb in SQLgrey-1.7.6
Received: from server.hosting2all.com (unknown [174.133.115.194])
	by hosting.visp.net.lb (Postfix) with ESMTP id EBD37487B31
	for <hussam@visp.net.lb>; Sun, 14 Oct 2012 14:00:12 +0300 (EEST)
Received: from nobody by server.hosting2all.com with local (Exim 4.80)
	(envelope-from <nobody@server.hosting2all.com>)
	id 1TNLvU-0007tg-AR
	for hussam@visp.net.lb; Sun, 14 Oct 2012 06:00:08 -0500
To: hussam@visp.net.lb
Subject: hi, this is a test mail.
From: Free Email Service <info@send-email.org>
X-Mailer: PHP/5.3.9
Message-Id: <E1TNLvU-0007tg-AR@server.hosting2all.com>
Date: Sun, 14 Oct 2012 06:00:08 -0500
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.hosting2all.com
X-AntiAbuse: Original Domain - visp.net.lb
X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12]
X-AntiAbuse: Sender Address Domain - server.hosting2all.com

his is a test mail
Comment 61 Hussam Al-Tayeb 2012-10-14 11:34:01 UTC
In other words, one is locally filtered and one isn't
Comment 62 Hussam Al-Tayeb 2012-10-17 08:40:17 UTC
I found another way to reproduce this.
Start a new 'check mail' while the old one hasn't finished yet.
Comment 63 András Manţia 2012-10-17 13:41:19 UTC
The generic conflict issue that appears when flags get conflicted is fixed. The second when local spam filter duplicates the message and creates weird stuff is fixed in 4.10 and will be backported to 4.9.3 soon.
Comment 64 Hussam Al-Tayeb 2012-10-21 09:03:55 UTC
This still happens to me in latest build from KDE/4.9 branch.
It also happens if kmail checks for new emails when previous operation is still in progress.
Comment 65 András Manţia 2012-10-21 09:26:31 UTC
Hav you updated all kde pim modules (kdepimlibs, kdepim-runtime, kdepim) and restarted akonadi? Can you post a screenshot of the dialog coming up?
Comment 66 Hussam Al-Tayeb 2012-10-21 09:33:11 UTC
Yes. I will post a screenshot if it happens again.
There is also a chance I am running to https://bugs.kde.org/show_bug.cgi?id=305073 as well as a conflict.
I will see if it happens again after a new build. thank you.
Comment 67 András Manţia 2012-10-21 18:15:14 UTC
Git commit 05c67ec79b0c9fb9f9791462e597d293e75a1e8c by Andras Mantia.
Committed on 21/10/2012 at 20:15.
Pushed by amantia into branch 'KDE/4.9'.

Actually we should always disable the conflict dialog when a filter modifies a mail.
Mail (bodies) cannot be modified from anywhere else and flag changes do not
worth the conflict dialog.
Related: bug 302235

M  +1    -3    mailfilteragent/filtermanager.cpp

http://commits.kde.org/kdepim/05c67ec79b0c9fb9f9791462e597d293e75a1e8c
Comment 68 Nancy Anthracite 2015-05-03 02:44:31 UTC
I am having trouble with this with Kmail 4.14.1 and KDE 4.14.2.  The conflict resolution dialog pops up behind the Kontact Kmail window and waits for a response to be made, making Kmail cease to be usble until I minimize everything and find the popup dialog.  I would like to be able to set the default to keep both if I want so I don't have to find this dialog, or have the dialog box come up on top so I don't have wonder why Kmail is not responding and go hunt for the dialog box.  I am not sure yet while this is happening.  This long old bug report may help me figure it out after I read it all.