# Issue configuring reply by email: 553 5.7.1 Sender address rejected: not owned by user

**URL:** https://meta.discourse.org/t/issue-configuring-reply-by-email-553-5-7-1-sender-address-rejected-not-owned-by-user/119897
**Category:** Support
**Created:** [10.Июнь.2019 09:21:45 UTC](https://meta.discourse.org/t/issue-configuring-reply-by-email-553-5-7-1-sender-address-rejected-not-owned-by-user/119897 "2019-06-10T09:21:45Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![degrees380](https://avatars.discourse-cdn.com/v4/letter/d/22d042/32.png) [@degrees380](https://meta.discourse.org/u/degrees380)
#### Post date: [10.Июнь.2019 13:27:45 UTC](https://meta.discourse.org/t/issue-configuring-reply-by-email-553-5-7-1-sender-address-rejected-not-owned-by-user/119897/3 "2019-06-10T13:27:45Z")

</div>

Hello Jay,

thank you for your quick reply,

Jay Pfaffman via Discourse Meta [meta@discoursemail.com](mailto:meta@discoursemail.com) writes:

> Your mail server doesn’t like the address. You need to figure out how  
> to allow the user that is sending mail be allowed to use that  
> address. It may be that it doesn’t like the + addressing? But I  
> suspect it’s that it’s denying forumreply.

Thanks to your reply I can now have a look to the relevant email headers  
`meta.discourse.org` used in notification email sent to me:

```plaintext
Return-Path: <meta+verp-7f805e7e715078262ca96f39e643111c@discoursemail.com>
Message-ID: <topic/119897/590490@meta.discourse.org>
In-Reply-To: <topic/119897@meta.discourse.org>
References: <topic/119897@meta.discourse.org>
 5.7.1 Sender address rejected: not owned by user

```

So it’s clear that the `meta.discourse.org` instance is using **the same**  
email address both for the `notification email` and the `reply by email address` template: am I misreading the headers?

In other words it seems to me that `meta.discourse.org` is using

```plaintext
reply by email address: meta+%{reply_key}@discoursemail.com

```

This means that the `Return-Path` is the same of `From`: this is why any  
authendicated SMTP server will never complain about this.

In our instance, instead, we **cannot use**

```plaintext
reply by email address: forum+%{reply_key}@HIDDEN

```

since  
[Notification email cannot be the same as reply by email](https://meta.discourse.org/t/notification-email-cannot-be-the-same-as-reply-by-email/28840);  
in fact I get a validation error if I try:

```plaintext
reply_by_email_address: Value must contain '%%{reply_key}' and be different from the notification email.

```

(why the double %%?)

If I use

```plaintext
forum+%%{reply_key}@HIDDEN

```

(note double %%) our Discourse instance is able to send the email via  
our SMTP server, **but** the headers are different from the ones I  
observe from `meta.discourse.org`

```plaintext
Return-Path: <forum+%verp-9b32231ead642e0cb2cb33563aaf413b@HIDDEN>

```

Please ho can I set our instance to have the same behaviour as  
`meta.discourse.org` regarding `reply by email` delivery?

To be clear, I need to understand how to configure things in order to  
have this set of email headers:

```plaintext
Return-Path: <forum+verp-7f805e7e715078262ca96f39e643111c@HIDDEN>

```

the same way `meta.discourse.org` instance is able to generate?

Thanks for your support.  
degrees380

---

_[View the full topic](https://meta.discourse.org/t/issue-configuring-reply-by-email-553-5-7-1-sender-address-rejected-not-owned-by-user/119897)._
