Bug 53610

Summary: Extremely annoying pop-up windows
Product: [Unmaintained] kmail Reporter: Stefan Kebekus <stefan.kebekus>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: CLOSED DUPLICATE    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Stefan Kebekus 2003-01-29 20:38:23 UTC 
Version:            (using KDE KDE 3.1)
Installed from:    Compiled From Sources

Thank you for producing this great program.

I use the IMAP server of a big freemailer for reading my mail. When I am abroad and have a bad internet connection, the connection to that server goes down once in a while. In that case, KMail pops up a window "Connection to host ... is broken". The virtual desktop is switched to KMail, and the KMail window moves to the front.

I find this extremely annoying, because this message shows quite often, and it completely disrupts my workflow. In practise, I have to switch off KMail whenever I want to type a document, for example.

A less intrusive warning message (perhaps a passive popup) would be greatly appreciated.

Thanks,

Stefan Kebekus.
Comment 1 Daniel Lyddy 2003-07-21 20:57:20 UTC 
I agree, but I think that it would be better if you could disable this
"Connection to host ... is broken" popup on a server-by-server basis as well as
globally.  

I use one server that is extremely reliable, and I want to know when I have lost
a connection to it.  I use another one that disconnects so often, it would be
less intrusive to report when it's actually connected.  This second server is
way out of my control, but I still have to use it occasionally for a very good
reason.  Disabling automatic checking on this unreliable server is not an option
because I need to know as soon as possible when someone has sent email to this
second address.

Thanks again,
Dan
Comment 2 Ismail Donmez 2004-07-22 18:48:15 UTC 
Less annoying message boxes -> Dup of bug #50605

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