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

[MM3-users] Re: cache files?

by Dave McGuire

On 7/12/21 10:45 PM, Mark Sapiro wrote: >> Hi folks. I'm seeing quite a few .css files, thousands of them >> totaling 600+MB, building up in /var/lib/mailman3/web/static/CACHE/css. >> Some of them date back to when I set up the mm3 instance a few years ago. >> >> Is this expected, or am I missing a cron job or something to clean >> them up? > > This is not expected. I don't see it on the instances I manage. > > In the `static` directory, I see > ``` > $ du -h -d 1 > 1.7M ./admin > 12K ./facebook > 68K ./django_extensions > 4.0K ./browserid > 68K ./django-mailman3 > 2.6M ./postorius > 12K ./paintstore > 1.6M ./rest_framework > 5.2M ./hyperkitty > 404K ./CACHE > 12M . > $ find -type f|wc > 401 401 18253 > ``` > > I think when you run the Django admin `collectstatic` command, you need > to specify the `--clear` option. Interesting, I know nothing of that command. Is that something that should be run periodically? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

5 years, 1 month

[MM3-users] Re: remove non members from a list

by Guillermo Hernandez (Oldno7)

On 6/8/21 19:33, Mark Sapiro wrote: > On 8/6/21 10:28 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > >> Thanks. Now it's no showing errors (and nothing at all) but >> apparently it does nothing. The non mebers of the list (the few that >> remains: I've been deleting one at a time from the web) aparently >> still are there.. >> >> Knowing the correct procedure will ease me to try tomorrow with a >> clean head. > > It doesn't report anything, and if you don't commit() or exit with > control-D, any changes will be rolled back. I think I did a typpo. (forgot to add "()" after the "commit" sentence). And exit with quit() maybe not helps. I've done it exactly as you wrote it and it worked like a charm. Thank you very very much > > What does > > list(m.nonmembers.members) > > show before doing the unsubscribe() and commit() and then what after? >

5 years

[MM3-users] Re: Is logging.subscribe working in /etc/mailman.cfg?

by Alan So

Mark Sapiro wrote: > On 12/11/18 2:11 AM, ktso(a)cuhk.edu.hk wrote: > > I have put the following in /etc/mailman.cfg and restart mailman. An > > empty file can be created but nothing can be logged when admin or non-member > > subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in > > mailman.log and smtp.log. Thanks. > > > > [logging.subscribe] > > path: subscribe.log > > level: debug > > The above is correct. As far as not seeing things in the log, very > little is logged in the subscribe log. Only (un)subscription requests > held for moderator approval and moderator approval of held unsubscribes > but not subscribes. > > In other words, unless your list's subscription police includes > 'moderate' nothing will be logged in subscribe.log. It looks like there is only a subscription policy but no unsubscription policy. I can't find anything even by exporting the settings using Python mailman client. Is it correct?

7 years, 8 months

[MM3-users] Re: Mailman web interface / uwsgi

by Jan Eden

On 2022-11-26 22:59, Mark Sapiro wrote: > > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > > files when using the virtualenv installation instructions > > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, > not mailman-web. If you want, you could put mailman-hyperkitty.cfg in > /etc/mailman3/ by putting > ``` > configuration: /etc/mailman3/mailman-hyperkitty.cfg > ``` > in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really > belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. I see. But the mailman.cfg is placed in /etc/mailman3, and this file also belongs to the core, doesn't it? In any case, I changed the configuration parameter for [archiver.hyperkitty] as you suggested and all settings are in one place now. I will post two more questions to this list today, and promise to stop spamming you afterwards. :) Thanks again, Jan

3 years, 8 months

[MM3-users] Re: Sending to mangled 'From' addresses.

by Jeremy Stanley

On 2024-06-01 09:49:54 -0700 (-0700), Mark Sapiro wrote: [...] > If this is the result of a `reply` and not `reply-all` the client > is not behaving reasonably. [...] I haven't seen it with replies, but rather mail clients recording every address they see into their address book, and then when the user of such a client wants to send new mail to someone they start typing that person's name and their mail client happily auto-completes it with the mailing list's address instead of the intended personal address. This is one of the reasons we don't use DMARC mitigations for most of our lists, and instead we just try to make Mailman avoid altering anything in the message headers or body that might invalidate DKIM signatures (so no changing From or Reply-To, no adding list-specific subject prefixes, no appending list unsubscribe info to the end of messages...). It's an unfortunate trade-off, but some of our users do tend to get confused by address book pollution. -- Jeremy Stanley

2 years, 2 months

[MM3-users] Re: Mailman not able to process "big" requests

by Darren Smith

