# Email updates without signing up

**URL:** <https://meta.discourse.org/t/email-updates-without-signing-up/27437>\
**Category:** Feature\
**Created:** [10 Abril , 2015 22:37 UTC](https://meta.discourse.org/t/email-updates-without-signing-up/27437 "2015-04-10T22:37:33Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![purldator](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@purldator](https://meta.discourse.org/u/purldator)\
**Post date:** [11 Abril , 2015 11:27 UTC](https://meta.discourse.org/t/email-updates-without-signing-up/27437/10 "2015-04-11T11:27:27Z")

</div>

Have the proposed script check the Discouse database before sending anything. Compare the current visitor email list vs new Discourse users or the entire user database. If there’s an email match, remove the email from the visitor list. Then it can query the database for the relevant posts as usual then tip off MailChimp via their API.

If the script does the above then the second problem won’t happen. A user wouldn’t have their email in two separate systems. They simply remove themselves from the digest via user prefs on Discourse.

Done and done.

EDIT: The ‘mirror check’ can include the last successful newsletter mailing to the current time. It takes the ‘last successful’ time and uses that to query the Discourse user database for emails by checking the registered date. That way there’s no need for the script to read the _entire_ database for emails, but instead pick up relevant new accounts and _then_ search those for duplicate emails (especially if you have enough users to equal a quaint Smalltown, USA).

---

_[View the full topic](https://meta.discourse.org/t/email-updates-without-signing-up/27437)._