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

[MM3-users] Re: MM3+Python3.11

by Odhiambo Washington

On Mon, Mar 6, 2023 at 7:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/6/23 03:38, Odhiambo Washington wrote: > > Has MM3 been tested with Python3.11? > > Yes, but not with uWSGI which is not part of Mailman per se. > Are there any specific tests that are required to be done with respect to uWSGI and mod_wsgi? I could run some of those in my VM. I have switched from uWSGI to mod_wsgi and I don't have any errors - so far. Web UI running without issues in both cases. I believe I do not need to test anything with Gunicorn as that is what the Developers are using all the time :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: See list of subscribers

by Tom Yates

On Wed, 27 Mar 2024, Mark Sapiro wrote: > On 3/27/24 00:38, Tom Yates wrote: >> >> But a random subscriber, who's signed up and authenticated, when she >> visits the list page she sees her subscription, but no option to list the >> other subscribers. >> >> Is she looking in the wrong place? Do I need to open up more settings? Am >> I just being an idiot? > > This is https://gitlab.com/mailman/postorius/-/issues/369 fixed in Postorius > 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/770 Thank you enormously! I'd've looked for a bug myself, but I was by no means sure I was looking in the right place for the user list in the first place. -- Tom Yates - https://www.teaparty.net

1 year, 10 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Fri, Jan 27, 2023 at 9:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/27/23 05:53, Odhiambo Washington wrote: > > On Mon, Jan 23, 2023 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Note that when following > >> https://docs.mailman3.org/en/latest/install/virtualenv.html you create > >> /etc/mailman3/settings.py and it contains > >> ``` > >> from mailman_web.settings.base import * > >> from mailman_web.settings.mailman import * > >> ``` > >> to establish a base set of settings that can be augmented or overridden > >> in /etc/mailman3/settings.py. mailman_web.settings.mailman in turn > contains > >> ``` > >> HAYSTACK_CONNECTIONS = { > >> 'default': { > >> 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > >> 'PATH': "fulltext_index", > >> ``` > >> which is a relative path for fulltext_index and may need to be set to an > >> absolute path. > >> > > > > Mi Mark, > > > > I have read this page - > > https://docs.mailman3.org/en/latest/install/virtualenv.html and further > - > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-config > > - without clicking any external links. > > I still don't see the HAYSTACK_CONNECTIONS in the settings.py included > on > > that page. > > I am missing something obvious, no? > > > Please reread what I wrote above. HAYSTACK_CONNECTIONS is not in the > suggested settings.py but it is in mailman_web.settings.mailman and is > imported by the suggested settings.py. I have reread what you wrote now and I'm beginning to get the hang of this method. My observation is that it can only be _obvious_ to someone very familiar with Python config to decipher that *additional* settings *that can be augmented or overridden in /etc/mailman3/settings.py* can be obtained from: /PATH-TO/mailman_web/settings/{base|mailman}.py after they have noticed these two lines in the sample settings given in /etc/mailman3/settings.py: from mailman_web.settings.base import *from mailman_web.settings.mailman import * [At first instance, it is not obvious that mailman_web.settings.base and mailman_web.settings.mailman are actually paths in Python - which magically translates to mailman_web/settings/base.py and mailman_web/settings/mailman.py] Granted, I am a slow learner, and perhaps already so mixed up after reading the myriad HOWTOs for installing MM3 that are available online. I am tempted to say there are many like me who are likely to miss "where to obtain" other settings from. For example, my mind all along has been tuned to having a settings_local.py for overriding the settings.py. However, with this particular documentation, it would appear that everything is intended to just go into /etc/mailman3/settings.py. Is it possible to modify the documentation to somehow make it obvious (in a language that a layman can easily understand, that those two "import *" _DO establish a base set of settings that can be augmented or overridden in /etc/mailman3/settings.py_ and that those settings are in what file(s) ? I am not saying @Johannes Rohr <johannes(a)rohr.org> is a layman like me, but I think that is what hit him. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

[MM3-users] Re: Is there a simple way to remove the footer without having to add a customized template?

by Odhiambo Washington

On Wed, Jun 14, 2023 at 9:30 PM Mark London <mrl(a)psfc.mit.edu> wrote: > I simply want to have no footer for a mailing list. Can I do that > without having to create a customized template? Thanks. > I hope you are good at RTF-Ming :-) https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… Then again, @Mark Sapiro <mark(a)msapiro.net> will tell you the real gospel, or ask you to submit a patch :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 8 months

