I've changed the config in this way ============================================================================ ================ smtpd_recipient_restrictions = check_policy_service inet:127.0.0.1:10031, permit_mynetworks #smtpd_sender_restrictions = # check_policy_service inet:127.0.0.1:10031, # permit_mynetworks, # permit smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10031 ============================================================================ ================ But now I can't connect postfix server (client goes time out) this are the log of maillog
Feb 28 17:02:47 smtp postfix/postfix-script[8538]: starting the Postfix mail system Feb 28 17:02:47 smtp postfix/master[8539]: daemon started -- version 2.6.6, configuration /etc/postfix Feb 28 17:03:40 smtp postfix/smtpd[8616]: fatal: parameter "smtpd_recipient_restrictions": specify at least one working instance of: check_relay_domains, reject_unauth_destination, reject, defer or defer_if_permit Feb 28 17:03:41 smtp postfix/master[8539]: warning: process /usr/libexec/postfix/smtpd pid 8616 exit status 1 Feb 28 17:03:41 smtp postfix/master[8539]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Feb 28 17:04:41 smtp postfix/smtpd[8620]: fatal: parameter "smtpd_recipient_restrictions": specify at least one working instance of: check_relay_domains, reject_unauth_destination, reject, defer or defer_if_permit Feb 28 17:04:42 smtp postfix/master[8539]: warning: process /usr/libexec/postfix/smtpd pid 8620 exit status 1 Feb 28 17:04:42 smtp postfix/master[8539]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Dr. Marcello Anderlini [email protected] --------------------------------------------- Database Informatica S.r.l. Microsoft Certified Partner Tel. +39059775070 Fax. +39059779545 http://www.database.it http://www.facebook.com/DatabaseInformatica -----Messaggio originale----- Da: Users [mailto:[email protected]] Per conto di Marinko Tarlac Inviato: mercoledì 27 febbraio 2013 14.35 A: [email protected] Oggetto: Re: [policyd-users] R: R: R: Policyd does not work I'm not an expert for Policyd but according to docs, ------- 6. Setup Postfix to use cbpolicyd... Add the following Postfix config... check_policy_service inet:127.0.0.1:10031 in BOTH smtpd_recipient_restrictions and smtpd_end_of_data_restrictions. -------- the line check_policy_service inet:127.0.0.1:10031 should be added in smtpd_recipient_restrictions and in your email I see it is inside smtpd_sender_restrictions On 27.2.2013 14:07, Marcello Anderlini wrote: > I've set my test rules in this way: > ====== > SenderIP:83.216.185.74/32 > ====== > Since is a test and I just want to check my ip it seems correct to me. > I'm using just IPv4. > I can not understad why this should be wrong. > > > > Dr. Marcello Anderlini > [email protected] > --------------------------------------------- > Database Informatica S.r.l. > Microsoft Certified Partner > Tel. +39059775070 > Fax. +39059779545 > http://www.database.it > http://www.facebook.com/DatabaseInformatica > -----Messaggio originale----- > Da: Users [mailto:[email protected]] Per conto di Robert > Anderson > Inviato: mercoledì 27 febbraio 2013 12.38 > A: [email protected] > Oggetto: Re: [policyd-users] R: R: Policyd does not work > > On 27/02/2013 12:52, Marcello Anderlini wrote: >> [2013/02/27-13:51:53 - 21856] [CBPOLICYD] INFO: Got request #1 >> [2013/02/27-13:51:53 - 21856] [QUOTAS] WARNING: Unknown key specification > in >> TrackSenderIP >> [2013/02/27-13:51:53 - 21856] [QUOTAS] ERROR: No key found for quota ID > '3' > > Looks like policyd is not understanding your quota track method: > > SenderIP:/bitmask > One can specify a bitmask to apply to the sending servers' IP address, > for instance /24. This will track the triplet through the entire /24 > block. SenderIP's bitmask can be any bitmask, 1-32. A sane value is /24. > Specifying any IPv6 bitmask, 1-128 will apply the bitmask to the sending > server's IP address. A sane value for this is /64. When using quotas on > both IPv4 and IPv6, please ensure you use the IPv4 policy member > 0.0.0.0/0 (or 0/0) and the IPv6 policy member ::/0 to distinguish > between the two so you get the bitmask right. (Support for IPv6 is > included in r493+, v2.1.x) > > http://wiki.policyd.org/quotas > > _______________________________________________ > Users mailing list > [email protected] > http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org > > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org > _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
