problem with dialup, Kinternet, Kmail
Running 9.1 with KDE 3.3.0 with dialup. I am using Kmail and since years I have had no problems whatshowever. I have the feeling that my ISP is playing around with their server but they deny that this is the case. Since two days dialing goes fine but after some waiting I get the message that the pop.indo.net.id could not be found. This pop server is the one which is included in my Kmail setup since years. If I okay the error message I can connect to my ISP pop server without any problems. Is there a method to make visible what the ISP is expecting instead of the (my) usual input? Why can I connect the second time without problems? Is my ISP the second time not receiving the string pop.indo.net.id? The actual problem is not severe but prevents me from an automated download of my email at hourly intervals. And by the way, I am also not able to send email after having made the connection. Unknown host: smtp.indo.net.id not found.
On Mon November 1 2004 7:18 am, Constant Brouerius van Nidek wrote:
Running 9.1 with KDE 3.3.0 with dialup. I am using Kmail and since years I have had no problems whatshowever. I have the feeling that my ISP is playing around with their server but they deny that this is the case. Since two days dialing goes fine but after some waiting I get the message that the pop.indo.net.id could not be found. This pop server is the one which is included in my Kmail setup since years. If I okay the error message I can connect to my ISP pop server without any problems. Is there a method to make visible what the ISP is expecting instead of the (my) usual input? Why can I connect the second time without problems? Is my ISP the second time not receiving the string pop.indo.net.id? The actual problem is not severe but prevents me from an automated download of my email at hourly intervals. And by the way, I am also not able to send email after having made the connection. Unknown host: smtp.indo.net.id not found.
I am having the same problem with kmail authentication on sending only with cable modem not dialup. I have narrowed it down to a kmail memory resident problem. Not sure what is getting confused but a reboot brings it back to authenticating on sending email again. This has been happening for several SUSE versions and many KDE/kmail versions. I can go days, weeks, months without an authentication problem and then it just happens. Before rebooting I've verified that its not an ISP issue by using Evolution or Mozilla mail or Thunderbird with the same ISP email settings and they work no problem. My resolution so far is to reboot. Neither a login/logout of the user, a restart of kdm/X has worked. This happens on several different machines with different versions of SUSE and KDE and kmail. All the same ISP with different user accounts. I haven't narrowed it down any more than this. It took quite a long time to get this far. Stan
On Monday, 1 November 2004 15.57, SRGlasoe wrote:
My resolution so far is to reboot. Neither a login/logout of the user, a restart of kdm/X has worked. This happens on several different machines with different versions of SUSE and KDE and kmail. All the same ISP with different user accounts. I haven't narrowed it down any more than this. It took quite a long time to get this far.
Hmm. Is nscd running? If it is, the next time it happens, try shutting it off (rcnscd stop) instead of rebooting
On Monday 01 November 2004 22:06, Anders Johansson wrote:
On Monday, 1 November 2004 15.57, SRGlasoe wrote:
My resolution so far is to reboot. Neither a login/logout of the user, a restart of kdm/X has worked. This happens on several different machines with different versions of SUSE and KDE and kmail. All the same ISP with different user accounts. I haven't narrowed it down any more than this. It took quite a long time to get this far.
Hmm. Is nscd running? If it is, the next time it happens, try shutting it off (rcnscd stop) instead of rebooting
My problem does not seem to have a connection with the name server cache demon. No difference at my side. Any other ideas?
On Monday, 1 November 2004 16.25, Constant Brouerius van Nidek wrote:
On Monday 01 November 2004 22:06, Anders Johansson wrote:
On Monday, 1 November 2004 15.57, SRGlasoe wrote:
My resolution so far is to reboot. Neither a login/logout of the user, a restart of kdm/X has worked. This happens on several different machines with different versions of SUSE and KDE and kmail. All the same ISP with different user accounts. I haven't narrowed it down any more than this. It took quite a long time to get this far.
Hmm. Is nscd running? If it is, the next time it happens, try shutting it off (rcnscd stop) instead of rebooting
My problem does not seem to have a connection with the name server cache demon. No difference at my side. Any other ideas?
No, your problem is due to a bug in kmail, I see it too on occasion. I suspect it's one of the kio_ slaves that dies for some reason. When you download a second time it gets restarted and everything works. I haven't invested a great deal of time in finding the reason for it, but I'm pretty sure the problem is a bug in KDE Stan's problem is something else though
On Mon November 1 2004 9:06 am, Anders Johansson wrote:
On Monday, 1 November 2004 15.57, SRGlasoe wrote:
My resolution so far is to reboot. Neither a login/logout of the user, a restart of kdm/X has worked. This happens on several different machines with different versions of SUSE and KDE and kmail. All the same ISP with different user accounts. I haven't narrowed it down any more than this. It took quite a long time to get this far.
Hmm. Is nscd running? If it is, the next time it happens, try shutting it off (rcnscd stop) instead of rebooting
nscd is running. What's the theory? I will try your suggestion IF it ever happens again. Could be months, could be today, could be tomorrow. I may have a way to produce the error "on demand" but it seems to require leaving kmail up and running overnight; system has to go through the midnight hour and any cron or other system checks that happen after midnight and are usually finished by 5AM. Stan
On Monday, 1 November 2004 16.29, SRGlasoe wrote:
On Mon November 1 2004 9:06 am, Anders Johansson wrote:
On Monday, 1 November 2004 15.57, SRGlasoe wrote:
My resolution so far is to reboot. Neither a login/logout of the user, a restart of kdm/X has worked. This happens on several different machines with different versions of SUSE and KDE and kmail. All the same ISP with different user accounts. I haven't narrowed it down any more than this. It took quite a long time to get this far.
Hmm. Is nscd running? If it is, the next time it happens, try shutting it off (rcnscd stop) instead of rebooting
nscd is running. What's the theory?
the theory is that something about your system changes that is so severe that a simple log out/log in won't cure it. I'm not saying it *definitely* is, but nscd is the usual suspect in these cases. Something that it caches changes, and since your system gets it from nscd instead of from the actual source, it doesn't see the change. Stopping nscd forces your system to get the real data from the actual source If it doesn't work, we'll have to come up with a second theory, but for now this is my guess
I will try your suggestion IF it ever happens again. Could be months, could be today, could be tomorrow. I may have a way to produce the error "on demand" but it seems to require leaving kmail up and running overnight; system has to go through the midnight hour and any cron or other system checks that happen after midnight and are usually finished by 5AM.
Yeah, I hate those erratic errors that you never know when they'll happen. They're a real PITA to debug
On Monday 01 November 2004 22:06, Anders Johansson wrote:
On Monday, 1 November 2004 15.57, SRGlasoe wrote:
My resolution so far is to reboot. Neither a login/logout of the user, a restart of kdm/X has worked. This happens on several different machines with different versions of SUSE and KDE and kmail. All the same ISP with different user accounts. I haven't narrowed it down any more than this. It took quite a long time to get this far.
Hmm. Is nscd running? If it is, the next time it happens, try shutting it off (rcnscd stop) instead of rebooting
Looking further into my problem I tend to think that it is my ISP. Running the Network Kmail setup /receiving extras I found that if I used check what the provider wants (or something like that) it wanted to have APOP. Until now it was just plain text what was required. APOP (whatever that is) though does not seem to function properly because I receive following error message: Login via APOP failed. The server may not support APOP, although it claims to support it, or the password may be wrong. The server terminated the connection. I have not tried out other mail programs because up to now I am quit happy with Kmail.
On Monday, 1 November 2004 16.50, Constant Brouerius van Nidek wrote:
Looking further into my problem I tend to think that it is my ISP. Running the Network Kmail setup /receiving extras I found that if I used check what the provider wants (or something like that) it wanted to have APOP. Until now it was just plain text what was required. APOP (whatever that is) though does not seem to function properly because I receive following error message:
Login via APOP failed. The server may not support APOP, although it claims to support it, or the password may be wrong. The server terminated the connection.
But this wasn't the error you talked about in the original post. Like I said, I get those "unknown host" errors too from time to time, even though both my DNS and POP is on my local LAN. I'm 99% certain it's a KDE/KMail bug
On Mon November 1 2004 10:05 am, Anders Johansson wrote:
On Monday, 1 November 2004 16.50, Constant Brouerius van Nidek wrote:
Login via APOP failed. The server may not support APOP, although it claims to support it, or the password may be wrong. The server terminated the connection.
But this wasn't the error you talked about in the original post.
Like I said, I get those "unknown host" errors too from time to time, even though both my DNS and POP is on my local LAN. I'm 99% certain it's a KDE/KMail bug
Agreed. I see those same errors saying the ISP's servers don't do the last known working protocol or my password is wrong even though kmail's settings haven't changed. Once in a while I do have success by changing kmail's Network, Sending Options, Authentication Method from/to plain, login or md-5 and/or changing the Encryption Method from/to none or tls. I think we are all seeing the same problem. Stan
On Monday, 1 November 2004 17.42, SRGlasoe wrote:
On Mon November 1 2004 10:05 am, Anders Johansson wrote:
On Monday, 1 November 2004 16.50, Constant Brouerius van Nidek wrote:
Login via APOP failed. The server may not support APOP, although it claims to support it, or the password may be wrong. The server terminated the connection.
But this wasn't the error you talked about in the original post.
Like I said, I get those "unknown host" errors too from time to time, even though both my DNS and POP is on my local LAN. I'm 99% certain it's a KDE/KMail bug
Agreed. I see those same errors saying the ISP's servers don't do the last known working protocol or my password is wrong even though kmail's settings haven't changed. Once in a while I do have success by changing kmail's Network, Sending Options, Authentication Method from/to plain, login or md-5 and/or changing the Encryption Method from/to none or tls.
I think we are all seeing the same problem.
I wonder. I don't have to reboot to fix my problem. I don't even have to log out, all I have to do is try again to make it work. Could that really be the same bug you're seeing?
On Mon November 1 2004 10:56 am, Anders Johansson wrote:
On Monday, 1 November 2004 17.42, SRGlasoe wrote:
On Mon November 1 2004 10:05 am, Anders Johansson wrote:
On Monday, 1 November 2004 16.50, Constant Brouerius van Nidek wrote:
Login via APOP failed. The server may not support APOP, although it claims to support it, or the password may be wrong. The server terminated the connection.
But this wasn't the error you talked about in the original post.
Like I said, I get those "unknown host" errors too from time to time, even though both my DNS and POP is on my local LAN. I'm 99% certain it's a KDE/KMail bug
Agreed. I see those same errors saying the ISP's servers don't do the last known working protocol or my password is wrong even though kmail's settings haven't changed. Once in a while I do have success by changing kmail's Network, Sending Options, Authentication Method from/to plain, login or md-5 and/or changing the Encryption Method from/to none or tls.
I think we are all seeing the same problem.
I wonder. I don't have to reboot to fix my problem. I don't even have to log out, all I have to do is try again to make it work. Could that really be the same bug you're seeing?
Maybe, maybe not. I have success like yours sometimes but lately its required a reboot. I do the baby steps of quitting KMail, waiting 5-10 minutes, restarting it. If no go, proceed to try different authentication methods one at a time to see what may work this time. Sometimes, but not always, if I don't do anything the problem goes away by itself after hours between sending attempts. My impatience combined with needing to get a time sensitive email response in or out usually won't allow me to wait. Almost every time it happens there is a different resolution. The reboot is the sure fire method that I know works to reset everything without changing any settings anywhere. That's why its taken me so long to define what I've seen, the methods I've used to isolate the issue, etc. I've seen this occurring since SUSE 8.0 or 8.1 and all the versions of KDE and kmail up to SUSE 9.1, KDE 3.3.0 and kmail 1.7. On very different hardware also. I really think its KDE/kmail. Still waiting to test the ncsd theory here though. And "Thanks Anders" for helping to tackle this one. I need someone with your expertise to do the sanity check on my troubleshooting methods and suggesting things to check.
participants (3)
-
Anders Johansson
-
Constant Brouerius van Nidek
-
SRGlasoe