No staff action triggered this. So my guess is some kind of glitch must have disabled the mailinglist globally across the forum. About 20h worth of emails were probably lost.
All mailing list functionality has been re-established and hopefully new emails will start arriving soon in your inboxes. All affected users should have received a message communicating this issue.
I’m getting forum emails again. Despite getting the emails the “Enable mailing list mode” wasn’t checked. However I enabled anyway, so everything is back to normal. Thanks.
Turns out this was a deliberate decision by the discourse team. I got the following response:
Discourse now sets the value of the disable mailing list mode setting to true by default. If users on your site were using mailing list mode, setting disable mailing list mode back to false will cause mailing list emails to be sent to them again.
So basically in all discourse instances across the world, the mailinglist feature got deactivated . No communication whatsoever to admins about this.
This was the reasoning behind their choice:
This decision was not take lightly. It was based on extreme real world problems we saw where email costs for self hosters and other discourse installations went sky high.
We opted for a safer default, to keep costs down for people.
I am not pleased with their choice at all, especially for the lack of communication. I mean, I can’t complain much because they’re hosting us for free, and do provide a great service. But if this sort unilateral-with-no-warning of stuff happens more frequently, I will not be happy at all.
Thanks for figuring that out. I understand there reasoning, but they should have communicated that first, and even better they could/should implement “Mailing List mode” as option (opt-in or opt-out) for administrators. The forum operator should be the one who decides.
I believe the software will edit out duplicate from the message you
reply to.
You can use MD,BBCode, and some HTML to format messages. If, eg you
wanted a specific quote you can use BBCode tags to enclose. I
have macros to do this. (I generally have no idea how my posts look on
the Forum except for helpful advice from other users.)
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I am seeing that forum software has edited out the reply quotation part from your reply. So, there’s no way to quote some portions of the previous messages in your replies via email?
My reply to you used both standard > and block quote markers - both
should have rendered as quotes.
[… 14 lines elided]
OK, let me see how this reply from my email client looks like. I am
quoting your message above my reply (ie, “bottom-reply-posting”). I am
also using simple > for quoting your message.
OK, let me see how this reply from my email client looks like. I am
quoting your message above my reply (ie, “bottom-reply-posting”). I am
also using simple > for quoting your message.
I’m guessing it looks like that on the Forum. It looks fine by email.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
Understood, no worries. Well, it is working for me as well, I guess. I
like this so far, let me see how following the whole forum via email
goes for a few weeks.
Understood, no worries. Well, it is working for me as well, I guess. I
like this so far, let me see how following the whole forum via email
goes for a few weeks.
Sometimes Discourse processes stuff within block quotes in strange
ways.
Also, you will not see edits or updates to posts, though they will be
evident in later posts. (This renders guides and wiki entries almost
useless.)
Most users dont provide alt text to images - if you are a text mode user
this is frustrating.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I have rolled out variations on offlineimap/mutt/edbrowse/thunderbird.
If you retain a MUA in the sending disposable, then SMTP support is
usually baked in.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.