OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: 421 Service not available

From: Jonathan Dill (jonathannerds.net)
Date: Fri Apr 25 2008 - 10:06:12 CDT


On Apr 25, 2008, at 9:53 AM, Brian Evans wrote:

> El Neofito wrote:
>> Dear All,
>>
>> I got "421 4.3.2 Service shutting down, closing channel" in all
>> scenarios using 'telnet localhost 25' be it sending to external and
>> local users despite all services are up n running.
>>
>> Excerpt:
>> Apr 25 18:33:46 fotohubmail postfix/smtp[7740]: 7C2C3D8DC3: to=<adminimumxxmail.dyndns.org
>> >, orig_to=<adminimum>, relay=127.0.0.1[127.0.0.1]:10024,
>> delay=5802, delays=5796/3.9/1.8/0.07, dsn=4.3.2, status=deferred
>> (host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down,
>> closing channel (in reply to end of DATA command))
> Notice the "relay=127.0.0.1[127.0.0.1]:10024". This is what is not
> responding. Check and/or post your master.cf to figure what this is.
> Note: i hope this is `postconf -n` below and not a copy/paste of
> main.cf.

As a hint, 127.0.0.1:10024 / 127.0.0.1:10025 are frequently used to
pass through some mail filtering such as antivirus, especially amavis,
could happen if amavisd / clamd died or check the load average, could
happen if CPU is too slow, not enough memory on system, too many clamd
are spawned and your system cannot handle it. The answer should be
clear if you check master.cf

Jonathan