Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: multiple sites on a mailman3 server question

by David Newman

> On Dec 29, 2021, at 08:49, William Oliver <billo(a)billoblog.com> wrote: > > On Tue, 2021-12-28 at 18:23 -0800, David Newman wrote: >>> >>> [snip] >>> I'm using nginx >> I'd asked about this a few weeks ago for a MM3 host running Ngnix >> with a >> few virtual domains, one of which runs Roundcubemail as its default. >> >> Mark Sapiro suggested the following, and it seems to be working OK. >> You'll need these lines in the Nginx config file for each virtual >> host >> you define. >> >> # begin mailman3 stuff >> >> location /static/ { >> alias /opt/mailman/web/static/; >> } >> > [snip] > > > > No joy. This just makes it kind of work as the mailman interface when > it gets rewritten. > > My problem is that the url is getting referred to > domainname/mailman3/lists even when I don't want it to. That sounds like an nginx configuration problem, not a Mailman3 issue. One assumption in the MM3 web setup docs is that MM3/Django/Postorius/Hyperkitty are the only web services running. If they’re not, and there are other services running, you’ll need to tell Nginx where they are. The setup I provided is an excerpt and covers only how to point to MM3 in such a scenario. It does not cover how to point to something else as root at, say, www.domain.tld. This is off-topic for a Mailman3 list, but maybe check your default files in the sites-available directory, and also anything they point to, paying particular attention to where / points and which root directory you’re using. Same thing with any other config files in that directory. dn > Adding these > changes just (partially) loads the mailman3 interface when it gets > rewritten. > > What I'm trying to figure out is where uwsgi yanks control from nginx > and does the rewriting. Pulling that proxypass stuff out will stop > mailman3 from coming up, and adding it allows mailman3 to show its > interface, but the address gets referred regardless. > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell > nginx not to push it to port 8000. But I don't see where nginx is > getting told to go to 8000 in the www.domain.com section. > > billo > > > > > > > _______________________________________________ > 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/

