Search results for "Postorius" - Mailman-users

Re: Postorius upgrade issue

by Joel Lord

So I tried to do this after upgrading, fortunately only from 1 point release back, and I get "ModuleNotFoundError: No module named 'paintstore'" from the collectstatic. Haven't tried to get past that point, and haven't really had the time to chase this down myself. It seems like that's referring to a requirement from several versions back, but this venv was built clean only 2 months ago so it strikes me as odd. On 2/8/2021 6:18 PM, Mark Sapiro wrote: > I neglected to mention `migrate`. All 4 Django management commands, `collectstatic`, > `compress`, `compilemessages` and `migrate` should be run after any upgrade. > _______________________________________________ > 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/ > -- Joel Lord

4 years, 5 months

Re: Apache shows No Lists

by Mark Sapiro

On 5/21/23 15:15, ceo(a)sartrack.nz wrote: > Running Debian 11. > > I have 6 mailing lists, but Apache2 says there are no lists. > I have not been able to set up Postorius because nowhere is any information on *where* the configuration file is supposed to be located. If Postorius is not running, what is Apache looking at? > I have found an example in > /usr/share/doc/python3-django-hyperkitty/examples/settings.py > > But I don't know if this example is the right one, and I have no idea where the final file should go... Please follow the doc at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. This is our current recommendation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

High Server Load problem

by Brian Carpenter

For about a week now, I am seeing very high server loads and it seems to have something to do with the following process hanging: uwsgi --ini /opt/mailman-web/uwsgi.ini I am using the docker version of Mailman. When this process hangs, the server load just goes sky high and both Postorius and Hyperkitty no longer responds. I don't have very many sites on this server and I am running about 30 lists. I really need some assistance here as this needs to be fixed. I am seeing nothing in the logs that is explaining why this process is hanging and why the server load goes through the roof. Running docker-compose restart mailman-web kills the hanged process and the server load goes down. Postorius and Hyperkitty starts responding again. This seems to happen once a day. Brian

