Bug 317275

Summary:	Unable to send emails in KMail 4.9.5
Product:	[Applications] kdepim	Reporter:	jmaldrich
Component:	libkdepim	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	grave	CC:	jmaldrich
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description jmaldrich 2013-03-24 15:40:32 UTC

I updated my Fedora this morning and saw there was an update for KMail, so I closed KMail and stopped Akonadi and waited until it was done installing. Then I restarted Akonadi and Kmail (both from the command prompt window) and later tried to send an email. I received a pop-up error message "Failed to transport message. Unable to create SMTP job."

Reproducible: Always

Steps to Reproduce:
1.Create new email in KMail 4.9.5
2.Try to send
3.Look for error pop-up
Actual Results:  
Pop-up error message states that the message can't be sent because an SMTP job can't be created

Expected Results:  
Email should just disappear from the outbox and go to the SMTP server.

Fedora 17 freshly upgraded with all available updates.

Comment 1 jmaldrich 2013-03-24 16:02:11 UTC

Now I am getting the following error when I start Akonadictl in a command prompt window: "Failed to fetch the resource collection." for just about everything, up to and including maildir folders. :( This latest update really screwed up my email!

Comment 2 jmaldrich 2013-03-24 21:07:07 UTC

May be duplicate of bug #301182. Also, have upgraded to KDEPIM 4.10.1-1 and things are even worse now! :(

Comment 3 Denis Kurz 2016-09-24 21:00:16 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 kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 22:24:00 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.