Bug 38587 - delete mail on server if deleted local
Summary: delete mail on server if deleted local
Status: RESOLVED DUPLICATE of bug 31114
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.3.2
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-23 08:48 UTC by gebhard
Modified: 2007-09-14 12:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gebhard 2002-02-23 08:36:01 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kmail
Version:           1.3.2 (using KDE 2.2.2 )
Severity:          wishlist
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:                Linux (i686) release 2.4.10-4GB
OS/Compiler notes: 

Hi

it would be nice to have a third configuration for deleting mails on the email server: "delete mail on server if deleted locally"

I can think about two different implementations:

1. all mails which are deleted in KMail are deleted on the POP Server during the next email pass (this has the disadvantage that every mail which shoul stay on the server has to be left undeleted locally)

2. implement a second deletion mark: "delete on server and client" - advantage: you can delete every mail local and it will stay on the server (using the normal delete) but if you wish a mail to be deleted on both sides you can choose the new delete method

I would prefer option 2 - I haven't seen this feature on another email client yet - another plus for kmail ;)


(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 Michael H 2002-02-24 06:18:11 UTC
Please check for already filed wishlist items before submitting new ones.
Comment 2 Martin Köbele 2004-10-15 13:40:07 UTC
re-opening for marking as duplicated report
Comment 3 Martin Köbele 2004-10-15 13:40:54 UTC

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