Hej there,

Recently my imap account from an MS exchange server suddenly stopped working. In KMail the account's folders are all grayed out, in akonadiconsole I can see the ressource offline. If I toggle it back online, it goes offline after a while again without giving any output.
When I configure the account, the "Connection settings->Auto detect"-Button in the advanced options results in the error "Unable to connect to the server, please verify the server address."

However, the server address is definitely correct. I didn't change it and with Thunderbird the same address works perfectly well.

Any ideas? Anybody experiencing the same problem?

Cheers
locke

Is any relevant debug output given in ~/.xsession-errors with regards to this issue?

When setting the resource to online, the only according message I can find is

Code: Select all

akonadi_imap_resource_17(3378)/kdepimlibs (kimap) KIMAP::SessionPrivate::onSocketTimeout: Socket timeout!

where akonadi_imap_resource_17 is the resource of concern.

It appears that the IMAP connection to the Exchange server is timing out. Can you please verify the port set in Kontact is correct?

The port is correctly set to 993 as it is in working thunderbird.

Unusual. If you try to recreate it, does that work?

I suspect something may be wrong with either the server name or port number, so if possible please reconfigure those in case it is a configuration loading/saving problem.

I tried that already. Unfortunately same result here.

I would recommend consulting with your network administrator then - KDE definitely seems to not be able to connect - and if you still cannot get it to connect, even with a new resource then something must not be correct in the settings you are trying to use.

It may be a coincidence that Thunderbird works - as it could be using a different type of encryption.

Im seeing a similar problem, exchange agent goes offline. Can manually set it online and email syncs normally for maybe a few hours and then goes silently offline again. This behaviour is regular since 4.8.2.

Please report a bug at bugs.kde.org, as this should not occur.