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

[MM3-users] Re: IndexError in archiving queue

by Mark Sapiro

On 3/16/23 04:13, Jacob Sievert via Mailman-users wrote: > Hello, > > it seems I have forgotten where I can kick an email out of the archiving > queue as it produces this error in a loop. > Might one of you know where I can do that? > Thanks in advance. The underlying error is a bogus Message-ID header in the message. We have observed cases of Message-IDs like Message-ID: <[d1e99408882e4aed93b0df4c1c28dfa3-JFBVALKQOJXWILKNK4YVA7COOVDWK5D4IVWWC2LMKB2WE3DJONUGK4T4IV4G6U3NORYA====(a)microsoft.com]> where the `[` and `]` are the problem. See the report at https://gitlab.com/mailman/mailman/-/issues/732 and fix for that at https://gitlab.com/mailman/mailman/-/merge_requests/1099 I would like to see the headers of the message in your case. To answer your question, the offending message is queued in Mailman's var/archives/hyperkitty/spool/ directory and can be examined with Mailman's `mailman qfile` command. -- 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

[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 12:30, Wikinaut wrote: > Now I wanted to start uwsgi, after having setup everything as documented but I got in the error log this: > > ModuleNotFoundError: No module named 'allauth.account.middleware' As it says at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… "Note either downgrade django-allauth or update MIDDLEWARE, but not both." Now you have added 'allauth.account.middleware.AccountMiddleware' to MIDDLEWARE and downgraded django-allauth<0.56. You can either do ``` pip install --upgrade django-allauth ``` or remove ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` from /etc/mailman3/settings.py. Either will do, but DO NOT DO BOTH. -- 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: Removing a moderator via the REST API

by Mark Sapiro

On 11/15/24 06:38, Andy Matthews wrote: > > Given a list address of announce(a)bar.com, and a subscriber of andy(a)bar.com, the API endpoint would be: > ``` > 'lists/announce.bar.com/moderator/andy@bar.com' > ``` > > Is that correct? Yes. > One question, I think I assumed that removing a user from the list would also cascade to remove any roles that user may have had. So we're currently POSTing to `lists/announce.bar.com/roster/member`, and I was expecting that to also remove the moderator role. But it sounds like it would require an extra call to explicitly remove them as moderator? Yes, member, nonmember, owner and moderator roles are all separate. removing a user from one of those roles has no effect on any other role the user might have. -- 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

[MM3-users] Re: Cannot Install Web UI

by Mark Sapiro

On 10/23/25 11:57, dap1--- via Mailman-users wrote: > OK, so gnuicorn is easier to install and set up. However, it has its own glitch not in the docs. I'm getting the following error trying to start web: > > gunicorn[42860]: !!! > !!! WARNING: configuration file should have a valid Python extension. This is just a warning and can be ignored. > gunicorn[42860]: !!! > gunicorn[42860]: Error: Error: '/opt/mailman/mm/var/logs/error.log' isn't writable [PermissionErr> > > The docs say to use conf but I think the error implies it should be py. In addition I'm guessing I have to change the log and access file names to something like gunicorn.error.log. The access.log and error.log names are correct. They should be owned by `mailman` and your /etc/systemd/system/mailmanweb.service should include User=mailman -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/25/24 11:20, Bryan Fields wrote: > Sorry for the delay, I was on some travel last week. > > On 7/19/24 7:30 PM, Mark Sapiro wrote: >> That URL gives me as server error. What's in the Django (mailman-web) >> logs for that? > > I did notice hitting a 500 error on occasion, sometimes it works. I just tried it twice more and got the error both times. > When this happens, I get an email error below. This is really wierd. See below. >> Are you running all the Django periodic jobs and is qcluster running? > > Ok, the docs said that qcluster service wasn't needed under uWSGI > https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s… > qcluster does appear to be running: Right, you don't need to create a separate service for it with our recommended uWSGI configuration because uWSGI runs it, but it does need to run. ... > line 88, in reverse > return resolver._reverse_with_prefix(view, prefix, *args, **kwargs) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/urls/resolvers.py", line 828, in _reverse_with_prefix > raise NoReverseMatch(msg) > > Exception Type: NoReverseMatch at > /archives/list/nanog(a)nanog-mm3.keekles.org/ > Exception Value: Reverse for 'hk_archives_with_month' with keyword > arguments '{'year': 999, 'mlist_fqdn': 'nanog(a)nanog-mm3.keekles.org', > 'month': 12}' not found. 2 pattern(s) tried: > ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$', 'hyperkitty/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$'] > Raised during: hyperkitty.views.mlist.overview It appears to be trying to get the threads for December, 999. What do these queries show? SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM date_active) < 1000; SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM date) < 1000; -- 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: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, you > can set max_message_size in your list configuration. It defaults to 40; > units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 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 11:48, Wikinaut wrote: > > I was "_forced_" :-) to install that in one of the very first steps of the documentation. https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… > > What I suggest is: > > I will (try to help) to fix the documentation, so that it also can work for mysql. > Please, I am willing to help. It seems to me that adding a sentence following "This will install latest release of Mailman Core, and Python bindings for Postgresql database." such as "If you are using a different database manager, do not install psycopg2-binary." would suffice. What do you think? -- 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: Mailman 3 Keeps Forgettings Imported Lists

by Mark Sapiro

On 07/30/2018 07:37 AM, Ryan McClung wrote: > GNU Mailman 3.2.0 (La Villa Strangiato) > Python 3.6.5 (default, Apr 10 2018, 17:08:37) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > config file: /opt/mailman/var/etc/mailman.cfg > db url: sqlite:////opt/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > > Shortly after I run an import on a bunch of lists they all disappear. > [root@mailman3(stg) mailman]# mailman lists > No matching mailing lists found > > I have 30+ lists. Does the 'mailman lists' command invoke the identical 'mailman' file as the 'mailman import21' command that did the imports. And how did you create the lists before importing them? We have done several imports of 2.1 lists to <https://mail.python.org/mm3/mailman3/> and have never seen an issue like this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/22/20 1:04 AM, Torge Riedel wrote: > Am 07.11.20 um 04:24 schrieb Abhilash Raj: >> I missed it in the original email, but a full list of changes in this >> version is present here: >> >> >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… >> > > Hi, > > this link now points to 3.3.3, is there a chance to make this link more > stable? Maybe > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… Those links are created by Sphinx and as you note the fragments are not stable. I don't know if it's possible to tell Sphinx via the .rst source how to name the fragments. Maybe the best idea is to not use fragments at all and just point to the document. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Moderation emails

by Mark Sapiro

On 3/3/21 7:59 PM, peter(a)chubb.wattle.id.au wrote: > > The third part is another message/rfc822 part that says, > If you reply to this message, keeping the Subject: header intact, > Mailman will discard the held message. The 'this message' in that text refers to the message in the message/rfc822 part. I know it's confusing, but it's been that way since Mailman 2.1.0. That said, it should be fixed. It should at least say "If you reply to this attached message part, not the outer message, keeping ...". It also refers to an Approved: header with the list password, and there is no list password. There is a moderator_password which works in this context, but it is rather obscure. Not only that, but it doesn't work anyway. See <https://gitlab.com/mailman/mailman/-/issues/631> and <https://gitlab.com/mailman/mailman/-/issues/169> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Search results for query "sapiro"