Search results for "Postorius" - Mailman-users

Re: Not able to start mailman server

by Stephen J. Turnbull

Mark Sapiro writes: >>>>> Kartheek wrote: > > I am trying to setup postorius using this website - I've used up all my bandwidth for now with the "can't send mail in Docker" thread, but FWIW Kartheek appears to be using Homebrew to manage third party packages on Mac, and in particular to install Python. I don't recall specifically with respect to Python, but I suspect that there's a "Homebrew system 'python'" (I know Homebrew does that with certain important programs that the Homebrew system depends on). That might very well confuse pip and other setup programs, since Homebrew likes to put stuff in places where you normally wouldn't find them to avoid conflicts (eg, multiple versions of Python). I can't be more specific about problems, and you'd hope that such stuff would "just work", but that might at least explain Mailman looking for stuff in "wrong places" (which might actually be right for Homebrew). Steve

5 years, 3 months

REST API for list owners/moderators

by Stephen J. Turnbull

mathias(a)koerber.org writes: > Does Mailman 3 have an REST API that allows list-owners/moderators > to perform list-management functions without having access to the > whole server/other lists etc? No. You can provide selective access to a selection of REST API endpoints via a front-end webserver such as Apache or nginx, but it would be rather painful, and possibly also rather insecure.[1] > The documentation seems to only indicate a single one-admin-user > REST API that should not even be accessible from outside? That's right. If the documentation only "indicates" that, we should fix the documentation. The point of separating Postorius from core was to put authentication and authorization in the hands of people who know how to do it (ie, Django). Footnotes: [1] That depends on what threats you're worried about. But the endpoint hierarchy is designed to make sense to application programmers, not to make it easy to disable access to "dangerous" endpoints that allow deleting lists or extracting user information.

2 years, 10 months

Re: Issues with Mail delivery after Mailman 3 installation

by Stephen J. Turnbull

