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