Search results for "Postorius" - Mailman-users

Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Mon, Dec 26, 2022 at 5:07 PM Eggert Ehmke <eggert(a)eehmke.de> wrote: > Ok, > > I hope this is readable. I just copíed the content of some files into the > pastebin, don't know if it is possible to post tar.gz there. > https://pastebin.ubuntu.com/p/mmRJJwKDc3/ > > Just tell me if this works for you, and when something is missing. > Most of the settings are copied from some other sites and just adjusted > for my > needs. > Good luck! So it seems your WSGIDaemonProcess is defined somewhere outside the VHOST, right? Or it wasn't necessary? And what does your urls.py look like? My setup is PUBLIC for everyone so I will not hide the domain name :-) In my setup, MM3 is installed in /opt/mailman/mm/. and mod_wsgi is enabled in Apache. I am running uwsgi on a TCP socket, not unix socket. The whole of my *VHOST:* <CUT> WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 user=mailman group=mailman python-path=/opt/mailman/mm:/opt/mailman/mm/venv/lib/python3.9/site-packages:/opt/mailman/mm/venv/lib/python3.9 python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var WSGIRestrictSignal Off <VirtualHost *:443> ServerName mm3-lists.kictanet.or.ke SSLEngine on SSLCertificateFile "/usr/local/etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/cert.pem" SSLCertificateKeyFile "/usr/local/etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/privkey.pem" SSLCertificateChainFile "/usr/local/etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/chain.pem" CustomLog /var/log/mm3-lists-access.log combined ErrorLog /var/log/mm3-lists-error.log LogLevel info Alias /favicon.ico /opt/mailman/mm/static/hyperkitty/img/favicon.ico Alias /static "/opt/mailman/mm/static" <Directory "/opt/mailman/mm/static"> Require all granted </Directory> WSGIScriptAlias / /opt/mailman/mm/wsgi.py <Directory "/opt/mailman/mm/"> <Files wsgi.py> Order deny,allow Allow from all Require all granted </Files> WSGIProcessGroup mailman-web </Directory> </VirtualHost> </CUT> *2. uwsgi.ini:* <CUT> [uwsgi] http-socket = 127.0.0.1:8000 pidfile = /opt/mailman/mm/var/uwsgi.pid chdir = /opt/mailman/mm/ virtualenv = /opt/mailman/mm/venv/ module=mailman_web.wsgi:application env =PYTHONPATH=/opt/mailman/mm/ env =DJANGO_SETTINGS_MODULE=settings master = true process = 2 threads = 2 attach-daemon = /opt/mailman/mm/venv/bin/mailman-web qcluster req-logger = file:/opt/mailman/mm/var/logs/uwsgi.log logger = qcluster file:/opt/mailman/mm/var/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons logger = cron file://opt/mailman/mm/var/logs/uwsgi-cron.log log-route = cron uwsgi-cron logger = file:/opt/mailman/mm/var/logs/uwsgi-error.log uid = mailman gid = mailman </CUT> *3. uwsgi - *Running supervised (supervisord): <CUT> [program:uwsgi] directory=/opt/mailman/mm/ environment=PYTHONPATH=/opt/mailman/mm/ command=/usr/bin/su -m mailman -c '/opt/mailman/mm/venv/bin/uwsgi --ini /opt/mailman/mm/uwsgi.ini' 2>&1 | logger -t uwsgi autostart=true autorestart=true user=mailman group=mailman stopasgroup=true killasgroup=true </CUT> *4. urls.py*: <CUT> from django.conf.urls import include from django.urls import re_path from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView from django_mailman3.views.profile import delete_account, user_profile urlpatterns = [ re_path(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), re_path(r'^postorius/', include('postorius.urls')), re_path(r'^hyperkitty/', include('hyperkitty.urls')), re_path(r'^user-profile/delete$', delete_account, name='mm_user_account_delete'), re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), re_path(r'^accounts/', include('allauth.urls')), re_path(r'^admin/', admin.site.urls), re_path(r'^mm/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), ] </CUT> And that's pretty much what I am using on my FreeBSD server. PS: Possible to bottom-post instead of top-posting? :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

1 year, 11 months

Re: Mailman not able to process "big" requests

by Jonas Felber

