Search results for "Postorius" - Mailman-users

Re: Postorius fails to show list because of a large message being held

by Mark Sapiro

On 12/21/21 4:42 PM, dancab(a)caltech.edu wrote: > > I'm considering the settings below for gunicorn.cfg > > [gunicorn] > OK > # No of seconds to wait before killing the worker processes. > graceful_timeout = 600 I don't think this is relevant. It only affects the delay before killing a worker when gunicorn is restarted, but I suppose it won't hurt. > # Timeout for the requests. > timeout = 900 I wonder if this is really the issue. Do you have tracebacks from these timeouts? I think there may be something else causing this that increasing the timeout won't solve. Maybe some database locking deadlock or similar issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/15/23 18:35, Mark Sapiro wrote: > > $ django_admin shell > >>> from django.contrib.sites.models import Site > >>> new_site = Site(id=5, domain='5.example.com', name='display_name') > >>> new_site.save() > > Of course the values are up to you and you can omit the id= to have > Django assign the first available.. Also note that the above is a django_admin shell interaction. You can also do this in python, but you need to precede the above with ``` >>> import os >>> import sys >>> sys.path.insert(0, '/path/to/directory/containing/settings.py') >>> os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' >>> import django >>> django.setup() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

mailman import21 passwords

by Sam Darwin

Hi, On https://docs.mailman3.org/en/latest/faq-migration.html it says "Mailman 3 has a completely new account management system, none of the passwords from Mailman 2 will work with Mailman 3. Each user needs to sign up in Postorius for a new account to manage their memberships on all lists on a single instance." "Each user needs to sign up in Postorius for a new account" I am (personally) satisfied with this answer. However others at the company are asking for a detailed explanation. Consider that - - Mailman2 has access to password information. - Import scripts such as "import21" are able to import list information. - It seems that scripts such as "import21" could also generate new user accounts and passwords based on the previous ones. Why can't passwords be imported from mailman2 to mailman3? How difficult would it be to do? (is there a link to where this is already explained? ) Thanks

1 year, 1 month

Re: Hiding the "subscribe without creating an account"

by Matthew Blissett

On 13/07/2024 07:17, Mark Sapiro wrote: > On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: >> >> Is there a configuration option that does this, or was it a custom >> change made in >> the templates? Was the change made to reduce fake registrations? Did >> it work? > > > It was added in Postorius 1.3.9. See the UI section at > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 > > Yes, the change was made in an attempt to reduce fake registrations. > > We haven't really studied it's effectiveness. It seems to help > somewhat, but it also seems that bots may already have a template to > POST so removing it from the UI is not a complete solution. They would be missing the CSRF token (a hidden field on the anonymous signup form) so this ought to fail. > There is also a lot of email to innocent third parties and > non-existent addresses from attempts to register them for an account. There are patches to integrate a Captcha system here: https://gitlab.com/mailman/django-mailman3/-/issues/33 I think it's needed, as less than 24 hours after migrating to Mailman 3 I already see bots retrieving the signup form to get the CSRF token (GET /accounts/signup/?next=/postorius/lists/) then POSTing the request for a new user account (POST /accounts/signup/). There's also the setting ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False, which prevents spam from the "forgot password" address, see https://gitlab.com/mailman/postorius/-/issues/591 -- Matt

1 year, 3 months

Re: Timeout in Postorius when trying to approve or reject moderated messages

by Mark Sapiro

On 8/27/20 8:07 AM, Sebastian Hagedorn wrote: > > Right now everything is running as root (except for Apache). I realized > too late that I should've used a mailman user. Could that be the reason > for the issue? Since you have determined it was a browser issue, that probably isn't the reason, but running Mailman as root is a bad idea in general for security reasons. I don't know if it's relevant or not, but I have just recently had issues with Firefox not working properly on two different (not mailman) web sites, and these issues were fixed by clearing cookies and cached data from the affected sites and restarting Firefox. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/9/24 6:11 PM, adam.heathcote(a)utas.edu.au wrote: > > mailman members -R owner your_list(a)your.domain > > Shows myself as an owner as well as the imported owners from the previous list. You originally wrote: "but now when clicking on the list, Postorius shows: An error occurred while processing your request." I'm guessing you are clicking the list in the Postorius `Mailing Lists` view, i.e. something like https://example.com/mailman3/ or https://example.com/mailman3/lists, and you are logged in, and the link is to https://example.com/mailman3/lists/listname.example.com. What if you go to that page without being logged in, or logged in as a different user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Re: More Mailman releases!

by Mark Sapiro

On 10/24/23 6:12 AM, Wikinaut wrote: > After installing the last program to be updated (mailman-web), the archives become unavailable due to (again) some glitches with the urls. > I did not(!) change the /etc/mailman3/ configuration files. > > before upgrade, example.com/mailman3/lists/mylist.mydomain (=> worked) > after upgrade, example.com/postorius/lists/mylist.mydomain failed Did example.com/postorius/lists/mylist.mydomain work before the upgrade? Does example.com/mailman3/lists/mylist.mydomain work after upgrade? > Why and who changed my settings? The latest mailman-web upgrade added entries to urls.py. mailman-web<0.0.8 would recognize only the /mailman3/ and /archives/ urls. mailman-web=0.0.8 still recognizes those and now also recognizes /postorius/ and /hyperkitty/ urls. If /postorius/ and /hyperkitty/ urls are not working for you now, the issue is probably in your web server configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Stefan Bauer

To comment my own text, as my typo let it look rude. I meant: I solved it by myself, just by thinking about it for a while again. Stefan Am Mo., 25. Okt. 2021 um 18:06 Uhr schrieb Stefan Bauer <cubewerk(a)gmail.com >: > So i fixed it by myself, just think about it again. > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > Note the trailing slash at the end. > After removing it, the webinterface is up again. > But i have no idea, why this is NOW a problem and was not in the past. > Maybe something has changed in the way, apache is handling this now. > > Anyway, problem solved for me. > > Am Mo., 25. Okt. 2021 um 10:45 Uhr schrieb Stefan Bauer < > cubewerk(a)gmail.com>: > >> Dear Users, >> >> I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the >> web-interface via >> >> https://my.mailinglistserver.local/mailman3/postorius/lists/ >> >> I receive >> >> Not Found: /mailman//postorius/lists/ >> [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} >> [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 >> bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core >> 1) >> >> Where does the wrong path come from (mailman vs. mailman3) >> >> After enabling Debug, i see in the browser the following: >> >> >> Page not found (404) >> Request Method: GET >> Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/ >> >> Using the URLconf defined in urls, Django tried these URL patterns, in >> this order: >> >> ^$ >> ^postorius/ >> ^hyperkitty/ >> ^user-profile/delete$ [name='mm_user_account_delete'] >> ^user-profile/$ [name='mm_user_profile'] >> ^accounts/ >> ^admin/ >> >> The current path, /postorius/lists/, didn't match any of these. >> >> You're seeing this error because you have DEBUG = True in your Django >> settings file. Change that to False, and Django will display a standard 404 >> page. >> >> My apache configuration is very simply: >> >> # more /etc/apache2/conf-enabled/mailman3.conf >> Alias /mailman3/favicon.ico >> /var/lib/mailman3/web/static/postorius/img/favicon.ico >> Alias /mailman3/static /var/lib/mailman3/web/static >> >> <Directory "/var/lib/mailman3/web/static"> >> Require all granted >> </Directory> >> >> <IfModule mod_proxy_uwsgi.c> >> ProxyPass /mailman3/favicon.ico ! >> ProxyPass /mailman3/static ! >> ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ >> </IfModule> >> >> I dont see where the path gets traversed in the wrong way. Any help is >> greatly appreciated. >> >> thank you. >> >> Stefan >> >

3 years, 11 months

Re: Upgrading other python packages than the mailman ones in a venv results in dependency conflicts

by Andreas Vetter

On Montag, 16. Dezember 2024 11:52:25 CET Odhiambo Washington via Mailman- users wrote: > On Mon, Dec 16, 2024 at 1:39 PM Ulf R. <ulf.rapphahn(a)offis.de> wrote: > > > > Hello, > > I know this should be the way to upgrade: > > https://docs.mailman3.org/en/latest/upgrade-guide.html > > I have 3.3.10 installed. > > I saw that some python packages are outdated an tried this which install > > all outdated packages in a row: > > pip list --outdated --format=json | jq '.[].name' | xargs -n1 pip install > > -U > > One outdated package was django and this part happened: > > ------------------------------- > > vDownloading Django-5.1.4-py3-none-any.whl (8.3 MB) > > Installing collected packages: Django > > > > Attempting uninstall: Django > > > > Found existing installation: Django 4.2.16 > > Uninstalling Django-4.2.16: > > > > Successfully uninstalled Django-4.2.16 > > > > ERROR: pip's dependency resolver does not currently take into account all > > the packages that are installed. This behaviour is the source of the > > following dependency conflicts. > > hyperkitty 1.3.12 requires django<5.1,>=4.2, but you have django 5.1.4 > > which is incompatible. > > mailman-web 0.0.9 requires django<4.3,>=4.0, but you have django 5.1.4 > > which is incompatible. > > postorius 1.3.13 requires django<5.1,>=4.2, but you have django 5.1.4 > > which is incompatible. > > django-mailman3 1.3.15 requires django<5.1,>=4.2, but you have django > > 5.1.4 which is incompatible. > > Successfully installed Django-5.1.4 > > ------------------------------- > > > > So I made a roll back. > > > > Is this really the only secure way to update the venv?: > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web > > Correct! > > > May be yes and I have to ignore the rest? ;-) > > Yes. Let them pull their own versions of dependencies. OK. So what about --upgrade-strategy eager: pip install -U --upgrade-strategy eager mailman postorius django-mailman3 hyperkitty mailman-web Is that allowed/supported? > -- > Best regards, > Odhiambo WASHINGTON, -- Mit freundlichen Gruessen, Andreas Vetter

10 months

Re: Removing banned emails

by Mark Sapiro

On 08/02/2018 11:47 AM, Kaleb White wrote: > I am trying to remove a banned email with a special character via the rest api and it's not working. It's also not working via the UI. Any ideas? > http://localhost:8001/3.0/lists/example.com/bans/provisor#41@bankofamerica.… > <Response [404]> You can't do it from Postorius (This should be considered a bug in Postorius or perhaps mailman-client). You can do it via rest if you URL encode the request as http://localhost:8001/3.0/lists/example.com/bans/provisor%2341@bankofameric… The issue is whatever client is making the HTTP request is considering '#41(a)bankofamerica.com' to be a fragment identifier so it issues the request for the resource '3.0/lists/example.com/bans/provisor' and expects to find sub-resource identified by '41(a)bankofamerica.com' in the response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

Mailman-users search results for query "Postorius"