Search results for "Postorius" - Mailman-users

Re: Hiding an ML from a site

by Odhiambo Washington

On Thu, Feb 8, 2024 at 1:21 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On February 7, 2024 1:34:32 PM PST, Odhiambo Washington < > odhiambo(a)gmail.com> wrote: > > >What should I do then? Edit some file? Apply some patch? > >It's pretty easy for me to create a DNS record for the same server (IP) > for > >use with the web host that I'd like to hide. > > > In the Domains view in postorius, you need separate mail hosts. Then you > need to change the domain of one of the lists to the 'new' mail host. This > implies changing its address which may not be acceptable. > Looking at Postorius, they do have different mail hosts. See the screenshot at: https://imgur.com/a/GsiiEjP Or, you can just live with it as is. > The problem with this is that those who go to the site have been trying to subscribe to the other ML. Note, I have been without power at my house for almost 3 days now, so I > don't have access to all my usual resources. > In Kenya, the blackouts can last equally long at times - and there is nothing we can do about it because the power distributor is a monopoly. Sorry for all the loss you've incurred from the foods getting spoilt in the fridge :-( -- 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]

1 year, 7 months

Re: Urgent help needed...

by Simon Hanna

On 05/24/2018 06:21 PM, Darren Smith wrote: > Hello, > > This morning our Mailman 3/Hyperkitty/Postorius installation has become > unresponsive. When looking at the machine, postgres is pegging all 4 CPUs > on the machine. > > We did some digging in postgres, and here is the query that is causing > problems: > > "SELECT hyperkitty_email.date FROM hyperkitty_email WHERE > hyperkitty_email.mailinglist_id = 'fooey(a)rootsweb.com' ORDER BY > hyperkitty_email.date ASC LIMIT 1;" > > We have found that it doesn't matter what mailinglist_id is being used. > > We have also found that this might be an issue with the LIMIT 1 - our > investigation is showing that using LIMIT 1 in postgres makes things > execute very differently than if you use a limit 2 or more, and that this > is probably what is going on. > > Basically, every time this gets called, it pegs an entire CPU for 20-30 > seconds. It appears to be called a LOT. > > So our users are getting 504 gateway timeouts right now. > > What has changed: > > We have been in the process of importing our 40 million archived emails > from our old mailman 2 archives. > > Questions: > > 1) We have tried doing a grep in the codebase - mailman3, hyperkitty, > postorius, django - basically anything that might be calling this code, but > we can't find it. Does anyone know what generates this query? It looks like the query is to get the date from the last email for a mailinglist. AFAIK Hyperkitty checks this when new emails get it (maybe even during import) It could also relate to the "active" state of mailinglists...

7 years, 3 months

Re: Disabling "delete account" option

by Jered Floyd

Hi Hitachi, There was a recent list message on the ways you can modify Mailman to hide or disable account deletion, escalating from "hide it with CSS" to disabling the REST endpoint -- I will forward it to you direct if I can quickly find it. I would suggest, however, that preventing a user from deleting their own account is generally undesirable, and may be restricted by local regulation. I believe there is an "are you sure" confirmation step, so I struggle to imagine a case where this was done accidentally.... Regards, --Jered ----- On Apr 19, 2025, at 7:03 AM, Hitashi mancho via Mailman-users mailman-users(a)mailman3.org wrote: > Dear all, > > Recently, I have migrated from Mailman2 to Mailman3 > > GNU Mailman 3.3.10 (Tom Sawyer) > Python 3.11.9 > > Some of the list users logged into Postorius and went to profile settings. > Over there, they found an option "Delete Account". Without any discussion, > they deleted their account and all their list membership. > > How can we prevent this from happening? Is it possible to disable this > "Delete Account" option, or can we add some admin approval? > > Regards, > Hitachi. > > ___________________________________________ > Mailman's content filtering has removed the > following MIME parts from this message. > > Content-Type: image/png > Name: firefox_lMnN5UcNTB.png > > Replaced multipart/alternative part with first alternative. > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

4 months, 3 weeks

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

by Andreas Barth

* Lars Schimmer (l.schimmer(a)cgv.tugraz.at) [210226 10:15]: > On 26/02/2021 00:55, Brian Carpenter wrote: > > 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. > > > > Hm, it completely ignores the standard way for Debian: > apt-get install mailman3-full > also exim4 as standard mailer. > And apache2. That's how I did it (for my first installation), and it worked out of the box. However I would recommend to directly use a real database (e.g. postgresql). Andi

