Search results for "Postorius" - Mailman-users

Installing Mailman3 under a Python Virtual environment running on RHEL9

by Andy Macheta

Hi, So tried, without much success, to get Postorius working on my Mailman3 server and every internet trick& tip I tried did not work so decided to take a new approach as recommended at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Used this reference: https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… which I know is more for Debian/Ubuntu systems but I was hoping that 90%+ would also work with Red Hat. Fell at the first hurdle with no packages available called "python3-dev" or "python3-venv" Is there anyone that has managed to install a running version of Mailman3 that has a working GUI whether it is on bare metal or Python virtual environment and if so, could they kindly let me know how they did it?? The closest I've come is a running command line version of Mailman3 which is fine for me of course but not for anyone else as they like access via web browser. Thanks in advance, Andy Macheta

1 year, 11 months

Re: Mailman3 is wrongly display name a list member

by Allan Hansen

Thank youi, Stephen. Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. Nevertheless, the new subscriptions still show up as 'B'. Now, for the workaround: " If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists." I modified the above workflow to: Removed the address from all the lists. Set the account display name to 'A' in Django. Verify that she is not subscribed to any list at all. Deleted the email address in Django (under 'Email addresses'). Resubscribed her as 'A'. In other words, no 'B' anywhere - straight 'A's. Nevertheless, the new subscriptions still has 'B' when I list it in Postorius. Further: When I search for 'Email addresses' in Django's list of emails (by account or email), it no longer exists. When I search under 'Users' (by account or email), it exists with 'A' as the display (which she entered when she created the account). Then since the email does not exist, under 'Email addresses' in Django, I go to 'Add email address', enter her account name and address. This gives and error: 'Select a valid choice. That choice is not one of the available choices.' I get this error no matter which 'Save...' button I press. I then tried to get into REST as per your advice here: " I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) " I get this, after setting myself up as user mailman (which works when entering mailman commands): mailman@list:~/scripts$ python3 Python 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from mailman.testing.documentation import dump_json Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'mailman' Looking around, I found mailman related stuff in /opt/mailman/mm and a file called 'mailman' in opt/mailman/mm/bin but hesitated editing your command above to: /opt/mailman/mm/mailman.testing.documentation (I don't want to mess up my system). So no go... Sorry for ranting. __ Please: 1. Always use the display name and email set up in the account everywhere. 2. Allow the member to change her display name using the account UI. 3. Allow the member to change her address and apply the new address to all list subscriptions. Yours, Allan On 1/11/22, 7:20 , "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: Allan Hansen writes: > When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' > <a(a)foo.com>. If I recall correctly, this issue occurs because Subscription objects have no display name attribute, but User and Address objects do. First, the advice part: > What can I do to help this member? Unfortunately the mailman command line utility doesn't seem to allow changing the display name. The REST interface does, though. I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) should do what you want. Note the numbers "8001" (Mailman core's REST port) and "3.1" (the API version) may be different on your system, I'm assuming the default install of a recent Mailman release. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information about accessing the REST API and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for a few more details on the update process. On to the rants, if you care. > I went into Django and added the name 'B' to the subscriber's > account (the name was empty). > > I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' > <a(a)foo.com>. > > The subscription again lists as 'B' <a(a)foo.com>. Does the user need to have different display names for different addresses? (I don't think it's possible to have different display names for the same address on different lists because there's no display name at all for Subscription objects.) If the answer is "no", the correct thing to do is to set the desired display name on the user's account. If the answer is "yes", there doesn't seem to be any way to do this with current Postorius/HyperKitty. Postorius doesn't expose the display name anywhere that I can see, and HyperKitty only manages the account's "real name". > This brings up a previous discussion of display names on this list, > but I have not been able to find any solution to the need to change > Mailman3's display names for a subscriber. It is beyond weird that > unsubscribing, setting the account display name and resubscribing > the member fishes back up the old and wrong display name. Unless you explained what you did incorrectly this is not weird, it's the expected result. You set "B" in the account, that's what's going to show up as the display name. It is not obvious that a new subscription should change an existing display name for a user or an address, given that there is no way to set a list-specific display name. It could go either way, and for the user I would definitely not change it, for the address I tend to agree that a new subscription should not change the address's display name. I agree that it's weird that neither Postorius nor HyperKitty seems to expose a way to set Address display names, though. If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists.

4 years, 3 months

Re: Rendering HTML for moderation

by Mark Sapiro

On 10/28/19 1:37 AM, Gila Halpern wrote: > Hi, new member here doing some research for my boss. Does Mailman 3 allow > HTML rendering in the moderation queue, or only plain text? I'm asking > because our list mod doesn't have time to check each image in a submission > individually, so we currently don't allow images, but the boss wants to > allow them. Postorius displays only plain text of a held message with HTML and images shown as attachments, and clicking an HTML attachment link will download the HTML and what happens depends on the browser, but if there are image parts referenced in the HTML, they will be separate links to download and won't render along with the HTML. However, is the list is set to notify the moderators of held messages, the notice will imclude the entire message which should render properly in the moderator's MUA. -- 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: Filter who can send on mailman3 list?

by Stephen J. Turnbull

Marcus Granath writes: > Sorry, but actually I can not find any "Users dropdown" to select > "Non-Members" at any Postorius in my web interface. :-( > Maybe, could it be that I am actually not the admin of the mailman3 > server, I'm "just" the admin of my mailman-list - so just admin for > my mailman-list and not for the mailman server? I think if you are *moderator* you should be able to see the Subscribers list, but maybe you need to be *list owner*. You definitely do not need to be *server admin* to see the Subscribers list. I'm not sure if the *server admin* has a way to see a sitewide Users list (other than using the mailman command line tool or directly from the database). Is it possible that you have multiple logons on the server, one of which you have subscribed to lists and the other is a user with administrative privileges? I know that burns me regularly. Steve

5 years, 1 month

Re: Adding users

by horvath.arpad.szfvar＠gmail.com

In my lists there are no big changes. I just need to add one or two persons a year as choir members doesn't change too much. I try to find out the parameters of the mailmanclient.Client I guess the URL is the REST root url from the output of the `mailman info` command I tried to add the admin username and the password with which I log into the postorius page. Or the rest admin is a different one? In [2]: mmc = mailmanclient.Client( ...: "http://localhost:8001/3.1/", ...: "admin", ...: "somepassword", ...: ) In [3]: mmc.get_list('korus') But that gives me this error /usr/lib/python3/dist-packages/mailmanclient/client.py in get_list(self, fqdn_listname) 354 :rtype: :class:`MailingList` 355 """ --> 356 response, content = self._connection.call( 357 'lists/{0}'.format(fqdn_listname)) 358 return MailingList(self._connection, content['self_link'], content) /usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py in call(self, path, data, method) 125 error_msg = response.text 126 --> 127 raise HTTPError(url, response.status_code, 128 error_msg, response, None) 129 if len(response.content) == 0: HTTPError: HTTP Error 401: REST API authorization failed

3 years, 6 months

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

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

3 months

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

2 months, 2 weeks

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, 6 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, 1 month

Mailman-users search results for query "Postorius"