-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Tuesday, July 24, 2018 4:19 PM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

Am 24.07.2018 um 21:07 schrieb TE Dukes:

...

Output from tail:

Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:35:59 ts130 postfix/qmgr[8283]: C33128410546: from=< mailto:root@ts130.palmettodomains.com

root@ts130.palmettodomains.com>,

...

size=949, nrcpt=1 (queue active) Jul 24 10:36:29 ts130 postfix/smtp[19763]: connect to http://paalmettodomains.com

paalmettodomains.com[198.105.254.65]:25:

...

Connection timed out Jul 24 10:36:59 ts130 postfix/smtp[19763]: connect to http://paalmettodomains.com

paalmettodomains.com[104.239.198.84]:25:

...

Connection timed out

That looks totally broken: http://paalmettodomains.com Where does that come from? An HTTP adddress has no valid function in SMTP communication. Even the domain seems to be a typo.

It's a typo.

...

Jul 24 10:36:59 ts130 postfix/smtp[19763]: C33128410546: to=< mailto:tdukes@paalmettodomains.com

tdukes@paalmettodomains.com>,

...

relay=none, delay=13075, delays=13015/0.02/60/0, dsn=4.4.1,

status=deferred

...

(connect tohttp://paalmettodomains.com paalmettodomains.com[104.239.198.84]:25: Connection timed out) Jul 24 10:45:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:55:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 11:04:19 ts130 postfix/pickup[19912]: 55271840D734: uid=0

from=<root>

...

Jul 24 11:04:19 ts130 postfix/cleanup[21840]: 55271840D734: message-id=< mailto:20180724150419.55271840D734@ts130.palmettodomains.com 20180724150419.55271840D734@ts130.palmettodomains.com> Jul 24 11:04:19 ts130 postfix/qmgr[8283]: 55271840D734: from=< mailto:root@ts130.palmettodomains.com

root@ts130.palmettodomains.com>,

...

size=466, nrcpt=1 (queue active)

mailto:root@ts130.palmettodomains.com <- What is the purpose to send yourself a mail locally? Did you even specify a valid, fully qualified recipient address?

A previous person instructed to do so.

...

Jul 24 11:04:20 ts130 postfix/smtpd[21846]: connect from localhost[127.0.0.1] Jul 24 11:04:20 ts130 postfix/smtpd[21846]: 49161841ED92: client=localhost[127.0.0.1] Jul 24 11:04:20 ts130 postfix/cleanup[21840]: 49161841ED92: message-id=< mailto:20180724150419.55271840D734@ts130.palmettodomains.com 20180724150419.55271840D734@ts130.palmettodomains.com> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92: from=< mailto:root@ts130.palmettodomains.com

root@ts130.palmettodomains.com>,

...

size=951, nrcpt=1 (queue active) Jul 24 11:04:20 ts130 postfix/smtpd[21846]: disconnect from localhost[127.0.0.1] Jul 24 11:04:20 ts130 amavis[423]: (00423-03) Passed CLEAN

{RelayedInbound},

...

[127.0.0.1] <mailto:root@ts130.palmettodomains.com root@ts130.palmettodomains.com> -> <

mailto:tdukes@palmettodomains.com

...

tdukes@palmettodomains.com>, Message-ID: < mailto:20180724150419.55271840D734@ts130.palmettodomains.com 20180724150419.55271840D734@ts130.palmettodomains.com>, mail_id: eYD2cL7fZ7rY, Hits: -0.001, size: 466, queued_as: 49161841ED92, 941 ms Jul 24 11:04:20 ts130 postfix/smtp[21842]: 55271840D734: to=< mailto:tdukes@palmettodomains.com

tdukes@palmettodomains.com>,

...

relay=127.0.0.1[127.0.0.1]:10024, delay=1, delays=0.07/0.01/0/0.94, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 49161841ED92) Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 55271840D734: removed Jul 24 11:04:20 ts130 dovecot: lda(tdukes): msgid=< mailto:20180724150419.55271840D734@ts130.palmettodomains.com 20180724150419.55271840D734@ts130.palmettodomains.com>: saved mail

to INBOX

...

Jul 24 11:04:20 ts130 postfix/local[21847]: 49161841ED92: to=< mailto:tdukes@palmettodomains.com

tdukes@palmettodomains.com>,

...

