Bug 59748

Summary:	disable notification messages when IMAP server not reacheable
Product:	[Unmaintained] kmail	Reporter:	Jonathan Felder <felder>
Component:	IMAP	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	bjoern, kde-bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	use_knotify_to_display_imap_errors.diff

Description Rolf Hillen 2003-06-13 21:52:33 UTC

Version:            (using KDE KDE 3.1.2)
Installed from:    Unspecified

When an IMAP server is not reacheable, kmail pops up a notification message.

Since this happens frequently in my environment (and partly by intention), these messages can be very annoying, especially as they push themselves in the foreground.

I suggest a checkbox in the preferences dialog  to enable/disable these messages, maybe separately for each imap server.

Comment 1 Ingo Klöcker 2003-06-14 00:58:28 UTC

Subject: Re:  New: disable notification messages  when IMAP server not reacheable

I wanted to make the type of notification configurable. As I'm using an 
unreliable IMAP server myself I wrote the attached hack which replaces 
the annoying popup dialog with a much less annoying passive popup. If 
you compile KMail yourself you might want to apply this patch. Else you 
will have to wait for KDE 3.2.


Created an attachment (id=1787)
use_knotify_to_display_imap_errors.diff

Comment 2 Stephan Kulow 2004-06-01 11:44:07 UTC

Replaced rhillen@tiscali.de with felder@path.berkeley.edu due to bounces by reporter

Comment 3 Ritesh Raj Sarraf 2007-08-08 23:11:25 UTC

It makes sense to implement this.

A user can have multiple account out of which some account will be requiring a vpn connection. Not having this option means that the user is required to be connected to vpn while using kmail to avoid these annoying popup dialogs.

I'd request for a notifier in the bottom pane of kmail where the last connect message is displayed.

Comment 4 Ritesh Raj Sarraf 2008-03-24 09:39:11 UTC

Hi, Please. Can this be fixed with the 4.1 release ?

Comment 5 Ritesh Raj Sarraf 2009-08-31 10:42:07 UTC

How do I close it as a duplicate ?

This issue is already fixed in #39097

Comment 6 Björn Ruberg 2009-12-18 01:17:34 UTC

Doing it for you

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