Bug 41022 - Shared_Folder - multiple issues
Shared_Folder - multiple issues
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Mail - Dovecot
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Mail maintainers
:
Depends on:
Blocks: 41138
  Show dependency treegraph
 
Reported: 2016-04-08 11:00 CEST by Jens Thorp-Hansen
Modified: 2019-01-03 07:23 CET (History)
5 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016032321000374, 2017012521000103
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Thorp-Hansen univentionstaff 2016-04-08 11:00:07 CEST
- The permissions "k" and "x" should be added to "all"

- It should be possible to create subfolder under shared_folders
--> suggestion: UCRV "mail_shared_explicit_inbox"

- "public_folder" and "shared_folder" should be handled the same way

Ticket#2016032321000374
Comment 1 Stefan Gohmann univentionstaff 2016-12-13 08:10:45 CET
The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.
Comment 2 Benjamin Fels univentionstaff 2017-01-25 15:10:15 CET
This bug was referenced in another customer project by one of our partners. Please see Ticket#2017012521000103.
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:23:55 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.