4 years, 6 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 10:29 -0800, Mark Sapiro wrote: > > > This is the issue. > > See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > for information on configuring Postfix with mailing lists in a > virtual > domain. > > Thanks, at least that changed the error :-) Clearly that was the problem, but it uncovered a new one -- the mailman vmap doesn't seem to be created. In the installation docs, it says about /opt/mailman/mm/data/postfix_vmap: "If this is done and the configured MTA is Postfix, Mailman will create an additional /path-to-mailman/var/data/postfix_vmap file with mappings from the example.com addresses to the corresponding addresses in the alias_domain and will use the alias_domain in the other files. " But, alas, I get a "temporary lookup failure" which isn't all that helpful. However, if I wander over to /var/logs/syslog, I see: Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: connect from localhost[::1] Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains: hash:/opt/mailman/mm/var/data/postfix_vmap: table lookup problem Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains lookup failure Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains: hash:/opt/mailman/mm/var/data/postfix_vmap: table lookup problem Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains lookup failure Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: NOQUEUE: reject: RCPT from localhost[::1]: 451 4.3.0 <billo(a)billoblog.com>: Temporary lookup failure; from=<mailman(a)libertyfp.org> to=<billo(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 15:18:23 libertyfp postfix/smtpd[20254]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory and on and on. This looks like a clue to me -- that mailman3 did not automagically make postfix_vmap.db. Is there a "make-the-freaking-virtual- map-database" command in mailman3, or is this postfix thing? Should I just touch the thing and create an empty file? I'm a little scared to... The error message makes me think that it should be populated with something... Sigh. That's enough for today. I'm off to eat Christmas turkey. Thanks for all your help this morning. billo

4 years, 7 months

[MM3-users] Re: Can disabled users enable themself?

by Flo

On 7/6/26 12:25 AM, Mark Sapiro wrote: > On 7/5/26 1:34 PM, Flo via Mailman-users wrote: >> >> Line 101 is the same as line 126. While 101 is the correct translation >> for line 100, it's wrong for line 125. But this is no explanation for >> not translating. > > If you want to help with the German translations, you are welcome to > contribute at https://hosted.weblate.org/projects/gnu-mailman/ or to > contact the last translator listed in the .po file. > I will do. >>> user's preferred language, not the list's. What is the user's >>> preferred language? >>> >> >> This field is empty at the user's settings, it should default to the >> list's language. This works for the unsubscription message, though. > > If the user's preferred language for the list is empty, fallback is to > the user's address based settings and then to their global Mailman > settings. > How can I find these settings in Postorius? There is only a user's language and a list's language. At the user's settings Postorius says: ``` Preferred language for your interactions with Mailman. When this is set, it will override the MailingList's preferred language. This affects which language is used for your email notifications and such. ``` > The unsubscription message to the user is also in the user's preferred > language, so that probably isn't the issue. > > Is the Subject message translated in your mailman/massages/de/ > LC_MESSAGES/mailman.po file? if so, is the corresponding mailman.mo up > to date (if in doubt, use `msgunfmt` to examine it)? > I found this file and also the translated message: ``` #: src/mailman/app/notifications.py:254 #, python-brace-format msgid "Your subscription for ${mlist.display_name} mailing list has been disabled" msgstr "Sie wurden von der Mailingliste ${mlist.display_name} abgemeldet" ``` I can't see any wrong such that it doesn't translate. Finally I had a look into the code of https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/notificati… . This was not very efficient as I don't know Python but I found out that if I add with _.using(language.code): on line 266 and do the correct intends below it translates. I found this by comparing send_user_disable_warning with send_goodbye_message . I also got confused by wrap and expand once being inside and once outside but apparently it works both ways. I leave it to you how to do the changes as, having already said, I don't know Python and for me everything is like guessing instead of knowing. Flo

3 weeks

[MM3-users] translating templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 13/2/21 20:00, Mark Sapiro wrote: > Also note that the translations on weblate only affect strings in the > core code. The Mailman core templates are not currently translated in > weblate and there are currently no Spanish language templates. One would > need to create Spanish translations of all the templates in > <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> > and submit a merge request to add them to a mailman/templates/es/ directory. I downladed the templates and I'm beginning the translation process, but I have a question. What language map has to be used? In my S.O. it's ISO-8859-15 but I'm concerned it has to be UTF-8... Better ask before having to do a remapping of the files after... It comes to my attention that three files have 0 bytes. -rw-r--r-- 1 Oldno7 wheel 382 14 feb. 00:22 domain:admin:notice:new-list.txt -rw-r--r-- 1 Oldno7 wheel 886 15 feb. 11:28 help.txt -rw-r--r-- 1 Oldno7 wheel 289 14 feb. 00:22 list:admin:action:post.txt -rw-r--r-- 1 Oldno7 wheel 120 14 feb. 00:22 list:admin:action:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 122 14 feb. 00:22 list:admin:action:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 133 14 feb. 00:22 list:admin:notice:disable.txt -rw-r--r-- 1 Oldno7 wheel 71 14 feb. 00:22 list:admin:notice:removal.txt -rw-r--r-- 1 Oldno7 wheel 59 14 feb. 00:22 list:admin:notice:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 257 14 feb. 00:22 list:admin:notice:unrecognized.txt -rw-r--r-- 1 Oldno7 wheel 45 14 feb. 00:22 list:admin:notice:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:member:digest:header.txt -rw-r--r-- 1 Oldno7 wheel 337 14 feb. 00:22 list:member:digest:masthead.txt -rw-r--r-- 1 Oldno7 wheel 154 14 feb. 00:22 list:member:generic:footer.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:member:regular:header.txt -rw-r--r-- 1 Oldno7 wheel 562 14 feb. 00:22 list:user:action:invite.txt -rw-r--r-- 1 Oldno7 wheel 753 14 feb. 00:22 list:user:action:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 739 14 feb. 00:22 list:user:action:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:user:notice:goodbye.txt -rw-r--r-- 1 Oldno7 wheel 281 14 feb. 00:22 list:user:notice:hold.txt -rw-r--r-- 1 Oldno7 wheel 439 14 feb. 00:22 list:user:notice:no-more-today.txt -rw-r--r-- 1 Oldno7 wheel 98 14 feb. 00:22 list:user:notice:post.txt -rw-r--r-- 1 Oldno7 wheel 568 14 feb. 00:22 list:user:notice:probe.txt -rw-r--r-- 1 Oldno7 wheel 273 14 feb. 00:22 list:user:notice:refuse.txt -rw-r--r-- 1 Oldno7 wheel 151 14 feb. 00:22 list:user:notice:rejected.txt -rw-r--r-- 1 Oldno7 wheel 353 14 feb. 00:22 list:user:notice:warning.txt -rw-r--r-- 1 Oldno7 wheel 532 14 feb. 00:22 list:user:notice:welcome.txt TIA.

5 years, 5 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Στις 2019-09-21 22:18, Mark Sapiro έγραψε: > On 9/21/19 1:00 PM, Manos Pitsidianakis wrote: >> >> Can I use a debugger to see exactly what happens in the runner? > > > You might be able to run the runner under pdb > <https://docs.python.org/3.2/library/pdb.html>. I think I found what's wrong: /usr/local/lib/python3.5/dist-packages/mailman/core/runner.py(134)run() -> filecnt = self._one_iteration() /usr/local/lib/python3.5/dist-packages/mailman/core/runner.py(173)_one_iteration() -> self._process_one_file(msg, msgdata) /usr/local/lib/python3.5/dist-packages/mailman/core/runner.py(266)_process_one_file() -> keepqueued = self._dispose(mlist, msg, msgdata) /usr/local/lib/python3.5/dist-packages/mailman/runners/outgoing.py(95)_dispose() -> self._func(mlist, msg, msgdata) /usr/local/lib/python3.5/dist-packages/mailman/mta/deliver.py(86)deliver() -> refused = agent.deliver(mlist, msg, msgdata) > /usr/local/lib/python3.5/dist-packages/mailman/mta/base.py(163)deliver() -> callback(mlist, message_copy, msgdata_copy) /usr/local/lib/python3.5/dist-packages/mailman/mta/decorating.py(32)decorate() -> decorator.process(mlist, msg, msgdata) /usr/local/lib/python3.5/dist-packages/mailman/handlers/decorate.py(264)process() -> process(mlist, msg, msgdata) /usr/local/lib/python3.5/dist-packages/mailman/handlers/decorate.py(89)process() -> footer = decorate('list:member:regular:footer', mlist, d) /usr/local/lib/python3.5/dist-packages/mailman/handlers/decorate.py(226)decorate() -> template = getUtility(ITemplateLoader).get(name, mlist, **extradict) /usr/local/lib/python3.5/dist-packages/mailman/model/template.py(188)get() -> name, lookup_context, **substitutions) /usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py(85)wrapper() -> return function(args[0], config.db.store, *args[1:], **kws) /usr/local/lib/python3.5/dist-packages/mailman/model/template.py(109)get() -> contents = protocols.get(actual_uri, **auth) /usr/local/lib/python3.5/dist-packages/mailman/utilities/protocols.py(38)get() -> response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) /usr/lib/python3/dist-packages/requests/api.py(70)get() -> return request('get', url, params=params, **kwargs) /usr/lib/python3/dist-packages/requests/api.py(56)request() -> return session.request(method=method, url=url, **kwargs) /usr/lib/python3/dist-packages/requests/sessions.py(488)request() -> resp = self.send(prep, **send_kwargs) /usr/lib/python3/dist-packages/requests/sessions.py(609)send() -> r = adapter.send(request, **kwargs) /usr/lib/python3/dist-packages/requests/adapters.py(487)send() -> raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /mailman3/api/templates/list/meli-announce.meli.delivery/list:member:regular:footer (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f4f0495a358>: Failed to establish a new connection: [Errno 111] Connection refused',)) mailman3 tries to get the template I've set via the mailman suite interface but it assumes it is hosted locally: 'http://localhost:8000/mailman3/api/templates/list/meli-announce.meli.delive…' In my setup, they are separate machines. I can't find any way to change this in the configuration. Also, can't the same template be loaded from the master's localhost:8001 api? Haven't fiddled with python for some time, why is this exception catched by "except socket.error"? Is it a subclass of requests.exceptions.ConnectionError?

6 years, 10 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Abhilash Raj

Hi, On Wed, 9 Aug 2017 13:42:20 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/09/2017 12:56 PM, cyp(a)trojina.si wrote: > > Thanks for the quick and helpful reply. (However, please note that until now I was under the impression that there had been no response yet to my question, since my post appears to indicate having 0 comments at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2017/8/) > > > Yes, I see that. It was apparently an issue with caching. I recently > enabled memcached on the server for django and apparently there was an > issue with that. I just did what @abompard suggested at > <https://gitlab.com/mailman/hyperkitty/issues/131#note_30244378> and > that seems to have fixed it, at least for the moment. > > > > Yes, the one-liner did indeed help the "More ..." problem. :) > > > > As for the bar graph, it's showing a bar now, probably correct. But I have not seen anything about django cronjobs in the MM3 documentation, haven't set any up, can't find any in our (Ubuntu 16.04) system and haven't done anything to fix this in-between (although I have restarted mailman-core and mailman-suite a few times). Could you point me in the right direction? > > > This is what I have in Mailman's crontab on lists.mailman3.org > > > @hourly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs hourly > > @daily /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs daily > > @weekly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs weekly > > @monthly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs monthly > > @yearly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs yearly > > 0,15,30,45 * * * * /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs quarter_hourly > > * * * * * /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs minutely > > > > # Send periodic digests. > > # I like 03:30 so they go overnight, but since we're 'global' and on UTC, > > # maybe 07:30 is good. > > 30 7 * * * /opt/mailman/mailman-bundler/bin/mailman digests --send I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as well? > > I don't recall exactly where I saw that that was needed, but you can > find it (except for the periodic digests bit) at > <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>. > Note that that suggests a system crontab with the web server user rather > than the 'mailman' user's crontab. -- thanks, Abhilash Raj

8 years, 11 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Odhiambo Washington

On Wed, Aug 7, 2024 at 2:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/6/24 14:27, Mark Sapiro wrote: > > > > Is this with only one browser? It's a long shot, but clearing browser > > cache might work. > > > Actually, I see the same issues from my browsers, so it's not a browser > caching issue. The only thing left is nginx caching, but, while I know > very little about nginx, I think it doesn't cache by default and I don't > see where in your posted config it's enabled. Perhaps there's more in > your config that you didn't post. > There is nothing I didn't post :) I finally found a way to purge the files cached by Cloudflare. It's in their Dashboard. But not before I had migrated everything to apache2! So now I have all my sites configured in both webservers and I can use whichever I like. Right now I am using apache2, but I am seeing something odd: https://mm3-lists.kictanet.or.ke/archives/ is empty. Is this normal? I am expecting my most active list to appear there or am I overthinking? Like this: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… > If there is a proxy_cache_path directive in your config try > > find /the/proxy/cache/path -type f -delete > > to clear the cache. > There isn't. All the caching mess was coming from Cloudflare proxy servers. If you host your DNS with CF, you will realize they proxy/cache your traffic by default unless you turn that off when creating an A record. As a last resort, your /opt/mailman/mm/static/CACHE/ directory should > contain a css/ directory with 3 files and a js directory containing one > file and a manifest.json file with a template for the `link` directives > referencing those files. > I have seen those files. The js/ directory is easy as its only one file, so your server is > looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create > a symlink in the js/ directory from output.3aaa7705d68a.js to the actual > file. For the css directory, your server is looking for > output.158acc288604.css and output.6dab123e4897.css, and I don't see the > third file in the logs you posted, but if I go to pages in your archive > that I see as unstyled and look at the stylesheet references, they are > to output.44ea6c55e917.css, output.e68c4908b3de.css and > output.9efeb5f3d52b.css so you could just symlink those to the actual > files, it doesn't matter which as all three are loaded on each page I did the symlinks and they helped with nginx, but because I have never had to do that before, I did not like it. That's why I switched to apache2 to see what the effects are and apache2 had/has no problem. Because I have purged the CF cache, I reverted back to nginx and to see from the logs what they are looking for: ``` root@eu:/opt/mailman/mm/static/CACHE/js# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:19:55 [error] 2403078#2403078: *62 open() "/usr/share/nginx/html/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.111, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" ^C root@eu:/opt/mailman/mm/static/CACHE/js# cd ../css/ root@eu:/opt/mailman/mm/static/CACHE/css# ls -al total 196 drwxr-xr-x 2 mailman mailman 4096 Aug 16 16:55 . drwxr-xr-x 4 mailman mailman 4096 Mar 21 15:55 .. -rw-r--r-- 1 mailman mailman 1209 Mar 21 15:55 output.d29798365ddb.css -rw-r--r-- 1 mailman mailman 569 Mar 21 15:55 output.e68c4908b3de.css -rw-r--r-- 1 mailman mailman 180904 Mar 21 15:55 output.e69dbb26da3b.css root@eu:/opt/mailman/mm/static/CACHE/css# ``` So I am left wondering why nginx is prefixing "usr/share/nginx/html" to /static. I then decided to specify a root directive in the vhost pointing to /opt/mailman/mm/static, and I saw nginx prefixing that path to the /static/ again: ``` root@eu:/opt/mailman/mm/static/CACHE/css# cp /dev/null /var/log/nginx/mm3-lists_error.log root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:28:11 [error] 2404382#2404382: *239 open() "/opt/mailman/mm/static/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.112, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` Finally, I changed the root directory to /opt/mailman/mm and this time, I see nginx getting the path correctly, but still looking for the same nonexistent file from above and another file: ``` root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:32:25 [error] 2405076#2405076: *38 open() "/opt/mailman/mm/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.112, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:36:17 [error] 2405080#2405080: *841 open() "/opt/mailman/mm/static/CACHE/css/output.9efeb5f3d52b.css" failed (2: No such file or directory), client: 108.162.238.56, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.9efeb5f3d52b.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` From the above logs, that IP making requests is not my IP! It's the CF proxies. I then disabled the A record proxying for the site and accessed it from a browser that I havven't used in months, and there was still some errors: The IP showing is my IP. ``` root@eu:/opt/mailman/mm/static/CACHE/css# systemctl restart nginx root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:41:11 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:41:11 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/css/output.9efeb5f3d52b.css" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.9efeb5f3d52b.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:41:12 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/js/output.3aaa7705d68a.js" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/js/output.3aaa7705d68a.js HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` And the issue is something about accessing the archives. Not sure if there is something to do for nginx to behave. Apache does not display any single error. -- 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, 11 months

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Stephen J. Turnbull

