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 791844 - Conversation is broken when using another smtp server
Conversation is broken when using another smtp server
Status: RESOLVED DUPLICATE of bug 713319
Product: geary
Classification: Other
Component: client
0.12.x
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 713319
Blocks:
 
 
Reported: 2017-12-21 14:03 UTC by Frédéric Parrenin
Modified: 2018-04-13 03:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frédéric Parrenin 2017-12-21 14:03:14 UTC 
At work I have a zimbra account.
On my phone I use gmail to access this zimbra account (using the exchange protocol).
On my PC I use Geary to access this account, albeit with a different smtp server (not the zimbra one), but still putting the sent emails in the zimbra folder.
If I get an email on zimbra and answer using my phone (and therefore the zimbra smtp server), the conversation is OK on Zimbra but it is broken on Geary.
Comment 1 Federico Bruni 2018-01-01 18:03:10 UTC 
As Geary relies on Message-IDs, probably the different smtp server you use on Geary is changing the Message-ID? Can you check the message source?

Make it depend on bug 713319, as it aims for using better grouping algorithms.
Comment 2 Frédéric Parrenin 2018-01-23 09:47:25 UTC 
Yes, the message ID is changed when sing the different smtp server.
Looking forward to better grouping algorithms.
Comment 3 Michael Gratton 2018-04-13 03:47:06 UTC 
Okay, marking as a duplicate of Bug 713319, it would be useful if you could attach to that bug some examples of the headers from the source of two messages that should have been grouped but weren't.Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 713319 ***