Search results for "Postorius" - Mailman-users

Re: Some doc updates from Fedora install experience

by tlhackque＠yahoo.com

Starting the suite - the server crashes with a deep traceback, but the root seems to be: MissingDependency: The 'whoosh' backend requires the installation of 'Whoosh'. Please refer to the documentation. So I ran (in the 2.7 venv) pip install Whoosh, got 2.7.4 Now I get: Request Method: GET Request URL: http://127.0.0.1:8000/ Django Version: 1.11.2 Exception Type: DisallowedHost Exception Value: Invalid HTTP_HOST header: '127.0.0.1:8000'. You may need to add u'127.0.0.1' to ALLOWED_HOSTS. Well, let's try loclhost:8000 instead And I get a 301 ... and eventually /postorius/lists/ Life. Everything is painfully slow, but life! email config issue. No way to request resending confirmation. Opened an issue. Now, where was that "email setup" for Django that I didn't find... ? Er, the doc says the e-mail should come to the "dummy backend" via `'django.core.mail.backends.console.EmailBackend'` But while the HTTP traffic is there, no sign of the e-mail. Hmmm. Well, `find` says there are 4 settings.py files: ```` ./postorius/src/postorius/doc/settings.py ./postorius/example_project/settings.py ./mailman-suite/mailman-suite_project/settings.py ./hyperkitty/example_project/settings.py # grep django.core.mail.backends ./postorius/src/postorius/doc/settings.py ./postorius/example_project/settings.py ./mailman-suite/mailman-suite_project/settings.py ./hyperkitty/example_project/settings.py ./mailman-suite/mailman-suite_project/settings.py:EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' ./mailman-suite/mailman-suite_project/settings.py: EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' ./hyperkitty/example_project/settings.py: EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' ```` Hmmm, must be "filebased.EmailBackend Next, we find ` EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails')` Ah - `./mailman-suite/mailman-suite_project/emails` and there, we find an e-mail with a confirmation URL! Amazingly, it's possible to sign in. And on that note, we end this episode of "Just reading the docs isn't quite enough"

9 years, 3 months

Re: 12/24 hour clock ?

by Per Jessen

Mark Sapiro wrote: > On 11/28/20 7:18 AM, Per Jessen wrote: >> Hi all >> >> at openSUSE we have recently migrated to mailman3, and we seem to be >> having a couple of teething issues: >> >> a) hyperkitty and postorius both seem to insist on using a 12 hour >> clock format, no matter what the user has set. Is there a way of >> changing it system-wide ? > > > This is a Django setting. Try > > TIME_FORMAT = 'H' > > in settings_local.py. See > https://docs.djangoproject.com/en/3.1/ref/settings/#time-format and >https://docs.djangoproject.com/en/3.1/ref/templates/builtins/#std:templatef… Thanks, will have a look. >> b) overriding the default set of footers - despite having set the >> template "list:member:regular:footer" to empty for a specific list, I >> am still getting the default footers attached. > > > How did you set the template to empty? I edited it in list settings under Templates, at first really just leaving it empty, then actually writing "empty" :-) > it works for me in Postorius from the HEAD of the gitlab branch and > should work with any Postorius >= 1.3.0 > > Note that when you set a template in Postorius, it sets the URI in > Mailman core for that template to > https://<HOST>/<PATH>/api/templates/list/<LIST-ID>/<TEMPLATE-NAME> > where the https://<HOST>/<PATH> part is the Django setting for > POSTORIUS_TEMPLATE_BASE_URL. Is that URI accessible from the Mailman > core host machine? I'll have to check, I only do the list admin, I don't maintain the installation. -- Per Jessen, Zürich (2.2°C) Member, openSUSE Heroes

5 years, 9 months

Re: Moderate mails from owner

by Malcolm Austen

