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 714450 - Immediately display reply / forwarded message in conversation
Immediately display reply / forwarded message in conversation
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: conversations
master
Other All
: Normal enhancement
: ---
Assigned To: Geary Maintainers
Geary Maintainers
: 730664 (view as bug list)
Depends on: 750695
Blocks:
 
 
Reported: 2013-05-06 06:05 UTC by Jim Nelson
Modified: 2019-08-11 12:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:26:47 UTC


---- Reported by jim@yorba.org 2013-05-06 11:05:00 -0700 ----

Original Redmine bug id: 6902
Original URL: http://redmine.yorba.org/issues/6902
Searchable id: yorba-bug-6902
Original author: Jim Nelson
Original description:

When a user replies or forwards a message in a conversation, it should appear
in Geary right away. This may be a bit of a trick, since Geary won't discover
the message in Sent Mail (if that folder even exists) for some time.

Related issues:
related to geary - 5188: Non-Gmail accounts not using Sent Mail folder (Open)
related to geary - 6498: more thorough full conversations (Fixed)
related to geary - 6903: Update conversations as new mail is discovered /
arrives ... (Duplicate)
related to geary - Feature #4554: compose new message in main window and
inline replies (Open)
related to geary - Feature #6873: Don't consider emails sent by user when
sorting conversat... (Fixed)
related to geary - 6876: Feedback when sending a message (Duplicate)
duplicated by geary - 6959: Reply within a mailing list thread (Duplicate)



---- Additional Comments From geary-maint@gnome.bugs 2013-07-08 15:11:00 -0700 ----

### History

####

#1

Updated by Jim Nelson 7 months ago

Ticketed on Launchpad at https://bugs.launchpad.net/geary/+bug/1091637

####

#2

Updated by Jim Nelson 6 months ago

  * **Target version** changed from _0.4.0_ to _0.5.0_

####

#3

Updated by Jim Nelson 5 months ago

  * **Subject** changed from _Display reply / forwarded message in conversation_ to _Immediately display reply / forwarded message in conversation_



--- Bug imported by chaz@yorba.org 2013-11-21 20:26 UTC  ---

This bug was previously known as _bug_ 6902 at http://redmine.yorba.org/show_bug.cgi?id=6902

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Jim Nelson 2014-05-23 21:55:04 UTC
*** Bug 730664 has been marked as a duplicate of this bug. ***
Comment 2 Jim Nelson 2014-06-12 00:56:37 UTC
commit c0607f improves (but does not solve) this problem.  When a message is sent the AccountSynchronizer will immediately schedule a re-sync with Sent Mail.  When the new message is fetched, it will be added to the conversation automatically.  There's still a delay, but it's much shorter and doesn't rely on background polling.
Comment 3 Jim Nelson 2014-06-12 00:57:52 UTC
commit c0607f improves (but does not solve) this problem.  When a message is sent the AccountSynchronizer will immediately schedule a re-sync with Sent Mail.  When the new message is fetched, it will be added to the conversation automatically.  There's still a delay, but it's much shorter and doesn't rely on background polling.
Comment 4 Pierre Equoy 2015-05-15 01:52:25 UTC
Hi,

I'm using Geary 0.10.0 with Ubuntu 14.04.2 and a non-GMail account and witnessed the same issue:

1. Reply to an e-mail
2. Send the reply
→ my answer disappears from the screen (NOK)

I waited a few minutes and my answer was not displayed in the view. Actually, in the meantime I even received a reply from my friend, so in the end it looks odd...

Is there a plan to fix this issue?

Thanks!
Comment 5 Jim Nelson 2015-05-24 21:46:28 UTC
(In reply to Pierre Equoy from comment #4)
> Is there a plan to fix this issue?

Do you have "Save drafts to server" enabled in your Accounts dialog?
Comment 6 Pierre Equoy 2015-05-25 02:51:58 UTC
Yes I do.
Comment 7 Ken Berland 2016-11-30 16:46:10 UTC
Using 0.11.2-1~xenial1.  I think this is an important issue to fix.  Replies should immediately show in the thread.  Perhaps mark them if sending is an issue later.  I work around this by visiting "Sent Mail" and then toggling back to see my reply in the thread.  Very sub-optimal.
Comment 8 Michael Gratton 2016-12-05 12:05:45 UTC
Ken, what server are you using? Also GMail? The lag for me (on a Cyrus-based server) is typically only 5-10s, while this is clearly still too long, are you seeing something much longer than that?
Comment 9 Ken Berland 2016-12-05 17:56:31 UTC
Using dovecot-2.2.  The lag for me is much longer than 15s.
Comment 10 Ken Berland 2016-12-05 20:26:49 UTC
Replies show up about 2 minutes after they send if I take no action.
Comment 11 Michael Gratton 2016-12-06 02:21:08 UTC
(In reply to Ken Berland from comment #10)
> Replies show up about 2 minutes after they send if I take no action.

Okay, that's unusual. Can I please get you to open a new bug for this, so we can look into whether there is something specific going wrong there? This bug is about fixing the more general issue. Ta!
Comment 12 Ken Berland 2016-12-06 22:39:11 UTC
#775730 filed.
Comment 13 Ken Berland 2016-12-06 22:40:37 UTC
With a link bug 775730.
Comment 14 Michael Gratton 2018-01-09 10:38:12 UTC
Solving this properly will probably involve keeping the draft hanging around the database and displaying that, then merging it when the server notifies us that it has appeared in the Sent folder. That would mean being able to merge messages based on Message-Id as well as RFC833 size and IMAP ordering, i.e. fixing Bug 750695, so marking as depending on that.
Comment 15 Michael Gratton 2019-08-11 12:49:19 UTC
A 90% complete fix for this will should make it into 3.34 when that is released, so I'm closing this in favour of the equivalent gitlab issue: https://gitlab.gnome.org/GNOME/geary/issues/131