Chihurumnaya Ibiam via Mailman-users writes: About disabling dovecot: > I don't plan on shutting down the host anytime soon, so hopefully, > I remember to the next time it restarts. systemctl stop dovecot systemctl disable dovecot systemctl daemon-reload should do the trick without rebooting the host. > Yes, postfix_lmtp table is set in transport_maps, virtual_mailbox_maps, > relay_domains, local_recipient_maps. Do you have lists.sugarlabs.org in $virtual_mailbox_domains? As Mark points out, virtual mailboxes make life more complicated. Also, I don't think postfix_lmtp should be in $relay_domains (that table contains addresses which won't match domains being looked up). If anything it should be postfix_domains. > > It's problematic for Mailman because that means that *all* local mail > > will be delivered to Mailman, which will reject it if it's not > > list-related. > I'm totally fine with this because that's why we setup the host, I'm sorry, that was unclear. By "list-related", I meant that "the key Postfix is trying to match is an exact match for a key in the postfix_lmtp table". Because these are hash tables, it is Postfix's responsibility to strip "+extension" from the recipient address before presenting the stripped address to the table for matching -- the table can't do it. Specifically, this applies to the confirmation and VERP cookies that may be attached to addresses for various reasons. > a mailing list, which should work just fine but then it seems > they need to connect to this host. > 165968 Feb 5 04:48:46 lists postfix/smtp[1941010]: connect to > weblate.sugarlabs.org[2001:5a8:601:f::214]:25: Connection refused > 165969 Feb 5 04:48:46 lists postfix/smtp[1941010]: B785D1A897F: to= > <root(a)weblate.sugarlabs.org>, relay=none, delay=17323, > delays=17323/0.02/0.33/0, dsn=4.4.1, status=deferred (connect to > weblate.sugarlabs.org[2001:5a8:601:f::214]:25: Connection refused) This is a problem at weblate.sugarlabs.org. Is it supposed to be receiving mail? I don't think that this is an authentication problem (SASL authentication takes place after connection), although if "weblate" expects authenticated TLS that might be the problem. So "lists" needs to be whitelisted (eg in $mynetworks) at weblate (I suppose Postfix is also the MTA at "weblate"?) If you have only the toplevel domain sugarlabs.org whitelisted, you may need to set another parameter to automatically include subdomains such as lists.sugarlabs.org. > No, I'm not running mailman as root, it's run as mailman. > Seeing as that's the case, would I still need to change lmtp_port? Yes, as far as I know. That's because by convention ports < 1024 can only bound to programs running as root (enforced by the kernel). I don't understand how Mailman is receiving mail configured to listen on port 24. This may have something to do with dovecot running. However I really don't understand the lsof output, because you present logs that indicate that Mailman is processing mail for lists, but nothing was listening or connected on port 24. You also say Postorius and HyperKitty are running, but nothing showed up on port 8000, which is where they would be listening. Maybe I got the lsof options wrong, but it did find Postgres and Mailman's REST API. > It did get it working, I can see mail being sent in the logs. > I sent a ping to the systems list just to get delivery confirmation > and I'm yet to get a response. I don't have an idea what's going on yet. The mail you see being sent in the logs, is that to a gmail address? Or is it a sugarlabs.org address? (Both of these seem to be problematic at the moment.) > > > > What does "lsof -i @127.0.0.1 -i '@[::1]' | grep 24" output? > > > > > python3 1592922 mailman 27u IPv4 177685024 0t0 TCP > > localhost:8001 (LISTEN) > > > python3 1592949 mailman 27u IPv4 177685024 0t0 TCP > > localhost:8001 (LISTEN) > > > python3 1592950 mailman 27u IPv4 177685024 0t0 TCP > > localhost:8001 (LISTEN) > > > > The above are Mailman (actually, a gunicorn application) listening for > > connections to its REST API. These are HTTP listeners used by > > Postorius and HyperKitty (I guess those aren't running?), not for email. > > > > Postorius and HyperKitty are running. But they should show up as several Python applications running as mailman, listening or connected on port 8000. But they're not here. Try "lsof -i :8000 -i :24". > This is one that's consistent with Dovecot in the logs; This is Postfix sending a non-delivery notification about A26F71A8977: > 157323 Feb 4 12:27:02 lists postfix/bounce[1587396]: A26F71A8977: sender non-delivery notification: AC7381A8978 The <> tells us that this is the nondelivery notification referred to as AC7381A8978 so there's no return address to send to: > 157324 Feb 4 12:27:02 lists postfix/qmgr[1593314]: AC7381A8978: from=<>, size=3129, nrcpt=1 (queue active) postfix/local looks at mailbox_transport and sends it to lmtp, where dovecot is listening; > 157325 Feb 4 12:27:02 lists postfix/local[1593315]: AC7381A8978: passing <mailman(a)lists.sugarlabs.org> to transport=lmtp > 157326 Feb 4 12:27:02 lists dovecot: lmtp(1600482): Connect from 127.0.0.1 Postfix is done with A26F71A8977, and pops it off the queue: > 157327 Feb 4 12:27:02 lists postfix/qmgr[1593314]: A26F71A8977: removed dovecot denies knowing about a local user named "mailman", rejecting it: > 157328 Feb 4 12:27:02 lists postfix/lmtp[1593316]: AC7381A8978: > to=<mailman(a)lists.sugarlabs.org>, relay=localhost[127.0.0.1]:24, delay=0.04, > delays=0.02/0/0/0.01, dsn=5.1.1, status=bounced (host localhost[127.0.0.1] > said: 550 5.1.1 <mailman(a)lists.sugarlabs.org> User doesn't exist: > mailman(a)lists.sugarlabs.org (in reply to RCPT TO command)) dovecot says "I'm done here": > 157329 Feb 4 12:27:02 lists dovecot: lmtp(1600482): Disconnect from 127.0.0.1: Logged out (state=READY) > Which we've established that mailman doesn't know how to deliver to local > users. So that's a bounce from dovecot. I don't know enough about dovecot or your configuration of dovecot to guess what happened. > Could be, doesn't seem to be an issue at the moment so I won't worry about > it. The Message-ID is syntactically well-formed. I'm worried about side effects from the hostname not being the FQDN in mail protocols. As long as all the configurations for Postfix use the FQDN (Postfix is smart enough to abbreviate when that's useful), there shouldn't be any problems like that. > Yes, earlier when I set it up I had set the port for Mailman to use as 465. OK. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months

