I do not know the details but suspect all the changes are on the server-side, and they web pages for subscribing or viewing archives may be a little more modern. See https://docs.mailman3.org/en/latest/migration.html JL On 10/11/23, 12:25, "ietf on behalf of tom petch" <ietf-bounces@xxxxxxxx <mailto:ietf-bounces@xxxxxxxx> on behalf of daedulus@xxxxxxxxxxxxx <mailto:daedulus@xxxxxxxxxxxxx>> wrote: I note that the RFP specifies an upgrade from V2 to V3 which to me implies changes. I cannot see any mention of education for end users which, experience tells me, is where many projects get a bad name. I come in on Monday morning and the muttering is loud and long because we can no longer do the work in the way we could on Friday because the system was upgraded the day before and the new version lacks features no-one knew we were using! The answer is then, sometimes, go read the manufacturer's man pages. Mmmm So what changes will end users see going from V2 to V3? What functions will we lose? If you were changing the version of IOS I would know exactly where to look and what to expect and there are doubtless those on this list who will feel the same about this software change but equally there will be those - like me - to whom it is a black box (or perhaps a black hole). Tom Petch ________________________________________ From: IETF-Announce <ietf-announce-bounces@xxxxxxxx <mailto:ietf-announce-bounces@xxxxxxxx>> on behalf of IETF Executive Director <exec-director@xxxxxxxx <mailto:exec-director@xxxxxxxx>> Sent: 10 October 2023 17:26 To: RFP Announcement List Cc: ietf-announce@xxxxxxxx <mailto:ietf-announce@xxxxxxxx> Subject: Award of contract for Email Processing Services The IETF Administration LLC issued an RFP [1] on 18 July 2023 for Email Processing Services. I am pleased to announce that on 09 October 2023, we awarded the contract for this RFP to Sirius Open Source [2], an open source company based in Spokane and Reading. Please feel free to contact me directly if you have questions. [1] https://urldefense.com/v3/__ https://www.ietf.org/media/documents/IETF_RFP_-_Email_Processing_Services.pdf __;!!CQl3mcHX2A!CW9mgpnnNQXB4JQRedl9YSEzg7fDLSooyZbFqKdmglBXVLLTKVl5hbjYWrZkKU8T0GgeVII8Wb38spzxrroX7DkomUpf$ <https://urldefense.com/v3/__https://www.ietf.org/media/documents/IETF_RFP_-_Email_Processing_Services.pdf__;!!CQl3mcHX2A!CW9mgpnnNQXB4JQRedl9YSEzg7fDLSooyZbFqKdmglBXVLLTKVl5hbjYWrZkKU8T0GgeVII8Wb38spzxrroX7DkomUpf$> [2] https://urldefense.com/v3/__https://www.siriusopensource.com__;!!CQl3mcHX2A!CW9mgpnnNQXB4JQRedl9YSEzg7fDLSooyZbFqKdmglBXVLLTKVl5hbjYWrZkKU8T0GgeVII8Wb38spzxrroX7Au1P8B3$ <https://urldefense.com/v3/__https://www.siriusopensource.com__;!!CQl3mcHX2A!CW9mgpnnNQXB4JQRedl9YSEzg7fDLSooyZbFqKdmglBXVLLTKVl5hbjYWrZkKU8T0GgeVII8Wb38spzxrroX7Au1P8B3$> -- Jay Daley IETF Executive Director exec-director@xxxxxxxx <mailto:exec-director@xxxxxxxx> _______________________________________________ IETF-Announce mailing list IETF-Announce@xxxxxxxx <mailto:IETF-Announce@xxxxxxxx> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ietf-announce__;!!CQl3mcHX2A!CW9mgpnnNQXB4JQRedl9YSEzg7fDLSooyZbFqKdmglBXVLLTKVl5hbjYWrZkKU8T0GgeVII8Wb38spzxrroX7Gc8kQfE$ <https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ietf-announce__;!!CQl3mcHX2A!CW9mgpnnNQXB4JQRedl9YSEzg7fDLSooyZbFqKdmglBXVLLTKVl5hbjYWrZkKU8T0GgeVII8Wb38spzxrroX7Gc8kQfE$>