4 years, 6 months

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 4:54 PM, Mark Sapiro wrote: > On 1/14/22 11:56 AM, David Newman wrote: >> >> I created a pending subscription request on a test list. Here is the >> text I'm using in a file called 'list:admin:action:subscribe.txt' >> (minus the rows of hypens): >> >> ---------- >> >> >> As list administrator, your authorization is required for a mailing >> list subscription request approval: >> >> For: $member >> List: $listname >> >> At your convenience, visit: >> >> https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ > > This looks like a Mailman 2.1 URL. Are you sure you don't want something > like > > https://${domain}/mailman3/lists/${short_listname}.${domain}/ Yes. The server redirects MM3-style requests to MM2.1 URLs. I need to determine why, but that may be a different issue than the templates one. There's nothing obvious in this vhost's nginx config that would generate the redirect. Will check, if I can't resolve this I'll open a different thread. > >> >> to approve or deny the request. >> >> ---------- >> >> Instead the message that goes out at midnight daily reads like this: > > > That's a different message. It is sent from the `mailman notify` command > run by cron. It's built from the list:admin:notice:pending template. OK, wrong template then. > >> >> On successive nights I have placed copies of the >> 'list:admin:action:subscribe.txt' file above in these locations: >> >> mm/var/templates/lists/test.lists.domain.tld/en > > I hope you mean > > /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en Yes > >> /opt/mailman/mm/var/templates/site/en > > > Either of those should work. The lists one will take priority over the > site one for that list. > > >> and then in Postorius, with the same contents as above. > > If you set a template in Postorius, it takes priority. If you later > decide you want to use one in /opt/mailman/mm/var/templates/ you have to > delete the postorius one. > > >> The file versions are owned by the mailman user, and have 0644 >> permissions. Not sure this is necessary but I've restarted the >> mailman3 and mailmanweb services each time after a change. >> >> There is no sign of trouble in the MM3 or web logs. The only thing I >> see is in the Postfix log, where the shorter and less helpful message >> goes out each night. I don't see anything in the template docs about >> this. >> >> Questions: >> >> 1. What to do to get the custom message working? > > > It should work. I suspect you need to go to the list's Settings -> > Automatic Responses and set `Admin immed notify` to Yes. It's enabled. I think this triggers notifications only for new subscription requests, not pending ones. > > >> 2. Is there a way to trigger a subscribe reminder for one list only? > > > If by subscribe reminder you mean the `list:admin:action:subscribe.txt` > message, yes that's the above list setting. If you mean the one sent > from the `mailman notify` command, see `mailman notify --help` for the > options. You can specify one or more lists (default is all lists) via > options and put them in your cron. > > >> Asking because there are other lists on this server with other >> requests pending, and I don't want to bother other moderators with >> multiple reminders per day. Not a big deal, but it would be nice to >> test this with one list rather than waiting up to 24 hours after each >> change. > > > You can test `mailman notify` at any time by running it by hand. Thanks. This still isn't working as intended. I took these steps: 1. Created the file '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' with these contents (minus the hyphens top and bottom): ---------- The $listname list has $count moderation requests waiting. $data At your convenience, visit: https://${domain}/mailman3/lists/${short_listname}.${domain}/ to approve or deny the request. ---------- 2. Restarted the mailman3 and mailmanweb services 3. As the mailman user, ran the command 'mailman notify -l test.lists.domain.tld -v' This generated an email message but its contents were the same as in my previous post: ---------- The test(a)lists.domain.tld list has 1 moderation requests waiting. Held Subscriptions: User: letmein(a)domain.tld Please attend to this at your earliest convenience. ---------- What I'm trying to do here is replicate a feature from MM2.1, where pending notifications had URLs embedded in the message. That's not available out of the box in MM3, and if there's a place for feature requests I'd be glad to ask that this be made the default. For now, though, I'm looking to get this customization working. Thanks. dn

3 years, 7 months

Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/10/21 10:22 AM, David Newman wrote: > > 1. At least on my system, the proxy_pass statement will only run without > errors if I change this to a fully formed URL, e.g., 'proxy_pass > http://127.0.0.1:8000'. Is this a typo in the docs? I changed it at https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… but I wonder if we shouldn't be using `uwsgi_pass` instead of proxy_pass. See https://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass Are you using uwsgi or some other wsgi server. > 2. What document root(s) and alias(es) to use for Postorius and > Hyperkitty and the Django admin on a server that also runs other > services (e.g., Postfix for non-list mail and Roundcubemail)? If you can separate Mailman from other services by subdomain, you can configure them separately and for Mailman, root is irrelevant as everything is proxied or aliased in a location directive. For example, Mailman on the server that supports this list uses the lists.mailman3.org domain and we have (excerpted) ``` server { listen 443 default_server; root /usr/share/nginx/html; index index.html index.htm; # root and index are probably irrelevant as we never go there server_name lists.mailman3.org; ssl on; #ssl stuff location / { proxy_pass http://127.0.0.1:8000/; # other proxy stuff } location /static/ { alias /var/spool/mailman-web/static/; } location /robots.txt { alias /usr/share/nginx/html/robots.txt; } location /favicon.ico { alias /var/www/listorg/images/favicon.ico; } } ``` And for the other stuff we have ``` server { listen 443; server_name .list.org mirror.list.org mirror.mailman3.org; root /var/www/listorg; ssl on; # ssl stuff } -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Re: Mailman 3 localization

