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

[MM3-users] Re: mailman import21

by Mark Sapiro

On 10/11/20 8:26 AM, Brian Carpenter wrote: > > On 10/11/20 11:06 AM, Mark Sapiro wrote: >> Also, things like message and digest headers and footers that are MM 2.1 >> list attributes that are templates in MM 3, although import21 tries to >> handle those. > > So are how these templates showing up on my Mailman 3 servers? They show > up in /opt/mailman/mm/var/templates/lists/listname/en/. I have a client > whose old footer template from Mailman 2 still showing up in list > messages. He then created a custom footer template via Affinity (same > thing happen in Postorius) and both custom footers were being included > in list messages. As I said, (msg|digest)_(header|footer) are MM 2.1 list attributes, not templates. Those, and I think only those, are converted to var/templates/lists/listname/lc/ templates by import21. If I understand you correctly, after creating a custom template in Postorius or Affinity, both that and the old template were included in delivered posts. I don't understand that. For Postorius at least, when a custom template is created, it sets the URI for the template in core to point to Postorius to get the template. the old template in var/templates/lists/listname/lc/ should not be referenced. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: lists.mailman3.org web site.

by Mark Sapiro

On 08/27/2016 09:15 PM, Mark Sapiro wrote: > I have just upgraded the lists.mailman3.org Mailman 3 installation to > the heads of the GitLab mailman* branches. A major change is the switch > from Persona to Django Allauth. This requires some configuration which > isn't yet complete. Hopefully it will all be working very soon. > > In the mean time if you want to log in to Hyperkitty/Postorius you > should be able to log in with your email address. The first time you do > this, Mailman probably won't even know your password so you'll have to > request a reset. Once you have reset your password, you should be able > to log in. > > I hope to have several social auth choices working very soon. Update: Django Allauth is now properly configured and working on lists.mailman3.org. You can log in by email/password as noted above or via OAuth2 with a GitHub, GitLab, Google or Facebook identity. If you are an existing user, in order to use one of the OAuth2 providers, you must first log in with email and password and go to the Account Connections tab in your account settings and add the 3rd party account(s) you wish. -- 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

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 4/15/19 10:16 AM, Dmitry Makovey wrote: > So our mailman got stuck again, but I did follow your advise. Here's > what I've found: > > On 3/29/19 2:58 PM, Mark Sapiro wrote: >> >> If the out runner is running, is there a file named *.bak along with all >> the *.pck files in queue/out/ > > there is one, yes: > > # ls -l /srv/mail/mailman/core/var/queue/out/*.bak > -rw-rw---- 1 100 65533 21512 Apr 14 19:45 > /srv/mail/mailman/core/var/queue/out/1555296331.8386078+2c905825b82708e5a682b872b0aff320c9dd0b2e.bak > > what does it indicate and what should my steps be to resolve this (other > than restarting queues)? This says that the out runner has picked up that entry and is processing it, but, of course, it is now hung somehow in that process. Examining that entry with 'mailman qfile' may possibly provide a clue, but I suspect not as when you restart the out runner process it will reprocess that entry (which is the whole purpose of saving it as .bak during processing), and this time it seems to go OK. You might try running strace or similar on the procees to try to see what it is waiting on. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/11/25 4:58 AM, Flo via Mailman-users wrote: > On 10/11/25 04:45, Mark Sapiro wrote: >> >> The fields in order are: >> >> 1. the id of the django_mailman3_maildomain entry >> 2. the mail_domain in the django_mailman3_maildomain entry >> 3. the site_id the django_mailman3_maildomain entry >> 4. the id of the django-site entry >> 5. the domain name in the django-site entry >> 6. the display name in the django-site entry >> > > For me it looks like that 5 is the display name and 6 the domain name Possibly sqlite displays them in a different order. To be sure you could do SELECT mail_domain, domain FROM django_mailman3_maildomain JOIN django_site ON site_id = django_site.id; which will display only the mail_domain and the site domain. > For each of the lines mail_domain (field 2) is the same as the domain > name (field 6, if I am right). > Any domain name (and mail_domain, which has the same value) differs from > the ones in any other line. > > So they are unique. Anyway, if all 3 mail_domain values are unique, that doesn't explain the issue. I can only guess that this is a Debian package issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: Display the last post time for a list or all lists.

by Mark Sapiro

Mark Sapiro wrote: > It wouldn't be difficult to do, but at the moment, it wouldn't provide anything useful because of <https://gitlab.com/mailman/mailman/issues/453>. The issue is now fixed in the branch head at least. The script corresponding to https://www.msapiro.net/scripts/last_post.py would be almost identical except for changing real_name to display_name, last_post_time to last_post_at and fixing the print for Python 3. Also changing the string interpolation to format(), it becomes: --------------------------------------------------- import time def last_post(mlist): print('{}: Last post at {}'.format( mlist.display_name, time.ctime(mlist.last_post_at) )) --------------------------------------------------- The only issue with the script is for a list which has had no posts since #453 was fixed, mlist.last_post_at is None and time.ctime(None) is the current date and time. That too could easily be fixed like: --------------------------------------------------- import time def last_post(mlist): if mlist.last_post_at: print('{}: Last post at {}'.format( mlist.display_name, time.ctime(mlist.last_post_at) )) else: print('{}: No posts'.format(mlist.display_name)) --------------------------------------------------- The trickier part is the Mailman 3 mailman withlist command has no option to run for all lists, so you'd need to run it something like #!/bin/sh for list in `mailman lists -q`; do mailman withlist -r last_post -l $list done -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[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, 9 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, 7 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, 11 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

6 months, 3 weeks

[MM3-users] Re: High IO for 8+ hours

by Mark Sapiro

On 3/1/26 13:03, Paul Tomblin via Mailman-users wrote: > > > On Sun, Mar 1, 2026, at 3:38 PM, Mark Sapiro wrote: >> On 3/1/26 05:10, Paul Tomblin via Mailman-users wrote: >> The HyperKitty update_and_clean_index job runs monthly and does the same >> thing as the hourly update_index job plus removing index entries for >> messages that have been deleted from HyperKitty. It is very long running > > Does that mean that removing the cron job for the monthly task would do the same thing as the patch? No. Removing the cron job would not run any monthly jobs and there is another one, namely the hyperkitty empty_threads job which removes empty threads. >> It's purpose is to drop entries for messages that have been removed. > > How do messages get removed? Is that an automatic thing or if not, is it something a user can do or only a list owner? Only by list owners or site admins via the `Delete this message` link in the message view or the `Delete this thread` link in the thread view. And I suspect but am not certain that the only thing that results in an empty thread is deleting all the messages in a thread one by one without deleting the thread. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 days, 1 hour

Search results for query "sapiro"