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

[MM3-users] Re: Header Filter madness

by Brian Carpenter

On 1/11/21 8:48 PM, Mark Sapiro wrote: > On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: >> I have a client whose header filters seemed to have stop working. No >> matter what I try, it seems none of their header filters are being >> applied. Other lists on the same server that use header filters, are >> working fine. This particular header is the subject header. I can >> duplicate their problem but only with their list. If I create the exact >> >> same header on a test list using the exact same subject line, the >> header >> filter does its job (moderate). Just not with this one list. > Is the poster's moderation action or the list's moderation action set to accept? Moderation action accept (rather than default processing) will bypass header filters an many other rules. > > The "Default action to take when a member posts to the list " is set to Default Processing for the problematic list. The list members moderation action is set to "List Default" for the problematic list. I duplicated the same settings using another list. Header filters works fine on the test list, does not on the production list. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

[MM3-users] Re: clearing pending db

by Morris Jones

On 8/8/25 11:48 AM, Mark Sapiro wrote: > On 8/8/25 09:59, Morris Jones wrote: >> >> But pendingdb.evict() doesn't seem to clear the list. For example, on >> one of my lists: >> >> >>> from mailman.interfaces.pending import IPendings >> >>> >> >>> from zope.component import getUtility >> >>> >> >>> pendingdb = getUtility(IPendings) >> >>> pendingdb.count() >> 5040 >> >>> pendingdb.evict() >> >>> pendingdb.count() >> 5040 >> >>> > > > pendingdb.evict() only deletes expired pendings, but by default > subscriptions pending confirmation expire after 3 days, but this is set > by pending_request_life in the [mailman] section of mailman.cfg. Have > you set that to a long time? > > On the other hand in Mailman 3.3.2, subscriptions pending approval were > pended with a 10 year lifetime. This was changed in 3.3.5 to a new > moderator_request_life setting (default 180 days). > > If you just want to delete all pendings you could do > ``` > pendingdb = getUtility(IPendings) > for pending in pendingdb: > pendingdb.confirm(pending[0], expunge=True) > # and if doing this in mailman shell > commit() > Perfect, thank you Mark. :) Mojo -- Morris Jones, Monrovia, CA

7 months, 4 weeks

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

by Flo

On 10/10/25 04:13, Mark Sapiro wrote: > >> I have deleted site - group - list now. And created the site again. If >> I go to 'view site' I see all mailing lists on the server and not only >> from this site/domain. This is the first thing where it shows >> irregularities. > > I'm not sure what you mean by `view site` but if you mean the VIEW SITE > link at the top of the Django admin UI, that is just a link to the host > site. I.e., if the Django admin page is https://www.example.com/admin/ > site/, its VIEW SITE link just goes to https://www.example.com/ and it's > always the same link regardless of what Django admin page you are on. > The url of the Django view is lists.example.com/mailman3/admin. The 'VIEW SITE' is in the header on the right side. It's a link to lists.example.com/mailman3 which apparently gets redirected to lists.example.com/mailman3/postorius/lists. The difference I am talking about is that lists.example1.com/postorius/lists shows only its mailing lists while lists.example2.com/postorius/lists shows all mailing lists on the server (ie. also mailing lists of example1.com) Flo

5 months, 4 weeks

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Abhilash Raj

On Fri, Nov 3, 2017, at 08:29 AM, Fabian A. Santiago wrote: > October 26, 2017 11:07 PM, "Mark Sapiro" <mark(a)msapiro.net> wrote: > > > On October 26, 2017 7:30:35 PM PDT, "Fabian A. Santiago" <fsantiago(a)garbage-juice.com> wrote: > > > >> That was it. Perfect. I manually modified my regexp map and it works > >> now. Excellent and Thank you. You're the man. Does mm3 ever refresh > >> those maps or only as I add new domains / lists? > > > > Only when you make changes to domains or lists. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> > > Sent from my Not_an_iThing with standards compliant, open source software. > > Mark, > > I've noticed that even simply restarting the mm3 components those alias > maps get rewritten and the problem returns until I can manually edit it. Yeah, that is true. Transport maps are re-generated everytime the container restarts. I don't think think there is any way around this right now :( > > -- > > Thanks, > > Fabian S. > > OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 5 months

[MM3-users] Re: mailman 3 adding extraneous /var/ to pid path?

by Barry Warsaw

On Sep 21, 2017, at 18:35, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote: >> On 09/21/2017 01:29 PM, Andrew Hodder wrote: >>> >>> I keep getting around this by creating symlinks to the pid file and then >>> the stop works, but it's getting silly. It seems like mailman just assumes >>> CWD + /var/ + master.pid must be the location. Once I realized this, I >>> found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since >>> it'd then add /var/master.pid). But that seems a little nonsensical. >> >> That is the normal expected behavior if devmode is enabled. Check your >> configs for this. > > I don't think `devmode` has anything to do with this, it only disables > sending out emails by accident and routes all emails to a pre-defined > address. Haven't looked at the relevant portion of the source so I might > be wrong. That’s correct. The [paths.*] sections are what control the file system layout, and [mailman]layout is what defines which of the [paths.*] sections to use. Cheers, -Barry

