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

[MM3-users] Re: Moderation for nested mailing lists

by Mark Sapiro

On 11/18/20 8:48 AM, peterbw(a)gmail.com wrote: > Hi Everyone, > > I have a list that has other mailing lists as members. When a non-member posts to this list I receive a moderation message. After approving the moderation message I then receive a lot of other moderation messages for the sub-lists that are members of the "top-most" list (since the non-member is not a member of any of the sub-lists). Is there any way to approve a message for moderation once and have all sub-lists automatically approve the message? That capability doesn't exist. If the poster were a member of the top-most list this issue <https://gitlab.com/mailman/mailman/-/issues/794>, currently not fixed, would apply, but for non-members, even that wouldn't do. If the same nonmembers post repeatedly, you could set the moderation action for their various non-member records to defer to accept their posts without moderator intervention, but for one-offs, this doesn't save any effort. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: HyperKitty failure

by Mark Sapiro

On 1/1/22 2:31 AM, horvath.arpad.szfvar(a)gmail.com wrote: > In the /var/log/mailman3/smtp.log I have at the same time: > > Jan 01 10:54:37 2022 (126980) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Jan 01 10:54:37 2022 (126980) Peer: ('127.0.0.1', 54816) > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) handling connection > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'LHLO yyy.hu' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'MAIL FROM:<horvath.arpad.szfvar.nospam(a)gmail.com>' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) sender: horvath.arpad.szfvar.nospam(a)gmail.com > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'RCPT TO:<test(a)lists.xxx.hu>' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) recip: test(a)lists.xxx.hu > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'DATA' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) Data: b'QUIT' > Jan 01 10:54:37 2022 (126980) ('127.0.0.1', 54816) connection lost > Jan 01 10:54:37 2022 (126980) Connection lost during _handle_client() This is all normal and expected for a post from horvath.arpad.szfvar.nospam(a)gmail.com to test(a)lists.xxx.hu. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Virtual alias + shell

by Mark Sapiro

On 5/26/23 9:51 AM, alopez(a)ac.upc.edu wrote: > Now I have created the mailing list with 'mailman create' but I get this error: > > postmap: warning: /etc/postfix/main.cf, line 65: overriding earlier entry: virtual_alias_maps=hash:/etc/postfix/virtual_alias/example.edu, hash:/etc/postfix/virtual_alias/example.org > > in my postfix file I have the following code: > > virtual_alias_maps = hash:/etc/postfix/virtual_alias/example.edu, > hash:/etc/postfix/virtual_alias/example.org, > hash:/var/lib/mailman3/data/postfix_vmap > > Should I remove hash:/etc/postfix/virtual_alias/example.edu, and hash:/etc/postfix/virtual_alias/example.org, ? In that case how I create alias not related to mailman? Without seeing the contents of those files, I can't say, but something in /var/lib/mailman3/data/postfix_vmap is conflicting with and overriding something in the other two files. Since the only things in /var/lib/mailman3/data/postfix_vmap are specific list addresses, they are probably what you want, and you could just ignore the warning, but you probably do want to examine and remove conflicts from the other two files. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/1/24 13:17, jkoral(a)luc.edu wrote: > Here is my plan for forwarding. Let me know if this looks correct. First off, I deleted the list off of the old server, so I am assuming that removed the alias as well. > > -Create new alias file in /var/lib/mailman/data/ called migratedaliases (this directory is where the aliases file is currently located, but under the aliases file). > -Edit /etc/postfix/main.cf and add the path to migratedaliases to alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases. After editing, it will look like this: alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases, hash:/var/lib/mailman/data/migratedaliases. > -Run newaliases command to update the aliases db. > -Then add the alias for the the migratedaliases file the way you posted above. > > Does that make sense? Yes On 10/1/24 13:19, jkoral(a)luc.edu wrote: > Or can I just put the forwarding alias in /etc/aliases? Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Re: List description as sender

by Mark Sapiro

On 09/14/2018 05:35 AM, Henrik Rasmussen wrote: > When receiving a mail from Mailman 3, the From: User name is the description of the list, like From: Long desription of the list for all members of certain project <project(a)lists.example.com>. > > Starting to get old, I recall something about a discussion we once had on http://mail.python.org/pipermail/mailman-users/, but I don't recall the reason for this and I can't find the discussion, so it might be something I dreamed. Specifically what messages are you talking about? The only case I see offhand where the From: is as you describe is in posts from an anonymous list. In any case, the list description is described in Postorius as "This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is." I.e., it shouldn't be a long description. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Emergency Moderation

