Search results for "Postorius" - Mailman-users

Re: Where does sender postorius@ come from?

by Mark Sapiro

On 6/14/23 14:35, Jens Günther wrote: > Thanks for the hint. Unfortunately it's not working as expected. I'm > using the docker-setup and tried it in 2 different locations, but > neither got the expected effect: > > - I put the variable in the mm-web-container-environment: > mm-web: > environment: > - EMAIL_CONFIRMATION_FROM=myaddress(a)something.org That won't work > - Then I tried settings_local.py with: > EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' That is the correct place. It should work. Did you restart the container after making this change? -- 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: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

On 1/10/20 4:55 PM, Jim Ward wrote: > Mailman2 allowed me to list my members and modify a number of their attributes (display_name, etc) > > Postorius is a beautiful interface BUT I am evidently not finding how to manage my members to the extent that I could in Mailman2 It's not like MM 2.1 where you have a membership list with columns of checkboxes, but if you pull down the Users menu and select Members or Non-Members, each user has an options link that allows you to set/change options. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Re: Change digest frequency and default threshold

by Mark Sapiro

On 9/24/18 4:52 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> On 9/21/18 6:21 AM, Henrik Rasmussen wrote: >>> 2) How do I change the default for existing lists >> >> Postorius -> Settings -> Digest > > Sorry, I was unclear here. I was aware of changing the size in the web interface, but what I meant was changing the Digest Size Threshold value for all lists using REST API. > > Is that possible? Probably not in a single REST interaction, but you could iterate over all lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 16:59 GMT+01:00 Terri Oda <terri(a)toybox.ca>: > > > On January 23, 2018 6:26:51 AM PST, Thor Atle Rustad < > thor.rustad(a)gmail.com> wrote: > >2018-01-23 14:37 GMT+01:00 Simon Hanna <simon(a)hannaweb.eu>: > > > >> On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > >> > >>> Imagine an installation with 500+ mailing lists and almost as many > >local > >>> admins that are supposed to maintain their own local lists with a > >few > >>> local > >>> members. As site admin, I see all 500+ lists, but I was expecting > >*local* > >>> admins to see only the lists they maintain. I have set all lists to > >>> "advertised = False", so they are hidden from ordinary view. Is > >there a > >>> way > >>> to show only relevant lists to local admins? > >I believe I wrote Postorius in the subject line, but it may not be so > >obvious. So yes, in Posterius I would like to hide the lists from email > >harvesters, while relatively "untrusted" admins should have access to > >basic > >operations on the one list he/she "owns" (and without having to browse > >through 50 pages of mailing lists). Somehow I don't think 500 > >superusers in > >our system is a good idea! > > What do you mean by local admins? > > Is this > 1. Giantsite.example.com hosts lists for a bunch of domains, and you want > the logged in admins of mydomain.com to see their list admin pages but > not otherdomain.org's lists > > 2. You want each logged in admin to have their own personal dashboard of > list admin pages for lists they administrate, even though they're all under > one big domain. > > (Neither of those scenarios talks about archives, since you say you're > only talking about postorious) > > I think #2 is something we should be doing, and the old "todo" section of > the interface kind of was made with that in mind. Probably worth mocking > up some screenshots and opening a feature request to keep the idea in mind, > but it should be more a matter of prioritizing how things are displayed > than any huge change. > > I'm not sure if we have a "local admin" concept in the system that lines > up with #1, though. > > Ok, this would more like number 2. It's National.dogclub.com with its various mailing lists like poodle.dogclub.com, which expands to poodle-regionA.dogclub.com, poodle-regionB.dogclub.com, poodle-regiionC.dogclub.com and so on. So with dozens of different dog breeds and geographic chapters, the number of mailing lists are between 500 and 1000, but all are under the same dogclub.com domain. The members of each list should be maintained by a person with some elevated rights, but not enough to mess up the system. What I called "local admin" should have rights to add and remove members of, say, the poodle-regionA mailing list.

6 years, 10 months

Re: Multiple domain problem

by Mark Sapiro

On 2/9/23 13:21, Lars Bjørndal wrote: > > I have lists on two domains, example1.com and example2.com. The mail > interface works perfectly. However, connecting a browser to > example1.com, I get the title List index - example1.com, and the web > interface seems to work fine. > > 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? What's in Postorius domains view? What's in the Django admin sites view. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

