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

[MM3-users] Re: CPU usage when idle

by Mark Sapiro

On 5/28/25 08:27, roughnecks via Mailman-users wrote: > > It's the manage.py qcluster whatever is called. I have shut down MM for > the time being, because I'm not fully motivated to have it running, so I > can't be more accurate right now. I don't know how qcluster is configured in the Debian packages (which are out of date and possibly buggy anyway). You may be using django-q <https://django-q.readthedocs.io/en/latest/> and if so, you should migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both typically use memcached as a backend. Settings that control this are typically ``` # Set retry > timeout. Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } ``` and possibly a setting like `'workers': 2,` (default is the CPU count of the system but see <https://django-q2.readthedocs.io/en/master/configure.html#f1>). ``` CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache', 'LOCATION': '127.0.0.1:11211', } } ``` although the default if not set is ``` CACHES = { "default": { "BACKEND": "django.core.cache.backends.locmem.LocMemCache", } } ``` It is the `'orm': 'default'` setting that says to use Django's CACHES. See <https://django-q2.readthedocs.io/en/master/brokers.html#django-orm>. You can get info about what qcluster is doing with `manage.py qinfo` and monitor things with `manage.py qmemory` and `manage.py qmonitor`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 2:27 PM, Ken Alker wrote: > --On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> > wrote: >> >> The 404s are addresses im HyperKitty's sender table for whih there is no >> corresponding Mailman user. There are multiple possible reasons for this. > > And that is OK, right? Sure. It only means that there are messages in the archive that are From: addresses that aren't currently Mailman users. >> If the behavior has stopped it's probably because the periodic Django >> jobs are not being run - this is bad. > > I see this in the logs from just after midnight: > > Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list > found > Jun 25 00:13:04 2023 (386086) ACCEPT: > <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > Jun 25 00:13:04 2023 (386090) HyperKitty failure on > https://lists.netlojix.com/hyperkitty/api/mailman/urls: > > Followed by a huge amount of HTML (strange). This is all from one post. The first is normal it just says that Mailman's var/public_suffix_list.dat doesn't exist, but it should be retrieved from https://publicsuffix.org/list/public_suffix_list.dat and then saved at var/public_suffix_list.dat so it doesn't need to be retrieved from the web again until the saved copy is older that the configured dmarc.cache_lifetime (default = 7 days, so that message) after which time the message will be 'Cached copy of public suffix list is out of date' The second is acceptance of the post. The third is a failure in archiving the message. Th HTML should contain an error message with a traceback which should help determine the problem. > Is there a way to kick it into re-running whatever it does at midnight > so I can test this again after putting the public suffix list back? I > assume I can just execute "mailman-web runjobs daily", but will this > mess things up, or is it OK to run it mid-day without stopping anything > first? Midnight is a coincidence in this case. the above are all due to the post with Message-ID: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> The cached var/public_suffix_list.dat should now be there with a timestamp of Jul 02 00:13:04 (7 days from Jun 25 00:13:04) > Is the last (third) log line excerpt simply a result of the first, or do > I have something else messed up? The third is not because of the first. It is because of some issue with archiving that post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: outgoing.py mailman@example.com issue

by Mark Sapiro

