Bug 12853 - Discourse: Reply via mail is broken
Summary: Discourse: Reply via mail is broken
Status: NEW
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Mail & Mailing Lists (show other bugs)
Version: unspecified
Hardware: unspecified Unspecified
: - Unknown - Minor Usability
Assignee: Michael Tremer
QA Contact: Peter Müller
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-24 08:45 UTC by Peter Müller
Modified: 2022-04-24 10:16 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Müller 2022-04-24 08:45:33 UTC
Replies apparently do not reach Discourse and/or are not properly being processed by it.
Comment 1 Peter Müller 2022-04-24 09:29:31 UTC
The Postfix Docker container on web06.haj.ipfire.org logs the following:

<23>Apr 24 08:42:17 receive-mail[2746]: Recipient: replies+d16d49b822f0ab1fbc4860010f1a7d78@community.ipfire.org
<19>Apr 24 08:42:17 receive-mail[2746]: Failed to POST the e-mail to https://community.ipfire.org/admin/email/handle_mail: SSL_connect returned=1 errno=0 state=error: certificate verify failed (OpenSSL::SSL::SSLError)
<19>Apr 24 08:42:17 receive-mail[2746]:   /usr/local/lib/ruby/2.3.0/net/http.rb:933:in `connect_nonblock'
  /usr/local/lib/ruby/2.3.0/net/http.rb:933:in `connect'
  /usr/local/lib/ruby/2.3.0/net/http.rb:863:in `do_start'
  /usr/local/lib/ruby/2.3.0/net/http.rb:852:in `start'
  /usr/local/lib/ruby/2.3.0/net/http.rb:1398:in `request'
  /usr/local/bin/lib/discourse_mail_receiver.rb:46:in `process'
  /usr/local/bin/receive-mail:12:in `<main>'
<22>Apr 24 08:42:17 postfix/pipe[2745]: DF36F1009D1: to=<replies+d16d49b822f0ab1fbc4860010f1a7d78@community.ipfire.org>, relay=discourse, delay=0.35, delays=0.17/0.01/0/0.18, dsn=4.3.0, status=deferred (temporary failure)
Comment 2 Michael Tremer 2022-04-24 10:16:43 UTC
This seems to be caused by a bug that has been introduced with the last update that I installed some time this week.

Since this is all Docker-based, I can only try to relaunch this and see if problems are gone.