Search results for "Postorius" - Mailman-users

Re: nextcloud as auth provider for postorius

by Mark Sapiro

On 12/2/23 00:56, Falk Hackenberger via Mailman-users wrote: > > Name mailman > redirection-URI https://website/mailman3/postorius/lists/ > Client-Identitifier: XXX > Secret **** The redirect URI should be something like https://website/accounts/nextcloud/login/callback/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

Re: Postorius List members

by Mark Sapiro

On 11/13/24 19:00, Alain D D Williams wrote: > > Is it possible to add delivery status to the summary where many users are > shown ? I find this (on mailman 2) to be very useful, ie get a quick overview of > what is happening to users. There is a merge request in process for this. See https://gitlab.com/mailman/postorius/-/merge_requests/953 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 5 days

Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Mark Sapiro

On 1/26/24 07:06, Stephen J. Turnbull wrote: > > I'm pretty sure it will install dependencies. I think (everything I > say below is based on reading the README.md from pipx's pypa.io repo, > so caveat installer) that the complexity that will arise is that (for > example) a naive approach like > > $ pipx install mailman > $ pipx install mailmanweb > $ pipx install postorius > $ pipx install hyperkitty > > will create 4 separate venvs with 3 copies of mailmanclient, 3 copies > of django-mailman3, and two copies of Django. But postorius and hyperkitty are dependencies of mailmanweb so only $ pipx install mailman $ pipx install mailmanweb should be required. This should put core in one venv and everything else in another without redundancy. > Besides the space > waste, there's also the small problem that mailmanweb won't have copies > of postorius and hyperkitty in its venv. But it will because they are dependencies of mailmanweb. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 4 weeks

Separating Lists by Domain

by brian＠emwd.com

I have successfully setup a second domain with my Mailman3 setup. I also created a list using the second domain. So I have two domains with one list each. The issue I see at this point is all of the lists are shown via Postorius regardless of the list domain used. Is it possible to have only the lists to show that are part of the domain being used to access? For example: http://domaina.com/postorius/lists/ Only listnames(a)domaina.com show up. http://domainb.com/postorius/lists/ Only listnames(a)domainb.com show up. Right now both domaina AND domainb lists showup regardless of the domain being used to access Postorius. The same goes for Hyperkitty as well. Brian

5 years, 11 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hey Everyone, > > I am pleased to announce new stable releases for Mailman Core, Postorius, > Hyperkitty. > > These include both new features and bug fixes. Complete change log for > each components: > > Mailman Core 3.3.3: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… May I ask if this is a typo? I am asking because Mailman Core 3.3.4 was announced on Marc 22nd. So is this new one version 3.3.3 or 3.3.5? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

3 years, 6 months

Re: Hyperkitty performance problem

by Mark Sapiro

On 11/22/24 00:37, Odhiambo Washington via Mailman-users wrote: > On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: >> >> Are Mailman3/Postorius and Hyperkitty supposed to run in separated >> databases, or are they supposed to use the same database? ... > > The official documentation specifies two DBs - one for Mailman Core and the > other for Mailmanweb. > As far as I know, there are no conflicts in the tables so you could use the > same DB for both. And the mailmanweb DB is for HyperKitty and Postorius. I know of no doc suggesting separate databases for HyperKitty and Postorius and in fact accomplishing that would require separate Django instances for HyperKitty and Postorius. I.e., Postorius, HyperKitty and django-mailman3 are all Django applications and use the database configured in Django's settings. Mailman core is separate and uses the database configured in mailman.cfg. As Odhiambo says, there are no table conflicts between these databases so they can be either the same database or separate databases as you wish. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 days, 20 hours

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 5:41 PM, Ruth Ivimey-Cook wrote: > >>> My reason for thinking, in my original post, that the wrong host >>> address is being used is that the ConnectionError above contains >>> 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only >>> present as >>> the listen address on the core web service and does not appear in >>> the >>> config for postorius. >> The ConnectionError above comes from requests.request (docs at >> <https://requests.readthedocs.io/en/master/>). Client only provides a >> URL in the call to request and the URL is the baseurl + the path and the >> baseurl is MAILMAN_REST_API_URL which you have as >> http://greyarea-post:8870. Entries above have >> http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? >> >> I suspect a DNS lookup issue. How does greyarea-web1 resolve >> greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS >> rather than relying on /etc/resolv.conf and/or /etc/hosts. > > No, ignore that... I edited the FQDN down to the hostname in the email > for simplicity, but even if it was in the log the hostname does map > properly (i.e. host greyarea-post and host greyarea.cam.ivimey.org > return the same thing). Is the above a typo. You are saying greyarea.cam.ivimey.org. Did you mean that or greyarea-post.cam.ivimey.org as in the http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 log messages? > In referring to the ConnectionError from: > > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > > if you reconstruct the url passed in it was presumably: > > "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk" I don't think so. I think it was http://greyarea-post:8870/3.1/domains/ch-bc.org.uk and requests.request couldn't resolve that to the correct IP. If you look at Mailman client <https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/re…> you'll see it makes the URL from the baseurl passed to the instantiation of the Connection class which occurs at <https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/cl…> which in turn is called from Postorius at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…> which makes the baseurl argument from '%s/3.1' % settings.MAILMAN_REST_API_URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

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?...

2 years, 8 months

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

2 years, 9 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, 5 months

Mailman-users search results for query "Postorius"