Search results for "Postorius" - Mailman-users

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, 2 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

4 months, 2 weeks

Re: Customizing Postorios web templates

by Stefan Bethke

On 22. Feb 2026, at 17:33, Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > > Stefan Bethke writes: > >> I have two list servers that I would like customize the web pages >> for, specifically I need to add some legal information to the >> footer, and I might want to apply some light branding to the >> site. I can't find any hints on how to do that, maybe I'm looking >> in the wrong place? > > Postorius is a Django application. There are copious docs on > djangoproject.com. We really don't want to duplicate the upstream > project's documentation, especially since our downstream (ie, OS > distros) are likely to have various different versions of Django > installed in their packages. > > The basic procedure is to add a local template path (I use > /etc/mailman3/templates) early in Django's template path in > /etc/mailman3/settings.py. Then copy any templates you want to modify > to the right place in that local template hierarchy and modify them > there. Thank you, after a little bit more research, I did find the necessary information and managed to configure https://github.com/maxking/docker-mailman to pick up my template overrides. > If so, would there be interest in adding a feature to define some >> blocks that can be overridden more easily, > > Don't think this approach is better than overriding base.html if you > want sitewide legal and branding. It would be more appealing if it > were list-specific. It might be slightly more convenient, but you > still need to create the local template hierarchy. On the other hand, > it would increase the documentation burden. And for obvious reasons > we don't want to make it too easy to replace our own branding. I understand. Would you be open to some documentation about the general approach and a few pointers in the right direction? For people who are not familiar with Django this is not very obvious. And also, would you accept a change that enables replacing the icon in the nav bar and (extending/replacing) the footer, by defining a block each for these places with the current content as the default? My rationale is that I do not want to track changes to postorius/base.html manually, and this would allow me to override just those two blocks. Regards, Stefan -- Stefan Bethke <stb(a)lassitu.de> Fon +49 175 3288861

4 months

Re: Converting discussion list to read-only list (settings)

by Paul Arenson

Thanks again Mark. The final result is to keep my list a discussion one (of a sort). I have set it to moderate both members and non members. If someone posts to a non existent topic, I will simply post it to the correct topic or create one on their behalf assuming it is a valid message. Settings: Default action to take when a non-member posts to the list AND Default action to take when a member posts to the list is MODERATE. Anonymous--> NO >Announce only style the list attribute allow_list_posts is False and for the Discussion style, it's True. I guess I should leave it as TRUE if I am keeping as discussion list, but since I am moderating all comments, I am guessing it doesn't matter. Am I right? This is the setting in Postorius -> Settings -> Alter Messages -> Include the list post header an all it does is include or not include the List-Post: header in mail from the list.

6 years, 8 months

Re: Question about whitlisting a domain for specific mailing list

by Mark Sapiro

On 3/30/23 08:55, Zaheer Abbas wrote: > Hi All, > > I need to whitelist a domain for a specific mailing list on your platform. > Only *(a)example.com email addresses should be allowed to post messages to > this list. > > Could you please provide me with documentation or instructions on how to > achieve this? I have already searched the knowledge base and user manuals > without success. In Postorius Header filters add a filter with Header = from, pattern = ^.*(a)(?!example\.com(\W|$)) and Action as desired. That pattern will match anything in a From: header which contains an @ followed by anything other than example.com and a non-alphanumeric or the end of string. I.e., things that won't match are for example xxx(a)example.com xxx(a)example.com> xxx(a)example.com yyy Things that will match are for example xxx(a)other.domain xxx(a)example.comp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Re: urllib.error --was: Re: No module named 'mailman3hyperkitty'

by Mark Sapiro

On 1/18/22 4:20 AM, Axel Rau wrote: > > While selecting a list in the browser, I’m getting: > - - - > Traceback (most recent call last): > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch > return handler(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get > 'hyperkitty' in archivers and # noqa: W504 > File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ > self[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ > return self._get(key) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get > return self.rest_data[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} > ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} The above seems to be from Django's log. What's in Mailman core's mailman.log? > Question: Am I missing aliases in my nginx.conf? > I just have: > - - - > location / { > uwsgi_pass unix:///tmp/uwsgi.sock; > include /usr/local/etc/nginx/uwsgi_params; > } > > location /static { > alias /usr/local/mailman3/static; > } > > location /static/favicon.ico { > alias /usr/local/mailman3/static/postorius/img/favicon.ico; > } > - - - I don't use uwsgi so I'm not sure, but I think the above is OK. This list's host uses gunicorn and has location / { proxy_pass http://127.0.0.1:8000/; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } The only locations beyond what you have above are for /robots.txt and /favicon.ico -- 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

Re: List Migration from MM2.1 -> MM3

by Mark Sapiro

On 8/14/22 11:04, Odhiambo Washington wrote: > So I thought I have everything running. Fresh install of MM3 on > Ubuntu-22.04. > > I have created a list in postorius - it has the same name as my old list in > MM2. > > [image: MM3.png] Your image didn't make it through content filtering. What is the fully qualified name of the list > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman import21 skunkworks(a)lists.my.co.ke /var/list/lists/skunkworks/config.pck > Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE > Try 'mailman import21 -h' for help. > > Error: No such list: skunkworks(a)lists.my.co.ke Apparently the list you created is not named skunkworks(a)lists.my.co.ke > What am I missing? The Mailman 3 list skunkworks(a)lists.my.co.ke including that exact domain must exist in order to import to it. Try /opt/mailman/mm/venv/bin/mailman create skunkworks(a)lists.my.co.ke -- 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

How To Install Mailman 3 on Debian 10 (Complete Guide)

by Brian Carpenter

I have finished my how-to install Mailman 3 on Debian 10 completed to the point where you can use it to get a fully functional Mailman 3 environment up and running. This is a comprehensive guide that walks you through installing EVERYTHING (currently!) that Mailman 3 needs to run. It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have not added the update directions yet but will very soon. I also plan on adding a section on setting up DKIM and Xapian with Mailman 3. I hope this helps those who wish to get a Mailman 3 server up and running quickly and brings a sense of sanity to the confusion regarding the various documentation out there concerning the installation of Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20 at some point. Without further ado: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 I am sure the above guide can use improvements. Feel free to contact me off-list to point out mistakes/improvements, etc. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

Re: Remove PDF attachents

by Mark Sapiro

On 3/4/20 7:42 AM, Eduardo Costa via Mailman-users wrote: > Hello, > > How do I configure the list to remove attachments of type pdf and others. You need to set the list's filter_types and or pass_types. For example, to filter out everything except HTML and plain text, collapse alternative parts and convert remaining HTML to plain text, you would set filter_content = True collapse_alternatives = True convert_html_to_plaintext = True pass_types = ['multipart', 'text/plain', 'text/html'] The first 3 of these can be set in Postorius -> Settings -> Alter Messages, but the last has to be set in mailman shell as in $ /opt/mailman/mm/bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell m. The variable 'm' is the list(a)example.com mailing list >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> commit() -- 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

Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark London

Andrew - The script had: DELETE_MAILMAN_USER = False When I set it to True, it got rid of the orphaned email addresses. Thanks! - Mark On 4/25/2023 6:02 AM, Andrew Hodgson wrote: > Mark London wrote: > >> I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. > You may find this script useful: > https://www.msapiro.net/scripts/clean_users.py > > I have it running in a cronjob. Thread discussing the script can be found here: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > TLDR you end up with orphaned Django users both from when users subscribe/unsubscribe and due to spam signups using the Postorius form which never get confirmed. > > Thanks. > Andrew.

3 years, 1 month

Mailman-users search results for query "Postorius"