Bug 326874

Summary:	Local folder offline
Product:	[Applications] kmail2	Reporter:	Salvo "LtWorf" Tomaselli <tiposchi>
Component:	folders	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	kde-bugs-68795
Priority:	NOR
Version:	4.11.2
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot

Description Salvo "LtWorf" Tomaselli 2013-10-30 12:52:24 UTC

For some reasons, my local folders are "offline", as a result it won't send emails (it should send using sendmail locally).

It seems already weird to have local folders that went offline (I didn't do that) but I guess it could in some rare cases make sense. However the problem is that it won't go back in online mode, so my outgoing email is not sent.

Mutt sends email like a charm, so my server is configured properly.

Reproducible: Always

Steps to Reproduce:
I have no idea how this happened.

Comment 1 Salvo "LtWorf" Tomaselli 2013-10-30 12:53:02 UTC

Created attachment 83223 [details]
Screenshot

Screenshot, in case I sound unbelievable.

Comment 2 Khumba 2014-06-04 16:34:03 UTC

Does it work to open akonadiconsole and re-enable Local Folders manually (Right-click on Local Folders in akonadiconsole > Toggle Online/Offline)?  Or is the resource continually being disabled?

Also make sure that the Mail Dispatcher Agent is running, I think that needs to be online for mail to send.

Comment 3 Salvo "LtWorf" Tomaselli 2014-06-04 23:02:22 UTC

I migrated to an IMAP server+fetchmail.

It is unreasonable to expect that I'd keep around for this many months those resources that wouldn't let me access my emails easily.

Comment 4 Denis Kurz 2016-09-24 18:22:21 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 5 Denis Kurz 2017-01-07 22:13:35 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.