Bug 206274 - Add system tray notification option to kmail for sending mail
Summary: Add system tray notification option to kmail for sending mail
Status: RESOLVED DUPLICATE of bug 115139
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-04 19:53 UTC by Fred Wells
Modified: 2009-12-22 03:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred Wells 2009-09-04 19:53:17 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Fedora RPMs

This has been a longstanding issue for me, going back to KDE3.  I don't really recall the disposition of the KDE3 feature request I had opened on this.  I think it fell stale for years and I finally closed it for lack of developer interest.  Thus, I'm reviving it here for KDE4.

Anyway, the problem remains that kmail provides no progress/status indicator when sending mail from an external application (e.g. digiKam).  Users have absolutely no clue as to the delivery status of the mail without taking the unnecessarily time consuming steps of opening kmail and checking outgoing/sent-mail folders.  This is particularly problematic for failed deliveries.   While it is possible to add a filter to play a sound upon sent mail success, this is hardly intuitive and still gives no visual indication.

Therefore, I recommend taking advantage of KDE4's new System Tray Notifications and Jobs component as a Notification "option" for kmail.  In this way, when configured, mail sent either from within kmail or externally (from digikam, for example) can provide the user with a useful progress/status indicator.  Perhaps it could/should be handled in a similar manner as file transfers are to/from konqueror.
Comment 1 Jonathan Thomas 2009-12-22 03:44:12 UTC

*** This bug has been marked as a duplicate of bug 115139 ***