Search results for "Postorius" - Mailman-users

Show diplay_name in a list

by ruben＠bkonrad.de

Hello, I'm trying to figure out how to show the display_name of a member in postorius in Members > Subscriber. I was trying to add {{ member.diplay_name }} in the template ${postorius}/templates/postorius/lists/members.html Here an abstract of where I inserted the code: [...] {% for member in members %} <tr> {% if role == 'subscriber' %} <td> <label class="checkbox-inline"> <input type="checkbox" class="member-checkbox" name="choices" id="id_choices_{{ forloop.counter0 }}" value="{{ member.email }}" /> {{ member.display_name }} <{{ member.email }}> </label> [...] I could not figure out why it wouldn't work. I'm running mailman3 Version 3.1.1-9 on an Ubuntu 18.04. Any idea what I was missing there? Thanks in advance for any help. - Ruben

6 years, 5 months

Starting from scratch

by Benjamin Ragheb

Hello! Over the weekend, I attempted to install the Mailman Suite on Debian Stretch. My goal is to set up some low volume mailing lists for family and friends. I ran into some problems, and I'm hoping to get some feedback on my overall approach before I make my second attempt. :-) I figured the safest thing to do would be to use pip to install the latest released version of all the components (core, postorius, hyperkitty, etc.). I copied the files from the [mailman-suite repository][1] to set up a Django project and got it mostly working with Apache and mod_wsgi. [1]: https://gitlab.com/mailman/mailman-suite Unfortunately, I was unable to log into the web interface; when I tried, I got a server error like this: > Exception Type: TypeError at /accounts/login/ > Exception Value: authenticate() takes exactly 0 arguments (3 given) Some research leads me to believe this is happening because authenticate() was changed in Django 1.10, and so I must be using a newer version of Django than the app expects. Given that I installed via Pip, I assumed the right version of Django would automatically be installed... I'm open to the possibility that I am misunderstanding how Pip works, or that postorius's and/or hyperkitty's dependency information is incorrect. The two alternatives I am weighing right now are: 1. Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration. 2. Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.) Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python. Which is the least crazy option? -- Ben

7 years, 11 months

Re: Customise Postorius templates?

by Stephen J. Turnbull

Duane Raymond writes: > Is anyone out there working on an overhaul of the web interface > templates Yes. There's a big accessibility project being done by a well-resourced organization. If you're going to be doing the kind of substantial work you describe, write me off-list and I'll do some introductions. (That applies to anybody reading this; project participation is by introduction, "well-resourced" doesn't mean "infinite" ;-), but anybody making a substantial contribution has need-to-know.) I'm not sure how much is still publicly available since the ownership change, but you might want to look at the Affinity and Empathy projects at emwd.com. The code is PHP but you may get some ideas from the UIs. Steve

4 years, 1 month

Debian10 pkg install: set up Postorius superuser?

by mcarter＠corneredrats.com

Hey, all. I've installed mailman3 to replace mailman2 from the Deb10 package mailman3-full. Command line appears to work, but I had to manually add the Uwsgi module to get the user web site to run. I can't find a reference to what the default admin user password is, and running "python settings.py createsuperuser" doesn't work with error: root@mail:/usr/share/mailman3-web# python manage.py createsuperuser Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management Any idea what else needs to get installed that the aptitude package missed? Any way to just manually set the admin's password without having to install anything else?

4 years, 8 months

Rejection Reason for refusing a subscription request

by Brian Carpenter

I was testing out the process of rejecting an incoming subscription request. Choosing the reject option for a moderated subscription request does send out a rejection notice but it gives no reason for the rejection. Please see: ------------------------------------------------------------------------ Your request to the redacted(a)redacted.com mailing list Subscription request has been rejected by the list moderator. The moderator gave the following reason for rejecting your request: "[No reason given]" Any questions or comments should be directed to the list administrator at: redacted-owner(a)redacted.com ------------------------------------------------------------------------ Is there a place somewhere in Postorius to provide a rejection reasons for moderated subscription requests? Does Mailman 3 core provide this via its REST api but it is just not revealed in Postorius yet? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

Re: Must every Moderator/Admin be member of a list to be able to use Postorius?

by Mark Sapiro

On 1/31/23 10:25, mm3-omf(a)sh.werbittewas.de wrote: > we're using debian/devuan with distribution-mailman3 and tried to add > admin/mod for a list, but if logging in as this user, there's no item to > manage the list at all. That's strange. If the logged in user is a moderator she should see the Subscription requests and Held messages tabs and with Postorius >= 1.3.9b1 also the Members tab, and if she is an owner she should see the full admin UI without needing to be a member. Are you sure the logged in user is the same user that's an owner/moderator? Log in as a superuser and find the user in the User's view fron the top nav bar in Postorius, click Manage to see all that user's roles and web account. > do we have to add this user as member of this list? > (that wouldn't be nice, because the user doesn't want to get normal > Mails from List, but only admin-Mails) It shouldn't be necessary, but a delivery can always be disabled for a member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Re: See list of subscribers

by Mark Sapiro

On 3/27/24 00:38, Tom Yates wrote: > > I have a list, as admin under "Settings" -> "List Identity" -> "Members > List Visibility" I have it set to "Only Mailinglist Members". > > But a random subscriber, who's signed up and authenticated, when she > visits the list page she sees her subscription, but no option to list > the other subscribers. > > Is she looking in the wrong place? Do I need to open up more settings? > Am I just being an idiot? This is https://gitlab.com/mailman/postorius/-/issues/369 fixed in Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/770 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 8:18 PM, Mark Sapiro wrote: >> https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > FYI, ${short_listname}.${domain} is the same as ${list_id} Good to know. Thanks. > Also, ${domain} as the web site address may not be appropriate. For > example, on this list $domain is `mailman3.org`, but the base URL for > Postorius is `https://lists.mailman3.org/mailman3` and > `https://mailman3.org/mailman3` doesn't work. There is no replacement > for the web domain if it's different from the email domain for the same > reason that there are no web URLs in the default templates. Is there a variable for the base Postorius URL? Something like: https://${baseVarName}/lists/${list_id} Thanks dn

4 years, 2 months

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/9/21 10:14 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I have the apache24 and uwsgi working together. I did this way: > > For the apache24 part I decided to use the mod-wsgi (and uswgi binary). > did a > > pip install mod-wsgi > (with "mod_wsgi-express module-config" it shows the conf needed.) > > after that a > > pip install uwsgi mod_wsgi and uwsgi are two different, incompatible ways of doing the same thing. It appears from the rest of your post(s) that you are actually using mod_wsgi and (hopefully) not running uwsgi at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

> On Jan 14, 2022, at 20:30, David Newman <dnewman(a)networktest.com> wrote: > >> Also, ${domain} as the web site address may not be appropriate. For example, on this list $domain is `mailman3.org`, but the base URL for Postorius is `https://lists.mailman3.org/mailman3` and `https://mailman3.org/mailman3` doesn't work. There is no replacement for the web domain if it's different from the email domain for the same reason that there are no web URLs in the default templates. > > Is there a variable for the base Postorius URL? Something like: > > https://${baseVarName}/lists/${list_id} Sorry, guess that should be something like: ${baseVarName}/lists/${list_id} Is there such an animal? Thanks dn

4 years, 2 months

Mailman-users search results for query "Postorius"