Bug 193450

Summary:	kmail not checking email when manual checks are sent sometimes
Product:	[Unmaintained] kmail	Reporter:	rbees <thejunk.b>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bjoern
Priority:	NOR
Version First Reported In:	1.11.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description rbees 2009-05-21 05:02:07 UTC

Version:           1.11.2 (using 4.2.2 (KDE 4.2.2), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.26-2-amd64

even though the email servers (gmail & charter) are set to the correct settings at times k'"mail reports that it can't find the servers.  Most notably when manual checks are made and I try to send an email.  Intervel checking seams to work most of the time, although at times I to will report the servers are not avalible.

I have also noticed that when configuring the server settings the "check what server supports" button seams to be non-functional.  The button seams to be accessing the net fine, but not the manual mail check.

These problems did not exist before upgrading to the plasma workspace.

Comment 1 Björn Ruberg 2010-02-28 01:17:55 UTC

Do you still have this problem in more recent kmail versions?

Comment 2 rbees 2010-02-28 01:39:07 UTC

On Saturday 27 February 2010, Björn Ruberg wrote:
> https://bugs.kde.org/show_bug.cgi?id=193450
> 
> 
> Björn Ruberg <bjoern@ruberg-wegener.de> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - Status|UNCONFIRMED                 |NEEDSINFO
>                  CC|                            |bjoern@ruberg-wegener.de
>          Resolution|                            |WAITINGFORINFO
> 
> 
> 
> 
> --- Comment #1 from Björn Ruberg <bjoern ruberg-wegener de>  2010-02-28
>  01:17:55 --- Do you still have this problem in more recent kmail versions?
> 

Thanks for getting back to me on this.  It seems to be fixed.  In fact I 
forgot about it.  It may have also been related to not entering the account 
password correctly. ;)