Re: [courier-users] lo is down

Idézem/Quoting Lindsay Haisley : > On Wed, 2016-12-28 at 15:44 -0800, Gordon Messmer wrote: >> On 12/28/2016 02:07 PM, Lindsay Haisley wrote: >> > This generally removes any dependency on DNS for resolving >> "localhost". >> >> Courier uses DNS for everything that comes to

Re: [courier-users] lo is down

On Wed, 2016-12-28 at 15:44 -0800, Gordon Messmer wrote: > On 12/28/2016 02:07 PM, Lindsay Haisley wrote: > > This generally removes any dependency on DNS for resolving > "localhost". > > Courier uses DNS for everything that comes to mind.  Modifying  > /etc/hosts won't resolve the problem in

Re: [courier-users] lo is down

On 12/28/2016 02:07 PM, Lindsay Haisley wrote: > This generally removes any dependency on DNS for resolving "localhost". Courier uses DNS for everything that comes to mind. Modifying /etc/hosts won't resolve the problem in question.

Re: [courier-users] lo is down

On 12/28/2016 01:38 PM, SZÉPE Viktor wrote: > Thank you Gordon! > > After a quick tcpdump. > Monit sends: > > EHLO localhost > QUIT What is the value for TCPDOPTS in /etc/courier/esmtpd? That test should work if you have -nodnslookup set (though I don't recommend that). If it's not set, as in

Re: [courier-users] lo is down

On Wed, 2016-12-28 at 22:38 +0100, SZÉPE Viktor wrote: > Thank you Gordon! > > After a quick tcpdump. > Monit sends: > > EHLO localhost > QUIT The following lines, or something very like them, should always be in /etc/hosts: 127.0.0.1 localhost ip4-localhost ::1 ip6-localhost

Re: [courier-users] lo is down

Thank you Gordon! After a quick tcpdump. Monit sends: EHLO localhost QUIT Idézem/Quoting Gordon Messmer : > On 12/28/2016 11:02 AM, SZÉPE Viktor wrote: >> Could it be that Courier unbinds from localhost when eth0 is down? > > > If Monit is testing SMTP on localhost,

Re: [courier-users] lo is down

On 12/28/2016 11:02 AM, SZÉPE Viktor wrote: > Could it be that Courier unbinds from localhost when eth0 is down? If Monit is testing SMTP on localhost, there are a bunch of possible causes of failure. The most likely, I would think, is that DNS is not available so one of the SMTP commands

Re: [courier-users] lo is down

Thank you for your answer. This is my Debian-way hosts file 127.0.0.1 localhost 127.0.1.1 localhost ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters # Original PTR=$(host "$IP" || true) ${IP} ${H} ${H%%.*}

Re: [courier-users] lo is down

Here it is. # https://bitbucket.org/tildeslash/monit/issue/112/smtp-error#comment-14395650 #if failed host localhost port 25 type tcp protocol smtp retry 2 times then restart if failed host localhost port 25 type tcp protocol smtp for 2 cycles then restart Full config:

Re: [courier-users] lo is down

SZÉPE Viktor writes: Good evening! I am investigating a strange monitoring phenomenon. localhost (lo interface) is monitored on port 25 with a program called Monit. Monit generates a very small SMTP communication. Usually it is OK. When the Internet-facing interface (eth0) is down - for some

Re: [courier-users] lo is down

On Wed, 2016-12-28 at 20:02 +0100, SZÉPE Viktor wrote: > Good evening! > > I am investigating a strange monitoring phenomenon. > localhost (lo interface) is monitored on port 25 with a program > called Monit. > Monit generates a very small SMTP communication. > Usually it is OK. > > When the

[courier-users] lo is down

Good evening! I am investigating a strange monitoring phenomenon. localhost (lo interface) is monitored on port 25 with a program called Monit. Monit generates a very small SMTP communication. Usually it is OK. When the Internet-facing interface (eth0) is down - for some reason but not DHCP -