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

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Mark Sapiro

On 6/24/16 8:18 AM, John Griessen wrote: > On 06/18/2016 02:10 PM, Mark Sapiro wrote: >> I think in the >> long run, you'd be better off with Mailman 3. > > > Is it time to install version 3? > > Is that going to work with different rewrite rules behind nginx? > > Will it cure my problem with moderation and nginx and https? If you are going to post to mailman-users(a)mailman3.org, please join the list. That way you will see replies to your posts such as the one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. You can join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>. The reply addresses your first question. With respect to your other questions, I think you have resolved your http/https issues in MM 2.1. MM 3 works similarly, but perhaps more obviously. When you create a domain in MM3 you specify a web URL for the domain's web UI. If this is an https URL, you won't have the issues you saw. There is another way to address this, and that's in the web server (nginx in your case) when you configure the web server to redirect http to https with a 301 Moved Permanently status (or maybe a 302), this tells the browser to issue a GET for the new URI, even if the original request was a POST. Thus the POST data is lost. That is the underlying issue. If instead, you configure the web server to issue a 308 Permanent Redirect instead, this tells the browser to issue a request for the new URI using the original GET/POST/whatever method, so the browser SHOULD reissue the original POST to the new URI. This will work provided the browser recognizes 308 and acts appropriately. Thus, fixing the scheme in Mailman is the more reliable solution as it doesn't depend on the browser knowing what to do. See, e.g., <https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 3 months

[MM3-users] Re: mailman2 import not working

by Mark Sapiro

On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote: > > ------------------------------------------- > mailman create -o <foo(a)example.com> foo-bar(a)lists.example.com > mailman import 21 foo-bar(a)lists.example.com path/to/config.pck > ------------------------------------------- You don't need to specify an owner for `mailman create`. The owners will be imported. > After everything done tried a test mail, but didn't reach any of the > inbox though mail is archived. mailman.log says message is accepted > > ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137(a)xxxxxx.org> > Nothing after this. It is surprising that no exception/traceback/SHUNTING message(s) are logged. That would seem to say that Mailman's `out` runner is not running. I think Mailman's var/ directory in the Debian package is /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? Is there a .pck file either in shunt/ or in out/? what does `ps -fwwu list` show? There should be a lot of runner processes. Is there one with argument --runner=out:0:1? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

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

by Mark Sapiro

On 7/22/21 11:41 AM, Sarah H wrote: > here is the full error message. Nginx proxies on http. > > https://pastebin.com/raw/TUf5dYi8 Thanks for the log. It is basically just confirming what we see with this. > the curl commands above result in. > ... > (venv) [mailman@sysname sarah]$ curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive > curl: (52) Empty reply from server I am at a loss to understand why HyperKitty isn't responding. Are you able to access HyperKitty normally from a web browser? Do you get a response from ``` curl http://127.0.0.1:8000/hyperkitty/ ``` If so, what? What you should get from ``` curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive ``` is ``` <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> ``` You should get the same response as a web page if you go to https://example.com/hyperkitty/api/mailman/urls. Do you? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Mailman 3 questions (purge archives, list metrics, and auto discard held messages)

by Mark Sapiro

On 8/2/22 08:53, bob B via Mailman-users wrote: > Mark, > > Thanks, I know you are not a docker guy, but any idea on how to run this in the maxking docker environment? Or maxking any thoughts? > > Not sure if the docker environment has all the components or can get them all to run this script, but I have been trying to figure it out. > I assume it should be run in the mailman-web container? we are using an external database, but I don't think that should matter. Yes, it would run in the mailman-web container in the same way the `manage.py` command is run for example. Looking at https://asynchronous.in/docker-mailman/web/#django-management-commands, I think this would be something like ``` $ docker exec -it mailman-web python3 prune_arch3 yyyy-mm-dd ``` after saving the prune_arch3 file in the same place as manage.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Mark Sapiro

On 11/25/23 6:35 AM, Jered Floyd wrote: > > OK -- my turn to ask a question... > > I created a new domain and lists in my (functioning) Mailman 3 install. > > Messages to these new lists are successfully delivered via LMTP to Mailman and then disappear. They are in the shunt queue, with a source queue of "in". There are no exceptions logged in my mailman.log. When Mailman shunts a message, it always attempts to log the exception to its error.log which by default is written to mailman.log. If you can't find these messages, either you aren't looking in the right place or Mailman doesn't have permission to write the log. > Unshunting the message has no effect, and no logs are generated. Actually, the message is moved back to the `in` queue and shunted again. -- 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: Adding Mass Subscribe custom template error

