Bug 282064 - kmail2 - no automatic update of local maildir
Summary: kmail2 - no automatic update of local maildir
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 08:49 UTC by hemathor
Modified: 2017-01-07 21:40 UTC (History)
0 users

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 hemathor 2011-09-15 08:49:56 UTC
Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

there is no possibility to automatically update a local maildir. no possibility to configure that.

f5 or manual update works just fine

Reproducible: Always

Steps to Reproduce:
add a local maildir account

Actual Results:  
local maildir is not updated automatically

Expected Results:  
local maildir should be updated automatically
Comment 1 hemathor 2011-09-18 08:19:21 UTC
after playing around a while, i found the setting, where to enable automatic updates:

- right click on folder -> folder properties...
- tab 'retrieval'
- deselect 'use options from parent folder or account'
- set 'automatically synchronize after:' to anything but 'Never'
Comment 2 hemathor 2011-10-06 11:16:08 UTC
actually it doesn't really work at all...

i was waiting until version 4.7.2, but it still shows the same behaviour:
after setting the retrieval intervall to e.g. '1 minute', it works for an undetermined time, but mostly exactly once! then the interval is set to 'Never' again, an the account isn't automatically updated again...
Comment 3 Denis Kurz 2016-09-24 18:01:25 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 4 Denis Kurz 2017-01-07 21:40:42 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.