Search results for "Postorius" - Mailman-users

Re: list footer questions

by Mark Sapiro

On 5/8/20 12:52 PM, Mohsen Masoudfar wrote: > Hi, > > This seems to me like basic simple questions, I have tried FAQ and other resources, with not much success. > > I have two questions: > > 1. When I send an email to a list, in gmail and yahoo I see the following text with the links at the end of the email body: > _______________________________________________ > Testlist_dmark1 mailing list - listname(a)domain.tlb<mailto:testlist_dmark1@newlistserv.aaas.org> > To unsubscribe send an email to listname-leave(a)domain.tlb > > In<mailto:listname-leave@domain.tlb%0b%0bIn> outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? There are a few things going on here. First, the actual footer is _______________________________________________ Testlist_dmark1 mailing list - listname(a)domain.tlb To unsubscribe send an email to listname-leave(a)domain.tlb The <mailto:...> links are added by the Mail client displaying the mail. > In outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? > > I know MS does it own stuff sometime and we have no impact on that, but I was thinking maybe we might change the footer in a way that outlooks sees that as part of email body. Yes, this is an outlook thing, but you do have some control. See the FAQ article at <https://wiki.list.org/x/4030707> for a more detailed explanation, but the issue is that after any content filtering has been applied, the message is still multipart so Mailman adds the footer as a separate MIME text/plain part at the end of the message. You can avoid this by doing heavy content filtering on the messages. Namely, accept only multipart, text/plain and text/html, collapse alternatives and convert html to plain text. Note that some of this involves updating the list's pass_types which is not exposed in Postorius before 1.3.3 which is not yet released. > 2. How may I change the format and the text in footer? > I was expecting it under list > setting, in postorius, but I could not find it. It's the top level Templates tab in Postorius (just left of Settings). It was added in Postorius 1.2.1. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

Mailman Core 3.3.1 release

by Abhilash Raj

Hey Everyone, I am pleased to announce Mailman Core 3.3.1 is now out. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1/ To install this release via pip, you can run: $ pip install --upgrade mailman -- thanks, Abhilash Raj (maxking)

6 years, 6 months

Re: Set Postorius interface locale

by Duane Raymond

Thanks - here is where that got ne so far... I have set the modest goal of changing a string on the list subscription page from the form label "Your name (optional)" to "Your name (and organisation)" What I did was 1) I edited /opt/mailman/mm/settings.py and changed the LANGUAGE_CODE from 'en-us' to 'en-gb' (or should I do it at /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/dj/settings.py or another location?) 2) Then I switched user using "su mailman" and started the venv environment (using: source /opt/mailman/mm/venv/bin/activate) 3) I edit the po file at /opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/locale/ and specifically I am testing it on editing en_GB/LC_MESSAGES/django.po - is this the correct location? 4) I run: mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py compilemessages - is this the correct one to run? After this, nothing changed on the list page yet. 5) After that I changed directory into "/opt/mailman/mm/static" and run python ./mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py collectstatic - but this produces an error about ROOT_STATIC not being set ...and I didn't want to fiddle too much in case I overwrote the current functioning site ;-) Is the collectstatic static necessary after running compilemessages? Am I using the right files to run it? Am I editing them in the right location? Cheers, Duane

5 years, 8 months

Question after upgrade to mm 3.2.3 and latest postorius

by Stephen J. Turnbull

David Krantz writes: > I have just upgraded to mailman 3.2.3. My installation is from the git > sources and I use two different venv:s, one for the web part as I did > not want to compile the web server plugin to a newer python version > than 3.5, I see elsewhere that this is mod_wsgi. I forget exactly what my story was, but I did recompile on Linux and it was straightforward. Of course there are a million reasons why you might not want to do that. I just wanted to take this chance to report that for 3.6 and 3.7 this was very straightforward, in case anybody else is thinking about doing it.

7 years, 3 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

8 years, 7 months

Re: I did something stupid. Can i back out of it?

by Mark Sapiro

On 2/19/22 14:06, William Oliver wrote: > > So.. as an aside, it was a bit of a hassle to copy and paste all the > usernames from the "Users" list in Postorius to the "Mass subscribe." > The only way I could see to do it was copy and paste them one at a > time. Postorius Users -> Members view has a CSV Export button. That exports a CSV with all the member addresses. It's actually just a flat list as it only has one column. -- 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

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

7 years, 1 month

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, 9 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, 9 months

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?

5 years, 3 months

Mailman-users search results for query "Postorius"