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

[MM3-users] Re: Issue with Held Messages

by Jean-Luc Wasmer

On 2016-08-19 17:58, Mark Sapiro wrote: > On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >> >> No matter what action I set for member posts (Hold for moderator, >> Reject) they are always delivered. > > > I don't know why this would be. Perhaps the member's moderation is set > to Accept immediately - you can see this on ther member's options page > in Postorius when logged in as a list owner. Apart from "Mode of Delivery" that is set to "Regular" for the user, none of the following attributes are set: Mail Delivery Receive own posts to the list Receive acknowledgement mails Conceal address from the subscriber list Avoid duplicate copies of messages > When the message is delivered, what are the X-Mailman-Rule-Hits: and > X-Mailman-Rule-Misses: headers? > There is no X-Mailman-Rule-Hits header. X-Mailman-Rule-Misses: approved; emergency; loop; member-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header; nonmember-moderation By the way, I didn't mention before but in Settings | Message Acceptance, the "Acceptable aliases:" box contains "[]". When I try to Save changes after modifying something, I gut "An error occured: []" in the yellow banner (instead of "The settings have been updated."). >> When I tried from a non-member email address, the message got held but >> when I try to see it I get a Server Error (500) page. The log files >> shows: >> >> ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server >> Error: /mailman3/lists/test.mydomain.com/held_messages >> Traceback (most recent call last): > ... >> File >> "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", >> line 443, in held >> moderation_reasons=entry['moderation_reasons'], >> KeyError: u'moderation_reasons' > > > This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> > fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> Any ETA when this will be pushed to "mailman-bundler"? Cheers, Jena-Luc

9 years, 5 months

[MM3-users] Re: Mailman 3 - Header Filter

by Henrik Rasmussen

Mark Sapiro wrote: > On 4/22/19 2:34 PM, Thomas Lehker wrote: > > I am a Mailman neophyte and need help with filtering posts based on the subject field. We have a few list owners that want 'Out of Office' replies discarded. When using the below syntax in Postorius/Header filter the post is not discarded but ends up in 'Held Messages'. Is there any syntax I am missing or a setting in the lists that needs to be disabled/enabled to get these posts dropped? Any help is much appreciated. > The issue may be that in Mailman core's 'builtin' chain, the checking of > header_matches occurs after the check for member moderation so if the > member moderation check results in the message being held, the > header_matches aren't checked. There may me a newer thread about this, but I haven't found it. In my case I would be more interested in holding or discarding mails with subject 'Out of Office' if the mail would otherewise be send the to the list members due to a non-moderated list. I would emagine that the order of "check for member moderation" and header_matches would not be significant if holding or discarding the mail due to header_matches, am I right? 🤞🏻 If so, I would think that Header "subject:" or "subject" with Pattern "^(?i)(.*)autosvar(.*)" - without the double quotes - and Function "Hold for moderation" or "Discard" should either hold or discard any message with "Autosvar" (danish word for "Out of Office reply") somewhere in the subject, but that doesn't happen. What is the correct syntax? I know that filtering out Out of Office replies is just as hard as spam filtering, since it varies, but at least there is some kind of consistency in the wording, so I would give it a try. *) In a prevous mail I was told that ^ would tell Mailman that it is a regex. -- Henrik Rasmussen her(a)adm.ku.dk Copenhagen, Denmark

2 years, 4 months

[MM3-users] Re: Postorius & multi domain

by Gelpi Andrea

Thank You so much for your quickly answer and explanation. I understand that the web server name must be equal to the email domain. I read the issue. I'm not a python programmer so I ask you if it'd be long to implement a workaround like this. If the web server is a.example.com and the email domain is example.com It'd be possible to drop the "a" and send the email domain only in the query? It's a workaround. Can you help me in this? Regards, -- AG Il 22/04/20 18:22, Mark Sapiro ha scritto: > On 4/22/20 8:14 AM, Gelpi Andrea wrote: >> >> I search internet for a while and I discovered that using >> FILTER_VHOST = True >> seems to solve the problem. >> >> >From posotrius config page: >> >> FILTER_VHOST >> Filter the list of available lists in Postorius and Hyperkitty >> depending on the domain they are being currently served from. Mailman 3 >> supports multiple domains in a single installation. >> >> But it doesn't work. I got err 500 form apache. > > > FILTER_VHOST is currently broken unless each domain has the same value > for the web and email domains. See the thread at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > and the issue at <https://gitlab.com/mailman/postorius/-/issues/394>. > > >> Were can I find an explanation or a how to configure the system to have >> 2 webserver with different domains working on the some server as it was >> with mailman 2? > > > If each domain has the same value for the web and email hosts, > FILTER_VHOST will work. > > Currently though if you have domains like web host = lists.example.com > and email host = example.com, FILTER_VHOST is broken. > -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 9 months

