# Reducing backscatter in email interface? **URL:** \ **Category:** Feature\ **Created:** [March 27, 2017, 3:36pm UTC](https://meta.discourse.org/t/reducing-backscatter-in-email-interface/59974 "2017-03-27T15:36:31Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\ **Post date:** [April 7, 2017, 3:45am UTC](https://meta.discourse.org/t/reducing-backscatter-in-email-interface/59974/8 "2017-04-07T03:45:25Z")
This looks pretty slick, nice work. There is mention of testing.. I’ve got a new discourse instance that’s up and running now, but not scheduled to be in production for a week or so. I can offer it for real-world testing (and can grant access as needed). As for the setup of this, looking at the new [variable in the mail-receiver](https://github.com/discourse/discourse_docker/pull/344/files#diff-628d12187a7feac3ca1ebb55e0ff3765R33), I wonder: If `DISCOURSE_SMTP_SHOULD_REJECT_ENDPOINT` is going to be optional, should that be commented out by default? If it should be on by default, maybe there should be just one variable to set, like `DISCOURSE_ADMIN_URL` I’m suggesting admin URL as it would have to take in to account any subfolder. Using this, the paths to `/email/handle_mail` and `email/smtp_should_reject.json` could be implied by the [mail-receiver](https://github.com/discourse/mail-receiver) itself. --- _[View the full topic](https://meta.discourse.org/t/reducing-backscatter-in-email-interface/59974)._