I've noticed a lot of people try to put policyd further "down" in the
list of
smtpd_recipient_restrictions entires in an attempt to load the system
less. Well,
in most cases, the extra load needed to -- for example -- see if the
connection is whitelisted is so low that we decided some time ago
Cami, thanks for the replay. Indeed , that seems to be the problem.
Two days ago I change the place for the policyd restrictions and it
start to work. Now is under surveillance. Once again.. Thank you
Alex
-
This SF
Cami Sardinha wrote:
Alexandru Constantinescu wrote:
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
check_recipient_access mysql:/etc/postfix/mysql-recipient.cf,
reject_unauth_destination,
permit_mx_backup,
permit_auth_destination,
check_policy_servi
Cami Sardinha wrote:
Alexandru Constantinescu wrote:
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
check_recipient_access mysql:/etc/postfix/mysql-recipient.cf,
reject_unauth_destination,
permit_mx_backup,
permit_auth_destination,
check_policy_servi
Alexandru Constantinescu wrote:
> smtpd_recipient_restrictions =
> permit_mynetworks,
> permit_sasl_authenticated,
> check_recipient_access mysql:/etc/postfix/mysql-recipient.cf,
> reject_unauth_destination,
> permit_mx_backup,
> permit_auth_destination,
> check_policy_service inet:127.0.0.1:1003
I have a CENTOS 5 with postfix (with virtual domains, mysql ,
amavis-new, spamassassin, dkim ,dk-filter) and I try to install policyd
(1.80,1.82, and 1.9XXX) with the intention to limit the number of
messages that the user send/period of time, at least just for start.
None of that versions seems to
