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

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/21/20 6:21 AM, r.woithe(a)callassoftware.com wrote: > Hello, > Version: > Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) > Mailman Core API Version 3.0 > Mailman Core Python Version 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0] > > But the Error was there allready before the update have been done. That means the Mailman-Core changed but the error persisted. What is the full traceback from this error? Mailman 3 has not supported Python 2 since 3.0 beta4. It is not clear what is invoking /usr/lib/python2.7/httplib.py, but if it is Mailman core, something is seriously amiss in the way it's installed. Even Postorius and HyperKitty have not supported Python 2 for quit some time. -- 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

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 6:05 PM, William Oliver wrote: > > So.. if I need to do it myself, can you point me to what file I need to > create/modify in the /opt/mailman/mm tree to set up the alias? Assuming you have Postorius working, just go to the Domains view, edit your domain and add an Alias Domain. Otherwise, you can do this in mailman shell, e.g. ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = x.example.com >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/6/22 10:21 AM, Michael Heseltine wrote: > > Btw, I the ProxyPass(Reverse) supposed to point at the URL listed in MAILMAN_REST_API_URL? Because that one is set to port 8001 in settings.py, and if I try to "telnet localhost 8000", i get "Connection refused". No. You probably don't need ProxyPassReverse at all, but it doesn't hurt and it should be the same URL as in ProxyPass. Port 8001 is Mailman core's REST server and that is what's in MAILMAN_REST_API_URL. Port 8000 is your wsgi server. The HowTo you're following tells you to install and configure gunicorn and it should be running and listening on port 8000 as it's what receives the proxied requests from Apache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Mailman and Mailman-web databases

by Mark Sapiro

On 4/5/23 02:31, Andrew Hodgson wrote: > > In these instructions we are using 2 databases for the Mailman and Django components. I guess it doesn't harm anything to have just one database for both but wondered whether it was a good idea to split eventually? It is mostly a matter of taste. There is no conflict in tables between Mailman core and Django, so it's perfectly OK to use a single database. Splitting the databases enables more separation between Django and Mailman core and would possibly make it easier to run them on different servers if that was desired. It would even allow using different database managers for them, although I don't know why one would want that. FWIW, this list's server uses a single database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Apache shows No Lists

by Mark Sapiro

On 5/23/23 17:47, ceo(a)sartrack.nz wrote: > > You should never have made the mailman so incredibly complicated with massive third-party software required, all of which did not install properly, and of which documention is either incomplete or plain wrong. > And with configuration files all over the place, which cannot be found...... anyway. I understand that installation of Mailman 3 is much more complex than was Mailman 2.1, but I think the installation doc at https://docs.mailman3.org/en/latest/install/virtualenv.html can be followed step by step. That is our intent and if there are issues with it we will correct them. Issues with installation of the Debian/Ubuntu packages and documentation or lack thereof is beyond our control and we would prefer you follow our recommended installation which we can support. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Configure new list via REST API - trying to add moderators

by Mark Sapiro

On 9/11/24 11:47, Andy Matthews wrote: > But looking at the docs for "Mailing list configuration" (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) I don't see anything named `moderator` The "Managing owners and moderators" docs (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…) indicate that we can perform add owners and moderators via a Python shell, but don't indicate that it's possible to do it via REST. Is this true? List members, nonmembers, moderators and owners are rosters. They are managed via REST at the /members endpoint. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for documention of owners and moderators. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 6/23/25 10:04, Cathryn McGuire wrote: > > Using Mailman 3 with Affinity web interface and we want to stop our members from sending to cc: or bcc: > > We've found the Header Filter and cc and bcc appear in it. Tried to configure it to "hold for moderation," but it hasn't worked. Partly because we don't understand what to put in the Pattern input box. I put in cc: because it requires something. The pattern box contains a regular expression that matches the value in the header that you want to apply the action to. What you want is a pattern that matches anything, e.g., `.*` to match zero or more occurrences of any character. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/8/25 08:26, dap1--- via Mailman-users wrote: > Thanks. That obviously means my list was never created: > > mysql> select id,domain from django_site; > +----+-------------+ > | id | domain | > +----+-------------+ > | 1 | example.com | > +----+-------------+ > 1 row in set (0.00 sec) > > I never got any errors trying to create it but at least now I know where to look when I do. Actually a better place to look in the db is select list_name from mailinglists; or in the file system ls -l /opt/mailman/mm/var/lists How did you attempt to create it? If in `mailman shell` did you `commit()`. The easiest way to create it is `mailman create my_list(a)my.domain` You don't need to specify any options as everything will be imported by `mailman import21` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Mark Sapiro

On 2/15/21 2:38 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 13/2/21 20:00, Mark Sapiro wrote: >> Also note that the translations on weblate only affect strings in the >> core code. The Mailman core templates are not currently translated in >> weblate and there are currently no Spanish language templates. One would >> need to create Spanish translations of all the templates in >> <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> >> >> and submit a merge request to add them to a mailman/templates/es/ >> directory. > > I downladed the templates and I'm beginning the translation process, but > I have a question. What language map has to be used? In my S.O. it's > ISO-8859-15 but I'm concerned it has to be UTF-8... Better ask before > having to do a remapping of the files after... They should be encoded as UTF-8. > It comes to my attention that three files have 0 bytes. The 0-byte files can either be left out of templates/es or put in as empty files. They are things for templates which are empty by default. Also, help.txt is unused and doesn't need to be translated. At one time it was intended to be the template for the response to the email `help` command, but it is not used for that purpose. Finally, although I said previously that the translated templates should be submitted as a merge request, that can still be done, but is not necessary. They can be translated in weblate. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and <https://gitlab.com/mailman/mailman/-/issues/825>. -- 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: MM3 Docker

by Mark Sapiro

On 1/7/19 1:18 AM, Odhiambo Washington wrote: > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Please help me understand what steps are missing and I will try to >> provide the information. > > > Okay. > > At the installation stage, you say the following: > "I already had some things set up in /opt/mailman including a git > subdirectory containing clones of the GitLab mailman, mailmanclient, > mailman-hyperkitty, hyperkitty, django-mailman3 and > postorius projects. On the third server I have added mailman-suite > because I use the settings.py from that project as the basis for mine." > > Please assume that the reader is a newbie to python3 virtualenv and give the > details of the commands they need to execute to (a) clone all the projects > needed > and (b) create the virtualenv. > > The next steps are: > mkdir /opt/mailman/mm > > Then you say "I then created a /opt/mailman/mm directory and within that a > Python 3.6 virtualenv" > What happens here is something that needs clarification, because you are > specific about "python3.6". > I have googled and realized that one has to be specific about the python > version they want to use in their virtualenv > as shown here -> > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > exact command to execute to create the /opt/mailman/mm/venv > exact command to execute to activate virtualenv I have added a comment to the page which I hope gives you what you want. I also added a section on templates instead of referring to a prior version of the page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

Search results for query "sapiro"