Search results for "Postorius" - Mailman-users

Re: "Private archives" aren't private

by cyp＠trojina.si

Hi, I'm having the same problem: changes to the "Archive policy" settings in postorius are not reflected in hyperkitty. Trying to use mailman_sync to fix this gave me the same BaseCommand traceback as above, but "mlist_object.update_from_mailman()" works. So luckily we have a workaround, thanks. But I suspect that there's some misconfiguration or permission problem on our server that's blocking the automatic synchronisation from taking place. Any advice to resolving this would be appreciated. :) Cheers, Cyprian

8 years, 9 months

Re: Typo in List Creation screen

by Abhilash Raj

On Thu, 10 Aug 2017 08:28:33 +0000 Henrik Rasmussen <her(a)adm.ku.dk> wrote: > There is a typo in the list creation screen in Mailman 3. The owner's address field says "Inital list owner address", which should be "Initial" with an extra 'i'. > Thanks for reporting. I have opened an issue at https://gitlab.com/mailman/postorius/issues/212 Please report the issues at our issue tracker[1]. [1]: https://gitlab.com/mailman/postorius/issues/ thanks, Abhilash Raj

8 years, 8 months

restrict sending to owner/moderator

by m.dohmen＠xconnect.de

Hello, I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. Is there a way to do this?

8 years, 7 months

The message is larger than the 40 KB maximum size

by Simon

Hello, I understand I cannot increase the message size limit in Postorius (yet). But is there another way to adjust it? Simon

8 years, 7 months

Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 10/07/2017 02:04 PM, Simon wrote: > Hello, > > I understand I cannot increase the message size limit in Postorius (yet). > > But is there another way to adjust it? $ bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the list(a)example.com mailing list m.max_message_size = nn commit() Substitute the appropriate list name and size. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

Re: Postorius: Dropdown menus problem

by thor.rustad＠gmail.com

Answering myself again... problem solved. It was indeed the missing certificate in nginx configuration that caused my grief. Thank you again for your patience :-) Thor

8 years, 5 months

Postorius: Show only own lists

by Thor Atle Rustad

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 am running docker running release. mailman info GNU Mailman 3.2.0a1 (La Villa Strangiato) Thor Atle Rustad

8 years, 3 months

Re: Postorius: Show only own lists

by Mark Sapiro

On 01/23/2018 08:54 AM, Thor Atle Rustad wrote: > What I called "local admin" should have > rights to add and remove members of, say, the poodle-regionA mailing list. By "local admin", do you mean "list owner", i.e., a list owner should be able to see her own "hidden" lists. Is that what you mean, or to you envision some new category of user that has more access than a list owner? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

Re: Where is postorius.wsgi?

by Peter Münster

On Sun, Jan 28 2018, Peter Münster wrote: > Anyway, with my patch (EmailMessage -> Message) it works. Sorry, I was wrong. Archiving did not work. You are right, I need to "pip2 install django-mailman3==1.1.0" Thanks for your help, -- Peter

8 years, 3 months

Re: django-mailman3 update causing errors

by Mark Sapiro

On 05/01/2018 01:35 PM, Darren Smith wrote: > Hello, > > In attempting to update our mailman3/postorius/hyperkitty installation, I > have run into an error after upgrading the django-mailman3 project. ... > Any thoughts on why updating django-mailman3 would cause this? To what version did you update? any 1.2 version is part of the migration of Postorius/HyperKitty to Python 3 and requires postorius>=1.2.0b1 hyperkitty>=1.2.0a1 Django>=1.11 django-mailman3>=1.2.0a2 mailmanclient>=3.2.0b1 and is all Python 3 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

Mailman-users search results for query "Postorius"