Search results for "Postorius" - Mailman-users

Re: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Mark Sapiro wrote: > On 6/25/22 07:54, denis.bitouze(a)univ-littoral.fr wrote: > > > Mark Sapiro wrote: > > The difference between Reject and Discard is Reject notifies the > > sender of the rejection whereas Discard just discards the message > > without notification. > > IMHO, even in English, “Reject” and “Discard” are not > > self-explanatory. > > They seem so to me, but in any case, if you look at Postorius -> > Settings -> Message Acceptance -> Default action to take when a > (non-)member posts to the list, they are described there in much more > detail. OK: not easy to figure out. A tooltip on the corresponding buttons would be helpful. > > BTW, no clue about an automatic banishment of emails from discarded > > messages? > > In the pop-up dialog from clicking the subject of a held post you can > set the sender's moderation status when discarding the post. Sorry but I can only see: - “--- Set member moderation ---” (non selectable, I guess) - “Hold for moderation” - “Reject (with notification)” - “Discard (no notification)” - “Accept immediately (bypass other rules)” - “Default processing” and cannot see how I can at the same time “Discard (no notification)” and “Banish the email of the post's sender”.

3 years, 4 months

[MM3-users]Incorrect URLs

by Mark Sapiro

There are various URLs exposed in various emails from the list, many of which are wrong. The underlying issue is there are generic replacements such as $listinfo_uri and $user_options_uri in various templates such as the welcome.txt list welcome message and the footer-generic.txt message and digest footer. Now that the Mailman 3 core engine has been separated from the web UI, the core doesn't know what these replacements should be and there is not yet an interface to get them from Postorius or whatever the web UI is. In the mean time, I have made list specific versions of welcome.txt (done before announcing the list) and footer-generic.txt (just now) with the correct URLs hard coded. The purpose of this post is two-fold. To explain the issue, and to test the footer. There are probably more of these incorrect replacements and I will fix them as I notice them or they are pointed out to me. Note that I am aware that the https URLs in the List-Subscribe: and List-Unsubscribe: headers added to posts are wrong, but I haven't got a handle on this yet. The mailto: links in those headers are correct as are the Archived-At: and List-Archive: URLs as there is an interface to get those from the archiver. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 6 months

Re: Adding user - Error 409 Subscription request already pending

by Kevin Hurtley

Thanks Mark, This is sounding like a case of users will be users. As you suggested, I think my moderator is dealing with a user that can't find their confirmation (or understand they need to reply to it). So the moderator tried to override things by trying to add them in by using the "mass subscribe" operation. It sounded on Github that some opinion was that it wasn't necessary to see these pending requests, but as "users will be users" I think would be useful to see what is in queue for subscription requests, it would be better yet to be able to either clear them out or accept them there. But at very least seeing them there would go a long way helping out my moderators troubleshoot. On another request, user found the confirmation email, replied, and was accepted. However that email was several weeks old. So I'm guessing our default for expiration of requests is not the default of 3 days. But I haven't been able to find that setting. Is that in Postorius somewhere or will I need to change with the shell? I wonder if temporarily changing the Subscription Policy to "open" would allow those in pending to be accepted and clear that queue out? Thanks again for the input, much appreciated! Kevin Hurtley CoastAlaska, Juneau, Alaska

6 years, 6 months

[MM3-users]Re: Installation issues

by Andrew Hodgson

Mark Sapiro wrote: >On 04/19/2016 11:40 AM, Andrew Hodgson wrote: > >> I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow? >Sort of, but it's not (yet) public. The process I followed is very >convoluted and not what I would recommend anyone follow. Part of the >issue is I started with mailman-bundler not using a venv, but bundler >still installs a lot of stuff in Python 2 and Python 3 venvs. I then >proceeded to install the git master branches of mailman, >mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their >dependencies system wide and ripped out most of the venv stuff. I started off without using venvs and ran into several issues, though one of them I think was due to the bundler pulling down an outdated dependency. My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. My main thing when looking at this is how package managers are likely to package Mailman3, especially from a Debian point of view. I know I can't second guess what is going to be done, but would like to try to build using similar goals if possible. Thanks. Andrew.

9 years, 6 months

Re: Hyperkitty import from mailman2

by Marvin Gülker

Am 24. December 2017 um 22:30 Uhr +0200 schrieb Sten Aus <sten.aus(a)eenet.ee>: > Oh my god. :) That's it! There are no latest messages and front page shows > only last month "activity". Thank you! I did not thought that I should check > some older posts. :D I know that feeling. It took me a while to figure this out as well. Error on OSI Layer 8. > But how did you manage to import all the lists and members from Mailman2 to > Mailman3? As I understand Mailman3 does not "support" (by manual) import > right now? You'll be surprised, but those mailinglists were not managed by Mailman2 before. They were managed by mlmmj[1]. I wrote a script that converted mlmmj's archive into mbox format, and then used the "hyperkitty_import" command as explained by the Hyperkitty manual[2]. This worked surprisingly well. As for the subscribers, Mailman 3's Postorius has a mass-subscription facility in the admin interface. I extracted the list of all subscriber emails from the mlmmj mailinglist and used that mass-subscription facility to subscribe people again. There's an option to disable delivery of the welcome email that should be ticked before this I guess, though. It can be reset afterwards again. Greetings Marvin [1] http://mlmmj.org/ [2] http://hyperkitty.readthedocs.io/en/latest/install.html#importing-the-curre… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 10 months