Henrik Rasmussen writes: > What I meant was, that the list admin may be able to set the list > to Open or Moderate, making it possible to subscribe others, and I > was told by our GDPR folks that we have to make the subscribers > re-confirm, so I was just trying to figure out a way to do it. I > don't know very much about GDPR yet. I think Mark misinterpreted "re-confirm". I assume you mean forcing the *existing* subscribers to perform some action to confirm that they still want to be subscribers. This is not currently a feature of Mailman 2 or Mailman 3. We only can require confirmation at initial subscription, except by something like unsubscribing or no-mail'ing everybody as Mark suggested. > I agree, I wouldn't remove [the mass subscription feature] either, > but I just have to be concerned about the possibility that someone > may have been subscribed against their will. I think you would hear about that. Re-confirmation in light of new rights for subscribers and responsibilities for providers seems reasonable to me, but I think it's reasonable to assume list admins are not malevolent. In light of GDPR, we may need to develop ways to enforce site policy about subscription confirmation and ability of users to unsubscribe themselves at will. > Is there a way to resend a confirmation request to either those who > haven't been requested to confirm or alternately to all > subscribers? It seems to me that what most organizations are doing is not to force reconfirmation, but rather informing their users of 1. their GDPR rights 2. what PII is present in the relevant databases 3. how to terminate the relationship if desired In the case of Mailman, you might also want to 4. require SSL to access the website 5. advise the users to change their passwords if you had been allowing access via HTTP or sending password reminders For stock Mailman 2, this is not a big deal (I don't think any of the subscriber configuration information is PII except display name and address), but for Mailman 3 I believe there's some profile information in HyperKitty that might be considered PII, and Mailman 3 will be easier to extend using plugins etc to potentially incorporate even more. Mark Sapiro writes: > Or, post to the list that everyone will need to resubscribe and > then remove everyone. Note that this means that people who resubscribe late will miss mail. That may or may not be a big deal. Steve

