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

[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

5 years

[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

8 years, 8 months

[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

5 years, 8 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

4 years, 11 months

[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.

1 year, 7 months

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Mark Sapiro

On 1/9/25 06:07, Alain D D Williams wrote: > > My request is to make finding content easier. Possibilities: > > • On the summary (left hand side) put the number of posts after the month name > > • Only show months (left hand side) where there are any posts This is a long standing issue. See https://gitlab.com/mailman/hyperkitty/-/issues/79 > For an example see: > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… The style of this page is not standard. Is this a downstream packaged HyperKitty? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2025/1/ for the standard page or https://mail.python.org/archives/list/mailman-i18n@python.org/2024/12/ for one with no posts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 11:53 AM, "Jörg M. Schulz" wrote: > and: When I put the stanza >>> [language.en] > into the mailman.cfg, the service doesn’t restart: > … > PermissionError: [Errno 13] Permission denied: '//var/templates' > > somehow the template path gets lost by defining this section. Possibly, somewhere the path to the .en / language templates must be set. How, where? How are you restarting the service? Is is running as the Mailman user? There are issues that can occur if the service has run as root and is then restarted as the Mailman user. Some files get created by root which then can't be read/written by the Mailman user after restart. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/26/20 10:13 PM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > But I am having a final query over this issue. Out of the two hyperkitty > records I observed in the database, I am confused which record do I need > to remove directly from the database? Because I doubt still there is one > more list with the same style i.e. with two hyperkitty records. If there are multiple rows in the listarchiver for the same `mailing_list_id` and archiver `name`, you can safely delete all but one of them. It doesn't matter which ones you delete. They should be identical except for the `id`. -- 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: bypassing rules on an individual basis

by Mark Sapiro

On 4/4/25 13:03, via Mailman-users wrote: > > And, out of curiosity, why is the "accept_these_nonmembers" collection not applicable here? Is its use deprecated or is there a very particular use case for it? *_these_nonmembers is an artifact from Mailman 2.1 and its use in Mailman 3 for individual email addresses is deprecated in favor of setting the moderation action for a non-member. It is still useful in Mailman 3 for regexps and the @fqdn_listname functions. However, It can still be used with an individual email address, but it doesn't work for you because a match in accept_these_nonmembers is equivalent to a moderation_action of Defer, not Accept. This is consistent with how it worked in Mailman 2.1. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Mailman web Stopped working after upgrade

by Mark Sapiro

On 3/3/20 1:26 PM, David Krantz wrote: > Hi, > > I tried psycopg2-binary and a few other rehashes of that. Now I got it > working by downloading the source for psycopg2 manually and building > it myself, then I installed it into my venv like any other self-built > package. https://pypi.org/project/psycopg2/#files I'm glad you got it working. I think installing psycopg2-binary with pip should have worked, so I suspect there was some residue of psycopg2 somewhere in the search path ahead of the psycopg2-binary that was the issue. > I run mod_wsgi in Apache so I thought it should be enough to restart > Apache. Yes, that should be sufficient. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

Search results for query "sapiro"