Our installation at https://lists.rootsweb.ancestry.com has around 33,000 lists and somewhere around 1.5 million members. We have lists with 5,000+ members. Note that I haven't tried any mass subscriptions. When we upgraded from mailman 2 to mailman 3, we used the old .pck files and ran the import on each of the lists. It did take about 6 weeks to do the full import all 33,000 lists. I'm not joking. As for sending messages - there isn't any problem sending that many messages out, but then we are also not trying to subscribe list members at the time. We are, though, in the process of importing the old archives from our old mailman 2 system. This doesn't seem to affect the rest of the system. We have seen some inefficiencies in the new system, such as the front page of postorius - loading all of the information for 200 lists (if the user set the "lists per page" to 200) was bringing down the system. We have our own metadata system to be able to search for lists by state/region/surname (ours is a genealogy mailing list system), so we had to replace the front page with our own "find a list" functionality. The other main problem was the page where a user can see what lists they subscribe to. That page was also a denial of service if the user had several hundred lists they are subscribed to. And for a genealogy mailing list system, this is common. We have actually ended up creating our own API layer (only accessible on the local machine) and make certain calls to it for the most painful of the issues. One of these days (when we get a moment to breathe) we are going to post some of our changes to the project so that we can ditch our own API and just use the internal REST API. To be fair, the inefficiencies are not necessarily with mailman or the rest API itself - but with Postorius making hundreds of calls to load a single page. Though if the API supported loading multiple lists at once instead of having to load them serially, that might help as well. So while we have not seen any timeout issues on the call to mass subscribe users, we HAVE found several other calls that are effectively a denial of service and have gotten around them ourselves, with plans to contribute to the project in the near future. -Darren On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/24/2018 12:36 AM, Abhilash Raj wrote: > > On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: > > >> We also have a problem with sending out emails to "large" (>50) groups, > >> as they seem to not getting sent out at all. Do you have any idea what > >> the problem here could be? > > > > Which MTA are you using? What do you see in mailman's logs and MTA's > logs? > > > > I haven't seen this kind of problem before with Mailman 3. This very > list is hosted using Mailman 3 and I believe has more than 50 subscribers. > > > Nor have I seen this issue. This list currently has 158 non-digest > members. There are several @python.org Mailman 3 lists with over 100 > non-digest members including the active yt-users(a)python.org list with > 301 members, and I have gotten no reports of an issue like this. > > Also, there are over 600 lists at <https://lists.fedoraproject.org/>, > and I don't think this is an issue there either. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 3 months

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

by Flo

On 10/11/25 00:18, Mark Sapiro wrote: > On 10/10/25 1:47 PM, Flo via Mailman-users wrote: >> >> :/var/lib/mailman3/data# sqlite3 mailman.db >> SQLite version 3.46.1 2024-08-13 09:16:08 >> Enter ".help" for usage hints. >> sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON >> site_id = django_site.id; >> Parse error: no such table: django_mailman3_maildomain >> sqlite> > > Is there a second database? Something like mailmanweb.db. If so, use > that one. > I found it, it's in a different directory: /var/lib/mailman3/web# sqlite3 mailman3web.db SQLite version 3.46.1 2024-08-13 09:16:08 Enter ".help" for usage hints. sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON site_id = django_site.id; ... ... 8|lists.example.com|7|7|Lists of Example|lists.example.com sqlite> The two working domains are first (...) . The problematic domain (renamed to lists.example.com) appears when I create it in Postorius. For me the only conspicuous is that the numbers are 8|.|7|7 while at the other two entries they are the same for the whole line: 2|.|2|2 and 4|.|4|4 . Flo

10 months, 1 week

[MM3-users] Re: Strange issue with bounce processing

by Brian Carpenter

On 12/25/20 10:07 PM, Mark Sapiro wrote: > On 12/25/20 6:36 PM, Brian Carpenter wrote: >> Dear List, >> >> First of all Merry Christmas to those of you that are observing it. >> >> I have an issue on one of my Mailman 3 servers. The bounce runner is not >> running, even after restarting mailman core. All the other runners are >> working fine. Here is the problem, after restarting it, a number of >> messages show up in queue/bounces from a single list. > > What happens if instead of restating core, you stop and then start it? Same behavior. > I don't really understand what's going on. The only messages which get > queued in queue/bounces/ are messages to the LIST-bounces address > delivered from the MTA, unless possibly they are somehow in queue/retry/ > and being retried. What do you see in the MTA logs? > The mail logs shows bounce notifications being sent out as per the list settings. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 7 months

[MM3-users] Unnecessary coded-words? [was: Shorted Subjects in Mailman]

by Stephen J. Turnbull

Mark Sapiro writes: > However, I did a test injecting directly to Mailman a message with > ``` > Subject: [SAV-LINUX] Notice from Sophos_Anti-Virus on server.example.com > [DEMO1] > ``` > on a German language test list with subject prefix [Janinsliste] and I > get the same result, I.e. the RFC 2047 encoded > ``` > Subject: > =?utf-8?q?=5BJaninsliste=5D=5BSAV-LINUX=5D_Notice_from_Sophos=5FAnti-Virus_on_server=2Eexample=2Ecom?= > ``` > so this is definitely a Mailman bug (or a bug in the underlying Python > email package. There seem to be other bugs here. First, I can't see any content-based reason for encoding this 100% ASCII content. I guess the list is set to always encode the subject prefix, and we just encode the whole field body if any part is encoded? Perhaps this is a quick workaround for the OP: set MIME-encoding for the subject prefix to "as needed". Second (and this is important because of RFC conformance!), the encoded word is over 75 characters. I've filed https://gitlab.com/mailman/mailman/-/issues/1021 for this.

4 years

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Henrik Rasmussen

Thanks, Mark. @Abhilash, any chance for an update to Docker-mailman to fix these known issues soon? https://gitlab.com/mailman/mailman/issues/256 https://gitlab.com/mailman/mailman/issues/359 @Mark, Mark Sapiro wrote: >>> In addition, the log contains other trace backs that might or might not associate to this problem: >>> >>> Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >> >> This may be a bug. The msgtext argument in >> 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed >> to be a string containing only ascii characters. I'm interested in >> what's in Mailman's >> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. >> You may be able to print the contents with Mailman's >> >> bin/mailman queue >> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck Isn't this a Mailman 2 command? What is the Mailman 3 equivalent? -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

8 years, 10 months

Search results for query "sapiro"