Search results for "Postorius" - Mailman-users

Message of the day

by Stephen J. Turnbull

Henrik Rasmussen writes: > Are there any way of displaying a "Mesage of the day" to the users > of Postorius and Hyperkitty? Not built in to those applications. However, you could easily alter a template, possibly the base template, to include a file would contain your message with appropriate formatting. Django has a conditional include feature so you wouldn't get an error and no glitch in the display if the file weren't present. Extensions to the idea would include putting the formatting in CSS (sort of pointless by itself) and adding Django code to check whether the user's previous login was before the MOTD was changed (and then the CSS could be used to hide the message in case they had logged in recently, and presumably already saw it). It wouldn't be hard to add a MOTD table to Django, and then you could display all messages more recent than previous login. I'm not interested in doing this myself but would be willing to help a volunteer write the code and get it committed (subject to Steering Committee consensus, but I don't see why not). Steve

4 years, 9 months

Integration with spamassassin?

by Stephen J. Turnbull

Peter Chubb via Mailman-users writes: > Has anyone integrated Mailman3 with Spamassassin? > > What I'd like is a way for emails that I click 'discard' on in > Postorius, to be submitted to the spamassassin Bayes classifier to > make it more likely similar ones will be rejected in future at SMTP > conversation time. I've not heard that anyone has done this. If there's a way to direct email into the classifier, then you can tell Mailman to send discarded emails to some email address, I believe. But I don't know anything about how that classifier is trained. You're likely to get better answers on Spamassassin channels. To make it one-click would require code changes in both Mailman and Postorius. Not terribly hard as such, but would require some thought as we probably wouldn't want it to be Spamassassin-specific (I think Mark uses SpamBayes on some of his lists, for example, and I suppose rspamd also knows about classifier training). Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 1 week

Re: A poll: "Delete this thread"

by Odhiambo Washington

