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

[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

6 months, 2 weeks

[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

9 years, 10 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, 5 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

5 days, 8 hours

[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, 1 month

[MM3-users] Re: Postorius web issues after upgrading mailman 3

by Mark Sapiro

On 10/19/21 2:33 AM, Tibor Molnar wrote: > /var/lib/mailman3/web/static/hyperkitty > > /usr/local/lib/python3.8/dist-packages/hyperkitty/static/hyperkitty If you examine the source of your HyperKitty pages that have the issue, what do you see for the hrefs in the `<link rel="stylesheet"` tags in the <head> section. Also, I don't know if it is significant or not, but https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade says to run ``` (venv) $ mailman-web compress (venv) $ mailman-web collectstatic ``` I always run those in the other order. I suggest you do mailman-web collectstatic --clear mailman-web compress (or whatever your django admin command is) in that order and see if that helps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Turned on archiving and it is not working

by Mark Sapiro

On 6/9/22 12:47, bob B via Mailman-users wrote: > Mark, > > Thanks, So how do I check the version of mailman-hyperkitty? I thought that was the HyperKitty version 1.3.5. that was displayed in the web interface, but I assume that mailman-hyperkitty is something different? Yes. mailman-hyperkitty is a shim between Mailman core and HyperKitty. Your mail message has `` File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message` ``` The fact that it is line 154 says it is 1.1.0. You need to upgrade mailman-hyperkitty. I don't know how to do that in your Docker container. If you can run pip ``` pip install --upgrade mailman-hyperkitty ``` should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Some threads donw download

by Mark Sapiro

On 8/17/19 6:53 PM, Andrew Bernard wrote: > As a possible clue, I use the filesystem to store attachments. For some reason I found that using Postgres if they are stored in the database they don't download in the Hyperkitty view mode for a post, although listed as present. Is this perhaps <https://gitlab.com/mailman/hyperkitty/issues/247>, although I don't store attachments in the file system? > Could this be a bug relating to being unable to package up attachments if they are in the filesystem? In my case even though I can't retrieve the attachment via the link in the HyperKitty thread view, if I download the thread mbox, there is no issue and the attachment is there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: max_message_size parameter not working in mailman 3.3.1

by Mark Sapiro

On 6/12/20 7:12 AM, Shashikanth Komandoor wrote: > > One of our users has sent a mail with nearly 27M to one of the > lists running on Mailman 3.3.1. Though I have configured the parameter > related to the Maximum message size as '0' which I meant as no limit to the > size of mail, I observed the mail is not accepted and rejected with the > message "Message size limit exceeds". The max_size rule will not reject a message. Barring other issues, a message which is too big will be held, not rejected, so something else is going on here. Without more information such as the actual rejection message, I can't say more. -- 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: Can't send emails to list users

by Mark Sapiro

On September 19, 2023 2:36:21 PM PDT, Rob Passalacqua <rpassalacqua(a)westminsteru.edu> wrote: >I said 'default-mailing-pipeline' but I meant the 'default-posting-pipeline' in the 'alter messages' setting for the mailing list. Any ideas why using the default-owners-pipeline could have broken? was it ever supposed to work? The list setting for pipeline shows all known pipelines in the drop-down. It is probably a bug that it shows default_owner_pipeline as that pipeline is only for messages to owners and moderators, not for list mail, as in addition to skipping several handlers, it sets recipients to the list admins rather than the members. It isn't broken, but using it for list mail is a serious misconfiguration. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

2 years, 9 months

Search results for query "sapiro"