Search results for "Postorius" - Mailman-users

Weekend releases

by Abhilash Raj

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.1 - Django-mailman3 1.3.1 - Hyperkitty 1.3.1 These are all bugfix releases and include several fixes each. The full changelogs are available at: - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) Most notable fixes include a fix for PostgeSQL support in Hyperkitty, ability to delete a MailingList in Hyperkitty and list settings changes are immediately reflected in Hyperkitty (like making a List private). It also includes support for Python 3.8 and Django 3.0 in Postorius and Django-maialman3. Hyperkitty doesn't yet support either of them due to some dependencies not yet supporting Django 3.0 and a bug in Python 3.8.0 causing a test case failure[1]. I hope that we are able to support the latest and greatest as soon as possible, I am excited to be able to play with Django's aync capabilities. Finally, since our i18n workflow has been setup, we have lots of new translations coming in. This release also includes more parts of Postorius being translatable, including section headers. I am really happy to see Mailman 3 move closer to Mailman 2 in terms of i18n. If you want to help us improve the coverage, head on to Weblate[2]. All the releases are available on PyPI, as usual! [1] Fun Fact: The bug was due to a code that I contributed ;-). It is now fixed and will be soon out with Python 3.8.1 sometime this month. [2] https://hosted.weblate.org/projects/gnu-mailman/ -- thanks, Abhilash Raj (maxking)

6 years, 9 months

Re: Unwanted E-mail to Maillists Submitted via Postorius Interface

by matthew＠alberti.us

Steve, Thanks for the response. I put " HYPERKITTY_ALLOW_WEB_POSTING = False " in and that has worked as intended. Sorry I wasn't more clear in my previous e-mail. I was trying to say that Django-recaptcha might be a good way to gate the signups, but it looked like mailman code would have to be changed to work with djangi-recaptcha. But it seems not effective enough to be worth pursuing. For now, maybe disabling posting via hyperkitty will be enough. Any SPAM sent in from other sources will be subject to scanning. - Matt Alberti -----Original Message----- From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Thursday, August 26, 2021 1:36 PM To: matthew(a)alberti.us Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Unwanted E-mail to Maillists Submitted via Postorius Interface matthew(a)alberti.us writes: > I’ve seen a recent uptick in SPAM messages making it into > mailing lists. Looking at the raw, it seems that the e-mails are > being submitted thru the Postorius/Hyperkitty “Start a New Thread” > interface. Is there a way to turn that off? I think this is HyperKitty only. Postorius doesn't know anything about posting or distributing posts. You can disable web posting by setting HYPERKITTY_ALLOW_WEB_POSTING = False (as above, no quotation marks etc) in settings.py. I don't know much about HyperKitty, so I'm not sure where that file lives in your installation. > Part of the problem is that our anti-spam system RSPAMD trusts the > mailman-web IP… so it doesn’t scan things originating from > there.. %G 笘ケ%@ You know your organizational constraints, but it's a bad idea to trust any web-facing application that can send email to be responsible about it. :-( > Another uestion: Is there a way to implement captcha, or is > there a recommended gate that can be put in the signup process? Here's the most recent technical discussion I can find. Archived-At: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message /RSZLMKPASCTKFY63RKGPGNCVVPAB5C4M/> However, it turns out that bots are almost as good at solving captchas as humans, and they can retry a lot faster. Captchas are also really horrible from an accessibility perspective. > Apparently bots are finding a way thru the signup process, and then > sending messages to the list via the Postorius web interface. There > seems to be a Django plugin for it; but it appears the Mailman code > would have to be adjusted to implement it. I don't think so, because Mailman (that is, HyperKitty and Postorius) delegate authentication to Django. Why do you think Mailman code needs to be adjusted? Steve

5 years

Mailman upgrade results in page not found error

by Andrew Hodgson

Hi. Just doing the Mailman suite upgrade on my small installation I use for test purposes. Steps include: Run backup script Stop services Mv venv venv-old python3 -m venv --system-site-packages --symlinks venv source venv/bin/activate pip install -U pip pip install mailman mailman-hyperkitty hyperkitty postorius whoosh deactivate ./bin/Django-admin collectstatic ./bin/Django-admin migrate At this step I got an error regarding the import of URLs, a quick Google suggested this was because the new venv has upgraded to Django 4.0. I downloaded the urls.py from the mailman-web Git repo (I should migrate to this at some point I know) and replaced my version with this one. This allowed the migrate to run correctly. Once services were up everything worked as expected except for the web page. If you go to https://lists.hodgsonfamily.org you get a Postorius page not found error, however if you click on the Mailman logo you get to the correct place. I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of having https://lists.hodgsonfamily.org going to the correct place? Urls.py: # -*- coding: utf-8 -*- # Copyright (C) 1998-2016 by the Free Software Foundation, Inc. # # This file is part of Postorius. # # Postorius is free software: you can redistribute it and/or modify it under # the terms of the GNU General Public License as published by the Free # Software Foundation, either version 3 of the License, or (at your option) # any later version. # # Postorius is distributed in the hope that it will be useful, but WITHOUT # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for # more details. # # You should have received a copy of the GNU General Public License along with # Postorius. If not, see http://www.gnu.org/licenses/. from django.conf.urls import include from django.contrib import admin from django.urls import path, reverse_lazy from django.views.generic import RedirectView urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), path('admin/', admin.site.urls), ] Thanks. Andrew.

