Bug 321054 - kmail2 doesn't send emails after long uptime ...
Summary: kmail2 doesn't send emails after long uptime ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-12 08:09 UTC by piedro
Modified: 2017-01-07 21:59 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description piedro 2013-06-12 08:09:17 UTC
When running KDE for a long time 48+ hours the mail dispatcher agent and the mail filter agent stop working ... they can be restarted via akonadi console  and they work again but this is very inconvenient and produces some undesired results ... (for example filters acting on incoming mail have not been applied and have to be reapplied manually - but this is no solution cause I don't know on which folders where to apply the filters manually - cause filtering obviously partially worked!)



Reproducible: Always

Steps to Reproduce:
1. let kmail2 run for 48 hours
2. try sending a new mail 
3. try to apply a filter that moves mail to a local folder e.g. spam
Actual Results:  
- the mail is stuck in the outbox
- the filter doesn't move the mail in question even on individual "apply filter" to a single mail

Expected Results:  
- mail should be sent 
- filter should move mail as it has done after a shorter period of uptime

this is really annoying as it renders kmail as productive PIM on a work machine useless - it's just still not reliable. If I can't trust filters and basic functions like"send immediately" and have to double check everytime to make sure - it's a waste of time ...
Comment 1 piedro 2013-08-06 02:08:44 UTC
KDE 4.10.5  - it's still present ...
Comment 2 Denis Kurz 2016-09-24 18:21:12 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 piedro 2016-09-24 19:45:14 UTC
I switched to gnome for productive work, sry, 
I can not provide anymore specific information on later versions... 

thx anyway, p.
Comment 4 Denis Kurz 2017-01-07 21:59:17 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.