Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

On 10/16/21 9:52 AM, Christian Stalberg via Mailman-users wrote: > When I go to https://.../admin/ I get a Django Administration screen and in > the upper right hand corner I see > > WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT And my point was if you go to Users under Authentication and Authorization you should find that alekos.pantazis is a user. If you go to your own https://www.grizz.org/user-profile/ page, do you see a gravatar to the right of the Username, First name, Last name boxes, and does going there produce the same error in the logs. If that's all OK, then I don't know what produced the original error, but I think you can ignore it. If that produces the same error in the logs, then something is wrong with your django-mailman3 installation, but I don't know what. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/20/22 14:50, Dan Caballero wrote: > > 2022-09-20 14:44:17 [FALCON] [ERROR] GET /3.1/lists/jewishlife(a)caltech.edu/held?count=10&page=1 => Traceback (most recent call last): > File "falcon/app.py", line 365, in falcon.app.App.__call__ > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 182, in on_get > resource = self._make_collection(request) > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in _make_collection > entries = [as_dict(resource) for resource in collection] > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> > entries = [as_dict(resource) for resource in collection] > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 173, in _resource_as_dict > assert resource is not None, resource > AssertionError: None This is most likely a race condition between two browsers, one of which handles the held message while the other is getting the held messages. Check Mailman's access.log entries with time stamps around 2022-09-20 14:44:17. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 13:15, Wikinaut wrote: > > However myserver/mailman3 page is throwing > > Erfolgreich als Admin angemeldet. > Something went wrong >>>> HTTP Error 401: REST API authorization failed > > Even when the API keys are unchanged from my previous installation. Any idea what can be wrong here? what does the command `mailman info` show for REST credentials? The defaults for these are REST credentials: restadmin:restpass set by admin_user: restadmin admin_pass: restpass in the [webservice] section of mailman.cfg and the corresponding defaults for Django settings are: MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' If you have something different, is it set in both mailman.cfg and settings.py? Is there more information in /opt/mailman/mm/var/logs/mailman.log or /opt/mailman/web/logs/mailmanweb.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Immediate notification to the administrator

by Mark Sapiro

On 11/2/23 07:48, Stephen J. Turnbull wrote: > > Until then, here's the crontab template distributed with Mailman 3.2.2: > > # At 8AM every day, mail reminders to admins as to pending requests. > 0 8 * * * @PYTHON@ -S @prefix@/cron/checkdbs > # > # At 9AM, send notifications to disabled members > 0 9 * * * @PYTHON@ -S @prefix@/cron/disabled > # > # Noon, mail digests for lists that do periodic delivery. > 0 12 * * * @PYTHON@ -S @prefix@/cron/senddigests > # > # Every 5 mins, try to gate news to mail. > */5 * * * * @PYTHON@ -S @prefix@/cron/gate_news > # > # At 3:27am every night, regenerate the gzip'd archive file. Only > # turn this on if the internal archiver is used and > # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py > 27 3 * * * @PYTHON@ -S @prefix@/cron/nightly_gzip This Mailman 3.2.2 cron/crontab.in.in file is is an artifact from Mailman 2.1. Nothing there is relevant to any Mailman 3 version -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by Mark Sapiro

On 11/9/24 05:32, ulf.rapphahn(a)offis.de wrote: > Hello, > I have the lasted version of mailman3 in an fresh venv installation and I am testing it for our upcoming migration from v2.1. > > When I add a new list in the django admin interface this list will never appear in postorius (vice versa it works). Because the mailing lists in the Django admin interface are HyperKitty Lists, not Mailman lists. When you create a list in Postorius or Mailman core, this is a Mailman list. A corresponding HyperKitty list will also be created if hyperkitty is one of the active archivers for the list so you see it in Django. When you create a list in Django, it is only a HyperKitty list and will be visible in HyperKitty, but no Mailman list is created so the list is not in Mailman/Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Mark Sapiro

