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

[MM3-users] Re: clicking on a username when viewing a thread results in "Page not found"

by Mark Sapiro

On 6/26/23 9:26 PM, Ken Alker wrote: > Mark Sapiro wrote: >> This is a problem. That link goes to, e.g., >> https://example.com/archives/users/<user_id>/. What do you get if you >> strip the user_id and just go to what >> https://example.com/archives/users/ translates to on your system? >> You should get a page saying >> Not implemented >> >> This feature has not been implemented yet, sorry. >> >> If you get a 404, there is an issue with your web server configuration >> or maybe your top level urls.py. > > I get "Not implemented". I do not get a 404 error. That indicates there is some corruption somewhere. I need to research it to figure out where, but the issue is the <user_id> in https://example.com/archives/users/<user_id>/ doesn't exist. Are the crons - https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m… running? If they are, the hyperkitty sync_mailman job should run daily and might fix this. You can also run `mailman_web mailman_sync` manually. -- 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

[MM3-users] Re: Post-installation documentation?

by Mark Sapiro

On 11/24/21 7:50 PM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > Here are the steps to migrate a 2.1 list named `alist(a)example.com` and > > its archives. > > This is documented at https://docs.list.org/en/latest/ (prominent link > in sidebar). This appears to be completely different from > https://docs.mailman3.org/ (and https://mailman.readthedocs.io/ which > I guess is just a redirect). But it looks like the sources are in the > some gitlab repo?! Both docs.list.org and docs.mailman3.org are CNAMEs the resolve ultimately to readthedocs.io. I.e. they both get to the same readthedocs pages the source for which is the https://gitlab.com/mailman/mailman-suite-doc project. https://mailman.readthedocs.io/ also goes readthedocs.io, but to the documentation for Mailman core rather than that for Mailman Suite. > > Did you specify the list's fqdn as in > > https://www.example.com/archives/list/list@example.com/ > > That's not an FQDN, though. "example.com" might be one, but that > whole thing is the URL to the archive. I meant did he go to a url like https://www.example.com/archives/list/list@example.com/ as opposed to https://www.example.com/archives/list/list/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 7:54 PM, David Newman wrote: > On 12/22/21 7:29 PM, Mark Sapiro wrote: > >> This looks like a uwsgi issue as discussed at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> although that's with apache and not nginx so it may not be. > > If I'm reading the thread correctly, it's Apache workarounds to an > underlying Debian issue, so I agree it may not apply with nginx. I think you're correct that it doesn't apply to nginx, but the symptom is not the same. It is not a Debian issue per se. It is an Apache change that got installed with a Debian update, but the underlying issue is with Apache. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > There are 260 files named 'urls.py' under /opt/mailman, mostly for > socialaccount stuff. > > Where does that change go? All files? Or just this one: > > /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py Not that one. The one whose content looks like https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py. It is probably in the same directory as your Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 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/21/23 09:58, Mark Sapiro wrote: > You can verify this by activating your > venv and doing > ``` > >>> MAILMAN_REST_API_USER > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > NameError: name 'MAILMAN_REST_API_USER' is not defined > >>> MAILMAN_REST_API_USER > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > NameError: name 'MAILMAN_REST_API_USER' is not defined > >>> MAILMAN_REST_API_PASS > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > NameError: name 'MAILMAN_REST_API_PASS' is not defined > >>> from mailman_web.settings.mailman import * > >>> MAILMAN_REST_API_USER > 'restadmin' > >>> MAILMAN_REST_API_PASS > 'restpass' > >>> > ``` Omitted in the above was invoking Python as in ``` (venv) mark@msapiro:~$ python Python 3.9.16 (main, Dec 11 2022, 12:49:23) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> MAILMAN_REST_API_USER etc, as above ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 22:30, Thomas Stein wrote: > Am 2024-04-26 00:52, schrieb Mark Sapiro: >> One thing you could try is in settings_local.py, put >> ``` >> from settings import MIDDLEWARE >> x = list(MIDDLEWARE) >> x.insert(0, 'allauth.account.middleware.AccountMiddleware') >> MIDDLEWARE = x >> ``` >> to work around the NameError. > > After that I get: > > File "/usr/share/mailman3-web/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' > (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: This is another Debian/Ubuntu packaging issue. The packaged /usr/share/mailman3-web/urls.py is incompatible with Django>=4.1. Replace it with the one at https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re… > I guess I'll wait for the new package for now. Hopefully that will fix it, or, as Odhiambo suggests, you can uninstall the Debian/Ubuntu packages and install per https://docs.mailman3.org/en/latest/install/virtualenv.html -- 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

[MM3-users] Re: Trying to understand the mailman.cfg from the virtualenv installation guide

by Mark Sapiro