by Simon Hanna

> We would like to contribute further german translations, since there > are still some parts missing, e.g. in the postorious interface. Would > https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate > be the right place to do so, so that everybody could use our > translations? > > If there are other areas in which you could use our help, please let > us know. > > Regards, > Alex I wanted to set it up, but the requirement is to use a free hosted solution. (So transifex and crowdin are a no-go, they would be great to get translations, especially crowdin looks very active in that regard) I tried out zanata.org but it's extremely slow... The other option at the time was pootle (http://pootle.translatehouse.org) which doesn't offer hosting but some folks at gnu had a customized instance set up, but they discontinued the service. I searched for a translation service for a private project and found weblate.org . They offer hosting (hosted.weblate.org) for open source projects and it looks like a couple of people are using it. You need to contact them if you want to set it up for an open-source project though and I didn't want to invest in it without knowing what the end-result would be... Since I'm also mainly interested in German translations for my own installation, I opted to just use plain .po files and filed merge requests against the repositories. Postorius has translations (not perfect, but a start for the moderators that use my instance) included by now but my merge request for core is still outstanding https://gitlab.com/mailman/mailman/merge_requests/400/ Since I don't use Hyperkitty, I didn't translate that. cheers, Simon

7 years, 2 months

Correct way to filter auto-replies to list?

by Stephen J. Turnbull

Gary Holman writes: > I have seen a few messages on this list regarding handling 'out of > office' auto-replies. However I do not see a final resolution. This problem is as hard as spam. There won't be a final resolution as long as people use out-of-office auto-replies. They're all different. If you are using a spam filter, I would suggest adding the offender's out of office message (or at least the spike protein :-) to your filter's body text blacklist. > What is the best practice to filter auto-replies to list: header > filter or postfix milter-reject or something else? You write "auto-replies" below. Set the subscriber to no-mail, or unsubscribe them for a second offense. Remind them that we put a huge amount of effort into creating and maintaining Postorius to make that as convenient as possible, and we at Mailman are "shock, SHOCKED, I tell you" that this courtesy was neglected. :-) > We are running dockerized Mailman 3 version 1.3.4. A list user > auto-replied their vacation message to list and then the listserv "listserv" is a trademark. Please don't use it to refer to Mailman. > created a chain-reaction of continuously replying to auto-replies > by that user. What do you mean by "chain reaction"? Other subscribers replying to the "out of office" message, or an auto-reply from the Mailman server? > There isn't really a good header option to filter > from, as the subject seems to be randomized. Vacation programs conforming to https://tools.ietf.org/html/rfc3834 https://tools.ietf.org/html/rfc5230 should provide some header fields to filter on. HTH, Steve

4 years, 4 months

Mailman issues after re-boot

by Paul Rubin

