Mail-receiver sending reply-to address as from address?

AI-generated summary

Mail-receiver sending reply-to address as from address? discussion is about an issue where the reply-to address is being used as the from address when sending emails using Netcore. Jacob_Peebles and Abdelrahman_MoHamed are experiencing this issue, and Netcore’s response is that this configuration is not controlled by them, but rather by Discourse. According to Netcore, when Discourse establishes an SMTP connection, it sends the reply address in the From field, which is a configuration used when connecting to other platforms as well.

Abdelrahman_MoHamed shared their SMTP configuration, showing that the sending domain is message.mamapedia.com and the reply-to domain is reply.mamapedia.com. However, Netcore rejected the sender address, stating that it is not owned by the user.

kelv suggested that this is the expected behavior due to how VERP handling works in Discourse, and recommended adding reply.mamapedia.com as a recognized domain in Netcore to resolve the issue.

We have been struggling with getting our emails to send correctly using netcore (formerly pepipost). To summarize the emails we are generating with their service places the reply-to address in the from address.

When bringing this to their attention this is the response we get. If anyone can confirm the accuracy of this statement we would appreciate it.

—————
We’ve conducted multiple rounds of testing, and here are the observations:

Problem Statement
When Discourse establishes an SMTP connection with an external ESP (e.g., Netcore, Mailgun, or others), it sends the reply address (e.g., reply+reply_id@reply.mamapedia.com) in the From field of the email during injection.
This configuration is not controlled by Netcore, as shown in the logs we shared earlier. Notably, Discourse uses this same configuration when connecting to other platforms.

Findings

  1. Domain Validation by Netcore:
  • Netcore validates whether the From domain is active in your Netcore portal.
  1. Testing With Non-Existing Domains:
  • We tested sending emails using non-existing domains like messages1.mamapedia.com and messagestest.test.com through Mailgun. These emails were delivered even though the domains were not added to the Mailgun account. The test emails are attached for reference. This can be a serious security issue.
  • In contrast, Netcore includes an added layer of security to prevent fraud. If an inactive domain (not validated in your Netcore account) sends a request, the request is rejected.

This added security helps prevent scenarios where a malicious actor could use your SMTP credentials to send emails from unauthorized domains (e.g., apple.com, [gmail.com]
(http://gmail.com/) or anything else).

Hello, I’m working with @Jacob_Peebles on this issue, and here is our SMTP configuration

Our sending domain from Netcore is

message.mamapedia.com

and we have configured the mail receiver to enable the reply by email feature with this domain

reply.mamapedia.com

But unfortunately, we got this from Netcore

553 5.7.1 replies+verp-43fdbee91575167a6b7634f2bc5d2e52@reply.mamapedia.com: Sender address rejected: not owned by user

And according to the attached screenshot for our configuration, the sending or notification email is “message.mamapedia.com” and reply-to is “reply.mamapedia.com”

I believe this is the expected behaviour due to how VERP handling works in Discourse (see discourse/lib/email/sender.rb at f44ec18fd23960a22a5d5d397959430d6b84cb1c · discourse/discourse · GitHub) - we set the unique bounce address in the return path header.

I don’t have a full historical account of how this behaviour came to be, though the commented code indicates it’s to account for Rails behaviour.

Suggestion: I’m not too familiar with Netcore, would you be able to add reply.mamapedia.com as a recognised domain there?