Re: spanish localization

by Abhilash Raj

On Sun, Feb 14, 2021 at 01:08, Victoriano Giralt <victoriano(a)uma.es> wrote: > El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió: >> What translations are those? Please give specific examples. What I >> am >> saying is Mailman core 3.3.3 is currently up to date with weblate. >> There >> are no Spanish translations for core done after 7 November in >> weblate >> and weblate shows 100% completion for Spanish for Mailman core. > > Mark, please, how do you check when translations happened? Nov 7th is > a > very significant date for me (it is my wedding anniversary) and I'm > 90% > sure that I dedicated time to Weblate after that date... You can look at the commit history of the spanish po file to get a detailed history of when and who made the changes. For example: Core: <https://gitlab.com/mailman/mailman/-/commits/master/src/mailman/messages/es…> Postorius: <https://gitlab.com/mailman/postorius/-/commits/master/src/postorius/locale/…> You find similar histories in all the repos. Each person's changes should be an individual commit in the repo, typically all outstanding translations are committed every night in Weblate. > > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, > after > updating to the latest releases, are still in Englanish (more English > than > Spanish). Could this be because of the .mo files not being up-to-update? There used to be some strings that were translated incorrectly, but I think we fixed all of those that we found. Abhilash > This is not a fight, we want to help, but do not know how. > > Thanks! > > -- > Victoriano Giralt Innovation Director > Digital Transformation Vicerectorate University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. >> Q: Are you sure ? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting annoying in email ? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> thanks, Abhilash Raj On Sun, Feb 14, 2021 at 00:57, Victoriano Giralt <victoriano(a)uma.es> wrote: > El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) > via > Mailman-users escribió: >> On 13/2/21 20:00, Mark Sapiro wrote: >> > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> > wrote: >> > > But... here is a thing that I can not understand: If the source >> (the >> > > .po >> > > file) is from november 7th, it doesn't matter how many times you >> > > recompile it: the result will be the same. >> > Correct, but the point is if you download the latest >> > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov >> 7 >> > file >> > in the distribution, you will find they are identical, so it it >> appears >> > that the weblate translation hasn't changed since that time. >> > >> > If there are issues in this mailman.po, they exist in weblate too >> and >> > need to be fixed there. >> >> That clarifies all. Thanks. As I said in my previous message, I'll >> wait >> for the next upgrade and hopingly the translations done after 7h of >> november (by others and me) will be there. > > I've visited Weblate, all Spanish strings are translated. Spanish is > 100% > translated, but, none of them have been "approved", whatever that is. > It > seems that a reviewer needs to approve the translation in order for > them to > be incorporated or released or whatever. I was sure I had reviewed > everything between November 7th and the day Abhilash announced the > release > candidate and asked for translation review, but nothing has made it > to the > released version. > > Maybe there's something in the translation flow that we are doing > wrong. > I'm starting to miss the good old days when Mailman 2 translators just > downloaded the .po files and returned them :-) > >> > Also note that the translations on weblate only affect strings in >> the >> > core code. The Mailman core templates are not currently >> translated in >> > weblate and there are currently no Spanish language templates. One >> > would >> > need to create Spanish translations of all the templates in >> > < >> > >> <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> >> > > >> > and submit a merge request to add them to a mailman/templates/es/ >> > directory. >> > >> I will make the template translations locally, test them, and then, >> if >> they are yet lacking in the main repo, follow your suggestion. > > I'm a bit short on time, but I'll help Guillermo with that, at least > reviewing or doing a second pass. I'm not proficient enough to speak > about > Mailman core templates, but for Django templates, there is a nice tag > for > marking text with translations in the .mo files ... > > -- > Victoriano Giralt Innovation Director > Digital Transformation Vicerectorate University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. >> Q: Are you sure ? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting annoying in email ? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

4 years, 8 months

Re: A new issue with installation

by Andrew Hodgson

