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 776129 - Use Message-ID from Header instead of from server envelop
Use Message-ID from Header instead of from server envelop
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: engine
master
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 776251
Blocks:
 
 
Reported: 2016-12-15 11:42 UTC by Gautier Pelloux-Prayer
Modified: 2021-07-05 13:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Gautier Pelloux-Prayer 2016-12-15 11:42:28 UTC 
I have some mail with somehow invalid Message-ID:

> Message-ID: <000701cf6eaa$d21a5330$764ef990$@username@domain.net>

There are stored with message-ID <661609367999992002@unknownmsgid> because this is what the server envelop is returning. However Geary should use the value contained in the Header instead since the message id is pretty important for conversations, it might be worthwhile keeping the one being used out in public.
Comment 1 Michael Gratton 2017-01-09 15:12:40 UTC 
Note that since for Bug 713530 we may end up needing to compare the IMAP message id with whatever is stored in the db. So that means either storing both (or both iff different), or when requesting Geary.Email.Field.REFERENCES fetching the IMAP Message-Id header instead.
Comment 2 GNOME Infrastructure Team 2021-07-05 13:27:29 UTC 
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/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/geary/-/issues/

Thank you for your understanding and your help.