# Protecting against gmail dot trick in Discourse

**URL:** <https://meta.discourse.org/t/protecting-against-gmail-dot-trick-in-discourse/22627>\
**Category:** Feature\
**Created:** [2014年十一月28日 15:18 UTC](https://meta.discourse.org/t/protecting-against-gmail-dot-trick-in-discourse/22627 "2014-11-28T15:18:38Z")\
**Posts on this page:** 1\
**Showing post:** 88

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2020年四月24日 04:12 UTC](https://meta.discourse.org/t/protecting-against-gmail-dot-trick-in-discourse/22627/88 "2020-04-24T04:12:58Z")

</div>

我已撤销了[我的更改](https://meta.discourse.org/t/gmail-dot-trick/22627/76?u=sam)，并引入了这个全新的出色默认设置。

> <https://github.com/discourse/discourse/commit/cbceadf48b60b29fb710586e2b03bde4c5fe0883>
>
> Previously we relied entirely on levenshtein\_distance\_spammer\_emails site
> settin…g to handle "similar looking" emails.
> 
> This commit improves the situation by always preferring to block (and check)
> canonical emails.
> 
> This means that if:
> 
> \`samevil+test@domain.com\` is blocked the system will block \`samevil@domain.com\`
> 
> This means that \`samevil+2@domain.com\` (ad infinitum) will be blocked

这意味着，如果 `evil.person+77@gmail.com` 被阻止，我们将直接阻止 `evilperson@gmail.com`。

随后，当 `e.v.i.l.person@gmail.com` 试图潜入时，也会因规范化匹配而被阻止。

这完全解决了此处原始发帖人的问题，并且是一项非常简洁且安全的更改，所有 Discourse 实例均可受益。

我将在一周后关闭此议题，标记为已完成。

---

_[View the full topic](https://meta.discourse.org/t/protecting-against-gmail-dot-trick-in-discourse/22627)._