On Thu, 21 Mar 2019 17:27:01 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/21/19 3:02 AM, Malcolm Austen wrote: >> >> 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. > > Isn't there a footer at the bottom of wach page with something like: > Postorius Documentation • GNU Mailman • Postorius Version 1.2.5 Unfortunately not Mark, Ancestry/RootsWeb have a history of tailoring Mailman heavily - and then deciding they don't have the resources to update to a new version :-( All there is on <https://lists.rootsweb.com/postorius/> is: RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community. Learn more. About Us | Contact Us | Rootsweb Blog | Copyright © 1997-2018 Ancestry | Corporate Information | Privacy | Terms and Conditions >> 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. > > New (non-)members always have Moderation set to List default. This means > their posts are governed by the applicable Settings -> Message > Acceptance settings. I suspect that everyone on the rootsweb system was mistakenly set to 'Default processing' when they were bulk-imported from Mailman2. > Setting a user's Moderation to Default Processing means that users posts > will not be held/rejected/discarded/accepted immediately based on > "Default action to take when a (non-)member posts to the list", but > additional checks will not be bypassed. See > <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html>. I will read that, and whatever else I can. >> Are my deductions correct? And if so, could this be the explanation of >> the issue detailed in this thread? > > Setting a user's Moderation to Default Processing (or Accept) would > bypass the list defaults and could be the explanation of this issue. > > When the non-member owner first posts to the list that address becomes a > non-member of the list. I.e. it is in the roster of known non-members of > the list and that non-member record could have had its Moderation set to > Accept or Default Processing at some point which would explain why the > posts are accepted. Thanks for the explanation and link, Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

7 years, 6 months

A new issue with installation

by Brian Carpenter

As usual, a new issue has arisen with installing Mailman 3. It seems Postorius and Hyperkitty want to install a module called cryptography. Which I am unable to install because of this: error: Can not find Rust compiler Question 1: Is cryptography a new addition to Hyperkitty/Postorius? Or was cryptography always included and something else is different about my installation process? "Building wheels for collected packages: hyperkitty, django-haystack, django-mailman3, mailmanclient, robot-detection, rcssmin, django-allauth, cryptography" Question 2: Will Hyperkitty/Postorius work without cryptography? I haven't proceed with this installation once I received the above error. Question 3: Are there any Mailman 3/Postorius/HK documentation that addresses with the installation of cryptography? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 7 months

Re: hidden list is hidden even to the owner

by Mohsen Masoudfar

As always: Thanks a lot! To answer your question, I am running 1.1.2-3 # apt search postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] Web user interface to access GNU Mailman3 This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, July 1, 2020 5:43 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: hidden list is hidden even to the owner [EXTERNAL EMAIL] On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… and if you are a member as well as owner of an unadvertised list, you will see it at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…. But (here's the tricky part) if you go to https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…, you will not see any unadvertised lists, not even ones you own. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 2 months

Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 3:47 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mark Sapiro writes: > > > 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, > > That's true from "outside", but there are internal links as well. For > example, in Postorius top page, the link to HyperKitty is .../archives. > I guess it's a good idea to grep the templates to see which URLS are > used. > > > > Now my question is about what could be adding the /mailman3. Is it > possible > > > that I installed something out of the ordinary? > > Besides mod_wsgi as Mark suggests and the uwsgi configuration, the > only thing I can think of is an Apache rewrite rule. It's not in the > Postorius and HyperKitty templates. > And I do not have any rewrite rules in my VHOST config: https://pastebin.ubuntu.com/p/9MRMJST9zZ/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 8 months

Re: Postorius performance with over 1000 pending users

by Mark Sapiro

On 6/8/19 9:13 AM, Nick W wrote: > I've got a couple things I need help with: The Symptom and The Problem. > > The Symptom: > > Postorius has gotten quite slow to load, taking more than 30s to load the > Subscription Requests tab. Having zero pending subscription requests (I'm on > v1.2.5), I started investigating unconfirmed subscriptions. > > I followed the commands from here[1] and got this: > > mailman shell -l your.list.id > util = getUtility(IPendings) > print(len(list(util.find(mlist=m,pend_type='subscription')))) > 1816 > > Wow, 1816 pending subscription requests. I can say for certain that my list is > not popular so these requests must have been submitted by bots. Let's get there > in The Problem. > > How can I "purge" this list? I'm willing to assume that none of these requests > are valid and would reject all unconfirmed user requests. mailman shell -l your.list.id util = getUtility(IPendings) for token, data in util.find(mlist=m, pend_type='subscription'): util.confirm(token, expunge=True) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

