Bug 144816 - no pop access via dialup connection
Summary: no pop access via dialup connection
Status: RESOLVED DUPLICATE of bug 130472
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-29 09:17 UTC by Edwin Boersma
Modified: 2007-04-29 18:35 UTC (History)
0 users

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 Edwin Boersma 2007-04-29 09:17:04 UTC 
Version:           1.9.5 (using KDE 3.5.5 "release 45.4" , openSUSE 10.2)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.8-0.1-default

Hi,

Kmail seems to fail on accessing my pop accounts when I'm on a dial up connection. Via wireless and cable connections, it works well.

Accessing local accounts is ok, but it seems the external pop accounts are not even accessed. Kwallet doesn't come up, and there is no message in the status bar.
I tried starting kontact from the command line to get some debug info but there is no information when I click the "retrieve mail" button.


Rgds,
Edwin
Comment 1 Edwin Boersma 2007-04-29 09:27:24 UTC 
I found Bug 130472 that explains what is happening....
Comment 2 Edwin Boersma 2007-04-29 09:44:08 UTC 
I found Bug 130472 that explains what is happening....

But Kmail (or Kontact) does not detect that the system is in offline mode. Is this a bug?
Comment 3 Edwin Boersma 2007-04-29 09:44:47 UTC 
Needs reopening.
Comment 4 Thomas McGuire 2007-04-29 18:35:50 UTC 
>But Kmail (or Kontact) does not detect that the system is in offline mode. Is this a bug? 
Yes, this is a bug, but bug 130472 like you mentioned before. KMail actually seems to ask a KDED module for the networkstatus. KNetworkmanager fails to tell that KDED module that the system is online. So it is a KNetworkmanager bug, and I am marking this a as duplicate of bug 130472.

If bug 130472 gets fixed and this problem here remains, please reopen.

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