We’ve just migrated our self-hosted Discourse instance from one server to another. All settings got migrated from the old to the new system, including ‘reply via email’ and ‘allow new posts through email’. We are using the discourse/mail-receiver setup to handle the email part.
Both the reply-to as the new-email functionality worked great in the old system, but we have an issue on the new server: reply-to doesn’t work anymore.
- As an unknown user, when I send an email to the for this purpose configured email address, I can see the mail coming in. A new staged user is being created. The message is being posted. Jay!
- As Team user, I can reply to this message, and the message is being delivered correctly. Great!
- BUT again replying to that email, which should result in a reply in discourse, fails. When the message arrives in mail-receiver, it tries to deliver it through the API, but that fails with the following log errors.
(For privacy reasons, I altered user and domain names)
<22>Sep 13 09:45:15 postfix/qmgr: AF8665CA560: from=<email@example.com>, size=9233, nrcpt=1 (queue active) <23>Sep 13 09:45:15 receive-mail: Recipient: firstname.lastname@example.org <19>Sep 13 09:45:15 receive-mail: Failed to POST the e-mail to https://forum.acme.org/admin/email/handle_mail: 400 <22>Sep 13 09:45:15 postfix/pipe: AF8665CA560: to=<email@example.com>, relay=discourse, delay=1126, delays=1126/0.01/0/0.21, dsn=4.3.0, status=deferred (temporary failure)
As I said, this whole back-and-forth worked perfectly fine in the old setup. The new setup is exactly the same (
local_discourse/mail-receiver) as the old one.
- Could anyone tell me why the handle_mail API would throw a 400 on a reply email?
- Would it be possible to make the logging more verbose, so I can dig deeper?