Resolved Re: Kmail won't send. Thanks

[Steven Vollom]

On Thursday 14 January 2010 07:29:47 pm Reinhold Rumberger wrote:
> On Thursday 14 January 2010, Steven Vollom wrote:
> > On Thursday 14 January 2010 08:19:09 am Lindsay Mathieson wrote:
> > > On Thu, 14 Jan 2010 12:02:32 am Steven Vollom wrote:
> > > > When I checked configuration, the sending smtp port had
> > > > changed from 465 to 25
> > >
> > > Rather than set the port you probably need to choose the "SSL"
> > > option which will also set the port for you.
> > >
> > > > and the password space was blank.  I successfully
> > > > changed the port number back, however, the 'apply' feature
> > > > does not activate  to set the password.
> > >
> > > Under the "Advanced" Tab did you check the "Server requires
> > > Authentication" box?
> >
> > Dear Lindsay,
> >
> > I just installed to SSL bug fixes and kmail started to work
> > properly again.  I am a bit confused, however, because the dots
> > that usually appear in the password box in smtp are not present
> > and when entering them "Apply" does NOT appear for setting the
> > application.  Also, I do not remember setting the password
> > recently, so it may have been taken from elsewhere.  This is a
> > bit confusing, but I am pleased that kmail seems to be working
> > again.  This reply is using kmail.
> 
> Linux is a multi-user system. Removing a system application will not
> remove your user-specific configuration. What you want to do is back
> up ~/.kde/share/config/emailidentities, ~/.kde/share/config/kmail*
> and ~/.kde/share/apps/kmail/. Unless I'm forgetting something,
> removing those files and that directory will clear your KMail
> configuration. After that, you simply have to start KMail (no re-
> starting the system or anything) to get an unconfigured KMail.
> 
> Just to be on the safe side: "~/.kde/share/config/kmail*" means all
> files beginning with "kmail" in the directory "~/.kde/share/config/".
> 
>   --Reinhold
   Today, two SSL bug fixes were installed.   I immediately had a working 
system.  Lindsay had it pretty good when she suggested it probably was a SSL 
problem.  I really don't know the fix, so I can't share anything.  Thanks all 
for helping me.

Steven