3 years, 10 months

Re: Auth question

by Mark Sapiro

On 03/29/2017 03:46 PM, Barry Warsaw wrote: > On Mar 30, 2017, at 12:34 AM, David Krantz wrote: > >> When starting this as the recipe seems reasonable I find that I have >> no reliable source for git links for the parts. Some of the git links >> I find are marked with "do not use" so it is a bit hard having >> confidence in selecting one of the others. > > All the Mailman 3 suite subprojects are listed here: > > https://gitlab.com/mailman > > Those project links will take you to the active git repositories. The only > one you should not use is mailman-bundler. To be more specific, the projects that are required for a fully functioning Mailman installation with Postorius and Hyperkitty are Mailman (the core) Hyperkitty (the archiver) Postorius (the web list management UI) django-mailman3 (common django things used by Postorius and Hyperkitty) MailmanClient (python bindings for the core REST API used by Postorius and Hyperkitty) HyperKitty - Mailman plugin (plugin for the core to communicate with Hyperkitty) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 5 months

Unwanted E-mail to Maillists Submitted via Postorius Interface

by Stephen J. Turnbull

matthew(a)alberti.us writes: > I$B!G(Bve seen a recent uptick in SPAM messages making it into > mailing lists. Looking at the raw, it seems that the e-mails are > being submitted thru the Postorius/Hyperkitty $B!H(BStart a New Thread$B!I(B > interface. Is there a way to turn that off? I think this is HyperKitty only. Postorius doesn't know anything about posting or distributing posts. You can disable web posting by setting HYPERKITTY_ALLOW_WEB_POSTING = False (as above, no quotation marks etc) in settings.py. I don't know much about HyperKitty, so I'm not sure where that file lives in your installation. > Part of the problem is that our anti-spam system RSPAMD trusts the > mailman-web IP$B!D(B so it doesn$B!G(Bt scan things originating from > there.. %G��%@ You know your organizational constraints, but it's a bad idea to trust any web-facing application that can send email to be responsible about it. :-( > Another uestion: Is there a way to implement captcha, or is > there a recommended gate that can be put in the signup process? Here's the most recent technical discussion I can find. Archived-At: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> However, it turns out that bots are almost as good at solving captchas as humans, and they can retry a lot faster. Captchas are also really horrible from an accessibility perspective. > Apparently bots are finding a way thru the signup process, and then > sending messages to the list via the Postorius web interface. There > seems to be a Django plugin for it; but it appears the Mailman code > would have to be adjusted to implement it. I don't think so, because Mailman (that is, HyperKitty and Postorius) delegate authentication to Django. Why do you think Mailman code needs to be adjusted? Steve

5 years

Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

In the OpenDev Collaboratory we've got a bunch of separate Mailman 2.1 vhosts we've started migrating into a single Mailman 3.3.7 server, desiring to take full advantage of its improved multi-domain support. For the most part everything is working great (kudos to everyone who maintains the software and documentation, it's excellent). One of the things our users noticed fairly quickly was Hyperkitty on the second vhost was incorrectly showing the FQDN of the first vhost near the top of its pages. This is covered in the FAQ of course, and seems to imply that what we want is to switch the SITE_ID from 1 to 0 in our settings.py in order to take advantage of magic domain-guessing behavior. So far so good. Unfortunately, SITE_ID = 0 seems to explicitly require the addition of "mail hosts" (or "mail domains" from Django's perspective), and all the web routing returns error pages for any list sites besides the first one since, by default, our server did not have these predefined. What's odd is that, if I log into Postorius as admin and visit the "manage domains" page, suddenly the database gets populated with mail hosts for all of the FQDNs associated with our imported mailing lists. I would not have expected merely visiting that page as an admin to have a side effect of adding entries for the "missing" mail hosts, is that an intentional behavior or merely a bug? Once these entries are automatically added by visiting that page, they're all associated with the one "web host" ("site" in Django) we have for the server, and now the list filtering functionality in Postorius breaks and any of the vhosts all display the full set of mailing lists on the server rather than only those associated with a particular vhost (note that this seems to only be confusing Postorius, Hyperkitty has them correctly filtered still). Okay, so it looks like this is because the mail hosts are all tied to the one web host. We can create additional "sites" in the Django admin UI and then switch the association of the mail hosts to those distinct web hosts. But after doing so, the first vhost still seems to show an unfiltered list of all lists in Postorius (Hyperkitty continues to be fine), while Postorius on the other vhosts correctly shows their filtered sets of lists instead. I also noticed when mailman-web is starting up, its log claims the first site is being set as the "default domain," so have to wonder if that's related to this behavior. Should we create an extra web host to serve as the "default" so that all our typical vhosts get the expected list filtering behavior, or am I completely off-base and there's a much better approach I've missed? Sorry this is so long, I feel like I have at most a tenuous grasp of the details and variables involved, but hopefully it makes sense to someone. Thanks in advance for any recommendations or guidance. -- Jeremy Stanley

3 years, 9 months

Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Wed, Feb 27, 2019, at 12:04 PM, Danil Smirnov wrote: > Hi, > > After upgrading my PostgreSQL from 9.2 to 9.6, I was able to up postorius container. > But when I try to open UI, I'm getting 500 Internal Server Error all the time - either for /postorius/lists/ as well as for /admin/. > I've checked all the logs but haven't found anything there which can bring some light at the issue. Just error 500... > > I've checked: > - nginx logs: just error 500 > - mailman-web docker container logs: no errors > - mailman-web (postorius) logs: mailmanweb.log is empty, uwsgi*.log with some errors > - mailman-core logs: no errors > > I've also called curl localhost:8000 from inside the mailman-web container and got the same 500 Internal Server Error. > > Could you guys advise what else should I check? We would need to figure out if it is Core or Web causing the 500 errors. So, what errors are you looking at in uwsgi*.log? Do you see any successful requests in mailman core's mailman.log? > > With my best regards, > Danil > > > пт, 22 февр. 2019 г. в 09:12, Danil Smirnov <danil(a)smirnov.la>: >> Hi Abhilash, >> >> Thank you for the quick resolution, but I'm still unable t start the container: >> https://github.com/maxking/docker-mailman/issues/309 >> >> DB migrations are failing. >> >> Danil >> >> вс, 17 февр. 2019 г. в 12:21, Danil Smirnov <danil(a)smirnov.la>: >>> Hi Abhilash, >>> >>> Thank you for the explanation, I've created a report: >>> https://github.com/maxking/docker-mailman/issues/307 >>> >>> Danil >>> >>> >>> >>> сб, 16 февр. 2019 г. в 18:40, Abhilash Raj <maxking(a)asynchronous.in>: >>>> On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote: >>>> > Hi, >>>> > >>>> > I'm interesting in Mailman3 deployment with archiving feature completely >>>> > disabled. >>>> > >>>> > I've tried to deploy Core + Postorius using this docker-compose >>>> > template: >>>> > https://github.com/maxking/docker-mailman/blob/master/docker-compose-postor… >>>> > >>>> > Unfortunately Postorius version came with this template is quite outdated: >>>> > 1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker image I >>>> > see version 1.2.3. >>>> > >>>> > I've also checked image maxking/postorius:rolling but it seems >>>> > irrelevant/broken (container exits with error). >>>> > >>>> > Are there newer Postorius docker image I can use? >>>> >>>> No, but if you could report the failure and error that you, maybe the Maintainer can help >>>> fix that issue you have? >>>> >>>> P.S. I maintain those images. The Postorius image is kind of neglected since there are >>>> fewer people using it, but I'd be happy to fix any error that you see. >>>> >>>> Package ugprades are merely a version number bump in Dockerfile :) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

7 years, 6 months

Re: Postorius admin/user guide

by Mark Sapiro

On 11/8/24 02:59, Florin Pasăre via Mailman-users wrote: > Hello, > We're trying to update mailman to version 3 from version 2, and I can't > seem to find some non-technical guide for Postorius, something like an > owners manual for all the configurations available in Postorius. > Is there such a thing? No, at this time there is not. All we have at the moment is https://docs.mailman3.org/projects/postorius/en/latest/ which isn't what you're looking for. You just have to page through the settings to see what's there. Hopefully the various categories are clear enough that if you're looking for something specific, you can find it easily. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Re: URL-lines in templates get folded

by Mark Sapiro

On 10/18/22 06:52, Frank Steinberg wrote: > Hi, > > I’ve added links to some templates to give owners and moderators > shortcuts to the postorius UI for moderation tasks, e.g., I’ve added > > https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> > > Unfortunately those lines seem to exceed a certain limit and get > folded, so that they appear as, e.g. > > https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> > messages > > (or similar) and are not directly useful. How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? Also are those lines of the form https://... <https://...> what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. Is the folding actually in the raw message or is it an artifact of the mail client viewing the message? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Re: 400 Bad Request when administrator tries to selectively override member options

by Mark Sapiro

On 5/8/21 1:17 PM, ieso(a)johnwillson.com wrote: > This is probably Design Intent, but I'd just like to confirm. > > When an administrator submits partial 'member options', it comes back with the details of a 400 - Bad Request, indicating essentially that all of the member options must be set. > > Screenshot: https://ibb.co/pzM5Z4m > > It would be a bit smoother to check that all values are selected before sending the request, and inform the administrator that they cannot selectively override member settings for their list. > > But most importantly, I would like to confirm that nothing is corrupt/broken in our implementation. What Postorius version is this? I just tried it on Postorius 1.3.5b1 (The HEAD of the gitlab branch), and for a user with no options at all set at the list level, I was able to set `Receive own postings` only with no problem. I think this is https://gitlab.com/mailman/postorius/-/issues/178 fixed in Postorius 1.2.0 by https://gitlab.com/mailman/postorius/-/merge_requests/321 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Mailman-users search results for query "Postorius"