by Mark Sapiro

On 5/25/20 8:21 PM, Allan Hansen wrote: > > Not sure what is the difference between ‘emergency moderation’ and ‘Hold for moderation.’ It appears redundant. `emergency` moderation is meant for emergencies such as flame wars on and otherwise open list. It trumps essentially everything else except pre-approval with and Approved: <password> header. It is not really intended as a "normal" list setting, although it can be used that way if you want to hold all posts. The default action "Hold for moderation" for members and non-members only applies to those whose individual moderation is set to "List default". To fully understand the difference, you have to know the order in which the various checks are applied. This is defined at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. You will see for example that emergency with a hold action comes before banned-address with a discard action. This means that if emergency is True, a post from a banned address will be held and not discarded, at least initially. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: MM3 to MM3 migration

by Mark Sapiro

On 1/31/23 13:34, David Newman wrote: > > Is this really as simple as building the new server, creating the same > lists on the new server, and rsync’ing the archives from the old server? > If not, how to do the migration? If you want to mirror the entire installation, you can dump the databases off the old server and import them to the new server. Depending on the installation, everything may be in one database or there may be separate ones for mailman core and mailman web. This is a little tricky because some of the tables have to do with Django stuff. To do only selected lists is much more difficult and there are no scripts that I am aware of. HyperKitty can dump a list's archive as a mbox which could then be used as input to hyperkitty_import on the new server to move archives, but there are no similar scripts to dump list settings, users, memberships, etc. in a format that can be imported. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Moderated unsub requests are not provided by mailman3 service

by Mark Sapiro

On 11/29/24 4:47 PM, Joachim Schrod wrote: > > The unsubscriptions requests are not shown in the web interface. I > suppose they should appear in the UI section "Subscription requests", > either as "Pending Approval" or "Pending Confirmation". (Frankly, I > don't understand the difference between these two options at all.) Subscriptions pending confirmation are those waiting for the user to confirm. Those pending approval are waiting for moderator approval. Unsubscription requests not being shown is https://gitlab.com/mailman/postorius/-/issues/332 which was fixed in Postorius 1,3.6 released over 3 years ago. Current release is 1.3.13. > System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; > both on Debian 11 (bullseye). > > I know that this is out of date; thus a definitive info "this is fixed > by now" is quite OK for me. (Debian upgrade is planned as the next > action after getting Mailman3 to work for that use case.) Yes, this is fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Re: Errors in MM3

by Mark Sapiro

On 4/7/25 04:08, Odhiambo Washington via Mailman-users wrote: > I am using uwsgi+APache2. > I am suddenly seeing hundreds of errors in my mailmanweb and uwsgi logfiles: > > 1. mailmanweb.log has hundreds of such lines: > [WARNING] [2025-04-07 13:01:50,162] [log] 317562 139768548886080 Method Not > Allowed (GET): /archives/list/ > kictanet@lists.kictanet.or.ke/message/YOPKCEWPHX4BV7U5MOTCVCNSWR2J2JOZ/vote ... > [WARNING] [2025-04-07 13:02:37,567] [log] 317562 139768548886080 Method Not > Allowed (GET): /archives/list/ > kictanet@lists.kictanet.or.ke/thread/MICNFIHVLOETVE4PXEDO5MBYWG7SN57H/favorite ... > > Any clues as to what needs to be done to mitigate the above? A web crawler is issuing GETs for those URLs which only allow POST. If you look in your web server logs, you can find the IPs they are coming from. If it's only a few, you can block them with a firewall or using access controls in your web server. If its a compliant web crawler, you may be able to use robots.txt to stop it. Also see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

[MM3-users] Re: Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py

by Mark Sapiro

On 5/24/25 5:04 AM, Stephen J. Turnbull wrote: > Christian Schneider writes: > > > In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the > > format did not change. > > I'm not sure what DATETIME_FORMAT is used for in Django 3.x. I doubt the OP is using Django 3.2. I suspect the URL <https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-DATETIME_FO…> came from a search result and the OP actually has Django 4.2 or 5.0 (django_mailman3 >= 1.3.12 requires django>=4.2,<5.1). Note that the doc for DATETIME_FORMAT for Django >=5.0 removes the note about USE_L10N = True and says "Note that the locale-dictated format has higher precedence and will be applied instead." Thus, with Django >= 5.0 I think the setting for DATETIME_FORMAT is ignored for output and the locale's format is used in all cases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

Search results for query "sapiro"