Bug 252114 - error message "Could not access the outbox folder (Unknown resource)"
Summary: error message "Could not access the outbox folder (Unknown resource)"
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-23 10:50 UTC by Dave High
Modified: 2015-04-12 09:50 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dave High 2010-09-23 10:50:33 UTC 
Version:           1.13.2 (using KDE 4.4.2) 
OS:                Linux

Every time kmail is started, an error message pops up saying:

Kein Zugriff auf den Postausgangs-Ordner (Unbekannter Fehler. (Unknown resource)) möglich.

Translated to english:
No access to the Outbox folder is possible (Unknown error. (Unknown resource)).

Reproducible: Always

Steps to Reproduce:
Start kmail on Ubuntu whith KDE 4

Actual Results:  
The funtionality of kmail seems to be intact.
Only this error message is annoying.
The message pops up, only once per session

Expected Results:  
kmail starts whithout error messages.

OS: Linux (x86_64) release 2.6.32-24-generic
Compiler: cc
Comment 1 Dave High 2010-10-15 09:55:42 UTC 
I like to add this information which may be useful:
The error message (No access to the Outbox ...) has the title:  Mail Dispatcher Agent - Akonadi-Modul

So, it seems there is a problem between akonadi and kmail.
Comment 2 Laurent Montel 2011-09-22 08:19:42 UTC 
still valid ?
Comment 3 Christophe Marin 2011-09-22 09:03:05 UTC 
not sure, I see this actually:

kmail2(2296) MessageList::StorageModel::StorageModel: Using model: Akonadi::EntityTreeModel
kmail2(2296)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-krop/ksycoca4"
kmail2(2296)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kmail2(2296)/kdeui (KNotification) KStatusNotifierItemDBus::KStatusNotifierItemDBus: service is "org.kde.StatusNotifierItem-2296-1"
kmail2(2296)/kdeui (KNotification) KStatusNotifierItemPrivate::registerToDaemon: Registering a client interface to the KStatusNotifierWatcher
kmail2(2296) KMSystemTray::KMSystemTray: Initting systray
kmail2(2296) KMSystemTray::setMode: Setting systray mMode to 0
kmail2(2296) AkonadiSender::doSendQueued: Sending queued message with custom transport: ""
kmail2(2296)/kdepimlibs (mailtransport): Could not access Outbox.
Comment 4 Stefan Taferner 2011-11-12 21:30:18 UTC 
I see this message too at the moment, and I cannot get kmail to send the mails in the outbox in any way. It's kmail 4.7.2 here.

$ kmail
Object::connect: No such slot KMMainWidget::slotItemNotMovedByFilters( Akonadi::Item )
kmail2(6654)/kdepimlibs (mailtransport): Could not access Outbox.
Comment 5 Adrien 2012-04-20 09:23:51 UTC 
same here with KDE 4.8.2 from Mageia 2 beta 3.
Comment 6 Adrien 2012-04-20 10:35:00 UTC 
FYI, doing a:

$ akonadictl restart

solved the problem for me..
Comment 7 Laurent Montel 2015-04-12 09:50:03 UTC 
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.