Bug 311244 - Manual check button does not check
Summary: Manual check button does not check
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: MDN (show other bugs)
Version: 4.9.3
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-06 09:38 UTC by Roger Larsson
Modified: 2017-01-07 21:41 UTC (History)
1 user (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 Roger Larsson 2012-12-06 09:38:01 UTC
I have several accounts configured.
When I press the manual check button none are checked.
If I check a specific account it is checked

Whether  an account is checked or not can be seen if the account configuration setting is currently shown. My accounts are both "included in manual check" and "checked on start"
Neither worked... same implementation for both functions?

Reproducible: Always

Steps to Reproduce:
My guess...
1. Set up several accounts (I have two POP3, one maildir to store, one local /var/spool/mail/xx)
2. Let config window be open visible
3. Click on manual check
Actual Results:  
No status change for any of the configured receive accounts

Expected Results:  
All accounts should activate checking simultaneously
(this happens on my wife account - but she only have one POP3 and one local maildir)

If I manually check one of the accounts to update I can see the status changes...
Comment 1 ro.ggi 2013-01-03 16:01:07 UTC
Same problem here with an exception that manualy check didn't work whether specifed account is checked or not. I have only imap accounts.

Kontact/Kmail 4.9.3
Comment 2 Denis Kurz 2016-09-24 18:09:38 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 Denis Kurz 2017-01-07 21:41:18 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.