Search results for "Postorius" - Mailman-users

Re: Separating Lists by Domain

by Mark Sapiro

On 5/1/20 9:59 AM, Sven Seeberg via Mailman-users wrote: > >> Is it possible to have only the lists to show that are part of the >> domain being used to access? This is the setting FILTER_VHOST = True. It causes problems in Postorius and doesn't work well in HyperKitty. See <https://gitlab.com/mailman/postorius/-/issues/394> and <https://gitlab.com/mailman/hyperkitty/-/issues/254>. Both these issues are fixed for the next releases of Postorius and HyperKitty which should be out later this month. > On > top of that another question: is it possible to add user accounts that > can manage lists for one domain but not other domains? We already have the concept of domain owner, but implementation of domain owner permissions is not yet done. -- 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

Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by IEM Network Operation Center (IOhannes m zmölnig)

thanks again, Mark, for your detailed answer. On 3/15/22 17:21, Mark Sapiro wrote: > See https://gitlab.com/mailman/mailman/-/issues/901 > > You can add something like > ``` > Alternatively, you can confirm by going to the URL > > https://$domain/mailman3/lists/$list_id/confirm/?token=$token > ``` hmm. the list-url (e.g. where you can subscribe to the list) for my instance looks like https://$domain/postorius/lists/$list_id/ (that is: it spells "postorius" rather than "mailman3"). so i guess the URL should be https://$domain/postorius/lists/$list_id/confirm/?token=$token, which unfortunately returns 404. also, my postorius/urls.py does not contain an url-pattern for "confirm", unlike the current one as found on <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83> so i guess this was not possible yet with postorius 1.2.4 > to the list:user:action:subscribe template. Note that `$domain` may not > be appropriate here because it is the email domain which may not be the > web domain. > >> also: the confirmation mail says that the subject must be kept intact. >> however, i noticed that the actual "From" address of the confirmation >> mail already contains the token. > > The current template > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l… > doesn't say that. yes. the *current* template. but not the template that came with mailman3 3.2.1 > >> finally: what else is required to approve the confirmation? will the >> sender's email-address be taken into account? (e.g. if they subscribed >> "foo+mylist(a)example.com" but send the confirmation-reply from >> "foo(a)example.com", will that still work? > > > Yes. Only the token is required. > cool thanks. together with the not-yet-expired tokens, i think i can create some ad-hoc web-service that translates URLs to confirmation replies. mfd IOhannes

3 years, 4 months

Re: domain owner role

by Abhilash Raj

> On Sep 1, 2021, at 7:52 AM, Rainer Herbst <rainer.herbst(a)aip.de> wrote: > > Dear all, > > recently, I have added one account to a domain as domain owner. I did expect the new owner to see all lists in that domain in Postorius, but he sees no list at all. > > Is this the way it should be? How can I add administrators able to perform administrative tasks on all lists in Postorius? > Domain owner role isn’t currently very useful in Postorius, they can so far only edit the domain templates. If you want to grant the user ability to manage lists in Postorius, you’d have to grant the user superuser privileges which will allow them to manage all the domains. I was thinking there is an open issue for it, but apparently there isn’t one so I opened a new one. https://gitlab.com/mailman/postorius/-/issues/533 -- thanks, Abhilash Raj (maxking)

3 years, 10 months

Re: Multiple domain problem

by Mark Sapiro

On 2/10/23 01:43, Lars Bjørndal wrote: > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: >> On 2/9/23 13:21, Lars Bjørndal wrote: >>> >>> If I connect to example2.com, the title is example2.com, without the >>> preceding List index. And the body says Page not found. >> >> >> What's in the browser's address bar for that page? > > It's https://example2.com/mailman3/lists/ And when you get the Page not found, is it a browser 404 error or a Postorius error page? > >> What's in Postorius domains view? > > I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). Why are you going to http://localhost:8000/? You should be able to see the domain's view at https://example1.com/mailman3/domains/ or https://example1.com/mailman3/domains/ or by just clicking Domains in Postorius top nav bar. > Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. Again you should be able to go to https://example1.com/admin or https://example2.com/admin. If these don't work, you need to add directives in your web server to proxy them to http://localhost:8000/admin -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Postorius: Dropdown menus problem

by Thor Atle Rustad