8 years, 6 months

[MM3-users] Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

I top post just for confirming that all your recommendations worked well and I am aplying them in the rest of servers Thanks a lot and all of you have a happy new year. El 27/12/22 a las 9:23, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 26/12/22 a las 23:57, Mark Sapiro escribió: >> ... >>> I don't want to put more noise in the list. But I'm confused because >>> I always updated via pip the apache mod_wsgi thinking is was needed >>> for my configuration. If it is not, I will stop updating it. >> >> Based on the above you ARE using Apache mod_wsgi and if you are still >> also running uwsgi as >> >> /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & >> >> that is unnecessary. > > It clarifies a pair of things. Thanks a lot. > > I'll try deactivating that in one of my servers (the "quieter" one) > and see how it goes. > > Again, thanks for your kind support. > > > > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 3 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 19:25, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:50 PM, Odhiambo Washington wrote: > > > Now that has clarified the matter for me. That even when I am logged out, > > the scripts do the neccessary > > to activate the venv to run things. > > > As mentioned before, a virtualenv is not like a container. It is only a > directory that contains among other things a bin/ directory with > activate scripts and easy_install, python, pip and wheel commands. > > When you activate a virtualenv in your shell, all it really does is add > a deactivate command, modify the command prompt and insert its bin/ > directory at the beginning of its PATH. > > What this means is whether or not a virtualenv is "active", running a > command from the bin/ directory in the virtualenv is using the virtualenv. > Thank you very much for the elaboration. What used to confuse me was the early stage documents which detailed how to run MM3 in a virtual environment - I am talking about the BETA days. I think from this point onward, I have the complete foundation information to move forward. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 2 months

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: > However, this is apparently not relevant because both the Member and > Non-Member actions are Hold. Thus, the post should be held unless it has > an Approved: header with the list's moderator_password attribute if > there is one, or it matches a Header filter rule with an accept action. At the risk of getting this really wrong - I have only limited MM3 knowledge - I will ask what is, I fancy, a closely related question ... My only experience of MM3 is with Ancestry's 'RootsWeb' installation. From the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't find anything to identify Postorius which is the only interface I have to the system. From symptoms seen and described by others, I have deduced that the Postorius admin-per-user moderation options of "Default processing" and "List default" mean that a user may be set (by default on the rootsweb system!) to use the system default moderation settings rather than the list default settings. Are my deductions correct? And if so, could this be the explanation of the issue detailed in this thread? Apologies if I'm barking up entirely the wrong tree, Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

7 years

[MM3-users] Re: Hyperkitty shows "<" as <

by Andreas Schamanek

Thanks Mark, Your support is unparalleled. On Tue, 4 Apr 2023, at 10:44, Mark Sapiro wrote: > On 4/4/23 09:53, Andreas Schamanek wrote: >> All "<" and ">" in old and new messages are shown as "<" and ">" in >> message views _however_ they are shown correctly in overview abstracts e.g. >> at //server/mm3/hyperkitty/list/testlist@server/latest > > I don't think I've ever seen this. Certainly it is not the case on this list > with either current messages such as those in this thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> I tried to dig deeper and realized that on my test list "<" and ">" are only mangled when they surround email addresses as e.g. in <user(a)example.net> (ie. < user @ example . net >) I see that lists.mailman3.org renders such addresses as e.g. <a target="_blank" href="mailto:user@example.net">user(a)example.net</a> whereas my Hyperkitty shows them as <user(a)example.nett> But I have not yet found the responsible code or setting since it seems this is related to the option to obscure addresses. Or is my Hyperkitty 1.3.4 simply too old? -- -- Andreas :-)

3 years

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Stephen J. Turnbull

Mark Sapiro writes: > One of the runners has died, most likely the `out` runner, but > possibly another. The missing messages are stuck in a queue. Do ``` > ls -laR /opt/mailman/core/var/queue ``` to see in which queue the > messages are. The runner that processes that queue is gone or > possibly stuck. I have seen "stuck", in a multisite installation where Mailman's smarthost ended up being about 1000 miles from Mailman. I'm not sure what the issue is (we fixed the DNS, not Mailman :-), but every once in the while the connection would hang. In that case nothing showed up in the log. The only symptoms were the buildup in the out queue and a stale connection to port 25 on the smarthost. If your smarthost is not "network far" from the Mailman host, this is quite unlikely from my experience, although Mark may know better. In any case, I think the best way to start diagnosis is to check the Mailman and MTA queues for stuck messages. Of course in normal operation you will often see messages in the queue, but long queues or messages older than a minute are 99% a dead or stuck queue runner. Steve

2 years

Search results for query "sapiro"