Version: Git (master) (using KDE 4.6.3) OS: Linux Since commit 49852b34 the presence of pipethrough filters causes new messages to uncontrolably multiply . It seems that the newly filtered message is not replacing the recieved one and is being filtered again as if it was a new message. This then plays in loops. It might be relevant in this case that the program I am piping through (bogofilter) may be changing the messages. Reproducible: Always Steps to Reproduce: Create a pipethrough filter and wait for new messages. Actual Results: New messages are being filtered and duplicated. Then the duplicates are being filtered and duplicated, ... 'ad infinitum' Expected Results: A new message should go through the filter chain and the end result written to the correct collection instead of the original. OS: Linux (i686) release 2.6.38-9-generic Compiler: cc
I am seeing this also in packages for Kubuntu Natty. I had to delete all Bogofilter filters.
Seeing this too (OpenSuse 11.4). But only one of my 4 cached IMAP accounts is affected by this bug.
I also have this problem but for online IMAP accounts even if my "Bogofilter Check" had "from all but online IMAP accounts" checked.
*** This bug has been confirmed by popular vote. ***
I can confirm this bug. Gentoo x86_64, KDE 4.7.1, Qt 4.7.4
Hej, I committed multiple changes to master today which might fix this issue. Can you retest, please? Ciao, Tobias
I just recompiled master and it seems that the issue is solved. I'll give it a few more days trial and mark this bug as RESOLVED if nothing bad happens. Thanks. (In reply to comment #6) > Hej, > > I committed multiple changes to master today which might fix this issue. Can > you retest, please? > > Ciao, > Tobias
Messages are not being duplicated any more. However, the changes as a result of the pipethrough filters are not being propagated to the server (I am using disconnected IMAP). The result is that new messages that go through a pipethrough filter are being fetched and filtered at every sync, over and over again. (In reply to comment #7) > I just recompiled master and it seems that the issue is solved. I'll give it a > few more days trial and mark this bug as RESOLVED if nothing bad happens. > Thanks.
Ouuupppss! Last famous words... There is indeed still message duplication, which may be related to the previous comment. However, I have one more observation. Duplication only seems to happen for messages on an exchange/outlook based server. Could this issue be related to the particular server implementation? (In reply to comment #8) > Messages are not being duplicated any more. However, the changes as a result of > the pipethrough filters are not being propagated to the server (I am using > disconnected IMAP). The result is that new messages that go through a > pipethrough filter are being fetched and filtered at every sync, over and over > again. >
Further information on this. Starting akonadi from a terminal I get the following output when clicking on one of the duplicate messages in kmail: void Nepomuk::Query::QueryServiceClient::close() 4721 FLAGS (\Seen) akonadi_imap_resource_2(27513)/kdepimlibs (kimap) KIMAP::StoreJob::handleResponse: We asked for UID but the server didn't give it back, resultingFlags not stored.
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!
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!