Bug 301105

Summary:	Sending mail fails - freeze of compose window
Product:	[Applications] kmail2	Reporter:	Jan <anmeldungen>
Component:	commands and actions	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	critical	CC:	kde
Priority:	NOR
Version:	4.8.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jan 2012-06-03 13:20:11 UTC

Composing a new mail in kmail and hit the send button ends in a freeze of the composer window and the email not getting sent.

Kmail is used for two POP3 accounts and onw local mail directory ~/.local/share/mail/
There are two SMTP accounts configured for sending

This doesn't happen on two other machines using IMAP and SMTP accounts on amd64 instead on i368

Reproducible: Always

Steps to Reproduce:
1. Write a new mail or reply to an existing one
2. Click the send button
Actual Results:  
The new email window turns grey/disabled and freeze. The mail wont get sent.
The main window is still responsive. Hitting the close icon in the titlebar of the composer window gives the normal close dialog, asking to save the draft or cancel. Hitting save as draft doesn't work either. Cancel works and cancels the new composed email.

Expected Results:  
The mail should get sent

Comment 1 Christian (Fuchs) 2012-06-08 12:33:14 UTC

Confirmed here on x86_64 with SMTP. 

Exactly the same behaviour, kmail is from 4.8.80 (4.9 Beta 1) 

The window freezes, when I try to close it it gives me the  option to save as draft, discard or abort. Saving as draft doesn't work  (still freezes), discarding works, but the mail is lost.

Comment 2 Denis Kurz 2016-09-24 18:23:32 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 3 Denis Kurz 2017-01-07 22:35:45 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.