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

[MM3-users] Re: Issue with Held Messages

by Mark Sapiro

On 08/20/2016 07:15 AM, Jean-Luc Wasmer wrote: > On 2016-08-20 02:08, Mark Sapiro wrote: >> >> If you look at the user's options when logged in as a list owner, you >> should see an additional "Administration options" section below those >> with a "Moderation" setting. What is that set to? > > I log in as the admin user created with "mailman-web-django-admin > createsuperuser", I created the list logged in as this admin user and > its email address is displayed in the "Owners" sections of the "Members" > tab. > I only have that 1 other member and when I check it settings, the last > section is "Avoid duplicate copies of messages?" and then there's the > "Save" button. You probably have an older version of Postorius than I have. I am a few weeks behind at the moment, but I basically am running the heads of the master branches as described at <https://wiki.list.org/x/17891998>, so I am unable to see what you see. Here's an example mailman shell session to see what various member moderation actions are. > mailman@mail:/opt/mailman/mailman-bundler$ bin/mailman shell mm3_test(a)python.org > Welcome to the GNU Mailman shell > The variable 'm' is the mm3_test(a)python.org mailing list > >>> list(m.members.members) > [<Member: None <barry(a)python.org> on mm3_test(a)python.org as MemberRole.member>, <Member: Mark Sapiro <mark(a)python.org> on mm3_test(a)python.org as MemberRole.member>, <Member: mark(a)msapiro.net on mm3_test(a)python.org as MemberRole.member>, <Member: gvanrossum(a)gmail.com on mm3_test(a)python.org as MemberRole.member>] > >>> m1 = list(m.members.members)[1] > >>> m2 = list(m.members.members)[2] > >>> m1.moderation_action > <Action.defer: 4> > >>> m2.moderation_action > <Action.accept: 3> >>> 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."). >> >> >> What happens if you clear the Acceptable aliases box before saving? > > Then I get "The settings have been updated." after pressing "Save changes". > But if I navigate elsewhere and come back, the brackets are back in the form. This is <https://gitlab.com/mailman/postorius/issues/51>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 1 month

[MM3-users] Re: Importing mbox files into hyperkitty since date

by Mark Sapiro

On 6/20/19 3:08 AM, andrew.bernard(a)gmail.com wrote: > Well, reading the hyperkitty command source code, looks like it uses dateutil.parser, which shoudl read pretty much any date format (?). > > This is what happens: > > $ django-admin hyperkitty_import -v 2 -l jackrail(a)list.jackrail.org --since "2010-01-01 00:00Z" /tmp/jackrail(a)list.jackrail.org-2019-07.mbox > > CommandError: No such file: 00:00Z This appears to be a bug in Django's BaseCommand class which somehow separates '--since "2010-01-01 00:00Z"' into '--since 2010-01-01' and '00:00Z' despite the quotes. As a workaround, you can use '--since "2010-01-01/00:00Z"' which doesn't contain the problematic whitespace and which is acceptable to dateutil.parser.parse(). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: mailman import21

by Mark Sapiro

On 10/11/20 7:41 AM, Brian Carpenter wrote: > Does the import21 script also import custom templates? No. > Are these custom > templates contained in the config.pck file? No. They are in the same MM 2.1 directory as the config.pck, but in a sub-directory for the language code, i.e. lists/LISTNAME/LC/ > Are there any known issues > with the importing of mm2 templates into a mm3 environment? The replacements are different. i.e., things like %(email)s and %(listname)s become $user_email and $short_listname. Also, there are some MM 2.1 templates that have no MM 3 equivalent. 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Question about "envelope-from" header

by Mark Sapiro

On 9/12/23 10:45 PM, Stephen J. Turnbull wrote: > Stephen Daniel writes: > > > Will bounce processing still work? > > I think so. Pretty sure bounce processing on the bouncing side > doesn't care who the envelope sender is, it is based on the RFC 822 > sender, which is the Sender header field if set and the From field if > Sender is not present. Actually, I think all modern MTAs will return DSNs (bounces) to the envelope sender (MAIL FROM address)[1] which for list mail is the, possibly VERPed, listname-bounces address. If this is altered to a different address, bounce processing won't work. [1] See https://www.rfc-editor.org/rfc/rfc5321.html#section-4.4 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/23/24 13:23, Gerald Vogt wrote: > > I don't quite understand the relevance of the user accessing the > localhost tcp port. Any local user can do that. I am trying to duplicate what Mailman does in an attempt to find the issue. > I can access the template content with > > curl > http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… > > as well as > > curl > http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… > > as any user on the mailman server. How about ``` curl -A 'python-requests/2.32.3' http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… ``` as the Mailman user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Python 3.13 compatibility

by Mark Sapiro