relay=local, delay=0.09, delays=0.02/0.01/0/0.06, dsn=2.0.0, status=sent (delivered to command: /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT") Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92: removed

Mail got delivered locally after passing amavis at the mailbox tdukes@palmettodomains.com.

Alexander

I am unable to read my system's mail. Cannot read it from roundcube or usermin. Roundcube times out on login attemps. In usermin there is no mail in the mailbox. There is no mail in /Maildir.

This just started this past Saturday morning. Everything was fine up to then.

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of mark Sent: Tuesday, July 24, 2018 5:21 PM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

TE Dukes wrote:

...

...

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of

Alexander

...

...

Dalloz Sent: Tuesday, July 24, 2018 4:19 PM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

Am 24.07.2018 um 21:07 schrieb TE Dukes:

...

Output from tail:

Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:35:59 ts130 postfix/qmgr[8283]: C33128410546: from=< mailto:root@ts130.palmettodomains.com

root@ts130.palmettodomains.com>,

...

size=949, nrcpt=1 (queue active) Jul 24 10:36:29 ts130 postfix/smtp[19763]: connect to http://paalmettodomains.com

paalmettodomains.com[198.105.254.65]:25:

...

Connection timed out Jul 24 10:36:59 ts130 postfix/smtp[19763]: connect to http://paalmettodomains.com

paalmettodomains.com[104.239.198.84]:25:

...

Connection timed out

That looks totally broken: http://paalmettodomains.com Where does that come from? An HTTP adddress has no valid function in SMTP communication. Even the domain seems to be a typo.

It's a typo.

...

...

Jul 24 10:36:59 ts130 postfix/smtp[19763]: C33128410546: to=< mailto:tdukes@paalmettodomains.com

tdukes@paalmettodomains.com>,

...

relay=none, delay=13075, delays=13015/0.02/60/0, dsn=4.4.1,

status=deferred

...

(connect tohttp://paalmettodomains.com paalmettodomains.com[104.239.198.84]:25: Connection timed out) Jul 24 10:45:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 10:55:02 ts130 clamd[3226]: SelfCheck: Database status OK. Jul 24 11:04:19 ts130 postfix/pickup[19912]: 55271840D734: uid=0

from=<root>

...

Jul 24 11:04:19 ts130 postfix/cleanup[21840]: 55271840D734: message-id=< mailto:20180724150419.55271840D734@ts130.palmettodomains.com 20180724150419.55271840D734@ts130.palmettodomains.com> Jul 24 11:04:19 ts130 postfix/qmgr[8283]: 55271840D734: from=< mailto:root@ts130.palmettodomains.com

root@ts130.palmettodomains.com>,

...

size=466, nrcpt=1 (queue active)

mailto:root@ts130.palmettodomains.com <- What is the purpose to send yourself a mail locally? Did you even specify a valid, fully qualified recipient address?

A previous person instructed to do so.

...

...

Jul 24 11:04:20 ts130 postfix/smtpd[21846]: connect from localhost[127.0.0.1] Jul 24 11:04:20 ts130 postfix/smtpd[21846]: 49161841ED92: client=localhost[127.0.0.1] Jul 24 11:04:20 ts130 postfix/cleanup[21840]: 49161841ED92: message-id=< mailto:20180724150419.55271840D734@ts130.palmettodomains.com 20180724150419.55271840D734@ts130.palmettodomains.com> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92: from=< mailto:root@ts130.palmettodomains.com

root@ts130.palmettodomains.com>,

...

size=951, nrcpt=1 (queue active) Jul 24 11:04:20 ts130 postfix/smtpd[21846]: disconnect from localhost[127.0.0.1] Jul 24 11:04:20 ts130 amavis[423]: (00423-03) Passed CLEAN

{RelayedInbound},

...

[127.0.0.1] <mailto:root@ts130.palmettodomains.com root@ts130.palmettodomains.com> -> <

mailto:tdukes@palmettodomains.com

...

tdukes@palmettodomains.com>, Message-ID: < mailto:20180724150419.55271840D734@ts130.palmettodomains.com 20180724150419.55271840D734@ts130.palmettodomains.com>, mail_id: eYD2cL7fZ7rY, Hits: -0.001, size: 466, queued_as: 49161841ED92, 941 ms Jul 24 11:04:20 ts130 postfix/smtp[21842]: 55271840D734: to=< mailto:tdukes@palmettodomains.com

tdukes@palmettodomains.com>,

...

relay=127.0.0.1[127.0.0.1]:10024, delay=1, delays=0.07/0.01/0/0.94, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 49161841ED92) Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 55271840D734: removed Jul 24 11:04:20 ts130 dovecot: lda(tdukes): msgid=< mailto:20180724150419.55271840D734@ts130.palmettodomains.com 20180724150419.55271840D734@ts130.palmettodomains.com>: saved

mail

...

...

...

to INBOX

...

Jul 24 11:04:20 ts130 postfix/local[21847]: 49161841ED92: to=< mailto:tdukes@palmettodomains.com

tdukes@palmettodomains.com>,

...

relay=local, delay=0.09, delays=0.02/0.01/0/0.06, dsn=2.0.0, status=sent (delivered to command: /usr/libexec/dovecot/dovecot-lda -

f

...

...

...

"$SENDER" -a "$RECIPIENT") Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92: removed

Mail got delivered locally after passing amavis at the mailbox tdukes@palmettodomains.com.

Alexander

I am unable to read my system's mail. Cannot read it from roundcube or usermin. Roundcube times out on login attemps. In usermin there is no

mail

...

in the mailbox. There is no mail in /Maildir.

This just started this past Saturday morning. Everything was fine up to then.

1. Have you checked /var/log/yum.log?

2. Is everything correct in /cron.*?

3. Have you considered running yum reinstall crony?

    mark
   

Thanks!

Everything seems to be OK.

I did find where the mail is going. I found it in /Maildir/new/

Postfix is set to home_mailbox = Maildir/ Changing it doesn't help.

Still can't login to roundcube.

On 25/07/18 12:10, TE Dukes wrote:

...

...

I am unable to read my system's mail. Cannot read it from roundcube or usermin. Roundcube times out on login attemps. In usermin there is no mail in the mailbox. There is no mail in /Maildir.

This is new information. It points to the issue being in dovecot or roundcube.

I did find where the mail is going. I found it in /Maildir/new/

This indicates that dovecot is working.

Postfix is set to home_mailbox = Maildir/ Changing it doesn't help.

It won't, this setting only applies when you're using the postfix local(8) delivery agent, but you have postfix configured to use dovecot so this setting does not actually do anything.

Still can't login to roundcube.

Check roundcube settings, check dovecot logs. See my previous email for where to get more help with dovecot.

Peter

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Pete Biggs Sent: Wednesday, July 25, 2018 5:45 AM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

...

I did find where the mail is going. I found it in /Maildir/new/

Yes, that's how Maildir mail works - delivery to a Maildir folder means that the mail is put in Maildir/new until it is seen, when it is moved to Maildir/cur via Maildir/tmp - it's complicated, but it's necessary in order to maintain appropriate locks on the files when multiple clients are accessing them.

...

Still can't login to roundcube.

When you say "can't login" - what is the error?

What do the dovecot logs say? You can see where dovecot logs to by looking in /etc/dovecot/conf.d/10-logging.conf - can you see your roundcube install attempting to authenticate?

P.

Geeeez!! Its working again. All I did was restart the system.

I stopped and restarted postfix, dovecot, mariadb several times over the past couple days. Pretty sure I did a system reboot a time or two.

Decided to do one a few minutes ago and now its working. Hate I never found the problem that caused this issue!

Thanks for all the help!!

On 08/19/2018 06:21 PM, TE Dukes wrote:

Another kernel update and things are broken again! YEARS with no problems. About tired of messing with this!

Earlier in this thread, you indicated that you saw "warning hostname localhost does not resolve to address 127.0.0.1" in /var/log/maillog, and some other logs indicated that postfix was timing out connecting to its locally hosted domains.  Both of those suggest that you have DNS or network related problems, and not something resulting from package updates.

You might consider posting /etc/resolv.conf, /etc/hosts, /etc/sysconfig/network-scripts/ifcfg-<your network interface>, and /etc/postfix/main.cfg on https://paste.fedoraproject.org/ for review.  It would also be useful to see the output of "ip addr show", "ip route show", and "ip -6 route show".  If the system starts working suddenly, as it did earlier, compare the output of those commands when the system is working to the output when it is not.

On Thu, 23 Aug 2018 at 18:21, TE Dukes tdukes@palmettoshopper.com wrote:

Thanks,

I'm not familiar with https://paste.fedoraproject.org . Guessing I need to register first but then what? Doesn't appear to have a subject area. Do I just post the files you recommended?

or use http://pastebin.centos.org/ and copy and paste the output into pastebin area and then hit submit. You will be given a URL which people can then refer to.

TIA

---

CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

On Thu, 23 Aug 2018 at 18:52, TE Dukes tdukes@palmettoshopper.com wrote:

...

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Stephen John Smoogen Sent: Thursday, August 23, 2018 6:24 PM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

On Thu, 23 Aug 2018 at 18:21, TE Dukes tdukes@palmettoshopper.com wrote:

...

...

Thanks,

I'm not familiar with https://paste.fedoraproject.org . Guessing I need

to

...

register first but then what? Doesn't appear to have a subject area. Do I

just

...

post the files you recommended?

...

or use http://pastebin.centos.org/ and copy and paste the output into pastebin area and then hit submit. You will be given a URL which people can then refer to.

...

TIA

---

CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

-- Stephen J Smoogen.

I pasted all the info requested but not seeing a link except for a deactivation token

In the URL section of your browser there should be something like https://paste.fedoraproject.org/paste/GzNwzOQt~uZdK5AahxX4Rg

That is the URL to give a person to review.

---

CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

On Thu, 23 Aug 2018 at 19:11, TE Dukes tdukes@palmettoshopper.com wrote:

Whoooosh, senior moment!!

Here's the link: https://paste.fedoraproject.org/paste/MMNEJmqIrEzK-A4N3MR0ZA

I just recently disabled IPV6 due to errors resolving I saw in the logs. This was AFTER mail quit working the second time. It did not correct the problem. Both times, this has happened after a kernel upgrade. I have had no errors this time, except for IPV6 stuff.

I think the error may be here:

/etc/hosts: multi on

If that is the /etc/hosts file then something is changing it somewhere (and the kernel rpms do not touch this file unless someone wrote over it.) The file should be:

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

The second problem may be in whatever created that ifcfg-eno1 file. I have resorted and cleaned it up so it is easier to look at

DEVICE=eno1 NAME=eth0 BOOTPROTO=none BROADCAST=192.168.1.255 DNS1=166.102.165.13 DNS2=207.91.5.20 DNS3=127.0.0.1 GATEWAY=192.168.1.1 IPADDR=192.168.1.110 NETMASK=255.255.255.0 NETWORK=192.168.1.0 DEFROUTE=yes DOMAIN=palmettodomains.com IPV4_FAILURE_FATAL=no IPV6INIT=no ONBOOT=yes TYPE=Ethernet UUID=cfd35a8f-6c40-4a80-bff5-821a91d0775b ZONE=public

The third problem is possibly your DNS3 which is pointing to 127.0.0.1 which means you have a local nameserver running on the box. No idea what that is but it is probably something that needs to be reconfigured or turned off.

TIA

---

CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

On 08/23/2018 04:10 PM, TE Dukes wrote:

Here's the link: https://paste.fedoraproject.org/paste/MMNEJmqIrEzK-A4N3MR0ZA

ip route show: default via 192.168.1.1 dev eno1 proto static metric 101 192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.111 metric 100 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.110 metric 101

You have two physical devices using the same IPv4 subnet.  Disable the one you aren't using.  Set ONBOOT=no in /etc/sysconfig/network-scripts/ifcfg-enp1s0 or remove the file entirely.

I have removed DNS3 from ifcfg-eno1 and set ONBOOT=no in ifcfg- enp1so0, reboot and still can't read mail. Logging into roundcube either times out or if I get in, the inbox is empty.

So, again, what do the dovecot logs say?

How is roundcube setup? Specifically what is the IMAP server set to? Remember, if you have changed the server definition in the config, the individual accounts that were already defined in the database will still have the old server definition.

P.

Here's the link for the maillog:

https://paste.fedoraproject.org/paste/kbH2N9Pc~JPuCqVpE1kszQ

OK. There are a couple of things:

Aug 23 21:47:18 ts130 postfix/smtpd[3750]: warning: hostname localhost does not resolve to address 127.0.0.1 Aug 23 21:47:18 ts130 postfix/smtpd[3750]: connect from unknown[127.0.0.1]

That needs to be fixed. What does the entry for 127.0.0.1 look like in /etc/hosts? Have you also defined ::1 to be localhost in /etc/hosts?

Aug 23 21:47:21 ts130 dovecot: imap-login: Login: user=<tdukes>, method=PLAIN, rip=::1, lip=::1, mpid=3754, secured, session=<9W1yjiR08AAAAAAAAAAAAAAAAAAAAAAB>

So you are connecting over TCPv6 from roundcube to dovecot? Is that what you want?

What is the IMAP hostname in the roundcube configuration?

P.

On Fri, 24 Aug 2018 at 10:36, TE Dukes tdukes@palmettoshopper.com wrote:

...

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Pete Biggs Sent: Friday, August 24, 2018 10:00 AM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

...

Here's the link for the maillog:

https://paste.fedoraproject.org/paste/kbH2N9Pc~JPuCqVpE1kszQ

OK. There are a couple of things:

Aug 23 21:47:18 ts130 postfix/smtpd[3750]: warning: hostname localhost does not resolve to address 127.0.0.1 Aug 23 21:47:18 ts130 postfix/smtpd[3750]: connect from unknown[127.0.0.1]

That needs to be fixed. What does the entry for 127.0.0.1 look like in /etc/hosts? Have you also defined ::1 to be localhost in /etc/hosts?

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 192.168.1.110 ts130.palmettodomains.com ts130 192.168.1.110 mail.palmettodomains.com mail

# ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.102 edukes1.palmettodomains.com edukes1 192.168.1.105 hp8200.palmettodomains.com hp8200

...

Aug 23 21:47:21 ts130 dovecot: imap-login: Login: user=<tdukes>, method=PLAIN, rip=::1, lip=::1, mpid=3754, secured, session=<9W1yjiR08AAAAAAAAAAAAAAAAAAAAAAB>

So you are connecting over TCPv6 from roundcube to dovecot? Is that what you want?

I have IPV6 disabled (I think).

You have it disabled in the configs you have shown.. but roundcube is configured to expect it to work. You are going to need to figure out where that is in the dovecot (possibly a

find /etc -type f -print | xargs grep -l "::1"

might give you some ideas unless this is in the database where you will be needing to play with that. It may be just easier to just turn on ipv6 and get that working again as that seems to be what 'broke' mail versus the kernel upgrade. [The kernel reboot probably just brought to light a 'oh I have ipv6 required somewhere but it is deeply hidden']

...

OK. There are a couple of things:

Aug 23 21:47:18 ts130 postfix/smtpd[3750]: warning: hostname localhost does not resolve to address 127.0.0.1 Aug 23 21:47:18 ts130 postfix/smtpd[3750]: connect from unknown[127.0.0.1]

That needs to be fixed. What does the entry for 127.0.0.1 look like in /etc/hosts? Have you also defined ::1 to be localhost in /etc/hosts?

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 192.168.1.110 ts130.palmettodomains.com ts130 192.168.1.110 mail.palmettodomains.com mail

# ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.102 edukes1.palmettodomains.com edukes1 192.168.1.105 hp8200.palmettodomains.com hp8200

In the file /etc/nsswitch.conf there is a line that starts hosts: what does that say?

...

Aug 23 21:47:21 ts130 dovecot: imap-login: Login: user=<tdukes>, method=PLAIN, rip=::1, lip=::1, mpid=3754, secured, session=<9W1yjiR08AAAAAAAAAAAAAAAAAAAAAAB>

So you are connecting over TCPv6 from roundcube to dovecot? Is that what you want?

I have IPV6 disabled (I think).

Well it's certainly trying to connect via v6 - that's what the ::1 on that line is.

...

What is the IMAP hostname in the roundcube configuration?

$config['default_host'] = 'localhost';

I think part of the problem is that 'localhost' is being interpreted as the IPv6 loopback device ::1 and not the v4 127.0.0.1 - it may be that roundcube has got a wrong mailhost stored. Try running the following SQL command on your roundcube database:

mysql --user=rc -p roundcubemail -e "select username,mail_host from users;"

It will prompt for the password. (Obviously use a different user if it's not 'rc' and a different databasename if it's not 'roundcubemail' - they are the defaults and are defined in the roundcube config file.)

It will come back with a list of the users defined and the mailhost it will attempt to connect to for that user.

P.

On Fri, 24 Aug 2018 at 14:15, TE Dukes tdukes@palmettoshopper.com wrote:

#hosts: db files nisplus nis dns hosts: dns files myhostname

^^^ that's probably broke also. hosts: files dns

That should be it. Putting dns first works if you can guarentee that DNS works fine all the time but if your DNS caches that localhost doesn't exist then /etc/hosts isn't used.

aliases: files nisplus

since you are doing email

aliases: files

On 08/24/2018 03:15 PM, TE Dukes wrote:

Made those changes and rebooted. No change. Still times out.

What do you get from this command?

getent hosts localhost

Can you reach localhost by "normal" means?

telnet localhost 25

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Stephen John Smoogen Sent: Saturday, August 25, 2018 3:12 PM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

On Fri, 24 Aug 2018 at 18:16, TE Dukes tdukes@palmettoshopper.com wrote:

...

...

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of

Stephen

...

...

John Smoogen Sent: Friday, August 24, 2018 3:58 PM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

On Fri, 24 Aug 2018 at 14:15, TE Dukes tdukes@palmettoshopper.com wrote:

...

...

#hosts: db files nisplus nis dns hosts: dns files myhostname

^^^ that's probably broke also. hosts: files dns

That should be it. Putting dns first works if you can guarentee that DNS works fine all the time but if your DNS caches that localhost doesn't exist then /etc/hosts isn't used.

...

aliases: files nisplus

since you are doing email

aliases: files

-- Stephen J Smoogen.

Hello,

Made those changes and rebooted. No change. Still times out.

OK in that case something is really taking your system for a ride. I would check to see if that 71.28.79.87 is your 'public' ip address with

My ip has changed since I ran telnet localhost 25 as I rebooted my router. But it is correctly reporting the IP.

curl -4 icanhazip.com

if it is then something from named or some other utility is translating localhost for you. host -v localhost might give you more information on what is giving lookups crazy answers

[smooge@linode01 ~]$ host -v localhost Trying "localhost.members.linode.com" Trying "localhost.smoogespace.com" Trying "localhost" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10855 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 10800 IN A 127.0.0.1

Received 55 bytes from 66.228.53.5#53 in 0 ms Trying "localhost" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2461 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION: ;localhost. IN MX

;; AUTHORITY SECTION: localhost. 10800 IN SOA localhost. nobody.invalid. 1 3600 1200 604800

10800

-- Stephen J Smoogen.

Results from host -v localhost:

Trying "localhost.palmettodomains.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12975 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION: ;localhost.palmettodomains.com. IN A

;; ANSWER SECTION: localhost.palmettodomains.com. 60 IN A 162.40.201.5

Received 63 bytes from 166.102.165.13#53 in 35 ms Trying "localhost.palmettodomains.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60995 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION: ;localhost.palmettodomains.com. IN AAAA

;; AUTHORITY SECTION: palmettodomains.com. 628 IN SOA ns2.no-ip.com. hostmaster.no-ip.com. 2015063193 10800 1800 604800 1800

Received 104 bytes from 166.102.165.13#53 in 28 ms Trying "localhost.palmettodomains.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62881 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION: ;localhost.palmettodomains.com. IN MX

;; ANSWER SECTION: localhost.palmettodomains.com. 1720 IN MX 5 mail.palmettodomains.com.

Received 68 bytes from 166.102.165.13#53 in 29 ms

Looks like my domainname has been appended unless you left your off.

Thanks!!

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Barry Brimer Sent: Sunday, August 26, 2018 10:38 AM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

I haven't read through all of this, but is this a CentOS 7 machine? If so

.. I

believe that systemd has some name resolution facility in it. Has that

been

looked into?

On August 25, 2018 2:11:38 PM CDT, Stephen John Smoogen smooge@gmail.com wrote:

...

On Fri, 24 Aug 2018 at 18:16, TE Dukes tdukes@palmettoshopper.com wrote:

...

...

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of

Stephen

...

...

John Smoogen Sent: Friday, August 24, 2018 3:58 PM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

On Fri, 24 Aug 2018 at 14:15, TE Dukes tdukes@palmettoshopper.com wrote:

...

...

#hosts: db files nisplus nis dns hosts: dns files myhostname

^^^ that's probably broke also. hosts: files dns

That should be it. Putting dns first works if you can guarentee

that

...

...

DNS works fine all the time but if your DNS caches that localhost doesn't exist then /etc/hosts isn't used.

...

aliases: files nisplus

since you are doing email

aliases: files

-- Stephen J Smoogen.

Hello,

Made those changes and rebooted. No change. Still times out.

OK in that case something is really taking your system for a ride. I would check to see if that 71.28.79.87 is your 'public' ip address with

curl -4 icanhazip.com

if it is then something from named or some other utility is translating localhost for you. host -v localhost might give you more information on what is giving lookups crazy answers

[smooge@linode01 ~]$ host -v localhost Trying "localhost.members.linode.com" Trying "localhost.smoogespace.com" Trying "localhost" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10855 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 10800 IN A 127.0.0.1

Received 55 bytes from 66.228.53.5#53 in 0 ms Trying "localhost" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2461 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION: ;localhost. IN MX

;; AUTHORITY SECTION: localhost. 10800 IN SOA localhost. nobody.invalid. 1 3600 1200 604800 10800

-- Stephen J Smoogen.

Thanks, yes it's a CentOS 7.5.1804. I do not know about the system.

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Pete Biggs Sent: Friday, August 24, 2018 5:16 PM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

...

...

I think part of the problem is that 'localhost' is being interpreted

as

...

...

the IPv6 loopback device ::1 and not the v4 127.0.0.1 - it may be that roundcube has got a wrong mailhost stored. Try running the following SQL command on your roundcube database:

mysql --user=rc -p roundcubemail -e "select username,mail_host from users;"

It will prompt for the password. (Obviously use a different user if it's not 'rc' and a different databasename if it's not 'roundcubemail'

• they are the defaults and are defined in the roundcube config file.)

It will come back with a list of the users defined and the mailhost it will attempt to connect to for that user.

P.

I seem to have forgotten the password I used. Have tried everything. I

may

...

have to re-install roundcube.

A bit further up in the roundcube config file there's a line defining the database connection. The username, password and database name are all in the definition - something like

$config['db_dsnw'] = 'mysql://username:password@host/database';

P.

Thanks!!

I ran the query. Got something like this

+---------------------------+-------------------------+ | username | mail_host | +---------------------------+-------------------------+ | tdukes | localhost | +---------------------------|-------------------------+

On 08/24/2018 05:40 PM, TE Dukes wrote:

...

getent hosts localhost

::1 localhost

Can't say that's what I expected.  What about "getent hosts 127.0.0.1"?

Also, uncomment the ::1 line in /etc/hosts.

...

Can you reach localhost by "normal" means?     telnet localhost 25

I cannot.

Can you share the specific output of the command?  It might help. From what you've told us, localhost resolves to the IPv6 local address, and that address is present on your "lo" device.  You *should* be able to connect.  The type of error might indicate what is still wrong with the system.

...

...

...

Can you reach localhost by "normal" means? telnet localhost 25

I cannot.

Can you share the specific output of the command? It might help. From what you've told us, localhost resolves to the IPv6 local address, and that address is present on your "lo" device. You *should* be able to connect. The type of error might indicate what is still wrong with the system.

Trying 71.28.79... telnet: connect to address 71.28.79.87: Connection timed out

So are you saying that if you do 'telnet localhost 25' it actually tries to connect to '71.28.79.87'?

If so, then that seems to indicate that host lookups are still being done primarily through DNS and it isn't looking in your /etc/hosts file.

What happens if you do

telnet 127.0.0.1 25

what about

telnet ::1 25

P.

On 08/25/2018 03:35 AM, TE Dukes wrote:

...

Can't say that's what I expected. What about "getent hosts 127.0.0.1"?

127.0.0.1 localhost

OK.  /etc/hosts isn't being used.  You indicated earlier that you had more hostnames in that file.  They should show up there.

Let's go back to pastebin.  What are the contents of /etc/nsswitch.conf and /etc/hosts, now?

Are you running nscd, nslcd, or sssd?  If so, you may need to stop them or flush their cache.

What do you get if you "dig @localhost localhost +short".  If that doesn't return a "localhost" address, then the name server that you're running has a broken configuration.

Do you get any output from "echo $HOSTALIASES"?

...

On 08/25/2018 03:35 AM, TE Dukes wrote:

...

...

Can't say that's what I expected. What about "getent hosts 127.0.0.1"?

127.0.0.1 localhost

OK. /etc/hosts isn't being used. You indicated earlier that you had more hostnames in that file. They should show up there.

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

You are multiply defining localhost and localhost.localdomain. All there should be is:

127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6

But that's not the underlying issue, it's just a complication. What the 'getent hosts 127.0.0.1' is showing is that the system is either not retrieving host information from the /etc/hosts file or not retrieving it all. That same command on my system returns

127.0.0.1 localhost.localdomain localhost

i.e. the line identical to the one in /etc/hosts. Yours doesn't. What does /etc/host.conf contain - does it have the line 'multi on' in it?

...

Are you running nscd, nslcd, or sssd? If so, you may need to stop them or flush their cache.

None of the above are running

Your nsswitch.conf files shows that you are retrieving information from sssd for users. (But not for hosts, so it's not relevant here)

...

What do you get if you "dig @localhost localhost +short". If that doesn't return a "localhost" address, then the name server that you're running has a broken configuration.

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @localhost localhost +short ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

Are you running your own named? (I thought you said you were - this output says you aren't.)

P.

On 08/25/2018 11:30 AM, Pete Biggs wrote:

You are multiply defining localhost and localhost.localdomain. All there should be is:

127.0.0.1		localhost.localdomain localhost
::1	 		localhost6.localdomain6 localhost6

The entries he posted were normal, default entries for CentOS and Fedora systems.

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Gordon Messmer Sent: Sunday, August 26, 2018 2:16 AM To: centos@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@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@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@palmettodomains.com Aug 26 09:12:34 ts130 postfix/cleanup[2197]: 4670E8252A22: message-id=20180826131234.4670E8252A22@ts130.palmettodomains.com Aug 26 09:12:34 ts130 postfix/qmgr[2194]: 4670E8252A22: from=fail2ban@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@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!

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Sunday, August 26, 2018 11:01 AM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

Am 26.08.2018 um 15:25 schrieb TE Dukes:

...

Checked maillog:

Aug 26 09:12:31 ts130 postfix/qmgr[2194]: E5B948331053:

from=fail2ban@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@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@palmettodomains.com

...

Aug 26 09:12:34 ts130 postfix/cleanup[2197]: 4670E8252A22: message-

id=20180826131234.4670E8252A22@ts130.palmettodomains.com

...

Aug 26 09:12:34 ts130 postfix/qmgr[2194]: 4670E8252A22:

from=fail2ban@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@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

Thanks. I did open the port but made no difference.

I found this in the roundcube mail error file:

[26-Aug-2018 11:48:41 -0400]: <a763f95e> IMAP Error: Login failed for tdukes from 192.168.1.102. Could not connect to localhost:143: php_network_getaddresses: getaddrinfo failed: System error in /usr/share/roundcubemail/program/lib/Roundcube/rcube_imap.php on line 197 (POST /?_task=login?_task=login&_action=login)

There is also a warning about the time zone. It's set as America/New_York in php.ini

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Sunday, August 26, 2018 12:35 PM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

Am 26.08.2018 um 18:12 schrieb TE Dukes:

...

Thanks. I did open the port but made no difference.

I found this in the roundcube mail error file:

[26-Aug-2018 11:48:41 -0400]: <a763f95e> IMAP Error: Login failed for

tdukes

...

from 192.168.1.102. Could not connect to localhost:143: php_network_getaddresses: getaddrinfo failed: System error in /usr/share/roundcubemail/program/lib/Roundcube/rcube_imap.php on

line 197

...

(POST /?_task=login?_task=login&_action=login)

There is also a warning about the time zone. It's set as

America/New_York

in

...

php.ini

Sorry to say, but you have to learn to analyze problems systematically and by following simples approaches. At this point it is not useful to get Roundcube involved.

You see a basic error message "Could not connect to localhost:143". So test that without using additional software. Foremost consult the maillog, in this case the log content produced by dovecot. And test connectivity on the lowest level.

echo QUIT | openssl s_client -connect localhost:143 -starttls imap

I'm getting what appears to be help file with various options when trying to run the above commad

That must be successful first. You can too test "lsof -i :143" or "ss -tulpen | grep 143". And tail your maillog.

Running lsof -i :143, I get:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap (LISTEN) dovecot 1576 root 38u IPv6 32015 0t0 TCP *:imap (LISTEN)

Running ss -tulpen | grep 143 :

tcp LISTEN 0 100 *:143 *:* users:(("dovecot",pid=1576,fd=37)) ino:32014 sk:ffff913e953e2e80 <-> tcp LISTEN 0 100 :::143 :::* users:(("dovecot",pid=1576,fd=38)) ino:32015 sk:ffff913b2e90a100 v6only:1 <->

Thanks!!

Alexander

---

CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Sunday, August 26, 2018 3:46 PM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

Am 26.08.2018 um 20:48 schrieb TE Dukes:

...

...

You see a basic error message "Could not connect to localhost:143". So test that without using additional software. Foremost consult the maillog, in this case the log content produced by dovecot. And test connectivity on the lowest level.

echo QUIT | openssl s_client -connect localhost:143 -starttls imap

I'm getting what appears to be help file with various options when

trying to

...

run the above commad

Can we guess that you don't offer TLS for IMAP connections?

I added this to /etc/postfix/main.cf from https://access.redhat.com/solutions/120383

smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_protocols = !SSLv2, !SSLv3 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtp_tls_protocols = !SSLv2, !SSLv3

...

...

That must be successful first. You can too test "lsof -i :143" or "ss -tulpen | grep 143". And tail your maillog.

Running lsof -i :143, I get:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap (LISTEN) dovecot 1576 root 38u IPv6 32015 0t0 TCP *:imap (LISTEN)

Running ss -tulpen | grep 143 :

tcp LISTEN 0 100 *:143 *:* users:(("dovecot",pid=1576,fd=37)) ino:32014 sk:ffff913e953e2e80 <-> tcp LISTEN 0 100 :::143 :::* users:(("dovecot",pid=1576,fd=38)) ino:32015 sk:ffff913b2e90a100

v6only:1

...

<->

So port 143 is listening. Are we back to the point that your DNS or NSS is broken so that even

I think so. Everything else work, I don't get it.

telnet localhost 143

fails while

telnet 127.0.0.1 143

is successful?

Yes, that is correct localhost fails but 127.0.0.1 responds.

Thanks

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Sunday, August 26, 2018 8:31 PM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

...

Date: Sunday, August 26, 2018 16:25:14 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Sunday, August 26, 2018 3:46 PM

Am 26.08.2018 um 20:48 schrieb TE Dukes:

...

...

You see a basic error message "Could not connect to localhost:143". So test that without using additional software. Foremost consult the maillog, in this case the log content produced by dovecot. And test connectivity on the lowest level.

echo QUIT | openssl s_client -connect localhost:143 -starttls imap

I'm getting what appears to be help file with various options when trying to run the above commad

Can we guess that you don't offer TLS for IMAP connections?

I added this to /etc/postfix/main.cf from https://access.redhat.com/solutions/120383

smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_protocols = !SSLv2, !SSLv3 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtp_tls_protocols = !SSLv2, !SSLv3

Randomly adding lines to a config file isn't going to help things. Those lines, which you added to the postfix config (which will have no impact on dovecot), are -- as the RH documentation indicates -- to turn off weak protocols, they don't turn anything on, other directives are used for that.

...

...

...

...

That must be successful first. You can too test "lsof -i :143" or "ss -tulpen | grep 143". And tail your maillog.

Running lsof -i :143, I get:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap (LISTEN) dovecot 1576 root 38u IPv6 32015 0t0 TCP *:imap (LISTEN)

Running ss -tulpen | grep 143 :

tcp LISTEN 0 100 *:143 *:* users:(("dovecot",pid=1576,fd=37)) ino:32014 sk:ffff913e953e2e80 <-> tcp LISTEN 0 100 :::143 :::* users:(("dovecot",pid=1576,fd=38)) ino:32015 sk:ffff913b2e90a100v6only:1 <->

So port 143 is listening. Are we back to the point that your DNS or NSS is broken so that even

I think so. Everything else work, I don't get it.

...

telnet localhost 143

fails while

telnet 127.0.0.1 143

is successful?

Yes, that is correct localhost fails but 127.0.0.1 responds.

In your pastebin:

https://paste.fedoraproject.org/paste/MMNEJmqIrEzK-A4N3MR0ZA

you show three nameservers:

nameserver 166.102.165.13 nameserver 207.91.5.20 nameserver 127.0.0.1

The first two nameservers belong to my ISP. Should I move 127.0.0.1 to the top?

I can't tell if that's what you still have in place, but note that your dns queries will query those DNS servers in that order. Based on that order, the "localhost" (127.0.0.1) server is the last one that will be queried. Unless explicitly queried (e.g., with an @<nameserver> syntax) it will only be queried if the other two fail.

Could you confirm the current order (and perhaps list) the nameservers in your /etc/resolv.conf file - so we are aware of any changes.

They are still in that order.

I did a "localhost" query against the first two and they respond correctly, e.g.,

;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 86400 IN A 127.0.0.1

;; Query time: 100 msec ;; SERVER: 166.102.165.13#53(166.102.165.13)

Somewhat related to the:

...

telnet localhost 143

fails [while it works when you try 127.0.0.1]

Not sure what I have done, but telnet localhost 143 now works but telnet 127.0.0.1 143 fails.

In an earlier message (from Sunday, August 26, 2018 14:37:57) you state:

...

I have all the files shipped with CentOS. I created 2 zone files

could you please enumerate the "named.*" files that you have under your defined directory. Note, if you've chrooted named that's a different location than in a non-chrooted setup.

total 28 -rw-r--r-- 1 root named 391 Aug 26 17:44 192.168.1.zone drwxrwx--- 2 named named 127 Aug 26 03:46 data/ drwxrwx--- 2 named named 31 Aug 26 16:28 dynamic/ -rw-r--r-- 1 root root 0 Aug 26 20:54 named -rw-r----- 1 root named 2281 May 22 2017 named.ca -rw-r----- 1 root named 152 Dec 15 2009 named.empty -rw-r----- 1 root named 152 Jun 21 2007 named.localhost -rw-r----- 1 root named 168 Dec 15 2009 named.loopback -rw-r--r-- 1 root named 793 Aug 26 17:44 palmettodomains.zone -rw-r--r-- 1 root root 1001 Aug 26 13:29 palmettodomains.zone.082618 drwxrwx--- 2 named named 6 Apr 12 14:48 slaves/

Then there's this:

...

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @localhost localhost +short ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

do you *really* have a name server running on your local machine? Just thought I'd ask.

root 600 0.0 0.0 112704 968 tty2 S+ 21:02 0:00 grep --color=auto named named 21096 0.0 0.3 391636 60160 ? Ssl 17:45 0:00 /usr/sbin/named -u named -c /etc/named.conf

While you are at it, could you show the current state of your /etc/hosts file (as well as its ownerships and permissions).

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 #127.0.0.1 localhost.localdomain localhost 192.168.1.110 ts130.palmettodomains.com ts130 192.168.1.110 mail.palmettodomains.com mail

::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 #::1 localhost6.localdomain6 localhost6 192.168.1.102 edukes1.palmettodomains.com edukes1 192.168.1.105 hp8200.palmettodomains.com hp8200 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

-rw-r--r-- 1 root root 509 Aug 26 14:02 hosts

Thanks!!

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Sunday, August 26, 2018 10:25 PM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

...

Date: Sunday, August 26, 2018 21:10:48 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Sunday, August 26, 2018 8:31 PM

...

Date: Sunday, August 26, 2018 16:25:14 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Alexander Dalloz Sent: Sunday, August 26, 2018 3:46 PM

Am 26.08.2018 um 20:48 schrieb TE Dukes:

...

> You see a basic error message "Could not connect to > localhost:143". So test that without using additional > software. Foremost consult the maillog, in this case the log > content produced by dovecot. And test connectivity on the > lowest level. > > echo QUIT | openssl s_client -connect localhost:143 -starttls > imap I'm getting what appears to be help file with various options when trying to run the above commad

Can we guess that you don't offer TLS for IMAP connections?

I added this to /etc/postfix/main.cf from https://access.redhat.com/solutions/120383

smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_protocols = !SSLv2, !SSLv3 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtp_tls_protocols = !SSLv2, !SSLv3

Randomly adding lines to a config file isn't going to help things. Those lines, which you added to the postfix config (which will have no impact on dovecot), are -- as the RH documentation indicates -- to turn off weak protocols, they don't turn anything on, other directives are used for that.

...

...

...

> That must be successful first. You can too test "lsof -i > :143" or "ss -tulpen | grep 143". And tail your maillog. > Running lsof -i :143, I get:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dovecot 1576 root 37u IPv4 32014 0t0 TCP *:imap (LISTEN) dovecot 1576 root 38u IPv6 32015 0t0 TCP *:imap (LISTEN)

Running ss -tulpen | grep 143 :

tcp LISTEN 0 100 *:143 *:* users:(("dovecot",pid=1576,fd=37)) ino:32014 sk:ffff913e953e2e80 <-> tcp LISTEN 0 100 :::143 :::* users:(("dovecot",pid=1576,fd=38)) ino:32015 sk:ffff913b2e90a100v6only:1 <->

So port 143 is listening. Are we back to the point that your DNS or NSS is broken so that even

I think so. Everything else work, I don't get it.

...

telnet localhost 143

fails while

telnet 127.0.0.1 143

is successful?

Yes, that is correct localhost fails but 127.0.0.1 responds.

In your pastebin:

https://paste.fedoraproject.org/paste/MMNEJmqIrEzK-A4N3MR0ZA

you show three nameservers:

nameserver 166.102.165.13 nameserver 207.91.5.20 nameserver 127.0.0.1

The first two nameservers belong to my ISP. Should I move 127.0.0.1 to the top?

...

I can't tell if that's what you still have in place, but note that your dns queries will query those DNS servers in that order. Based on that order, the "localhost" (127.0.0.1) server is the last one that will be queried. Unless explicitly queried (e.g., with an @<nameserver> syntax) it will only be queried if the other two fail.

Could you confirm the current order (and perhaps list) the nameservers in your /etc/resolv.conf file - so we are aware of any changes.

They are still in that order.

...

I did a "localhost" query against the first two and they respond correctly, e.g.,

;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 86400 IN A 127.0.0.1

;; Query time: 100 msec ;; SERVER: 166.102.165.13#53(166.102.165.13)

Somewhat related to the:

...

telnet localhost 143

fails [while it works when you try 127.0.0.1]

Not sure what I have done, but telnet localhost 143 now works but telnet 127.0.0.1 143 fails.

...

In an earlier message (from Sunday, August 26, 2018 14:37:57) you state:

...

I have all the files shipped with CentOS. I created 2 zone files

could you please enumerate the "named.*" files that you have under your defined directory. Note, if you've chrooted named that's a different location than in a non-chrooted setup.

total 28 -rw-r--r-- 1 root named 391 Aug 26 17:44 192.168.1.zone drwxrwx--- 2 named named 127 Aug 26 03:46 data/ drwxrwx--- 2 named named 31 Aug 26 16:28 dynamic/ -rw-r--r-- 1 root root 0 Aug 26 20:54 named -rw-r----- 1 root named 2281 May 22 2017 named.ca -rw-r----- 1 root named 152 Dec 15 2009 named.empty -rw-r----- 1 root named 152 Jun 21 2007 named.localhost -rw-r----- 1 root named 168 Dec 15 2009 named.loopback -rw-r--r-- 1 root named 793 Aug 26 17:44 palmettodomains.zone -rw-r--r-- 1 root root 1001 Aug 26 13:29 palmettodomains.zone.082618 drwxrwx--- 2 named named 6 Apr 12 14:48 slaves/

...

Then there's this:

...

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @localhost localhost +short ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

do you *really* have a name server running on your local machine? Just thought I'd ask.

root 600 0.0 0.0 112704 968 tty2 S+ 21:02 0:00 grep --color=auto named named 21096 0.0 0.3 391636 60160 ? Ssl 17:45 0:00 /usr/sbin/named -u named -c /etc/named.conf

...

While you are at it, could you show the current state of your /etc/hosts file (as well as its ownerships and permissions).

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 # 127.0.0.1 localhost.localdomain localhost 192.168.1.110 ts130.palmettodomains.com ts130 192.168.1.110 mail.palmettodomains.com mail

::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # ::1 localhost6.localdomain6 localhost6 192.168.1.102 edukes1.palmettodomains.com edukes1 192.168.1.105 hp8200.palmettodomains.com hp8200 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

-rw-r--r-- 1 root root 509 Aug 26 14:02 hosts

Since your:

dig @localhost localhost

failed, try:

dig @127.0.0.1 localhost a

(in this context, i like the longer output as it reveals more).

From dig @127.0.0.1 localhost a

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @127.0.0.1 localhost a ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36452 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 86400 IN A 127.0.0.1

;; AUTHORITY SECTION: localhost. 86400 IN NS localhost.

;; ADDITIONAL SECTION: localhost. 86400 IN AAAA ::1

;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Aug 26 22:29:21 EDT 2018 ;; MSG SIZE rcvd: 96

If that fails, then there is, at minimum, a problem with your local dns server. If that works, try:

dig @localhost4 localhost a

From dig @localhost4 localhost a

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @localhost4 localhost a ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39351 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 86400 IN A 127.0.0.1

;; AUTHORITY SECTION: localhost. 86400 IN NS localhost.

;; ADDITIONAL SECTION: localhost. 86400 IN AAAA ::1

;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Aug 26 22:30:35 EDT 2018 ;; MSG SIZE rcvd: 96

This will explicitly use the ipv4 127. entry in your /etc/hosts, while "localhost" could use either.

[by the way, you appear to have redundant ipv6 "localhost" entries in your /etc/hosts file. mostly to have things clean, i'd get rid of the bottom one.]

Thanks! Not sure where that came from but its been removed.

Thank!!

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:29 AM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

...

Date: Sunday, August 26, 2018 22:37:55 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Sunday, August 26, 2018 10:25 PM

...

Date: Sunday, August 26, 2018 21:10:48 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Sunday, August 26, 2018 8:31 PM

...

Date: Sunday, August 26, 2018 16:25:14 -0400 From: TE Dukes tdukes@palmettoshopper.com

> From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of > Alexander Dalloz > Sent: Sunday, August 26, 2018 3:46 PM > > Am 26.08.2018 um 20:48 schrieb TE Dukes: > >> You see a basic error message "Could not connect to > >> localhost:143". So test that without using additional > >> software. Foremost consult the maillog, in this case the > >> log content produced by dovecot. And test connectivity on > >> the lowest level. > >>

...

...

...

...

...

> > So port 143 is listening. Are we back to the point that your > DNS or NSS is broken so that even

I think so. Everything else work, I don't get it. > > telnet localhost 143 > > fails while > > telnet 127.0.0.1 143 > > is successful? >

Yes, that is correct localhost fails but 127.0.0.1 responds.

In your pastebin:

<https://paste.fedoraproject.org/paste/MMNEJmqIrEzK-

A4N3MR0ZA>

...

...

...

...

you show three nameservers:

nameserver 166.102.165.13 nameserver 207.91.5.20 nameserver 127.0.0.1

The first two nameservers belong to my ISP. Should I move 127.0.0.1 to the top?

...

I can't tell if that's what you still have in place, but note that your dns queries will query those DNS servers in that order. Based on that order, the "localhost" (127.0.0.1) server is the last one that will be queried. Unless explicitly queried (e.g., with an @<nameserver> syntax) it will only be queried if the other two fail.

Could you confirm the current order (and perhaps list) the nameservers in your /etc/resolv.conf file - so we are aware of any changes.

They are still in that order.

...

I did a "localhost" query against the first two and they respond correctly, e.g.,

;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 86400 IN A 127.0.0.1

;; Query time: 100 msec ;; SERVER: 166.102.165.13#53(166.102.165.13)

Somewhat related to the:

...

telnet localhost 143

fails [while it works when you try 127.0.0.1]

Not sure what I have done, but telnet localhost 143 now works but telnet 127.0.0.1 143 fails.

...

...

...

...

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 # 127.0.0.1 localhost.localdomain localhost 192.168.1.110 ts130.palmettodomains.com ts130 192.168.1.110 mail.palmettodomains.com mail

::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # ::1 localhost6.localdomain6 localhost6 192.168.1.102 edukes1.palmettodomains.com edukes1 192.168.1.105 hp8200.palmettodomains.com hp8200 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

-rw-r--r-- 1 root root 509 Aug 26 14:02 hosts

Since your:

dig @localhost localhost

failed, try:

dig @127.0.0.1 localhost a

(in this context, i like the longer output as it reveals more).

From dig @127.0.0.1 localhost a

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @127.0.0.1 localhost a ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36452 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 86400 IN A 127.0.0.1

;; AUTHORITY SECTION: localhost. 86400 IN NS localhost.

;; ADDITIONAL SECTION: localhost. 86400 IN AAAA ::1

;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Aug 26 22:29:21 EDT 2018 ;; MSG SIZE rcvd: 96

...

If that fails, then there is, at minimum, a problem with your local dns server. If that works, try:

dig @localhost4 localhost a

From dig @localhost4 localhost a

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @localhost4 localhost a ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39351 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;localhost. IN A

;; ANSWER SECTION: localhost. 86400 IN A 127.0.0.1

;; AUTHORITY SECTION: localhost. 86400 IN NS localhost.

;; ADDITIONAL SECTION: localhost. 86400 IN AAAA ::1

;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Aug 26 22:30:35 EDT 2018 ;; MSG SIZE rcvd: 96

...

This will explicitly use the ipv4 127. entry in your /etc/hosts, while "localhost" could use either.

Since the localhost4 approach worked, commend out the ipv6 localhost entries in your /etc/hosts file, then try:

IP6 is commented out

dig @localhost localhost a

That works

again. If that works try:

telnet localhost 143

This also works

once again. If those work, it would seem that your ipv6 is messed up and your system is trying it first and not falling back to ipv4.

Regarding your nameserver list in /etc/resolv.conf. If you have a working 127.0.0.1 nameserver you generally don't include external nameservers in that list. So, if non-ipv6 things seem to work, I'd remove the two non-127 nameservers from that list.

Removed the two nameservers. Still can't access mail. Getting connection to storage server failed on the roundcube login page.

Thanks, again!

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:58 AM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

...

Date: Monday, August 27, 2018 07:42:48 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:29 AM

...

Since the localhost4 approach worked, commend out the ipv6 localhost entries in your /etc/hosts file, then try:

IP6 is commented out

...

dig @localhost localhost a

That works

...

again. If that works try:

telnet localhost 143

This also works

...

once again. If those work, it would seem that your ipv6 is messed up and your system is trying it first and not falling back to ipv4.

Regarding your nameserver list in /etc/resolv.conf. If you have a working 127.0.0.1 nameserver you generally don't include external nameservers in that list. So, if non-ipv6 things seem to work, I'd remove the two non-127 nameservers from that list.

Removed the two nameservers. Still can't access mail. Getting connection to storage server failed on the roundcube login page.

...

That you can now successfully get to "localhost" is good progress. Seems you want to stay away from ipv6 networking issues unless/until you resolve whatever that issue is.

Roundcube is, potentially, a totally separate issue. I don't use it, so can only suggest minimal debugging ideas.

What is the hostname that you use to get to your roundcube instance? Can you resolve that:

dig <hostname> a

If you get an answer, is the ipnumber correct?

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mail.palmettodomains.com. IN A

;; ANSWER SECTION: mail.palmettodomains.com. 86400 IN A 192.169.1.110

;; AUTHORITY SECTION: palmettodomains.com. 86400 IN NS dns1.palmettodomains.com.

;; ADDITIONAL SECTION: dns1.palmettodomains.com. 86400 IN A 192.168.1.110 dns1.palmettodomains.com. 86400 IN AAAA aaaa:bbbb::110

;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Mon Aug 27 09:01:48 EDT 2018 ;; MSG SIZE rcvd: 132

Note, if the hostname for your roundcube instance is one of the ipv6 entries in your /etc/hosts file, I'd remove that - and either put in an ipv4 entry or put an entry for it in your dns.

Thanks again! I still think it's a mail issue. I can't get mail using usermin either.

Think I'm going to remove the TLS stuff from postfix main.cf that I added yesterday and retry.

Richard wrote:

...

Date: Monday, August 27, 2018 09:05:05 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:58 AM

...

Date: Monday, August 27, 2018 07:42:48 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:29 AM

Since the localhost4 approach worked, commend out the ipv6 localhost entries in your /etc/hosts file, then try:

IP6 is commented out

...

dig @localhost localhost a

That works

...

again. If that works try:

telnet localhost 143

This also works

...

once again. If those work, it would seem that your ipv6 is messed up and your system is trying it first and not falling back to ipv4.

Regarding your nameserver list in /etc/resolv.conf. If you have a working 127.0.0.1 nameserver you generally don't include external nameservers in that list. So, if non-ipv6 things seem to work, I'd remove the two non-127 nameservers from that list.

Removed the two nameservers. Still can't access mail. Getting connection to storage server failed on the roundcube login page.

...

That you can now successfully get to "localhost" is good progress. Seems you want to stay away from ipv6 networking issues unless/until you resolve whatever that issue is.

Roundcube is, potentially, a totally separate issue. I don't use it, so can only suggest minimal debugging ideas.

What is the hostname that you use to get to your roundcube instance? Can you resolve that:

dig <hostname> a

If you get an answer, is the ipnumber correct?

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mail.palmettodomains.com. IN A

;; ANSWER SECTION: mail.palmettodomains.com. 86400 IN A 192.169.1.110

;; AUTHORITY SECTION: palmettodomains.com. 86400 IN NS dns1.palmettodomains.com.

;; ADDITIONAL SECTION: dns1.palmettodomains.com. 86400 IN A 192.168.1.110 dns1.palmettodomains.com. 86400 IN AAAA aaaa:bbbb::110

;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Mon Aug 27 09:01:48 EDT 2018 ;; MSG SIZE rcvd: 132

...

Note, if the hostname for your roundcube instance is one of the ipv6 entries in your /etc/hosts file, I'd remove that - and either put in an ipv4 entry or put an entry for it in your dns.

Thanks again! I still think it's a mail issue. I can't get mail using usermin either.

Think I'm going to remove the TLS stuff from postfix main.cf that I added yesterday and retry.

Those TLS lines that you added to your postfix config file yesterday have nothing to do with your ability (or not) to get to your roundcube instance. I believe that the roundcube frontend is an application that runs via httpd/apache. Assuming I am correct on that, debugging your apache setup would be the next set of things to look at. Confirm that it (apache) is running and listening on the port(s) you expect it on (netstat and ps will help there) and then start with the access and error logs.

Pardon me if I butt in - I haven't really been following this thread, but what's selinux set to - off, permissive, enforcing?

mark

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of centos--- via CentOS Sent: Monday, August 27, 2018 9:31 AM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

On 08/27/2018 09:05 AM, TE Dukes wrote:

...

...

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:58 AM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working

...

Date: Monday, August 27, 2018 07:42:48 -0400 From: TE Dukes tdukes@palmettoshopper.com

...

From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:29 AM

...

Since the localhost4 approach worked, commend out the ipv6 localhost entries in your /etc/hosts file, then try:

IP6 is commented out

...

 dig @localhost localhost a

That works

...

again. If that works try:

 telnet localhost 143

This also works

...

once again. If those work, it would seem that your ipv6 is messed up and your system is trying it first and not falling back to ipv4.

Regarding your nameserver list in /etc/resolv.conf. If you have a working 127.0.0.1 nameserver you generally don't include external nameservers in that list. So, if non-ipv6 things seem to work, I'd remove the two non-127 nameservers from that list.

Removed the two nameservers. Still can't access mail. Getting connection to storage server failed on the roundcube login page.

...

That you can now successfully get to "localhost" is good progress. Seems you want to stay away from ipv6 networking issues unless/until you resolve whatever that issue is.

Roundcube is, potentially, a totally separate issue. I don't use it, so can only suggest minimal debugging ideas.

What is the hostname that you use to get to your roundcube instance? Can you resolve that:

dig <hostname> a

If you get an answer, is the ipnumber correct?

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mail.palmettodomains.com. IN A

;; ANSWER SECTION: mail.palmettodomains.com. 86400 IN A 192.169.1.110

;; AUTHORITY SECTION: palmettodomains.com. 86400 IN NS

dns1.palmettodomains.com.

...

;; ADDITIONAL SECTION: dns1.palmettodomains.com. 86400 IN A 192.168.1.110 dns1.palmettodomains.com. 86400 IN AAAA aaaa:bbbb::110

;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Mon Aug 27 09:01:48 EDT 2018 ;; MSG SIZE rcvd: 132

...

Note, if the hostname for your roundcube instance is one of the ipv6 entries in your /etc/hosts file, I'd remove that - and either put in an ipv4 entry or put an entry for it in your dns.

Thanks again! I still think it's a mail issue. I can't get mail using usermin either.

Think I'm going to remove the TLS stuff from postfix main.cf that I

added

...

yesterday and retry.

If I missed this further up thread my apologies - is SELinux enabled and are there any relevant exceptions being logged?

Pretty sure SELinux is turned off unless it got turned on without my knowledge through an updtate/upgrade.

I removed the TLS lines from main.cf I added last night and remotely did a reboot from here at work.

Mail is again working!! I am skeptical to mark this thread solved as I thought it was solved back in July.

I think, removing my ISP's DNS servers from resolve.conf was the fix, could be removing IPV6 from etc/hosts. Might put it back in just to see.

Again, many, many thanks!!

I really want to thank everyone for their help and patience!!

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Gordon Messmer Sent: Sunday, August 26, 2018 12:35 PM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

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': failure

That'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.

I have all the files shipped with CentOS. I created 2 zone files, domain and reverse from the example in RHEL Documentation https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/htm...

https://paste.fedoraproject.org/paste/9-ZvmUg5vF-UI7lfuAIJjQ

I did find one typo in the domain zone but correcting that didn't help

"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.

Getent hosts localhost and getent hosts 127.0.0.1 returned no info.

Thanks!

-----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of Jonathan Billings Sent: Friday, August 24, 2018 8:12 AM To: centos@centos.org Subject: Re: [CentOS] Mail has quit working

On Fri, Aug 24, 2018 at 07:17:29AM -0400, TE Dukes wrote:

...

I have removed DNS3 from ifcfg-eno1 and set ONBOOT=no in ifcfg-enp1so0, reboot and still can't read mail. Logging into roundcube either times out or if I get in, the inbox is empty.

It sounds to me like you just have a broken apache httpd or roundcube setup. Try ignoring that for now.

Can you verify that mail is getting to where you've got it set up using other tools, such as mutt or just looking at the spool files?

-- Jonathan Billings billings@negate.org _______________________________________________

Thanks,

There is mail in ~/Maildir/new