5 years, 9 months

Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 6/2/21 18:08, Abhilash Raj wrote: > > On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I restarted de server and the error changed. Now the log shows >> "KeyError: 'subscription_mode'": > Did you also restart Mailman Core after the upgrade? Yes, indeed: I stopped mailman core and all the processes related. Did the upgrades. Started all again. Find the errors in the web user interface. Stopped all again. Looked for errors in the log. Restarted the complete server. Found the second error that this second mail is about to. It happens when, in the main page that shows all the lists you click to see one of them. It seems to me that it has been database structure changes in django that the upgrade is not aware... but it's a very long shot from my side. I'm using sqlite as django database and mysql for mailman. > >> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server >> Error: /mailman3/mailman3/lists/name_and_domain.of.the.list >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ >> return self._get(name) >> File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get >> raise KeyError(key) >> KeyError: 'subscription_mode' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >> line 34, in inner >> response = get_response(request) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 115, in _get_response >> response = self.process_exception_by_middleware(e, request) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 113, in _get_response >> response = wrapped_callback(request, *callback_args, **callback_kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 71, in view >> return self.dispatch(request, *args, **kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >> line 74, in dispatch >> return super(MailingListView, self).dispatch(request, *args, **kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 97, in dispatch >> return handler(request, *args, **kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line >> 295, in get >> member.subscription_mode == >> File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 124, in __getattr__ >> self.__class__.__name__, name)) >> AttributeError: 'Member' object has no attribute 'subscription_mode' >> *********************** >> some info about the installed versions via pip list: >> pip list | grep django >> django-allauth 0.44.0 >> django-appconf 1.0.4 >> django-compressor 2.4 >> django-extensions 3.1.0 >> django-gravatar2 1.4.4 >> django-haystack 3.0 >> django-mailman3 1.3.5 >> django-picklefield 3.0.1 >> django-q 1.3.4 >> djangorestframework 3.12.2 >> >> pip list | grep mailman >> django-mailman3 1.3.5 >> mailman 3.3.3 >> mailman-hyperkitty 1.1.0 >> mailmanclient 3.3.2 >> >> pip list | grep postorius >> postorius 1.3.4 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >>> I've just upgrade mailman 3 installation following Mr. Sapiro advice: >>> did a >>> >>> pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient >>> mailman-hyperkitty postorius >>> >>> I did a "python3 manage.py migrate" after, too. >>> >>> And all seemed to run well. >>> >>> All the lists showed in postorius via web, but when I try to accesss >>> into one of them the browser shows an error. >>> >>> In the log you can see: >>> >>> *-*-*-*-*-*-* >>> >>> Traceback (most recent call last): >>> File >>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>> line 119, in __getattr__ >>> return self._get(name) >>> File >>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>> line 86, in _get >>> raise KeyError(key) >>> KeyError: 'get_requests_count' >>> >>> ... (And after all the traceback lines) >>> >>> AttributeError: 'MailingList' object has no attribute >>> 'get_requests_count' >>> >>> *-*-*-*-*-*-*-* >>> >>> The lists seem to be distributing messeages well.. but I cannot acces >>> via web administration (django/postorius) >>> >>> Can anyone point me in the right direction to solve this, please? >>> >>> _______________________________________________ >>> 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/ >>> >> _______________________________________________ >> 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/ >>

4 years, 5 months

Re: add custom styles to postorius list creation menu

by Mark Sapiro

On 5/3/22 04:53, mhazan(a)mandint.org wrote: > > working on that plugin, i have found where to inserts the various > setting, however it's not clear what types and possibles value are > excepted for each ? ie "advertised" is bool True/false, but what about > "default_member_action" ? i've tried hold 'hold' "hold" all throw error > when trying to apply the style. from mailman.interfaces.action import Action mlist.default_member_action = Action.hold > i cannot find the types in the > documentation and all the other non bool settings. Look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py for an example. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stephen J. Turnbull

Stefan Bauer writes: > No matter what i try, mailman still only connects without STARTTLS: Earlier you wrote: > SMTPSenderRefused at /accounts/login/(530, b'5.7.0 Must issue a STARTTLS command first', 'postorius(a)lists.mydomain.tld') > Request Method: POST > Request URL: https://mm3.mydomain.tld/mailman3/accounts/login/ > Django Version: 2.2.12 This looks like Django errors, not Postorius (Mailman). So this is something Django is doing, not Mailman (including Postorius). I'm not sure why Django is sending email (somebody made a password reset request seems likely, but I'm not that familiar with Django authn stuff). Anyway, if it's internal to Django, it would not consult Mailman's configs. This recent StackOverflow seems relevant: https://stackoverflow.com/questions/60025730/530-5-7-0-must-issue-a-starttl… HTH Steve

3 years, 8 months

Re: Template Ignored?

by Stephen Daniel

Thanks for clarifying. All is working now!!! On Thu, Feb 17, 2022 at 1:27 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/17/22 10:10, Stephen Daniel wrote: > > Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. > > I've been playing with wget, and no matter what I put, I keep getting a > 404 > > error. > > > > So: this works: > > > > wget -O wget.out --user restadmin --password restpass ' > > http://localhost:8001/3.1/lists/list.example.com' > > > > but this does not (404 error): > > > > wget -O wget.out --user restadmin --password restpass ' > > > http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… > > > You are using Mailman core's REST API which is wrong. You need to get > the template from Postorius. Maybe something like > > > > http://localhost/postorius/api/templates/list/list.example.com/list:user:no… > > Where http://localhost/postorius/ is the URL you use to access > Postorius, maybe mailman3 instead of postorius. > > Once you figure that out, POSTORIUS_TEMPLATE_BASE_URL is just the scheme > and domain part of that. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ >

3 years, 5 months

Re: Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > > My point was after you remove the newly minted mailmandb database and > then create a new blank one, and import into that, you should then run > manage.py migrate to apply any new migrations to the imported database. Ah, right ... ok, I've done that now, and all's good. Actually, I've noticed something related. It looks like the mailman-web container runs manage.py as part of its startup procedure in any event. After the import completes, I start up the mailman-web container and, its logs say this: mailman-web | Operations to perform: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Applying auth.0012_alter_user_first_name_max_length... OK mailman-web | Applying django_q.0014_schedule_cluster... OK mailman-web | Applying hyperkitty.0022_mailinglist_archive_rendering_mode... OK mailman-web | Applying postorius.0014_auto_20210329_2248... OK mailman-web | Applying postorius.0015_auto_20210619_0509... OK mailman-web | Applying postorius.0016_auto_20210810_2157... OK If the container is restarted again, it shows that there's nothing to do this time: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | No migrations to apply. These latter diagnostics are also what I see if, at this point, I enter the mailman-web container and run "manage.py migrate" explicitly. I really appreciate the help, thanks so much.

3 years

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Mark Sapiro

On 5/13/16 5:05 PM, Simon Hanna wrote: > On 05/12/2016 09:26 PM, Barry Warsaw wrote: >> On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >> >>> It is the intent that Postorius will eventually expose all these >>> settings. We're not there yet. At present you could possibly do this by >>> interacting with mailmanclient, although I'm not certain the settings are >>> exposed there. >> >> I'm not sure if they're exposed in mailmanclient, but they are exposed in the >> core's REST API, on the member resource. It's the `delivery_mode` attribute >> and it takes as legal values one of 'regular', 'plaintext_digests', >> 'mime_digests', and 'summary_digests' (IOW, the enum item names for the >> DeliveryMode enum). > They are exposed in mailmanclient and are used in postorius. They can be > found in the users personal subscription settings > https://lists.mailman3.org/mailman3/accounts/mailmansettings/ You are correct. When I checked this before my initial reply, I never pulled down the Delivery Mode list to see all the options. My bad. However, please correct me if I'm wrong, but there does not appear to be a way in Postorius to set a list's mime_is_default_digest attribute. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

Re: Welcome message template errors

by Mark

On 2024-04-22 14:07, Mark Sapiro wrote: > I think you must be setting the custom template via Postorius and > your Django setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. It > should be set to the scheme and host you use to access Postorius. I.e, > if you normally access Postorius via something like > https://example.com/mailman3 set > > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' > > It is probably now set as > > POSTORIUS_TEMPLATE_BASE_URL = 'http://<REDACTED-PUBLIC-IPv4-ADDRESS>' ================================================================================ There was no line POSTORIUS_TEMPLATE_BASE_URL in /etc/mailman3/settings.py So I've now added the line: POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mydomain.com' Checked in settings.py that: - "lists.mydomain.com" is in ALLOWED_HOSTS; and - "https://lists.mydomain.com" is in CSRF_TRUSTED_ORIGINS Restarted everything... rm /opt/mailman/mm/var/locks/* systemctl restart mailman3 systemctl restart mailmanweb systemctl daemon-reload systemctl restart qcluster # pstree systemd─┬─ ├─gunicorn───gunicorn ├─mailman-web───mailman-web───4*[mailman-web] ├─nginx───2*[nginx] ├─postgres───18*[postgres] ├─python3─┬─11*[python3] │ ├─python3───{python3} │ └─python3───2*[python3] I deleted the custom Welcome template via the WebUI (Postorius), and checked it was removed from the database (PostGres mailman.template). Then, as site-owner, creating a new custom Welcome template (again via the WebUI) I can see it correctly added to the database in mailman.template.uri - https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… Previously it was writing ... - http://localhost:8000/mailman3/api/templates/list/lists.mydomain.com/list:u… So far so good. Nothing showing in mailmanweb.log yet. Then, still as site-owner using Postorius, I mass-subscribed a new member (pre confirm, pre approve, pre verify all ticked). The error below displays on the webpage, the member is subscribed, but no custom welcome message emailed out. =================================== HTTP Error 400: HTTPSConnectionPool(host='lists.mydomain.com', port=443): Read timed out. (read timeout=5) =================================== And the syslog shows a ton of issues, starting with: =================================== 2024-04-22T23:39:27.536002+00:00 lists mailman[1317]: Apr 22 23:39:27 2024 (1317) HTTPSConnectionPool(host='<LISTS.MYDOMAIN.COM>', port=443): Read timed out. (read timeout=5) 2024-04-22T23:39:27.537648+00:00 lists mailman[1317]: Traceback (most recent call last): 2024-04-22T23:39:27.537681+00:00 lists mailman[1317]: File "/opt/mailman/venv/lib/python3.11/site-packages/urllib3/connectionpool.py", line 536, in _make_request 2024-04-22T23:39:27.537700+00:00 lists mailman[1317]: response = conn.getresponse() 2024-04-22T23:39:27.537717+00:00 lists mailman[1317]: ^^^^^^^^^^^^^^^^^^ 2024-04-22T23:39:27.537740+00:00 lists mailman[1317]: File "/opt/mailman/venv/lib/python3.11/site-packages/urllib3/connection.py", line 461, in getresponse 2024-04-22T23:39:27.537757+00:00 lists mailman[1317]: httplib_response = super().getresponse() 2024-04-22T23:39:27.537772+00:00 lists mailman[1317]: ^^^^^^^^^^^^^^^^^^^^^ 2024-04-22T23:39:27.537790+00:00 lists mailman[1317]: File "/usr/lib/python3.11/http/client.py", line 1374, in getresponse =================================== I removed the custom welcome message and the newly subscribed members. The default "You've been unsubscribed" notice got emailed out okay. Then mass subscribing a member, the default welcome message gets emailed out okay and no error displayed on the webpage. I have no idea what the report in syslog is saying, or where to look next. Any help appreciated.

1 year, 3 months

Mailman-users search results for query "Postorius"