If I don’t need any of the advanced things, then I do not need to use the POSTCONF_smtpd_tls... variables, right? The website is of course https.

If it started last November, that’s almost certainly the Let’s Encrypt root certificate expiry. You should just need to pull the new image and rebuild. [immagine] Self-hosted mail-receiver update following Let's Encrypt root certificate change announcements This announcem…

You won’t need the variations above but you will still need the TLS config found in samples/mail-receiver.yml, modified for your domain name, in order to support TLS encryption. Assuming you’re using the Let’s Encrypt template for https, the lines from the sample just need to be uncommented with th…

hm, then any ideas why it stopped working recently, showing this error about certificates? <19>Oct 6 19:18:27 receive-mail[94]: Failed to POST the e-mail to https://www..../admin/email/handle_mail: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (O…

Well the error is showing that it has received an email and is failing to verify the certificate trying to connect to your Discourse instance. This tells us that the issue isn’t with something else connecting to your mail receiver, though not necessarily that TLS is working. (The email may have been…

If you would include your hostname then we could help more. Have you changed the domain name of your site? Is the certificate correct on the site? Has anything else changed on the site in the past 90 days?

https://www.programmersforum.rocks No changes in the domain or anything, the site works fine. Actually the logs show that it started last November, but still there were no changes.

Ok, so that certificate is perfectly fine. Tell us more about the mail server that connects to your forum. Is it a regular mail-receiver docker container?

[immagine] Alex P.: https://www.programmersforum.rocks [immagine] Richard - Communiteq: Ok, so that certificate is perfectly fine. I checked it with //email/testTo: ; if you want to see for yourself, that’s a way to test. As Richard suggests, the problem does not appear to be with Dis…

[immagine] Jay Pfaffman: As Richard suggests, the problem does not appear to be with Discourse the email receiver. No, I think the issue is between the email receiver and Discourse. Discourse is public facing so I was able to check Discourse’s certificate and see that it was fine. So my sus…

[immagine] Simon Manning: If it started last November, that’s almost certainly the Let’s Encrypt root certificate expiry. That sounds like a good possibility! [immagine] Richard - Communiteq: No, the issue is between the email receiver and Discourse. Agreed, but Simon’s explanation mi…

[immagine] Simon_Manning: If it started last November [immagine] Alex P.: it stopped working recently :thinking: …

Il server di posta in arrivo ha un errore di certificato

Supporto Installazione

Simon_Manning (Simon Manning) 6 Ottobre 2022, 9:40pm 9

Se è iniziato lo scorso novembre, è quasi certamente la scadenza del certificato root di Let’s Encrypt. Dovresti semplicemente estrarre la nuova immagine e ricompilare.

Argomento		Risposte	Visualizzazioni
Possible bug with mail: certificate verify failed (unable to get local issuer certificate) Self-hosting	6	651	Dicembre 27, 2023
Hostname doesn't match server certificate (Let's Encrypt) Self-hosting	4	1585	Novembre 11, 2021
Discourse setup completed successfully but not working due to SSL error Support	6	336	Dicembre 18, 2024
Issue with mail-receiver and self-signed certificate? Self-hosting mail-receiver	4	401	Maggio 31, 2023
Emails not working after upgrade: certificate verify failed Self-hosting	1	1244	Maggio 13, 2022

Il server di posta in arrivo ha un errore di certificato

Argomenti correlati