[MM3-users] Re: Trouble Installing Mailman3

by Henry Hartley

>> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> >> >> >> The next step in the instructions has me create >> >> /etc/mailman3/mailman.cfg. The first thing in that file is shown as: >> >> >> >> [paths.here] >> >> var_dir: /opt/mailman/mm/var >> >> >> >> Looking in /opt/mailman, there is no mm directory. Should that have >> >> been created, or is that something I need to create myself? >> > >> > You need to create it. I'll update the doc for that too. >> >> Actually, that's wrong. You don't need to create it. The first time you start Mailman core, it will be created. Excellent. Thanks. -- Henry

8 months, 2 weeks

[MM3-users] Re: How to subscribe members without sending unsubscribe message

by Flo

On 9/15/25 14:25, Mark Sapiro wrote: > On 9/15/25 14:11, Flo via Mailman-users wrote: >> Hi, >> >> I need to remove subscribed members without sending them an >> unsubscription message. Despite of my research I haven't figured out >> how to do this using the GUI. > > With Postorius, you can do it by first setting the list's Automatic > Responses -> Send goodbye message to No, and then doing the unsubscribe. > > From the command line, you can use the `mailman delmembers` command > which has options to control the sending of the admin notice and the > goodbye message. > Thank you. I don't why I don't find these things in Postorius easily? Flo

5 months

[MM3-users] Re: Search problem in 3.2.1?

by Mark Sapiro

On 10/22/19 7:51 AM, Mark Dadgar wrote: > Anyone seen this before? This is the result of any search query I run. I installed ElasticSearch as the search engine yesterday and this is the result. It is still indexing (large archives). How did you install ElasticSearch. What ElasticSearch version? This list uses elasticsearch 5.5.3 installed from the .deb as described at <https://www.elastic.co/guide/en/elasticsearch/reference/5.5/deb.html#instal…>. You can't use a later version because there are no python bindings for versions later than 5.x In addition we use the python bindings installed with `pip install elasticsearch5` <https://pypi.org/project>/elasticsearch5/ This version also requires haystack > 2.8.1 which we installed via `pip install -e git+https://github.com/django-haystack/django-haystack.git@master#egg=djang… Finally, we have these patches to the python bindings > --- elasticsearch5_backend.py.orig 2019-05-24 21:26:04.031867202 -0700 > +++ elasticsearch5_backend.py 2019-05-25 08:45:42.521374647 -0700 > @@ -28,6 +28,15 @@ > installation of 'elasticsearch>=5.0.0,<6.0.0'. \ > Please refer to the documentation." > ) > +# We need to override some elasticsearch_backend settings as string type is > +# gone in elasticsearch 5. > +from haystack.backends import elasticsearch_backend > +elasticsearch_backend.DEFAULT_FIELD_MAPPING = { > + "type": "text", "analyzer": "snowball"} > +elasticsearch_backend.FIELD_MAPPINGS["edge_ngram"] = { > + "type": "text", "analyzer": "edgengram_analyzer"} > +elasticsearch_backend.FIELD_MAPPINGS["ngram"] = { > + "type": "text", "analyzer": "ngram_analyzer"} > > > class Elasticsearch5SearchBackend(ElasticsearchSearchBackend): > --- elasticsearch_backend.py.orig 2019-06-16 10:21:42.441334321 -0700 > +++ elasticsearch_backend.py 2019-06-16 10:24:20.802264202 -0700 > @@ -78,8 +78,10 @@ > ) > > # Settings to add an n-gram & edge n-gram analyzer. > + # And, set max_result_window. > DEFAULT_SETTINGS = { > "settings": { > + "max_result_window": "100000", > "analysis": { > "analyzer": { > "ngram_analyzer": { The patch to elasticsearch_backend.py may require an even bigger value for max_result_window. The issue is the monthly Django hyperkitty - update_and_clean_index job runs into <https://stackoverflow.com/questions/41677198/result-window-is-too-large-fro…> > Mailman 3.2.1 from the debian packages in Ubuntu 19.10. > > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > Begin forwarded message: > > From: root(a)pdc-racing.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/search > Date: October 22, 2019 at 7:44:49 AM PDT > To: mark(a)pdc-racing.net > > Internal Server Error: /mailman3/hyperkitty/search > > UnboundLocalError at /hyperkitty/search > local variable 'search_exception' referenced before assignment > > Request Method: GET > Request URL: https://mail.pdc-racing.net/mailman3/hyperkitty/search?q=Ken ... > Traceback: > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in count > 79. return self.object_list.count() > > File "/usr/lib/python3/dist-packages/haystack/query.py" in count > 522. return len(self) > > File "/usr/lib/python3/dist-packages/haystack/query.py" in __len__ > 86. self._result_count = self.query.get_count() > > File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in get_count > 619. self.run() > > File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in run > 951. results = self.backend.search(final_query, **search_kwargs) > > File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in wrapper > 33. return func(obj, query_string, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in search > 524. _source=True) > > File "/usr/local/lib/python3.7/dist-packages/elasticsearch/client/utils.py" in _wrapped > 84. return func(*args, params=params, **kwargs) > > > During handling of the above exception (search() got an unexpected keyword argument 'doc_type'), another exception occurred: I suspect this error is because indexing is still in process. I'm not certain, but I think so. > File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py" in search > 90. request.GET.get('count'), > > File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py" in paginate > 72. objects = paginator.page(page_num) > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in page > 57. number = self.validate_number(number) > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in validate_number > 46. if number > self.num_pages: > > File "/usr/lib/python3/dist-packages/django/utils/functional.py" in __get__ > 35. res = instance.__dict__[self.name] = self.func(instance) > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in num_pages > 91. if self.count == 0 and not self.allow_empty_first_page: > > File "/usr/lib/python3/dist-packages/django/utils/functional.py" in __get__ > 35. res = instance.__dict__[self.name] = self.func(instance) > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in count > 84. return len(self.object_list) > > File "/usr/lib/python3/dist-packages/haystack/query.py" in __len__ > 86. self._result_count = self.query.get_count() > > File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in get_count > 619. self.run() > > File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in run > 951. results = self.backend.search(final_query, **search_kwargs) > > File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in wrapper > 33. return func(obj, query_string, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in search > 524. _source=True) > > File "/usr/local/lib/python3.7/dist-packages/elasticsearch/client/utils.py" in _wrapped > 84. return func(*args, params=params, **kwargs) > > > During handling of the above exception (search() got an unexpected keyword argument 'doc_type'), another exception occurred: > > > > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner > 41. response = get_response(request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 187. response = self.process_exception_by_middleware(e, request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py" in search > 100. if not isinstance(e, search_exception): > > Exception Type: UnboundLocalError at /hyperkitty/search > Exception Value: local variable 'search_exception' referenced before assignment This is a bug in HyperKitty. We've never encountered it, but the code at <https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/views/search.p…> only considers the whoosh and xapian backends and needs to be updated for elasticsearch. I've reported that at <https://gitlab.com/mailman/hyperkitty/issues/263>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

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

