I'm also a user and manager of several groups.io lists. While I appreciate the service and find it well thought-out and designed, I've noticed a steady stream of features finding themselves behind their paywall, and, in general, it seems some of these "freemium" services don't have sufficient non-profit / small business membership tiers -- the pay tiers are simply not affordable for groups with small-to-zero budgets.

Some of the objections to cloud-hosted solutions in this thread may be related to these issues.

-- 
73,
Chris KE2A


On Fri, Apr 22, 2022, at 10:45 AM, Teton Amateur Radio Repeater Association via 44net wrote:

Well, there are some interesting comments. One being the cost of service. If you look at the discourse link, right away it says it is $100 per month, so it is not free. And if they were to decide this group was a business then it is $300 per month. Still not free. Trying to find pricing for groups.io shows starting at $20 per month for up to 500 members. I don't have any idea how many members there may be to this group.

A few have said they don't want anything that is "cloud based". Anything you get from the internet is "cloud based" one way or another.

A few years ago when most of the groups were jumping from Yahoo some of the groups talked about google. That is probably one of the worst places to go to. I, along with several others in several groups said if they went to google we would drop out. That hasn't changed for me. Trust google for much of anything? Good luck with that.

A bit of my experience with groups.io. For those who like the digest, it works, for those who like to get email, it works, for those who just want to look at the messages in the group, it works. It works well for archive and searching. A couple of other good features, it allows an email receiver to limit attachment size (for those inconsiderate people who think they have to send an image that is 10 megs and larger) so instead it sends a link for the attachment. Also, if a user is no longer interested in getting email about a subject, it allows that user to mute the subject, which means they don't get any more emails about it. Since I don't manage any groups, I'm sure there are several management tools available to manage the group.

Mick - W7CAT


----- Original Message -----
From: Rosy Schechter - KJ7RYV via 44net <44net@mailman.ampr.org>
To: 44net@mailman.ampr.org
Sent: Thursday, April 21, 2022 06:53:23 PM
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/
>
> Curious if folks haved used it and like it.
>
> Rosy
>
> Rosy Schechter - KJ7RYV
> Executive Director
> Amateur Radio Digital Communications (ARDC)
> 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
> >
> >
> > On Thu, Apr 21, 2022 at 11:03 AM Mike Tindor via 44net
> > <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 > > > 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 > 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 SPF record
> >
> > and it appears themailman.ampr.org emails are being signed with anARDC.NET DKIM key rather than amailman.ampr.org DKIM key
> >
> > Mike / AA8IA
> >
> >
> > On Thu, Apr 21, 2022 at 9:07 AM Chris Smith via 44net
> > <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/
> >
> >
> > The MX record has been updated to point to the new
> > server, so you should continue to send emails to
> > 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
> >
> > 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
> >
> >
> > _______________________________________________
> > 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
> _______________________________________________
> 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