Search results for "Postorius" - Mailman-users

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Mark Sapiro

On 12/10/2016 12:52 AM, Barry Warsaw wrote: > > Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. Done. There is one "temporary" commit in my MR to work around <https://github.com/sphinx-doc/sphinx/issues/3212> and get "docs" to pass. >> I can also work on Postorius. Also in this vein I have a question. >> Should the DMARC settings be added to the Alter Messages tab in the List >> Settings view or would it be better to have a separate DMARC Mitigations >> tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I have a WIP MR at <https://gitlab.com/mailman/postorius/merge_requests/194> that adds a tab. Maybe Florian and Terri can look at that and chime in. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 10 months

Re: Email to list owner on list creation only sent when using mailman create --notify command

by Mark Sapiro

On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/9/25 13:58, via Mailman-users wrote: > > I have updated the welcome message for a mailing list by directly updating the file at: > file:///var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au/en/list:user:notice:welcome > > I then restarted theses services: mailman3, mailman3-web and nginx. > > But when I test subsribe to the mailing list, the welcome message does not update. > > GNU Mailman 3.1.1 (Between The Wheels) > Postorius Version 1.1.2 These are extremely old - over 7 years. This may have something to do with the issue. There may be an issue in that the template table in the database is saying to look elsewhere. What do you get for a database query like ``` SELECT uri FROM template WHERE name = 'list:user:notice:welcome' AND context = '[redacted].lists.[redacted].org.au'; ``` where `[redacted].lists.[redacted].org.au` is the actual list-id. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

Re: Templates

by Barry Warsaw

On Sep 23, 2017, at 10:36, David Krantz <gazorg(a)gmail.com> wrote: > > 1. I do not know how to force a cache invalidation on a template. So > only way to change is to set a new name on the file and change the uri > there. Unpractical. No, restarts do not work. With Mark’s help you figured out how to use file templates, which is probably best for your use case. URL templates will be best when using a CMS or other system that allows you to upload templates into them. I can imagine Postorius one day supporting this feature. The way to do cache invalidation for the template you added to the database would be (let’s say for mailing list alpha(a)example.com) $ mailman shell -l alpha(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the alpha(a)example.com mailing list >>> getUtility(ITemplateManager).delete('list:member:generic:footer', m.list_id) More information is provided here: https://gitlab.com/mailman/mailman/blob/master/src/mailman/interfaces/templ… http://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html Cheers, -Barry

9 years, 1 month

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

8 months, 2 weeks

Re: Settings for https support

by Abhilash Raj

On Thu, Jan 16, 2020, at 5:15 AM, Dieter Leupold via Mailman-users wrote: > Hi, > > I configured Postorius (via Apache2) to use https, which looks fine. But > the connection to hyperkitty failed with "code 400, message Bad request > syntax". I tried serveral settings....without success. Could you give me > an example, which settings are to configure? > Thanks for your help! When you say "connection to hyperkitty failed", did you mean in the browser or when archiving the emails? If it is in browser, you can add `DEBUG=True` in your settings.py and get more details, which can be helpful to determine what is happening here. I am not completely sure why would HK have problem when P works fine, given that they are both served from the same Django server. > -- > > Dieter > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 9 months

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

2 years, 5 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, 9 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

7 years

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, 6 months

Mailman-users search results for query "Postorius"