Tony Nelson:
> tnelson@njmail:/var/log$ grep i...@opulum.us<mailto:i...@opulum.us> mail.log
> Apr 24 09:46:21 njmail postfix/postscreen[8764]: NOQUEUE: reject: RCPT from
> [142.11.233.149]:21725: 450 4.3.2 Service currently unavailable;
> from=<i...@opulum.us<mailto:i...@opulum.us>>,
> to=<validu...@starpoint.com<mailto:validu...@starpoint.com>>, proto=ESMTP,
> helo=<dsc149.opulum.us<http://dsc149.opulum.us>>
>
> Service unavailable makes me think I have a problem with my config.
> Digging a little further:
The following text is plastered over the postscreen(8) manpage and
over the POSTSCREEN_README file.
The optional "after 220 server greeting" tests involve postscreen(8)'s
built-in SMTP protocol engine. When these tests succeed, postscreen(8)
adds the client to the temporary whitelist, but it cannot not hand off
the "live" connection to a Postfix SMTP server process in the middle of
a session. Instead, postscreen(8) defers attempts to deliver mail with
a 4XX status, and waits for the client to disconnect. When the client
connects again, postscreen(8) will allow the client to talk to a Post-
fix SMTP server process (provided that the whitelist status has not
expired). postscreen(8) mitigates the impact of this limitation by
giving the "after 220 server greeting" tests a long expiration time.
It is really hard to miss, if one bothers to read.
Wietse
