[Mailman-Developers] Re: Improving the speed of mailman import21
On Mon, Oct 7, 2019, at 5:37 PM, Mark Sapiro wrote: > On 10/6/19 10:11 AM, Abhilash Raj wrote: > > > > I am hoping that I can commit the change with the commented out code, > > unless I am reminded of a use for the passwords in Core's database. Then, > > it might be a bit more of work trying to figure out another way to improve > > the speed. > > > I'm not at all sure what's actually implemented, but there is a feature > for pre-approving a post with an Approved: header with a password. This > is also supposed to work to approve held posts, but approving/discarding > held posts by email is broken anyway[1]. > > Lists have a moderator_password attribute which is an encrypted version > of a plain text password that can be used for this purpose, but the > original intent IIRC was that this could be the password of the user > sending the mail and would be accepted if the user was an owner or > moderator. As I said, I'm not sure (don't think) this is implemented, > and a much better approach is to abandon the Approved: header in favor > of a pgp signature from an owner/moderator. That's correct, it does seem to be implemented today but using the moderator password. I agree that it is better implemented using gpg signatures instead of passwords. > > The other possible use for this password is if a user imported by > import21 wants to authenticate to Django, she might be able to use this > password. I don't think that's the case now. I don't think we should be doing this, it is better than the migration allows for a new more secure password than re-using old ones, which have been sent out over email in past. It is tricky how multiple-password world get translated to single-password world, it makes the final password somewhat non-deterministic, depending on what the last mailing list imported was, which does not sound right anyway. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > ___ > Mailman-Developers mailing list -- mailman-developers@python.org > To unsubscribe send an email to mailman-developers-le...@python.org > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ > Mailman FAQ: https://wiki.list.org/x/AgA3 > > Security Policy: https://wiki.list.org/x/QIA9 > -- thanks, Abhilash Raj (maxking) ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Improving the speed of mailman import21
On 10/7/19 5:37 PM, Mark Sapiro wrote: > > I'm not at all sure what's actually implemented, but there is a feature > for pre-approving a post with an Approved: header with a password. This > is also supposed to work to approve held posts, but approving/discarding > held posts by email is broken anyway[1]. Forgot the reference [1] https://gitlab.com/mailman/mailman/issues/169 -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: Improving the speed of mailman import21
On 10/6/19 10:11 AM, Abhilash Raj wrote: > > I am hoping that I can commit the change with the commented out code, unless > I am reminded of a use for the passwords in Core's database. Then, it might > be a bit more of work trying to figure out another way to improve the speed. I'm not at all sure what's actually implemented, but there is a feature for pre-approving a post with an Approved: header with a password. This is also supposed to work to approve held posts, but approving/discarding held posts by email is broken anyway[1]. Lists have a moderator_password attribute which is an encrypted version of a plain text password that can be used for this purpose, but the original intent IIRC was that this could be the password of the user sending the mail and would be accepted if the user was an owner or moderator. As I said, I'm not sure (don't think) this is implemented, and a much better approach is to abandon the Approved: header in favor of a pgp signature from an owner/moderator. The other possible use for this password is if a user imported by import21 wants to authenticate to Django, she might be able to use this password. I don't think that's the case now. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: GSOD Update
Hi everyone, Here's an update for week 5: For this week, I wrote a guide called ‘Why Should You Migrate from Mailman 2 to Mailman 3’. It talked about the pros of Mailman 3 as compared to Mailman 2. Just like the week before, everything worked out well. Week 5 update can be viewed here: https://medium.com/@ariessa_norramli/google-season-of-docs-week-5-update-46de203136a Thank you. Best Regards, Ariessa Norramli ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Mailman 3 Internationalization setup
Hi All, Mailman 3 is now setup for continuous internationalization. We are using Hosted Weblate[1], which is the hosted service for the Weblate project[2]. It is actually quite nice and I've been learning how to properly document a Django project from it's documentation. Which brings me to it's documentation. Weblate has great documentation for translators[2]. The UI pretty simple and should be easy to navigate around. We have setup the workflow in a way that each commit in Gitlab generates a webhook and updates Weblate. Weblate is then able to pull all the changes in real time. To pull translations back into Gitlab, I have a custom script running every night that pulls translations (as commits) and generates pull requests against the upstream repos. Weblate has the ability to automatically push the translations back, but for security reasons, I didn't want to give a 3rd party service direct push access to our repos. I've been working on a Patch to Weblate[3], which would allow it to send translations as Merge Requests (as compared to direct-push). After it is merged and deployed at hosted.weblate.org, I hope I can retire my custom script. We have setup the following projects: - Mailman Core (https://hosted.weblate.org/projects/gnu-mailman/mailman/) - Postorius* (https://hosted.weblate.org/projects/gnu-mailman/translations/) - Hyperkitty (https://hosted.weblate.org/projects/gnu-mailman/hyperkitty/) - Django-mailman3 (https://hosted.weblate.org/projects/gnu-mailman/django-mailman3/) There should be empty .po files generated for most languages supported by Django and Mailman Core. If there are any questions or bugs related to source strings, please send out an email to mailman-developers@python.org. The current translation %age is pretty low, hopefully we'll be ale to get it close to Mailman 2 sometime soon :) [1]: https://hosted.weblate.org/projects/gnu-mailman/ [2]: https://docs.weblate.org/en/latest/user/translating.html [3]: https://github.com/WeblateOrg/weblate/pull/3024 [*] Yeah, the URL for Postorius is a bit weird, because it was called "translations" before. At the time, I didn't know the difference between a project and a translation component in Weblate terminologies. And they don't give out permissions to change the URL, so we're maybe stuck with it. -- thanks, Abhilash Raj (maxking) ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
