Community blog messages are e-mailed in raw HTML

I know this has come up before, but it deserves its own topic for tracking and awareness purposes.

Some automatically created topics in Discourse result in e-mail notifications containing raw HTML. I was looking forward to going through the election interviews from the comfort of my inbox, but no luck:

<small>Originally published at:
		</small><br><p><em>This is a part of the Elections Interviews series for Fedora Linux 38. <a href="" target="_blank" rel="noreferrer noopener">Voting</a> is open to all Fedora contributors. The voting period starts on Monday, 29 May and closes promptly at 23:59:59 UTC on Sunday, 11 June.</em></p>
<h2 class="wp-block-heading">Interview with Sumantro Mukherjee</h2>
<li><strong>Fedora Account:</strong> sumantrom</li>
<li><strong>Matrix:</strong> #fedora, #fedora-kde, #fedora-mindshare, #fedora-social, #fedora-social-hour, #fedora-arm, #fedora-devel, #fedora-qa, #fedora-workstation, #fedora-test-days, #fedora-i3, #fedora-badges, #fedora-docs, #fedora-l18n, #fedora-ambassadors</li>
<li><a href="">Fedora User Wiki Page</a></li>

This is what the beginning of the plaintext part looks like, which is generated from the interview with Sumantro Mukherjee: F38 Council election: Interview with Sumantro Mukherjee

I hope this will get fixed soon, since I have the tendency to skip badly formatted messages. I can’t be bothered switching rendering mode or heading over to the WebUI.

This one is a hard problem, because the posts are coming from Wordpress like that. I wish the Wordpress-to-Discourse plugin would post Markdown instead, but it doesn’t do anything smart like that. See this upstream:

I’m open to any clever ideas anyone has!

It’s not clever (or even particularly good), but the best short term solution is probably to subscribe via email to the Community Blog and suppress notifications from Discourse.

1 Like

That would work. But it would leave me without an option to reply. Since
these are more like announcements, I’m not sure that is required. But
then these could be posted to ye olde mailing list…

On the other hand, why have information duplicated? If I need to be
elsewhere to properly read the content, a link to the community blog
article would suffice.

Or, have the entire community blog integrated in Discourse. I’m probably
stepping on many a people’s toes right now, but why not? I don’t visit
Community Blog often, but what I see there seems simple enough, layout
wise, that it may as well be published on Discussion.

That way the formatting in the notification e-mail is readable and we
have one less problem to solve.