Re: [ovirt-users] Mailing-Lists upgrade

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --r06HXIJQUqr6fMScECWxihviBhteo46Nk Content-Type: multipart/mixed; boundary="j2E7QVK06iaeKVlWVeB6pDk6Csdl3eeux"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck@redhat.com> To: karli@inparadise.se, oVirt Infra <infra@ovirt.org>, users <users@ovirt.org>, devel <devel@ovirt.org> Message-ID: <e97ce7d5-87ab-8490-2e40-e21d7e3f6fd5@redhat.com> Subject: Re: [ovirt-users] Mailing-Lists upgrade References: <c5c71fce-0290-e97a-ddd0-eab0e6fccea4@redhat.com> <1504761696.2440.9.camel@inparadise.se> In-Reply-To: <1504761696.2440.9.camel@inparadise.se> --j2E7QVK06iaeKVlWVeB6pDk6Csdl3eeux Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Quack, First, reminder, it starts in one hour. On 09/07/2017 02:21 PM, Karli Sj=C3=B6berg wrote:
Stupid question perhaps but, have I understood it correctly that all of=
us are going to have to create new accounts for the new mail-list system, if we don=C2=B4t wish to log in using Fedora, GitHub or Google?= Or are the existing local accounts going to be migrated as well?
There is no obligation to create an account. Your subscriptions will continue working as before. You can also subscribe to new MLs without an account. Nevertheless to unsubscribe or change your settings, as there is no more a per-list email+password, you will need to create one. As for local accounts, they cannot be migrated. Accounts are global across the lists now, which makes settings practical for many things, but you previously had subscribed with different passwords and potentially different emails, so I guess it would be too complicated and Mailman developers did not consider it. Nevertheless you may recreate it using the "Sign-Up" link, and you will receive a validation link by mail, so you do not have to rely on "social" accounts. You can link other email addresses using the same method in your account settings. Hope that helps. \_o< --j2E7QVK06iaeKVlWVeB6pDk6Csdl3eeux-- --r06HXIJQUqr6fMScECWxihviBhteo46Nk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlm14rYACgkQVen596wc RD8WSw/6AmXw+BbokgdJcrf+i8a5cFpDlXNT3uQQFq0k0kPYD9fBmjG4WKKVT+Tu gAfP2EXTy06C9a84o/mCLVc2EZJ9edfXRVxXtIXXkQa8ua1QbwadMB1A5T2AaFic u5sBT4+YzaCz7kxqPYUCGmuQcZ0ZeDV+cf2XzeOgTxPpRwDYMgnMMaxmHgqtQfR1 Nsp1VtP1I17SqNwQFAD/yA5TrwwX3e0Z3YGZ3GgjcxQsHnWvSl71/roo/zfIVmzt EoDRwfjB5wP2rsJtX4XC16vCWpUTOC3TRCIuKcKV7MUKKl/EbugjmtDTICai17pQ FO9+X9NcXvvAor+T6GZ/OpzWPTKJHvKRez8UGRjJYwvp35qx3jFTNat2OtHlRWDS jgg98tRj3PgFnkOCs41hXmuowW21YhhEymVlAe3bnYfEW3ZNqBSoMlxGCRLJht9m 7CV2fpHtrPevsEC02ZbRnI0QNf+H0JhEZQolVYuDtii3EeDNiH2UZvY6igMHClex i5HfoF3eLUcqGepbxnRh+TarTiS3sn49qq3kO8kLpnqqL3qYtBE6MJHNgnxS7YLR p/1DAMOBCyrnJzt3VN2A39I4l/Ox8GX0vR0AVG0Pvvq/MPBJXijeel8aZTp1jgA5 AEZe22jVOHUAAfWhoQyK/rfBf5Y8UNAoDsWSYRNfLLYzlDetWL4= =EnOZ -----END PGP SIGNATURE----- --r06HXIJQUqr6fMScECWxihviBhteo46Nk--

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VORjUKjEkHl87tnP2OpvAcDP6P3cDrplE Content-Type: multipart/mixed; boundary="ErRA58xQUPI4B0r7sg94A6samB36fGTgr"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck@redhat.com> To: oVirt Infra <infra@ovirt.org>, users <users@ovirt.org>, devel <devel@ovirt.org> Message-ID: <17206a71-ce9b-0fe0-8909-b333903b4b01@redhat.com> Subject: Re: [ovirt-users] Mailing-Lists upgrade References: <c5c71fce-0290-e97a-ddd0-eab0e6fccea4@redhat.com> <1504761696.2440.9.camel@inparadise.se> <e97ce7d5-87ab-8490-2e40-e21d7e3f6fd5@redhat.com> In-Reply-To: <e97ce7d5-87ab-8490-2e40-e21d7e3f6fd5@redhat.com> --ErRA58xQUPI4B0r7sg94A6samB36fGTgr Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Quack, In short, it did work out well and I had to rollback because of a nasty bug. A few mails were lost, mostly automated, sorry about this. There is a bug in the LMTP communications between Postfix and Mailman 3, which probably lies in the LMTP library (aiosmtpd) used by MM3. They dropped Python 3.4 support so that was not very practical. I backported patches which seemed relevant, experimented too, but I was not able to fix the bug. I will need more time to dig into the problem and in the meanwhile I decided to rollback to the previous server so that people can work. We can reattempt a sync+migration when this is ready. Sorry about the disturbance. \_o< --ErRA58xQUPI4B0r7sg94A6samB36fGTgr-- --VORjUKjEkHl87tnP2OpvAcDP6P3cDrplE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlm2TsUACgkQVen596wc RD9gDhAAqFMtS7i2pcRptNlNwLxGVsxSYjMdvLjWJV2thYMrMWYG+2Uh7SNthuOk EPNl9ncrpRWewwHcj5la+ePHWws6Kez6gi0F5YoNjaxtnza5mKVNCPJAW/TQYrgs 8QKRv40GUB25AFotJ4RG0+/iOy5Qfqu5a97zi8Zd/IKD/FC3AEKDxt9gq3Tm3zkZ HF0Vdt3wXCS6p59GbO/Rp3N6KIRt7EtySiacN+AhugeJ9vFspzgy+QqHhBUroaCW nNTvTHBepg+Y/DPMrEdfO9CMgiAAxi8yE91aaiX0tdNn4Aw1/ejF/ZAedF1vEHS7 H+YjdftUckVdx35lNT89pU+DHgtD33QBMFPOPNKG+sL491e2pAusNsmnQAJAN92z G84y99QKMZ4O6nycRJRIRoCTtZV/zU6fdt2EMpzaoReekoANZwBAMm+BZt3BSVmW Ss3CFYaDAyBXAGFyr2At1Bnz5z9KFDp7Itx4CT9GKvWFWIIPj3f4PyxRBo2lOa/i G8BpGJwUlS/IwjWYKOax+57ZXEdCfITkaSf9qfj9jRd6VEnNILZqpMUCYVs4en80 AnWuLOKvAqcdr8eq7KVEJeuHq/qHENdVmbBA9KmN7fPhfU+cR+nVbLy5E2PHUUxH IFKo5G51D4Fkz2Zm/33DIwAHnOfo2mdUy8mmyQJFOQqICT9XvtY= =mnob -----END PGP SIGNATURE----- --VORjUKjEkHl87tnP2OpvAcDP6P3cDrplE--
participants (1)
-
Marc Dequènes (Duck)