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

[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, 4 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, 5 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

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Abhilash Raj

> On Sep 29, 2021, at 2:34 PM, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/29/21 9:50 AM, Odhiambo Washington wrote: >>> 1. Confirmation emails to Users has wrong domain name (example.com!) >>> <https://docs.mailman3.org/en/latest/faq.html#id1> >>> < >> https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… >>> >>> >>> This happens when your reverse (SSL) proxy isn’t setting up the correct >>> headers when proxying requests. Fix this by setting the right >>> proxy_set_header directives: >> ... >>> How is this supposed to be mitigated in Apache when using WSGI? >>> >>> My config: >>> >>> WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman >>> user=mailman group=mailman >>> WSGIPythonHome "/usr/local" >>> WSGIProcessGroup hyperkitty >> >> >> You are using mod_wsgi and not proxying at all, so this is not relevant >> in your case. >> >> Are you actually seeing this issue? If so, it might be related to >> >> https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… >> > > My issue is related to this, but the documentation referred to is not for > the faint-hearted! > I can't make head or tails of it. Click on “Domain” in Postorius from the top bar, which should take you to the Domains page. For your domain (in the “Mail Host” column), see the corresponding “Web Host” column, it should look something like: lists.mailman3.org (lists.mailman3.org) (Edit) SITE_ID = 1 on a new-ish version of Postorius. If it doesn’t show the right values and instead shows “example.com” for you, click on the “Edit” link, which will take you to a page that will allow you to edit both the values. In that page, you can update “Domain name” to whatever your domain is (lists.xxx.xxx) and then “Display Name” can be anything else you want or the domain name itself. Click “Save” and then Click on “View Site” in the top right corner of the page to go back to Postorius. Abhilas > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' :-) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Thu, 21 Mar 2019 17:27:01 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/21/19 3:02 AM, Malcolm Austen wrote: >> >> My only experience of MM3 is with Ancestry's 'RootsWeb' installation. >> From the emails I can see a header "X-Mailman-Version: 3.1.0" but I >> can't find anything to identify Postorius which is the only interface I >> have to the system. > > Isn't there a footer at the bottom of wach page with something like: > Postorius Documentation • GNU Mailman • Postorius Version 1.2.5 Unfortunately not Mark, Ancestry/RootsWeb have a history of tailoring Mailman heavily - and then deciding they don't have the resources to update to a new version :-( All there is on <https://lists.rootsweb.com/postorius/> is: RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community. Learn more. About Us | Contact Us | Rootsweb Blog | Copyright © 1997-2018 Ancestry | Corporate Information | Privacy | Terms and Conditions >> From symptoms seen and described by others, I have deduced that the >> Postorius admin-per-user moderation options of "Default processing" and >> "List default" mean that a user may be set (by default on the rootsweb >> system!) to use the system default moderation settings rather than the >> list default settings. > > New (non-)members always have Moderation set to List default. This means > their posts are governed by the applicable Settings -> Message > Acceptance settings. I suspect that everyone on the rootsweb system was mistakenly set to 'Default processing' when they were bulk-imported from Mailman2. > Setting a user's Moderation to Default Processing means that users posts > will not be held/rejected/discarded/accepted immediately based on > "Default action to take when a (non-)member posts to the list", but > additional checks will not be bypassed. See > <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html>. I will read that, and whatever else I can. >> Are my deductions correct? And if so, could this be the explanation of >> the issue detailed in this thread? > > Setting a user's Moderation to Default Processing (or Accept) would > bypass the list defaults and could be the explanation of this issue. > > When the non-member owner first posts to the list that address becomes a > non-member of the list. I.e. it is in the roster of known non-members of > the list and that non-member record could have had its Moderation set to > Accept or Default Processing at some point which would explain why the > posts are accepted. Thanks for the explanation and link, Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

6 years, 10 months

[MM3-users] Re: missing graphics in Postorius

by David Newman

On 12/7/21 11:17 AM, Mark Sapiro wrote: > On 12/6/21 10:15 PM, David Newman wrote: >> After installing MM3 on Debian 10 using the venv docs, no graphics >> appear in the admin or list pages, just broken links. >> >> The mailmanweb log has lines like this: >> >> ERROR 2021-12-07 06:04:10,002 18262 django.security.DisallowedHost >> Invalid HTTP_HOST header: '127.0.0.1'. You may need to add '127.0.0.1' >> to ALLOWED_HOSTS. >> >> which is odd because there is the line for "localhost" in settings.py, >> and /etc/hosts correctly ties this to 127.0.0.1. > > > Add '127.0.0.1' to ALLOWED_HOSTS anyway. Done, thanks. Given that DNS works fine on this host, with localhost and 127.0.0.1 resolving backward and forward, this seems like a bug. Shouldn't the resolver be able to recognize localhost without hard-coding an address? Particularly this address, since the IETF is considering what is IMO a crazy idea to unreserve 127/8? https://www.ietf.org/id/draft-schoen-intarea-unicast-127-00.html > > >> There are entries like this in /var/log/nginx/error.log saying the >> files just aren't there: >> >> 2021/12/06 22:00:30 [error] 18123#18123: *65 open() >> "/opt/mailman/web/static/postorius/img/mailman_logo_small_trans.png" >> failed (2: No such file or directory), client: x.x.x.x, server: >> somehost.example.com, request: "GET >> /static/postorius/img/mailman_logo_small_trans.png HTTP/2.0", host: >> "somehost.example.com", referrer: >> "https://somehost.example.com/mailman/lists/" >> >> (I've obfuscated names and addresses here, but "somehost.example.com" >> refers to a valid FQDN in the log.) >> >> I thought I'd followed all the venv docs, but the >> /opt/mailman/web/static/postorius directory doesn't exist. Did I miss >> something? > > Assuming you have > ``` > STATIC_ROOT = '/opt/mailman/web/static' > ``` > in your /etc/mailman3/settings.py file, you may need to create that > directory if it doesn't exist. You shouldn't need to manually create the > /opt/mailman/web/static/postorius directory if the > /opt/mailman/web/static directory exists and is writable/searchable by > the Mailman user. Yes, that was it. Thanks. Previously you'd pointed out what you considered an error in the venv docs, with the workaround to manually create the /opt/mailman/web directory [1]. I think the same issue applies here, and also that /opt/mailman/web and subdirectories need to be owned by the mailman user. Thanks again. dn > > That should enable > ``` > (venv)$ mailman-web collectstatic > ``` > to populate that directory. Be sure you've run all four commands at > https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… > et seq. >

4 years, 1 month

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/08/06 10:46, Odhiambo Washington via Mailman-users wrote: > On Tue, Aug 6, 2024 at 10:46 AM Roland Giesler via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> On 2024/08/05 19:59, Mark Sapiro wrote: >>> If you really have local users on box2.gtahardware.co.za with >>> addresses '@fast.za.net' and you want to relay list mail to lists >>> '@fast.za.net', you need to see >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… >> . >> >> Thank you for that! From that it seems it may still be possible to use >> PMiaB as my MTA after, but I'll work through that reference and test it >> and report back. > I think that ALL MTAs have the concept of local domains (for which mails > are delivered to 'local mailboxes') and remote domains (aka relay domains) > for which mail is relayed to another host which has the mailboxes. > So in your case box2.gtahardware.co.za (this is FQDN) could be handling > local emails, e.groland@gtahardware.co.za,johndoe@gtahardware.co.za, etc. > Those are local, and so gtahardware.co.za is a local domain. However, > fast.za.net is a relay domain and all mail toXXX(a)fast.za.net should be > relayed to the MM3 server. > If your MTA does not have this concept, then it's either not ready for > prime time or it wasn't intended to have such ability. With Mail-in-a-box and it's fork Power-mail-in-a-box, the recipient domain is created when an email address is added for which the box should receive mail. When the last email address for a domain is deleted, the domain is deleted too. More than that, the DNS zone file for the domain is also created and so are certificates, aliases and more. If I stick to that, then it's easy to run a mail server and everything *just works*. This is why I don't want to remove any of the MiaB settings. If I therefore want to allow mail for fast.za.net onto box2.gtahardware.co.za, then I need to have at least one mailbox for that domain, or an email alias on that box. This of course complicates matters for forwarding, since not all mail for fast.za.net must be forwarded, only the mail that is not specifically configured on box2. With Mark's link I think I may get this to work, but I need to still impliment and test this. It will take a couple of days for me to get around to it bit by bit (no pun intended!). > >

1 year, 5 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Fri, Dec 23, 2022 at 9:21 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Fri, Dec 23, 2022 at 4:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/22/22 16:03, Odhiambo Washington wrote: >> > >> > There is just one more thing - I have this in settings.py: >> > LOGGING['handlers']['file']['filename'] = >> > '/opt/mailman/mm/var/logs/mailmanweb.log' >> >> >> And what are LOGGING['handlers']['file']['level'], >> LOGGING['handlers']['file']['class'] and >> LOGGING['handlers']['file']['formatter'] >> > > Those are left as defaults in my setup.py. > > >> > However, the referenced file is ever empty. At what point is it >> supposed to >> > record anything? >> >> What is logged depends on `level` but even with `DEBUG` not much routine >> stuff is logged. See >> https://docs.djangoproject.com/en/3.2/topics/logging/ > > > I will read that and see if I get to pick up something. > > And now I am having a problem with mod_wsgi. > First, the URL displayed when I load the page looks bogus to me. > While I expect the URL to be > https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me > https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is an > extra /mailman3! > > So I have; > 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - working, > or appears to. > 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - working, > or appears to. > 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, or > appears to > 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, or > appears to > 5. > https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… > - This throws an exception error when I click "Manage Subscription". > > -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ > > And while I do not quite understand the error itself, there is also one > particular line that I also saw that has left me baffled: > [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client > 197.232.81.246:13865] AH00128: File does not exist: > /usr/local/www/apache24/data/archives/list/ > kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, > refe > rer: > https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke > > I also need to add the fact that at the point where I am clicking "Manage Subscription", the URL has changed to https://mm3-lists.kictanet.or.ke/mailman3/archives/list/kictanet@lists.kict… (just a single /mailman3). -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: how to unhold a hold message from a nonmmeber in hold list.

by Odhiambo Washington

On Fri, Apr 21, 2023 at 12:04 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > El 21/4/23 a las 10:37, Odhiambo Washington escribió: > > > > > > On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via > > Mailman-users <mailman-users(a)mailman3.org> wrote: > > > > I'm having troubles with Django and cannot access to web admin. > > > > I need to unhold a message while figures out what is happening. > > > > Searching the mailman cli help commands didn't help me. > > > > Anyone who knows how to unhold a message, please? > > > > > > TBH, I find it a lot easier to fix the web UI than mess with the > > python shell :-) > > > > While you wait for @Mark Sapiro <mailto:mark@msapiro.net> to save you, > > you can be reading the following: > > > > > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > Thanks: it seems the place to do it (I didn't find it) > > I'm fighting the web UI problem. It seems that something in wsgi has > changed and is no more compatible with my version of things. Error log > from apache shows: > > mod_wsgi (pid=30632): Failed to exec Python script file > '/usr/local/mailman3/wsgi.py'. > mod_wsgi (pid=30632): Exception occurred processing WSGI script > '/usr/local/mailman3/wsgi.py'. > Traceback (most recent call last): > File "/usr/local/mailman3/wsgi.py", line 34, in <module> > from django.core.wsgi import get_wsgi_application > File "/usr/local/lib/python3.9/site-packages/django/core/wsgi.py", line > 2, in <module> > from django.core.handlers.wsgi import WSGIHandler > File > "/usr/local/lib/python3.9/site-packages/django/core/handlers/wsgi.py", > line 3, in <module> > from django.conf import settings > File "/usr/local/lib/python3.9/site-packages/django/conf/__init__.py", > line 19, in <module> > from django.utils.deprecation import RemovedInDjango50Warning, > RemovedInDjango51Warning > File > "/usr/local/lib/python3.9/site-packages/django/utils/deprecation.py", > line 4, in <module> > from asgiref.sync import iscoroutinefunction, markcoroutinefunction, > sync_to_async > ImportError: cannot import name 'iscoroutinefunction' from > 'asgiref.sync' (/usr/local/lib/python3.9/site-packages/asgiref/sync.py) > If you did some system updates then that is where you need to check. Obviously, something did update, leading to the breakage. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 9 months

[MM3-users] Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > But whatever is listening on port 8001 is apparently not Mailman's rest > server. What does > ps -fww 14080 > or whatever PID is currently listening on port 8001 show. UID PID PPID C STIME TTY STAT TIME CMD list 15972 15963 0 Aug11 ? Sl 0:13 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 > > OK. > Perhaps instead you should have > uid: list > gid: list > in your uwsgi configuration if you don't already. Tried that while also switching mailman3-web.service to list:list, exactly the same error. Also, I have /run/mailman3-web/uwsgi.sock owned by list:list now instead of www-data:www-data. What the logs say: *** Starting uWSGI 2.0.18-debian (64bit) on [Thu Aug 12 08:46:37 2021] *** compiled with version: 8.2.0 on 10 February 2019 02:42:46 os: Linux-4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) nodename: mail machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 2 current working directory: / detected binary path: /usr/bin/uwsgi-core chdir() to /usr/share/mailman3-web your processes number limit is 3831 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) error removing unix socket, unlink(): Permission denied [core/socket.c line 198] bind(): Address already in use [core/socket.c line 230] Not sure if that means the two directories need to be owned by list, currently they are owned by root > > I'm not familiar enough with this form of ProxyPass using sockets to > understand what the localhost:8001 does in this context, but uwsgi > should not be doing anything with port 8001. In a configuration using > TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API > server listens. uwsgi should receive connects in your case via the unix > socket and then pass them to Django via the application in wsgi.py > Also, you may want other paths proxied to uwsgi, namely at least some of > hyperkitty, postorius, archives, accounts, admin and user-profile. Ok, I removed that port again, now it's exctly like in the automatically generated config file. And you mean like <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /hyperkitty unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /postorius unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /admin unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /archives unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /accounts unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /user-profile unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> > > These should be 'list', not 'www-data'. That's your permissions issue on > settings.py

4 years, 5 months

Search results for query "sapiro"