# Catch-All Issue for Reply in Email
**URL:** https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909
**Category:** Support
**Created:** [March 12, 2017, 12:51am UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909 "2017-03-12T00:51:07Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@jylinman](https://meta.discourse.org/u/jylinman)
#### Post date: [March 12, 2017, 12:51am UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909/1 "2017-03-12T00:51:07Z")
So I am currently setting everything up on AWS for discourse, and because I need to comply with certain laws I need to have the email hosted on it as well using WorkMail. Now, as of right now workmail doesn’t have a catch all address and can’t let me create a rule to redirect / forward an email when it was sent to an address that doesn’t exist.
There are some hacky solutions I could do in terms of publishing something to SES and posting with discourse API, but I was wondering if someone has any thoughts on how to fix this so users can reply / start topics by email?
Another solution, is there a way to setup discourse to send it to an email address (like [replies@site.com](mailto:replies@site.com)) and CC it to the actual email needed for the topic (like [site+jfNEKSKJFwlkvjdlsjkl@site.com](mailto:site+jfNEKSKJFwlkvjdlsjkl@site.com))?
Thanks,
Jon
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 12, 2017, 1:31am UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909/2 "2017-03-12T01:31:12Z")
You can add addresses to categories and groups such that sending there posts. Is that what you need or did I miss something about yourv complications?
---
### Author:  [@jylinman](https://meta.discourse.org/u/jylinman)
#### Post date: [March 12, 2017, 2:22am UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909/3 "2017-03-12T02:22:37Z")
Yes, I am aware of the categories setting to specify an email, but what about a specific topic? If a user wants to reply to a topic they are replying to an email that looks like `sitename-VEJInlkjlkdjslkfjdlksjkw@site.com` (because its specific to the topic as far as I understand). So this is generated per topic and obviously thats too many aliases to add.
I’m trying to have the SES send the email, and when they reply to it the MX server at amazon receives it and redirects it to the general replies@ email with the full email address of `sitename-VEJInlkjlkdjslkfjdlksjkw@site.com`.
Did you have some thoughts on this @pfaffman?
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [March 12, 2017, 12:01pm UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909/4 "2017-03-12T12:01:10Z")
> [@jylinman](#):
>
> There are some hacky solutions I could do in terms of publishing something to SES and posting with discourse API
We use this solution for our customers and it works 👍
The advantage of this solution is that you don’t have to wait for the “_email polling_” period. You get the incoming email as soon as it is received 😉
---
### Author:  [@jylinman](https://meta.discourse.org/u/jylinman)
#### Post date: [March 12, 2017, 2:45pm UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909/5 "2017-03-12T14:45:37Z")
Hey @zogstrip well thats good to hear! Would you be able to share what you’ve found as the best implementation? Were you able to subscribe directly to SNS topic or did you setup some sort of Lambda function?
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [March 12, 2017, 2:46pm UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909/6 "2017-03-12T14:46:50Z")
I didn’t mean the SES part but the “use the API” part. I have no idea what’s best between using SES or Lambda.
---
### Author:  [@jylinman](https://meta.discourse.org/u/jylinman)
#### Post date: [March 12, 2017, 3:05pm UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909/7 "2017-03-12T15:05:01Z")
After some investigation I actually found this tool that can forward SES to SNS and then to Lambda then you can just forward it to your general email for inbound email where Discourse will poll for new emails.
[https://github.com/arithmetric/aws-lambda-ses-forwarder](https://github.com/arithmetric/aws-lambda-ses-forwarder)
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [October 31, 2023, 7:52pm UTC](https://meta.discourse.org/t/catch-all-issue-for-reply-in-email/58909/9 "2023-10-31T19:52:03Z")