Re: sendmail was working fine...until now

[Jeff Nelson <jnelson_(_at_)_jgndesigns_(_dot_)_com>]

On Tue, Nov 30, 2004 at 04:45:56AM -0800, Dave Smith wrote:
> On my 3.5 install with default sendmail it's been
> working no problem for months. However, yesterday my
> clients started to get error messages when sending
> mail. This happens on many different clients so the
> problem is server side. In the logfile I get these
> messages:
> 
> Nov 30 05:35:51 rundle sm-mta[27375]: NOQUEUE: connect
> from [192.168.1.225]
> Nov 30 05:35:51 rundle sm-mta[27375]: iAUCZp37027375:
> --- 220 rundle.ed.shawcable.net ESMTP Sendmail
> 8.12.11/8.12.11; Tue, 30 Nov 2004 05:35:51 -0700 (MST)
> Nov 30 05:35:51 rundle sm-mta[27375]: iAUCZp37027375:
> --- 421 4.4.1 rundle.ed.shawcable.net Lost input
> channel from [192.168.2.225]
> Nov 30 05:35:51 rundle sm-mta[27375]: iAUCZp37027375:
> [192.168.2.225] did not issue MAIL/EXPN/VRFY/ETRN
> during connection to MTA
> 
> >From what I've read the NOQUEUE message isn't a big
> deal, but the "did not issue" seems to be killing the
> clients. They will pickup mail no problem, they just
> can't send. Any ideas guys?

Sounds like a DNS issue. I was having a similar problem with long
resolution times. An upgrade from release to stable and rebuilding BIND
solved my problems.

Have a great day!
-jeff