The discussion revolves around the creation of a %{reply_key} in Discourse. esepjav is having trouble with email replies being rejected by Discourse, receiving an error message from their server.
pfaffman suggests checking if the server is configured to receive email. esepjav shares their email settings, and pfaffman advises against using an alternative reply-to address.
pfaffman explains that the endpoint is only accessible via POST, and notes that esepjav’s MX records do not resolve to their Discourse server, which is likely causing the error.
Hi,
How %{reply_key} is created by discourse, for my case when outlook send reply to topic to discourse, it is getting reject by discourse. outlook report shows it sent successfully.
Server at (IP address) returned ‘400 4.4.7 Message delayed’
7/31/2018 8:39:53 PM - Server at (IP address) returned ‘451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect -> SocketConnectionRefused: Socket error code 10061’
That’s not a URL that you get get. It’s only for POST.
And if you did Straight-forward incoming mail, you don’t have a POP3 host. And the MX for discourse-staging.lmera.ericsson.se doesn’t resolve to your Discourse server, so the error message you’re getting on mail delivery isn’t from your Discourse server.
With that many problems, I don’t think that you’ll be able to get it sorted out here.
If you have a budget, my contact information is in my profile.