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

[MM3-users] Re: mailman-web Cleaning Up a Few Issues

by Mark Sapiro

On 11/5/25 10:22, dap1--- via Mailman-users wrote: > Mark: I hope to do that but I am getting killed with emails in the mean time. I'm guessing all these issues stem from the incorrect location of django. How do I fix that? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I find it very difficult to help you when you don't report the results of things I suggest > Stephen: I can't find anything. Here is /opt/mailman/venv/lib/python3.12/site-packages/hyperkitty/jobs: > > empty_threads.py __pycache__ thread_starting_email.py > __init__.py recent_threads_cache.py update_and_clean_index.py > new_lists_from_mailman.py sync_mailman.py update_index.py > orphan_emails.py thread_order_depth.py The problem isn't with your virtualenv install. It is with some left over crontab from a prior attempt to install Ubuntu packages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Re: Getting rid of held messages from the command line

by Mark Sapiro

On 03/19/2018 02:22 PM, Aymeric Mansoux wrote: > > Ah, so if I understand you correctly, as long as I'm on 3.1.1, I could > run into this issue again, but then: Yes, this issue will recur with Mailman 3.1.1 and a MySQL database. > - Would patching 3.1.1 with 5477a201 be enough to prevent further issues > until the next stable is released? I think so. The only potential issue is if mailman/database/alembic/versions/4bd95c99b2e7_fix_template_password.py is not in 3.1.1. I think it is, so I think it's OK, but if not, you'd need to modify mailman/database/alembic/versions/3f31035ed0d7_further_increase_pendedkeyvalue_value_.py to point to the 3.1.1 head of the alembic versions. > - How can I clean the current pendedkeyvalue table? With phpMyAdmin or the mysql command. I think you can just delete those entries from the pendedkeyvalue table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: HyperKitty Question

by Mark Sapiro

On 5/4/20 6:11 PM, Samir Faci wrote: > > I have nginx running with multiple website being serviced from the same > server. > > I updated the config where port 80 gets redirected to SSL. > > I tried setting mailman3-hyperkitty.conf to both: > > base_url: http://localhost/hyperkitty> base_url: https://lists.domain.com/hyperkitty/ > Either should be OK, possibly dependent of your nginx config. > But neither seem to be working. Does hyperkitty require traffic to be > going over port 80? No. https should work. Can you go to https://lists.domain.com/hyperkitty/ in a browser? Do you have api_key: set in mailman3-hyperkitty.conf and is it set to the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django settings. Note the value needs to be quoted in MAILMAN_ARCHIVER_KEY = 'the_value' and not in api_key: the_value because the former is a Python string and the latter is a config value. -- 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: Footer from templates not working - DB issue?

by Mark Sapiro

On 9/25/22 05:26, mailman--- via Mailman-users wrote: > Dear All, > I have a similar issue. Also on Debian 11. Also installed as Debian PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) > I am using sqlite3. When I do the SQL-query I get an URI which is in multiple reasons wrong > http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… The initial part of that URL is set from the Django setting `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to `http://localhost/mailman3/`, it should probably be just `http://localhost/`. > OK - the hostname could be changed but the path is not existing at all. > There is no file "list:member:regular:footer" on the complete filesystem. It's not a file. It refers to an entry in the postorius_emailtemplate table in the database which is retrieved via the Postorius API. -- 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: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 12:01 AM, Ken Alker wrote: > When I view a list via Postorius the "Held Messages" menu item has an inverse-red-"2" next to it, as if there are two held messages. There are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held messages should be in "pipeline" subdirectory). When I click on "Held Messages" I get "Something went wrong" followed by "HTTP Error 500: {"title": "500 Internal Server Error"}". How do I fix this? The held messages are not in any queue. They are stored in Mailman's var/messages/ hierarchy. They can be examined with `mailman qfile` Also, there is a long thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and maybe others that might be relevant. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Topics - Tags

by Mark Sapiro

On 3/21/24 21:10, Mark wrote: > Hi, > > I'm reading the docs on "Message tagging" > (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) as saying shell access is needed to: (a) enable topics, and (b) write the keywords. > > In Mailman 2 there is an Admin web UI for "Topics". Is there such a web > UI that can be enabled in Mailman 3 so that the list owners can create > topics (tags) in their lists? At this point, topics are not exposed in REST. Managing them via Postorius first requires updating the REST API to read and set the topic attributes and then updating Postorius to display/set them. Further, there is currently no implementation for list member topics of interest either in Mailman core or the REST API. I.e., there is no way for a list member to indicate topics of interest. -- 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: Moving existing lists to a new domain

by Mark Sapiro

On 11/21/24 07:43, Jeremy Stanley wrote: > > Preparing to test this, I poked around the schema a bit and noticed > that the domain names are also embedded as strings in the following > fields: > > django_mailman3_maildomain.mail_domain > django_site.domain > django_site.name These are all Django things. You can modify those values in the db. Note that django_site.name is just a name and doesn't need to be the exact domain name. > domain.mail_host This is Mailman core's domain table. Again, you can modify the value in the db. > Can anyone think of any additional tables/columns which would need > updating for this? I'll see if scanning a dump of the full DB > content turns up anything I might be missing too. Thanks again! I don't think there's anything else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: changing the main template for subscriptions and more

by Mark Sapiro

On 6/22/21 2:41 AM, Andreas Barth wrote: > > I'm using this patch (however, german-only) > > > Andi > > > diff --git a/src/mailman/templates/de/list:admin:action:post.txt b/src/mailman/templates/de/list:admin:action:post.txt ... > diff --git a/src/mailman/templates/de/list:admin:action:subscribe.txt b/src/mailman/templates/de/list:admin:action:subscribe.txt ... > diff --git a/src/mailman/templates/de/list:admin:action:unsubscribe.txt b/src/mailman/templates/de/list:admin:action:unsubscribe.txt ... > diff --git a/src/mailman/templates/de/list:user:notice:welcome.txt b/src/mailman/templates/de/list:user:notice:welcome.txt ... It isn't necessary to patch the source in this way. If you put the modified templates in Mailman's var/templates/site/de/ directory, ensuring that the Mailman user can read them, they will be used and you won't have to patch the source every time you upgrade. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/15/21 2:11 PM, Sarah H wrote: > I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get: > > curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number A 301 from http will be an issue always. I'm not sure where the `wrong version number` comes from. This could be the issue. If I do for example, curl -X POST https://lists.mailman3.org/archives/api/mailman/archive I get the response <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> This is the expected response. You need to figure out what base_url will give you a similar response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: hyperkitty url not found

by Mark Sapiro

On 3/9/22 07:13, Eggert Ehmke wrote: > I installed mailman3 in a virtualenv following this guide: > > https://docs.mailman3.org/en/latest/install/virtualenv.html[1] > The mailinglists work very good. However, I did not manage to set up hyperkitty archiving. > Archiving is enabled in mailman.cfg. I can call the Archive site from my configuration page, > but it is empty. > > In my /opt/mailman/mm/var/logs/mailman.log > file I find error messages like: > > HyperKitty failure on http://localhost/mailman/hyperkitty/api/mailman/archive: > The requested URL was not found on this server. Your setting in mailman-hyperkitty.cfg for base_url is base_url: http://localhost/mailman/hyperkitty/ It needs to be the base URL for accessing hyperkitty, possibly base_url: http://localhost/mailman3/hyperkitty/ or whatever you use to access hyperkitty from a web browser. Whatever it is, `<base_url>/api` should return a page of API documentation. -- 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

Search results for query "sapiro"