Search results for "Postorius" - Mailman-users

Re: Managing users in postorius

by Mark Sapiro

On 9/25/24 11:08, Lieuallen, Thomas Otis wrote: > I don’t seem to have very much control with the site admin account. I’d like the ability to add a secondary address for a user instead of talking them through the process of doing it themselves. Is there a way that I’m not aware of? In the Django admin web UI under Email addresses, you can add an address and associate it with an existing user. > Additionally, when I look up users and choose ‘manage’, it only lists a person’s member roles. It doesn’t list any other roles (owner/admin, moderator, etc). Any way to fix that? It should list both member and nonmember rolls. If you scroll down past Subscriptions to Ownerships, it lists owner and moderator rolls. > I’m also curious what the process would be for merging two postorius accounts into one? My thought process was that I should remove one and then have the user add that email address to the other account. But, if you delete the account, it will unsubscribe the user. In the Django admin UI, you can edit the user associated with an email address under Email addresses -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

Re: Postorius: Search field in lists overview

by Mark Sapiro

On 1/14/25 23:36, Andreas Vetter wrote: > Hi, > is there a way to search lists in Postorius' Lists overview > https://lists.example.com/mailman3/lists/?all-lists > > Well, one can change "results on page" to 200 and then use the search function > of the browser, but that is some more clicks. No, there is no search function for this. If you know the name you are looking for, e.g., list(a)example.com, you can just go to https://lists.example.com/mailman3/lists/list@example.com/ but if you are looking for lists matching a pattern, there is no Postorius function for that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

Re: Deactivate list without deleting it?

by Stephen J. Turnbull

Colin Watson writes: > I possibly should have explained our situation in a little more > detail. Well, I was pretty clear on your requirements, it turns out. I don't, and I believe I'm in agreement with the rest of the team here, need to know why you want something (at least not at this "let's see if we can hash out the requirements and the design a bit" stage). After all, even if we end up WONTFIXing it, it's open source and we're happy to talk about how you might do something even if we won't do it for you! > Postorius wouldn't come into it in our case That's an interesting detail. Thing is, at present Postorius *is* the "control panel" for the whole suite (all the best bands are run by their bassists, you know), so we would bring it up if you left it out. However, if you don't want to use Postorius, I think the mailman-client functionality will make it strightforward to implement your UI within Launchpad, and it now includes a nicer CLI so if you prefer to implement core and Hyperkitty functionality before the Launchpad side, mailman-client will allow you to test core features at that stage. > I'd been thinking more of a new enum in HyperKitty for the visibility > state, since it does seem like quite an archiver-specific thing. Well, there is an enum in core for it already. I'm not sure how that works currently (specifically, how you go about telling Hyperkitty if that changes). Keeping that in sync is an issue (at least for us), since Postorius can query it, IIRC. For the rest, I have nothing to add to what Barry already wrote. Steve

8 years, 2 months

Re: Is it possible to grant all users the ability to Create List

by Mark Sapiro

On 7/12/21 8:25 AM, tibor.molnar(a)waltoninstitute.ie wrote: > Hi, > > I would like to know if anyone have implemented this feature or used any workaround to be able to grant users with the ability to create list. This has been a feature in mailman2 where you as a user were able to create list with a password and you did not need to be a superuser in order to do that. I do understand that in the development documentation it states the following: Three of Django’s default User roles are relevant for Postorius: > > Superuser: Can do everything. > AnonymousUser: Can view list index and info pages. > Authenticated users: Can view list index and info pages. Can (un)subscribe from lists. > > Can we maybe add a different user role where the user would be able to create lists? If this is possible would anyone let me know how? The user's `role` is a Django thing. A user can be given either `staff` or `superuser` status or both or neither. As far as Django is concerned, `staff` status only allows the user to visit the Django administration interface. Currently, Postorius has decorators @list_owner_required, @list_moderator_required and @superuser_required defined in postorius/auth/decorators.py. There is also a @login_required decorator in django.contrib.auth.decorators. Postorius decorates the list_new() function in postorius/views/list.py with @login_required and @superuser_required. It would be simple enough to create a new @staff_required decorator which would require staff or superuser status and replace the @superuser_required decorator on the list_new() function with @staff_required. Then any user with `staff` status could create lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Postorius with screen readers