8 years, 2 months

[MM3-users] Re: How to delete non-users

by Allan Hansen

Thank you, Stephen. Yes, I have verified that the users will be subscribed once the moderator accepts their subscription requests. The tricky time is between the non-member record is created and the moderator accepts the application. Many of them will try to post before their subscription is approved (some moderators are good at procrastinating). During this time the user thinks that the subscription has been entered, but is not able to send/receive messages. Then they complain to me... While some of the users and moderators may have visual impairments (well, it's possible that even a majority wears glasses - I do), the bigger issue is that most are not techies, and some are very much not techies. They are brilliant in other ways and Mailman has been a wonderful tool for them all to communicate and organize, but it's also a bit quirky. Yours, Allan On 9/16/22, 23:28 , "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: Mark Sapiro writes: > My original point is the presence of a nonmember role should not prevent > the user from subscribing. If there is an issue with subscribing it is > probably because of the outstanding subscription request waiting > moderator approval. I don't think it is likely, but is it possible that the moderator is not just refusing the subscription, but banning the address from subscribing? > I understand that you would like the nonmember role to disappear, but > that isn't going to happen in the distribution, and I can't undertake > the extensive effort required to figure out how you can do it for your site. It seems to me that explicitly displaying the nonmember role is an internal and/or administrative need, and most ordinary users are only interested in whether they are subscribed or not. If the list appears in "their" list of list, they're going to assume they're subscribed. (We've even had that confusion about moderators and owners in the past.) I haven't done any deep thinking about this, but perhaps we could provide a more streamlined view tuned to this specific need? That is, the role won't go away, but at least in some contexts you'll have to ask explicitly for that user-list relationship to be displayed. Also, IIRC Allan's community contains a substantial group of folks with visual impairments, presumably including admins and moderators. Especially to serve that circumstance I think it makes sense for us to provide streamlined views that are more easily grasped as a whole where we can. _______________________________________________ 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/

3 years, 10 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Odhiambo Washington

On Mon, Jan 30, 2023 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 02:44, Odhiambo Washington wrote: > > The documentation > > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > > > says that I need to create /path/to/postfix-mailman.cfg containing: > > [postfix] > > transport_file_type: regex > > > > Then append the path to the [mta] section of mailman.cfg, viz: > > > > [mta] > ... > > configuration: /path/to/postfix-mailman.cfg > > > > That is exactly what I have done on my test platform, but I get the error > > below when creating a list. > > Perhaps I overlooked something? > ... > > "/opt/mailman/venv/lib/python3.9/site-packages/mailman/mta/postfix.py", > > line 87, in __init__ > > self.postmap_command = mta_config.get('postfix', 'postmap_command') > > File "/usr/local/lib/python3.9/configparser.py", line 792, in get > > raise NoOptionError(option, section) > > configparser.NoOptionError: No option 'postmap_command' in section: > > 'postfix' > > This is a bug. Whether it is a bug in documention or code is not > completely clear. Current code requires there be a `postmap_command:` > setting in the [postfix] configuration even though it isn't used if > `transport_file_type:` is set to regex. > > You can fix this in one of two ways. Either apply this patch > ``` > --- a/src/mailman/mta/postfix.py > +++ b/src/mailman/mta/postfix.py > @@ -84,9 +84,10 @@ class LMTP: > def __init__(self): > # Locate and read the Postfix specific configuration file. > mta_config = external_configuration(config.mta.configuration) > - self.postmap_command = mta_config.get('postfix', > 'postmap_command') > self.transport_file_type = mta_config.get( > 'postfix', 'transport_file_type') > + if self.transport_file_type == 'hash': > + self.postmap_command = mta_config.get('postfix', > 'postmap_command') > > def create(self, mlist): > """See `IMailTransportAgentLifecycle`.""" > ``` > (watch for possible wrapped lines in above) or add > > postmap_command: unused > > to /path/to/postfix-mailman.cfg. > > Note however that hash tables for Postfix are more efficient than regex > tables and the only reason we support regex tables is for a Docker > container that doesn't have Postfix installed in the Mailman container. > So, if I understand this correctly, there is no need for the addition of this parameter: ``` configuration: /path/to/postfix-mailman.cfg ``` to the mta config block in mailman.cfg in a non-docker environment, or when only using hash tables?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 5 months

Search results for query "sapiro"