Bug 306203

Summary:	Mail dispatcher agent doesn't send emails from queue
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Alexander <vo.zaeb>
Component:	Mail Dispatcher Agent	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel, peter, vkrause
Priority:	NOR
Version First Reported In:	4.9
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Proof

Description Alexander 2012-09-03 16:35:17 UTC

Hi, the problem is in that sent email is not always being actually sent. So I created new message and sent it, but noticed it's still in queue. Was able to send it only after restarting the mail dispatcher agent.

This happens from time to time, but at least once per day.

Reproducible: Sometimes

Steps to Reproduce:
1. Create new email message
2. Send it
3. Check it is still in out box
4. Restart the mail dispatcher agent
5. Email will be sent immediately
Actual Results:  
Sometimes email is not being sent and remains in outcoming mail box instead of to be sent immediately.

Expected Results:  
Email should be sent immediately after user clicked "send" button.

Comment 1 Alexander 2012-09-03 16:36:30 UTC

Created attachment 73628 [details]
Proof

Comment 2 Alexander 2013-09-07 08:21:29 UTC

Any chance this could be confirmed or any workarounds given?

Comment 3 Laurent Montel 2013-09-07 08:46:02 UTC

it's valid in last 4.11.1 ?

Comment 4 Laurent Montel 2013-09-07 08:46:22 UTC

it's valid in last 4.11.1 ?

Comment 5 Alexander 2013-09-07 09:28:18 UTC

It is not yet available in the Linux distribution I do use. Will get back to this after upgrade.

Comment 6 Alexander 2013-09-15 08:12:02 UTC

Hi, yes, it is still appear in 4.11.1

Comment 7 Denis Kurz 2016-09-24 20:32:00 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 8 Denis Kurz 2017-01-07 21:46:58 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.