Re: Policy Log Warning - Why?

1 msg	Postfix 2.3.9 available
2 msg	Postfix 2.4.1 available
4 msg	Alias directory
4 msg	Aliased domains bypass address verification
2 msg	Correct smtp auth config...
11 msg	smtp_connection_cache_on_demand
4 msg	Multiple Instances status quo?
15 msg	Setting up to send mail
5 msg	Relayhost - specify port inside or outside the ...
6 msg	Policyd for postfix is going crazy
2 msg	Can't seem to connect
10 msg	'lost connection with domain while sending end ...
21 msg	Whitelisting Redux
7 msg	question about 'local_recipient_maps ='
2 msg	SMTP relay
5 msg	Need help
2 msg	specifying relay_domains

Policy Log Warning - Why?
\ Duane Hill (27 Apr 2007)
. \ (Wietse Venema) (27 Apr 2007)
. . \ Duane Hill (28 Apr 2007)
. . . \ (Wietse Venema) (28 Apr 2007)
. . . . \ Duane Hill (28 Apr 2007)
. . . . . \ (Wietse Venema) (28 Apr 2007)
. . . . . . \ Duane Hill (28 Apr 2007)
. . . . . . . \ (Wietse Venema) (28 Apr 2007)
. . . . . . . . \ Duane Hill (28 Apr 2007)
. . . . . . . . . \ (Wietse Venema) (28 Apr 2007)
. . . . . . . . . . \ Duane Hill (29 Apr 2007)
. . . . . . . . . . . \ Victor Duchovni (29 Apr 2007)
. . . . . . . . . . . . \ Duane Hill (29 Apr 2007)
. . . . . . . . . . . . . \ (Wietse Venema) (29 Apr 2007)
. . . . . . . . . . . . . . \ Duane Hill (30 Apr 2007)
. . . . . . . . . . . . . . . \ Victor Duchovni (30 Apr 2007)
. . . . . . . . . . . . . . . . \ (Wietse Venema) (30 Apr 2007)
. . . . . . . . . . . . . . . . . \ (Wietse Venema) (30 Apr 2007)
. . . . . . . . . . . . . . . . . . \ Duane Hill (30 Apr 2007)
. . . . . . . . . . . . . . . . . . . \ (Wietse Venema) (30 Apr 2007)
. . . . . . . . . . . . . \ Victor Duchovni (29 Apr 2007)
. . . . . . . . . . . . . . \ Duane Hill (30 Apr 2007)

27 msg	Epoll fun
3 msg	relocated_maps message

Subject:	Re: Policy Log Warning - Why?
Group:	Postfix-users
From:	(Wietse Venema)
Date:	30 Apr 2007

Duane Hill:
> >> I've got a FreeBSD 6.2 test machine and can see what happens when one
> >> makes multiple UNIX-domain connections to a stuck server.
> >
> > Sure enough, when the UNIX-domain server falls behind and the
> > connection queue fills up, clients receive a "Connection refused"
> > indication.
...
> > So it is possible that the OP gets "Connection refused" because
> > his policy server isn't accepting connections. This could mean
> > that the master.cf process limit for policy service is lower
> > that the master.cf process limit for the smtpd service.
> >
> > This can happen when they increase the smtpd process limit in
> > master.cf by hand. The SMTPD_POLICY_README example specifies a
> > "-" process limit for policy daemons (i.e. use main.cf value). It
> > may be better to explicitly specify a 0 there for the policy server.
>
> Makes sense now. I did supply a zero(0) and do not receive the warnings
> any more. Thanks for checking this out and the explanation!
>
> The master.cf process limit for smtpd is set to 1200 which is well above
> the default_process_limit default of 100.

I've updated the SMTPD_POLICY_README example and replaced the "-"
process limit in the examples by "0", i.e. no limit. This is safe
because there is at most one policy process per smtpd process.

Wietse