by Stephen J. Turnbull

Andrew Hodgson writes: > Just wanting to let people know that since bumping to Postorius > 1.3.3 I am seeing a real improvement in access to the Mailman > settings and tabs using a screen reader with Chrome. Thanks for telling us! > When navigating through the tabs you are hearing two iterations of > the tab, the first for example saying "Held Messages 0 tab" which > is not a link, but then if you arrow down past that you hear "Held > Messages 0" which is advertised as a link and if you hit enter on > those it changes the page to the requested view. I don't think we have accessibility specialists among the developers, although several of us care deeply about it. So I'd like to confirm: the two iterations, one telling you you are on a tab, the other telling you you have a link, is a good thing? Would it be better if you got one notification that there is a tab with a link on it? I don't know if there is anything we can do about that, since our accessibility features come from the Django framework. But I'd like to improve my awareness and knowledge of how these features work for our users in Mailman. Steve

5 years, 9 months

Re: restricting public lists per virtual domain

by Mark Sapiro

On 12/16/21 12:25 PM, David Newman wrote: > Can lists set to be viewable on the index page be limited to the virtual > domain they are a part of? > Have you set FILTER_VHOST = True in your Django settings? This works for HyperKitty and works partially for Postorius. For Postorius, it doesn't work if there are multiple domains with different email hosts which have the visiting host as their web host[1] but works otherwise. See https://gitlab.com/mailman/postorius/-/merge_requests/500 and https://gitlab.com/mailman/postorius/-/issues/394 In your case, as long as the domains lists.dom1.tld and lists.dom2.tld have different mail hosts, this should work. [1] An example of what doesn't work in Postorius is the following: Visit https://lists.example.com/mailman3/lists. If there are 2 domains with web host lists.example.com, one of which has mail host example.com and the other has mail host lists.example.com, all lists will be shown regardless of domain. On the other hand, if all the domains with web host lists.example.com have the same email host, say example.com, then only lists with email host example.com will be shown. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: FW: lists.arun@gmail.com's bounce score incremented on Degrowcali

by Mark Sapiro

On 11/6/25 07:38, Christian Stalberg via Mailman-users wrote: > Whenever I post to this list I get quite a few of these bounce score > messages. How can I obtain a list of actual unsubcribes based on bounce > scores to remaining subscribers please? What can I do to stop this behavior > please? The sending of bounce score incremented notices is controlled by the list's bounce_notify_owner_on_bounce_increment setting exposed in Postorius as Settings -> Bounce Processing -> Notify owner on bounce increment. All bounce processing settings are in Postorius' Settings -> Bounce Processing section. The Users -> members list in Postorius displays the current bounce score for all members. The head of the GitLab branch, not yet released, also displays the member's delivery status, see https://gitlab.com/mailman/postorius/-/merge_requests/953. Disabling delivery due to bounces is logged in Mailman's bounce.log with messages like Disabling delivery for user(a)example.com on list mailman-users.mailman3.org by bounce Members whose delivery is disabled by bounce will normally be removed from the list after (Bounce disabled warnings interval)*(Bounce disable warnings) days. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > Mark Sapiro writes: > > > > Some of the `path` settings are probably not in the same order as > > > in that file. The > > > > > > ``` > > > path('mailman3/', include('postorius.urls')), > > > path('archives/', include('hyperkitty.urls')), > > > ``` > > > settings should come after the > > > ``` > > > path('postorius/', include('postorius.urls')), > > > path('hyperkitty/', include('hyperkitty.urls')), > > > ``` > > > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > > > order). Or you can just delete the 'postorius/' and 'hyperkitty/' > > > ones or you can add > > > ``` > > > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > > > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > > > ``` > > > to your Apache config. > > > 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. > > I believe this is the Apache configuration the OP is using: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/admin" "http://127.0.0.1:8000/admin" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > </IfModule> > > 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')), > > I think Mark must have a configuration with > > ProxyPass "/" "http://127.0.0.1:8000/" > > in the Apache configuration in mind? Or an alias or rewrite rule. > Otherwise I don't see how "/postorius" and "/hyperkitty" paths ever > get transmitted to the WSGI server. > 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, or a urls.py be provided for inclusion in /etc/mailman3/ and which sysadmins can edit to their liking. For example, I'd prefer to have /mm3 instead of /mailman3 to save on transmitted bytes and not clog the Internet pipes :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years