by Fabian A. Santiago

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. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

8 years, 3 months

[MM3-users] Re: Stalwart plugin

by Schulz

Thanks, it took some days to evaluate that - and the result is disappointing. While outgoing messages get routed to mailman, incoming messages get stuck in the created virtual users for the lists. Will post _if_ I have better news. Am 10. Juni 2025 um 17:27 schrieb "Mark Sapiro" <mark(a)msapiro.net mailto:mark@msapiro.net?to=%22Mark%20Sapiro%22%20%3Cmark%40msapiro.net%3E >: > > On 6/10/25 07:24, Jörg Schulz via Mailman-users wrote: > > > > > Hi all, > > I'm just reviewing Stalwart as a many-in-one mailing system. Did anybody yet succeed in plugging mailman into stalwart (the incoming bit seems to be difficult)? > > > See https://github.com/ewdurbin/stalwart-mailman > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >

5 months, 3 weeks

[MM3-users] Confusing order of checkboxes in Postorius

by Markus Grandpré

Dear list, dear Mailman3 developers, dear Mark Sapiro, in Postorius under "Mass operations / Mass subscribe" we find the order of the checkboxes confusing: 1. Pre confirm 2. Pre approved 3. Pre Verified 4. Invitation We think it would be easier for us and our mailing list administrators to understand the interaction of these settings if they were displayed in the following order: 1. Pre confirm 2. Pre Verified 3. Pre approved 4. Invitation as in our opinion "Pre confirm" and "Pre Verified" belong together more than "Pre confirm" and "Pre approved". Incidentally, a typing error has crept into the term "Pre Verified". It should read "Pre verified". Yours sincerely, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 4 months

Search results for query "sapiro"