After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 326142 - Not merging "Include Threads" between source folders
Not merging "Include Threads" between source folders
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[vfolders]
Depends on:
Blocks:
 
 
Reported: 2006-01-07 22:00 UTC by Karsten Bräckelmann
Modified: 2020-12-22 14:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to not ignore "Sent" folders when vfolder is set to search in all local folders. (1.40 KB, patch)
2008-08-24 00:14 UTC, Rouslan Solomakhin (Руслан Соломахин)
rejected Details | Review

Description Karsten Bräckelmann 2006-01-07 22:00:40 UTC
Well, at least it looks like this. Pretty strange...

I just set up a vFolder, filtering all mails from a particular sender. Set the option "Include Threads" = "All related". This does *not* work as expected. My sent mails which are replies to mails matching the criteria are *not* displayed. All I get are the mails matching the criteria, no threads included.

This is the same with "all criteria" or "any criteria". All local and active remote folders does not work, and it doesn't make a difference if I specifically choose only the folders I'd need.

This is an IMAP account.


This issue is most strange, since I do know I used it just recently. Evo version 2.4.2.1 here. There was a report on the mailing list describing this behavior on 2.2.x as well.
Comment 1 Karsten Bräckelmann 2006-01-07 22:02:32 UTC
High priority, blocker. Scheduled for 2.4.3 (and thus of course 2.5). Woohoo.
Comment 2 Karsten Bräckelmann 2006-01-07 22:12:46 UTC
OK, more details.

On a different IMAP server I got 2 differnt "Sent" folders. One is the default Sent folder for the IMAP account -- the other one is a Sent folder for a sending *only* account.

Sent mails in the latter folder are picked up and threading.

Sent mails in the default Sent folder of this account are *not* being included.
Comment 3 Karsten Bräckelmann 2006-01-07 22:16:04 UTC
In a previous test I even changed the Sent folder to not point to a folder on the IMAP server, but used the local Sent folder instead. This did not change anything.

Thus it looks like the Sent /folder/ setting itself is not the culprit. All mails being sent by Evolution using the default account for this IMAP server are omitted.

Most strange.
Comment 4 Karsten Bräckelmann 2006-01-07 22:37:54 UTC
Fuck! The last comment #3 may not be accurate. For some strange reason I could not reset the Sent folder to the default. Thus my test did not what I thought it did.

Though this still seems to stand. Even copied mails (out of my Sent folder somewhere else) are not picked up. Changing the Sent folder doesn't change this either.

Have fun reproducing this. :)
Comment 5 parthasarathi susarla 2006-01-09 08:42:12 UTC
Whew! i tried all possiblities. I *cannot* reproduce this. Sigh!
Comment 6 parthasarathi susarla 2006-01-31 08:13:42 UTC
This works, i have the following options:
include threads - all releated
Sender contains - "some name"
Search Folder Sources - "With all active local and remote folders"

And this shows the entire thread.

Are we expecting to see the mails 'we sent' (the ones in the Sent Items folder). Then the Sender rule wont suffice. We need to have recipients rule too.

Am i missing something here?? 
Comment 7 parthasarathi susarla 2006-02-02 04:24:41 UTC
setting this to NEEDINFO
Comment 8 André Klapper 2006-02-26 15:12:44 UTC
hmm.... news, anyone?
i would decrease priority and severity since it does not seem to be easily reproducible. comments?
Comment 9 Shreyas Srinivasan 2006-03-07 06:48:08 UTC
I agree, reducing priority and severity.
Comment 10 Karsten Bräckelmann 2006-07-23 15:25:23 UTC
Need to investigate more and hopefully come up with a test case.
Comment 11 André Klapper 2006-11-01 10:53:50 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 12 Karsten Bräckelmann 2006-11-03 21:37:32 UTC
(In reply to comment #11)
> [...] if you can provide the information asked for.

What was the question?
Comment 13 André Klapper 2006-11-03 22:11:59 UTC
you asked yourself to investigate more, and to possibly come up with a test case.
feel free to assign this to yourself if you don't want to see this bug closed. :-)
Comment 14 Karsten Bräckelmann 2006-11-03 23:19:09 UTC
Testcase... *sihg*  My IMAP account. As simple as that. :/


Just checked again. I do see this still on 2.6.something.

To clarify this: This is about not including the entire thread, when the thread actually is distributed in multiple folders. Some examples -- teh search criteria in all these cases is one email address for sender. Include Threads is set to All Related.

In case the entire thread happens to be in one folder, this works. Yeah, easy...


Now the example that doesn't work (basically the initial report though). The thread that actually happend would be this, straigth ping pong style (colums are From and Subject, enumerated):

 me   + some issue [1]
 you    + Re: some issue [2]
 me       + Re: some issue [3]
 you        + Re: some issue [4]

All mail from me is in my Sent folder. All mail from you is in my Inbox. Both these folders are selected as sources for the vFolder. Filter is for all mails sent by you, including threads.

The poor result in the vFolder is this:

 you    + Re: some issue [2]
 you        + Re: some issue [4]


Other than that... No better tast case, for the simple fact that I did not observe this to work as expected ever since my report.
Comment 15 Gilles Dartiguelongue 2007-06-14 09:45:09 UTC
I could reproduce this bug. The example of the comment #14 is exactly what's happening. It's not related to a special treatment of folders named "Sent" since when I renamed the folder, evolution --force-shutdown and restarted evolution, it didn't changed anything. There as to be something else.
Comment 16 Rouslan Solomakhin (Руслан Соломахин) 2008-08-24 00:14:52 UTC
Created attachment 117282 [details] [review]
Patch to not ignore "Sent" folders when vfolder is set to search in all local folders.

This patch shows matching "Sent" messages regardless of whether it is a reply to searched message. Is this desired? I think it would be better if "Sent" messages are displayed only when they are parts of matching threads.
Comment 17 Srinivasa Ragavan 2008-08-31 18:31:32 UTC
Hmm, It wont work, if you have it set to specific folders. I dont know it use to work before, but I dont see much code for this to happen.

NOTE: With disk summary thread search/vfodlers don't work well. I know it is a regression, but should be fixed post release. So the the option (thread) is bluntly ignored :( and the query is executed.
Comment 18 Milan Crha 2012-05-31 10:55:30 UTC
I made some significant changes in vFolders for 3.5.2, and I would tell that this will not work, because the searches are done on respective folders, which means that the threads from folder A are unknown when searching in folder B. A workaround for such search would be to create a search folder with "match-all" from all folders you are interested in (note of bug #565483), and then create search folder for threads which will have a source folder this new "match-all"-folder. For this are required changes from 3.5.2.
Comment 19 André Klapper 2020-10-28 11:38:12 UTC
Hi, is this still a problem in a recent Evolution version (currently 3.38)? Asking as some parts of the code base and underlying dependencies changed in the meantime.
Comment 20 André Klapper 2020-12-22 14:16:05 UTC
Closing this bug report as no further information has been provided if this is still an issue in a recent version. Please feel free to report this ticket in https://gitlab.gnome.org if this problem still happens in 3.38 or newer. Thanks!