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

[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, 9 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>

7 years, 4 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, 7 months

[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, 11 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, 7 months

[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]

3 years, 3 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, 11 months

[MM3-users] Re: disabled users

by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia

Hello, Thank you for your answers. The problem is: I have a lot of user disabled for too many bounces. These users have the same provider that, probably, has some limits of number of mail that can be delivered from the same server. This causes timeout connections and, mailman creates correctly a bounce. So I would like to discover a way to reset bounce limits so they can be re enabled to receive. I tried also to unsubscribe and resubscribe users but it does not change anything. Thank you Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it Il 26/10/23 00:13, Mark Sapiro ha scritto: > On 10/25/23 10:44 AM, Stephen J. Turnbull wrote: >> Servizio Informatico U.I.C.I. Sezione territoriale di Brescia writes: >> >> > Wher I find the disabled user of a mailing list and wher I can >> > reactivate them? >> >> If you are the list owner or superuser, when you visit the list's >> information page there will be a horizontal menu across the top. One >> of the entries is Users. Click to open the dropdown menu and choose >> Members. There doesn't seem to be an explicit notation for disabled >> users, but if the entry in the far right column "bounce score" is >> None, the member may be disabled. > > I don't think this is correct. Members with delivery disabled by > bounce will normally show 0 rather than None for bounce score. > > If you have shell access to the server as the Mailman user, you can > run this shell interaction to find members with delivery disabled by > bounce. > ``` > $ mm/bin/mailman shell -l test(a)example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the test(a)example.com mailing list > >>> for member in m.members.members: > ... if member.delivery_status == DeliveryStatus.by_bounces: > ... print(member.address.email) > ... > >>> > ``` > But the question is, why do you want to re-enable their delivery. > Granted, there are situations such as a misconfigured MTA or not > applying needed DMARC mitigations that could result in 'spurious' > bounced deliveries, but normally bounce processing disables delivery, > sends warnings to the bouncing address and ultimately unsubscribes > them because the address it truly not deliverable. > >

2 years, 9 months

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Mark Sapiro

On 9/20/19 5:39 AM, Henrik Rasmussen wrote: > I know this is quite long (sorry), but I hope this part of the mailman.log may provide some clue to what went wrong. It doesn't. > As mentioned, Mailman stopped receiving mails some days ago and I have been restarting Mailman (without solving anything) at Sep 18 13:30:03 2019. On Sep 20 07:05:23 2019 everything started working again by itself. > > / Henrik Rasmussen > I'm snipping a bunch of irrelevant stuff having to do with web interactions, etc. > Sep 20 06:42:22 2019 (35) HOLD: listname(a)lists.example.com post from someone(a)foo.bar held, message-id=<4E8DB72B-66D9-456E-B51C-2A49423CF29F(a)foo.bar>: The message comes from a moderated member > Sep 20 06:42:23 2019 (35) ACCEPT: <CALcvC6H5ko14LT8F_z_nbddp0DmDgfb-Rt32s+0TbpPrY3BL_g(a)mail.foo.bar> There are lots of these indicating messages have been received via LMTP and passed to Core. > Sep 20 06:42:48 2019 (35) ACCEPT: <CAG3z+4+67M9jAjbVtSqUdUCU6cS1dOYBsmMTAdePL3+O+Nn+sQ(a)mail.foo.bar> > Sep 20 06:42:56 2019 (32) Exception in the HyperKitty archiver: 'url' > Sep 20 06:42:56 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 217, in _send_message > archived_url = result["url"] > KeyError: 'url' > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: 'url' > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 217, in _send_message > archived_url = result["url"] > KeyError: 'url' > Sep 20 06:42:57 2019 (32) HyperKitty failure on http://mailman-web:8000/hyperkitty/api/mailman/archive: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > (500) > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > > Sep 20 06:42:57 2019 (32) HyperKitty failure on http://mailman-web:8000/hyperkitty/api/mailman/archive: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > (500) > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: > > <!DOCTYPE html> > <html lang="en"> > <head> > <meta charset="UTF-8"> > <meta http-equiv="X-UA-Compatible" content="IE=edge"> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <title>Server Error</title> > <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> > <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> > <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> > <link rel="stylesheet" href="/static/postorius/css/style.css"> > >  >  >  > </head> > <body> > <div class="container"> > <h1>Server error</h1> > <div class="alert alert-danger">An error occurred while processing your request.</div> > </div> > </body> > </html> > > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: 'url' > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 217, in _send_message > archived_url = result["url"] > KeyError: 'url' > Sep 20 06:42:57 2019 (32) Exception in the HyperKitty archiver: 'url' > Sep 20 06:42:57 2019 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/usr/local/lib/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 217, in _send_message > archived_url = result["url"] > KeyError: 'url' There are lots of the above errors/tracebacks. They are a problem, but not specifically the one affecting Postfix delivery. There are two different tracebacks. The ValueError is because the mailman_hyperkitty shim has called Hyperkitty via http://mailman-web:8000/hyperkitty/api/mailman/archive to archive the message and HyperKitty returned a 500 status with the HTML <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css">    </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Then the KeyError occurs because the response did not include the URL of the archived message. When this occurs, mailman_hyperkitty retries the message until it succeeds. For more information on the HyperKitty issue, look in the Django log whose path is defined in LOGGING['handlers']['file']['filename'] in the Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Odhiambo Washington

On Thu, 30 Jul 2020 at 22:02, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/30/20 11:24 AM, Odhiambo Washington wrote: > > > This works - I mean changes the error message to > > > > [Thu Jul 30 18:11:50.269667 2020] [wsgi:error] [pid 7627] [remote > > 197.232.81.246:63962] > > > /opt/mailman/mm/venv/lib/python3.7/site-packages/readme_renderer-26.0-py3.7.egg/readme_renderer/markdown.py:38: > > UserWarning: Markdown renderers are not available. Install > > 'readme_renderer[md]' to enable Markdown rendering. > > [Thu Jul 30 18:11:50.269700 2020] [wsgi:error] [pid 7627] [remote > > 197.232.81.246:63962] warnings.warn(_EXTRA_WARNING) > > > I'm not sure why you are getting this warning, and it's non-fatal, but > you can get rid of it by > > pip install cmarkgfm > > in your virtualenv. > (venv) [mailman3@gw ~]$ pip install cmarkgfm Requirement already satisfied: cmarkgfm in ./mm/venv/lib/python3.7/site-packages/cmarkgfm-0.4.2-py3.7-freebsd-12.1-RELEASE-p7-amd64.egg (0.4.2) Requirement already satisfied: cffi>=1.0.0 in ./mm/venv/lib/python3.7/site-packages/cffi-1.14.0-py3.7-freebsd-12.1-RELEASE-p7-amd64.egg (from cmarkgfm) (1.14.0) Requirement already satisfied: pycparser in ./mm/venv/lib/python3.7/site-packages/pycparser-2.20-py3.7.egg (from cffi>=1.0.0->cmarkgfm) (2.20) (venv) [mailman3@gw ~]$ > > [Thu Jul 30 21:11:50.573233 2020] [authz_core:error] [pid 10846] [client > > 197.232.81.246:63962] AH01630: client denied by server configuration: > > /var/spool/mailman-web, referer: > > http://mm3-lists.my.server/mm3/mailman3/lists/ > > > > There is NO /var/spool/mailman-web anywhere. It has not been created. > > You mentioned that it should be created automatically, IIRC. > > > No. I think I told you that the references to > /var/spool/mailman-web/static in your Apache config should be changed to > /opt/mailman/mm/static and that directory would be created/populated by > mailman-post-update. > > I think you still have > > Alias /static "/var/spool/mailman-web/static" > > in your Apache config and it needs to be > > Alias /static "/opt/mailman/mm/static" > > That may be my fault as when I recently edited > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > >, > I missed that line. After changing the Alias line and running the mailman-post-update, all errors are gone and I have a web UI. Yayi!!! I have been able to create a domain, a list for testing. Now I just need to go through the analysis of what I have been doing so that I can clean up my notes. Then I can come back on migration issues. A BIG THANK YOU for all the support up to this point. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 11 months

Search results for query "sapiro"