Thank you for your support, I got informed that we are now able to send out emails again. The problem was that the crashes we got while mass subscribing led to database corruptions. (From what I know, the problem was on our side, as we kubernetes did not properly restore some files after restarting so the database got corrupted (apparently we are running now a cleanup script on each restart)) There are still some problems, but I just wanted to send out a quick update. Thanks for your support, Jonas Jonas Felber <jonas.felber(a)vis.ethz.ch> Aktuar & CTF Präsident VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch > On 24 Apr 2018, at 17:21, Darren Smith <silas.crutherton(a)gmail.com> wrote: > > Our installation at https://lists.rootsweb.ancestry.com has around 33,000 > lists and somewhere around 1.5 million members. We have lists with 5,000+ > members. > > Note that I haven't tried any mass subscriptions. When we upgraded from > mailman 2 to mailman 3, we used the old .pck files and ran the import on > each of the lists. It did take about 6 weeks to do the full import all > 33,000 lists. I'm not joking. > > As for sending messages - there isn't any problem sending that many > messages out, but then we are also not trying to subscribe list members at > the time. We are, though, in the process of importing the old archives from > our old mailman 2 system. This doesn't seem to affect the rest of the > system. > > We have seen some inefficiencies in the new system, such as the front page > of postorius - loading all of the information for 200 lists (if the user > set the "lists per page" to 200) was bringing down the system. We have our > own metadata system to be able to search for lists by state/region/surname > (ours is a genealogy mailing list system), so we had to replace the front > page with our own "find a list" functionality. > > The other main problem was the page where a user can see what lists they > subscribe to. That page was also a denial of service if the user had > several hundred lists they are subscribed to. And for a genealogy mailing > list system, this is common. > > We have actually ended up creating our own API layer (only accessible on > the local machine) and make certain calls to it for the most painful of the > issues. One of these days (when we get a moment to breathe) we are going to > post some of our changes to the project so that we can ditch our own API > and just use the internal REST API. > > To be fair, the inefficiencies are not necessarily with mailman or the rest > API itself - but with Postorius making hundreds of calls to load a single > page. Though if the API supported loading multiple lists at once instead of > having to load them serially, that might help as well. > > So while we have not seen any timeout issues on the call to mass subscribe > users, we HAVE found several other calls that are effectively a denial of > service and have gotten around them ourselves, with plans to contribute to > the project in the near future. > > -Darren > > >> On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 04/24/2018 12:36 AM, Abhilash Raj wrote: >>> On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: >> >>>> We also have a problem with sending out emails to "large" (>50) groups, >>>> as they seem to not getting sent out at all. Do you have any idea what >>>> the problem here could be? >>> >>> Which MTA are you using? What do you see in mailman's logs and MTA's >> logs? >>> >>> I haven't seen this kind of problem before with Mailman 3. This very >> list is hosted using Mailman 3 and I believe has more than 50 subscribers. >> >> >> Nor have I seen this issue. This list currently has 158 non-digest >> members. There are several @python.org Mailman 3 lists with over 100 >> non-digest members including the active yt-users(a)python.org list with >> 301 members, and I have gotten no reports of an issue like this. >> >> Also, there are over 600 lists at <https://lists.fedoraproject.org/>, >> and I don't think this is an issue there either. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 7 months

Re: Modify approval email

by Odhiambo Washington

On Fri, Sep 15, 2023 at 5:33 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > pau.baiges(a)csuc.cat writes: > > > Is there a way to modify the email that is sent by default to list > > owners when a non-list member sends email to the list? > > Yes. As list owner (or site admin) in Postorius go to Templates, and > click on "New Template". Select list:admin:action:post from the > drop-down menu to the right of "Name". Copy the current message > (site-packages/mailman/templates/en/list:admin:action:post.txt is the > original, but do not edit this -- it will be overwritten on upgrades) > to the text box and edit to taste. Unfortunately there is no "web > site" variable but typically that is the same for all lists, so adding > > https://your.host.here/mailman3/lists/$list_id/held_messages > > in some appropriate place probably does what you want. > > There is no way to indicate that this is a link because these messages > are plain text. However, most mail clients will turn a URL into a > link. If your moderators are not so lucky, try wrapping it with > > <URL:https://your.host.here/mailman3/lists/$list_id/held_messages> > > or even the usual HTML: > > <a href="https://your.host.here/mailman3/lists/$list_id/held_messages"> > Moderation Page > </a> > > One of those may help. > Also, you can take a look at this documentation: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- 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]

1 year, 2 months

Re: Can login at /admin, but cannot login at the account/login page.

by Mark Sapiro