[MM3-users] Re: No styling for web apps?

by Morris Jones

On 11/26/20 10:09 PM, Mark Sapiro wrote: > On 11/26/20 8:44 PM, Morris Jones wrote: >> I have most of a new mailman suite server built and working ... >> >> collectstatic gathered a good array of static files (uncompressed so far) >> >> nginx appears to be serving them successfully >> >> The Firefox developer tools show css and js files all being delivered >> >> But none of the postorius or hyperkitty pages exhibit any styling at >> all, only bare HTML elements. >> >> The Firefox inspector will show the available styles being requested and >> delivered (style.css, bootstrap, jquery, all the things). >> >> But if I use the inspector to look at the page, nothing has any CSS >> properties. >> >> I know I'm missing something simple. > > Try running collectstatic and, if you use it, compress again. These have > to be run following various kinds of changes. > Appreciated, but to no avail: (venv) mailman@mail:~/mailman-suite/mailman-suite_project$ python manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /opt/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: yes 0 static files copied to '/opt/mailman/mailman-suite/mailman-suite_project/static', 399 unmodified. (venv) mailman@mail:~/mailman-suite/mailman-suite_project$ python manage.py compress CommandError: Compressor is disabled. Set the COMPRESS_ENABLED setting or use --force to override. And then https://mailman.whiteoaks.com I'll spend time in the Firefox developer tools to see if I can figure out what's missing. A DuckDuckGo search suggested it could be a character encoding issue. The style sheets all come up reporting "0 rules" in the developer tools. I haven't tried any other browsers either. Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 2 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Mon, Dec 26, 2022 at 7:33 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/26/22 06:14, Odhiambo Washington wrote: > > I'd like to integrate Twitter OAuth as part of the Social Accounts in my > > setup. > > I have gone through > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter, > but > > cannot find the config options to add to my settings. > > Does someone have a config block setting for "SOCIALACCOUNT_PROVIDERS =" > ? > > > The last I looked into using Twitter as an OAuth2 provider, which was > some time ago, it would not work because Twitter would not provide the > user's email address via OAuth2. Possibly this could work if the user's > name was her Twitter handle. > > As far as SOCIALACCOUNT_PROVIDERS is concerned, you don't need anything. > You just need to create your OAuth2 app and provide the keys via the > Django admin SOCIAL ACCOUNTS interface. See > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… What I did: 1. I had to uncomment the relevant line under the INSTALLED_APPS = in settings.py. I had to restart Apache so that I can get the relevant provider name at https://mysite.name/admin/socialaccount/socialapp/ 2. I would then configure the social app as per https://django-allauth.readthedocs.io/en/latest/providers.html 3. Lastly, I needed to add the relevant options under the SOCIALACCOUNT_PROVIDERS = in settings.py. Now I have this: SOCIALACCOUNT_PROVIDERS = { 'google': { 'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}, }, 'github': { 'SCOPE': [ 'user', 'repo', 'read:org', ], }, 'facebook': { 'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': [ 'email', 'name', 'first_name', 'last_name', 'locale', 'timezone', ], 'VERSION': 'v15.0', }, } And those are working but was wondering what to add for Twitter. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: MTA setup

by Arte Chambers

