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

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/7/25 02:30, MegaBrutal via Mailman-users wrote: > On Mon, Apr 7, 2025, 03:04 Mark Sapiro <mark(a)msapiro.net> wrote: > >> so it is saying there is only one choice for sender which I think means >> there is only one address associated with your login. That still doesn't >> explain why it thinks you're not a list member. >> > > Indeed, it doesn't explain. Are there any maintenance scripts or DB queries > you recommend to run to get to see what's happening under the hood? Not offhand. What is the exact email address that you are logging on to the web UI with. Does it match exactly with the address of a list member or are there mixed-case differences? You might try an interaction like this: ``` mailman-web shell Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from django_mailman3.lib.mailman import get_mailman_client >>> client = get_mailman_client() >>> list_id = 'test.example.com' # your actual list_id >>> rest_list = client.get_list(list_id) >>> email = 'user(a)example.com' # your actual email >>> member = rest_list.get_member(email) >>> member This should print something like <Member 'user(a)example.com' on 'test.example.com' with role 'member'> ``` This is exactly what HyperKitty is doing except in your case rest_list.get_member(email) is throwing a ValueError exception instead of returning the member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

[MM3-users] Re: MM3 Docker

by Mark Sapiro

On 1/6/19 6:54 AM, Odhiambo Washington wrote: > > If I could run MM3 using the apt-get install method, perhaps that would > have made my life a bit easier, hoping that MM3 can actually be run in > parallel with MM2.1 on the same host. Is anyone doing that already?? Yes. I am on two production and one development machines. See, e.g. <https://mail.python.org/mailman/listinfo/> and <https://mail.python.org/mailman3/> One caveat here is I install both Mailman 2.1 and Mailman 3 from source on all these machines. I don't know for example if the Debian/Ubuntu packages play well together. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> for more on how I install MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Affinity Mailman Is Now Beta

by Mark Sapiro

On 6/18/20 12:44 PM, Brian Carpenter wrote: > Dear Mailman Admins and Users, > > Affinity Mailman is our new admin interface for Mailman 3 and we intend > to use it to replace Postorius. It has been under development for about > 3 months now and it recently reached beta. Just to be clear, Brian has the full support of the GNU Mailman project in his endeavor to create a new web UI for Mailman 3, but "our" above means Brian and EMWD, not the GNU Mailman project. We of the GNU Mailman project are delighted that Brian is working on an alternative web UI, but we have no plan to abandon Postorius and HyperKitty. -- 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

[MM3-users] Re: Using external services for deliverability?

by Mark Sapiro

Mark Sapiro wrote: > On 7/10/20 8:10 PM, tom(a)gather.coop wrote: > > Makes sense. So given that the opendkim milter > > matches on the From header, am I correct in telling opendkim to sign emails from > > any email address with my domain? > > So my whole SigningTable might be something like > > > > * mail._domainkey.mydomain.com > > > > Yes. Actually, I knew there was more to it than that, but I had forgotten the detail. You can have *(a)mydomain.com mail._domainkey.mydomain.com as your SigningTable entry, but you need to specify SenderHeaders List-Post,Sender,From in your opendkim.conf. This will find the list address in the List-Post header of mail from your lists and that will be list(a)mydomain.com which will match the above SigningTable entry.

5 years, 7 months

[MM3-users] Re: Make archives private by default

by Mark Sapiro

On 1/8/23 06:40, Johannes Rohr wrote: > Dear all, > > in mailman2 there was a setting that ensured that the archives of newly > created lists are by default privat ( > > DEFAULT_ARCHIVE_PRIVATE = 1 > > > Is there something similar in Mailman3? Set [styles] default: private-default in mailman.cfg. There are other effects to this style. namely, in addition to setting archives to private, it also sets the subscription policy to confirm then moderate and sets the list unadvertised. If you want a style that's like ordinary discussion list style except with private archives, but advertised and subscription policy = confirm, you'd need to create a plugin with your own style. -- 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

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Mark Sapiro

On 1/28/23 11:48, Stephen J. Turnbull wrote: > Odhiambo Washington writes: > > > from mailman_web.settings.base import * > > from mailman_web.settings.mailman import * > > I think just putting these as close to the top as possible, and > including a comment (or two) saying that this is importing defaults > that can be overridden by any assignment made later in the file is > about as far as we can go for explaining. I've Just updated this. It now says: ``` # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * # Settings below supplement or override the defaults. ``` -- 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

[MM3-users] Re: Python is updated

by Mark Sapiro

On 4/29/23 01:44, Odhiambo Washington wrote: > On Sat, Apr 29, 2023 at 8:25 AM Lars Bjørndal <lars(a)lamasti.net> wrote: > >> So you have settings.py in /opt/mailman/mm rather than in /etc/mailman3? >> > > That's right - based on an earlier installation method before the official > virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> > one was put together, and that's why he has that shell file. > For a virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> > setup, your settings should live in /etc/mailman3 as stated. If you are interested in background on prior installation methods and their evolution, see https://wiki.list.org/x/17891998 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Subscribing users stuck in pending hell

by Mark Sapiro

On May 24, 2023 9:45:45 AM PDT, Quanah Gibson-Mount <quanah(a)fast-mail.org> wrote: >That shell script seems to have errors: > >>>> pendings = getUtility(IPendings) >>>> for token, data in pendings.find( >... token_owner=TokenOwner.subscriber, >... pend_type='subscription'): >... print("hello") >... >Traceback (most recent call last): > File "<console>", line 3, in <module> > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) >TypeError: find() got an unexpected keyword argument 'token_owner' Your Mailman core is too old for that script. Tell me your core version and I will try to make one that works for you. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

2 years, 9 months

[MM3-users] Re: Importing mailman 2 shows member's "Moderation Action" = "Default processing". But new members show = "None". Why

by Mark Sapiro

On 5/29/23 10:45, mrl(a)psfc.mit.edu wrote: > Thanks. Although IMHO I would prefer that the display show the actual action, and adding with a red asterisk to denote that it's the list default. It's a somewhat simple fix, although I've omitted the asterisk, because it's not important to me that it's the list default. Something like: I plan no further changes beyond <https://gitlab.com/mailman/postorius/-/merge_requests/811>, but if you were to submit a merge request, we'd consider it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Postorius admin/user guide

by Mark Sapiro

On 11/8/24 02:59, Florin Pasăre via Mailman-users wrote: > Hello, > We're trying to update mailman to version 3 from version 2, and I can't > seem to find some non-technical guide for Postorius, something like an > owners manual for all the configurations available in Postorius. > Is there such a thing? No, at this time there is not. All we have at the moment is https://docs.mailman3.org/projects/postorius/en/latest/ which isn't what you're looking for. You just have to page through the settings to see what's there. Hopefully the various categories are clear enough that if you're looking for something specific, you can find it easily. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Search results for query "sapiro"