Update release announcements links on website

[Amedee]

I work in InfoSec and my threat feeds warned me about a RoundCube vulnerability.
I was glad to see on the GitHub page that mailinabox has a new release with updated RoundCube.

I went to Mail-in-a-Box Maintenance Guide to read the upgrade instructions. I quote from the page:

Upgrading Mail-in-a-Box

You should move to the latest Mail-in-a-Box release as releases are posted, especially if an update addresses any security issues, although you do not necessarily need to do so. We will post release announcements to our twitter account @mailinabox, the announcements section of the discussion forum, and our Slack chat (see the homepage).

• The Twitter account is no longer active. It does mention a Mastodon account Mail-in-a-Box (@MailInABox@fosstodon.org) - Fosstodon though.
• It wasn’t announced in the announcements section of the forum. The last activity there was from 2022.
• Slack: the URL https://mailinabox.email/slack/ gives me a 502 Bad Gateway

I fully appreciate that communication channels can and will evolve over time, and often with good reason. Can this be reflected in the documentation on the website?

I propose the following changes:

• REMOVE link to Twitter (no longer in use)
• REMOVE link to announcements on forum (no longer in use)
• REMOVE link to Slack (broken)
• ADD link to Mastodon (in active use and current)
• ADD link to GitHub releases page Releases · mail-in-a-box/mailinabox · GitHub (in active use and current)

If there is agreement, then I will submit a pull request to the git repo that holds the website: GitHub - mail-in-a-box/mailinabox.email: The website at mailinabox.email.

[JoshData]

That would be great, thanks!

If people think I should also post to the announcements in the forum, I can make a better effort to do that also and you can keep it in.

[MSSEsq]

@Amedee

If there is agreement, then I will submit a pull request to the git repo that holds the website: GitHub - mail-in-a-box/mailinabox.email: The website at mailinabox.email.

My pull request is now many months old. Please see:

Proposed Maintenance Guide Updates

The instructions in the Mail-in-a-Box Maintenance Guide for restoring from S3 compatible backups did not work, so I updated and enhanced the instructions in a forked copy of the maintenance.html file on GitHub: Update maintenance.html. The instructions now work, and are clearer and more complete. Since I was editing the maintenance.html file, I decided to update it more comprehensively. This included updating the body to use UTF-8 character encoding, as specified in the header. I also updated th…

Update maintenance.html

Update maintenance.html

[JoshData]

It shows that the PR was closed in 2024. Feel free to re-open.

[MSSEsq]

Update maintenance.html #112 is still open along with the associated PR: Update maintenance.html by MSSEsq · Pull Request #112 · mail-in-a-box/mailinabox.email · GitHub. For some reason that I can no longer recall particularly, GitHub required me to close #111 and create #112. One line of the patched file in #112 is newer than in #111.

I started a MiaB Forum discussion, linked above, about the changes that I proposed, but little discussion resulted. I put a substantial amount of work into the proposed edits, and think the result warrants being merged into the main branch, yet always welcome constructive comment or criticism.

[JoshData]

Thanks. Merged.