On Fri, Jun 21, 2024 at 5:46 PM Sam Darwin via Mailman-users < mailman-users(a)mailman3.org> wrote: > Thanks for the replies. Not yet a close match to what I have installed. > Jeremy is using Dockerfiles. Marc is running mailman3-web from 4 years ago > "20200530". I may need to dig into the code and attempt to debug, line by > line. "Oh, of course, in your settings refresh_cache needs to be set to 1, > you have it set to 0", or something obscure like that. Or who knows. > I am running the latest MM3 stable code, I believe, and I can delete a thread without any problems. Running in a virtualenv. Mailman 3.3.9, Postorius Version 1.3.10, HyperKitty version 1.3.8. ``` Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 1 month

Try to Implement Template for The message sent to subscribers when a subscription confirmation is required

by msok＠lalawlibrary.org

My NGINX configure redirect for HTTP to HTTPS. For the domain below, mailman.example.com = my actual domain -NGINX config server { # EXTERNAL: Redirects all port 80 traffic to HTTPS listen 80 default_server; listen [::]:80 default_server; # server_name mailman.example.com; server_name mailman.example.com; # no issue for accessing from outside, it will redirect to https return 301 https://$host$request_uri; # Redirect http to https server_tokens off; } # INTERNAL: Listens ONLY on 127.0.0.1 to handle local HTTP requests server { listen 127.0.0.1:80; server_name localhost; location / { include uwsgi_params; uwsgi_pass unix:/run/mailman3-web/uwsgi.sock; uwsgi_param HTTP_HOST $host; } location /mailman3/static { alias /var/lib/mailman3/web/static; } location /mailman3/static/favicon.ico { alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; } -The URL syntax https://mailman.example.com/mailman3/lists/list-id/confirm/?token=$token -The error message when tried to add subscriber HTTP Error 400: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url: /postorius/api/templates/list/list-id/list:user:action:subscribe (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1029)'))) Please help! Thanks, Marin

6 months

Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: > > How to find out the versions of the each and every component > of the mailman 3 like mailman core, mailmancilent, postorius, > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, > after installation? cd to the directory in which you cloned the gitlab project for the component and do `git log` > If I am running an old mailmanclient or older version of any > other mailman component, please suggest how to upgrade either one or > multiple components based on the requirement. Is there any link that > would help me to upgrade ? > > I have used the > link https://docs.mailman3.org/en/latest/devsetup.html to install the > mailman 3 components. I expected that the procedure followed in this > link would install the latest versions of the mailman 3 components. > Please correct me if I am wrong. Is there any latest version > compatibility table ? If you installed each of mailman, mailmanclient, django-mailman3, postorius and hyperkitty according to instructions like $ cd ~/mailman $ git clone https://gitlab.com/mailman/mailmanclient.git Then set up mailmanclient: $ cd mailmanclient $ python setup.py develop $ cd .. from that document, you should have the latest version. If that is the case, `git log` in the mailmanclient directory should begin like commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, origin/master, origin/HEAD) Merge: ff39dd8 8670751 Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Thu Oct 15 01:09:32 2020 +0000 Merge branch 'fix-ci' into 'master' Use GHCR for the CI image See merge request mailman/mailmanclient!130 commit 8670751caff689733751ef323ef521c4a3fa1237 Author: Abhilash Raj <raj.abhilash1(a)gmail.com> Date: Wed Oct 14 17:36:58 2020 -0700 Use GHCR for the CI image commit ff39dd8f03a820f442f2251553c444370df3b914 Merge: 80ebed4 76d44e1 Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Fri Aug 7 19:35:05 2020 +0000 Merge branch 'invite' into 'master' Add support for inviting an email address to join a list. See merge request mailman/mailmanclient!129 or if you did this before Oct 15, maybe it starts with commit ff39dd8f03a820f442f2251553c444370df3b914 The particular commit you need for your issue is commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 Merge: c8dcb1e 28d1c3a Author: Abhilash Raj <maxking(a)asynchronous.in> Date: Sat May 16 08:02:21 2020 +0000 Merge branch 'held-count' into 'master' Add a new get_held_count() API to get a count of held messages. See merge request mailman/mailmanclient!122 Note that unless you intend to do actual development of Mailman 3, you should be following <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather than <https://docs.mailman3.org/en/latest/devsetup.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Re: urls.py location on venv install

by Torsten

Am 2026-08-10 15:13, schrieb Stephen J. Turnbull: > Torsten writes: > > > >> I have just nearly finished the migration of Mailman 3 from > > >> Debian packages to venv and mailman (master and runner) is up > > >> and running and uwsgi is also up and running. > > It looks like you are trying to use the configuration files from > Debian with minimal or no changes. > > If I were you I would > > 1. rsync -av /etc/mailman3 /tmp/ # if you don't have rsync, "cp -r" > 2. purge (not just uninstall) all the Debian mailman packages > this should delete a lot of the stuff you just copied to /tmp > 3. copy the configuration from Mailman's virtualenv install > instructions into /etc/mailman3 > 4. diff -r /etc/mailman3 /tmp/mailman3 > 5. make only essential changes you see in that diff (eg, > /opt/mailman/mm/var/web to /var/lib/mailman3/web), and see if > things work better > 6. if things still don't work, make more adjustments. > > Steve Yes, that was my intention. But now I started from scratch, following the documentation about Virtualenv installation at mailman3.org and also created the config files with the defaults shown there (with a few adjustments to match my installation). Now, I have everything running as user mailman (had user list before for mailman-core and www-data for mailman-web). And the tracebacks have changed: mailman throws this one: 2026-08-10 16:11:20 [FALCON] [ERROR] GET /3.1/lists?advertised=true&count=0&page=1 => Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.13/site-packages/falcon/app.py", line 476, in __call__ process_resource(req, resp, resource, params) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/mailman/rest/wsgiapp.py", line 65, in process_resource raise HTTPUnauthorized( ~~~~~~~~~~~~~~~~^ '401 Unauthorized', ^^^^^^^^^^^^^^^^^^^ 'REST API authorization failed', ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ challenges=[realm]) ^^^^^^^^^^^^^^^^^^^ TypeError: HTTPUnauthorized.__init__() takes 1 positional argument but 3 positional arguments (and 1 keyword-only argument) were given [10/Aug/2026:16:11:20 +0200] "GET /3.1/lists?advertised=true&count=0&page=1 HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.5" and mailman-web this one: ERROR 2026-08-10 14:11:20,011 1557501 postorius Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.13/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.13/site-packages/postorius/views/list.py", line 1141, in list_index lists = paginate( _get_list_page, ...<2 lines>... paginator_class=MailmanPaginator, ) File "/opt/mailman/venv/lib/python3.13/site-packages/django_mailman3/lib/paginator.py", line 71, in paginate objects = paginator.page(page_num) File "/opt/mailman/venv/lib/python3.13/site-packages/django_mailman3/lib/paginator.py", line 46, in page number = self.validate_number(number) File "/opt/mailman/venv/lib/python3.13/site-packages/django/core/paginator.py", line 53, in validate_number if number > self.num_pages: ^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/django/utils/functional.py", line 57, in __get__ res = instance.__dict__[self.name] = self.func(instance) ~~~~~~~~~^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/django/core/paginator.py", line 99, in num_pages if self.count == 0 and not self.allow_empty_first_page: ^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/django/utils/functional.py", line 57, in __get__ res = instance.__dict__[self.name] = self.func(instance) ~~~~~~~~~^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/django_mailman3/lib/paginator.py", line 56, in count return self.function(count=0, page=1).total_size ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/postorius/views/list.py", line 1137, in _get_list_page return client.get_list_page( ~~~~~~~~~~~~~~~~~~~~^ advertised=advertised, mail_host=mail_host, count=count, page=page ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/opt/mailman/venv/lib/python3.13/site-packages/mailmanclient/client.py", line 211, in get_list_page return Page(self._connection, url, MailingList, count, page) File "/opt/mailman/venv/lib/python3.13/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() ~~~~~~~~~~~~~~~~~^^ File "/opt/mailman/venv/lib/python3.13/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, error_msg, response, None) urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2026-08-10 14:11:20,041 1557501 django.request Internal Server Error: /mailman3/lists/ ERROR 2026-08-10 14:11:20,041 1557501 django.request Internal Server Error: /mailman3/lists/ I have taken the old database from the Debian configuration and moved it to /opt/mailman... where it should belong (I hope).

1 week

Re: Change Member's Address

by Mark Sapiro

On 1/13/26 11:30 AM, alain williams wrote: > > Like it or not it is sometimes easier for me to do that sort of thing than try > to explain it to them. I understand. > So: it would be really useful if the list manager were able to do this via the > web interface. As you indicate, a list admin can use the mass subscribe/removal UI to remove the old address subscription and add a new address subscription, but as you probably know, this doesn't preserve the user's other settings, and for a user with multiple subscriptions, it needs to be done list by list, so this really isn't a satisfactory way for an admin to change a user's address. There is a current issue at https://gitlab.com/mailman/postorius/-/issues/399 to simplify the process for a user to change their address and one at https://gitlab.com/mailman/postorius/-/issues/194 to allow an admin to change a user's address. Merge requests are welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months

Re: My list has been switched from public to private archives, but they are still visible

by Abhilash Raj

On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: > I am having a very similar issue. Here is what I have found: > > There are basically three archive settings we can select via the > postorious web front end for archives. These can be found in: Settings > > Archiving and they are: > Public archives > Private archives > Do not archive this list This is interface of Mailman to set the archives. > > In the Django administrative interface we can find those > same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists > > Mailing List object(x) > Archive policy: > never > private > public This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run. I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :) > > I’m not sure which of the two takes precedence. My guess is postorius > since that is a list owner accessible setting and the Django > administrative interface would typically not be accessible to list > owners. We have noticed the following odd behavior, not sure if it is a > bug. For existing lists with private archives, when switching to “Do > not archive this list” in postorious, the desired effect of no longer > archiving the list is instantaneous. However, after the daily cron job > that syncs with Mailman Core happens, the existing archives now become > publicly accessible. Is this behavior based on the assumption that the > list will no longer be archived and will therefore be purged? Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that. Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty. For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible. > Enrique > > > On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: > >> Can anyone help with this? > >> > >> I set my list to private archives today. Up until then, it was pubic. > >> And yet, if you go to the list page, you will see that if you click > >> archives (top left), you can see them. (Filled with a bunch of tests > >> posts for now) > > > > This change takes a bit of time to sync up Hyperkitty. THere is a daily > > cron job which syncs this information from Mailman Core. > > > > I have made a change which should fix this problem and the process would > > become synchronous. > > > > You can run `python manage.py runjobs --daily` command to force sync > > that information. > > > >> > >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… > >> > >> Am I misunderstanding what a private archive is? > > > > Not really, your expectation is right. > > > >> > >> Is something wrong with my setup (which is hosted)? > >> > >> Thank you. > >> _______________________________________________ > >> Mailman-users mailing list -- mailman-users(a)mailman3.org > >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org > >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… > >> > > > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… > > -- thanks, Abhilash Raj (maxking)

6 years, 10 months

Re: Issue with Held Messages

by Mark Sapiro

On 08/20/2016 07:15 AM, Jean-Luc Wasmer wrote: > On 2016-08-20 02:08, Mark Sapiro wrote: >> >> If you look at the user's options when logged in as a list owner, you >> should see an additional "Administration options" section below those >> with a "Moderation" setting. What is that set to? > > I log in as the admin user created with "mailman-web-django-admin > createsuperuser", I created the list logged in as this admin user and > its email address is displayed in the "Owners" sections of the "Members" > tab. > I only have that 1 other member and when I check it settings, the last > section is "Avoid duplicate copies of messages?" and then there's the > "Save" button. You probably have an older version of Postorius than I have. I am a few weeks behind at the moment, but I basically am running the heads of the master branches as described at <https://wiki.list.org/x/17891998>, so I am unable to see what you see. Here's an example mailman shell session to see what various member moderation actions are. > mailman@mail:/opt/mailman/mailman-bundler$ bin/mailman shell mm3_test(a)python.org > Welcome to the GNU Mailman shell > The variable 'm' is the mm3_test(a)python.org mailing list > >>> list(m.members.members) > [<Member: None <barry(a)python.org> on mm3_test(a)python.org as MemberRole.member>, <Member: Mark Sapiro <mark(a)python.org> on mm3_test(a)python.org as MemberRole.member>, <Member: mark(a)msapiro.net on mm3_test(a)python.org as MemberRole.member>, <Member: gvanrossum(a)gmail.com on mm3_test(a)python.org as MemberRole.member>] > >>> m1 = list(m.members.members)[1] > >>> m2 = list(m.members.members)[2] > >>> m1.moderation_action > <Action.defer: 4> > >>> m2.moderation_action > <Action.accept: 3> >>> By the way, I didn't mention before but in Settings | Message >>> Acceptance, the "Acceptable aliases:" box contains "[]". When I try to >>> Save changes after modifying something, I gut "An error occured: []" in >>> the yellow banner (instead of "The settings have been updated."). >> >> >> What happens if you clear the Acceptable aliases box before saving? > > Then I get "The settings have been updated." after pressing "Save changes". > But if I navigate elsewhere and come back, the brackets are back in the form. This is <https://gitlab.com/mailman/postorius/issues/51>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 11 months

Re: Disable archives per list

by Bernd Wurst

Hello. Thank you for your answers. Am 25.02.21 um 22:01 schrieb Mark Sapiro: > Normally a list admin can select which of the enabled archivers is > active for that list via Postorius. To prevent this, you would have to > modify Postorius. It would be easy enough to just remove settings from > the relevant templates. This will take effect for all lists at once, I suppose. :( > I'm not sure what you mean by "custom archiver settings", but other than > enable/disable and public/private, probably not. Hyperkitty has a rather cool frontend but stores all messages from all lists together in one database table. Additionally, neither Mailman nor Hyperkitty seems to know or tell anything about archive sizes of a list. This is horribly for accounting. So I thought if I can have a separate hyperkitty installation per user without having to duplicate the whole mailman. Alternatively, I'd like to enable archiving only for some customers that buy a suitable plan. I did not really get into mailman plugins. Is is possible for plugins to hook into such settings? I could not really find examples for plugins. regards, Bernd

5 years, 5 months

Mailman-users search results for query "Postorius"