Re: KMail re-downloads POP3 emails that are supposed to be deleted
MoC <[email protected]> Sun, 18 May 2025 23:48:29 +0200
| Newsgroups | gmane.comp.kde.users.pim |
|---|---|
| Message-ID | <2548852.XAFRqVoOGU@mlptp> |
On Friday, May 16, 2025 10:37:02 PM CEST Ingo Kl=F6cker wrote: >=20 > You can write > ``` > export QT_LOGGING_RULES=3D"org.kde.pim.pop3resource.debug=3Dtrue" > ``` > in a file called enable-logging-of-pop3-resource.sh that you put into the= =20 > folder ~/.config/plasma-workspace/env >=20 > The logs will then be written to the journal which you can read with=20 > journalctl. >=20 Thanks! >=20 > In theory this should be possible by using the "DB Console" of akonadicon= sole,=20 > but I have no idea which query you'd have to use. >=20 I did not find anything resembling a UID in the DB Browser, but did realize that the Browser tab can show emails and display their Unique ID in the Internals tab. Weirdly enough, it only showed a small subset of my emails, even though it seems to have detected the correct amount of emails. >=20 > No idea. Maybe checking the status for being unread doesn't work. > While I failed to get the filter working, I did manage to delete all unread messages by using the quick filters and disabling messages I click on from being marked as "Read". Deleting them went more or less smoothly. KMail/Akonadi took a long time and failed the first time around. Afterwards, around 200 new duplicates appeared, even though I was working in offline mode, which I had to delete in small batches, otherwise some of them would always reappear. Before I emptied the trash, I checked Akonadi Console and noticed that I could now see some of the duplicate messages in the Trash folder. Unfortunately the duplicates had pairwise different Unique IDs, so the server may have indeed been messing things up. I deleted the emails on the server-side as well and am leaving logging enabled for the time being. Thanks for the help so far! Kind regards, MoC