GNOME Bugzilla – Bug 418425
'searching on message contains' doesn't return results for meeting requests
Last modified: 2021-05-19 12:13:16 UTC
Please describe the problem: As a result of things described elsewhere (http://bugzilla.gnome.org/show_bug.cgi?id=301363) I have a need to revisit all the calendar requests I've seen recently. There is no search function I can find that will show me this information; apparently, calendar emails are so special that they get exempted from many normal searches. Unlike OWA, they are not displayed with special icons, and the "message contains" function doesn't seem to return things that I can see that the message contains (using view source.) For instance, all of the calendaring requests I've been able to dig up have a header: Content-class: urn:content-classes:calendarmessage ...but searching on "message contains" and "calendarmessage" gives me a null set, even while I'm looking at the message source in another window and cut/pasted the search string directly from it. Likewise, searching on "VCALENDAR" or "meeting.ics" or even ".ics" returns nothing (except possibly one or two emails that discuss the structure of icalendar.) Am I being stupid, or should the "message contains" search function allow me to search on the raw message text in its entirety? If so, it doesn't; if not, please add a search that does. (While you're at it, howsabout also adding an arbitrary-text search on just the headers?) Steps to reproduce: 1. send yourself an Exchange meeting request 2. click in search field, select "message contains" 3. enter "calendarmessage" for the search string Actual results: empty result set Expected results: meeting invite message should show Does this happen every time? yes Other information:
"search on message contains" generally is not able to search in attachment data.
(In reply to comment #1) > "search on message contains" generally is not able to search in attachment > data. That's somewhat to be expected, although in this case lamentable -- the attachments are ASCII, albeit inside MIME delimiters. But the *headers* ? It's not like they're base64-encoded or anything... This one: Content-class: urn:content-classes:calendarmessage shows up before the Subject, To, From, and Date headers. What's the difference between "search on message contains" and "search on message body contains" if it's not that the former also searches header data?
I think that "message contains" is basically "body contains" + "indexed headers contains" Content-class would not be an indexed header that's probably why it doesn't show up... anyways, it's been a few years since I've looked at the code for this so I could be wrong.
If I were going to try and hack in a new search (for all header text) where would I start? What pieces of the code should I be looking at?
You'll want to mostly be looking inside evolution-data-server/camel, specifically at camel-folder-search.c and camel-search-private.c I think. depending on the backend, possibly also the imap search implementation (for example). I think you can define new search functions in camel-folder-search (it's been a while). To make them show up in the UI, tho, you'll need to look at evolution/filter/vfolders.xml (unless there is a searches.xml?) and hook into the function there. sorry for being somewhat vague, but I don't know what all has changed since I was a mail maintainer (I work on another project now).
Still in 3.2.3 with "Message contains" "text/calendar"
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new bug report ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.