Search results for "Postorius" - Mailman-users

Re: Rolling releases for Container Images and Funding Campaign for Mailman

by Abhilash Raj

On Sun, Nov 12, 2017, at 08:06 AM, Simon Hanna wrote: > > >>> These images are built using git-heads *only* if they are passing our > >>> test suite and are re-generated weekly. You should be aware that while > >>> all these components are tested with their individual test suites, their > >>> combination might sometimes not be stable. This will get you > >>> updates/bug-fixes much faster :) > >> This contradicts what you said in my merge request for Postorius > >> https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 > >> > >> You either use released versions, or make sure that the master branches > >> are always compatible. You can't have both with the current development > >> model. > > Not exactly, I still believe all our git-heads should be compatible with > > released (i.e. stable) versions of dependencies, regardless of the fact > > that we maintain those dependencies. > > > > Also, there is at least one test per-project which tests with git-heads > > of dependencies we maintain, so that we know if we make any incompatible > > changes. > > > > I am not sure what in the current development model prevents us > > to do both? > > > > The story for container images is different than testing with git-heads. > > We need better integration testing for the entire suite to be stable in > > conjunction, rather than independently. In fact, containers might be the > > perfect way to actually do the integration testing. > Scenario: Core changes something about rest that is backwards > incompatible. The change is commited to master. Since your containers > use the master branches, all future builds will fail until mailmanclient > and postorius/hyperkitty. Yes, that is a totally possible scenario. But, given that kind of testing we currently do, this scenario can happen not only to git-heads but also releases. That is what I am trying to build using container images. The fact that I *announced* and *released* these rolling images for public use, is only because people asked for it before. These images come with a fair amount of warning that, right now, they can break! > If you want to always have Postorius (and others) compatible with the > latest release of master, development for Postorius will be a Pain, > because you can't use the master branch of mailman for testing and quick > changes. Also your containers and all integration tests that can be done > with them will always fail. It would most definitely be a pain if we were to break REST API frequently, but that is quite rare. Given that in future API will be consumed by not just us, it is important to keep this assumption true. Another wishful project I have is to be able to "map" the REST API and monitor for changes; it'd also help us with lemme (the authenticating/authorization proxy for Core). And yes, container images will fail, and that's the point! I want them to fail so that releases don't :) Rolling images are meant to bring a faster feedback-loop from users who are OK with rare occasional breaking and want to help test the software, something like public-beta releases. > Until you fix Postorius and the other clients... So why not just have > the master branches always compatible and make life easier for > developers. Incompatible changes are released only with major version upgrades, so it is not going to happen with everyone, unless they choose to use the git-heads and get themselves into it. > I don't see a good reason why you want to do it the other way round... > > Any bug in core that affects Postorius will also just remain there until > you release a new version of core. > > If you really really want to have it your way, there have to be more > frequent releases. Yes, we definitely don't want to say "use new beta-quality container images or stone age stable release". Going forward, we will have more frequent releases too :) > >>> - Improve the container images to work with new micro-services > >>> architecture, > >>> to achieve scaling and redundancy in services. > >> The current bottleneck is the rest api from core. IMO bulk actions, > >> filtering and sorting should be added there before trying to have > >> multiple postorius/hyperkitty instances serving the same core... > > I didn't say they will be served from the same core ;-) > > > > Yes, the Core's API can be further improved to be more efficient. But > > that > > doesn't prevent us from scaling. I understand there are issues around > > multiple > > instances of containers, but I have ideas to get around most of them. > I just don't want that people that have issues with big installations > get the answer: > We know of that issue, please deploy Mailman on X containers/machines as > a workaround Containers are just an easy way to scale, given that we already have them, it'd be fun to see if I can make multiple instances run in parallel. Given that _most_ parts store their data in a data store (database, redis etc), it shouldn't be too difficult. There will be quirks with logging, queues in Core and hence held message views in Postorius, but apart from that, I think everything else can be served using any random instance of Core/Postorius/Hyperkitty. We can most definitely run multiple instances of Hyperkitty, which I feel will be more used than any other part of UI. If we partition the data smartly, we could do the same with Core. Again, these are just theories and needs much more testing and some changes in components themselves! This would most definitely increase the availability and auto-scaling. Making Core's API more efficient would definitely be a good thing and we do intend to do that in future. But, this would still be relevant if we had an efficient REST API, it's not a band-aid to the actual problem :) -- Abhilash Raj maxking(a)asynchronous.in

