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

[MM3-users] Re: What to backup?

by Mark Sapiro

On 5/26/19 3:07 PM, Mark Sapiro wrote: > > You could modify the above to write the list to a file and then wrap the > whole thing in a shell script which would make the list and then do > something like > > for f in `find var/messages -type f`;do > n=`cut -d / -f5 <<<$f` > for keep in `cat list` ;do > k=0 > if [ $n == $keep ] ;then > k=1 > break > fi > done > if [ $k -eq 0 ]; then > rm $f > fi > done Actually, I thought about it a bit more, and I decided that arcane shell script was a bit obscure and it would be easier to just do it in Python. Plus, you can properly delete the message that way. A complete script for `mailman shell` is like import os msg_ids = {} lm = getUtility(IListManager) ms = getUtility(IMessageStore) for mlist in lm.mailing_lists: requestdb = IListRequests(mlist) for rq in requestdb.held_requests: key, msgdata = requestdb.get_request(rq.id) if msgdata['_request_type'] != 'held_message': continue msg = ms.get_message_by_id(key) msg_ids[(msg['Message-ID-Hash'])] = True for root, dirs, files in os.walk('path/to/var/messages'): for file in files: if not msg_ids.get(file, False): msg = ms.get_message_by_hash(file) ms.delete_message(msg['Message-ID']) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/8/21 1:03 PM, Mark Sapiro wrote: > On 7/8/21 8:35 AM, Sarah H wrote: >> >> When trying to add a new thread via the hyperkitty interface I can see >> the email go through the maillog, I get the email with the entered >> content and everything else works, it just doesn't add a new thread to >> the archive. > > What if anything is in Mailman's var/archives/hyperkitty/spool/ directory? > > Do you have something like > ``` > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > ``` > in your mailman.cfg? Do you then have > ``` > [general] > base_url: ... > api_key: ... > ``` > in the mailman-hyperkitty.cfg file and is base_url set to a url tha > accesses hyperkitty and is api_key set to the same value as the > MAILMAN_ARCHIVER_KEY is your Django settings - quoted in settings but > not in mailman-hyperkitty.cfg, i.e., > ``` > api_key: xxx > MAILMAN_ARCHIVER_KEY = 'xxx' > ``` > I see that these settings are not covered in the virtualenv installation guide at https://docs.mailman3.org/en/latest/install/virtualenv.html. This is now https://gitlab.com/mailman/mailman-suite-doc/-/issues/32 and we'll fix that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: lmtp runner not starting

by Mark Sapiro

On 4/1/23 12:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > El 1/4/23 a las 21:14, Mark Sapiro escribió: >> >> If you had completely stopped Mailman core and then started it, lmtp >> runner should have started. What are the complete log messages from >> mailman.log following the start? >> > I sent them before And there is no `lmtp runner started` message in the log, so it isn't being started at all. >> What does `mailman conf -s runner.lmtp` show? >> > Here it is: > > root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c > "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf > -s runner.lmtp" > [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner > [runner.lmtp] instances: 1 > [runner.lmtp] max_restarts: 10 > [runner.lmtp] path: > [runner.lmtp] sleep_time: 1s > [runner.lmtp] start: yes This says the runner should be started. That is the command that starts Mailman? is it /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg start" or is it something that perhaps uses a different config. What happens if you do /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" -- 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: Main daemon process sticks around after forking

by Mark Sapiro

On 8/6/25 18:17, Mark Sapiro wrote: > On 8/6/25 09:03, Jérôme Charaoui wrote: >> >> I'm running a (rather large) mailman3 instance on Debian 13 (trixie) >> using the distribution packages. >> >> To manage the mailman3 daemon, the package installs this systemd >> service unit: >> https://sources.debian.org/src/mailman3/3.3.10-2/debian/mailman3.service/ >> >> It has been working fine until recently: after a reboot, we noticed >> the mailman3 unit consistently failing to start due to a timeout error. >> >> I figured out that the timeout was related to the service unit type >> (Type=forking) and the fact that the main/parent process was forking >> subprocesses (and running normally), writing a PID file, but it wasn't >> exiting, so systemd identifies this as an error and aborts the service. > > > The master is not supposed to exit. It continues to run and monitor the > child runner processes and will under some circumstances restart a > runner that dies. Further, our recommended systemd configuration is at https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… and includes `Type=forking` and this is the first I've heard of an issue with that. -- 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: Header Filter madness

by Mark Sapiro

On 1/14/21 9:54 AM, Brian Carpenter wrote: > Mark Sapiro wrote: >>> What's in the X-Mailman-Rule-* headers of the post that should be >> but >> isn't held? >> Are there other header filter rules besides the one that doesn't work? > > This is what the client provided me: > > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-listname.listdomain.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header So header-match-listname.listdomain.org-0 and no other header-match rule misses and no rule hits says there is only one header match rule and it missed. Since it hits in your test, I can only guess that the regexp in your test or the specific header in your test was not identical to what was in your test. I assume you have access to the list settings. Does the offending regexp have trailing white space or something else different from your test? Or perhaps the offending header or regexp has some character which is ascii in one and a visually similar but different unicode in the other. Also, I think but am not sure that we don't always properly decode RFC2047 encoded headers for header match rules. This would 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