Re: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/23/19 5:22 PM, Franklin Weng wrote: > > Franklin Weng 於 2019/10/24 上午8:05 寫道: >> >> What may be possible wrong that I couldn't see Preferred Language >> settings in the web interface? > > I got it. It is implemented in postorius 1.2.5 but my Debian buster > contains 1.2.4-1 for now. Actually, there is no 1.2.5. The next release after 1.2.4 is 1.3.0, but you can still set preferred_language for the list using the REST API or mailman shell. For example in mailman shell $ mailman shell -l zh-l10n.lists.linux.org.tw Welcome to the GNU Mailman shell The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list >>> m.preferred_language <Language [en] English (USA)> >>> m.preferred_language = 'zh_TW' >>> m.preferred_language <Language [zh_TW] Chinese (Taiwan)> >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Re: Welcome Message

by Mark Sapiro

On 4/16/19 9:18 AM, brian(a)emwd.com wrote: > Thanks Mark. I added the POSTORIUS_TEMPLATE_BASE_URL to my settings: > > /opt/mailman/web/settings_local.py > > Now I get the following errors: ... > requests.exceptions.SSLError: HTTPSConnectionPool(host='mailman3.emwd.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/testlist.mailman3.emwd.com/list:user:notice:welcome (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)'),)) > Apr 16 15:38:44 2019 (28) 172.19.199.3 - - "POST /3.1/members HTTP/1.1" 500 59 > > I am confused by the SSL errors. I have a valid SSL certificate installed on mailman3.emwd.com. These errors occur whether the POSTORIUS_TEMPLATE_BASE_URL is using http or https. I'm confused too. What happens if you just do in a python3 interactive session >>> import requests >>> response = requests.get('https://mailman3.emwd.com/postorius/api/templates/list/testlist.mailman3.em…') and if you get this far >>> response.status_code >>> response.text -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

Re: FutureWarning: Use `header_id_prefix` instead

by Andreas Vetter

Am Tuesday, 28 July 2026, 11:06:42 Central European Summer Time schrieb Andreas Vetter: > Am Tuesday, 28 July 2026, 10:40:51 Central European Summer Time schrieb > > Andreas Vetter: > > Hi, > > after a recent update of the prerequisites using: > > pip install -U --upgrade-strategy eager mailman postorius django-mailman3 > > hyperkitty mailman-web > > > > I get warnings from the cronjobs: > > > > /opt/mailman/venv/lib64/python3.11/site-packages/readme_renderer/ > > markdown.py:44: FutureWarning: Use `header_id_prefix` instead > > > > gfm_extension_options.header_ids = _HEADER_ID_PREFIX > > > > What would be the best way to silence the warnings? Google does not find > > the warning message yet. > > > > Cheers, > > > > Andreas > > Quick fix is to change line 44 in /opt/mailman/venv/lib64/python3.11/site- > packages/readme_renderer/markdown.py from > gfm_extension_options.header_ids = _HEADER_ID_PREFIX > to > gfm_extension_options.header_id_prefix = _HEADER_ID_PREFIX > > Greetings, > Andreas Since this is a readme_renderer issue, I opened an issue there: https://github.com/pypa/readme_renderer/issues/380 Andreas

