Can't set up SMTP correctly =\

FATAL 2021-04-04 11:00:06 UTC #1

Hi everyone!
I use Debian 10 and installed just as it said here: https://github.com/EGroupware/egroupware/wiki/20.1--Installation-using-egroupware-docker-RPM-DEB-package
Latest version. However keep in mind what I tried 14 and 17 versions too (quite some time ago).

I have a problem with email account setup. It works perfectly on 1.8 CE version but in 20 version it says:
Error when communicating with the server. (2) ©
I get an error every time when I try to set Secure connection: No, 25 port SMTP settings, which is actually working.

Where should I start looking? This error message needs clarification, where is the logs now?

StefanU 2021-04-04 14:45:06 UTC #2

Hi Aleksey.

First:
Is your mail server very old? Then check:

You could test an older EGroupware version (< 20.1.20210324) to verify this:

For now:
If you go through the wizard in the email account, you will get more information.

Do you have access to the mail server?

Stefan

FATAL 2021-04-04 16:56:57 UTC #3

No, this issue is unrelated to me.
First of all, this problem appeared a long time ago, in 14 version (or sort of). At least 3 years old.
Moreover, I updated mail server to check this out. Nothing changed (so I rolled back for some other reasons).

Perhaps I used some other Wizard? This one told me Error when communicating with the server. (2)
I have an access. I created:
login/pass

*(deleted)

The server:
mail.dnk-diagnostika.ru

StefanU 2021-04-04 20:30:44 UTC #4

Hi Aleksey.

My result:

The resolved IP address gives the same result.

If so, you should look there to see why the mail server is rejecting the connection.

I can only assume that there is something wrong with his SSL certificate.

Or:
Bye professional support:

Stefan

RalfBecker 2021-04-04 20:50:16 UTC #5

Problem is the server only supports SSLv3:

openssl s_client --starttls smtp -connect mail.dnk-diagnostika.ru:25
---
New, SSLv3, Cipher is DHE-RSA-AES256-SHA

Even if you select Secure connection: No, but the server advertises StartTLS, we try it and the fail because of the old TLS version.

Please update you mailserver to support a recent TLS version.

Ralf

FATAL 2021-04-04 21:23:52 UTC #6

Moreover, I updated mail server to check this out. Nothing changed (so I rolled back for some other reasons).©

FATAL 2021-04-04 21:33:34 UTC #7

SSL, TLS, SHMLS… It works just fine without it. So this cannot be related. It would be insane.

And this is why I’m stuck here. I already tried to blame everything related to secure connection but

I don’t use it ( you can confirm it in different ways)
I tried to update the server, nothing changed, rolled back.
This problem exist some time so no reason to blame recently updates.

RalfBecker 2021-04-05 06:44:50 UTC #8

Please read what I wrote:

The problem is your old TLS version SSLv3, which was disabled by the unlaying Ubuntu 20.04 / PHP 7.3.27 of our latest maintenance release. There are currently only two ways around it:

downgrade to the previous maintenance release (by changing the tag in your /etc/egroupware-docker/docker-compose.override.yml to 20.1.20210125-2), which is only recommended as a temporary solution until you
upgrade your mailserver to use one of the secure and recommended TLS versions, which are TLSv1.2+

Ralf

FATAL 2021-04-05 07:40:16 UTC #9

I said what this error was in previous versions as well (that was definetely 17 at least), but whatever.

I downgraded successfully to 20.1.20210125-2 and Egroupware suggest maintenance update, so it went well. I mean, downgrade.
The error didn’t go anywhere =(

FATAL 2021-04-19 16:45:19 UTC #10

Because simply upgrading TLS or downgrade Egroupware version did nothing I created new mailserver and migrated everything there. Now it works correctly.