Docker Support Sucks

by Brian Carpenter

Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: ### The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: [webservice] configuration: /path/to/gunicorn.cfg and then in the gunicorn.cfg you can add [gunicorn] timeout = 90 graceful_timeout = 30 ### I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. After restarting docker-mailman, I can't access Postorius due to the following error: ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 160, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 84, in create_connection raise err File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 74, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 677, in urlopen chunked=chunked, File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 392, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/lib/python3.6/http/client.py", line 1254, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1300, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1249, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1036, in _send_output self.send(msg) File "/usr/lib/python3.6/http/client.py", line 974, in send self.connect() File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 187, in connect conn = self._new_conn() File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 172, in _new_conn self, "Failed to establish a new connection: %s" % e urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f96340a2e10>: Failed to establish a new con$ During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 449, in send timeout=timeout File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 725, in urlopen Commenting out "configuration: /opt/mailman/gunicorn.cfg" brings Postorius back up. I am really frustrated here. All I want to do is export a 3000 member list and I can't. Updating Mailman 3 using new Docker images shouldn't break a stable installation either. Please help. Brian

6 years, 2 months

Re: mm3 installation question

by Mark Sapiro

On 3/6/24 1:33 AM, Odhiambo Washington wrote: > On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Odhiambo Washington writes: >> >> > The odd thing is that the HOWTO that he followed never involves the >> > manipulation of any urls.py at all - it's not even mentioned at any >> > point. So obviously the issue is caused by something else and I >> > suspect something within Apache needs to be re-evaluated in the >> > guide. The HOWTO installs mailman-web which contains a urls.py. >> >> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" >> URI paths. It is quite unclear to me how this works at all with >> either the >> >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> >> version of urls.py or the reverse order version >> >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), This is an issue with Django. I'm not sure of the exact mechanism, but consider the first of the above two sets. If you go to the mailman3/ URL that gets redirected to the postorius/ URL. I.e. two paths that ultimately reference the same thing wind up considering the second path as the canonical path and redirecting the first path to the second. I was not initially aware of this when I added the postorius/ and hyperkitty/ paths to mailman_web/urls.py. I did this with the intent of making either set of paths work, and I added those paths after the mailman3/ and archives/ paths, and this version got released as mailman-web 0.0.8. That caused the recommended Apache config to fail because now the mailman3/ and archives/ paths were redirected to the postorius/ and hyperkitty/ URLs which are not in the recommended Apache config. I have since reordered the paths in mailman_web/urls.py, but that version isn't yet released. Thus the issue. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for some background. > My thinking then is that the documentation at > https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration > needs to be fixed by adding the missing bits, What needs to be done is a mailmab-web 0.0.9 release in PyPI. This will fix the issue. -- 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

Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Hi, I just set up a new Mailman 3 Suite installation (GNU Mailman 3.3.1 (Tom Sawyer)) on CentOS 7 using the virtualenv installation guide: https://docs.mailman3.org/en/latest/install/virtualenv.html I encountered a few issues, but I was able to resolve all of them, I think. All three components of the suite are up and running. The backend is a MariaDB database, the frontend is Apache with mod_wsgi. I can send messages to the server, and they are delivered to list members. One thing that I can't figure out is why I can't approve or reject messages that are held for moderation. In case it matters, I'm trying to moderate the list using the "root" account. Discarding works, but when I try to either accept or reject a message, there is a timeout. I can't find anything in mailman.log, mailmansuite.log or even /var/log/httpd/access_log. I managed to reject and approve messages manually using mailmanclient and the REST API, so the issue appears to be somewhere between Postorius 1.3.3 and mailmancore. Any ideas? -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

6 years

Mailman-users search results for query "Postorius"