*<< I sent this to the mailman3 issues on gitlab and Mark replied but asked me to move to this list, so I copied everything and inserted responses. I hope this makes sense and someone can help me.>>* After a lengthy power failure I had to reboot a machine that has been running for several years. the WEB-UI does not seem to be able to see mailman-core. I have looked for log entries that might explain what the issue is and I am stumped to even find logs that will update when I get an error on the browser. Mailman is definitely running, postgres is running and mailman web is running. if I go to the lists page I see lists, if I try to access a specific list I get Server error: An error occurred while processing your request. I looked in /var/logs/mailman /opt/mailman/web/mailmanweb All I can find is: django.urls.exceptions.NoReverseMatch: Reverse for 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is not a valid view function or pattern name.16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/goodstein.goodstein.org/ File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", line 8, in <module> from django.utils.translation import ungettextImportError: cannot import name 'ungettext' from 'django.utils.translation' (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/__init__.py) Also I have to run mailman from "mailman start" because the systemctl returns this: ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2023-09-12 10:06:31 EDT; 13s ago Process: 31159 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 806msSep 12 10:06:31 mail mailman[31159]: Error in atexit._run_exitfuncs:Sep 12 10:06:31 mail mailman[31159]: Traceback (most recent call last):Sep 12 10:06:31 mail mailman[31159]: File "/usr/lib64/python3.8/logging/__init__.py", line 2126, in shutdownSep 12 10:06:31 mail mailman[31159]: h.flush()Sep 12 10:06:31 mail mailman[31159]: File "/opt/mailman/venv/lib64/python3.8/site-packages/mailman/core/logging.py", line 67, in flushSep 12 10:06:31 mail mailman[31159]: if self._stream:Sep 12 10:06:31 mail mailman[31159]: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream'Sep 12 10:06:31 mail systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURESep 12 10:06:31 mail systemd[1]: mailman3.service: Failed with result 'exit-code'.Sep 12 10:06:31 mail systemd[1]: Failed to start GNU Mailing List Manager. Please tell me where to start looking or adjusting. Reply from Mark Sapiro,* Edited to include responses:* Mark Sapiro <https://gitlab.com/msapiro>@msapiro <https://gitlab.com/msapiro>· 1 day ago <https://gitlab.com/mailman/mailman-web/-/issues/23#note_1557601916> Owner Add reaction More actions The mailman-users(a)mailman3.org list is probably a more appropriate place for issues like this. django.urls.exceptions.NoReverseMatch: Reverse for 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is not a valid view function or pattern name. 16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/ goodstein.goodstein.org/ /opt/mailman/venv/lib64/python3.8/site-packages/postorius/urls.py should contain re_path( r'^unsubscription_requests$', list_views.list_unsubscription_requests, name='list_unsubscription_requests', ), Y *Yes this exists* and /opt/mailman/venv/lib64/python3.8/site-packages/postorius/views/list.py should define list_unsubscription_requests. *Yes there is a method by this name defined* File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", line 8, in from django.utils.translation import ungettext ImportError: cannot import name 'ungettext' from 'django.utils.translation' (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/ *init*.py) See https://docs.djangoproject.com/en/4.2/internals/deprecation/#deprecation-re… - ungettext() is removed from django>=4.0 Sep 12 10:06:31 mail mailman[31159]: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' I don't understand this one offhand, but what is the content of /etc/systemd/system/mailman3.service, in particular the settings for User, Group and ExecStart? *The service looks right:* 1 [Unit] 2 Description=GNU Mailing List Manager 3 After=syslog.target network.target postgresql.service 4 5 [Service] 6 Type=forking 7 PIDFile=/opt/mailman/mm/var/master.pid 8 User=mailman 9 Group=mailman 10 ExecStart=/opt/mailman/venv/bin/mailman start 11 ExecReload=/opt/mailman/venv/bin/mailman restart 12 ExecStop=/opt/mailman/venv/bin/mailman stop 13 14 [Install] 15 WantedBy=multi-user.target *It seems I may have two versions of the mailman script:* mail:/opt/mailman # which mailman /usr/bin/mailman mail:/opt/mailman # ls -al /usr/bin/mailman -rwxr-xr-x 1 root root 382 May 10 2021 /usr/bin/mailman mail:/opt/mailman # ls -al /opt/mailman/venv/bin/mailman -rwxr-xr-x 1 mailman mailman 231 Sep 12 10:02 /opt/mailman/venv/bin/mailman Somehow, your installation is corrupted. I don't know how *I need to know what to remove, how to correctly update, etc., That said the two scripts appear to be very similar:* mail:/opt/mailman # head /usr/bin/mailman #!/usr/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' __requires__ = 'mailman==3.3.4' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( mail:/opt/mailman # head /opt/mailman/venv/bin/mailman #!/opt/mailman/venv/bin/python3 # -*- coding: utf-8 -*- import re import sys from mailman.bin.mailman import main if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) sys.exit(main()) mail:/opt/mailman # *Given the two years since the last reboot I also tried following * https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was running the latest* pip install -U mailman postorius django-mailman3 hyperkitty mailman-web

1 year, 11 months

Re: Place holders

by Mark Sapiro

On 5/27/25 23:23, Mark wrote: > Hi, > > The place holders listed as available on the "Add new template" page are: > > $hyperkitty_url > $listname > $list_id: > $display_name > $short_listname: > $domain > $info > $request_email > $owner_email > $site_email > $language What Postorius version is this? You may be missing some things added in 1.3.11. A more complete list including the ones that only work in certain contexts is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… a pointer to which was added in 1.3.11. > The only one that seems to sort of work on my template is $list_id - > which displays as "testlist". (I was expecting to see > "testlist(a)example.com"). $listname should be replaced with the fqdn list name like "testlist(a)example.com" and $short_listname should be replaced with the list name without the @domain as in "testlist". The others should all work as documented. I don't know why they wouldn't. Can you give an example of a template that doesn't get these substituted. > The others just get displayed as a variable. Eg. $owner_email > > Have I missed a setting somewhere? The actual substitution is done by the Python `string` library module Template class, safe_substitute method. See the doc at https://docs.python.org/3/library/string.html#template-strings Note that because we use the safe_substitute method, invalid substitutions don't produce errors, they just aren't substituted. In particular if `$identifier` is followed immediately by a letter, digit or underscore, `identifier` must be wrapped in `{}` to separate it from the following characters, e.g., `${identifier}x`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

Mailman-users search results for query "Postorius"