Haraka - View Closed Connections

[JLX89]

Hello All,
We are using a LAMP App that uses email piping and access via IMAP and or POP3 and getting errors "Error: cannot read - connection closed".

Is there a way to research this in the Haraka logs to view why the connection might be closed?

Thank you

[girish]

@JLX89 So the LAMP app is using IMAP and POP3 to access some mailboxes which are hosted in Cloudron ? Both these protocols are implemented by dovecot and not by Haraka. Dovecot logs are in /run/dovecot/dovecot.log of the mail container. You can docker exec -ti mail /bin/bash and then inspect the file.

Have you just tried simple openssl s_client -connect mailserver.domain.com 993 from LAMP app's web terminal ? Does it connect?

[JLX89]

@girish I've found the following, looks like it just drops for around a minute and then works again.

Mar 02 19:16:21 auth: Error: LDAP: Connection lost to LDAP server, reconnecting
Mar 02 19:16:21 auth: Error: LDAP: Can't connect to server: 172.18.X.X:3002
Mar 02 19:16:23 auth: Info: ldap(user@domain.com,149.28.X.X,<T6POp+/1YuCVHCuj>): Aborting (timeout), we're not connected to LDAP server
Mar 02 19:16:24 auth: Error: LDAP: Can't connect to server: 172.18.X.X:3002
Mar 02 19:16:25 imap-login: Info: Aborted login (auth service reported temporary failure): user=<user@domain.com>, method=PLAIN, rip=149.28.X.X, lip=172.18.X.X, >

[girish]

@JLX89 In the mail container does telnet 172.18.0.1 3002 work ? (that is the LDAP server) . It should look like this:

# telnet 172.18.0.1 3002
Trying 172.18.0.1...
Connected to 172.18.0.1.
Escape character is '^]'.

[JLX89]

@girish Yeah, that seems to be working.

telnet 172.18.0.1 3002
Trying 172.18.0.1...
Connected to 172.18.0.1.
Escape character is '^]'.

[girish]

@JLX89 can you check if supervisorctl restart dovecot inside mail container helps? Otherwise, if you write to us at support@cloudron.io , I can take a look. It's not clear why it cannot connect to the LDAP server. It's really just connecting internally ...

[JLX89]

@girish Thank you -- that actually seems to have solved the issue for now!