| Summary: | when offline/online modes are irrelevant -- please disable this distinction | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Maciej Pilichowski <bluedzins> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | wishlist | CC: | bjoern, luigi.toscano, martin+kde |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
I see this as a rather interesting point. The difference for me in online/offline is, that kmail does not fetch mails automatically (and you get a warning, when you do it manually) Actually it would be better to get the network state from NetworkManager and handle offline/online only internal based on this. My $0.02 : what about renaming the "offline mode" to "disable automatic fetching/sending"? IMO it's a lot clearer. Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding. Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. |
Version: (using KDE KDE 3.5.8) Installed from: SuSE RPMs When user uses only on-demand features (send on demand, fetch on demand) and when user relies on such on-demand behaviour all questions related to offline/online switch are: a) unrelated b) confusing I don't know what Kmail tries to do when the network is dead, user sends a message and KMail asks if it should go online. Establish connection? For me it is just bizarre, for weekend users the question is surreal, i.e. "what online? I just want to send message like I did all the time". Reporting error with connection right away is much more clear ("oh, I have to turn the router on"). So please, if offline/online distinction is irrelevant (user do not use auto-fetch feature) please disable this switch.