Search results for "Postorius" - Mailman-users

Mailman Core 3.3.1rc1 release

by Abhilash Raj

Hey Everyone, I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1rc1/ To install this release via pip, you can run: $ pip install --upgrade --pre mailman Note the `--pre` flag because this is a pre-release. If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. If there aren't any major breaking changes reported, the final release will be identical to this one. -- thanks, Abhilash Raj (maxking)

6 years, 7 months

Re: Postorius no connection to REST API

by Abhilash Raj

> On Aug 18, 2021, at 6:44 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: > > Abhilash Raj wrote: >> is the config to talk uwsgi protocol and you want to configure Web server to Proxy using the same protocol. You can find that in the uwsgi docs here: https://uwsgi-docs.readthedocs.io/en/latest/Apache.html You probably need an apache module to speak uwsgi, the docs should have the details. >> Notice the URL is uwsgi:// instead of http://. >> Other way is to configure uWSGI to speak HTTP, which can be done by replacing "uwsgi-socket" by "http-socket” in the uwsgi.ini configuration. This might be the easiest for you to try, do make sure to restart the mailman-web service after making the change in uwsgi.ini. > > Thanks, that already helped quite a bit. The website is now loading again, but unfortunately not much else. The site still shows no Connection to REST API. Is your mailman core systemd service up and running? Have you modified the default host:port for Core in mailman.cfg? -- thanks, Abhilash Raj (maxking)

5 years, 2 months

MM3 gateway errors and frequent reboot needs

by Stephen J. Turnbull

hansen(a)rc.org writes: > We have had to reboot the list server almost every week and wonder > if there is something leaking and eating up resources. That's something you would have to check yourself, using Unix tools like ps, df, and lsof or Activity Monitor on Mac. I don't recall any cumulative resource problems like this. Some old reports indicate certain configurations and activity patterns put a lot of instantaneous pressure on the system, but this doesn't sound like that. Also those problems were specific to the software stack (databases, caches, search engines) that was used. The current recommended stacks do not have those problems as far as I know. The only current performance problem I'm aware of is in using the REST API directly to get large collections (eg, 10,000 member subscriber lists). (My currect thinking is that those are best addressed by using the corresponding paged endpoints, but still researching.) However, that is not a cumulative problem, it's a size-of-list problem, so it doesn't sound related. Are you running all of Mailman core, Postorius, and HyperKitty on the same server? For Postorius and HyperKitty, what webserver are you using? What database backend? What other applications are running on the server? What operating system and version? Recent hardware? > I does not appear to be memory, though. The server is slow to > respond (could be because it's overseas) and then after some time > we get intermittent gateway errors and finally we cannot access the > lists online because of the gateway errors. What does "gateway errors" mean? If problems with Internet routing or firewalls, I don't understand how network errors could be arise from a problem in Postorius. Why do you think Postorius could be responsible for those, aside from them appearing after switching to Mailman 3? Are you sure you weren't having them before? > It appears to me that the issue is with Postorius, but I could be > wrong. Do files get closed after opening? Yes, as far as we know. No reason to think otherwise since this is not something that has been reported that I can recall, and Python 3 helps us to code in a style that is not so vulnerable to such leaks. > Are we alone having such issues? So far, yes. > PS: My old MM2 installation could (and did) run without any > help. Not so with MM3. I don't think any of *our* feelings would be hurt if people decided to keep their Mailman 2 installations. :-) It's still great software for what it does. But it took more than 10 years to get there (the first production installations were in about 1994! and it's been feature- stable since about 2005 I'd guess. Unfortunately it wasn't possible to bring in the kind of features that many people need nowadays without a complete rewrite (partly a matter of manpower -- Python 3 brings a lot of power and fun to programming, partly a matter of technical debt making Mailman 2 code hard to change in big ways, and partly a matter of the need to port to Python 3 for the very long run), and the new features themselves changed the way that Mailman (and Mailman's users and administrators) interact with the network.

6 years, 6 months

Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Mark Sapiro

On 8/25/25 12:42, Flo via Mailman-users wrote: > Hi, > > I have setup in Debian Trixie mailman3-full and came that far, that I > have created a mailing list. I can sent emails to the members. Your primary support resource for the Debian package is Debian. See https://wiki.list.org/x/12812344 > However when I send from an email which is non-member the message is > held. If I want to accept this message as list admin, I get: > > `An error occurred while processing your request.` > > And I get an email: > > `Internal Server Error: /mailman3/postorius/.../held_messages > > TemplateSyntaxError at /postorius/lists/.../held_messages > 'humanize' is not a registered tag library. Must be one of: You need to add 'django.contrib.humanize' to the INSTALLED_APPS list in settings.py. If you Debian packages don't do this, it should definitely be reported to Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

Re: Customizing Look and Feel?

by Mark Sapiro

On 12/27/18 7:42 PM, Joel Lord wrote: > Is it possible to customize the look at feel of the web interface at > all? I have some lists that really require that subscription requests > include full name, to make the workload on the moderators, well, > workable in keeping a closed list tight. I've found where the "Your > name (optional)" text is in list_forms.py, but modifying that strikes me > as a poor plan. > > Changing that text would be lovely. Actually making that field required > would be seriously awesome. > > Is this possible in the current code base (3.2.0) without doing > ill-advised things modifying source code? None of this is really possible in Postorius without modifying source code. However, Postorius is just an example of a web list management UI. While it is non-trivial, it is possible to build your own web UI that either communicates directly with Mailman core's REST API or communicates via MailmanClient. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

Re: Unsubscribe Notifications Clarification

by Abhilash Raj

On Wed, Sep 2, 2020, at 7:32 AM, Brian Carpenter wrote: > I am trying to understand how Mailman 3 handles unsubscribe > notifications. From my testing I see the following behavior: > > 1. If list member sends email to listname-leave@listname, an > unsubscribe notification is sent to both list owner and list member if > list settings have them enabled. > > 2. If list list member is a registered user of Postorius and he uses > Postorius to unsubscribe, then no notification is sent out to either > list owner or list member, even if list settings has unsubscribe > notifications enabled. > > Is this correct? This is a bug in Core, for which I have opened https://gitlab.com/mailman/mailman/-/issues/759 It seems like the Unsubscriptions via the API do not follow the right codepath and just unsubscribe the user. It also does not seem to take the unsubscription policy into account. > Brian > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

Re: only show mail domains from web host on web-host-url

by Jens Günther

Thanks, already had a look at the issues and thought with the merge requests that it was solved :-) Maybe I have to update my mailman to 3.3.3 so that it does!? Or is it that you are saying that this hasn't been fixed but tried to and it didn't work!? Actually I see the logic of what you are talking about in the issues, but don't see if what happens with the code can be correct, since I'm unfortunately not a coder. Any other ideas how I could go on / help? This qould be a quite central feature for using mailman3 for us. Thanks anyway. Am 19.03.21 um 17:21 schrieb Mark Sapiro: > On 3/19/21 6:38 AM, Jens Günther wrote: >> Thank you for your answer. I should have seen that in the Docs, but >> somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html >> >> I set it in the corresponding file, but unfortunately it doesn't work >> :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS >> works, changed here from '*' to 'localhost' and my example-domains, this >> works). It seems to be the same as this user describes (a while ago): >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > FILTER_VHOST is problematic. It works fairly well for HyperKitty, but > not so well for Postorius. In particular with Postorius it doesn't work > if there is more than one mail host domain with the current web host. > See these issues and MRs for more detail. > > https://gitlab.com/mailman/hyperkitty/-/issues/254 > https://gitlab.com/mailman/hyperkitty/-/merge_requests/243/diffs > https://gitlab.com/mailman/hyperkitty/-/merge_requests/244/diffs > https://gitlab.com/mailman/postorius/-/issues/394 > https://gitlab.com/mailman/postorius/-/merge_requests/500/diffs >

