Bug 332491

Summary: Clicking deleting the message does not go automatically to the trash
Product: [Applications] kmail2 Reporter: it
Component: commands and actionsAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: montel
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description it 2014-03-24 06:37:51 UTC
Clicking deleting, the message does not go automatically to the trash.

Reproducible: Always
Comment 1 Laurent Montel 2014-03-27 19:55:24 UTC
?
What is your account type ?
Comment 2 it 2014-03-28 06:28:51 UTC
My account type is root

*Departamento IT*
Servicios de Apoyo al Derecho, S.L.
it@sad.es
T. +34 954 657 889
www.sad.es

El 27/03/2014 20:55, Laurent Montel escribió:
> https://bugs.kde.org/show_bug.cgi?id=332491
>
> Laurent Montel <montel@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |montel@kde.org
>
> --- Comment #1 from Laurent Montel <montel@kde.org> ---
> ?
> What is your account type ?
>
Comment 3 Laurent Montel 2014-03-28 06:40:34 UTC
no :)
your account is type imap/pop3/mbox/maildir :)
Comment 4 it 2014-03-28 06:41:30 UTC
sorry,
Is IMAP

*Departamento IT*
Servicios de Apoyo al Derecho, S.L.
it@sad.es
T. +34 954 657 889
www.sad.es

El 28/03/2014 7:40, Laurent Montel escribió:
> https://bugs.kde.org/show_bug.cgi?id=332491
>
> --- Comment #3 from Laurent Montel <montel@kde.org> ---
> no :)
> your account is type imap/pop3/mbox/maildir :)
>
Comment 5 Denis Kurz 2016-09-24 17:58:35 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 6 Denis Kurz 2017-01-07 22:31:24 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.