I got this feedback from a member today relating to discourse and attachments:
Tobias, is there a different way to attach docs on discourse? this function only allows me to save the document, not open it…For a couple of Vivek’s e-mails, I’ve saved the document, and then gotten pulled away, ans then never opened it… can there be an “open in another tab” option? Or even a kind of attachment like in google, where the pop up box would have an “open” option?
We use gmail, and I am assuming she’s hoping for something more gmail-like.
The first request here I think is for “mailing list mode” to actually attach the file to the message. I hope this can be added to the roadmap, at least as an admin setting.
The second is more of a “wondering”. Is there not a way to indicate in the mailing that a link is to an attachment, which email clients can then use to offer different ways to access said attachment?
I don’t really see a practical use for the request – if the user can’t figure out how to open a downloaded file, they are going to be in a world of hurt sooner or later… they need to learn how to do that.
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.
Major enhancement of incoming emails. This work effected a whole bunch of email improvements, the vast majority of which you can find listed in our v1.5 changelog.
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.
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 that you commented in. Thank you!
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.
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?
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 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?
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.
Is there some kind of development report? I remember reading a plan when it was announced. Any debrief?
Added:
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.
and many thanks! 
Is there any update? Has the MOSS budget run out?