On 11/8/21 8:28 PM, dancab(a)caltech.edu wrote: >> In either case, the bounce message (fake DSN) should have contained a >> message body like >> Mail to user(a)example.com failed at outgoing SMTP >> with the actual user's address. These fake DSNs are sent in the case >> where the outgoing MTA refuses a message from Mailman so there is no >> actual failure DSN. > > Thanks. I think I'm missing how I can configure Mailman so that the actual user's address is used. I think you are missing the point. This is a pseudo DSN. If it were a real DSN it would be something like From: mailer-daemon@somewhere To: listname-bounces@listdomain However, there is no real DSN because Mailman has gotten a reject in it's attempt to deliver to the outgoing MTA so it creates it's own pseudo DSN for the failure. Another way of looking at this is if you configured Mailman to deliver to a local MTA and configured that MTA to relay to your remote MTA, your local MTA would accept the message and then receive the 5xx status upon delivery to the Remote MTA and would then send an appropriate DSN back to the list-bounces address. Since you are skipping the local MTA part, Mailman gets the 5xx status upon delivery to the remote MTA and creates it's own DSN for itself. -- 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

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/5/25 13:00, megabrutal--- via Mailman-users wrote: > Hi Everyone, > > I've recently installed Mailman3 and still testing it. I tried to reply to a topic on my own list while also being a superuser from HyperKitty, but I got this error message: > > "This list is moderated, please subscribe to it before posting." Is your login a member of the list? > Then why I even see the archive of the private list? What might be wrong? You can see the private archive because you are logged in as a superuser. > One thing that might confuse the system is that I added a secondary e-mail to my account. I thought it would allow me to post from any of my addresses, but it seems like it's not the case, looks like I can only subscribe with one of the addresses. How did you add that email? When you find yourself at https://example.com/mailman3/users and click Manage, do you see the expected addresses? > It also looks like HyperKitty has trouble matching up the addresses, as it lists 4 participants for the conversation, while 2 of them is my account, the other 2 is my test address. In reality, it should list 2 posters. This is normal. Hyperkitty lists participants by address whether or not the addresses are linked to the same 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, 6 months

[MM3-users] Re: not correct language in subject(s)

by Mark Sapiro

On 5/23/23 06:24, Jens Günther wrote: > > I find those changes, but: in the merge request there is mentioned a > /usr/lib/python3.10/site-packages/mailman/testing/mailman-fr.po > > -> but I don't find a mailman-de.po ... is it maybe that? That file was for a test only. The German message catalog is at mailman/messages/de/LC_MESSAGES/. That directory should contain a mailman.po and a mailman.mo. If there is no mailman.mo, it needs to be created. The source distribution contains a generate_mo.sh script to generate these for all languages, but you can do the German one by changing to the mailman/messages/de/LC_MESSAGES/ directory in the running installation and doing msgfmt mailman.po -o mailman.mo >> Please be more specific than `all types of system mails`. Which >> specific message subjects are not translated. > > It's exactly as mentioned in issue 993 the welcome and goodbye-messages > that I don't see translated. > > But also other examples: > - bounce-mail for the user that moderator approval is necessary (there > the text is in german, but the reason is in english) > - approval-mail for moderator (also text is in german, but subject and > reason in english) I'll look into these. If you don't have the mailman/messages/de/LC_MESSAGES/mailman.mo file, this could be the reason, but there may be a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/3/23 00:31, Onyeibo Oku wrote: > > (1) Mailman refuses to resolve to a preferred subdomain. If the > server's domain is "website.tld", I'd like mailman's homepage to be > at "list.website.tld". Mailman insists that I add "website.tld" to > the ALLOWED HOSTS, whereas "lists.website.tld" is already there as an > ALLOWED HOST (same VPS/IP address nonetheless). The result is that > the homepage ends up at "https://website.tld/mailman3/lists" when the > desired url is "https://lists.website.tld/mailman3/lists". This is a > conflict because the main domain is intended for another service. How > do I approach this? This is all configured in your web server. It needs to proxy requests for lists.website.tld to gunicorn and depending on the web server, may need more. E.g. see https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for nginx. > (2) See the traceback below: > ERROR 2023-01-03 07:40:32,078 27926 django.request Internal Server > Error: /mailman3/lists/ Traceback (most recent call last): ... > "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/query.py", > line 650, in get raise self.model.DoesNotExist( > django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist. > > It seems a migration is missing. How should I approach this? Set SITE_ID = 0 in your Django settings. Also see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- 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: configuring postfix local recipient table

by Mark Sapiro

On 4/25/25 01:02, Alexander Inzinger-Zrock via Mailman-users wrote: >>>> 3.1 parameter for default lookup table type >>> 3.2 pointing to command ''postmap'' >>> Both entries must be present or Mailman will error out before creating >> the postfix_lmtp file. There should be a template (actually, you can >> probably use it "as is") in site-packages/mailman/mta/postfix.cfg (or >> maybe in config/postfix.cfg). >> This file can be located anywhere, but I recommend putting it where >> mailman.cfg is (usually /etc/mailman3), and pointing to it in the >> [mta] section of mailman.cfg with the full path. > > + this file seems to be missing in my setting > + also the postmap command seemed to be unavailable for the user ''mailman''. > + [X] placed file in same dir as mailman.cfg (/etc/mailman3/) > + [X] replaced old config and pointed to it in mailman.cfg with full path: > #+begin_src txt /etc/mailman3/mailman.cfg > #configuration: python:mailman.config.postfix > configuration: /etc/mailman3/postfix.cfg > #+end_src > command ''mailman conf'' will show the new configuration path for > [mta] but no results for search term 'postmap_command' nor 'transport_file_type'. What does `mailman info` show for config file:? What does `mailman conf -s mta` show for [mta] configuration: [mta] incoming: mailman.mta.postfix.LMTP What's in /etc/mailman3/postfix.cfg? -- 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: looking for more detailed traceback for shunted message

by Mark Sapiro

On 4/27/23 1:23 PM, bob B via Mailman-users wrote: > Had a message get shunted in > /opt/mailman/core/var/queue/shunt/. *** but that is the location in the docker environment, which we are running. > > The mailman log shows: > > Apr 26 13:09:56 2023 (31) ACCEPT: 2e0e82a5-0924-1777-bed8-34862417fe7e@[Redacted] > Apr 26 13:09:56 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) > Apr 26 13:09:56 2023 (35) Traceback (most recent call last): > Apr 26 13:09:56 2023 (35) SHUNTING: 1682514596.7976818+6067e5ddeb70e4aad97977071b5ed00c41999057 > Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] > Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] > Apr 26 13:10:16 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) > Apr 26 13:10:16 2023 (35) Traceback (most recent call last): > Apr 26 13:10:16 2023 (35) SHUNTING: 1682514616.5346222+7292ba8b651bc1bd76a9098733a39090e092add2 > > > > Is there anyway to get more info, Is there a more detailed traceback somewhere? I have never seen anything like this. There should be a complete Traceback in between the `Traceback (most recent call last):` line and the `SHUNTING: ...` line. However, I'm pretty sure the issue is a defective email which has non-ascii bytes in an explicit or implicit ascii part. You can see the raw message by pointing `mailman qfile` at the shunted .pck file(s) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Timeouts

