Search results for "Postorius" - Mailman-users

Problems configuring hyperkitty

by Alain D D Williams

I am having another go at installing mailman3 - I seem to have mailman3 & postorius working - although basic testing, much more needed to confirm that I understand it. I want to get hyperkitty working before I start full testing. I am running Debian 12 - Bookworm and have installed the Debian packages. The database is Mysql. This is not a virtualenv setup. There is no documentation in the hyperkitty package so I am following: https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html I read the following: "The database can be created with the following command: django-admin migrate --pythonpath example_project --settings settings " I assume that that will create some database tables. Hopefully this will have been done by installing package python3-mailman-hyperkitty. • What database & tables will that be ? It would be really useful to be told so that I can check. • The config file is: /etc/mailman3/mailman-hyperkitty.cfg This does not contain any comment about databases. Where does hyperkitty get its database parameters from ? • I have several different maildomains each with several lists. Some lists in different domains have the same name. Do I need a different example_project/settings.py for each domain, if so what changes ? One of the next things that I will need to do is to import archives from mailman2. How does the command below change for the different domains ? django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] Is there some better documentation that I have failed to find ? Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

11 months, 1 week

Re: Mailman 3 localization

by Alexander Klotz

> 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. > Thanks for the reply, Simon! We were thinking of using plain .po-files too, however, we couldn't find the matching "src" folder in our installation, do you have any more details where it or the .po-files may also be located? Regards, Alex

7 years, 3 months

Proper permissions for mailman installation under home directory, with layout: local

by Eric Abrahamsen

I recently upgraded my server from Ubuntu 16.04 to 18.04, and have hit some snags in the process. I've had my mailman3 installation under my home directory, running as my own user, without too many problems. var_dir was set to something in my home directory. Recently, while tracking down some weird behavior, I realized that with this sort of setup I'm supposed to use "layout: local", and that previously I'd had a sort of weird half-way installation where some things were kept in my /home/<me>/sites/mailman directory, and other bits (pids and whatnot) were scattered around the filesystem. Now that I'm using "layout: local", mailman really is trying to keep everything under that main directory, and now everything's breaking. The hyperkitty search indexer is saying it has no permissions to write into that directory, postfix won't deliver mail, saying the mailbox is unavailable, and in the web UI postorius shows no configured list domains (though hyperkitty still displays the archives correctly). So obviously I've got quite a big problem with permissions, but I don't know how to resolve it. My webserver is nginx, running as www-data. I'm starting mailman in a systemd script, with User and Group set to my user -- though maybe that should be set to root? I guess postfix runs as root, I'm not sure, but obviously it's not able to read the files in var/data/*, which appear all correct to me. What's the recommended solution here? I'd still like to keep this whole directory under my home directory, if possible... Thanks, Eric

7 years

Re: Question about whitlisting a domain for specific mailing list

by Odhiambo Washington

So the MTA option that doesn't involve any regex is better than no? On Thu, Mar 30, 2023, 20:17 Mark Sapiro <mark(a)msapiro.net> wrote: > 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 > > _______________________________________________ > 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 odhiambo(a)gmail.com >

2 years, 6 months

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, 8 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, 5 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

6 months, 1 week

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, 8 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, 9 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, 10 months

Mailman-users search results for query "Postorius"