Hi all, and apologies if this is similar to some of the other posts that mention this error. For the last four days all emails have stopped getting sent, and the test email also fails. I have browsed through existing topics that are similar, but in my case nothing (that I am aware of) has changed, and email has stopped working after previously working for months without issue. We are using hosting on Digital Ocean, and are using G Suite SMTP relay configured to relay emails from the droplet’s IP address. The exact error listed in Sidekiq is a bit more verbose than what I get from the discourse-doctor. Jobs::HandledExceptionWrapper: Wrapped EOFError: end of file reached discource-doctor merely says: UNEXPECTED ERROR: end of file reached I was also able to confirm connecting to the server with: telnet smtp-relay.gmail.com 587 I believe there was one other short lapse where e-mails stopped sending many months ago, but I can’t remember the error (at that time I was able to retry from sidekiq without any issues). Has anyone experienced anything similar or have a similar configuration that is still functional? Thanks in advance!

Follow [画像] Discourse SMTP sends "EHLO localhost" instead of domain, breaking Google smtp-relay Bug Can you please try adding a new line with DISCOURSE_SMTP_DOMAIN: conversation.sevarg.net and try again? Fill the new env var with your email domain and rebuild.

I’ve had good luck on these forums before helping track down and solve issues. Not sure why this one is so quiet.

It’s possible that it’s an gmail/gsuite smtp issue, but @Syonyk mentioned he was able to manually send an email through telnet on his droplet. I’m not nearly experienced enough to know how g-suite might interpret traffic dispatched from the site compared to manually sent message, but that seems to make it seem like it’s an issue with the service sending the email to smtp-relay.gmail, and not on the relay itself. Fwiw, I also have the droplet’s IP address specifically allowed in the admin gsuite settings, and I had not (and still have not) changed any settings in any of the services for several months. The one time I saw something similar happen it was only a day (maybe two – it wasn’t a very busy page at the time so I probably wouldn’t have noticed if it was longer), but it seemed to have resolved itself pretty quickly.

Without a good trace of the SMTP conversation from Discourse, I don’t know how to troubleshoot any further - and I don’t know how to get those traces.

Is there any way to confirm the number of emails I’m sending out of discourse per month? If I need to go to another smtp-relay I’d need to know what sort of budget I’d need. This is super frustrating.

Under /admin/email/sent on your instance, you should be able to see what’s been sent and estimate usage from there.

Hm… I tossed a tcpdump on the server and ran discourse-doctor. And found this in the output… ... 0x0030: d10f f8e4 4548 4c4f 206c 6f63 616c 686f ....EHLO.localho 0x0040: 7374 0d0a st.. ... 0x0030: de62 f0c3 3432 3120 342e 372e 3020 5472 .b..421.4.7.0.Tr 0x0040: 7920 6167 6169 6e20 6c61 7465 722c 2063 y.again.later,.c 0x0050: 6c6f 7369 6e67 2063 6f6e 6e65 6374 696f losing.connectio 0x0060: 6e2e 2028 4548 4c4f 2920 6a31 3673 6d34 n..(EHLO).j16sm4 0x0070: 3831 3932 3976 736d 2e31 202d 2067 736d 81929vsm.1.-.gsm 0x0080: 7470 0d0a tp.. And, importantly, I CAN reproduce this failure with telnet. root@conversation:~# telnet smtp-relay.gmail.com 587 Trying 74.125.137.28... Connected to smtp-relay.gmail.com. Escape character is '^]'. 220 smtp-relay.gmail.com ESMTP ls8sm507258pjb.6 - gsmtp ehlo localhost.localdomain 421 4.7.0 Try again later, closing connection. (EHLO) ls8sm507258pjb.6 - gsmtp Connection closed by foreign host. If I send an actual domain, I get the expected response. root@conversation:~# telnet smtp-relay.gmail.com 587 Trying 74.125.137.28... Connected to smtp-relay.gmail.com. Escape character is '^]'. 220 smtp-relay.gmail.com ESMTP p10sm668563uaw.3 - gsmtp ehlo conversation.sevarg.net 250-smtp-relay.gmail.com at your service, [64.227.96.27] 250-SIZE 157286400 250-8BITMIME 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-CHUNKING 250 SMTPUTF8 So, now the question is, how does one get Discourse to send a proper domain string in the ehlo? I don’t know if it’s the only issue, but it sure looks promising to run down.

This is so strange. Where would this have suddenly crept in? I haven’t done any updates.