3 months, 1 week

Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 1:10 PM, Brian Carpenter wrote: > > Ok. The first thing however is did I miss a step? Not really. The problem is FILTER_VHOST = True doesn't work for web hosts that aren't email hosts. > Here is the complete error that is sent to me via email as superuser: > > > Internal Server Error:/mailman3/lists/ > > KeyError at/mailman3/lists/ > 'file' > > Traceback: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" > in inner > 34. response = get_response(request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 115. response = > self.process_exception_by_middleware(e, request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 113. response = wrapped_callback(request, > *callback_args, **callback_kwargs) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in list_index > 755. paginator_class=MailmanPaginator) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in paginate > 71. objects = paginator.page(page_num) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in page > 46. number = self.validate_number(number) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in validate_number > 48. if number > self.num_pages: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in num_pages > 97. if self.count == 0 and not self.allow_empty_first_page: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in count > 56. return self.function(count=0, page=1).total_size > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in _get_list_page > 751. advertised=advertised, mail_host=mail_host, > count=count, page=page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/client.py" > in get_list_page > 181. return Page(self._connection, url, MailingList, count, page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in __init__ > 37. self._create_page() > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in _create_page > 62. response, content = self._connection.call(self._build_url()) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py" > in call > 112. error_msg, response, None) > > *During handling of the above exception (HTTP Error 404: {"title": "404 > Not Found"}), another exception occurred:* The above 404 is the underlying problem. In the traceback above we see that /opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py at line 751 calls client to get the view for lists for this host. The full code is def _get_list_page(count, page): client = get_mailman_client() advertised = not request.user.is_superuser mail_host = request.get_host().split(":")[0] if ( getattr(settings, 'FILTER_VHOST', False)) else None return client.get_list_page( advertised=advertised, mail_host=mail_host, count=count, page=page) The issue is the FILTER_VHOST = True setting is broken. This is <https://gitlab.com/mailman/postorius/-/issues/394> The broken code tries to get the lists for the domain in the requesting URL which here is the web_host but the web_host has no lists. This is a complicated issue. See the whole comment thread in the issue where I am trying to mentor someone to a fix, but he apparently has given up. The issue is we don't have a method for retrieving lists by web host. It is simple enough to get all the email hosts associated with a web host, but what do we do if that's more than one email host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

Re: Strange error in uwsgi-error.log

by brian＠emwd.com

Derek Lambert wrote: > Brian, > > When I was seeing this, new lists weren't showing in HyperKitty. > > I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from > functioning. I had to drop the constraint to get the lists in. None of them have a > description now. > > Was this working for you in the past? If so, did you do any updates recently? > > Derek Lambert Hi Derek, Actually you are right. None of my new lists are showing in http://mailmam3domain/hyperkitty/. However if you go directly to each lists' archives then you can access their archives via HK. I also recently did an update when Postorius 1.2.3 came out. I am using the Docker images for my Mailman 3 install. How do you drop the constraint? DId that fix the error message? So this seems to be a new bug that was introduced in the recent updates? It's weird because I know Hyperkitty was not touched. Brian

7 years, 9 months

Cannot setup announce-only mailing list

by Alberto Granzotto

Dear all, I don't understand how to set up an "announce only" mailing list using Postorius Version 1.2.4. What I do is the following: - Click on "Create New List" - From "List Style", select "Announce only mailing list style." - Fill all other fields in the form - Click "Create list" At this point people can subscribe to the newly created announce mailing list. If they add themselves they end up in "List Members", and if they email the announce mailing list, their email is relayed to all other members, just like a normal mailing list :/ Moreover, subscribers get this message, inviting them to post to the announce only mailing list: > Welcome to the "Test-announce" mailing list! > > To post to this list, send your email to: > > test-announce(a)lists.dist0rtion.com Of course, I want to keep this mailing list "read only" for members, and I want only selected people to post to that mailing list. Any idea on how to achieve that? Best, Alberto

6 years, 9 months

Re: How to run 'manage.py update_index_one_list' command.

by Brian Carpenter

On 2/25/20 7:09 PM, Mark Sapiro wrote: > The issue is we don't in general know exactly how Django has been > installed or what the management command is, byt hyperkitty_import > should be able to figure out how it was invoked and use that. I did their installation for them basically using your setup listed at: https://wiki.list.org/DOC/Mailman%203%20installation%20experience I used a venv and pip to install the various components: pip install mailman pip install hyperkitty pip install postorius pip install mailman-hyperkitty -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/ Mailman 2 & 3 Hosting https://www.mailmanhost.com -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 8 months

Mailman-users search results for query "Postorius"