5 years, 7 months

Re: SUBSCRIBE_FORM_SECRET in MM3?

by Mark Sapiro

On 1/30/20 1:50 AM, Gila Halpern wrote: > I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option? This feature in MM 2.1 is not very effective. On mail.python.org, this feature as well as reCAPTCHA is enabled (e.g. <https://mail.python.org/mailman/listinfo/mailman-users>) and we still get periodic attacks of robotic subscribes that get around these measures. To answer your question, no, this does not exist in Postorius which is an entirely different, Django based web UI. Django may have some protections built in; I'm not sure about that, but there's nothing in Postorius itself like this MM 2.1 feature. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 14/2/21 18:42, Mark Sapiro wrote: > On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I did some exploration this morning (Spain time) in the weblate >> statistics and archives and I found that the changes done from >> Victoriano and me were recorded. I did a screencopy of all that if >> someone has any doubt about it. I downloaded this files: >> >> -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po >> -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po >> -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po >> -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po >> >> The thing is that they differ from the .po installed via pip upgrade. >> Mostly, as said, postorius, hyperkitty and django_mailman3. > > The latest packages in PyPI (pip) were released on Feb 2 except for > django-mailman3 which was released on Jan 15. They don't include updates > after those dates. > And I say that I (and others ) have made translations in postorius, hyperkitty an Django_mailman3 in January. Yes, I've made some changes in february 10th, but It were a pair of messages. But that's all about this from me. If in the next upgrade I find that there is any translation missing, I know, thanks to you and Victoriano, how to handle it. And if some new admin installs mailman 3 and try to localize it to spanish and comes to this list to ask how to do a more complete translation... well, these messages can point him or her to the right direction. My postorius web access to the lists is now almost completely translated to spanish and now I can help the users without hesitating language problems. Thanks. Thanks a lot.

5 years, 8 months

Re: spanish localization

by Mark Sapiro

On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I contributed in january to translate to spanish all the items left in > Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I > thought they will be used in the next upgrade, but I cannot see any > improvement and there are many words untranslated. The Spanish translations for Mailman core and HyperKitty are currently completely up to date with weblate. django-mailman3 differs in one string that was translated on Feb 10 and hasn't yet been merged. Postorius also differs in a few places from the Feb 10 version that hasn't yet been merged. Other than that, the translations should be good. > Is there any way to upgrade the .po files in order to get the last > translation? For the web UI you need to run the django management `compilemessages` command. For Mailman core you need to run ``` cd mailman/messages/es/LC_MESSAGES msgfmt -o mailman.mo mailman.po ``` to compile the mailman.po file for gettext. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Mailman-users search results for query "Postorius"