It hasn’t crept in, it’s been like this. Google changed something. discourse-doctor calls the test in /var/www/discourse/lib/tasks/emails.rake - if you’re in the image. I changed: Net::SMTP.start(smtp[:address], smtp[:port], 'localhost', smtp[:user_name], smtp[:password], smtp[:authentication]) to Net::SMTP.start(smtp[:address], smtp[:port], 'conversation.sevarg.net', smtp[:user_name], smtp[:password], smtp[:authentication]) Now I get a different error. ======================================== ERROR ======================================== UNEXPECTED ERROR 503 5.5.1 bad sequence of commands e190sm562849qkd.9 - gsmtp ====================================== SOLUTION ======================================= This is not a common error. No recommended solution exists! Please report the exact error message above to https://meta.discourse.org/ (And a solution, if you find one!) ======================================================================================= BUT: importantly, the tcpdump shows something resembling a sane(ish) flow. 22:33:48.393862 IP 64.227.96.27.54610 > 74.125.137.28.587: Flags [P.], seq 1:31, ack 59, win 502, options [nop,nop,TS val 3732187266 ecr 3508646052], length 30 0x0000: 4500 0052 d4d6 4000 3f06 f237 40e3 601b E..R..@.?..7@.`. 0x0010: 4a7d 891c d552 024b 01b4 04a4 94ce dcc7 J}...R.K........ 0x0020: 8018 01f6 74dc 0000 0101 080a de74 a882 ....t........t.. 0x0030: d121 b0a4 4548 4c4f 2063 6f6e 7665 7273 .!..EHLO.convers 0x0040: 6174 696f 6e2e 7365 7661 7267 2e6e 6574 ation.sevarg.net 0x0050: 0d0a .. 22:33:48.408832 IP 74.125.137.28.587 > 64.227.96.27.54610: Flags [.], ack 31, win 256, options [nop,nop,TS val 3508646067 ecr 3732187266], length 0 0x0000: 4500 0034 5e5d 0000 2b06 bccf 4a7d 891c E..4^]..+...J}.. 0x0010: 40e3 601b 024b d552 94ce dcc7 01b4 04c2 @.`..K.R........ 0x0020: 8010 0100 a8ae 0000 0101 080a d121 b0b3 .............!.. 0x0030: de74 a882 .t.. 22:33:48.469560 IP 74.125.137.28.587 > 64.227.96.27.54610: Flags [P.], seq 59:234, ack 31, win 256, options [nop,nop,TS val 3508646128 ecr 3732187266], length 175 0x0000: 4500 00e3 5e8a 0000 2b06 bbf3 4a7d 891c E...^...+...J}.. 0x0010: 40e3 601b 024b d552 94ce dcc7 01b4 04c2 @.`..K.R........ 0x0020: 8018 0100 929f 0000 0101 080a d121 b0f0 .............!.. 0x0030: de74 a882 3235 302d 736d 7470 2d72 656c .t..250-smtp-rel 0x0040: 6179 2e67 6d61 696c 2e63 6f6d 2061 7420 ay.gmail.com.at. 0x0050: 796f 7572 2073 6572 7669 6365 2c20 5b36 your.service,.[6 0x0060: 342e 3232 372e 3936 2e32 375d 0d0a 3235 4.227.96.27]..25 0x0070: 302d 5349 5a45 2031 3537 3238 3634 3030 0-SIZE.157286400 0x0080: 0d0a 3235 302d 3842 4954 4d49 4d45 0d0a ..250-8BITMIME.. 0x0090: 3235 302d 5354 4152 5454 4c53 0d0a 3235 250-STARTTLS..25 0x00a0: 302d 454e 4841 4e43 4544 5354 4154 5553 0-ENHANCEDSTATUS 0x00b0: 434f 4445 530d 0a32 3530 2d50 4950 454c CODES..250-PIPEL 0x00c0: 494e 494e 470d 0a32 3530 2d43 4855 4e4b INING..250-CHUNK 0x00d0: 494e 470d 0a32 3530 2053 4d54 5055 5446 ING..250.SMTPUTF 0x00e0: 380d 0a 8.. So, at a minimum, sending the “EHLO localhost” or “EHLO localhost.localdomain” is part of the problem. Now, how on earth does one go reporting a P0 issue to actual developers?

I’ve definitely seen these guys on the forums. They monitor them fairly closely from what I can tell. I’d say github but issues seem to be disabled for the repo.

Ok. This is a test email from https://conversation.sevarg.net Email deliverability is complicated. Here are a few important things you should check first: I’ve just demonstrated a fix, but I do not know how to upstream this. cd /var/discourse ./launcher enter app vim ./vendor/bundle/ruby/2.7.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb You need to find the following section: DEFAULTS = { :address => 'localhost', :port => 25, :domain => 'localhost.localdomain', :user_name => nil, :password => nil, :authentication => nil, :enable_starttls => nil, :enable_starttls_auto => true, :openssl_verify_mode => nil, :ssl => nil, :tls => nil, :open_timeout => nil, :read_timeout => nil } Change the domain lines. DEFAULTS = { :address => 'conversation.sevarg.net', :port => 25, :domain => 'conversation.sevarg.net', :user_name => nil, :password => nil, :authentication => nil, :enable_starttls => nil, :enable_starttls_auto => true, :openssl_verify_mode => nil, :ssl => nil, :tls => nil, :open_timeout => nil, :read_timeout => nil } I don’t know which one matters, but changing both solved the issue. Obviously use your domain… Exit out of the app environment. ./launcher restart app It should now be able to send emails. I expect this will not survive any upgrades. However, I am now sending and receiving emails as expected. Devs? Plz2fix?

メールの送信が停止しました - ファイルの終端に到達しました

製品サポート

Falco (Falco) 2021 年 1 月 26 日午後 10:02 25

フォロー

新しい環境変数にメールドメインを入力して、再構築してください。

What does DISCOURSE_SMTP_DOMAIN mean?

トピック		返信	表示
Gsuite smtp-relay issue "end of file reached" Product Support	5	1036	2021 年 1 月 20 日
Discourse SMTP sends "EHLO localhost" instead of domain, breaking Google smtp-relay Bug	25	5898	2021 年 2 月 23 日
Mail does not go out after recent update Product Support email	21	1004	2026 年 3 月 13 日
Mail test failure in discourse-doctor Product Support email	17	734	2025 年 3 月 13 日
Discourse with other websites, SMTP issue: End of file reached Self-hosting	7	2606	2020 年 9 月 22 日

メールの送信が停止しました - ファイルの終端に到達しました

関連トピック