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 659440 - Doesn't mark messages as replied when sending offline
Doesn't mark messages as replied when sending offline
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.0.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-09-19 08:56 UTC by Milan Crha
Modified: 2011-09-26 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
evo patch (1.20 KB, patch)
2011-09-20 15:17 UTC, Milan Crha
committed Details | Review

Description Milan Crha 2011-09-19 08:56:40 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=739260

Evolution behaves totally wrong when sending (or outboxing) e-mails offline.

This bug, together with other bugs that keep evolution offline most of the time
(namely the bug that evolution doesn't reconnect and the bug that wifi
disconnects every 10 minutes).

By the way, going offline (by clicking the status icon or through menu) seems
to be broken now (nothing changes after clicking it and choosing „do not
synchronize“).

Version-Release number of selected component (if applicable):

evolution-3.0.3-1.fc15.x86_64

How reproducible:

Always (AFAIK)

Steps to Reproduce:
1. Disconnect/go offline (evolution wrongly thinks it's offline most of the
time anyway)
2. Send a reply
3. Click the only button available (discard)
4. Connect/go online
5. Look at the original message

Actual results:

after 2) a dialog box that cannot be cancelled (to keep the message window open
and not to put the message to outbox), which is totally wrong from the UI
perspective (the system wants to do something, informs you that it's going to
do that but offers no way to stop it)

after 5) the message is not marked as replied... that means you cannot dispatch
messages you haven't replied yet, because you don't even know which are already
replied and which not


Expected results:

after 2) OK and Cancel buttons, so user can actually choose what to do in this
unstandard situation (maybe he wants to change the message when he realizes
he's not able to send it now but will have to send it later)

after 5) The message MUST be marked as replied, unless there is some serious
error (and this serious error should be reported!)


Additional info

There are so many serious (and reported) bugs in Evolution that it can't be
considered a ready to use software. Maybe there should be some other mail
client
made default for new fedora users, or at least they should be warned they're
touching something experimental and broken.
Comment 1 Milan Crha 2011-09-20 15:16:10 UTC
Confirming, I see it too.
Comment 2 Milan Crha 2011-09-20 15:17:29 UTC
Created attachment 197075 [details] [review]
evo patch

for evolution;

There was a forgotten place to process drafts and source headers after message sending. Adding utility functions there fixes the issue.
Comment 3 Milan Crha 2011-09-26 10:24:36 UTC
Created commit 8db7139 in evo master (3.3.1+)
Created commit be8f9a8 in evo gnome-3-2 (3.2.1+)