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

[MM3-users] Re: modify subscription page by mailinglist?

by Mark Sapiro

On 1/10/22 5:32 AM, Lars Schimmer wrote: > > And I think I could fiddle out how it works. But in general, e.g. a > custom page per mailinglist for the "list information page" is a bit > more work than expected and I will not follow this idea. > (e.g. adding a logo per list, ...) I don't know if this would meet your requirement or not, but the Summary section of the list information page is built in part from list settings. The first line is the list's `description` and the next part is the lists `information`. The `information` can contain HTML so you could include a logo there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 11/16/22 15:52, Dan Caballero wrote: > Thanks Mark! > > We're using GNU Mailman 3.3.5 (Tom Sawyer). The tests I did via the Docker container used a database dump from our production MySQL server. > > We have 2050 lists. The address table in the database has 95028 rows. For what it's worth, mail.python.org has 188 Mailman 3 lists and 85852 rows in the address table, and handling a message waiting moderation takes only a second or two. Thus, whatever the scaling issue is, it's likely related to the number of lists as opposed to the number of list members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: ham-confirm+3ee85b006eeb5897ca6f53b093cb063672f6a784@example.com

by Mark Sapiro

On 2/17/21 1:27 AM, Jörg Klein wrote: > I want add some subscribers. When the I get this error message: > I have no address ham-request(a)example.com. Do I need for every mailing list more as the mailing list email address? How does your MTA deliver to Mailman? If you are using one of the Postfix or Exim configurations described at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>, things should work, but in any case, for every list you need to deliver all of the following to Mailman: LISTNAME(a)example.com LISTNAME-bounces(a)example.com LISTNAME-confirm(a)example.com LISTNAME-join(a)example.com LISTNAME-leave(a)example.com LISTNAME-owner(a)example.com LISTNAME-request(a)example.com LISTNAME-subscribe(a)example.com LISTNAME-unsubscribe(a)example.com -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

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

by Mark Sapiro

On 7/22/21 12:34 PM, Sarah H wrote: > Hyperkitty works fine in browser at https://lists.client.org/archives/ and the vast majority of my testing messages are made through the web browser, though I've tried via email as well with the same results. > > curl to http://127.0.0.1:8000/hyperkitty/ results in the same error as above. What if you ``` curl http://127.0.0.1:8000/archives/ ``` and what to you get in a browser from ``` https://example.com/archives/api/mailman/urls ``` And what's in urlpatterns in /opt/mailman/mm/urls.py? I'm sure it contains ``` url(r'^archives/', include('hyperkitty.urls')), ``` but I'm suspecting it doesn't contain ``` url(r'^hyperkitty/', include('hyperkitty.urls')), ``` -- 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

[MM3-users] Re: importing from google groups.

by Mark Sapiro

On 1/22/19 7:33 PM, Abhijith PA via Mailman-users wrote: > Hello. > > > Is it possible to import google group archives to mailman3. With this[1] > script, I was able to export archives. Please let me know if anyone have > tried and succeeded. > > > --abhijith > [1] - https://github.com/icy/google-group-crawler It looks like the script produces a mbox format output file, so all you need to import the archive is to run the django admin job hyperkitty_import to import the mbox. Run hyperkitty_import with the --help option for information and note that if there are existing messages in the target archive, you need the --since option to get older messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

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

by Mark Sapiro

On 7/15/21 11:08 AM, Sarah H wrote: > the logs definitely look like it's the hyperkitty URL. I have tried several different variations of the default URL, the sites URL, and anything else I can find but they all return either a not found or bad response error. is there any way I can find specifically what the URL is aside from changing the config and making a new post each time? Have you tried the base URL that you use to access HyperKitty from your web browser?, E.g., for this list 'https://lists.mailman3.org/archives/' Also, it should be a URL you can get from a shell on the server with curl. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/6/22 10:35 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > It looks the right way (I have apache running in that server) to solve > it. What intrigues me is the fact that I didn't change anything in the > apache config or update apache itself. That doesn't matter. With your older HyperKitty and mailman-hyperkitty the MAILMAN_ARCHIVER_KEY was sent from mailman-hyperkitty to HyperKitty as a query fragment (key=...) in the URL. The changes in HyperKitty 1.3.5 and mailman-hyperkitty 1.2.0 send it in an Authorization HTTP header instead, so before, it didn't matter if the Authorization HTTP header was dropped, now it does. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Excluding archives from a mailman3web database backup

by Mark Sapiro

On 6/23/22 17:38, Andy Smith wrote: > > Is that a realistic proposal? i.e. does a typical maildir2mbox > conversion script generate something that "manage.py > hyperkitty_import" would be happy with when run on prototype's > maildir? Yes. > If so, is it safe to just exclude every table starting with > "hyperkitty_" from the database backup of mailman3web? Dumping only > the schema for these, I mean, so that an import would restore empty > tables. That should be safe. The hyperkitty_import job should populate the tables as necessary. You will lose things like favorites, last views, tags and votes, but that may not be important. -- 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: Link to account

by Mark Sapiro

On 4/11/23 23:08, Lars Bjørndal wrote: > > I would like to have postorius at .../mailman3 and admin, accounts etc. under .../mailman3/admin .../mailman3/accounts etc. Try this. In urls.py ``` urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('mailman3/archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('mailman3/accounts/', include('allauth.urls')), path('mailman3/admin/', admin.site.urls), path('mailman3/', include('postorius.urls')), ] ``` In apache ``` <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3/archives" "http://127.0.0.1:8000/mailman3/archives" ProxyPass "/mailman3/accounts" "http://127.0.0.1:8000/mailman3/accounts" ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/mailman3/admin" ProxyPass "user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" </IfModule> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/25/21 5:18 AM, Marco Marinello wrote: > Finally have found my issue... Apache automatically removes the header, see https://stackoverflow.com/questions/26549250/apache-strips-down-authorizati… . Hope it can be useful for somebody else! I'm glad you found this, but I'm a bit confused. I run a few servers with apache 2.4 proxying to gunicorn and I don't see the issue. Perhaps this is a uWSGI or mod_wsgi issue. In any case, it can possibly be avoided by setting base_url in mailman-hyperkitty.cfg to something like base_url: https://127.0.0.1:8000/archives or whatever localhost port the WSGI application is listening on to bypass apache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Search results for query "sapiro"