In my latest iteration I installed Maxking docker-mailman by downloading the files (git clone https://github.com/maxking/docker-mailman.git) and building the images myself by modifying docker-compose.yaml like this: services: mailman-core: container_name: mailman-core build: context: ./core dockerfile: Dockerfile-alternate Same thing goes for mailman-web. Only modification was changing the uid/gid in the images to make it equal to the local user on the host. Now a few things are not working. In Postorius <server>/postorius/lists/<listname>) there is a menu row (Subscription requests|Held messages|Members|Settings|Mass operations|Banned addresses etc). The two items Members and Mass operations should normally show a drop-down menu when clicked, but here nothing happens. Same thing for the Admin menu (can't access Logout, amongst other things). In Hyperkitty, messages are not loaded properly. In various places on the page I see spinning discs indicating something is loading, but nothing happens. Any ideas? Thor

7 years, 7 months

Issue with Held Messages

by Jean-Luc Wasmer

Hi, No matter what action I set for member posts (Hold for moderator, Reject) they are always delivered. When I tried from a non-member email address, the message got held but when I try to see it I get a Server Error (500) page. The log files shows: ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server Error: /mailman3/lists/test.mydomain.com/held_messages Traceback (most recent call last): File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/generic.py", line 67, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/auth/decorators.py", line 81, in wrapper return fn(*args, **kwargs) File "/usr/local/mailman/mailman-bundler/eggs/Django-1.8.14-py2.7.egg/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/usr/local/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/list.py", line 387, in get held_messages = utils.paginate(request, self.mailing_list.held, 20) File "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", line 443, in held moderation_reasons=entry['moderation_reasons'], KeyError: u'moderation_reasons' Cheers, Jean-Luc

8 years, 11 months

Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Jonas Meurer

Abhilash Raj: > On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: >> Hey Abhilash, >> >> Thanks a lot for your work on mailman3! >> >> Abhilash Raj: >>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. >>> >>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that >>> I can think of is non-member management in Postorius. >>> >>> New releases are available on PyPI[3][4]. >> >> For earlier releases, you provided GnuPG signature files to >> cryptographically verify that the release files were not tampered with. >> >> I couldn't find such signature files for the two latest releases. Would >> you mind adding them? When packaging for Debian, I prefer to check the >> GnuPG signatures before uploading new releases. Also, the signature >> files get uploaded to the Debian archive as well so they can be checked >> by everybody. That way we can cryptographically proof that the Debian >> package is based on the original tarball that got packaged and signed by >> upstream. > > > Ah, sorry about that. I completely forgot about that. > > I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. Thanks a lot, that would be awesome. I'll wait for it before doing the Debian package uploads. Just to let you know: we're close to soft freeze in Debian, so in order to get those uploads into the next stable release (Buster), they'll have to be uploaded rather soon. The same holds for other pending releases of Mailman3 components: Just in case you plan to do new upstream releases anytime soon, it's still possible to upload them to Debian in time for Buster. Cheers jonas

6 years, 5 months

Re: Another interesting error...

by Mark Sapiro

On 04/23/2018 02:59 PM, Darren Smith wrote: > Well, using the mailman shell we were able to find the request that was > causing the problem - it was apparently a spam message that had some > chinese characters in it. I am trying to duplicate this issue in a test environment. I can create a message with an invalid RFC 2047 encoded subject, i.e., Subject: =?gb2312?Q?=ff=fe=de=21=a2?= and send it to a list where it gets held, but I don't get a 500 in postorius and I see the held message with a raw (not decoded) header. I think there were some recent changes that affect this. I'll look some more. > We used the shell to delete the held request... > > And postorius is still giving me an error 500. > > If I'm not mistaken the held messages are kept in .pck files - do you know > if when postorius asks for held messages through the API, does mailman go > to the database or to the .pck? I would actually suspect the latter, or > removing the request should have fixed the problem. They were held in .pck files in Mailman 2.1, but not in Mailman 3. They should just be in the database and deleting them via mailman shell should delete them as long as you quit the shell or commit(). -- 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

Re: Postorius & multi domain

by Gelpi Andrea

Thank You so much for your quickly answer and explanation. I understand that the web server name must be equal to the email domain. I read the issue. I'm not a python programmer so I ask you if it'd be long to implement a workaround like this. If the web server is a.example.com and the email domain is example.com It'd be possible to drop the "a" and send the email domain only in the query? It's a workaround. Can you help me in this? Regards, -- AG Il 22/04/20 18:22, Mark Sapiro ha scritto: > On 4/22/20 8:14 AM, Gelpi Andrea wrote: >> >> I search internet for a while and I discovered that using >> FILTER_VHOST = True >> seems to solve the problem. >> >> >From posotrius config page: >> >> FILTER_VHOST >> Filter the list of available lists in Postorius and Hyperkitty >> depending on the domain they are being currently served from. Mailman 3 >> supports multiple domains in a single installation. >> >> But it doesn't work. I got err 500 form apache. > > > FILTER_VHOST is currently broken unless each domain has the same value > for the web and email domains. See the thread at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > and the issue at <https://gitlab.com/mailman/postorius/-/issues/394>. > > >> Were can I find an explanation or a how to configure the system to have >> 2 webserver with different domains working on the some server as it was >> with mailman 2? > > > If each domain has the same value for the web and email hosts, > FILTER_VHOST will work. > > Currently though if you have domains like web host = lists.example.com > and email host = example.com, FILTER_VHOST is broken. > -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 3 months

Re: Postorius: Dropdown menus problem

by thor.rustad＠gmail.com

I'll add some additional information. Chrome inspect to the rescue :-) I don't know what it means. Is it Nginx that needs configuration? Could it be because I still lack the certificate for https? Refused to execute script from 'https://myserver/static/postorius/libs/jquery/jquery-1.11.3.min.js' because its MIME type ('') is not executable, and strict MIME type checking is enabled. myserver/:1 Refused to execute script from 'https://myserver/static/postorius/libs/bootstrap/js/bootstrap.min.js' because its MIME type ('') is not executable, and strict MIME type checking is enabled. myserver/:1 Refused to execute script from 'https://myserver/static/django-mailman3/js/main.js' because its MIME type ('') is not executable, and strict MIME type checking is enabled. myserver/:1 Refused to execute script from 'https://myserver/static/postorius/js/script.js' because its MIME type ('') is not executable, and strict MIME type checking is enabled. -rw-r--r-- 1 ubuntu ubuntu 95957 Dec 1 16:18 jquery-1.11.3.min.js

7 years, 7 months

Mailman-users search results for query "Postorius"