natan:
> Dec 20 14:51:19 m4 postfix/postscreen[5883]: warning: cannot connect to
> service private/smtpd: Resource temporarily unavailable
> Dec 20 14:51:19 m4 postfix/postscreen[5883]: warning: cannot connect to
> service private/smtpd: Resource temporarily unavailable
> Dec 20 14:51:20 m4 postfix/postscreen[5883]: warning: cannot connect to
> service private/smtpd: Resource temporarily unavailable
> Dec 20 14:51:20 m4 postfix/postscreen[5883]: warning: cannot connect to
> service private/smtpd: Resource temporarily unavailable
There is a limit in your operating system kernel, or in your Postfix
configuration.
> in main.cf:
> default_process_limit = 1200 --> beacause i have many incomming e-mail
>
> in master.cf
> smtp inet n - - - 1 postscreen
> smtpd pass - - - - - smtpd -o
> receive_override_options=no_address_mappings
postscreen tries to hand off each 'good' connection to an smtpd
process. Apparently, there are not enough of smtpd processes to
take those connections, and some kernel-internal queue is filling up
resulting in an EAGAIN kernel error code.
Possible causes:
1) The default_process_limit of 1200 is too low. In that case a
higher default_process_limit would help.
2) Your kernel cannot support the default_process_limit of 1200.
In that case a higher default_process_limit would not help. Instead,
kernel configuration or more memory (or both) would help.
3) Some non-Postfix "security" feature is getting in the way.
In the implementation, postscreen makes a non-blocking connect() call
with a 1-second time limit, and immediately receives an EAGAIN
kernel error code (immediately, because postscreen logs the same
warning message multiple times per second).
Wietse
