Northamerican Alied Fruit Experimenters

Northamerican Alied Fruit Experimenters
nafex list at ibiblio - http://lists.ibiblio.org/mailman/listinfo/nafex

Tuesday, January 23, 2024

[NAFEX] Fwd: [MIGRATION OUTAGE] lists.ibiblio.org outage and change Jan 29-31

---------- Forwarded message ---------
From: lists-migration-announce-le-z <
lists-migration-announce-le-z@ibiblio.org>
Date: Tue, Jan 23, 2024 at 5:51 PM
Subject: [MIGRATION OUTAGE] lists.ibiblio.org outage and change Jan 29-31
To: lists-migration-announce-le-z <lists-migration-announce-le-z@ibiblio.org
>
Cc: admin <admin@ibiblio.org>


Hello from the students and staff at ibiblio, the hosts of a mailing list
you own or manage.

We are writing to inform you that lists.ibiblio.org, which is currently
running the Mailman mailing list software, will be unavailable for a period
spanning three (3) business days from

START of outage: Mon Jan 29 10:00:00 EST 2024

(Click here to see the outage START time in your local time zone
<https://www.timeanddate.com/worldclock/converter.html?iso=20240129T150000&p1=746>
)

END of outage: Wed Jan 31 14:00:00 EST 2024

(Click here to see the outage END time in your local time zone
<https://www.timeanddate.com/worldclock/converter.html?iso=20240131T190000&p1=746>
)


We have put together a page about this outage available here:

https://support.ibiblio.org/t/lists-ibiblio-org-planned-outage-and-changes/771

And we are copying some of the content at that link here for your
convenience.

Q&A:

Q: Why this change? Why now? Why so long?

A: Our existing infrastructure powering lists.ibiblio.org is now
End-of-Life and not receiving updates. A major change to the web interface
was inevitable, as our existing software moved to a new major version that
split the web interface out into its own separate project. We reviewed what
other institutions that had migrated away from our old solution had done,
and we prioritized looking at migrations that had stayed with self-hosted
Free/Libre and Open Source Software (F/LOSS), as well as migrations done by
institutions similar to ours. We considered several of the options and
eventually settled on one that has an active community, good documentation,
and multiple large universities that have been public about their migration
from the same system we currently have to this solution.

The reason we have accelerated this change and are implementing it now is
that our parent institution has support for complying with new rules from
Google and Yahoo!
<https://blog.google/products/gmail/gmail-security-authentication-spam-protection/>
about mail signing (and other factors) for bulk mail. There is no way for
us to be confident of the needed changes to comply with Google's new rules
using our existing platform.

The reason why this outage is taking multiple business days has two parts.
The first is that we have relatively few staff given the size of our
infrastructure, and the second is that we take our role as an archive very
seriously. While we could have a relatively short outage, we are not
confident that we could assure you that your list archives would still be
present in full and available (either privately to subscribers or publicly
depending on the list) as they are now. The only way that we can
confidently migrate our systems is to take additional time to test while
the system is down to prevent changes.

Q: Do I need to forward this to my mailing list?

A: Not necessarily, but you may choose to do so, and we encourage you to do
so if your list members depend on posts from your list to make decisions
about their day the same day the post is sent.

For a shorter outage, mail would simply be delayed. Given the length of
this outage, it is inevitable that some number of mailing list subscribers
will attempt to post and eventually see a "bounce" notification from their
mail provider. If you think your subscribers will be concerned, or will
send you complaints, we encourage you to pass along this notice, or some
kind of notice of your choosing, before the planned outage starts.

After the outage, list subscribers should be able to receive messages from
your list and post messages to your list as before. The list addresses will
not change with this migration.

Q: Do I need to do anything with my list settings before this migration?

A: No, we have an export and import procedure that will migrate your list
from the old system to the new one. This includes subscription and
moderation policies, archive policies, etc.

Q: I'd rather stick with the Mailman system I know, so how can I opt out?

A: Unfortunately there's no way to do this and keep your mailing list from
getting slowly increasing amounts of abuse inbound, and slowly (and maybe
later suddenly and dramatically) less email delivered outbound. We are
doing as much as we can to ease your transition to the new platform, and we
acknowledge that with our limited staffing, for some of our contributors it
will not be nearly enough help to make the transition comfortable. For
that, we apologize and hope you will bear with us.

Q: If something is broken after the migration, who can I talk to?

A: We encourage you to start by just naming your mailing list and linking
to the list information page at lists.ibiblio.org as a reply to the support
post here:

https://support.ibiblio.org/t/lists-ibiblio-org-planned-outage-and-changes/771

If you do not get a reply in a timely manner, please do not add another
post. Instead, please fill out a help request at
https://www.ibiblio.org/help/request/ and check your email, including spam
trap, for an automated response after 10 minutes.

--
You received this message because you are subscribed to the Google Groups
"lists-migration-announce-le-z" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lists-migration-announce-le-z+unsubscribe@ibiblio.org.


--
Lawrence F. London, Jr.
lfljvenaura@gmail.com
__________________
NAFEX mailing list
NAFEX@lists.ibiblio.org
Northamerican Allied Fruit Experimenters
subscribe/unsubscribe|user config|list info:
https://lists.ibiblio.org/mailman/listinfo/nafex

No comments:

Post a Comment