Bug 46858

Summary: delete on server after deleted in kmail
Product: [Unmaintained] kmail Reporter: Unknown <null>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: esigra
Priority: NOR    
Version: 1.4.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Bugzilla Maintainers 2002-08-23 20:41:50 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kmail
Version:           1.4.1 (using KDE 3.0.0 )
Severity:          wishlist
Installed from:    
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)
OS:                Linux (i686) release 2.4.18-3
OS/Compiler notes: 

Now the user can select between leaving the message on the server or deleting it on the server. But what I would like to be able to do is leave it on the server until I delete it in kmail then have kmail delete it on the server.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 Ingo Klöcker 2002-08-23 23:00:31 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 23 August 2002 22:41 pthomas@lclark.edu wrote:
> Package: kmail
> Version: 1.4.1 (using KDE 3.0.0 )
> Severity: wishlist
> Installed from:
> Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.3
> 2.96-110) OS:                Linux (i686) release 2.4.18-3
> OS/Compiler notes:
>
> Now the user can select between leaving the message on the server or
> deleting it on the server. But what I would like to be able to do is
> leave it on the server until I delete it in kmail then have kmail
> delete it on the server.

This is a duplicate.

Regards
Ingo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9Zr6PGnR+RTDgudgRAiEbAJ0cgveAB0HwxHnJyxVmXxpDaw0MbQCgwFry
Jf+Ay3zly4lTI8eqWwZmgy8=3D
=3DgA8w
-----END PGP SIGNATURE-----
Comment 2 Martin Köbele 2004-10-15 13:44:41 UTC
re-opening for marking as duplicated report
Comment 3 Martin Köbele 2004-10-15 13:45:09 UTC

*** This bug has been marked as a duplicate of 31114 ***