Problem with SMTP configuration

Product Support Self-hosting
1

Hi!
I went through most of the “SMTP problems” threads but still cannot solve my problem.
Ubuntu in AWS EC2, fresh Discourse installation, can’t receive confirmation email.
Current configuration:

DISCOURSE_SMTP_ADDRESS: smtp.motomirko.pl
DISCOURSE_SMTP_PORT: 465
DISCOURSE_SMTP_USER_NAME: admin@motomirko.pl
DISCOURSE_SMTP_PASSWORD: secretplainpassword
DISCOURSE_SMTP_ENABLE_START_TLS: true

I can telnet to smtp.motomirko.pl 465 from instance, connection is ok.
I test my mail server with setting outlook client, and there I saw the problem. When connection was set only to TLS than it was refused, when I set to SSL than connection was successful.
I’m not really sure is it helpful.
Dump from logs : Started POST "/finish-installation/register" for 87.206.151.152 at 2017-07-09 14 - Pastebin.com

Please help!
Cheers!

2

Port 465 was, many years ago, SMTP over SSL/TLS – it doesn’t use STARTTLS. I say “was”, because it’s been deprecated for so many years that the IETF has deregistered smtps as a protocol. You should use either port 25 (SMTP) or port 587 (submission) and STARTTLS.

3

Yeah, you’re absolutely right, I moved from my old provier to gmail, and now everything works like a charm! Thanks!

4

Gmail is not recommended as it has limits for outbound mail. Check out MailGun - it is very straight forward to setup.

5

I hope it’s ok to bump instead of creating a new topic. My host only has smtps (465/ssl) available and I can’t seem to get it to work.

  DISCOURSE_SMTP_ADDRESS: mail.myprovider.com
  DISCOURSE_SMTP_PORT: 465  # smtps/ssl
#  DISCOURSE_SMTP_PORT: 587
  DISCOURSE_SMTP_USER_NAME: login@mydomain.com
  DISCOURSE_SMTP_PASSWORD: "PASSWORD"
  DISCOURSE_SMTP_ENABLE_START_TLS: false           # (optional, default true)

These settings work in Thunderbird. Is smtps not supported or am I doing something wrong? Maybe I need to connect to mail.mydomain.com where a valid ssl cert is installed?

6

So my solution was first to switch to Gmail, but when google started making me problems (limits…) than i switched to MailGun like @ljpp suggested (thanks man it’s great!). I think that’s not possible to force discourse to use 465 anymore.

7

Thank you. I’ve signed up for SparkPost as I don’t want to change hosts for my mail. They give you 100 mails per day without verifying your mail, 500 if you do and 10.000 if you add your credit card details. Not too bad.

8

2018년 1월 IETF RFC에서 “implicit” TLS를 위해 포트 465의 사용을 권장하고 있습니다. 그 이유는 필수 암호화(mandatory encryption)가 점점 더 보편화되면서 STARTTLS의 필요성이 상대적으로 줄어들고 있기 때문입니다. RFC 8314 - Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access

9

안녕하세요, discourse SMTP 설정에 문제가 생겼습니다.

AWS EC2에 discourse bitnami 이미지를 설치했고,

해당 문서와 체크리스트를 따라 진행했지만 문제가 해결되지 않습니다. 혹시 아이디어가 있으신가요? 정말 감사합니다!

instruction
https://docs.bitnami.com/bch/apps/discourse/configuration/configure-smtp/

checklists
https://docs.bitnami.com/aws/how-to/use-ses/

10

Bitnami는 공식적으로 지원되지 않으므로, 지원이 필요하시면 Bitnami에 직접 문의해 주세요.

11

네, 알려주셔서 감사합니다.

12

아직도 작동하지 않습니다. 465 포트는 타임아웃이 발생하고, 587, 25, 2525 포트는 이메일이 SSL 또는 TLS로 암호화되어야 한다는 오류가 나요. 다음 공개 메일 서비스들과 가능한 모든 조합을 시도해 보았습니다:

13

동작하나요?

14

마침내 해결했습니다. Yandex 문제는 DISCOURSE_NOTIFICATION_EMAIL이 DISCOURSE_SMTP_USER_NAME과 동일해야 한다는 것이었습니다.