Bug 296389 - Entire local trash folder moved to local inbox
Summary: Entire local trash folder moved to local inbox
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.8
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-19 21:09 UTC by Russ Kepler
Modified: 2017-01-07 22:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Russ Kepler 2012-03-19 21:09:40 UTC
I'm not sure of the exact trigger but something moved all 5000+ messages from my local folders trash to my local folders inbox.  It seemed to happen about the time I was manually running filters on "incoming" maildir.  My configuration seems foreign to KMail2 when it was natural in KMail - I have a mail server handling my domain, it used to deliver mail to the mail spool directory and KMail picked it up.  With KMail2 I have to have postfix deliver to procmail that then delivers to my "incoming" directory where I'd like to have KMail2 filter it to the appropriate local folder.  With filtering not reliable I've been manually running the filters against the incoming maildir, but after spending a hour resorting trash out of my inbox I'm not even comfortable doing that...

In case it matters:
Qt: 4.8.0
KDE Development Platform: 4.8.1 (4.8.1)
KMail: 4.8.0
Comment 1 Unknown 2013-01-23 10:12:37 UTC
Please, make a control with "akonadi console"
Choose "DB Browser", "collectiontable", "Refresh"
Get a look to the column "remoteId".
Are there any cell(s) with nothing? If yes, let me/us know by copying the raw(s).
Comment 2 Russ Kepler 2013-01-24 00:24:16 UTC
Error is pretty old so the bug might simply need closing.  In any event, the only row with a blank remoteId is my search folder which I usually keep empty.
Comment 3 Denis Kurz 2016-09-24 18:22:45 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:10:23 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.