4 years, 10 months

[MM3-users] Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 11:18 AM, Mark Sapiro wrote: > > Please do send me the shunted .pck. what is going on is this is an > English language list which has character set `ascii` and the notice for > some reason has non-ascii, possbbly the Subject: or the user's display > name has non-ascii. But possibly the message itself is defective. > > In any case, I'd like to get the shunted message to see if there's > something we should fix. Thanks for sending me the shunted .pck. It turns out I didn't need it. Had I looked more closely at the Traceback, I would have realized that the issue is that the list's list:admin:action:post template contains non-ascii. In particular, the character in position 5 is ’ which is a unicode right_single_quote, not an ascii apostrophe. There may be other unicode fancy quotes ad well. You can fix the template to contain only ascii or you can set the character set for English to utf-8 by adding ``` [language.en] charset: utf-8 ``` to mailman.cfg. The downside of the latter is that outgoing message bodies will always be base64 encoded which generally precludes grepping mailboxes to find things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Problem with debian uipgrade

by Mark Sapiro

On 3/8/22 11:40, Mark Sapiro wrote: > On 3/8/22 10:10, Lars Schimmer wrote: >> Hi! >> >> Today I tried a mailman3 upgrade of the debian packages and I got this >> error: >> >> django.db.migrations.exceptions.NodeNotFoundError: Migration >> hyperkitty.0007_allauth_20160808_1604 dependencies reference >> nonexistent parent node ('socialaccount', '0003_extra_data_default_dict') >> >> Anyone has a idea howto fix those? > > This is a reference to a migration in django-allauth. is django-allauth > installed. If so, what version? > > What does the database query > ``` > SELECT app, name FROM django_migrations WHERE app = 'socialaccount'; > ``` > show. It should be > ``` > app | name > ---------------+------------------------------ > socialaccount | 0001_initial > socialaccount | 0002_token_max_lengths > socialaccount | 0003_extra_data_default_dict > (3 rows) > ``` Possibly one way to fix this is to run ``` django-abmin migrate socialaccount ``` where django-admin is the name of your django management command. Then running `django-abmin migrate` should succeed. The issue appears to be due to the face that `django-admin migrate` runs the migrations in alphabetical order by app. This is fine if migrations were run during the period after socialaccount.0003_extra_data_default_dict was created and before hyperkitty.0007_allauth_20160808_1604 was created, but it's an issue in an installation that wants to migrate hyperkitty.0007_allauth_20160808_1604 without having previously migrated socialaccount.0003_extra_data_default_dict. -- 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: Weird hourly indexing error

by Mark Sapiro

On 5/5/20 2:39 PM, Mark Dadgar wrote: > On May 5, 2020, at 2:27 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> This is how less >> displays it >> >>> XSUBJECT9<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>5<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>2<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>5<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>1<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>4<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>1<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>3<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B> >> >> >> Each of those <U+200B> represents a unicode zero width space. > > > That’s gnarly. > > BTW, the patch did not fix it. I haven’t had a chance to look more deeply into it yet. Actually, if I take the above as a unicode string and encode it as utf-8, each of the <U+200B> unicodes becomes three hex bytes \xe2\x80\x88 and the length of the result is 247 bytes, so I suspect that the 'word' in the error message has been truncated. As to the patch not working, there is a different patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> which may work. There is one issue with this patch. Namely it calls force_str() in the section > + # https://trac.xapian.org/wiki/FAQ/UniqueIds#Workingroundthetermlengthlimit > + # Working round the term length limit > + word = force_str(word) > + word_length = len(word) but xapian_backend.py imports force_text <https://github.com/notanumber/xapian-haystack/blob/master/xapian_backend.py…>. They are actually synonymous <https://docs.djangoproject.com/en/3.0/ref/utils/#module-django.utils.encodi…>, but just appliing the patch without changinf force_str to force_text won't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Multiple domain problem

by Mark Sapiro

On 2/10/23 01:43, Lars Bjørndal wrote: > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: >> On 2/9/23 13:21, Lars Bjørndal wrote: >>> >>> If I connect to example2.com, the title is example2.com, without the >>> preceding List index. And the body says Page not found. >> >> >> What's in the browser's address bar for that page? > > It's https://example2.com/mailman3/lists/ And when you get the Page not found, is it a browser 404 error or a Postorius error page? > >> What's in Postorius domains view? > > I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). Why are you going to http://localhost:8000/? You should be able to see the domain's view at https://example1.com/mailman3/domains/ or https://example1.com/mailman3/domains/ or by just clicking Domains in Postorius top nav bar. > Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. Again you should be able to go to https://example1.com/admin or https://example2.com/admin. If these don't work, you need to add directives in your web server to proxy them to http://localhost:8000/admin -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[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, 6 months

Search results for query "sapiro"