On 9/11/24 01:44, Danil Smirnov via Mailman-users wrote: > Hi Mark, > > ср, 11 сент. 2024 г., 06:26 Mark Sapiro <mark(a)msapiro.net>: > >> On 9/8/24 01:04, unite42--- via Mailman-users wrote: >>> [mta] >>> verp_confirmations: yes >>> verp_personalized_deliveries: yes >>> verp_delivery_interval: 1 >>> >>> What is the background of these recommendations? >> >> >> These settings enable VERP for all list messages. This results in more >> reliable bounce processing. >> > > > Is there any downsides of using it, so it's not enabled by default? With verp_delivery_interval set to 1, Mailman delivers a separate VERPed message to the MTA for each recipient whereas without this, Mailman delivers one or a few messages with multiple recipients each. This can have a performance impact. This is not a consideration for confirmations or personalized deliveries as those messages have only one recipient per message in any case. I.e., there is no performance impact from setting verp_confirmations: yes verp_personalized_deliveries: yes This is not the default because there can be issues with some MTAs dealing with the VERPed envelope sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 5/8/19 4:45 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: > >> I'll post a follow-up with how to change pass_types via mailman shell >> when I work it out. > > Look forward to that, thanks. OK. in mailman shell with your list as 'm' >>> list(m.pass_types) ['multipart/mixed', 'multipart/alternative', 'text/plain'] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> commit() >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> If you want to allow text from forwarded messages, add 'message/rfc822' in the pass_types list above. This setting will allow inspection of all elementary parts within any multipart parts ant will accept only text/plain and text/html. Then if collapse_alternatives is True (settable here or in Postorius), any multipart/alternative parts will by replaced by the first, presumably text/plain, sub-part. Finally, if convert_html_to_plaintext is True (settable here or in Postorius), any remaining text/html parts will be converted to plain text by lynx or whatever is configured as html_to_plain_text_command in mailman.cfg. This will ensure that filter_action is applied only to those messages which have no text/plain or text/html parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: How to turn off Emergency Moderation for imported MM2 lists?

by Mark Sapiro

Mark Sapiro wrote: > On 7/28/20 5:40 AM, Brian Carpenter wrote: > > > > This is the client that I asking about in my post. > > She said what I > > did, did not work. This is what I did: > > > > Get into a venv as user mailman > > > > #mailman shell > > from mailman.model.mailinglist import MailingList > > mlist = MailingList('listname(a)listdomain.org') > > mlist.emergency = False > > commit() > > ctrl-d (just to be on the safe side) I half understand why this didn't work. Instantiating the list via ``` from mailman.model.mailinglist import MailingList mlist = MailingList('listname(a)listdomain.org') ``` for some reason (that's the half I don't understand) does not get the actual list object so changes you make to it don't affect the actual list. In `mailman shell` you need to do ``` mlist = getUtility(IListManager).get('listname(a)listdomain.org') ``` `getUtility` and `IListManager` are in the namespace in `mailman shell`, but outside of that, e.g. just in `python` in your virtualenv, you also need ``` from mailman.interfaces.listmanager import IListManager from zope.component import getUtility ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Mark Sapiro

On 1/23/23 12:17, Odhiambo Washington wrote: > On Mon, Jan 23, 2023, 23:09 Mark Sapiro <mark(a)msapiro.net> wrote: >> >> It's actually trying to create fulltext_index, so clearly it's not >> looking at the fulltext_index that you are. If you are following >> https://docs.mailman3.org/en/latest/install/virtualenv.html you probably >> need to specify the path in /etc/mailman3/settings.py as in, e.g. >> ``` >> HAYSTACK_CONNECTIONS['default']['PATH'] = >> '/opt/mailman/mm/var/fulltext_index' >> > > Doesn't this follow the same rules of getting the settings.py from gitlab? I don't understand. Can you be more specific? Note that when following https://docs.mailman3.org/en/latest/install/virtualenv.html you create /etc/mailman3/settings.py and it contains ``` from mailman_web.settings.base import * from mailman_web.settings.mailman import * ``` to establish a base set of settings that can be augmented or overridden in /etc/mailman3/settings.py. mailman_web.settings.mailman in turn contains ``` HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': "fulltext_index", ``` which is a relative path for fulltext_index and may need to be set to an absolute path. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 09/29/2017 02:10 AM, Henrik Rasmussen wrote: > Thanks, Mark. > > @Abhilash, any chance for an update to Docker-mailman to fix these known issues soon? > https://gitlab.com/mailman/mailman/issues/256 @Henrik, Contrary to what I said earlier, your issue is not exactly #256. #256 is fixed in Mailman to the extent that the defective message no longer breaks Postorius or causes exceptions in REST, but the underlying issue causing the "KeyError: 'content-transfer-encoding'" exception is not in Mailman. It's in the Python email package. The issue that needs to be fixed for that is <https://bugs.python.org/issue27321>. The bottom line is at this point, <https://bugs.python.org/issue27321> no longer affects Postorius, but it still affects message delivery. I have opened <https://gitlab.com/mailman/mailman/issues/406> about defending against that and also the UnicodeEncodeError you included in your OP. > @Mark, > > Mark Sapiro wrote: >>> >>> bin/mailman queue >>> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck > > Isn't this a Mailman 2 command? What is the Mailman 3 equivalent? No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command is 'bin/show_qfiles'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

Search results for query "sapiro"