Prev: MX Records: separate web and email servers
Next: access db rejection for some destination addresses and not others (domain based)?
From: John Covici on 27 Jun 2008 17:14
Just wanted to thank you -- I took the include for dialup.m4 out of
the sendmail.mc and it fixed that -- maybe it broke something else,
but I haven't seen it yet.

Thanks.

on Wed, 25 Jun 2008 02:22:24 +0200 Kees Theunissen <theuniss(a)rijnh.nl> wrote:

> John Covici wrote:
>> Hi. I am not sure what is going on -- I am using sendmail under
>> Debian and I am getting the following strange thing -- for instance
>> here is a line which should be the hello command.
>> 220 ;; ESMTP connection timed out; no servers could be reached
>> Sendmail 8.13.8/8.13.8/Debian-3; Tue, 24 Jun 2008 05:49:47 -0500; (No
>> UCE/UBE) logging access from:
>> pool-71-171-111-192.clppva.fios.verizon.net(OK)-pool-71-171-111-192.clppva.fios.verizon.net
>> [71.171.111.192]
>> What the heck is the string after the 220 -- it is appended before
>> every command and so sendmail can't send out because of this.
>
> This is the result of lacking error handling in a bunch of overly
> complicated shell and perl scripts used to automatically configure
> sendmail on debian systems.
> I've seen this error on the first debian system I ever installed
> and configured; a late pre-release etch. As far as I understood
> the scripts debian will configure sendmail during installation of
> the program and -depending on installed packages and configuration-
> probably also in the startup scripts or even on every change in
> network connection. And "configure sendmail" means: generate among
> others new sendmail.mc and sendmail.cf files.
>
> This particular error is the error message "connection timed out;
> no servers could be reached" that is interpreted as the host name
> of the system. I'm not sure about this but IIRR this error is
> included (two times I think) in /etc/mail/m4/dialup.m4.
> Do a "grep -R 'connection timed out' /etc/mail/*" to locate
> the file(s) containing this error.
>
> In my particular case it's likely that I didn't have any network
> connected during installation of the system, causing (reverse)
> DNS lookups to fail. But I don't remember all details; it was
> the first debian I installed and I experimented/played a lot.
> I'm not sure how I solved this. As I said I played a lot with
> that system.
> Purging (i.e. uninstalling with removal of all configuration files)
> of sendmail and associated packages might be a good starting point.
> Make sure your network is connected and working when you reinstall
> those packages.
>
> Regards,
>
> Kees.
>
> --
> Kees Theunissen.

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici
covici(a)ccs.covici.com
 | 
Pages: 1
Prev: MX Records: separate web and email servers
Next: access db rejection for some destination addresses and not others (domain based)?