# MOSS Roadmap - Mailing lists
**URL:** https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432
**Category:** Feature
**Created:** [12월 8, 2015, 5:37오후 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432 "2015-12-08T17:37:27Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [2월 12, 2016, 9:23오후 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/23 "2016-02-12T21:23:32Z")
I think she’s just hoping the functionality can be made more equivalent to what she’s used to. That would happen if the file were actually attached to the message and not provided as a link. She really is a candidate for mailing list mode in a big way - she does not log into our discourse at all and, even now after a year, misses the google groups we replaced.
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [4월 6, 2016, 10:56오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/24 "2016-04-06T10:56:15Z")
### Update - 6. April, 2016
- Major enhancement of [incoming emails](https://meta.discourse.org/t/setup-incoming-emails-e-mail/42026). This work effected a whole _bunch_ of email improvements, the vast majority of which you can find listed in our [v1.5 changelog](https://meta.discourse.org/t/discourse-version-1-5/30609/3).
- Attachments support
- Email notifications in user’s language. [gh#4004](https://github.com/discourse/discourse/pull/4004)
- Layout improvements [gh#3969](https://github.com/discourse/discourse/pull/3969), [gh#4008](https://github.com/discourse/discourse/pull/4008)
- Unsubscribe by email [gh#3952](https://github.com/discourse/discourse/pull/3952)
- [Better email context](https://meta.discourse.org/t/forcing-email-context-input-requested/25577/67).
Major shoutout to @simon, @gdpelican and @joebuhlig for stepping up to the email plate and taking on a portion. @zogstrip please let me know if I missed anything major.
Will post another update in a couple of months!
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [4월 6, 2016, 1:55오후 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/25 "2016-04-06T13:55:59Z")
amazing. congrats 🎉 and many thanks! 😻
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [4월 6, 2016, 3:21오후 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/26 "2016-04-06T15:21:45Z")
> [@erlend\_sh](#):
>
> 💭 Threaded replies by e-mailhttps://discourse.chef.io/t/thread-detection-when-responding-via-email/7329
I _think_ I fixed that one. Not sure though, will have to confirm this.
---
### Author:  [@tarek](https://meta.discourse.org/u/tarek)
#### Post date: [5월 31, 2016, 11:06오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/27 "2016-05-31T11:06:54Z")
Hello @erlend_sh. I wonder if you would consider adding the feature to allow replying only to sender to within this work? Before I found this thread, I described the problem [in another topic](https://meta.discourse.org/t/allow-reply-to-individual-instead-of-topic-forum-mailing-list-feature/44905) that you commented in. Thank you!
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [5월 31, 2016, 11:14오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/28 "2016-05-31T11:14:26Z")
If that topic culminates in (1) a clear specification that (2) multiple users clearly want, then it’s a great candidate for MOSS work, yes.
---
### Author:  [@tarek](https://meta.discourse.org/u/tarek)
#### Post date: [5월 31, 2016, 11:15오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/29 "2016-05-31T11:15:52Z")
Could you point to an example of a clear specification so that I could generate one?
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [5월 31, 2016, 11:23오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/30 "2016-05-31T11:23:48Z")
Sure, you can peruse our many #feature:spec topics to get an idea of what we’re looking for in a spec. But there’s no point spending too much time putting together a spec until you’ve reached a semblance of a consensus in the topic where this feature request is currently being discussed.
---
### Author:  [@tarek](https://meta.discourse.org/u/tarek)
#### Post date: [5월 31, 2016, 11:39오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/31 "2016-05-31T11:39:27Z")
Understood. Because of the utility of the feature for me (essentially, it’s a must-have for our group), it seems prudent to develop a spec for me to work from, no? That way, people with strong programming skills / experience might be able to comment / stop me from making errors before I make them / contribute code?
---
### Author:  [@scombs](https://meta.discourse.org/u/scombs)
#### Post date: [5월 31, 2016, 5:24오후 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/32 "2016-05-31T17:24:52Z")
I agree let’s get
> [@erlend\_sh](#):
>
> semblance of a consensus in the topic where this feature request is currently being discussed.
I have some input on the reply-to-sender feature and a request from my customer. I will post back on the [other topic](https://meta.discourse.org/t/allow-reply-to-individual-instead-of-topic-forum-mailing-list-feature/44905) shortly.
---
### Author:  [@peircej](https://meta.discourse.org/u/peircej)
#### Post date: [7월 31, 2016, 2:17오후 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/33 "2016-07-31T14:17:58Z")
As well as migrating existing posts I’m keen to forward posts (for a period) that will continue to arrive at our old mailing list (a googlegroup). @erlend_sh suggested [back in 2013](https://meta.discourse.org/t/import-from-google-groups-to-discourse/7307/4) that this could be achieved by simply subscribing a Discourse email recipient to the mailing list.
The problem is that the mail gets rejected by discourse on the basis that it’s from a list :-/
Is there a way to whitelist particular mailing lists so we can make this work?
---
### Author:  [@modius](https://meta.discourse.org/u/modius)
#### Post date: [9월 22, 2016, 7:46오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/34 "2016-09-22T07:46:11Z")
> [@erlend\_sh](#):
>
> 🔨 Read-only web archive of active mailing list.
> [MOSS Roadmap - Mailing lists - #9 by sam](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/9)
Been holding out for Web Archive for a long time 😉 Is there any update? Has the MOSS budget run out?
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [9월 22, 2016, 8:35오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/35 "2016-09-22T08:35:51Z")
I’m working on a proof of concept for this… might take some time though…
---
### Author:  [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [9월 22, 2016, 9:40오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/36 "2016-09-22T09:40:30Z")
> [@modius](#):
>
> Has the MOSS budget run out?
It has, but of course we still care about email 😁
Post-MOSS we’ve continued to approach developers from our community with bite-sized paid projects. The web archive is one such project, which we’ve enlisted @gerhard to work on. But like he said, it’ll certainly take some time as we’ve definitely pushed the limits of our usual “bite-sized” requirement here.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [9월 22, 2016, 2:51오후 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/37 "2016-09-22T14:51:24Z")
I’ve made some improvements to the mbox importer. I could imagine some cron job solution that used that importer as a stop gap.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [9월 30, 2016, 9:20오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/38 "2016-09-30T09:20:20Z")
> [@erlend\_sh](#):
>
> Post-MOSS
Is there some kind of development report? I remember reading a plan when it was announced. Any debrief?
Added:
> [@erlend\_sh](#):
>
> A user should be able to join, participate and leave group discussions run through Discourse without ever having to log in to the Discourse web interface.
How far are you from this? I have Web-angry users that complain the mailing-list mode sends HTML email (and I didn’t try subscription by email). That suggests me we’re not there yet, but I’d be very happy if we were.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [9월 30, 2016, 10:40오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/39 "2016-09-30T10:40:41Z")
Not true; it is always multi part email where the text part is raw Markdown. If you don’t want the HTML bit then don’t use that and look at the plain text payload.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [9월 30, 2016, 11:07오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/40 "2016-09-30T11:07:12Z")
Maybe that’s an issue with their MUA. I don’t have this problem. I will ask for more precision.
---
### Author:  [@coderanger](https://meta.discourse.org/u/coderanger)
#### Post date: [9월 30, 2016, 11:25오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/41 "2016-09-30T11:25:03Z")
Most mail clients will default to showing HTML content if present. I’m not sure Mail.app actually has a way to force it to show the text content by default. That said most of those clients also stopped loading remote content by default and it would be hard to imagine a case where a security issue would be a real concern. But as Discourse rolls into more “traditional” (read: with expectations of traditional mailing list features) environments, you’re going to get more and more pushback on not having this as a user preference. I’ve certainly had a fair bit of flak from Chef folks about it.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [9월 30, 2016, 11:43오전 UTC](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432/42 "2016-09-30T11:43:58Z")
Here’s what [RFC 2046](https://tools.ietf.org/html/rfc2046#section-5.1.4) has to say (emphasis mine):
> Systems should recognize that the content of the various parts are interchangeable. **Systems should choose the “best” type based on the local environment and references** , in some cases even through user interaction. As with “multipart/mixed”, the order of body parts is significant. In this case, **the alternatives appear in an order of increasing faithfulness to the original content**. In general, **the best choice is the LAST part** of a type supported by the recipient system’s local environment.
From that reading, the Discourse emails are properly formatted, and the problem comes with mis-configuration on the user’s side. **BUT** according to mailing list _tradition_, HTML and email do not mix well, and **plain text is always preferred**. Maybe there could be a switch in the admin section for the order of parts?
[이전 페이지](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432.md?page=1)
[다음 페이지](https://meta.discourse.org/t/moss-roadmap-mailing-lists/36432.md?page=3)