Bug 324203

Summary:	abort sending mail, resend still shows aborted
Product:	[Applications] kmail2	Reporter:	Martin Koller <kollix>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	NOR
Version:	4.11
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Martin Koller 2013-08-29 07:06:52 UTC

When I try to send a mail but abort the send before it completed, then later send the mail again competely, the mail then moved to the sent-mail folder still shows a red warning area on top of the message with "Message transport aborted." although it was sent completely.

Reproducible: Always

Comment 1 Laurent Montel 2013-09-02 17:34:15 UTC

Work fine here.
Which type of mailtransport do you use ?
Do you have error in console ?

Comment 2 Martin Koller 2013-11-11 10:46:21 UTC

I had the issue today again and can reproduce it.
I send an email to an SMTP Server, which is not reachable (our company internal server, which I do not reach when VPN is not activated).
I get a "Socket operation timed out" error also in the top area of the mail still in the outbox.
I now select the File Menu -> Send Queued Message via -> <my providers public SMTP Server>
and the mail is now sent correctly.
The mail now moved into the "Sent" mail folder is still marked with the red message block:
"Failed to transport message. eis2k212: Socket operation timed out"

However, when I try to send the queued mail via the original (first) mail server, which timed out,
(so I activate VPN and select File -> send queued messages) then the mail ends up in the Sent mail folder _without_ the original error.

So it seems this only happens when the suceeding second transport is different from the first failing one.

Comment 3 Denis Kurz 2016-09-24 18:12:18 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 22:29:09 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.