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

[MM3-users] Re: High memory usage

by Mark Sapiro

On 2/15/22 08:11, Stephen Daniel wrote: > TL;DR: quite likely your system has plenty of memory and is operating > normally. ... > On Tue, Feb 15, 2022 at 5:28 AM Prasanth Nair <prasanth.nair(a)linaro.org> > wrote: > >> Hi, >> >> We are having an issue with high memory usage on our Mailman3 server. >> Initially, our server had 16GB RAM and the memory usage went up from 5% to >> 92% within a week. So, we increased the memory capacity to 32GB RAM and we >> can see that the memory usage is going up in the same pattern. >> >> Any idea why it is happening? or any suggestions? Just for reference, mail.python.org supports 231 MM 2 lists and 182 MM 3 lists with 16 GB of ram and no swap. The server that supports this list and also the www.list.org web site has 4 GB of ram and no swap. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Migrated from MM2 to MM3, all is well except *one* list

by Mark Sapiro

On 8/27/22 1:20 PM, Scott Courtney wrote: > Hello, all > > I have migrated a multi-list server from MM2 to MM3, on Debian 11, and > migrated about half a dozen lists with fairly large archives. > Absolutely everything has been working for a couple of months, but I > am still unable to get one specific list to send mail to its > subscribers. Of course, the first place I started was the logs, but > that's the problem -- even with logging turned up, it appears to be > failing silently as it connects to the MTA. See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You probably ran `mailman import21` for that list as root or some other non Mailman user (`list` with Debian packages) causing that list's templates to be unreadable by Mailman. -- 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 configuring mailman3 on debian bullseye

by Mark Sapiro

On 3/15/23 09:55, Odhiambo Washington wrote: > On Wed, Mar 15, 2023 at 7:10 PM Servizio Informatico U.I.C.I. Sezione > territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: > >> Hi, >> >> I created a template but after some tests I deleted it. >> >> Now I created only a standard list without modifying any templates. >> >> So they are the standard templates coming with the distribution. I did not >> change also the language >> > Maybe you can start by deleting any templates in postorius_emailtemplate > table in the DB? There shouldn't be any, but if the issue is with accessing postorius templates, that might make it worse. If you want only the system default templates, you could do this database query to remove any non-defaults: DELETE FROM templates; That will ensure that you aren't accessing Postorius for any templates. -- 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: Can't subscribe on new site/domain

by Mark Sapiro

On 10/9/25 2:39 PM, Flo via Mailman-users wrote: > > In this case I see that I have permanently troubles with this software > (OS-packages) so your suggestion is worth to consider. > > Is there a possibility to export all members including real names. It > doesn't work with Postorius, yet, is there another possibility? If I > have my user data exported, I could delete everything and start from > scratch. Maybe this is the most reasonable ... You can install mailman following https://docs.mailman3.org/en/latest/install/virtualenv.html and keep your existing database(s) which will include all lists and memberships. The current released versions of Postorius include only emails in the csv export. This is fixed for the next release by https://gitlab.com/mailman/postorius/-/merge_requests/993 You can currently get a list of members with display names with the `mailman members` command. See `mailman members --help`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/31/2017 01:06 AM, David Krantz wrote: > On Fri, Mar 31, 2017 at 9:29 AM, Simon Hanna <simon.hanna(a)serve-me.info> wrote: >> On 03/31/2017 08:10 AM, David Krantz wrote: >>> I think that would correspond to this line in urls.py >>> >>> url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), >> Yes, that's the culprit. Replace it with the following: >> >> url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), >> You can also update whatever guide you were using... > > Great, will try that! I don't know whether I can update the guide. > It's the one referenced earlier in this thread named something like > setup experience of mailman 3 in production. Yes, that comes from "https://wiki.list.org/DOC/Mailman%203%20installation%20experience", specifically the attachment urls.py. The interesting thing is that works for me both at <https://lists.mailman3.org/> and <https://mail.python.org/mm3/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 4 months

[MM3-users] Re: WEB UI fail to reply and create new thread

by Mark Sapiro

