Bug 175325 - kmail gives message: "Unknown host Temporary failure in name resolution"
Summary: kmail gives message: "Unknown host Temporary failure in name resolution"
Status: RESOLVED DUPLICATE of bug 172130
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.10.90
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-16 20:42 UTC by Cyrill Helg
Modified: 2010-02-02 01:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cyrill Helg 2008-11-16 20:42:49 UTC
Version:           1.10.90 (using 4.1.72 (KDE 4.1.72 (KDE 4.2 >= 20081104)), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.27-zen3-IBM-T43

Actually kmail should detect if there is an internet connection available or not. However it does show the message periodically if I'm not connected.

Unknown host Temporary failure in name resolution

That message should imho be supressed.
Comment 1 Jaime Torres 2008-11-19 16:46:18 UTC
Hello,

  It is almost impossible to know if there is an internet connection available or not (by router, by USB, by ethernet ....). It is possible to know if you can reach a machine or not, or if you can reach your dns server or not (the message you get).

  By the way, the message is a message box you have to click or a popup window that dissapears after some time?
Comment 2 Cyrill Helg 2008-11-19 17:26:34 UTC
I thought that solid should be able to do that? I mean for normal mail checking this works great since kde4. Its just this only message. (message box btw)
Comment 3 Jaime Torres 2008-11-19 20:55:12 UTC
The wish is to add a checkbox like "don't inform me anymore" in the message box, or transform the message box into an informative popup.
Comment 4 Björn Ruberg 2010-02-02 01:11:45 UTC

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