Bug 40349 - when restricting mailing lists, allow mail/lists::members to send to them
when restricting mailing lists, allow mail/lists::members to send to them
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Mail
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-30 09:46 CET by Daniel Tröder
Modified: 2019-01-03 07:21 CET (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
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.069
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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 Daniel Tröder univentionstaff 2015-12-30 09:46:36 CET
Currently only users in mail/lists::univentionAllowedEmailGroups and mail/lists::univentionAllowedEmailUsers are allowed to send to a mailinglist when mail/postfix/policy/listfilter=yes.

It is possible to add external email addresses as members, but there is no way to allow them to keep sending emails to the list, once mail/postfix/policy/listfilter=yes.

If an option were added (either per mailing list or globally (eg UCR)) to allow all members of a mailing list to send to it, then /usr/share/univention-mail-postfix/listfilter.py could be adapted to include mail/lists::members.
Comment 1 Stefan Gohmann univentionstaff 2016-12-13 08:10:41 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 Stefan Gohmann univentionstaff 2019-01-03 07:21:48 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.