https://bugs.kde.org/show_bug.cgi?id=320180
Daniel Vrátil dvra...@redhat.com changed:
What|Removed |Added
CC||dvra...@redhat.com
--
You
https://bugs.kde.org/show_bug.cgi?id=320180
Marc González Majoral gons...@gmail.com changed:
What|Removed |Added
CC||gons...@gmail.com
--
https://bugs.kde.org/show_bug.cgi?id=320180
Daniel Vrátil dvra...@redhat.com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=320180
--- Comment #5 from Thomas Kear thomas.k...@gmail.com ---
(In reply to comment #4)
This seems to me to be related to bug #316840.
I'm fairly confident bug 317790 is also describing the same issue, and possibly
bug 315382 too.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=320180
Ingo Stierand stier...@informatik.uni-oldenburg.de changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=320180
Thomas Kear thomas.k...@gmail.com changed:
What|Removed |Added
CC||thomas.k...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=320180
--- Comment #1 from miklos mtm...@freemail.hu ---
Created attachment 80068
-- https://bugs.kde.org/attachment.cgi?id=80068action=edit
wireshark-kmail.png
I monitored it with Wireshark for a while. It seems that immediately after
client hello the
https://bugs.kde.org/show_bug.cgi?id=320180
--- Comment #2 from miklos mtm...@freemail.hu ---
Now I see that I forgot the best part of it: interval mail checking is not
enabled, so it shouldn't even do anything in the first place. Especially if
kmail is already closed.
--
You are receiving this