by Mark Sapiro

On 1/29/25 11:20, Arte Chambers via Mailman-users wrote: > Ok I did install using the > https://docs.mailman3.org/en/latest/install/virtualenv.html > > I added > ``` > POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' > ``` I hope you didn't add the above literally without replacing www.example.com with your actual host name. It should be ``` POSTORIUS_TEMPLATE_BASE_URL = 'list.louisvillecommunitygrocery.com' ``` > to /etc/mailman3/settings.py and restarted mailman services > > However I'm still getting the same error from mailman.log > > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', > port=8000): Read timed out. (read timeout=5) I don't understand why it should still be trying to connect to localhost:8000. Also, I don't understand why localhost:8000 times out. What is your setting for localhost in /etc/hosts? it should be `127.0.0.1`. If it is `::1` that could be the issue. > Not sure if I'm editing the correct config file. /etc/mailman3/settings.py should be correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Mark Sapiro

On 8/25/25 12:42, Flo via Mailman-users wrote: > Hi, > > I have setup in Debian Trixie mailman3-full and came that far, that I > have created a mailing list. I can sent emails to the members. Your primary support resource for the Debian package is Debian. See https://wiki.list.org/x/12812344 > However when I send from an email which is non-member the message is > held. If I want to accept this message as list admin, I get: > > `An error occurred while processing your request.` > > And I get an email: > > `Internal Server Error: /mailman3/postorius/.../held_messages > > TemplateSyntaxError at /postorius/lists/.../held_messages > 'humanize' is not a registered tag library. Must be one of: You need to add 'django.contrib.humanize' to the INSTALLED_APPS list in settings.py. If you Debian packages don't do this, it should definitely be reported to Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/10/22 22:22, Stephen J. Turnbull wrote: > > Will let you know if I find anything. Mark will be back soon, too. Yes, I'm back and am looking at this. I'm looking at the traceback at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and I would like to get a copy of the shunted 1662376669.3194733+25b74de3b7cd8a28d0c3cf5b6cc6fc582726efec.pck file. If that is not available, any of the shunted files from the same `Uncaught runner exception: 'list' object has no attribute 'encode'` will do. Also, the same post contains a traceback from mailman_hyperkitty indicating the message has no Message-ID header. This is possibly related to the fact this is an anonymous list. For anonymous lists, the original Message-ID is removed because it can reveal the sender's domain, but it should always be replaced by a generated one. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/clean… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/9/25 10:04, dap1--- via Mailman-users wrote: > > I can now see the list. I can't find the URL for members so I'm not sure if this really worked. Have you created a Django superuser for yourself? mailman-web createsuperuser You need to do that and then go to https://your.host/accounts/login/ and log in as that user. Then if you go to https://your.host/mailman3/lists/lllllllllll@ddddddddd.net/ you will see a Users dropdown in the secondary nav bar and can view members, nonmembers, moderators and owners. You can also go directly to https://your.host/mailman3/lists/lllllllllll@ddddddddd.net/members/x/ where x is one of member, nonmember, moderator or owner. > It seems the archives were imported but when I go to that page there are no entries: To what URL are you going? Are you logged in? depending on the list's archiving settings you may need to be logged in as a superuser or list member to see the archives. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: Postfix Hooks and Fetchmail

by Mark Sapiro

On 11/13/25 08:33, dap1--- via Mailman-users wrote: > I'm using fetchmail to feed mailman3 and am having a problem with the postfix hooks. My list name is llllllllll(a)ddddddddd.net. However, fetchmail passes the email to lllllllllll@localhost. So I am getting this error in the mail log: > > Out: 550 5.1.1 <llllllllll@localhost>: Recipient address rejected: User unknown in local recipient table > > Is there something I need to add to mailman's recipient table, fetchmail or an alias in postfix? You have probably configured Postfix per https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mta which is based on https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. The issue is the postfix_lmtp file referred to in transport_maps and local_recipient_maps only have addresses in the ddddddddd.net domain. I think you can solve this by instead adding 'localhost' as an alias domain for the ddddddddd.net domain and configuring Postfix per https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

Search results for query "sapiro"