Bug 40608 – control smtpd_sender_restrictions via main.cf

Bug 40608 - control smtpd_sender_restrictions via main.cf


Summary:	control smtpd_sender_restrictions via main.cf

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:
Blocks:	40609
	Show dependency tree / graph

Reported:	2016-02-09 14:47 CET by Jens Thorp-Hansen
Modified:	2019-01-03 07:23 CET (History)
CC List:	2 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?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.011
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016020921000214
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 Jens Thorp-Hansen

2016-02-09 14:47:28 CET

controlling smtpd_sender_restrictions in the main.cf of postfix is not possible anymore:

"""
# smtpd_sender_restrictions is not defined since all relevant checks have been
# moved to smtpd_recipient_restrictions (see below) and every mail has to pass
# smtpd_recipient_restrictions too.
#smtpd_sender_restrictions =
"""

Customer asks if smtpd_sender_restrictions will be optionally controllable in the main.cf in the future.

Ticket#2016020921000214

Comment 1 Stefan Gohmann

2019-01-03 07:23:50 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.