On 8/14/21 9:34 PM, Stephen J. Turnbull wrote: > I'm sorry, I'm in a "second vaccination" fog at the moment (mending > but concentration lasts only about 10 minutes), so I'll answer what I > know offhand since Abhilash is busy and Mark is probably offline for > vacation by now. Not quite, but very soon. > pabsta(a)gmail.com writes: > > > However, if logout and attempt to login from the postorius website, > > I get a « 502 bad gateway » error after roughly 30 seconds. The > > logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech > > free" error message > > I would guess this is also just a connection drop because it doesn't > receive the expected response within timeout. I'm sure that's right. > > and the nginx error logs just show a connection drop: > > > > 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: > > [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" > a > I see in the above `upstream: "http://127.0.0.1:8006/accounts/login/",` but in your settings ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" I suspect you may be getting a redirect from http to https which is losing POST data and you need to change proxy_pass http://127.0.0.1:8006; in your nginx configuration to proxy_pass https://127.0.0.1:8006; or set ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Re: Where to find disabled members?

by Bill Oliver

On Mon, 2024-11-04 at 22:36 -0800, Mark Sapiro wrote: > On 11/4/24 19:28, Bill Oliver wrote: > > > > a) See who is disabled, and > > b) un-disable them by hand > > > > or... do I just have to wait seven days for them to automatically > > get > > un-disabled? > > They do not get automatically re-enabled ever the user or you has to > manually re-enable delivery. > > For an individual user, in Postorius you can click the user in the > members list and see their delivery status and reset it. > > To deal with the whole list membership for a list, you can do > ``` > $ shell -l list(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 list(a)example.com mailing list > >>> for member in m.members.members: > ... if member.delivery_status == DeliveryStatus.by_bounces: > ... member.preferences.delivery_status = > DeliveryStatus.enabled > ... > >>> commit() > >>> > ``` > If you just want to list them > ``` > >>> for member in m.members.members: > ... if member.delivery_status == DeliveryStatus.by_bounces: > ... print(member) > ... > >>>``` > Thank you. It worked like magic. Looks like I've got some learnin' to do with respect to the cli. I've never played with it beyond the commands indicated for installation. It looks like a great way to manage things. I much prefer a cli to gui for most of this kind of thing. billo

3 weeks, 1 day

IsADirectoryError: [Errno 21] Is a directory: '/usr/local/lib/python3.7/site-packages/mailman/templates'

by sunil soprey

Has anyone encountered this error? I pulled the latest mailman suite (versions below), and facing this error in two places * mass subscription add of users -> Click on mass-subscription for list, enter email Django 2.2.11 django-allauth 0.41.0 django-appconf 1.0.3 django-ca 1.15.0 django-compressor 2.4 django-extensions 2.2.8 django-gravatar2 1.4.4 django-gunicorn 0.1.1 django-haystack 2.8.1 django-health-check 3.12.1 django-mailman3 1.3.2 django-object-actions 2.0.0 django-picklefield 2.1.1 django-prometheus 2.0.0 django-q 1.2.1 django-redis 4.11.0 django-redis-cache 2.1.0 django-rest-auth 0.9.5 django-saml2-auth 2.2.1 djangorestframework 3.11.0 djangorestframework-jwt 1.11.0 python3 -V Python 3.7.6 django-mailman3 1.3.2 HyperKitty 1.3.2 mailman 3.3.0 mailman-hyperkitty 1.1.0 mailmanclient 3.3.0 postorius 1.3.2 sADirectoryError: [Errno 21] Is a directory: '/usr/local/lib/python3.7/site-packages/mailman/templates' [2020-03-17 03:56:54 +0000] [4220] [ERROR] Socket error processing request. Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 134, in handle self.handle_request(listener, req, client, addr) File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 190, in andle_request util.reraise(*sys.exc_info()) File "/usr/local/lib/python3.7/site-packages/gunicorn/util.py", line 625, in reraise raise value File "/usr/local/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 175, in andle_request respiter = self.wsgi(environ, resp.start_response) File "/usr/local/lib/python3.7/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.7/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/usr/local/lib/python3.7/site-packages/mailman/rest/members.py", line 266, in on_post pre_approved=pre_approved) File "/usr/local/lib/python3.7/site-packages/mailman/app/subscriptions.py", line 523, in register list(workflow) File "/usr/local/lib/python3.7/site-packages/mailman/app/workflow.py", line 69, in __next__ return step()

4 years, 8 months

Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