On 12/18/20 10:26 AM, Milan P. Stanić wrote: > > Sending mail by mail clients works and mails are sent to subscribers > properly. > Most other 'things' works but we have problem with reply to posts and > creating new threads using web ui. When replying to post with web ui it > says that the everything is ok and post is sent but post doesn't arrive > to mailing list. Same happens with creating new thread. > > Our debug says "KeyError: 'display_fixed'" but we are not sure what > should be changed/fixed/set for this problem. > Attached is excerpt from debug log. I don't think that exception is the problem. See <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/posting.…> for whit I think might be the issue. I.e., Hyperkitty won't send the mail if DEBUG = True -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Bounce Problems

by Mark Sapiro

On 2/23/21 2:25 AM, M4tze wrote: > If I understand the settings correctly, bounce_info_stale_after = 7d > means that any bounce received > 7d ago are not counted (which would be > intuitive). But it doesn't work that way. It means that the user's bounce info is ignored/discarded if the user hasn't received a bounce within the last bounce_info_stale_after days. I.e it is bounce_info_stale_after and not bounces_stale_after. > It seems, that there must be a 7d gap between the last > bounce received and a new bounce to get the score reset to 1. Is my > interpretation right? Is this intentional? Can this be changed? Yes, this behavior is intentional and no, it won't be changed. Consider a list that gets fewer than five posts per week. While default settings probably aren't appropriate for this list, with default settings, if we discarded bounces older than 7 days, an address that bounced every post would never be disabled. -- 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: can't get mail into mailman3 in docker

by Mark Sapiro

On 8/6/21 6:26 AM, bob B wrote: > > But when I send a message, the docker host machine in /var/log/email/ shows "connection refused" & "lost connection" to mailman-core port 8024 > > > ************************************ > 2021-08-06T09:08:41.885213-04:00 dockerhost postfix/cleanup[109782]: D630B3083ED0: message-id=<4805A7DC-E100-4851-B1BB-E6C1806568A1(a)sender.com> > 2021-08-06T09:08:41.896943-04:00 dockerhost postfix/qmgr[105559]: D630B3083ED0: from=<USER(a)sender.com>, size=8308, nrcpt=1 (queue active) > 2021-08-06T09:08:41.949022-04:00 dockerhost postfix/lmtp[109783]: connect to localhost[::1]:8024: Connection refused > 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) The Connection refused is from trying to connect to localhost at IPv6 ::1. Then Postfix tries 127.0.0.1, gets connected and then Mailman's LMTP runner closes the connection. There may be more info from aiosmtpd in Mailman's smtp.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: How to edit default 'Reject (with notification)' message

by Mark Sapiro

On 5/26/23 7:57 AM, Zaheer Abbas wrote: > > I have created a template with the option, "Notice sent to a poster when > their message has been rejected by the list’s moderator." but it only works > if message acceptance is set to 'Hold for Moderation' and then the > moderator rejects the post manually. > > Is there any source file, which I can modify to replace the default > rejection text mentioned above? The template you want is described in Postorius as [list.user.notice.rejected] Notice sent to a poster when their message has been rejected automatically You can set it in Postorius per list or per domain or you can set it sitewide by putting it in Mailman's var/templates/site/en/list.user.notice.rejected.txt and if you do that, be sure the Mailman user has access to read it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

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

by Mark Sapiro

On 3/1/26 05:10, Paul Tomblin via Mailman-users wrote: > > I did a "update_index_one_list" on each archive after I brought it into hyperkitty. I was impressed with the full text search. 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 and there are lock contention issues between it and the hourly update_index job. It's purpose is to drop entries for messages that have been removed. It's not critical that it runs at all. If you don't want to run it, you can apply a patch like: ``` --- a/hyperkitty/jobs/update_and_clean_index.py +++ b/hyperkitty/jobs/update_and_clean_index.py @@ -31,7 +31,7 @@ from hyperkitty.search_indexes import update_index class Job(BaseJob): help = "Update the full-text index and clean old entries" - when = "monthly" + when = "never" def execute(self): run_with_lock(update_index, remove=True) ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

Search results for query "sapiro"