Docs clarification

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Docs clarification

Michael Orlitzky-2
POSTSCREEN_README.html says that the error

  NOQUEUE: reject: CONNECT from [address]:port: all server ports busy

is affected by the postscreen_pre_queue_limit parameter. However, in
postscreen.c it looks like the error associated with the "pre_queue"
parameter is "all screening ports busy", and that the error above is
actually affected by the postscreen_POST_queue_limit parameter.
Reply | Threaded
Open this post in threaded view
|

Re: Docs clarification

Wietse Venema
Michael Orlitzky:
> POSTSCREEN_README.html says that the error
>
>   NOQUEUE: reject: CONNECT from [address]:port: all server ports busy
>
> is affected by the postscreen_pre_queue_limit parameter. However, in
> postscreen.c it looks like the error associated with the "pre_queue"
> parameter is "all screening ports busy", and that the error above is
> actually affected by the postscreen_POST_queue_limit parameter.

Thanks. I think that is more correct.

Postscreen maintains two queues:

    pre-queue -> post-queue -> smtpd
       |
       v
    hangup, drop, built-in dummy SMTP server

- The post-queue with connections that have passed all tests and
  that are being handed off to a real smtpd(8) process. "All server
  ports are busy" means that all smtpd(8) processes are busy and
  that the post-queue size has reached the postscreen_post_queue_limit.

- The pre-queue with all other connections, including connections
  that are handled by to the postscreen built-in dummy SMTP server.
  "All screening ports are busy" means that the pre-queue size has
  reached the postscreen_pre_queue_limit.

        Wietse