Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: MM3 generates long lines?

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210623 15:34]: > We would need to see the email itself in order to begin to > understand if this is a Mailman issue or some issue withe the mail > as received by Mailman. > > Assuming the prototype archiver is enabled, you should be able to > find the messages in Mailman's var/archives/prototype/LIST/new/ > directory. One question, in order to ease debugging, can I forcefully activate the prototype archiver from the global configuration, or do I need to do that on a per-list basis? Andi

4 years, 4 months

[MM3-users] Re: Is it possible to grant all users the ability to Create List

by Stephen J. Turnbull

Mark Sapiro writes: > It would be simple enough to create a new @staff_required decorator > which would require staff or superuser status and replace the > @superuser_required decorator on the list_new() function with > @staff_required. Then any user with `staff` status could create lists. This simple scheme would allow them to create lists on any domain, right? Probably would not want to enable it on multi-domain sites. Steve

4 years, 3 months

[MM3-users] Re: Postorius no connection to REST API

by Guillermo Hernandez (Oldno7)

On 10/8/21 4:24, Mark Sapiro wrote: > It appears from the rest of your post(s) that you are actually using > mod_wsgi and (hopefully) not running uwsgi at all. You're completely right, as always. My apologies for the noise --

4 years, 2 months

[MM3-users] Re: Installation -- error on mailman-web migrate

by Mark Dale

> On 9/16/21 8:11 PM, Mark Sapiro wrote: > Actually, upon reflection, the paths in the doc will work as var_dir only affects Mailman core and the settings.py file is for Django. What's missing is that you would need to create the directories `/opt/mailman/web/` and `/opt/mailman/web/logs` manually. > > Thanks. And done. root@mx:/opt/mailman# mkdir web root@mx:/opt/mailman# mkdir web/logs root@mx:/opt/mailman# chown -R mailman:mailman web

4 years, 1 month

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 18/9/21 20:27, Mark Sapiro wrote: > from mailman.interfaces.action import Action > def moderar(mlist, member): > memb = mlist.members.get_member(member) > if not memb: > print('{} is not a list member.'.format(member)) > return > memb.moderation_action = Action.hold > print('{} moderation_action set to hold.'.format(member)) That completely did it. The problem about finding the module was completely gone when I made a soft link in the same directory where mailman command is (in /usr/local/bin, for your info). Thank you very, very much.

4 years, 1 month

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 18/9/21 22:59, Mark Sapiro wrote: > On 9/18/21 11:56 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> Just a one more silly question: >> >> Where do I can find the diferent values that memb.moderation_action >> can take? (I want to prepare the "unhold" script too) > > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/act… > Thanks: It's perfect

4 years, 1 month

[MM3-users] Re: disable body transcoding

by Markus Schaaf

Am 22.09.21 um 19:26 schrieb Mark Sapiro: > This is probably due to the message body charset being utf-8. The Python > email library used by Mailman encodes utf-8 message bodies as base64. Thank you very much for that helpful clue. > Note this is just a guess and could be a disaster so test it before > trying it in production. It doesn't look dangerous ... :-) But ok, maybe it's a good idea to have a playground anyway. I'll report back after setting up a test system and trying your patch. BR

4 years, 1 month

[MM3-users] Re: API privileges question for mailman3

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/14/21 12:41 PM, bob B wrote: > > So I just wanted to confirm there is no way to limit API access? What Mark said. > > For example I have a group that wants to use API access to mange > > their mail lists, but from what I can gather, if I give them > > access to the API they would have access to ALL the mail lists > > etc.. You could give them a separate VM or container with their own instance of Mailman. But that means they can't share user information with the main instance. Steve

4 years

[MM3-users] Re: Message IDs

by Stephen J. Turnbull

Mark Sapiro writes: > Note also that Mailman core communicates with archivers to determine > what goes in the Archived-At: header and this value is usually based on > the Message-ID:. Changing the Message-ID: could possibly render that > value incorrect. I forgot about that. MTAs allow existing Message-IDs through though, so Mailman could generate that outgoing Message-ID, add it to the the message, and put that in the Message ID hash. I'm obviously not in favor of doing that, though.

4 years

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Quanah Gibson-Mount

--On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: >> >> My conclusion: >> I ask you to consider these experiences in an update for the mailman3 >> packages in debian bullseye. It would save time, questions and nerves. > > > Issues with Debian packaging should be directed to Debian. Or as previously discussed, the debian packages should be avoided entirely. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

3 years, 11 months

Search results for query "sapiro"