7 years, 11 months

Re: Separating Lists by Domain

by Johannes Winter

Am Mon, 24 Dec 2018 00:41:43 -0000 schrieb brian(a)emwd.com: > I have successfully setup a second domain with my Mailman3 setup. I > also created a list using the second domain. So I have two domains > with one list each. The issue I see at this point is all of the lists > are shown via Postorius regardless of the list domain used. Is it > possible to have only the lists to show that are part of the domain > being used to access? For example: > > http://domaina.com/postorius/lists/ > > Only listnames(a)domaina.com show up. > > http://domainb.com/postorius/lists/ > Only listnames(a)domainb.com show up. > > Right now both domaina AND domainb lists showup regardless of the > domain being used to access Postorius. The same goes for Hyperkitty > as well. Hi Brian, I once asked a similar question: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Best regards, Johannes

6 years, 10 months

New subscribed (by invitation) user: no password received in invitation/welcome e-mail. Postorius sign up / password reset broken

by Stephen J. Turnbull

^m'e via Mailman-users writes: > I migrated form MM2.1 to MM3.3.10 on Debian Trixie (mariadb > backend) -- I know that's a bit unorthodox to ask here for help on > a non venv-based installation, We appreciate your courtesy, but this is inaccurate. If you install a distro-packaged Mailman and it doesn't do the basic stuff such as "start" or "respond to web requests" out of the box, that's a distro problem. (That includes any features missing because of the inevitable lag in distro packaging.) On the other hand, if you have a misconception (see Issue #1) or if Mailman is basically working but doing a particular weird thing (in your opinion, and that's Issue #2), asking here is the right thing to do. Distro maintainers are frequently experts in packaging but ordinary users of their package without expertise in troubleshooting the package, and usually zero interest in educating users. That is what we are here for! And, obviously, "real" bugs may manifest first in a distro package. > but hopefully I'll first gain a bit of insight of MM3 in order to > formulate a more precise request to Debian maintainers. I don't think these are Mailman issues, and quite likely they're not Debian issues. > ## Issue #1. > > A newly invited (from Postorius mass subscription page) and > confirmed user doesn't get any password in their invitation/welcome > e-mail. The invitation/welcome emails usually don't know if the user is verified, and they are otherwise not personalized, so sending a one-time password (OTP) at that time would be a lot more complicated than it's worth. Also, many users may prefer to NOT set a password at all. For example, if you configure the Gmail socialauth plugin, a Gmail user can log in without doing the OTP dance. (I think we still require the dance to verify the address, because socialauth is hard and the burden is small. And if 'confirm' is set in the list preferences, you have to either log in to Postorius to subscribe, or do the dance for an email subscription.) Because Mailman 3 has a model of a user with multiple addresses and subscriptions, the burden of using the reset password dance for the initial setting of a password is considered very small (it usually is done once during the user's association with the Mailman instance, if at all). So that's the way we do it. > ## Issue #2 > > Anyway, if that new user asks for a password reset on Postorius they get > > "Server error > An error occurred while processing your request." This appears to be an MTA misconfiguration, either in Mailman or possibly in the MTA: > File "/usr/lib/python3.13/smtplib.py", line 861, in sendmail > self.ehlo_or_helo_if_needed() Mailman tried to connect to a mail server. > File "/usr/lib/python3.13/smtplib.py", line 365, in send > raise SMTPServerDisconnected('please run connect() first') > smtplib.SMTPServerDisconnected: please run connect() first It failed. Twp possibilities off hand: (1) The server expects authenticated and/or encrypted email (SASL and TLS), but Mailman is not configured to do that. (2) A typo in the server IP or hostname. There are all sorts of other reasons why a server might refuse a connection, but we'd need a lot more information to diagnose. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months

Error -- postorius Un-handled exception

by Stephen J. Turnbull

Mark writes: > # tail -f /opt/mailman/web/logs/mailmanweb.log > File > "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/connection.py", > line 160, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server > Error"} > ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server > Error: /postorius/lists/testing.example.com/ I don't recall seeing this one before, maybe Mark S has some idea. Try running all the system initializations with "mailman info" and "mailman conf". This often will elicit errors if the system is messed up. More likely to get this error would be "mailman withlist $LIST" (maybe you need an '-l' option to specify the list, I forget). If that doesn't elicit the error, then check that Mailman's runners are running with ps. Since it's Debian, I guess they should be running as the 'list' user. Are Mailman's files and directories owned by 'list' or sometimes 'www-data' for log files? The log is saying that when Postorius tried to look up that list, it tried to call out to Mailman core via HTTP to the API to get the information and that access failed with HTTP status 500. I think the actual error is likely to be reported in mailman.log (or it might be in error.log, "grep '05:41:46' *.log" in Mailman's log directory will probably find it). I'm pretty sure there will be relevant log entries, probably a matching traceback. You might also try grepping in your SQL DB logs for that timestamp. > And the Mailman log is a mystery to me, It's hard to get good exception reporting when you have multiple layers in the stack, and some of them are separated by TCP/IP connections. You'll have to correlate across logs by timestamp. > and no error is reported in the Nginx log ... Right, this is happening far far away from nginx, much farther down the stack. Steve

1 year, 9 months

Re: New subscribed (by invitation) user: no password received in invitation/welcome e-mail. Postorius sign up / password reset broken

by Marco Emilio Poleggi

Thanks Steve. Yeah, indeed, it was a stupid configuration error. So, while investigating malformed-url errors (https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, I had set mistakenly in `/etc/mailman3/mailman-web.py`: EMAIL_HOST = '' Of course, then how can Postorius contact my SMTP!? Bah, tweaking stuff uncritically is always Bad Thing (TM), dumb me. Everything looks OK now. The workflow is clear: the new user can get their password via the reset page and then go through with e-mail verification, etc. [*] I had meanwhile disabled unused apps to reduce attack surface and noise. Cheers, -- Marco On 2025-08-29 19:42, Stephen J. Turnbull wrote: > ^m'e via Mailman-users writes: > > > I migrated form MM2.1 to MM3.3.10 on Debian Trixie (mariadb > > backend) -- I know that's a bit unorthodox to ask here for help on > > a non venv-based installation, > > We appreciate your courtesy, but this is inaccurate. If you install > a distro-packaged Mailman and it doesn't do the basic stuff such as > "start" or "respond to web requests" out of the box, that's a distro > problem. (That includes any features missing because of the > inevitable lag in distro packaging.) > > On the other hand, if you have a misconception (see Issue #1) or if > Mailman is basically working but doing a particular weird thing (in > your opinion, and that's Issue #2), asking here is the right thing to > do. Distro maintainers are frequently experts in packaging but > ordinary users of their package without expertise in troubleshooting > the package, and usually zero interest in educating users. That is > what we are here for! > > And, obviously, "real" bugs may manifest first in a distro package. > > > but hopefully I'll first gain a bit of insight of MM3 in order to > > formulate a more precise request to Debian maintainers. > > I don't think these are Mailman issues, and quite likely they're not > Debian issues. > > > ## Issue #1. > > > > A newly invited (from Postorius mass subscription page) and > > confirmed user doesn't get any password in their invitation/welcome > > e-mail. > > The invitation/welcome emails usually don't know if the user is > verified, and they are otherwise not personalized, so sending a > one-time password (OTP) at that time would be a lot more complicated > than it's worth. Also, many users may prefer to NOT set a password at > all. For example, if you configure the Gmail socialauth plugin, a > Gmail user can log in without doing the OTP dance. (I think we still > require the dance to verify the address, because socialauth is hard > and the burden is small. And if 'confirm' is set in the list > preferences, you have to either log in to Postorius to subscribe, or > do the dance for an email subscription.) > > Because Mailman 3 has a model of a user with multiple addresses and > subscriptions, the burden of using the reset password dance for the > initial setting of a password is considered very small (it usually is > done once during the user's association with the Mailman instance, if > at all). So that's the way we do it. > > > ## Issue #2 > > > > Anyway, if that new user asks for a password reset on Postorius they get > > > > "Server error > > An error occurred while processing your request." > > This appears to be an MTA misconfiguration, either in Mailman or > possibly in the MTA: > > > File "/usr/lib/python3.13/smtplib.py", line 861, in sendmail > > self.ehlo_or_helo_if_needed() > > Mailman tried to connect to a mail server. > > > File "/usr/lib/python3.13/smtplib.py", line 365, in send > > raise SMTPServerDisconnected('please run connect() first') > > smtplib.SMTPServerDisconnected: please run connect() first > > It failed. > > Twp possibilities off hand: (1) The server expects authenticated > and/or encrypted email (SASL and TLS), but Mailman is not configured > to do that. (2) A typo in the server IP or hostname. > > There are all sorts of other reasons why a server might refuse a > connection, but we'd need a lot more information to diagnose. > > Steve > ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pgp-keys Name: OpenPGP_0xC366FCF67CDBD9F9.asc

2 months

Re: Postorius no connection to REST API

by Guillermo Hernandez (Oldno7)

On 9/8/21 17:56, Richard Rosner wrote: >> I don't use uwsgi and know little about it so I don't know what the Unix > domain socket /run/mailman3-web/uwsgi.sock connection is for, but this > appears to be some miscunfiguration between apache and uwsgi. > Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via > tcp port 8000 and uwsgi is configured with > [uwsgi] > uwsgi-socket = 0.0.0.0:8000 I have the apache24 and uwsgi working together. I did this way: For the apache24 part I decided to use the mod-wsgi (and uswgi binary). did a pip install mod-wsgi (with "mod_wsgi-express module-config" it shows the conf needed.) after that a pip install uwsgi In my systems the mailman3 files are located at /usr/local/mailman3, and the apache24 config path is /usr/local/etc/apache24 (I'm running FreeBSD) - Included these lines in the "loadmodule" part of /usr/local/etc/apache24/httpd.conf Watch out the correct path of your python ##### begin of added lines LoadModule wsgi_module "/usr/local/lib/python3.7/site-packages/mod_wsgi/server/mod_wsgi-py37.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty ##### end of added lines - Added this line in the correct places of my /usr/local/etc/apache24/extra/httpd-vhosts.conf (in the listen 80 and 443 servers) Include "/usr/local/mailman3/apache24.uwsgi.conf" ( my apache24.uwsgi.conf is copied below) Then all you have to do is a - service apache24 restart and initiate the uwsgi with a /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & (beware the "&" backgrounding it) ####### start of /usr/local/mailman3/uwsgi.ini # uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # Move to the directory wher the django files are. chdir = /usr/local/mailman3/ # Use the wsgi file provided with the django project. wsgi-file = wsgi.py # Setup default number of processes and threads per process. master = true process = 2 threads = 2 # Drop privielges and don't run as root. uid = www gid = www # Setup the django_q related worker processes. attach-daemon = ./manage.py qcluster # Setup the request log. req-logger = file://usr/local/mailman3/logs/uwsgi.log # Log cron seperately. logger = cron file://usr/local/mailman3/logs/uwsgi-cron.log log-route = cron uwsgi-cron # Log qcluster commands seperately. logger = qcluster file://usr/local/mailman3/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file://usr/local/mailman3/logs/uwsgi-error.log ####### end of /usr/local/mailman3/uwsgi.ini ####### start of /usr/local/mailman3/apache24.uwsgi.conf Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico Alias /static /usr/local/mailman3/static ######### # for hyperkitty Alias /static/admin /usr/local/mailman3/static/admin Alias /static/CACHE /usr/local/mailman3/static/CACHE Alias /static/django_extensions /usr/local/mailman3/static/django_extensions Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 Alias /static/rest_framework /usr/local/mailman3/static/rest_framework # for postorius Alias /static/postorius /usr/local/mailman3/static/postorius Alias /static/archives /usr/local/mailman3/static/postorius ##### ###ErrorLog /var/log/httpd/hyperkitty_error.log ###CustomLog /var/log/httpd/hyperkitty_access.log combined <Directory "/usr/local/mailman3/static"> Require all granted </Directory> ######## end of /usr/local/mailman3/apache24.uwsgi.conf

4 years, 2 months

Re: postorius configuration of the from-part

by Mark Sapiro

On 11/12/19 2:27 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > can someone give me an advice how I can configure in the > postorius-menues the view of the from-part of my list-member like in > this mailinglist: > > Wolfgang Bock_via Mailman-users_ <mailman-users(a)mailman3.org> The above is the result of Settings -> DMARC Mitigatations -> DMARC mitigation action = "Replace From: with list address" You can apply that to only messages From: a domain the publishes a DMARC policy of reject or quarantine or to all messages depending on DMARC Mitigate unconditionally. > case 1 reply goes to the list or to the member > case 2 reply goes only to the list The DMARC Mitigatations settings are independent of the various reply settings on the Alter Messages tab. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Postorius endless loading on Sign in / Register then "Internal Server Error"

by Jacob Bargery

Pre-cursor, I am in a new position to learn on the go and new to Linux but have been tasked with setting up a List Serv and they wanted Mailman 3 with Postorius and HyperKitty. Running on Ubuntu 20.04 LTS using Postfix and MySQL. I can open up the initial pages. With no Lists created yet. I can open up Register, Login, and Forgot Password but when I submit anything it spins the loading icon for a long time then reads" "Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Apache/2.4.41 (Ubuntu) Server at groups.smccme.edu Port 80" If I try to re-navigate to the page, nothing loads. If I reboot the server, I can get to the same point again with the same problem. Performed a log tail on mailman-web.log and got this and then nothing happens after this no matter how long I wait: 15:18:31 [Q] INFO Q Cluster-1686 starting. 15:18:31 [Q] INFO Process-1:1 ready for work at 1932 15:18:31 [Q] INFO Process-1:3 monitoring at 1934 15:18:31 [Q] INFO Process-1 guarding cluster at 1931 15:18:31 [Q] INFO Q Cluster-1686 running. 15:18:31 [Q] INFO Process-1:2 ready for work at 1933 15:18:31 [Q] INFO Process-1:4 pushing tasks at 1935 [pid: 1683|app: 0|req: 1/1] 10.212.134.135 () {56 vars in 1124 bytes} [Tue Jun 9 15:20:48 2020] GET /mailman3 => generated 0 bytes in 545 msecs (HTTP/1.1 301) 6 headers in 213 bytes (1 switches on core 0) [pid: 1683|app: 0|req: 2/2] 10.212.134.135 () {56 vars in 1174 bytes} [Tue Jun 9 15:20:49 2020] GET /mailman3/postorius/lists/ => generated 3927 bytes in 378 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 1) [pid: 1683|app: 0|req: 3/3] 10.212.134.135 () {58 vars in 1240 bytes} [Tue Jun 9 15:21:02 2020] GET /mailman3/postorius/lists/ => generated 3927 bytes in 63 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 0) [pid: 1683|app: 0|req: 4/4] 10.212.134.135 () {58 vars in 1225 bytes} [Tue Jun 9 15:21:05 2020] GET /mailman3/hyperkitty/ => generated 11265 bytes in 120 msecs (HTTP/1.1 200) 5 headers in 164 bytes (2 switches on core 1) [pid: 1683|app: 0|req: 5/5] 10.212.134.135 () {58 vars in 1235 bytes} [Tue Jun 9 15:21:10 2020] GET /mailman3/postorius/lists/ => generated 3927 bytes in 77 msecs (HTTP/1.1 200) 5 headers in 163 bytes (2 switches on core 0) [pid: 1683|app: 0|req: 6/6] 10.212.134.135 () {58 vars in 1303 bytes} [Tue Jun 9 15:21:14 2020] GET /mailman3/accounts/signup/?next=/mailman3/postorius/lists/ => generated 8958 bytes in 74 msecs (HTTP/1.1 200) 6 headers in 331 bytes (2 switches on core 1) [pid: 1683|app: 0|req: 7/7] 10.212.134.135 () {68 vars in 1502 bytes} [Tue Jun 9 15:21:54 2020] POST /mailman3/accounts/signup/ => generated 9132 bytes in 96 msecs (HTTP/1.1 200) 6 headers in 331 bytes (1 switches on core 0) [pid: 1683|app: 0|req: 8/8] 10.212.134.135 () {60 vars in 1389 bytes} [Tue Jun 9 15:22:03 2020] GET /mailman3/accounts/login/?next=/mailman3/accounts/signup/ => generated 9128 bytes in 43 msecs (HTTP/1.1 200) 6 headers in 331 bytes (2 switches on core 1) [pid: 1683|app: 0|req: 9/9] 10.212.134.135 () {60 vars in 1384 bytes} [Tue Jun 9 15:22:04 2020] GET /mailman3/accounts/password/reset/ => generated 7749 bytes in 17 msecs (HTTP/1.1 200) 6 headers in 331 bytes (1 switches on core 0) This is a traceback I could find from another attempt: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 702, in list_index lists = paginate( File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py", line 71, in paginate objects = paginator.page(page_num) File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py", line 46, in page number = self.validate_number(number) File "/usr/lib/python3/dist-packages/django/core/paginator.py", line 48, in validate_number if number > self.num_pages: File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django/core/paginator.py", line 97, in num_pages if self.count == 0 and not self.allow_empty_first_page: File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py", line 56, in count return self.function(count=0, page=1).total_size File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 699, in _get_list_page return client.get_list_page( File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 177, in get_list_page return Page(self._connection, url, MailingList, count, page) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/usr/lib/python3/dist-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API Any help would be greatly appreciated. Definitely in over my head on this one. Thanks.

5 years, 4 months

Re: error changed after restart (was: KeyError: 'get_requests_count' after an upgrade)

by Abhilash Raj

On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I restarted de server and the error changed. Now the log shows > "KeyError: 'subscription_mode'": Did you also restart Mailman Core after the upgrade? > > ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server > Error: /mailman3/mailman3/lists/name_and_domain.of.the.list > Traceback (most recent call last): > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 119, in __getattr__ > return self._get(name) > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 86, in _get > raise KeyError(key) > KeyError: 'subscription_mode' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", > line 34, in inner > response = get_response(request) > File > "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", > line 115, in _get_response > response = self.process_exception_by_middleware(e, request) > File > "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", > line 113, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", > line 71, in view > return self.dispatch(request, *args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", > line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", > line 97, in dispatch > return handler(request, *args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line > 295, in get > member.subscription_mode == > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 124, in __getattr__ > self.__class__.__name__, name)) > AttributeError: 'Member' object has no attribute 'subscription_mode' > *********************** > some info about the installed versions via pip list: > pip list | grep django > django-allauth 0.44.0 > django-appconf 1.0.4 > django-compressor 2.4 > django-extensions 3.1.0 > django-gravatar2 1.4.4 > django-haystack 3.0 > django-mailman3 1.3.5 > django-picklefield 3.0.1 > django-q 1.3.4 > djangorestframework 3.12.2 > > pip list | grep mailman > django-mailman3 1.3.5 > mailman 3.3.3 > mailman-hyperkitty 1.1.0 > mailmanclient 3.3.2 > > pip list | grep postorius > postorius 1.3.4 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I've just upgrade mailman 3 installation following Mr. Sapiro advice: > > did a > > > > pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient > > mailman-hyperkitty postorius > > > > I did a "python3 manage.py migrate" after, too. > > > > And all seemed to run well. > > > > All the lists showed in postorius via web, but when I try to accesss > > into one of them the browser shows an error. > > > > In the log you can see: > > > > *-*-*-*-*-*-* > > > > Traceback (most recent call last): > > File > > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > > line 119, in __getattr__ > > return self._get(name) > > File > > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > > line 86, in _get > > raise KeyError(key) > > KeyError: 'get_requests_count' > > > > ... (And after all the traceback lines) > > > > AttributeError: 'MailingList' object has no attribute > > 'get_requests_count' > > > > *-*-*-*-*-*-*-* > > > > The lists seem to be distributing messeages well.. but I cannot acces > > via web administration (django/postorius) > > > > Can anyone point me in the right direction to solve this, please? > > > > _______________________________________________ > > 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/ > > > _______________________________________________ > 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, 8 months

Mailman3-web/Postorius behind Lighttpd

by Élodie BOSSIER

Hi, I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from packages : #dpkg -l | grep mailman ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty ii python3-mailmanclient 3.3.2-1 all Python bindings for Mailman3 REST API (Python 3 version) I can access from localhost to http://127.0.0.1:8000/ which move me correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be correct. But 127.0.0.1:8000 listen only in localhost : #netstat -tanpu | grep 8000 tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 626175/python3 So I try to use my lighttpd as proxy as recommanded with this config : > scgi.protocol = "uwsgi" > scgi.server = ( > "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => > "disable" )), > ) but it's return me a "502 Bad Gateway". I see nothing on there logs : - /var/log/lighttpd/error.log - /var/log/mailman3/web/error.log - /var/log/mailman3/web/access.log But on the file : /var/log/mailman3/web/mailman-web.log I can see that : > QUERY_STRING > REQUEST_URI/postorius/lists/REDIRECT_STATUS200 > SCRIPT_NAME" 400 - I don't know what I'm doing wrong ... There is a way to solve it with lighttpd or bind the port 8000 to 0.0.0.0 instead 127.0.0.1 (which is not recommanded) ? Thank you in advance. Best regards, Elodie

3 years, 8 months

Mailman-users search results for query "Postorius"