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

[MM3-users] Re: Do not show archives to public

by Mark Sapiro

On 6/18/19 5:21 PM, Andrew Bernard wrote: > > This resulted in dozens of messages about Django errors, when I turned on > Private Archives, and then accessed the page. Is that to be expected? [Hard > to imagine.] Perhaps you have to wait? But how long typically? This is definitely not expected. What are the errors? Including tracebacks from logs if any. As far as waiting is concerned, I think the thing you might be waiting for is the Django sync_mailman job which, if you have set up cron to run the periodic Django jobs, runs daily, but you can run it manually via the Django admin `runjob sync_mailman` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Mark Sapiro

On 10/29/19 8:21 PM, Franklin Weng wrote: > Yes, it is checked. Have you checked Mailman's logs - Mailman's var/logs/mailman.log in particular? Do messages received from the list have an Archived-At: header? What's in /etc/mailman3/mailman-hyperkitty.cfg? In particular does the [general] setting base_url define a URL that accesses hyperkitty and does the [general] setting api_key match the MAILMAN_ARCHIVER_KEY setting in /etc/mailman3/mailman-web.py, but note that the MAILMAN_ARCHIVER_KEY setting is quotes because it is a Python string assignment and the api_key setting is not quoted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Easiest way to install a new mailman3 deployment?

by Mark Sapiro

On 1/5/21 3:37 PM, Ruth Ivimey-Cook wrote: > > I have only split mailman in two: mailman-core with the email-related > parts, and postorius for the UI. As yet, although Hyperkitty "works", I > haven't addressed the fact that mails get archived in folders on the > email host and so (for me) hyperkitty can't see them. Ideally, they > would be on the postorius/hyperkitty host, or possibly network shared The emails that get archived in folders on the Mailman core host are archived by the 'prototype' archiver, not by HyperKitty. HyperKitty archived emails are in tables in Django's database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors

by Mark Sapiro

On 7/18/24 11:12 AM, willie.castillo(a)caemilusa.com wrote: > Mark first let me thank you for your assistance with this. I don't believe I mentioned that this is a fresh/new installation I'm performing on an AlmaLinux 9.4 VM. I have searched everywhere for a solid Mailman installation on AlmaLinux document/process but, I haven't had any luck. I tried following documentation on this site and I only found this https://docs.mailman3.org/en/latest/install/distro.html. Did you see my post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… We recommend installing Pypi packages in a virtualenv. Doc is at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Help on removing moderators

by Mark Sapiro

On 3/4/20 12:30 PM, sean_sullivan(a)rhoworld.com wrote: > Never mind, I was able to figure it out. If anyone else is searching for a similar issue. Here again, using mailmanclient can work, but it is very round about. I.e. you are calling client which makes a REST call via http to core to do what you want when you can talk to core directly. > from urllib.error import HTTPError > > def remove(mlist): > curr_list = mlist.fqdn_listname > my_list = client.get_list(curr_list) > r_addresses = ['test1(a)example.com', 'test2(a)example.com', 'test3(a)example.com'] > for email_addr in r_addresses: > try: > my_list.remove_owner(email_addr) > except HTTPError as err: > print (email_addr,my_list, err) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Editing a Subscriber's Mailman 3 list Settings

by Mark Sapiro

On 7/1/21 11:08 AM, Terry Earley wrote: > Admin users can edit subscriber's Mailman list settings. Once that > subscriber registers as a user, then only he/she can edit. Admin no longer > has permission to change these settings. > [image: editSubscriberByAdmin.gif] The image removed by this list's content filtering was a partial screenshot of a Postorius member options page with the error message "Cannot convert parameters: acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings" What Postorius version is this? I am unable to duplicate this either as a site admin or a non-site-admin list owner with Postorius from the head of the gitlab branch (1.3.5b1). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Apache shows No Lists

by Mark Sapiro

On 5/21/23 15:15, ceo(a)sartrack.nz wrote: > Running Debian 11. > > I have 6 mailing lists, but Apache2 says there are no lists. > I have not been able to set up Postorius because nowhere is any information on *where* the configuration file is supposed to be located. If Postorius is not running, what is Apache looking at? > I have found an example in > /usr/share/doc/python3-django-hyperkitty/examples/settings.py > > But I don't know if this example is the right one, and I have no idea where the final file should go... Please follow the doc at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. This is our current recommendation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/10/21 3:22 PM, David Newman wrote: > On 12/10/21 12:57 PM, Mark Sapiro wrote: >> >> Are you using uwsgi or some other wsgi server. > > uwsgi, per the venv and PDF docs. Thanks for the fix. > > Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives > replace the 'proxy_set_header' ones in the venv doc? > > Looking at the uwsgi doc, it seems they might do different things. If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working for you, then I'm satisfied that the docs are OK now and we don't need to say anything about uwsgi_pass. > It's not the situation I have to deal with, though. Short of changing a > long-standing URL, what I'm looking to do is have "/" continue to > default to roundcubemail, and have users type in longer URLs for MM3 and > other services. I think you can set the document root to the roundcubemail root and then set locations for the Mailman destinations as, e.g. location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } I haven't tried anything like this, so I'm not sure it will work, but I think so. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 08:14, Eggert Ehmke via Mailman-users wrote: > I edited this file: > venv/lib/python3.9/site-packages/mailman/commands/cli_members.py > > The content at line 107ff is: > #patch of Mark Sapiro > # if email_only: > if email_only or not address.display_name: > print(address.original_email, file=outfp) > else: > # print(formataddr((address.display_name, address.original_email)), file=outfp) > print(f'{address.display_name} <{address.original_email}>', file=outfp) > > This file is actually executed when I call mailman members. I verified this by uncommenting the first (old) print line. Now each address is printed twice (as expected), with the utf8 code in both lines in case of umlauts. In that case the address.display_name value is the RFC 2047 encoded name. One way this can happen is if the subscribe was via email prior to Mailman 3.3.3. See https://gitlab.com/mailman/mailman/-/issues/802. You could try something like this to fix these. ``` mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> um = getUtility(IUserManager) >>> from email.header import decode_header, make_header >>> for address in um.addresses: ... decoded = str(make_header(decode_header(address.display_name))) ... if decoded != address.display_name: ... address.display_name = decoded ... print(f'Fixed {decoded}') ... >>> # while you're at it do users too. >>> for user in um.users: ... decoded = str(make_header(decode_header(user.display_name))) ... if decoded != user.display_name: ... user.display_name = decoded ... print(f'Fixed {decoded}') ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Editing "automatic responses" tab i Postorius does not work

by Mark Sapiro

On 5/21/17 12:49 PM, David Krantz wrote: > But this one is already exposed. But I cannot change it anyway as the > tab requires URIs for the different templates to allow saving. I do > not use those URIs as I have configured the defaults as I like them. I > tried once and it failed so I decided to set the defaults instead. I'm sorry for totally missing your point in my prior reply. I now understand. The page should not require entries in those fields. This is now reported at <https://gitlab.com/mailman/postorius/issues/186>, and we will fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

Search results for query "sapiro"