1

Topic: sender throttle

Hi,

  We have configured sender throttling, but after a while I have the following message:
<END-OF-MESSAGE>: End-of-data rejected: Policy Rejection- Invalid data

A piece of log:

Jun  2 00:12:04 s13 postfix/smtpd[29873]: >>> START End-of-data RESTRICTIONS <<<
Jun  2 00:12:04 s13 postfix/smtpd[29873]: generic_checks: name=check_policy_service
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr request = smtpd_access_policy
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr protocol_state = END-OF-MESSAGE
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr protocol_name = ESMTP
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr client_address = x.x.x.x
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr client_name = x.x.x.x.net
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr reverse_client_name = x.x.x.x.net
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr helo_name = [127.0.0.1]
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr sender = lucas@xXXXXX.net
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr recipient =
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr recipient_count = 3
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr queue_id = EE6B228E02CC
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr instance = 74b1.4de6b931.d6eb9.0
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr size = 1593
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr etrn_domain =
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr stress =
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr sasl_method = PLAIN
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr sasl_username = lucas@xXXXXX.net
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr sasl_sender =
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr ccert_subject =
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr ccert_issuer =
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr ccert_fingerprint =
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr encryption_protocol = TLSv1
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr encryption_cipher = AES256-SHA
Jun  2 00:12:04 s13 postfix/smtpd[29873]: send attr encryption_keysize = 256
Jun  2 00:12:04 s13 postfix-policyd: invalid triplet_array[8][2]: (recipient throttle):
Jun  2 00:12:04 s13 postfix/smtpd[29873]: 127.0.0.1:10032: wanted attribute: action
Jun  2 00:12:04 s13 postfix/smtpd[29873]: input attribute name: action
Jun  2 00:12:04 s13 postfix/smtpd[29873]: input attribute value: defer_if_permit Policy Rejection- Invalid data
Jun  2 00:12:04 s13 postfix/smtpd[29873]: 127.0.0.1:10032: wanted attribute: (list terminator)
Jun  2 00:12:04 s13 postfix/smtpd[29873]: input attribute name: (end)
Jun  2 00:12:04 s13 postfix/smtpd[29873]: check_table_result: inet:127.0.0.1:10032 defer_if_permit Policy Rejection- Invalid data policy query
Jun  2 00:12:04 s13 postfix/smtpd[29873]: generic_checks: name=check_policy_service status=0
Jun  2 00:12:04 s13 postfix/smtpd[29873]: >>> END End-of-data RESTRICTIONS <<<

Following this link, we should disable sender throttling or upgrade to policyd 2.0.
http://www.iredmail.org/forum/topic1579 … -work.html

Some news?

Thank you in advanced,
   Lucas

2

Re: sender throttle

Still no update on this issue.
You can try to report this issue in policyd mail list, but policyd-1.x is not under active development.

3

Re: sender throttle

Hi ZhangHuangbin,

   Do you plan to solve 1.85 issue or upgrade to policyd 2.0?. We need throttle.

Regards,
   Lucas

4

Re: sender throttle

Major problems of upgrading to policyd-2:
- There's no official upgrading tutorials to migrate data from v1 to v2.
- We need to support Policyd-2 in iRedAdmin-Pro. It will take some time.

May i know what kind of throttling you need?