Loading ...
Sorry, an error occurred while loading the content.
 

Re: Policy Log Warning - Why?

Expand Messages
  • Wietse Venema
    ... 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
    Message 1 of 22 , Apr 30, 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
    Your message has been successfully submitted and would be delivered to recipients shortly.