[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems

[John Andersen]

https://bugs.kde.org/show_bug.cgi?id=316107

John Andersen <jsamyth at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jsamyth at gmail.com

--- Comment #20 from John Andersen <jsamyth at gmail.com> ---
My 4.11.1 akonadi_imap_resource starts spamming our in-house mail server (Cyrus
Imap) anywhere for 5 minutes to 30 minutes after KDE-Kontact (Kmail) is
started.  It will persist after Kontact is shut down.  It *only* uses 15% cpu,
but floods the imap server with messages like this:
Sep  9 13:17:09 screenio imaps[16405]: starttls: TLSv1 with cipher AES256-SHA
(256/256 bits new) no authentication
Sep  9 13:17:09 screenio imaps[16408]: accepted connection
Sep  9 13:17:09 screenio imaps[16408]: mydelete: starting txn 2150652719
Sep  9 13:17:09 screenio imaps[16408]: mydelete: committing txn 2150652719
Sep  9 13:17:09 screenio imaps[16408]: mystore: starting txn 2150652720
Sep  9 13:17:09 screenio imaps[16408]: mystore: committing txn 2150652720
Sep  9 13:17:09 screenio imaps[16408]: starttls: TLSv1 with cipher AES256-SHA
(256/256 bits new) no authentication
Sep  9 13:17:09 screenio imaps[16403]: accepted connection
Sep  9 13:17:09 screenio imaps[16403]: mydelete: starting txn 2150652721
Sep  9 13:17:09 screenio imaps[16403]: mydelete: committing txn 2150652721
Sep  9 13:17:09 screenio imaps[16403]: mystore: starting txn 2150652722
Sep  9 13:17:09 screenio imaps[16403]: mystore: committing txn 2150652722
Sep  9 13:17:09 screenio imaps[16403]: starttls: TLSv1 with cipher AES256-SHA
(256/256 bits new) no authentication
Sep  9 13:17:09 screenio imaps[16408]: accepted connection
Sep  9 13:17:09 screenio imaps[16408]: mydelete: starting txn 2150652723
Sep  9 13:17:09 screenio imaps[16408]: mydelete: committing txn 2150652723
Sep  9 13:17:09 screenio imaps[16408]: mystore: starting txn 2150652724
Sep  9 13:17:09 screenio imaps[16408]: mystore: committing txn 2150652724
Sep  9 13:17:09 screenio imaps[16408]: starttls: TLSv1 with cipher AES256-SHA
(256/256 bits new) no authentication
Sep  9 13:17:09 screenio imaps[16403]: accepted connection
Sep  9 13:17:10 screenio imaps[16403]: mydelete: starting txn 2150652725
Sep  9 13:17:10 screenio imaps[16403]: mydelete: committing txn 2150652725
Sep  9 13:17:10 screenio imaps[16403]: mystore: starting txn 2150652726
Sep  9 13:17:10 screenio imaps[16403]: mystore: committing txn 2150652726

This will persist for hours, filling the logs on the server.  Its a one station
DOS attack.
It makes Kmail unusable. 

If I kill the akonadi_imap_resource  task, Kmail keeps operating normally, I
see server side message suggesting my Kmail logged in again


Sep  9 13:26:18 screenio imaps[16547]: starttls: TLSv1 with cipher AES256-SHA
(256/256 bits new) no authentication
Sep  9 13:26:18 screenio imaps[16547]: login: [192.168.2.232] jsa PLAIN+TLS
User logged in
Sep  9 13:26:18 screenio imaps[16547]: seen_db: user jsa opened
/var/lib/imap/user/j/jsa.seen
Sep  9 13:26:18 screenio imaps[16547]: open: user jsa opened INBOX
Sep  9 13:26:18 screenio imaps[16547]: open: user jsa opened INBOX
Sep  9 13:26:55 screenio master[3246]: process 15854 exited, status 0
Sep  9 13:26:55 screenio master[3246]: process 16548 exited, status 0
Sep  9 13:26:55 screenio master[16552]: about to exec /usr/lib/cyrus/bin/imapd

And it will work fine for a while.  A new aknodi_imap_resource will spawn, and
after 
another period of inactivity, it till will start dossing the imap server again. 

This has been going on for several KDE releases now.  Its time to fix this
guys!!

-- 
You are receiving this mail because:
You are the assignee for the bug.