Rosy, All,
I fully agree with Tom’s assessment.
Jack Spitznagel – KD4IZ
Associate Editor – AMSAT News Service
AMSAT Ambassador
kd4iz@arrl.net
From: Tom M0LTE via 44net <44net@mailman.ampr.org>
Sent: Friday, April 22, 2022 03:50
To: 44Net general discussion <44net@mailman.ampr.org>; Rosy Schechter - KJ7RYV <rosy@ardc.net>
Subject: [44net] Re: Mailman migration
Hi Rosy
groups.io is the obvious choice here.
Ticks the boxes of:
- simple, modern, widely adopted and not just by hams
- doesn’t need someone to maintain some server
- keeps the format of email
- also has a good web UI
- free/cheap
Best regards
Tom
On Fri, 22 Apr 2022 at 02:12, Rosy Schechter - KJ7RYV via 44net <44net@mailman.ampr.org> wrote:
Thanks for the discussion, folks.
Have people enjoyed groups.io better?
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
On 4/21/22 6:08 PM, Damien Gardner via 44net wrote:
> Yeah I'm just adding my vote for please god, do NOT move to discourse.
> SAGE-AU moved to discourse a couple of years ago, and it killed the
> organisation. As it turned out, like 90% of the members REALLY like
> email, and had absolutely no interest in moving their conversations to a
> web message board. As much as discourse likes to say it supports email,
> it really doesn't do a good job of it, and with members cracking the
> shits and leaving, SAGE-AU went broke last year, and now we don't have a
> peak body for IT Professionals in Australia.
>
> --DG
>
> On Fri, 22 Apr 2022 at 11:03, Jim Kutsch KY2D via 44net
> <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote:
>
> Hi,
> Here's just one vote *NOT* to use Discourse. It's a discussion
> system, not email. So we have to go there to see if anything is new
> rather than just having info come in our inbox. For me (YMMMV) I
> find it like having an inconvenient PO Box that you have to
> intentionally go visit to see if anything is there vs. mail being
> delivered to my home mailbox.
>
> 73 Jim KY2D
>
>
> -----Original Message-----
> From: Rosy Schechter - KJ7RYV via 44net <44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>>
> Sent: Thursday, April 21, 2022 20:53
> To: 44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>
> Subject: [44net] Re: Mailman migration
>
> Hey Jeff,
>
> Great question. As it turns out, we are in fact looking to switch to
> Discourse.
>
> https://www.discourse.org/ <https://www.discourse.org/>
>
> Curious if folks haved used it and like it.
>
> Rosy
>
> Rosy Schechter - KJ7RYV
> Executive Director
> Amateur Radio Digital Communications (ARDC)
> ampr.org <http://ampr.org>
>
> On 4/21/22 5:44 PM, Jeff Hochberg via 44net wrote:
> > Evidently, some of the configurations were transferred over, but
> not the
> > user database. I'm unable to authenticate and, even if I try to
> perform
> > password recovery, I get the following message:
> >
> > "The e-mail address is not assigned to any user account"
> >
> > Not for anything but why not just switch to something like Google
> Groups
> > or Groups.io instead of having someone host a Mailman server?
> >
> > Jeff Hochberg
> > W4JEW
> > Atlanta, GA
> > jeff@w4jew.com <mailto:jeff@w4jew.com> <mailto:jeff@w4jew.com
> <mailto:jeff@w4jew.com>>
> >
> >
> > On Thu, Apr 21, 2022 at 11:03 AM Mike Tindor via 44net
> > <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>
> <mailto:44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>>> wrote:
> >
> > I too have the same issue with regard to logging in to mailman.
> > The password reset claims my Gmail address is not a valid user ("
> > The e-mail address is not assigned to any user account ")
> >
> > Mike / AA8IA
> >
> > On Thu, Apr 21, 2022 at 10:56 AM Jon Anhold <jon@anhold.com
> <mailto:jon@anhold.com>
> > <mailto:jon@anhold.com <mailto:jon@anhold.com>>> wrote:
> >
> > Looks like this lost my digest preference, and I am unable to
> > login via the web interface to change it - it says I am not a
> > user when I try to reset my password.
> >
> > 73 de KM8V
> >
> > On Thu, Apr 21, 2022 at 10:51 AM Mike Tindor via 44net
> > <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>
> <mailto:44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>>> wrote:
> >
> > Looks like there might be a little more to do, with
> regard
> > to email reputation.
> >
> > SPF and DKIM signing fail, and there is a published DMARC
> > record that quarantines 100% of DMARC failures. So the
> > list emails are going to end up in spam folders (they
> ended
> > up in my Gmail spam folder) because SPF/DKIM/DMARC
> all failed.
> >
> > 2a0a:bb00:0:44::1d needs added to themailman.ampr.org
> <http://themailman.ampr.org> <http://mailman.ampr.org
> <http://mailman.ampr.org>> SPF record
> >
> > and it appears themailman.ampr.org
> <http://themailman.ampr.org> <http://mailman.ampr.org
> <http://mailman.ampr.org>> emails are being signed with anARDC.NET
> <http://ARDC.NET <http://ARDC.NET>> DKIM key rather than
> amailman.ampr.org <http://amailman.ampr.org>
> <http://mailman.ampr.org <http://mailman.ampr.org>> DKIM key
> >
> > Mike / AA8IA
> >
> >
> > On Thu, Apr 21, 2022 at 9:07 AM Chris Smith via 44net
> > <44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org> <mailto:44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>>> wrote:
> >
> > Hello All,
> >
> > FYI, we had an issue with the mailing list server
> last week:
> >
> > The server the mailing list is hosted on
> experienced an
> > unexpected reboot. The server came back up ok and all
> > the services associated with the mailing list
> continued
> > to run, so Nagios (the application we use to
> monitor our
> > systems) did not report any issues. However, the
> sudden
> > reboot had corrupted several open files
> associated with
> > the mailing list software (Mailman 2.1) and the 44net
> > mailing list was not passing emails. As the list
> often
> > goes through quiet periods this was not noticed for
> > several days.
> >
> > Unfortunately the backup period for the server
> was only
> > set to a few days and by the time the issue was
> > investigated all the available backups were of the
> > corrupted files.
> >
> > As the longer term plan was always to migrate
> from the
> > older (now unsupported) Mailman 2.1 to the latest
> > Mailman 3.1 the decision was taken to migrate the
> > mailing list to a new server. ARDC already has a
> Mailman
> > 3 server for some internal mailing lists, so we
> migrated
> > the 44net list there.
> >
> > I am pleased to report that the archives from the old
> > server were successfully migrated over, so no loss of
> > data there thankfully.
> >
> > The web interface for the new home of 44net can
> be found
> > here:
> >
> >
> https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/
> <https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/>
> >
> <https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/ <https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/>>
> >
> > The MX record has been updated to point to the new
> > server, so you should continue to send emails to
> > 44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>
> <mailto:44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>>
> > to post to the list.
> >
> > I want to take this opportunity to thank John -
> KI5D for
> > hosting the mailing list since we had the last
> big crash
> > in 2012. The mailman server, with John looking
> after it
> > has provided excellent service to the community.
> John is
> > going to continue to help out by acting as admin
> for the
> > 44net mailing list on it’s new home.
> >
> > Best 73,
> > Chris - G1FEF
> >
> >
> > _______________________________________________
> > 44net mailing list -- 44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>
> > <mailto:44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>>
> > To unsubscribe send an email to
> > 44net-leave@mailman.ampr.org <mailto:44net-leave@mailman.ampr.org>
> > <mailto:44net-leave@mailman.ampr.org
> <mailto:44net-leave@mailman.ampr.org>>
> >
> > _______________________________________________
> > 44net mailing list -- 44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>
> > <mailto:44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>>
> > To unsubscribe send an email to
> 44net-leave@mailman.ampr.org <mailto:44net-leave@mailman.ampr.org>
> > <mailto:44net-leave@mailman.ampr.org
> <mailto:44net-leave@mailman.ampr.org>>
> >
> > _______________________________________________
> > 44net mailing list -- 44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>
> > <mailto:44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>>
> > To unsubscribe send an email to 44net-leave@mailman.ampr.org
> <mailto:44net-leave@mailman.ampr.org>
> > <mailto:44net-leave@mailman.ampr.org
> <mailto:44net-leave@mailman.ampr.org>>
> >
> >
> > _______________________________________________
> > 44net mailing list -- 44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>
> > To unsubscribe send an email to 44net-leave@mailman.ampr.org
> <mailto:44net-leave@mailman.ampr.org>
> _______________________________________________
> 44net mailing list -- 44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>
> To unsubscribe send an email to 44net-leave@mailman.ampr.org
> <mailto:44net-leave@mailman.ampr.org>
>
> _______________________________________________
> 44net mailing list -- 44net@mailman.ampr.org
> <mailto:44net@mailman.ampr.org>
> To unsubscribe send an email to 44net-leave@mailman.ampr.org
> <mailto:44net-leave@mailman.ampr.org>
>
>
> _______________________________________________
> 44net mailing list -- 44net@mailman.ampr.org
> To unsubscribe send an email to 44net-leave@mailman.ampr.org
_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org