Bug 36083 – distinguish mail/cyrus/mailbox/delete and mail/cyrus/sharedfolder/delete

Bug 36083 - distinguish mail/cyrus/mailbox/delete and mail/cyrus/sharedfolder/delete


Summary:	distinguish mail/cyrus/mailbox/delete and mail/cyrus/sharedfolder/delete

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Mail
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	Mail maintainers
QA Contact:

URL:
Keywords:

Depends on:	34165
Blocks:
	Show dependency tree / graph

Reported:	2014-10-07 09:00 CEST by Janis Meybohm
Modified:	2019-01-03 07:22 CET (History)
CC List:	3 users (show)

See Also:
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:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Janis Meybohm

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

2016-10-14 08:58:31 CEST

Security issue, because "deleted" mail is still accessable.

Comment 2 Stefan Gohmann

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.