by Mark Sapiro

On 4/25/21 4:37 PM, tlhackque via Mailman-users wrote: > The described timeouts are something that hyperkitty ought to be able to > avoid. For apache, the timeout is idle time between blocks of output. > Hyperkitty can avoid this by generating the archive in segments (based > on size, or elapsed time), flushing its output buffer, generating a > multi-file archive, and/or using Transfer-Encoding: chunked (chunked > doesn't work for http/2). It ought to be able to break the work into > blocks of "n" messages & do something to generate output. Besides > avoiding timeouts, working in segments allows the GUI to display > meaningful progress (e.g. if you're loading with XMLHttpRequest, > "onprogress") It really oughtn't be up to the user to break up the > request. It is not the web server that times out. I'm not sure about uwsgi because I don't use it, but the timeouts I see are on servers that use gunicorn as the WSGI interface to Django and the timeout is in a gunicorn worker. This is controlled by the timeout setting in the gunicorn config. <https://docs.gunicorn.org/en/stable/settings.html#timeout> Note that even 300 seconds is not enough to download the entire <https://mail.python.org/archives/list/python-dev@python.org/> archive. It may be possible to get HyperKitty to chunk the output to avoid this, but it doesn't currently do that. Care to submit an MR? -- 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: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Mark Sapiro

On 5/25/24 10:00 AM, schaefer(a)alphanet.ch wrote: > > How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer? The host name displayed in the web UI is based on the SITE_ID setting in Django's settings. This is a system configuration not associated with any lists. it references an entry in the django_sites table in the database. As far as the comment/display name in From: is concerned, what specific emails are you talking about? I don't know where `example.com` would come from unless you mean email from Django in which case look at your setting for ADMINS in your Django settings. > Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR. The `mailman import21` command will properly import the Mailman 2.1 from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. If you have some customization in this area, that probably won't be handled. -- 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

Search results for query "sapiro"