Search results for "Postorius" - Mailman-users

Re: displayed list with FILTER_VHOST

by Jens Günther

If you have domains registered here: https://.../admin/sites/site/ but not here: https://.../postorius/domains/ then all lists from other domains are displayed. Might this be the case with your situation? If you register the domain here: https://.../postorius/domains/ and have no lists, then no list is shown I think. Am 24.03.22 um 09:11 schrieb Stanisław Findeisen via Mailman-users: > What I also noticed is that in the Postorius Web UI:https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?...

3 years

Re: Time Zone Issue in Postorius

by Stephen J. Turnbull

Henrik Rasmussen writes: > > Fra: Mark Sapiro <mark(a)msapiro.net> > > It should be TIME_ZONE = 'UTC' > > > > Times passed from Mailman core are naive times, I.e. they don't have > > time zone info, but they are in UTC. Mark is saying that Mailman core converts to UTC. All times that come out of Mailman core in the relevant API are UTC. > As stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-django > seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), > to make sure, am I right to understand it as for Mailman, Danish time > should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? No, USE_TZ=True means "hey Django, you need to add a time zone to this datetime." And you use TIME_ZONE=UTC (exactly), because this variable is *not* the local time zone, it's the time zone that Postorius tells Django to add to datetime objects that don't carry their timezone with them. There is a setting somewhere else that tells Django what time zone should be used for I/O. Steve

3 years, 2 months

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"

7 years, 9 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

4 years, 2 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

4 years, 4 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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 3 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

5 years, 10 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>

6 years

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…

4 years, 9 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.:.

4 years, 7 months

Mailman-users search results for query "Postorius"