Bug 297894 - Akonadi/kmail 4.8.2 refuses to send emails through smtp
Summary: Akonadi/kmail 4.8.2 refuses to send emails through smtp
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Mail Dispatcher Agent (show other bugs)
Version: 4.8
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-11 12:33 UTC by T Kleindienst
Modified: 2017-01-07 22:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description T Kleindienst 2012-04-11 12:33:40 UTC
After upgrade to 4.8.2 kmail / Akonadi shows strange behaviour

When trying to send emails, the message composer window stays open, gets grayed out, but the mail is not being sent anymore.

Using smtp without password in a local network.

It did work before (up to 4.8.1) and also continues to work when using claws.

What can it be?
Comment 1 T Kleindienst 2012-04-11 13:49:34 UTC
how to reproduce:

open kontact

write a mail and send it - it's sent


write a second mail - voila - it's not sent - composer window stays open.
when closing the composer window akonadi/kmail is dysfunct, also unable to show messages from the imap account
Comment 2 Martin Tlustos 2012-05-30 15:04:48 UTC
confirmed on Kubuntu 12.04 with kde 4.8.3.
Sometimes restarting akonadi helps, sometimes not.
Saving the email as draft in local folders works, "send later" as well.

Opening akonadiconsole and clicking on the resources results in long update times and sometimes a "cannot fetch data from backend" error.
Comment 3 Denis Kurz 2016-09-24 20:37:52 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:42:39 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.