For some reason, I am not getting a mail from my discourse setup.
I already tested my SMTP settings and they are working for other platforms
Also tested it with Telnet.
For some reason, I am not getting a mail from my discourse setup.
I already tested my SMTP settings and they are working for other platforms
Also tested it with Telnet.
See Troubleshooting email on a new Discourse install.
A common problem is that Discourse is sending from an address that your server will not accept.
I am in a similar situation. Installed, website responds, registration e-mail never gets there. Tested sending e-mail from the discourse server, from inside the app container using the same configuration/credentials => works, test message sent and received correctly. Running doctor gives me:
Sending mail to my_correct_user@my_correct_domain. . .
Testing sending to my_correct_user@my_correct_domain using correct_smtp_server_name:465, username:correct_smpt_user@correct_sender_domain with plain auth.
======================================== ERROR ========================================
UNEXPECTED ERROR
Net::ReadTimeout
====================================== SOLUTION =======================================
This is not a common error. No recommended solution exists!
[....]
I tried switching port to 587, then the Net::ReadTimeout doesn’t show in the logs but still nothing gets sent. What next? What is the correct content of DISCOURSE_SMTP_DOMAIN ? That’s the only thing I am still suspicious about.
same issue here. Please help
If you’re getting a read timeout it’s because the outgoing smtp port is blocked. You’ll need to get it unblocked or use another port.
Personalmente uso el puerto submission en ese servidor, por lo que ciertamente no está bloqueado. Y, correcto, cuando se usa 587, el error de tiempo de espera no aparece. Dado que no tengo forma de realizar cambios en la configuración del servidor, ¿debo entender que solo se admite SMTPS?
El puerto 587 tiene TLS explícito (STARTTLS) y un servidor de correo podría configurarse para aceptar envíos en ese puerto sin requerir TLS, por lo que podrías usar SMTP sin cifrar en ese puerto.
(El puerto 465, ahora algo obsoleto, tenía TLS implícito y no tenías opción allí).
Bien, el servidor está configurado para funcionar con TLS explícito en el puerto de envío (587). Ahora, ¿qué se necesita hacer en la configuración de Discourse para que funcione en el puerto 587 con TLS? ¿Debería/no debería funcionar OOB (out-of-the-box)?
Hay DISCOURSE_SMTP_ENABLE_START_TLS que es true por defecto.