Is the mailman lmtp runner a cron job? Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Tue, Dec 24, 2024 at 12:31 PM Arte Chambers <paul.m.robey(a)gmail.com> wrote: > Looks like the from header is the email address I am using for testing: From: > Arte Chambers <paul.m.robey(a)gmail.com> > > > > ``` > $mailman qfile > /opt/mailman/mm/var/archives/hyperkitty/spool/1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck > [----- start pickle -----] > <----- start object 1 -----> > Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com > [209.85.208.182]) > by list.louisvillecommunitygrocery.com (Postfix) with ESMTPS id 3E36381ED2 > for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec 2024 > 17:02:48 +0000 (UTC) > Received: by mail-lj1-f182.google.com with SMTP id > 38308e7fff4ca-3003e203acaso44323081fa.1 > for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec > 2024 09:02:48 -0800 (PST) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=20230601; t=1734973367; x=1735578167; darn= > list.louisvillecommunitygrocery.com; > h=cc:to:subject:message-id:date:from:in-reply-to:references > :mime-version:from:to:cc:subject:date:message-id:reply-to; > bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; > > b=SFr5MsvE4S5GUIy9pEuqDHdEW5nW16briFnXG6ARqjLiFgAX12TU5ozUgw5NCJobcx > > RQWkL64TyXv2C2CTKHjcBH26jiLo1p7h2edLXSBCmd374QbRYQPbv5yZb4jmwX5kfMzr > > fc/I3pSk6ruN/j+JPGLVxBJBreyLRDV+YL0rDJts83a8hcPHghGMkRTmi2Z1vLYgqThA > > 2fV/IYwrOe/q4c2+/AwlKQFUuClaxFN4AniNi++Hk7eql7q4ceDtURp1pHW/h4+8UXgJ > > 2DQ+zwPapOiU5POtfka1fAHTJgykuOoMCmO0YiwfP9p51lXmr4GmdFjFgDOiQwzhx8dH > vAEw== > X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=1e100.net; s=20230601; t=1734973367; x=1735578167; > h=cc:to:subject:message-id:date:from:in-reply-to:references > > :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id > :reply-to; > bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; > > b=IwucO1D8XfIbWVT6dQ/LdKNsesrSsiekzj0khFI38CLd6WryQGJOQftxOLR5AvneNs > > 9gUbVvFAe0VENzTbMrelFr4H5DTI9HrKbNVYEbleeMrbuPypsTdtqWTrjizGhMQROhvs > > vOxl3T+UfRjDywLj9OuYBiWKTDIIaTpeQ7rR4u1lT8iMGTUre0V8kikm1BsFXwRRzl+U > > e0ghdIaZYN5kfu/bfR5veCCQhU0l0IF+DvoZzdJCgLkYgImIPhB/X7Zv0wQiUnKoebJo > > h1UFAEQIrVx2iMFHzLsHiqBhKHvJqG72PAa1bMiG0K3EsYvSJHu5zjrkTjoHXazAci4c > trXg== > X-Gm-Message-State: > AOJu0Yz8oZOnap/9jvXAOcFZnjYoReVHBQrfUnC9u6Mi6M2Ea7dkofrs > 4mAlHtOuQYGEyFxJZIOdFybTI20qdBoQBJAPF7FHL6d4mAGrLbPMgTZy3/hWFtmXfOo93a74CSu > YsRCZKH5ixK5jPHn4Vye0i/h0oilWXQ== > X-Gm-Gg: > ASbGncsYG3zr9300F+iwV6VLqHlMKoLuiS2mnT5tGiid8o6Ojd4JIrOBQI0BVNx1aeO > FVisNFC7AKewms0adY+Ug4HLKEtg8GwSIz0i32IOtPNA+tNxEAac47wHBGkcv+H2EfTOMsD/p > X-Google-Smtp-Source: > AGHT+IFNyfqXALTZ0zcO0GJZfpIf/4WT9IZ2EG3oThjt5aoZP3sdPhxjN2UOMTqwI2axiu9io1WSiFszsjxPLHtLIs8= > X-Received: by 2002:a05:6512:1190:b0:53e:37e4:1457 with SMTP id > 2adb3069b0e04-54229550e25mr4737922e87.33.1734973365282; Mon, 23 Dec 2024 > 09:02:45 -0800 (PST) > MIME-Version: 1.0 > References: < > 77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com> > In-Reply-To: < > 77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com> > From: Arte Chambers <paul.m.robey(a)gmail.com> > Date: Mon, 23 Dec 2024 12:02:08 -0500 > Message-ID: <CAM05vAepJnJQengX825dZ4E1PVVxeEgv4ogUcmifP9tqh1i= > mg(a)mail.gmail.com> > To: Arte Chambers <paul.m.robey(a)gmail.com> > Content-Type: multipart/alternative; > boundary="00000000000021f3da0629f2f7aa" > Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG > X-Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG > X-MailFrom: paul.m.robey(a)gmail.com > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; > banned-address; emergency; member-moderation; nonmember-moderation; > administrivia; implicit-dest; max-recipients; max-size; news-moderation; > no-subject; digests; suspicious-header > CC: testing(a)list.louisvillecommunitygrocery.com > X-Mailman-Version: 3.3.10 > Precedence: list > Subject: [Testing] Re: test 12.23.24 11.57 > List-Id: For testing mailing list software < > testing.list.louisvillecommunitygrocery.com> > Archived-At: <> > List-Archive: <> > List-Help: <mailto:testing-request@list.louisvillecommunitygrocery.com > ?subject=help> > List-Owner: <mailto:testing-owner@list.louisvillecommunitygrocery.com> > List-Post: <mailto:testing@list.louisvillecommunitygrocery.com> > List-Subscribe: <mailto:testing-join@list.louisvillecommunitygrocery.com> > List-Unsubscribe: <mailto: > testing-leave(a)list.louisvillecommunitygrocery.com> > > --00000000000021f3da0629f2f7aa > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Thank you, > Paul 'Arte Chambers' Robey > 502-408-6922 > > > On Mon, Dec 23, 2024 at 2:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/23/24 09:01, Arte Chambers via Mailman-users wrote: >> > Output from mailman log after sending a test message to the list: >> > >> > Dec 23 16:52:23 2024 (684048) Traceback (most recent call last): >> > File >> > >> "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", >> > line 158, in _archive_message >> > url = self._send_message(mlist, msg) >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> > File >> > >> "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", >> > line 228, in _send_message >> > raise ValueError(result.text) >> > ValueError: >> > <!doctype html> >> > <html lang="en"> >> > <head> >> > <title>Bad Request (400)</title> >> > </head> >> > <body> >> > <h1>Bad Request (400)</h1><p></p> >> > </body> >> > </html> >> >> mailman_hyperkitty is sending the message to hyperkitty to be archived >> and receiving the 400 response. Presumably it has previously requested >> and received the list_url and the permalink to put in the message >> headers. This can be confirmed by the presence of List-Archive: and >> Archived-At: headers with values in the messages from the list. So the >> configuration seems to be correct to allow mailman_hyperkitty to >> communicate with hyperkitty. It is not clear why, but this code >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… >> is getting the ValueError. That can come from one of three places in >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming…. >> >> The lack of a Message-ID: is not it because Mailman's lmtp runner will >> add one. Most likely it is the non-ascii sender address from >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming… >> >> What do you get from >> ``` >> mailman qfile var/archives/hyperkitty/spool/xxx.pck >> ``` >> where xxx.pck is one of the (hopefully smaller) files. In particular, >> what is the From: header in that? >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to paul.m.robey(a)gmail.com >> >

1 year, 1 month

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 4:08 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 3:33 PM, Mark Dadgar wrote: >> >> Any thoughts on how to salvage ~20 years of list archives? > > > The archives shouldn't be an issue. I don't think they are involved in > the corruption, but anyway, hopefully you still have the archive mbox > you imported. Then for the messages since then, you should be able to > get a mbox from hyperkitty with something like > > https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… > > with the obvious substitutions and appropriate start and end dates. > > The list is trickier. If you are going to start over with a clean > install, and if you have a config.pck that you imported from MM 2.1, I > suggest the following: > > Use the `mailman members` command to get a list of all members. Then > depending on how much work you want to do, also get separate lists of > plaintext and mime digest members and members with delivery disabled. > > Then on the new install, import the config.pck with `mailman import21` > and import the archive mboxes with hyperkitty_import. > > Run `mailman members --sync` with the full current membership list, and > record the [ADD]s. Then you can match the [ADD]s against the plain and > mime digest members and those with delivery disabled and set their options. > > That's a lot to do, but it should get you close. I would probably be satisfied with just exporting the current list of member email addresses + names and letting people go back and change their list settings to switch to digest, etc. if necessary. > On the other hand, if you can wait, we might be able to figure out how > to fix this, and it's even possible the underlying issue isn't database > corruption. Sure - I can wait. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 7 months

[MM3-users] Re: API timeout for one list

by Abhilash Raj

On Wed, Sep 23, 2020, at 6:33 AM, Seth Seeger wrote: > > > On Sep 22, 2020, at 4:30 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 9/22/20 12:45 PM, Seth Seeger wrote: > >> I apologize, because I think this was talked about before, but I could not find it in the archives. > >> > >> For one list, the REST API times out. Doesn’t seem to matter which page I try to go to. The uwsgi-error.log entry: > >> > > ... > >> The other lists work fine. > > > > This can happen on lists with lots of members. > > > > Try increasing the timeout. See <https://wiki.list.org/x/17892072> > > Thank you - that did solve my timeout problem. > > However, each page for this list takes between 40 and 80 seconds to > load. The list has 465 members, and it’s running (via Docker) on a 2 > core, 4 GB RAM Linode VM. I’ve watch htop during the load - one CPU > is around 20%, and the other hovers around 80%, mostly with the process > “runner”. > > Is there a way to optimize this list? There are no held messages, no > subscription requests, no templates. Are there any subscription requests pending confirmation from the User. If you go to Subscription Requests -> Pending Confirmation from list's admin page, you'll see the list there. In the past, I've noticed this caused a significant delay in every list page. This has since been fixed in the master branch, but yet to be released. > > The next biggest list has 438 members, and all those pages load very > quickly (0-2 seconds). I can’t figure out what the difference between > the two lists. > > Thanks, > Seth > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 4 months

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Stephen J. Turnbull

Mark Sapiro writes: > I have had some contact [with EMWD], but not much. As far as I > know, they are still in business and offering list hosting > including Mailman 3 lists with Affinity and Empathy. They no longer > offer support for installation and maintenance of Mailman on other > people's servers. That exactly describes my experience. To jaboyib556, I recommend you contact them directly and make your own judgment. I do not know the current operators of EMWD, but I do know that the Carpenter family carefully vetted several bids. And their concentration on servers they run suggests they know what they're good at and have focus. I think they're a good bet, but only you can judge. > As far as I know, it was only EMWD that did this and for business > reasons, kept it proprietary. I corresponded with Brian about this.[1] He said that a third-party consultant (not sure if they're related to the current operators) built the Affinity and Empathy applications in PHP on a limited budget, and he felt that he needed to keep them proprietary as a temporary "no competition" measure until they could build up a nest egg to support on-going development. He said, and I have no reason to disbelieve him, that he thought it would take a year to build the reputation, another year to recoup the investment, and within that time frame he planned an open source release. I suspect he planned a Aladdin Ghostscript-like strategy: with the publication of release N, he would release N-1 as open source. He made no commitments, but I believe that was his aspiration. He was always a great supporter of Mailman, giving generously of his time and expertise to people on our lists including those hosting with other businesses. We miss him a lot. Footnotes: [1] On friendly terms: "hope for an open-source release" is not a matter of moral imperative with me, and I believe I speak for all Mailman developers on that.

3 years

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 6/21/24 02:07, Mark wrote: >> ...The mmdf files don't exist in the list's directory although there >> have been many posts to the list throughout the day. On 2024-06-21 15:55, Mark Sapiro wrote: > Assuming your mailman/app/digests.py is unmodified, there is some race > condition. The code beginning at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… > finds the file and size is > 0, but by the time it gets to > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… > the file is gone. > > What other crons run at the same time? The digest.py file is out-of-the-box and unmodified. ls -la /opt/mailman/venv/lib/python3.11/site-packages/mailman/app/ ... -rw-r--r-- 1 mailman mailman 4642 Jan 30 08:06 digests.py The /var/log/cron.log shows the crons running at the same time as digest at 22:30 hours. # tail -f cron.log ... 2024-06-21T22:30:01.368407+00:00 deu CRON[3422196]: (root) CMD (sh /templates/mailman_custom_templates.sh > /dev/null) 2024-06-21T22:30:01.369050+00:00 deu CRON[3422197]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs quarter_hourly) 2024-06-21T22:30:01.371586+00:00 deu CRON[3422198]: (mailman) CMD (/opt/mailman/venv/bin/mailman notify) 2024-06-21T22:30:01.371878+00:00 deu CRON[3422199]: (mailman) CMD (/opt/mailman/venv/bin/mailman digests --periodic) 2024-06-21T22:30:01.372190+00:00 deu CRON[3422202]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) /////////////////////////////////////////////////////////////////////////////////////////////////////////////// The mailman crons are more or less out-of-the-box: MAILTO=imark(a)posteo.net 30 22 * * * /opt/mailman/venv/bin/mailman digests --periodic 30 22 * * * /opt/mailman/venv/bin/mailman notify #@daily /opt/mailman/venv/bin/mailman digests --periodic #@daily /opt/mailman/venv/bin/mailman notify # * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly # The root cron just runs a bash script every 5 minutes to copy custom templates from the mailman and mailmanweb databases and write them to files. ...

1 year, 7 months

Search results for query "sapiro"