On Mon, Jun 09, 2008 at 04:46:47PM -0400, Ray Leventhal wrote:
> >DNS. It's always DNS :-)
> While I agree, I'm still a bit stumped. Nothing changed other than a
> reboot on Sunday afternoon. I do have Friday's rsync snapshot and running
> diff against the sendmail files (cf/mc) as well as hos
DNS. It's always DNS :-)
(more accurately, host and IP address resolution).
How long is it taking your server to resolve the IP address into a
name? To resolve names into IP addresses? To resolve destination MX
records?
Hi Stephen,
While I agree, I'm still a bit stumped. Nothing cha
On Mon, Jun 09, 2008 at 11:34:11AM -0400, Ray Leventhal wrote:
> This now seems like a timeout issue. Increasing client-side timeout to
> > 180 seconds gets mail going just fine.
>
> Any ideas on what might be happening since a reboot to cause this change
> in MTA behaviour would be greatly app
where does the server point to for its dns? if it's (supposed to be)
running a nameserver (e.g., you're pointing to 127.0.0.1) but the dns
server isn't running you'll get a timeout. if you have a second
nameserver configured in /etc/resolv.conf you'll likely ultimately
get a response, but only
lists-centos wrote:
are you configured for spamassassin or clamav as milters on the
server (in the sendmail.cf) and either/both of these didn't start up
on the reboot? sendmail will still accept mail with sa/clamav not
running, but it takes a bit longer.
there's also the possibility of an invers
This now seems like a timeout issue. Increasing client-side timeout to
> 180 seconds gets mail going just fine.
Any ideas on what might be happening since a reboot to cause this change
in MTA behaviour would be greatly appreciated.
Regards,
-Ray
__
6 matches
Mail list logo
