Bug 38024 – Use postfix-policyd for sender limitations

Bug 38024 - Use postfix-policyd for sender limitations


Summary:	Use postfix-policyd for sender limitations

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-03-12 13:49 CET by Sönke Schwardt-Krummrich
Modified:	2019-01-03 07:23 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Feature Request
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 Sönke Schwardt-Krummrich

2015-03-12 13:49:52 CET

postfix-policyd provides the ability to restrict users from sending mails.
The following limitations are possible:
- limit the number of recipients per time interval (e.g. 20 recipients per 90mins)
- limit the number of mails per time interval (e.g. 15 mails pro hour)
- limit the mail sizes

It is possible to define global defaults and to define user specific limits.
A (my)SQL server is required for postfix-policyd.

Untested installation steps:
1) univention-install postfix-policyd
2) vim /etc/postfix-policyd.conf
        SENDERTHROTTLE=1
        SENDER_THROTTLE_SASL=1
        SENDER_THROTTLE_HOST=0
        SENDERMSGLIMIT=50
        SENDERRCPTLIMIT=40
        SENDERTIMELIMIT=1h
3) invoke postfix-policyd restart
4) ucr set mail/postfix/smtpd/restrictions/recipient/05=\
             "check_policy_service inet:127.0.0.1:10031"
5) invoke postfix restart

WARNING: 
step 4) has to be checked carefully; probably the limitation is also applied to usual incoming mails from other mail systems or incoming mails via fetchmail!

Comment 1 Daniel Tröder

2016-10-14 08:36:56 CEST

(In reply to Sönke Schwardt-Krummrich from comment #0)
> WARNING: 
> step 4) has to be checked carefully; probably the limitation is also applied
> to usual incoming mails from other mail systems or incoming mails via
> fetchmail!
Maybe the restriction could be set upon 587 only (in master.cf).

Comment 2 Stefan Gohmann

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