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

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/18/19 11:13 PM, Paul Arenson wrote: > Thank you Mark. I appreciate the response. Let me respond in two messages. The first is to confirm the rules for signing off for both types of used: > > The second is to clarify my problems with the signup procedure and how I might deal with it. (Mostly a very small change on your part and an explanation on my website for my users) > > 1) So, for both subscribers vi postorius only and hyperkitty users: > email to discuss-leave(a)list.tokyoprogressive.org (or > discuss-unsubscribe(a)list.tokyoprogressive.org) Yes, but you seem to have some confusion about how things work. Mailman 3 consists of several pieces. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/introduction.html…>. As it says there, Postorius and HyperKitty are separate, web based applications for list management and archiving respectively. Both of these are Django projects - Django is a Python web framework. What you refer to as hyperkitty users are actually Django Users. When you create and account and/or log in at Postorius or HyperKitty, you are creating/logging in to a Django account. When you are logged in, Django, and thus Postorius and HyperKitty know who you are. If you aren't logged in, they don't. > 2) Only for hyperkitty users, you can login, go to > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > and click the big red unsubscribe button. You need to be logged in for this so Postorius knows who to unsubscribe. > 3) Also only for hyperkitty users, log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/ and click the Delete > Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/delete This deletes your Django account, but does not affect your list memberships. > (Guessing that #3 will not unsubscribe the person and--if they have already done 1 or 2, failing to do number 3 is not going to be a big problem. Am I right?) That's right. The important thing is Postorius itself knows nothing about lists or list settings or list members. It gets and/or sets this information by communicating with Mailman core. You saw an example of this when you changed an archive from public to private. Postorius told Core to make it private and Postorius would then tell you it was private because it would get that information from Core. But, it required a daily cron job to propagate that setting to HyperKitty, so HyperKitty didn't get the memo until later. I hope this helps rather than adding confusion. -- 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: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

On 10/24/23 18:53, Mark Sapiro wrote: > On October 24, 2023 3:47:10 PM PDT, Thomas Ward via Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 10/24/23 18:29, Mark Sapiro wrote: >>> What if you try this with `mailman-web shell`? >>> >> Doesn't error on load, but can't access configs in order to see if my custom handler is present. Which Abhilash said has to be done in the mailman shell - as does the documentation. Mailman can't even start with this added. Which is a problem. > > I was confused. I should have said ` mailman shell`, not `mailman-web shell`. Insert "circular problem" here. When I DO NOT have the module loaded in the configuration, `mailman shell` works. Since that was functional, I went into the shell and executed this: > from mailman_customizations.hooks import MailmanCustomizations This worked fine, but obviously importing the class doesn't necessarily *activate* the class. So something is up with how I'm *supposed* to activate the plugin in the config, and we know that it's visible to Mailman in its shell, but it can't autoload it. So, again, not sure where to look next for debugging. Thomas

2 years, 3 months

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/24/22 00:00, Odhiambo Washington wrote: > > These are my files: > 1. urls.py > <CUT > > from django.conf.urls import include > from django.urls import re_path > from django.contrib import admin > from django.urls import reverse_lazy > from django.views.generic import RedirectView > > urlpatterns = [ > re_path(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), > re_path(r'^postorius/', include('postorius.urls')), > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > re_path(r'', include('django_mailman3.urls')), > re_path(r'^accounts/', include('allauth.urls')), > # Django admin > re_path(r'^admin/', admin.site.urls), > re_path(r'^mailman3/', include('postorius.urls')), > re_path(r'^archives/', include('hyperkitty.urls')), > ] > </CUT> You don't need all of those. ^postorius/ and ^mailman3/ are two different ways to access Postorius, and ^hyperkitty/ and ^archives/ are two different ways to access HypereKitty. You only need one of each, but having both is OK. > 2. apache.conf > <CUT> > ... > Alias /static "/opt/mailman/mm/static" > <Directory "/opt/mailman/mm/static"> > Require all granted > </Directory> > # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py > WSGIScriptAlias / /opt/mailman/mm/wsgi.py This will send every http request to mod_wsgi except for requests to /static. This is OK if there are no other web sites on this server and the only http requests are for Django related things. ... > I have tested with creating all those commented out aliases and that ended > up still giving me /mailman3/mailman3/* which I did not > like, although everything appeared to work. > I then ended up with only "WSGIScriptAlias / /opt/mailman/mm/wsgi.py" > and now when I type https://mm3-lists.kictanet.or.ke I end > up at https://mm3-lists.kictanet.or.ke/mailman3/lists/. Of course something > has appended "/mailman3" > So this has resulted in all URLs having /mailman3/ appended, except for the > /archives link. How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > Now my question is about what could be adding the /mailman3. Is it possible > that I installed something out of the ordinary? It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time (I now use gunicorn on all the sites I manage), but when I did I think I had WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py and all the URLs were like https://example.com/mm3/mailman3/..., https://example.com/mm3/archives/..., etc. -- 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: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Johannes Rohr

Am 24.01.2023 um 01:26 schrieb Mark Sapiro: > On 1/23/23 14:00, Johannes Rohr wrote: >> >> Am 23.01.23 um 21:08 schrieb Mark Sapiro: >>> e.g. >>> ``` >>> HAYSTACK_CONNECTIONS['default']['PATH'] = >>> '/opt/mailman/mm/var/fulltext_index' >> >> Thanks! Indeed. Including this line helps. It makes the error go >> away. So I guess the instructions should be amended. >> >> After that, for some reason, I have to re-index all lists, because >> initially, empty results were returned for any query, only after >> re-indexing to I get results. > > Did you adjust the path to point to your existing fulltext_index? yes, I did. > If not and if you had, I don't thing you would have needed to reindex. That's precisely, why I was surprised. > > The question is what changed so that the relative "fulltext_index" no > longer pointed to where the actual directory was. I don't think that anything had changed, I just don't think I never checked whether the fulltext search actually works and so I spotted this error rather late in the game. Thanks, Johannes > >

3 years

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/14/19 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > On my server are several virtual hosts running with different lists per > host. The appropriate webaddress is in general: > https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. > My domains: > [domain-1] starts with a b* > [domain-2] starts with a s* > [domain-3] starts with a t* > > If I use the webadress > https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… > and I do a click on the https-symbol in the address line of my browser I > get the secury-information " every thing is ok" and the > certificate-information is about the wildcard-certificate I just created > for the right domain. > > Different result is for the webadress > https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. > In this case I get an information like "you are using a wrong > certificate" clicking on the https-symbol references tot he certificate > of [domain-1] > > I set in my apache2 configuration a symbolic link to apache.conf in the > /etc/mailman3/directory and made this active. > > What did I wrong?? Your Apache config needs to define separate a VirtualHost for each domain, either by IP address or ServerName, and each VirtualHost points to its own SSL certificates. > If I set use_https to yes in mailman.cfg I get on the website for all > lists: > > postorius: Something went wrong > Mailman REST API not available. Please start Mailman core. > > In the logs I found … ... > mailman-web.log > ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", > line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, > in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, > in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, > in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, > in connect > self.sock = self._context.wrap_socket(sock, server_hostname=self.host) > File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket > session=session > File "/usr/lib/python3.7/ssl.py", line 853, in _create > self.do_handshake() > File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake > self._sslobj.do_handshake() > ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number > (_ssl.c:1056) Does your setting in settings(_local).py for MAILMAN_REST_API_URL have an https scheme? -- 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: MM2 -> MM3 Migration

by Odhiambo Washington

On Fri, Dec 30, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/29/22 23:17, Odhiambo Washington wrote: > > On Thu, Dec 29, 2022 at 10:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> The default without the since= option is to import only those messages > >> from the mbox which are newer than the newest message in the existing > >> archive which is exactly what you want. > >> > > > > So I ended up using this and I can see the list metrics indicating that > the > > last post was on 29Dec22, but > > I don't seem to be able to see those posts in the archives. > > > If Postorius list metrics show the last post was 29 Dec, that was a post > to the MM3 list and if it was archived, then running hyperkitty_import > without a since= option will not import any messages older than that. > Is there a way to delete the whole archive and re-import afresh? I checked the django-admin options for hyperkitty and did not see any such option. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: Internal Server Error: /archives/api/mailman/archive OperationalError at /archives/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1")

by Mark Sapiro

5 months, 2 weeks

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

by Mark Sapiro

On 1/27/23 23:53, Odhiambo Washington wrote: > > 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 * This is how it was always done in Mailman 2.1 and how it should have been done in Mailman 3's Django web UI from the start, but wasn't. MM 2.1 had mm_cfg.py which had ``` from Defaults import * ################################################## # Put YOUR site-specific settings below this line. ``` > [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] This is very basic Python. > 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. In that method you had the defaults in settings.py which at the end imported settings_local.py. This method has defaults in /PATH-TO/mailman_web/settings/{base|mailman}.py and those are imported at the beginning of settings.py which then has overrides. This is preferable because it allows things in settings.py like ``` HAYSTACK_CONNECTIONS['default']['PATH'] = 'some path' ``` to just override that one thing rather than having to redefine all of HAYSTACK_CONNECTIONS or import it from settings in settings_local.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) ? Again, this is very basic Python, but if you submit a merge request to update https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…, we'll certainly consider 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

[MM3-users] Re: Mailman3 Setup

by George R. Kasica

Thank you! Will take a look. — ===[George Kasica]=== 🇺🇦 On Jun 5, 2022, 10:29 -0500, Mark Sapiro <mark(a)msapiro.net>, wrote: On 6/5/22 06:26, George R. Kasica wrote: Hello: I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: Postfix Apache2 MySQL Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 8 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Odhiambo Washington

On Tue, Jan 31, 2023 at 9:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 11:43, Mark Sapiro wrote: > > > > add another section header > > > > Regular Expression Tables > > ------------------------- > > > > and change that text to > > > > Regular Expression tables are less efficient than hash tables, but they > > remove the additional dependency of having ``postmap`` command available > > to Mailman. If you want to use ``regexp`` or Regular Expression tables, > > then add the following to Postfix's ``main.cf`` file > > > This is now done. > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > That is now quite clear, but I still have one question and this is cosmetic (because Postfix isn't my MTA of choice. You can ignore it if it feels like spoon-feeding a Postfix admin. In the section: ``` https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… ``` .. the Postfix admin had to figure out whether they are using hash or regex tables and modify accordingly, right? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

Search results for query "sapiro"