Re: hello， Discussion on how to subscribe to themailing list

by 朱超

thank you for your reply 1. It is not the MTA that refuses to send emails because the recipient's mailbox is too long, but the MUA that refuses to send the email because the recipient's mailbox is too long. Of course, you can use the confirm $token message to dev-request@domain for confirmation. This is a comparison Troublesome process, by visiting https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token, but he reported 404. 2. It is recommended to modify postorius, in order to keep the logic function of the underlying mailman-core unchanged, and optimize postorius at the application layer to increase user experience; even if there is no mailman-web service or postorius service, mailman-core can still run normally. If you look at the separation of the application layer and the underlying software, I think it is possible From: Tom At 2023-01-17 19:44:20, "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: >朱超 writes: > > > Yes, You got it. It is too cumbersome to ask the user to write a > > reply email for email confirmation. > >Surely clicking on "reply" then "send" is not cumbersome (unless >there's a way to get rid of confirmation altogether). Your problem is >that some of your subscribers can't do that. > >I have not previously heard of a MTA that refuses to *send* mail >because the addressee's mailbox is too long. IIRC there's a limit of >256 characters on domains, but only the (long-obsolete) recommendation >that lines in the message be 998 bytes or less restricts the length of >the local-part. > >I don't really see a good reason to change this default because there >are a number of configurations where there is no web service >available. I suggest a partial remediation in the issue I just filed. >(I think dealing with the rest of the issue is a Simple Matter of >Programming, but the question of determining existence and status of >an appropriate web service is more complex so I did address that.) > > > Why do you need to modify the mailman-core service， > >I suggest we should modify the code of the postorius, > >We are not going to do that, because >1. Mailman provides no guarantee that any web service is present, and > we're not going to make changes that require one. >2. Mailman provids no guarantee that the web service is Postorius > even if there is one, and we are definitely not going to make > creating compatible implementations more annoying than necessary. > > > Currently I have achieved it this way。 > >We encourage you to use your code. ;-) But using it exclusively to >accomplish this change would go against several of our goals in term >of separation of concerns. If we can do it in an alternative way that >serves those goals, there's no point in complexifying Postorius in >this way as well. > >Regards, >Steve >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >This message sent to tom_toworld(a)163.com

3 years, 2 months

Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/14/19 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > On my server are several virtual hosts running with different lists per > host. The appropriate webaddress is in general: > https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. > My domains: > [domain-1] starts with a b* > [domain-2] starts with a s* > [domain-3] starts with a t* > > If I use the webadress > https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… > and I do a click on the https-symbol in the address line of my browser I > get the secury-information " every thing is ok" and the > certificate-information is about the wildcard-certificate I just created > for the right domain. > > Different result is for the webadress > https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. > In this case I get an information like "you are using a wrong > certificate" clicking on the https-symbol references tot he certificate > of [domain-1] > > I set in my apache2 configuration a symbolic link to apache.conf in the > /etc/mailman3/directory and made this active. > > What did I wrong?? Your Apache config needs to define separate a VirtualHost for each domain, either by IP address or ServerName, and each VirtualHost points to its own SSL certificates. > If I set use_https to yes in mailman.cfg I get on the website for all > lists: > > postorius: Something went wrong > Mailman REST API not available. Please start Mailman core. > > In the logs I found … ... > mailman-web.log > ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", > line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, > in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, > in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, > in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, > in connect > self.sock = self._context.wrap_socket(sock, server_hostname=self.host) > File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket > session=session > File "/usr/lib/python3.7/ssl.py", line 853, in _create > self.do_handshake() > File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake > self._sslobj.do_handshake() > ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number > (_ssl.c:1056) Does your setting in settings(_local).py for MAILMAN_REST_API_URL have an https scheme? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Mailman-users search results for query "Postorius"