On 08/25/2018 10:20 AM, TE Dukes wrote:> >> Let's go back to pastebin. What are the contents of /etc/nsswitch.conf >> and /etc/hosts, now? >> > Link to pastebin: https://paste.fedoraproject.org/paste/97keKuhV4lMoLZ8DIrYT8w"Hosts: files dns" Try again.? "hosts"
> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Gordon > Messmer > Sent: Sunday, August 26, 2018 2:16 AM > To: centos at centos.org > Subject: Re: [CentOS] Mail has quit working > > On 08/25/2018 10:20 AM, TE Dukes wrote: > > > >> Let's go back to pastebin. What are the contents of /etc/nsswitch.conf > >> and /etc/hosts, now? > >> > > Link to pastebin: > https://paste.fedoraproject.org/paste/97keKuhV4lMoLZ8DIrYT8w > > "Hosts: files dns" > > Try again. "hosts" >Thanks! Made the change above in nsswitch, rebooted, ran dig @localhost localhost +short Got: dig: couldn't get address for 'localhost': failure Checked maillog: Aug 26 09:12:31 ts130 postfix/qmgr[2194]: E5B948331053: from=<fail2ban at palmettodomains.com>, size=469, nrcpt=1 (queue active) Aug 26 09:12:31 ts130 postfix/smtp[2307]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused Aug 26 09:12:32 ts130 postfix/smtp[2307]: E5B948331053: to=<root at ts130.palmettodomains.com>, orig_to=<root>, relay=none, delay=77, delays=77/0.39/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) Aug 26 09:12:34 ts130 postfix/pickup[2193]: 4670E8252A22: uid=0 from=<fail2ban at palmettodomains.com> Aug 26 09:12:34 ts130 postfix/cleanup[2197]: 4670E8252A22: message-id=<20180826131234.4670E8252A22 at ts130.palmettodomains.com> Aug 26 09:12:34 ts130 postfix/qmgr[2194]: 4670E8252A22: from=<fail2ban at palmettodomains.com>, size=482, nrcpt=1 (queue active) Aug 26 09:12:34 ts130 postfix/smtp[2307]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused Aug 26 09:12:34 ts130 postfix/smtp[2307]: 4670E8252A22: to=<root at ts130.palmettodomains.com>, orig_to=<root>, relay=none, delay=0.58, delays=0.58/0/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) Really appreciate everyone's help and patience!
Am 26.08.2018 um 15:25 schrieb TE Dukes:> Checked maillog: > > Aug 26 09:12:31 ts130 postfix/qmgr[2194]: E5B948331053: from=<fail2ban at palmettodomains.com>, size=469, nrcpt=1 (queue active) > Aug 26 09:12:31 ts130 postfix/smtp[2307]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused > Aug 26 09:12:32 ts130 postfix/smtp[2307]: E5B948331053: to=<root at ts130.palmettodomains.com>, orig_to=<root>, relay=none, delay=77, delays=77/0.39/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) > Aug 26 09:12:34 ts130 postfix/pickup[2193]: 4670E8252A22: uid=0 from=<fail2ban at palmettodomains.com> > Aug 26 09:12:34 ts130 postfix/cleanup[2197]: 4670E8252A22: message-id=<20180826131234.4670E8252A22 at ts130.palmettodomains.com> > Aug 26 09:12:34 ts130 postfix/qmgr[2194]: 4670E8252A22: from=<fail2ban at palmettodomains.com>, size=482, nrcpt=1 (queue active) > Aug 26 09:12:34 ts130 postfix/smtp[2307]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused > Aug 26 09:12:34 ts130 postfix/smtp[2307]: 4670E8252A22: to=<root at ts130.palmettodomains.com>, orig_to=<root>, relay=none, delay=0.58, delays=0.58/0/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) > > Really appreciate everyone's help and patience!That part of the log just indicates that your service which is called inb port 10024 isn't running. In your setup that is likely the amavisd-new filter service. Make sure it runs or take it out of your Postfix configuration. Alexander
On 08/26/2018 06:25 AM, TE Dukes wrote:> > Made the change above in nsswitch, rebooted, ran dig @localhost localhost +short > Got: dig: couldn't get address for 'localhost': failureThat's a secondary issue.? A properly configured DNS server *should* answer correctly for "localhost".? Yours doesn't.? It's broken.? Red Hat ships ISC Bind with a working configuration (/etc/named.rfc1912.zones).? I'm not sure whether you're using something else, or if you've removed the RFC1912 zones.? Fix that later. "host" and "dig" are both DNS tools, and won't tell you if your files are being used properly.? While you're troubleshooting the libc name resolution system, use "getent".? "getent hosts localhost" and "getent hosts 127.0.0.1" should return something that looks vaguely like the data in /etc/hosts.? You can also verify that it works in practice using "telnet localhost 25" to verify that you can reach services running on the local system.