Search results for "Postorius" - Mailman-users

Mailman REST API not available. Please start Mailman core.

by joseverde＠gmail.com

Okay, so I got the webservice of Mailman3 up and running, but when I go to mailman3/postorius/lists/, I get the following error: Something went wrong Mailman REST API not available. Please start Mailman core. When I logged in to the admin user, it threw a server 500 error, but I could refresh and see myself logged in. If I try to go to lists or mailman settings, however, I get the error above.

5 years, 11 months

Re: New releases

by brylon＠oit.rutgers.edu

I already have ruby-sass installed and the compress command used to work as expected prior to my upgrading to the latest core, postorius, hyperkitty versions using pip in my venv. Does It matter at all when performing the Django-admin commands whether I've activated the venv or not? I think I've tried running them both activated and deactivated to no avail, but any other suggestions?

5 years, 9 months

Re: Member Issue Discovered

by Jörg Schulz

just created an issue on gitlab https://gitlab.com/mailman/postorius/-/issues/451 regarding name changes, member deletions. Maybe this adds some coolness to this discussion.

5 years, 8 months

Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

If you set the unsubscription policy to confirm then moderate for a list and someone unsubscribes, they receive a confirmation request. That is good. They respond to it. That is also working fine. However the list owner/moderator than gets a request to approve the unsubscribe request and well, unless I am missing something, I don't see an interface to handles such requests via Postorius. How does one handle an unsubscribe request that requires moderator approval? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 8 months

Unsubscribe Notifications to List Owners and Members

by Brian Carpenter

It seems that the only time an unsubscribe notification is sent to a list owner and/or list member is when a list member sends an email to lisname-unsubscribe@listdomain and that list member is not registered with Affinity/Postorius. Can anyone confirm this and if confirmed, is this considered a bug? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 8 months

Re: migration from 2.1 - owners and moderators

by Mark Sapiro

On 10/24/20 5:34 PM, Alex Schuilenburg via Mailman-users wrote: > > Thanks for reminding me I need to upgrade :-) 3.2.1 Does not have "notify" Yes, It did not appear until 3.3.0. > I'll wager that the sporadic notification messages are down to this > version, so upgrading just bumped up my todo. What is your setting for admin_immed_notify (Postorius Settings -> Automatic Responses -> Admin immed notify)? This should definitely be Yes if you don't have `mailman notify`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Re: Member Issue Discovered

by Brian Carpenter

I just wanted to let the community know that we have addressed the issue of user data being retained when they unsubscribe from a single list or delete their Affinity/Empathy registration account. The latter was a bug on our end. In both scenarios, all data is removed from the server when someone unsubscribes from a single list and/or deletes their registration. The only time data is retained is if the user still holds a subscription to one or more lists on the server for obvious reasons. This is in regard to our Affinity/Empathy UIs. I believe the issue that was raised originally in this thread/post still exists with Postorius/Hyperkitty. Brian Mailmanhost.com

5 years, 7 months

Re: KeyError: 'subject_prefix'

by Torge Riedel

Am 15.11.20 um 23:24 schrieb Abhilash Raj: > Is the value of subject prefix for that list set to*something* in Mailman? Hi, yes, it is: Mail list is "aktive@lists.<domain>" and the subject_prefix is "[Aktive]". In database and also visible in Postorius. The error report also didn't happen again. Kind regards Torge

5 years, 7 months

Re: installation

by Christian Stalberg

Continuing to work through installing mailman3 on Ubuntu 20.04.1 LTS / apache 2.4.41 / postfix 3.4.13. I am at https://docs.mailman3.org/projects/postorius/en/latest/deployment.html?highl ight=compilemessages#final-setup-instructions What do I do now about this? (venv) root@localhost:/opt/mailman/mailman-suite/mailman-suite_project# python manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /opt/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: y CommandError: Collecting static files cancelled. (venv) root@localhost:/opt/mailman/mailman-suite/mailman-suite_project# Thank you! ~Christian

5 years, 7 months

Re: Module Not Found Error after update

by Brian Carpenter

On 2/4/21 11:46 AM, Mark Sapiro wrote: > You need django-mailman3 1.3.5 > > > While all are not required in this case, when you upgrade like this with > pip, you should upgrade all of django-mailman3, hyperkitty, mailman, > mailmanclient, mailman-hyperkitty and postorius. Thanks Mark. Perhaps Abhilash can include that in the instructions on the following page for future releases: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I will make a note of this in my own personal documentation and the Debian 10 How-to guide that I am currently working on. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

Mailman-users search results for query "Postorius"