Bug 286955 - "Mail Dispatcher Agent: Could not access the outbox folder" message on every login
Summary: "Mail Dispatcher Agent: Could not access the outbox folder" message on every ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Mail Dispatcher Agent (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-18 19:54 UTC by Dima Ryazanov
Modified: 2017-01-07 22:31 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 Dima Ryazanov 2011-11-18 19:54:24 UTC 
Version:           unspecified (using KDE 4.7.3) 
OS:                Linux

Every time I log in, I get a notification:
"Mail Dispatcher Agent: Could not access the outbox folder (Unknown error. (Failed to fetch the resource collection.))."

I have no idea what it means or what I'm supposed to do about it.


Reproducible: Always

Steps to Reproduce:
Start KDE.

Actual Results:  
The notification appears.

Expected Results:  
KDE shouldn't display notifications unless they actually mean something to the user.
Comment 1 Daniel Welch 2011-12-27 08:45:58 UTC 
same here - I haven't configured kmail or other PIM as I use gmail via web. I have installed gmail-plasmoid notifier widget.
Comment 2 Tapani Tarvainen 2012-04-01 04:40:25 UTC 
Same here. Disabling akonadi server makes the message go away, but I'd like to know what that message actually means - what exactly triggers it.
Cf.
http://forum.kde.org/viewtopic.php?f=20&t=97385
Comment 3 Denis Kurz 2016-09-24 20:43:08 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:31:02 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.