Bug 334170

Summary: IMAP accounts are always switched online at startup
Product: [Applications] kmail2 Reporter: Jonathan Marten <jjm>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: rjvbertin
Priority: NOR    
Version: Git (master)   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jonathan Marten 2014-05-01 11:02:14 UTC 
An IMAP or POP account in KMail has the option (under Retrieval Options), "Switch offline on KMail shutdown".  This works, and is useful for those cases where the user may not want to retrieve mails all the time.

However, there is no corresponding option to choose whether the account is made online at KMail startup - this always happens.  This may not be what the user wants - e.g. they may not want the additional network traffic, or may not want to synchronise a disconnected account automatically.

Suggest that there should be an additional option "Switch online on Kmail startup" (with the default being true) to cover cases like these.


Reproducible: Always

Steps to Reproduce:
1.  Configure Kmail with an IMAP account
2.  Set its Retrieval Options: Include in manual mail check OFF, Switch offline on KMail shutdown ON, Check mail on startup OFF.
3.  Exit KMail
4.  Start akonadiconsole and confirm that the resource is offline.
5.  Start KMail again.  The resource will go online immediately.

Actual Results:  
Resource goes online when KMail starts up.


Expected Results:  
Have not requested it do do that.
Comment 1 RJVB 2014-06-04 15:23:49 UTC 
I concur, while it is a good idea to offline resources when quitting kmail, the very least would be to store and restore the state they had. That way, an account that was taken offline manually will remain so across restarts until it is onlined manually again.

Note that this is how OS X's Mail.app works, and there too it is a setting that completes the account-specific settings whether and how often checks for new mail ought to be done.
Comment 2 Denis Kurz 2016-09-24 18:19:50 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 22:26:50 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.