Bug 36083

Summary: distinguish mail/cyrus/mailbox/delete and mail/cyrus/sharedfolder/delete
Product: UCS Reporter: Janis Meybohm <meybohm>
Component: MailAssignee: Mail maintainers <mail-maintainers>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P5 CC: gohmann, jmm, troeder
Version: UCS 4.1   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
What kind of report is it?: Security Issue What type of bug is this?: ---
Who will be affected by this bug?: --- How will those affected feel about the bug?: ---
User Pain: Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional):
Max CVSS v3 score:
Bug Depends on: 34165    
Bug Blocks:    

Description Janis Meybohm univentionstaff 2014-10-07 09:00:15 CEST 
+++ This bug was initially created as a clone of Bug #34165 +++

Shared folders are not removed on delete in UMC if mail/cyrus/mailbox/delete set to "no". This is okay in first place but it leads to situations where the Administrator removes the folder and it is still accessible and useable for the users (e.g. still showing up in mail client) because the ACLs do not get removed either.

I think we should add another UCRV like "mail/cyrus/sharedfolder/delete" so that the administrator may configure different behaviour for user mailboxes and shared folders.
In addition to that we should wipe out all ACLs if "mail/cyrus/sharedfolder/delete=no".
Comment 1 Daniel Tröder univentionstaff 2016-10-14 08:58:31 CEST 
Security issue, because "deleted" mail is still accessable.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:22:25 CET 
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.