# Reply by email - additional addresses

**URL:** <https://meta.discourse.org/t/reply-by-email-additional-addresses/125891>\
**Category:** Product Support\
**Created:** [August 15, 2019, 2:46pm UTC](https://meta.discourse.org/t/reply-by-email-additional-addresses/125891 "2019-08-15T14:46:11Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![turkeyphant](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/turkeyphant/32/153147_2.png) [@turkeyphant](https://meta.discourse.org/u/turkeyphant)\
**Post date:** [August 15, 2019, 7:37pm UTC](https://meta.discourse.org/t/reply-by-email-additional-addresses/125891/15 "2019-08-15T19:37:45Z")

</div>

You’re right, it’s far from ideal.

But the solution does make sense (bear with me). First of all, the outgoing email address can be outgoing-only, just as the receiving address is incoming-only. This allows you to reduce unwanted spam as well as identify the source.

As explained, aliasing is not a solution when you still have to manually set each one up. If Gmail or other platforms could intelligently reply from the appropriate plus-address or dot-address the issue would be resolved but that seems unlikely (not to mention dot addressing is non-standard).

Frankly, I have not had the security issue with replying from alternative addresses explained to me. Surely if we trust the recipient with the (sometimes-private) data they receive, we equally trust them to post. Why not include a token with the email notification allowing any email address to reply (as long as the token is valid).

Just thinking things through here - please feel free to pick these points apart…

---

_[View the full topic](https://meta.discourse.org/t/reply-by-email-additional-addresses/125891)._