Abhilash Raj wrote: >On Sat, Feb 20, 2021, at 9:28 AM, Abhilash Raj wrote: >> >> >> On Sat, Feb 20, 2021, at 8:51 AM, Brian Carpenter wrote: >> > As usual, a new issue has arisen with installing Mailman 3. It seems >> > Postorius and Hyperkitty want to install a module called cryptography. >> > Which I am unable to install because of this: >> > >> > error: Can not find Rust compiler >> >> You need to install a Rust compiler. Depending on which distro you are >> using, you can run `sudo apt install rustc` or same command with `yum`. [...] >FAQ: https://cryptography.io/en/latest/faq.html#installing-cryptography-fails-wi… > >You can skip the Rust components by setting `CRYPTOGRAPHY_DONT_BUILD_RUST` but that would work just for this release and you won't be able to skip from the next release of cryptography. Its also possible to install an older version of Cryptography before installing Mailman dependencies which doesn't require this. Version 3.3.2 is the version I have been using recently at work. On a side note I have been experimenting with using underlying Debian packages for some of the Python dependencies and using the --system-site-packages option when creating the venv to simplify installation and reduce the number of compilation tools required on the system. Thanks. Andrew.

4 years, 8 months

Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/16/25 13:43, via Mailman-users wrote: > HI Mark, > > I simply tested by unsubsribing to the mailing list and then re-subscribing to receive the welcome message. > > How do you test using the mailman command with user list? sudo -u list mailman addmembers -h or in your case, you may not have that subcommand in which case see sudo -u list mailman members -h However, that is all irrelevant. I only thought you might be testing by using `mailman` commands to add a member and if so and if the command is not run as user `list`, it might not have access to read the template. If you are (un)subscribing via Postorius or via email these are handled by Mailman runner processes which should all be running as user `list` and should have access to the template. So, as I said, I don't know what the issue is unless it is something with your Debian package which is ancient. Even Debian buster has mailman core 3.2.1. Does your empty list:member:generic:footer.txt work to not add any footer to list messages? If so, I can't think of any reason why your list:user:notice:welcome.txt wouldn't be used. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Mark Sapiro

On 12/02/2016 08:07 AM, Barry Warsaw wrote: > Hello Mailman 3 users and developers! > > It's been a long slog but I think we are finally ready to begin the release > process for Mailman 3.1. I am pretty happy about the state of the Core, and > Florian is going to do some more integration testing with HyperKitty and > Postorius. We still have a few issues and a merge proposal or two to address, > but I am planning to spin a beta of Core this weekend to facilitate testing. Barry, I understand you need to feel comfortable about everything going into the core and this takes time and energy to review all the MRs, but I think it is pretty important to get the DMARC mitigations into the core. If there's anything I can do to help with this, let me know. I will rebase my branch again and possibly make one minor tweak, but I think it should be OK. I can also work on Postorius. Also in this vein I have a question. Should the DMARC settings be added to the Alter Messages tab in the List Settings view or would it be better to have a separate DMARC Mitigations tab. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 10 months

Enforcing SSO and subscription options

by Stephen J. Turnbull

dlb-ml--- via Mailman-users writes: > I'm looking to see if there's any way to isolate the third-party > login section and prevent local account sign in and sign up. This > way, we can ensure that the people within our organization are > using a stronger auth method that prioritizes MFA, rather than just > username/password. This is really a Django/allauth question. I strongly recommend you ask there. Maybe Mark knows more, but my own experience with it is limited, and the client specified the setup, I just implemented it. > I did see that there is the SOCALACCOUNT_ONLY option, as provided > by allauth > (https://docs.allauth.org/en/latest/socialaccount/configuration.html) > but that broke any attempt to display the sign in page, My experience was using Shibboleth to authenticate to Apache, require authenticated user for all Mailman and Django locations, and Apache would communicate the authenticated user ID directly to Postorius. You could visit the page, but because you were already authenticated, you had to log out to log in. But -- Catch-22 -- that access would go through Apache and log you in. > assuming [SOCIALACCOUNT_ONLY] is not supported with the current > version of MM3. AFAIK, there's no code in Postorius that's specific to processing authentication -- that's all done by Django or Django plugins, and controlled by the standard Django and allauth parameters. So it's not something Mailman is related to supporting. This is a question of what allauth, and possibly Django core, supports. It's possible that Mailman defaults to a configuration that messes up Django's support, but if so I would bet that somebody with deep knowledge of how allauth works could tell you how to get the effect you want. > Is my plan to modify the templates viable? It's not clear what your goal is. If it's just to keep typical users on the straight and narrow, yes, that should work. But as far as I know, a competent user who is mischievous or malicious can probably craft requests to successfully access any locations that are not disabled in code or protected by the frontend webserver. Disabling the signup adapter will definitely make mischief much harder, but I can't promise it's impossible. But if you have a SSO system with an organization-specific IDP or a database of 3rd-party accounts with Google or whatever, I would think you'd want to use that as the source of ground truth directly, as I described my experience above, rather than creating a separate credientials database in Django. > Given the discussions on disabling the anonymous subscription form, > are the email commands a less spam-susceptible solution or are they > just as vulnerable as the form? The whole point of email commands was to allow anonymous signups (more precisely, pseudonymous signups tied to a mailbox). If you don't want "anonymous" signups, you don't want to enable the email commands.

8 months, 2 weeks

Mailman-users search results for query "Postorius"