CentOS - Aug 2018 - 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

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

Alexander

> -----Original Message-----
> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Alexander
> Dalloz
> Sent: Sunday, August 26, 2018 12:35 PM
> To: centos at 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 at centos.org
> https://lists.centos.org/mailman/listinfo/centos

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?
>> 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

telnet localhost 143

fails while

telnet 127.0.0.1 143

is successful?
> Thanks!!
Alexander