# 邮件列表模式下的电子邮件地址簿陷阱

**URL:** <https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838>\
**Category:** Support\
**Created:** [2018年十二月9日 15:47 UTC](https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838 "2018-12-09T15:47:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Campbell](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@Matt\_Campbell](https://meta.discourse.org/u/Matt_Campbell)\
**Post date:** [2018年十二月9日 15:47 UTC](https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838/1 "2018-12-09T15:47:13Z")

</div>

Steps to reproduce:

1. Use a forum in mailing list mode.
2. Receive a forum message from someone you want to stay in contact with.
3. Add the sender to your address book, because you think this works like an old-school mailing list.
4. Send a private message to that entry in your address book.

Oops. Your private message went to the whole community.

I’ve witnessed this in a community that uses a competing forum application (I won’t name and shame here), but it affects Discourse as well.

When sending to the address in the From header, the message should either bounce, or go to the sender as a PM. Maybe the forum administrator should be able to choose the behavior.

---

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [2018年十二月9日 16:46 UTC](https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838/2 "2018-12-09T16:46:41Z")

</div>

> [@Matt\_Campbell](#):
>
> because you think this works like an old-school mailing list.

They did work like this? News to me.

One Yahoo mailing list (I replaced with Discourse) would send from `the-group@yahoogroups.co.uk` so if you saved this address and attempted to send a mail to it, it would have done exactly the same thing?

> [@Matt\_Campbell](#):
>
> When sending to the address in the From header, the message should either bounce, or go to the sender as a PM. Maybe the forum administrator should be able to choose the behavior.

I believe you can and _should_ already set this up and is determined by the person who manages the domain and the email service account - usually the admin.

On one of my sites I occasionally get even fairly tech savvy users replying to the [noreply@blah.com](mailto:noreply@blah.com) notifications because the email ‘from’ name uses someone’s account name which confuses them.

However, if your admin has set up reply-by-email, that will work as described - it will reply to the topic!

I don’t think this is a bug, isn’t this simply a misunderstanding and misuse of the functionality and risk of enabling this feature?

---

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [2018年十二月9日 17:33 UTC](https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838/3 "2018-12-09T17:33:22Z")

</div>

> [@merefield](#):
>
> They did work like this? News to me.

Twenty years ago this was all the rage, and precisely why Google and Yahoo moved away from the model with their Groups products.

Discourse has a mailing list mode which emulates some of the features seen on products such as ListServ, but it’s **not** ListServ. Anyone looking to substitute an old mailing list needs to understand the differences beforehand and educate their users, otherwise this kind of problem is inevitable. It’s not a bug, just a consequence of trying to use one product as if it were a carbon-copy for another.

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [2018年十二月9日 21:10 UTC](https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838/4 "2018-12-09T21:10:41Z")

</div>

The big difference, and how to explain it to your users, is that Discourse does not ever give out anyone’s email address. For those trained On listserv in the 1990s, it’s a difficult transition.

---

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [2018年十二月10日 06:37 UTC](https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838/5 "2018-12-10T06:37:58Z")

</div>

You wouldn’t believe it Jay, but the the guy who used to do this most is one of the youngest on the group and an experienced web developer!

---

<div class="post-metadata">

**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\
**Post date:** [2019年一月4日 16:57 UTC](https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838/6 "2019-01-04T16:57:22Z")

</div>

We changed the format of the `From` header which should make it more obvious that the email was sent by Discourse instead of the user.

> [@Change Send As in Email Notifications](https://meta.discourse.org/t/change-send-as-in-email-notifications/31881/27):
>
> This changes the From header of emails from “Jane Doe” to “Jane Doe via \<site\_name\>”. For Meta it will look like “Jane Doe via Discourse Meta”. It uses the value of the email site title site setting or, if it isn’t set, the title setting as \<site\_name\>. The format of the From header can be customized with the email\_from site text.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [2021年十二月9日 01:29 UTC](https://meta.discourse.org/t/the-mailing-list-mode-email-address-book-trap/103838/7 "2021-12-09T01:29:17Z")

</div>


