Summary: | smtp sending transport failure | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | alexandra <lynx> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | kollix, lynx |
Priority: | NOR | ||
Version: | 1.12.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
alexandra
2009-11-17 07:02:32 UTC
to receive messages needed to change from ssl to no encryption. Have checked with my ISP and all the settings are correct Do I understand you correctly, you have fixed the issue by changing from SSL to no encryption? Yes all very weird - not sure where the fault lies. Will go back to the ISP and have them check their logs. KMail worked perfectly Sunday Nov 15. Then I reloaded the machine with Suse 11.2 Sunday eve. On Monday the ISP had a power outage. On Monday evening my other mail programs worked but not KMail. I like Kmail so... -- Alexandra Look To This Day! On Wed, 18 Nov 2009, Torgny Nyblom wrote: > https://bugs.kde.org/show_bug.cgi?id=214926 > > > > > > --- Comment #2 from Torgny Nyblom <kde nyblom org> 2009-11-18 13:17:11 --- > Do I understand you correctly, you have fixed the issue by changing from SSL to > no encryption? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > You reported the bug. > This is confusing. Your first report talks about SENDING. Your second entry talks about RECEIVING. Please try to explain in more detail what works and what doesn't, but please try to first define a new sending and receiving account just to be sure you entered all needed info and there is no problem with the upgrade to openSuse 11.2 (BTW: I also recently switched from 11.1 to 11.2 and had no problem) Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you! |