Closed laymonk closed 1 year ago
We don't provide support here on GitHub Either ask in our telegram channel or in our forum
I think it's wrong to consider this a support issue. This is vleat;y a bug on TLS usage in postfix that is not dependent on user configuration.
This is resolved now, thankls to MAGIC from the forum ... not sure how I ended up having data/conf/postfix/main.cf replaced by contents of extra.cf ...
Stopping postfix-mailcow, and recreateing data/conf/postfix/main.cf and then restarting postfix-mailcow has fixed it.
@laymonk, your private key is posted above. You should re-create your private key.
Yeah, I recreated it immediately after posting that ...
Thanks for the heads up.
On Mon, 3 Apr 2023 at 05:25, Simon Biggs @.***> wrote:
@laymonk https://github.com/laymonk, your private key is posted above. You should re-create your private key.
— Reply to this email directly, view it on GitHub https://github.com/mailcow/mailcow-dockerized/issues/5156#issuecomment-1493644268, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPEMHOYK6OUOBOBCRAKGMDW7JGMRANCNFSM6AAAAAAWMSK3M4 . You are receiving this because you were mentioned.Message ID: @.***>
Contribution guidelines
I've found a bug and checked that ...
Description
I then tried a few things to resolve this:
Relay this domain
was set andRelay all recipients
was set.None of these helped until I ran the following command - (see this):
That problem was fixed (error message went away), but then mail delivery to users was failing on account of
Relay access denied
. Also, users could no longer send emails, as it was failing to smtp authentication error. Both seemed TLS related.I looked at the
/etc/postfix/main.cf
in the postfix container and discovered that it had:So, essentially, TLS was broken and that meant external senders couldn't auth via sasl, and relay failed.
So, my focus shifted to looking at SSL.
The mailcow version was from early last year, so I decided to update to the latest first. But after the updates, the issues remained ...
Things I have since tried ... but none helped
Need to figure out how to ensure postfix sees the certs being obtained by acme
Logs:
The issues reported by ACME and Postfix and openssl tests
Acme renews the certs successfully or detects certs don't need renewal, but throws up a few repeated errors in it's logs
Openssl tests of all the mailports fail with the same library errors
root@mail:~/mailcow-dockerized# openssl s_client -showcerts -connect mail.example.net:587 -starttls smtp CONNECTED(00000003) 139983341598016:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331:
no peer certificate available
No client certificate CA names sent
SSL handshake has read 268 bytes and written 346 bytes Verification: OK
New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok)
root@mail:~/mailcow-dockerized# bash helper-scripts/expiry-dates.sh unable to load certificate 139828192908608:error:0909006C:PEM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: TRUSTED CERTIFICATE TLS expiry dates: Postfix: Dovecot: Jun 27 21:11:36 2023 GMT Nginx: Jun 27 21:11:36 2023 GMT
postfix/submission/smtpd[411]: warning: No server certs available. TLS won't be enabled ... postfix/smtps/smtpd[379]: warning: Wrapper-mode request dropped from unknown[46.148.40.197] for service smtps. TLS context initialization failed. For details see earlier warnings in your logs.
Which branch are you using?
master
Operating System:
Ubuntu 20.04
Server/VM specifications:
16GB; 2 Core x Xeon X5550 @ 2.67 GHz
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
None
Docker version:
23.0.2
docker-compose version or docker compose version:
v2.17.2
mailcow version:
2023-03
Reverse proxy:
Nginx
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: