Hi hefee, I strongly assume that it makes no sense if I _currently_ would test my PIM environment in the current Debian testing release because the behavior described in this bug issue did not occur anymore since the last time I updated this bug issue on Wed, 27 Feb 2019.
This is now the 5th day after Wed, 27 Feb 2019 that the behavior did not occur again. Before that, between Sunday, 24th 2019 and Wed, 27 Feb 2019, the behavior occurred very often. let's say about 30 times. Since Wed, 27 Feb 2019 I installed at least one system update via apt-get, could it be that this update resolved the behavior? I cannot remember which package this update updated. Or could it be that a misconfiguration of one of the remote mail servers which I am utilizing, or a erroneous software environment the respective mail server is running in, temporary could caused the behavior? I will report new occurrences of the behavior in this bug issue, but I do not know when these occurrences will happen again. Regards, Jens Am Sonntag, 3. März 2019, 22:41:51 CET schrieb Sandro Knauß: > Control: tags -1 +moreinfo > Control: reassign -1 kdepim-runtime 4:16.04.2-2+b2 > Control: forcemerge -1 900957 > > Thanks for reporting the issue and sorry for not responding for so long > time. > > The bug is actually in the maildir_resource that is shipped within kdepim- > runtime package, that why reassign the bug. > > It would be super great if you could test your setup with kmail on Debian > Buster, that is currently in testing. Because kdepim fixed serveral issues > for maildir resource. > > hefee