On 1/23/25 14:08, peter--- via Mailman-users wrote: > > Hi Folks, > I'm running the Debian-packaged mailman3 (version 3.8) which is a > little behind the current 3.9 release ... > Debian is now shipping Python 3.13 in 'sid'. > > https://docs.python.org/3/whatsnew/3.13.html#id4 > says: > Remove the ability to use Path objects as context > managers. This functionality was deprecated and has had no > effect since Python 3.9. (Contributed by Barney Gale in > gh-83863.) > > As a result, I'm hitting tracebacks from many operations where > pathlib.Path objects are used as context managers, like this one: This is https://gitlab.com/mailman/mailman/-/issues/1190 fixed for Mailman 3.3.11 by https://gitlab.com/mailman/mailman/-/merge_requests/1309 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: user self registration

by Mark Sapiro

On 12/7/25 07:46, Christian Stalberg via Mailman-users wrote: > Spammers have been registering and not subscribing. I want to turn off the > user self registration at https://lists.ccalternatives.org/mailman3/ . > > I edited /etc/mailman3/settings.py adding ACCOUNT_ALLOW_REGISTRATION = False > and restarted the services, but the ' Sign Up' option remains. I assume > /etc/mailman3/settings.py is my active settings file. > > What am I doing wrong? Web searches may find reference to a django-allauth setting ACCOUNT_ALLOW_REGISTRATION, but this setting doesn't exist in current django-allauth The setting you want is ACCOUNT_ADAPTER = ‘django_mailman3.views.user_adapter.DisableSignupAdapter’ See https://docs.mailman3.org/en/latest/faq.html#how-to-disable-signup or https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail… -- 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: Installation Wooes

by Mark Sapiro

On 5/3/20 8:43 PM, Samir Faci wrote: > Inline. > > On Sun, May 3, 2020, 20:32 Mark Sapiro <mark(a)msapiro.net > <mailto:mark@msapiro.net>> wrote: > > You are sending from a remote machine 198.199.98.177 to a presumably > remote domain domain.com <http://domain.com> so relay access is > denied as it should be. > > You need to add 198.199.98.177 to mynetworks in Postfix. > > > I can but domain.com <http://domain.com> is basically my Gmail I just > regex-ed the logs. If that's the fix is have to add every recepients > domain to mynetworks. You absolutely don't want to do that. The log entry is confusing. Between your munging domains and my MUA adding mailto: links to every email address, it's a mess. Let's try again: May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com>: Relay access denied; from=<booh-bounces+csgeek=domain.com(a)lists.domain.org> to=<csgeek(a)domain.com> proto=ESMTP helo=<[127.0.1.1]>. This says Postfix received a RCPT command from 98.199.98.177. It looks like it comes from Mailman, i.e., the envelope sender loogs like a Mailman VERPed address <booh-bounces+csgeek=domain.com(a)lists.domain.org> for a message to <csgeek(a)domain.com> and that is the envelope recipient and the sender identified itself in EHLO as [127.0.1.1]. So Postfix thinks it is asked to relay from 98.199.98.177 to domain.com. Note that 98.199.98.177 is a Comcast network IP. It has nothing to do with gmail. So is the connect comes from Mailman on the Postfix machine, why does Postfix think it comes from 98.199.98.177. That's the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 12/30/22 03:25, Jan Eden via Mailman-users wrote: > > On minor issue: All user names with > non-ASCII characters appear with quoted-printable encoding (e.g. > =?utf-8?q?J=C3=BCrgen?=). Is there a way to output UTF-8 instead of QP? I just created https://gitlab.com/mailman/mailman/-/issues/1048 for this. I think this patch ``` --- a/src/mailman/commands/cli_members.py +++ b/src/mailman/commands/cli_members.py @@ -104,10 +104,10 @@ def display_members(ctx, mlist, role, regular, digest, if nomail is not None: if member.delivery_status not in status_types: continue - if email_only: + if email_only or not address.display_name: print(address.original_email, file=outfp) else: - print(formataddr((address.display_name, address.original_email)), + print(f'{address.display_name} <{address.original_email}>', file=outfp) ``` (line may be wrapped) will fix 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, 9 months

[MM3-users] Re: postfix_lmtp doesn't exist

by Mark Sapiro

On 6/17/26 5:09 AM, Flo via Mailman-users wrote: > > ModuleNotFoundError: No module named 'nntplib' > > Did I forget something to install? I can't see where I made a mistake > looking to the documentation. nntplib was removed from the Python standard library as of Python 3.13. For Python 3.13+ you need the standard-nntplib package from PyPI. This is fixed for the next release of Mailman core by <https://gitlab.com/mailman/mailman/-/merge_requests/1348>. In the mean time, you can do, with your venv active if applicable, ``` pip install standard-nntplib ``` Also, Mailman core is not yet compatible with Python 3.14 because it depends on aiosmtpd which is not yet compatible. See <https://gitlab.com/mailman/mailman/-/merge_requests/1392>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

Search results for query "sapiro"