The discussion revolves around an issue where incoming emails with a reply-to header are not honored when replying via Discourse. evantill reports that replies are sent to the from address instead of the reply-to address, which is problematic for their use case of integrating a WordPress contact form with Discourse. simon suggests the behavior is expected due to security concerns, as using reply-to could enable impersonation. Stephen reinforces this, explaining that allowing reply-to could compromise security. simon proposes alternatives, such as using a mailto link or integrating the Discourse API for authenticated users.
When a user reply in discourse to a message coming from an email with a reply-to header, it seems that the outgoing email is sent to the from email address and not the one in reply-to header.
Is it expected to work like this ?
Note: We have a Wordpress web site using a contact form. We would like to receive the message into discourse and be able to reply directly within discourse.
I think that is expected. Have you added a form to your website that users can add their email address to? If I’m understanding what you are trying to do, it would be risky to assume that users are entering the correct email address into the form.
I realize that it would be less straightforward from the user’s point of view, but you could use a mailto link on your website to open the user’s default mail program. That way the email would be sent from the user’s email address.
If users are able to login to your website and you have some way of associating your website’s users with Discourse users (for example, checking that the emails match), you could add a form to your website that would allow logged in users to post to Discourse via the Discourse API.