On 10/24/23 3:56 PM, Thomas Ward via Mailman-users wrote: > > When I DO NOT have the module loaded in the configuration, `mailman > shell` works. Since that was functional, I went into the shell and > executed this: > > > from mailman_customizations.hooks import MailmanCustomizations > > This worked fine, but obviously importing the class doesn't necessarily > *activate* the class. So something is up with how I'm *supposed* to > activate the plugin in the config, and we know that it's visible to > Mailman in its shell, but it can't autoload it. I'm past the limit of my knowledge here and only stabbing in the dark, but what happens after you import it. Can you instantiate it, e.g. ``` instance = MailmanCustomizations() dir(instance) ``` I'm not saying this should succeed, just that it may possibly provide useful information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Show number of subscribers

by Mark Sapiro

On 6/28/19 3:19 AM, andrew.bernard(a)gmail.com wrote: > Would there be a way to show the number of subscribers to a list in the web UI? > > The number of participants per message is great, but this would be good too. My users seem very interested in this number. I guess they want to know how big the audience is that is reading their posts. I don't know how difficult it would be to add this to HyperKitty, and I'm not sure how useful it would be in general. HyperKitty is an archiver. It deals with archiving posts. It knows who has sent a post, but doesn't know or care if that person is, was or will be a member of the list. Postorius knows who the list members are and this information should be available to list members or the world depending on the list's member_roster_visibility setting, but see <https://gitlab.com/mailman/postorius/issues/369>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Cannot show archives

by Mark Sapiro

On 9/26/19 5:48 PM, Qiuhong.Su 蘇秋紅 wrote: > Hi all, > > After I setup mailman3 and run mailman-suite, I can do: > > 1. Register user > > 2. Login > > 3. Create new Domain > > 4. Create new List > > 5. Subscribe to the list > When I try to send email to the list by run command: echo “test email” | mail –s “test email” test(a)example.com > User test can receive this email, but I cannot find it on Archives, and other members cannot receive this email too. You say "User test can receive this email". Is test(a)example.com a user or the list's posting address? If you are saying that test(a)example.com should be the list's posting address, but the mail is instead delivered to the user test(a)example.com, you have not set up your MTA to properly deliver list mail to Mailman. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html>. -- 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

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Mark Sapiro

On 9/29/21 9:50 AM, Odhiambo Washington wrote: > 1. Confirmation emails to Users has wrong domain name (example.com!) > <https://docs.mailman3.org/en/latest/faq.html#id1> > <https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h…> > > This happens when your reverse (SSL) proxy isn’t setting up the correct > headers when proxying requests. Fix this by setting the right > proxy_set_header directives: ... > How is this supposed to be mitigated in Apache when using WSGI? > > My config: > > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > user=mailman group=mailman > WSGIPythonHome "/usr/local" > WSGIProcessGroup hyperkitty You are using mod_wsgi and not proxying at all, so this is not relevant in your case. Are you actually seeing this issue? If so, it might be related to https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… -- 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

[MM3-users] Re: Apache Configuration for Subdomain

by Mark Sapiro

On 7/26/22 14:20, Mail Person wrote: > Ok, progress with tinkering some. Using the below configuration I can manually navigate to lists.example.com/mailman3/postorius/lists/ and all is working fine. If I go to lists.example.com/mailman3 it for some reason redirects to lists.example.com/mailman/postorius/lists/ which generates a 404. This is a uWSGI issue. > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost Others have found that changing this to ``` ProxyPass /mailman3/ unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ``` fixes it. Note the added slashes after `mailman3` and `localhost`. See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Going to lists.example.com also hits a 404. Here > RewriteEngine on > RewriteCond %{SERVER_NAME} =lists.example.com [OR] > RewriteCond %{SERVER_NAME} =www.lists.example.com > RewriteRule ^ https://%%7BSERVER_NAME%7D%%7BREQUEST_URI%7D [END,NE,R=permanent] You're redirecting http to https, but have you defined a VirtualHost for port 443? Just copy your <VirtualHost *:80> block to a <VirtualHost *:443> block. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Search results for query "sapiro"