Hello everybody, I successfully resolved the owner:group issue and I am no longer getting the permission errors. Basically, I had to set the ownership:group to mailman:www-data and make the group permissions rw for everything to work successfully with Apache and Mailman3. As I mentioned earlier, I have mailman (core) now working, however, I cannot seem to get the web interface to work. I believe that I have gotten rid of all of the permissions issues and the mailman3-web service starts and stops without error. However, when I use a browser to go to the web interface, I get File Not Found errors in the browser window and my Apache2 logs say: 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /mailman3/postorius/lists/members.georgiajets.org/ HTTP/1.1" 404 282 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /favicon.ico HTTP/1.1" 200 318 So, I get File Not Found error 404 for the web page but the favicon.ico file appears to be found successfully. Therefore, I suspect that my apache configuration file for mailman3 may be at the source of my problems and specifically the alias for the static directory. Here is my apache configuration file: Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! # ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> By the way, this is the Apache configuration file that the Debian package installed with my initial installation. Does anybody see any problems in my Apache configuration file that could be causing my problems? Do you see or suspect any other issues? Thanks, Gordon

2 years, 9 months

Re: Strange error in uwsgi-error.log

by Derek Lambert

Brian, I'd presume it's from something recent since you only started seeing it after updating. Do you recall what the prior version was? To drop the constraint on postgres I did: alter table hyperkitty_mailinglist alter column description drop not null; That's pretty standard SQL so I'd imagine it'd work on other platforms. After dropping it the error message is no longer logged, but none of the maillists have descriptions in HK. To add the constraint back after the bug is fixed: alter table hyperkitty_mailinglist alter column description set not null; Derek On 2/6/19, 4:23 PM, "brian(a)emwd.com" <brian(a)emwd.com> wrote: Derek Lambert wrote: > Brian, > > When I was seeing this, new lists weren't showing in HyperKitty. > > I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from > functioning. I had to drop the constraint to get the lists in. None of them have a > description now. > > Was this working for you in the past? If so, did you do any updates recently? > > Derek Lambert Hi Derek, Actually you are right. None of my new lists are showing in https://urldefense.proofpoint.com/v2/url?u=http-3A__mailmam3domain_hyperkit…. However if you go directly to each lists' archives then you can access their archives via HK. I also recently did an update when Postorius 1.2.3 came out. I am using the Docker images for my Mailman 3 install. How do you drop the constraint? DId that fix the error message? So this seems to be a new bug that was introduced in the recent updates? It's weird because I know Hyperkitty was not touched. Brian _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mai…

5 years, 9 months

Re: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

On 5/18/22 10:48, dancab(a)caltech.edu wrote: > Mark, > > We have a question related to this thread. We use LDAP for authentication. It seems that the name attributes can only be edited via the LDAP synchronization when a user logs in for the first time and thus creates their user account. > > But what about list members that are not in LDAP? What happens behind the scenes when a member is added to a list? The user's display name is set when the user record is initially created. Assuming someone who is initially unknown, this can happen when the unknown user signs up for a web account, when the unknown user subscribes to a list via the web UI or when the unknown user is mass subscribed to a list. > Manually subscribing members has different results with our configuration. > > I've seen the manually entered name show up as "None" <foobar(a)caltech.edu>. There was a pre-existing user with that address and no display name. > I've seen the entry be accepted as is, eg. "John Doe" <jdoe(a)example.com> > I've seen the name entry be ignored but the email accepted eg. "Foo Bar" <foobar(a)caltech.edu> is subscribed but the member list only shows <foobar(a)caltech.edu> The display name has nothing to do with message acceptance. That is based only on the address. In Postorius >=1.3.6 there is a `Users` selection at the top of most pages if you are logged in as a superuser. This allows management of users including their display name. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[SOLVED] Re: how to unhold a hold message from a nonmmeber in hold list.

by Guillermo Hernandez (Oldno7)

El 21/4/23 a las 11:03, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > 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 :-) > Well... I found you where right. Messing with the CLI seems a nightmare to me. The problem with the UI seems solved. What I finally have done: Detected that the module "asgiref" was in a different version that the server (with all the same config) that is working. pip upgraded it. This didn't work, but it raised new error messages (about hyperkitty parsing messages) Installed pip-review and upgraded ALL python modules with pip-review --local --interactive (Re)upgraded all mailman3 packages with pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi Restarted apache24 And then all begun to work. Thanks a lot for your advising and help. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

1 year, 7 months

Mailman-users search results for query "Postorius"