Re: changing adverstised status

by Simon Hanna

On 8/22/18 10:27 AM, Alexander Klotz wrote: > Hi there, > > we are trying to set a once public list to private but have trouble > doing so. In Postorius this doesn't seem to work - you can change > "show list on index page" via the settings, but the value isn't saved. > Is there a way to set advertised = False to a specific list via the > shell? What do you mean it isn't saved? Are you getting an error? Is it just being overwritten to True? I use the rest api, using it you can do the following: ./manage.py mmclient lists = client.lists l = <choose your list> l.settings['advertised'] = False l.settings.save()

6 years, 3 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Jim Popovitch

On Sat, 2021-02-13 at 10:40 -0500, Brian Carpenter wrote: > On 2/13/21 10:37 AM, Jim Popovitch via Mailman-users wrote: > > On Sat, 2021-02-13 at 08:01 -0500, Brian Carpenter wrote: > > > Features are not the only thing about a modern UI, UX design plays a > > > MAJOR role in the modern UI. Postorius should have at least matched MM2 > > > in features in regards to something as important as Member management > > > but instead it took a step back into the dark ages. > > I'm gonna be a dick and remind you that less than 1 year ago you were > > trying to convince me that MM3 was a gift from god and that it was time > > for me to jump from MM2 to MM3 because it was sooo easy and such a time > > saver.. or something like that. The point being, you yourself just > > still aren't happy with MM3. Welcome to the club. > > I am very happy with MM3 just not with Postorius. MM3 allowed me to come > up with my own admin interface. Mailman 2 would never allowed me to do > that. So please leave your Mailman 2 bondage and come over to Mailman 3. > We have cookies! But how do you display a "Membership List page" for admins in MM3 (choice of wording is specific to other emails you've posted today) without third-party application(s), and isn't that too a shortcoming in MM3 due to that functionality being present in MM2? Look, without a doubt the REST API of MM3 Core is cool, but let's be honest, all the 3rd party wrapping and baggage is, well, not so cool. But, again being honest, you can't have a MM3 system without all of those things. With MM2 we have all those things, and we are happy with them. :) -Jim P.

3 years, 9 months

Re: Is logging.subscribe working in /etc/mailman.cfg?

by Mark Sapiro

On 2/19/19 6:39 PM, Alan So wrote: > I just tested it and observe that, > > 1) If the member send the request to list-leave(a)example.com, the user can confirm and the request is then moderated. The held request is also logged as expected and a notification is also sent to the owner or moderator. However, the owner cannot fulfill his/her request like those under "Subscription requests" in Postorius. The owner have to remove the address manually as a workaround. This is now reported at <https://gitlab.com/mailman/postorius/issues/332> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Re: Removing a moderator via the REST API

by Mark Sapiro

On 11/14/24 13:44, Andy Matthews wrote: > > However it doesn't appear that you can remove a person as moderator via the API, per a comment made by Mark on 8/12/24 in this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I'm not sure what I said there to make you think that, but first you have to be able to do this via the API because Postorius does it via mailmanclient which uses the API. See https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/re… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks

Hyperkitty - not sending from GUI & reply-thread

by sunil soprey

With latest release (HK 1.3.1), does anyone have an issue with no emails from reply-thread? I able to send/receive emails to/from mailman. I see MTA delivered emails, just no emails from HK GUI. No errors logs (py exception) nor mailman. ideaS? Versions: mailman-hyperkitty (1.1.0) - Mailman archiver plugin for HyperKitty INSTALLED: 1.1.0 (latest) HyperKitty (1.3.1) - A web interface to access GNU Mailman v3 archives INSTALLED: 1.3.1 (latest) mailman (3.3.0) - Mailman -- the GNU mailing list manager INSTALLED: 3.3.0 (latest) postorius (1.3.1) - A web user interface for GNU Mailman INSTALLED: 1.3.1 (latest) django-mailman3 (1.3.1) - Django library to help interaction with Mailman INSTALLED: 1.3.1 (latest) mailmanclient (3.3.0) - mailmanclient -- Python bindings for Mailman REST API INSTALLED: 3.3.0 (latest) f

4 years, 10 months

Mailman-users search results for query "Postorius"