First of all: sorry but I'm italian and so, many received messages are in my language. Anyway...when I try to connect to the IMAP server to retrieve messages but it's unable to receive new connections because too many already exists (dovecot server), I receive (correctly) an alert box that say: -------------------------------------- Il server dell'account «MyAccount» ha rifiutato il nome utente e la password forniti. Vuoi modificare le impostazioni, riprovare nuovamente ad accedere, o non fare nulla? Login failed, server replied: A000003 NO Maximum number of connections from user+IP exceeded ( mail_max_userip_connections ) -------------------------------------- This happens too much. I receive infinite number of popup box (Approximatively 100. After that, I've rebooted my pc) All alert boxes are identical and I'm no more able to proceed to use my pc. Reproducible: Always Steps to Reproduce: 1. Connect with hostA (my andoid phone in push mode) to the IMAP server and occupies all the available connections 2. Open Kmail (to trigger akonadi) and try to dowload the messages 3. Done Actual Results: You receive the infinite alert boxes reporting the unavailability to connect Expected Results: A single box reporting the error. Full stop. (Better can be to use kde notification system)
I can confirm this on KDE 4.11. After creating an IMAP account I get infinite amount of pop-ups saying "The server rejected the username and password account provided. Do you want to go to the settings, trying to re-enrollment or to do nothing. Login failed, server replied: A000002 NO IMAP4 access not allowed." Pop-ups will make my computer freeze and have to reboot and same thing happens when trying to log back to KDE when it tries to check for new emails. Removing line "akonadi_imap_resource_X\AgentType=akonadi_imap_resource" in /.config/akonadi/agentsrc makes it possible to boot to KDE again. Connecting to account probably failed due some wrong setting, since it didn't succeed in Thunderbird either.
Just happened to me a while ago. The dialog is not modal, so you can get tons of them at once. The cause is probably that all sessions failed at once and the requests accumulated.
*** Bug 325516 has been marked as a duplicate of this bug. ***
*** Bug 326045 has been marked as a duplicate of this bug. ***
Short snipped from my xsession-errors (I actually used akonadictl stop to exit Aknoadi but the dialogs still pop up): [...] A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" plasma-desktop(3037)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" A message was received from the server with no job to handle it: "* BYE Zimbra IMAP server terminating connection " "(2a20425945205a696d62726120494d415020736572766572207465726d696e6174696e6720636f6e6e656374696f6e2 0)" Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_sendlater_agent' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_maildispatcher_agent' exited normally... Application '/usr/bin/akonadi_davgroupware_resource' exited normally... QProcess: Destroyed while process is still running. ProcessControl: Application /usr/bin/akonadi_imap_resource stopped unexpectedly ( "Process crashed" ) Application '/usr/bin/akonadi_imap_resource' crashed. No restart! Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_mailfilter_agent' exited normally... Application '/usr/bin/akonadi_archivemail_agent' exited normally... QProcess: Destroyed while process is still running. ProcessControl: Application /usr/bin/akonadi_imap_resource stopped unexpectedly ( "Process crashed" ) Application '/usr/bin/akonadi_imap_resource' crashed. No restart! QProcess: Destroyed while process is still running. ProcessControl: Application /usr/bin/akonadi_imap_resource stopped unexpectedly ( "Process crashed" ) Application '/usr/bin/akonadi_imap_resource' crashed. No restart! ProcessControl: Application /usr/bin/akonadi_imap_resource stopped unexpectedly ( "Process crashed" ) Application '/usr/bin/akonadi_imap_resource' crashed. No restart! Application '/usr/bin/akonadi_newmailnotifier_agent' exited normally... Application '/usr/bin/akonadi_nepomuk_feeder' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... plasma-desktop(3037)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed" plasma-desktop(3037)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed" krunner(3445)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed" kmail2(4113)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed" kmail2(4113)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed" Application 'akonadiserver' exited normally...
Have a look at attchment 82858 from bug 326045 for a beautiful screenshot.
The IMAP resource has a new maintainer, reassigning to him.
*** Bug 328474 has been marked as a duplicate of this bug. ***
*** Bug 328061 has been marked as a duplicate of this bug. ***
same problem in Fedora 20 with the imap account of my ISP (telecomitalia.it) which doesn't allow to access imap outside its net, so either when I'm travelling or when I'm at work with my ultrabook I will get hundreds error windows as soon as I get Internet access
Git commit a13c4655ea54d9902d98d97c11b5e4ba996bbceb by Christian Mollekopf. Committed on 23/03/2014 at 17:37. Pushed by cmollekopf into branch 'KDE/4.13'. IMAP-Resource: Async dialogs. Async password request dialog that is aborted after disconnecting. This properly aborts the dialog after the connection attempt is no longer relevant, and avoids the stacking of dialogs. The configuration dialog is also made async to avoid similar problems. With this change the dialog appears at most once, and vanishes if the network is disconnected again. Related: bug 306955 M +16 -12 resources/imap/imapresource.cpp M +3 -1 resources/imap/imapresource.h M +3 -0 resources/imap/passwordrequesterinterface.cpp M +1 -0 resources/imap/passwordrequesterinterface.h M +7 -0 resources/imap/sessionpool.cpp M +1 -0 resources/imap/sessionpool.h M +69 -20 resources/imap/settingspasswordrequester.cpp M +8 -0 resources/imap/settingspasswordrequester.h http://commits.kde.org/kdepim-runtime/a13c4655ea54d9902d98d97c11b5e4ba996bbceb
Thank you Christian, but is there a way to implement this solution right now? Because this bug really drives me crazy at the moment. Or do I have to wait for the 4.13 release on April 16th?
(In reply to comment #12) > Thank you Christian, > > but is there a way to implement this solution right now? Because this bug > really drives me crazy at the moment. Or do I have to wait for the 4.13 > release on April 16th? Unfortunately you'll have to wait. But there might be release candidate packages for your distributions, which would also allow you to give me feedback in case you're not yet happy with the solution.