Search results for "Postorius" - Mailman-users

Re: Finding a user to delete them

by Brian Carpenter

On 3/14/20 5:03 AM, Stephen J. Turnbull wrote: > The bundled administrative interface*is* Postorius. The Mailman > shell is basically a quick hack (sorry Abhilash; if you want to call > it a masterwork and say the speed of development is testimony to your > skills, I won't deny it;-) to give more convenient access to > internals to experienced Mailman hackers. More administrative > features is something we plan to work on, but the Mailman project will > focus on Postorius for the forseeable future. I do think List Admins would want an interface to help "manage" a user account on behalf of a user then what is currently available in Postorius. I see this come up with my Mailman 2 clients frequently. For instance, a mm2 list member asked their list admin to subscribe them to a list topic to limit the amount of messages they receive. The list admin was new and open up a ticket to find out how they do that in which I replied showing them how they as a list admin, can go in and change options on behalf of a list member. I don't see this functionality built into Mailman 3 nowhere near the extent that Mailman 2 has. Last night a Mailman 3 client wanted to know how they can add a real name to a list member. I said you can't, not as list admin. I directed them to instead of unsubscribe the member and mass subscribe them so they can include a real name along with the email address of the list member. > For alternatives to Postorius and the Mailman shell, Brian Carpenter > (follow Allan's subthread) is working on a new management UI (using > PHP), and I believe there's a working node.js API "out there > somewhere". Please be very considerate of Brian's time; he and EMWD > constitute a bulwark of the Mailman ecosystem and will be even busier > with the UI project. But do pass on your suggestions to him as well > as to us, he's indicated he's open to that. There were some very good suggestions that were brought out in this thread and I had already passed them on to my developer. My approach with Affinity is definite leaning very heavy on the needs of list admins atm. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

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

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

4 years, 8 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 >

4 years, 7 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.

4 years, 8 months

Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

On 24/06/2020 00:20, Mark Sapiro wrote: > Go to your Django admin web UI and look at your Django Mailman 3 Mail > domains. This will be at a URL like > https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ > > Do you see this domain there? If so, delete it. I hadn't logged in as admin before, so having done so I can now confirm that having done so this screen shows "0 mail domains" Because I could, I then visited "VIEW SITE" and see a mailing lists page, which is I think the same one I have been trying to visit, except of course now I am logged in. I do now see the correct, and only, mailing list configured on the core server. Returning to the previous "maildomain" page, that now shows the expected mailing list as well. Other admin pages seem to be working fine as well. I think, possibly, that it is now installed and working. ... But I don't know why. Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 3 months

Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Mark Sapiro

On 5/6/23 16:02, volkmar(a)grote-family.com wrote: > > My urls.py: >> (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py >> from django.contrib import admin >> from django.urls import include, reverse_lazy, re_path >> from django.views.generic import RedirectView >> >> urlpatterns = [ >> re_path(r'^$', RedirectView.as_view( >> url=reverse_lazy('list_index'), >> permanent=True)), >> re_path(r'^postorius/', include('postorius.urls')), >> re_path(r'^hyperkitty/', include('hyperkitty.urls')), >> re_path(r'', include('django_mailman3.urls')), >> re_path(r'^accounts/', include('allauth.urls')), >> # Django admin >> re_path(r'^admin/', admin.site.urls), >> ] We and the various docs are inconsistent about 'postorius' vs 'mailman3' and 'hyperkitty' vs 'archives' in urls. Add these re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), to your urlpatterns list in urls.py to cover both variants. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 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.

5 years, 5 months

Re: Acceptable aliases defaults to []

by Barry Warsaw

On Aug 28, 2017, at 03:42, Henrik Rasmussen <her(a)adm.ku.dk> wrote: > > * Docker-mail 0.1.1 > * Mailman 3.1 > * Postorius 1.1.1 > * Hyperkitty 1.1.1 > > Minor issues: > > Settings -> Message Acceptance -> Acceptable aliases has a default of [] resulting in "An error occured: [u'[]']" when saving. This fiend should be empty by default or at least accept the default when saving. Hi. Could you explain where this error happens? Is it in Postorius or the core/REST API? > To me the description right under the Acceptable aliases field is not user friendly. It doesn't explain the purpose of the field, but is meant for the Mailman sysadmin, not the list admin who can't be expected to understand this. A much better description would be the ones used for MM2: > > * http://www.list.org/mailman-admin/node23.html > * https://wiki.list.org/DOC/What%20does%20%22message%20has%20implicit%20desti… > > On a second note: Where I can change the field and message descriptions in MM3, like the /usr/lib/mailman/messages/[sprog]/LC_MESSAGES/mailman.po in MM2? Currently, there are no translations for MM3. Cheers, -Barry

8 years, 1 month

Re: Welcome Message

by Abhilash Raj

On Tue, Apr 16, 2019, at 6:41 PM, brian(a)emwd.com wrote: > With all of this back and forth, I got it working. Using the mass > subscribe feature or the subscribe form on the info page WHILE LOGGED > IN AS ADMIN was causing the error. That shouldn't cause the error. Irrespective of how you subscribe, when you subscribe anyone to a list, Core will try to send the welcome message and try to reach Postorius for template. If the URL for template is wrong, or Postorius is down for whatever reason, the subscription will fail with the error that you saw before. > I logged out of Postorious and subscribed using the subscribe form on > the info page and the change to the welcome template showed up. So it > looks like being logged in as admin while trying to subscribe someone > was what was causing the problem. Is that a bug I discovered? I suspect stopping-restarting and re-creating the template (idk, if you really did that) might have something to do with it. I am not sure if this is a bug unless you can reliably reproduce this. -- thanks, Abhilash Raj (maxking)

6 years, 6 months

Mailman-users search results for query "Postorius"