Bug 276285 - KMail cannot use an already running Akonadi resource for sending
Summary: KMail cannot use an already running Akonadi resource for sending
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdepimlibs
Classification: Applications
Component: mailtransport (show other bugs)
Version: 4.6
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-22 20:39 UTC by Alexander Potashev
Modified: 2017-01-07 22:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Potashev 2011-06-22 20:39:11 UTC 
Version:           2.0.95 (using KDE 4.6.4) 
OS:                Linux

I have an Akonadi resource that handles both receiving and sending of message/rfc822 messages.
Firstly I added that resource using "System Settings -> Personal Information -> Akonadi Resources", so that I was able to read the messages from that resource in KMail.
Then I tried to add the same resource to KMail as mail transport (Configure KMail... -> Accounts -> Sending -> Add...). I worked, but now I have two identical resources running, I can see them in both SystemSettings and AkonadiConsole.

It would be nice if KMail could start using an already added Akonadi resource for sending.

P.S.: I could split the resource into two resources, i.e. one for sending and another for message retrieval. But they would need to share configuration options, and I'm not sure if that can be done easily.

Reproducible: Always
Comment 1 Denis Kurz 2016-09-24 20:56: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 kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:00:40 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.