Mailinglist Archive: opensuse (3964 mails)
| < Previous | Next > |
Re: [SLE] problem with dialup, Kinternet, Kmail
- From: SRGlasoe <srglasoe@xxxxxxxxxxx>
- Date: Mon, 1 Nov 2004 08:57:37 -0600
- Message-id: <200411010857.37961.srglasoe@xxxxxxxxxxx>
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
> 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
| < Previous | Next > |