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

[MM3-users] Re: restricting public lists per virtual domain

by David Newman

On 12/16/21 2:40 PM, Mark Sapiro wrote: > On 12/16/21 12:25 PM, David Newman wrote: >> Can lists set to be viewable on the index page be limited to the >> virtual domain they are a part of? >> > > > Have you set > > FILTER_VHOST = True > > in your Django settings? I had not, and this was the variable I was looking for. Thank you! This works for HyperKitty and works partially > for Postorius. For Postorius, it doesn't work if there are multiple > domains with different email hosts which have the visiting host as their > web host[1] but works otherwise. > > See https://gitlab.com/mailman/postorius/-/merge_requests/500 and > https://gitlab.com/mailman/postorius/-/issues/394 > > In your case, as long as the domains lists.dom1.tld and lists.dom2.tld > have different mail hosts, this should work. > > [1] An example of what doesn't work in Postorius is the following: > > Visit https://lists.example.com/mailman3/lists. If there are 2 domains > with web host lists.example.com, one of which has mail host example.com > and the other has mail host lists.example.com, all lists will be shown > regardless of domain. On the other hand, if all the domains with web > host lists.example.com have the same email host, say example.com, then > only lists with email host example.com will be shown. Awhile back Stephen Turnbull suggested a terminology guide that included an MM3-specific definition of FQDNs. Also in an MM3 context, I think it would be useful to distinguish between mail hosts and web hosts and domains (all in the general Internet sense) and mail domains and sites (in the MM3/Django/Postorious/Hyperkitty sense). Not sure I fully understand these distinctions yet, but I can take a crack at it. dn

4 years, 1 month

[MM3-users] Re: translating templates

by Guillermo Hernandez (Oldno7)

On 16/2/21 22:47, Mark Sapiro wrote: > On 2/16/21 2:59 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> /usr/local/lib/python3.7/site-packages/mailman # ls templates/es >> domain:admin:notice:new-list.txt list:member:regular:header.txt >> help.txt list:user:action:invite.txt >> list:admin:action:post.txt list:user:action:subscribe.txt >> list:admin:action:subscribe.txt list:user:action:unsubscribe.txt >> list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt >> list:admin:notice:disable.txt list:user:notice:hold.txt >> list:admin:notice:removal.txt list:user:notice:no-more-today.txt >> list:admin:notice:subscribe.txt list:user:notice:post.txt >> list:admin:notice:unrecognized.txt list:user:notice:probe.txt >> list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt >> list:member:digest:header.txt list:user:notice:rejected.txt >> list:member:digest:masthead.txt list:user:notice:warning.txt >> list:member:generic:footer.txt list:user:notice:welcome.txt >> >> But mailman isn't aware of them (I restarted the server). May I have to >> execute some process as "compilemessages" to mailman be capable to use >> them? Now mailman is using the "en" templates for sure. > Does Mailman have permission to search the templates/es directory and > read the templates? They have exactly the same permissions that the other templates directories. > Are there overriding templates in Mailman's > var/templates/ directory? Not at all. > > Are you sure your tests access the templates in a Spanish language > context? Yes, I think so, but it could be that I'm missing something here. I double check this tomorrow as for your answer It seems there is no ulterior process as with messages. Anyway, I could just substitute all the en templates, but it's not the way to maintain language flexibility, you know :) Thanks for your answer P.S.: anyway, I did a merge request in gitlab as you advised. > >

4 years, 11 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 29 jan 2024, om 18:29 heeft Mark Sapiro <mark(a)msapiro.net> het volgende geschreven: > On 1/29/24 03:09, Marco van Tol wrote: >> Right now I’m back at the original issue as I see no other solution than to go back to whoosh. >> Thanks! >> Marco van Tol >> Paste: >> ---- >> Indexing 194620 emails >> [ERROR/MainProcess] Failed indexing 156001 - 157000 (retry 5/5): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… (pid 32): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… > > > I'm not sure why the patch you are using doesn't avoid this, but you could try the other patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> instead. If that fails, you could always find the offending message in the database maybe with a query like > ``` > SELECT * FROM hyperkitty_email Where subject LIKE 'http://www.google.com/url?q=\%68\%74\%74%'; > ``` > and modify or delete it - it's probably spam anyway. I tried the other patch, which looked very promising until something that had come in over SMTP some day threw a spanner in the wheels: ``` [ERROR/MainProcess] Failed indexing 287001 - 288000 (retry 5/5): Term too long (> 245): XTEXTº@[åeèúp¢i*h{õimô;]>ò&žôyþiýã#dzç8"¹ë= ;æmyš€vqe.âés:æä>üzúõœ'âú·ž[]kzñ-µ€3æfdñù£8çô<bœkkñ/ãžæjïw¿òþp-ùšã7/'ûvksqé (pid 404): Term too long (> 245): XTEXTº@[ åeèúp¢i*h{õimô;]>ò&žôyþiýã#dzç8"¹ë=;æmyš€vqe.âés:æä>üzúõœ'âú·ž[]kzñ-µ€3æfdñù£8çô<bœkkñ/ãžæjïw¿òþp-ùšã7/' ûvksqé ``` I agree that this is very likely the result of some spam, but the main point is that something that comes in over SMTP shouldn’t cause manual work on the listserver side. I’ll try it with a maximum length of 122 which should never explode into more than 244 bytes, unless I overlook something. I really wish Xapian would have a reliable fix for this. Will keep you posted. Marco van Tol

1 year, 11 months

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Jim Popovitch

On Wed, 2021-03-24 at 14:00 -0400, Jim Popovitch via Mailman-users wrote: > On Wed, 2021-03-24 at 10:57 -0700, Mark Sapiro wrote: > > On 3/24/21 7:58 AM, Brian Carpenter wrote: > > > On 3/24/21 9:54 AM, Ralph Weber wrote: > > > > Comments received directly from one of the people who developed the > > > > AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively > > > > established that AWS Mailman is *not* intended to interact with AWS > > > > SES when receiving email messages > > > > > > I don't think there is a Mailman 4 and the person who is marketing his > > > services under that name is sending a confusing message to the public. > > > > Danil Smirnov owns both the mailman3.com and mailman4.com domains. > > Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". > > In response to our request, the following is included at the bottom of > > <https://mailman3.com/>;;: > > > > Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain > > used to coordinate development of the Mailman 3 free software suite. The > > Mailman 3 core developers are not involved with Mailman3.com, and cannot > > answer any questions or provide any support related to its operations. > > If you are looking for resources for development of the Mailman 3 free > > software suite, please see mailman3.org. > > > > Yes, this is all ripe for confusion ... > > Just to add, Danil also owns mailman2.com, and I own (and parked) > mailman2.org. Apologies to this list and Danil who has informed me that mailman2.com is not theirs. This of course means that there is another stakeholder out there somewhere.... ;) -Jim P.

4 years, 9 months

[MM3-users] Re: mailman admin (django) interface does not work anymore after deleting website example.com

by Abhilash Raj

On Sun, Mar 10, 2019, at 9:00 AM, Torge Riedel wrote: > Am 10.03.19 um 16:44 schrieb Mark Sapiro: > > On 3/10/19 8:18 AM, Torge Riedel wrote: > >> I deleted the existing "example.com" and added a new one > >> "lists.mydomain.de". > >> > >> Now the admin (django) interface always gives "An error occurred while > >> processing your request". After one of the first navigation clicks I saw > >> a message that "site with id 1 is missing". > > > > In your Django settings your have > > > > SITE_ID = 1 > > > > which pointed to the example.com domain you deleted. > > > > You need to override this in settings_local.py. Probably > > > > SITE_ID = 2 > > > > but if that doesn't work, try '0' > > > Ah, thank you Mark. That makes a kind of sense. I changed the database > directly to fix it. And renamed example.com to lists.mydomain.de. Now > the error is gone. > > I'm wondering why the initial database set up of postorius (?) adds > "example.com". Is there a way to directly add my domain instead? > Somewhere in settings_local.py? Django does that and there doesn't seem to be a way to override that to something else during initial migration. Or nothing I have found yet. Only way is to edit "example.com" to something you'd like or add another domain entry and change SITE_ID to point o that. > _______________________________________________ > 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)

6 years, 10 months

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

by Odhiambo Washington

On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 9:12 AM, Odhiambo Washington wrote: > > On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 7/26/20 3:15 AM, Odhiambo Washington wrote: > >> > >>> There is still some confusion on my part about the directives in the > file > >>> so allow me to seek some clarifications. > >>> > >>> The following are the contents of a file I have created and placed in > my > >>> Apache Includes/ directory. > >>> I was hoping that with it, I can now access http://lists.my.server/mm3 > >> and > >>> get the UI. > >>> > >>> <CUT> > >>> > >>> # Global section > >>> WSGIDaemonProcess mailman-web display-name=mailman-web > >>> maximum-requests=1000 umask=0002 user=mailman3 \ > >>> group=mailman3 > >>> > >> > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > >>> \ > >>> python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > >>> WSGIRestrictSignal Off > >>> > >>> <VirtualHost *:80> > >>> ServerName lists.my.server > >>> ServerAdmin odhiambo(a)gmail.com > >>> > >>> # (I'm not sure that WSGIRestrictSignal Off is required, but it was in > >> the > >>> # provided example so I kept it. I also made changes to > WSGIDaemonProcess > >>> # based on my own mod_wsgi experience elsewhere.) > >>> > >>> ErrorLog /var/log/myserver-error.log > >>> LogLevel debug > >>> > >>> # This goes in the VirtualHost block for the domain. > >>> > >>> # Mailman 3 stuff > >>> Alias /static "/var/spool/mailman-web/static" *<----- Where is this > >>> directory supposed to be and what/who creates it and with what > >> permissions?* > >> > >> > >> It is created/updated by the mailman-post-update script based on CONFDIR > >> and STATIC_DIR. > >> > > > > The fact that I have run the mailman-post-update script and these > > directories aren't created means there is a problem in my setup, yes? > > > If your mailman-post-update script is essentially the same as > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > and it ran successfully, it would have created opt/mailman/mm/static and > populated it. What was the output when you ran it? > > > Yes, I have these files: > > (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* > > -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 > > /opt/mailman/mm/settings.py > > -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 > > /opt/mailman/mm/settings_local.py > > > Is there an empty /opt/mailman/mm/__init__.py file? > No. root@gw:/usr/local/mailman # ls -al /opt/mailman/mm/ total 88 drwxr-xr-x 8 mailman3 wheel 512 Jul 26 14:55 . drwxr-xr-x 6 mailman3 wheel 512 Jul 26 18:38 .. drwxr-xr-x 8 root wheel 512 Jul 25 22:16 .sass-cache drwxr-xr-x 2 mailman3 wheel 512 Jul 26 16:35 __pycache__ drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:42 bin -rw-r--r-- 1 mailman3 wheel 248 Jul 25 14:37 gunicorn.conf -rw-r--r-- 1 mailman3 wheel 266 Jul 26 15:34 gunicorn.conf.py lrwxr-xr-x 1 mailman3 wheel 24 Jul 25 14:39 logs -> /opt/mailman/mm/var/logs -rw-r--r-- 1 mailman3 wheel 370 Jul 25 14:32 mailman-hyperkitty.cfg -rw-r--r-- 1 mailman3 wheel 1291 Jul 26 17:12 mailman.cfg -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 settings.py -rw-r--r-- 1 mailman3 wheel 15805 Jul 26 21:22 settings_local.py drwxr-xr-x 9 mailman3 wheel 512 Jul 25 22:16 static -rw-r--r-- 1 mailman3 wheel 1395 Jul 25 14:35 urls.py drwxr-xr-x 12 mailman3 wheel 512 Jul 26 19:30 var drwxr-xr-x 5 mailman3 wheel 512 Jul 26 17:11 venv -rw-r--r-- 1 mailman3 wheel 1170 Jul 26 11:39 wsgi.py > > > PS: I made my /opt/mailman to be owned by mailman3:wheel because of a > > confusion with the instructions at some point in the reading > > of some documentation previously (in my previous attempt last year!) and > > had noted that in my NOTES. I'll change this once things get clear for > me. > > Also, the fact that one of the init scripts > > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > > in your "reflection" page was calling sudo :) > > > It does `sudo -u $USER ...` so that it runs Mailman as the Mailman user > as it should. Have you set > > USER=mailman3 > in yours? > Yes. However, that also means the /opt/mailman should be owned by mailman3, right? So I wasn't quite mistaken. PS: There is the issue with qcluster, which doesn't seem to have been documented in details from your "experience". I see the configuration file and the init script, but not how to install it, or whether the procedure already installed it. Kindly clarify. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 5 months

[MM3-users] Re: Problem updating mailman

by Brian Carpenter

Mark Sapiro wrote: > On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't > > remember consciously > > installing that because it was never in the guide I followed (which is your > > own writeup). > > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update > > > > '[' False == False ']' > > mkdir -p /opt/mailman/mm/static > > /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > /opt/mailman/mm/bin/django-admin compress > > CommandError: An error occurred during rendering > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > > /bin/sh: sass: not found > > > > You can't just uninstall rubygem-sass. You have to replace it. Here's > one recipe for Ubuntu > cd /usr/local/lib > # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the > # appropriate version. > wget > https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5-... > sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz > sudo chmod -R o-w dart-sass > sudo ln -s dart-sass/sass /usr/local/bin/sass > rm dart-sass-1.32.5-linux-x64.tar.gz > Then you should see the command > sass --version > prints > 1.32.5 > Then, because dart-sass doesn't recognize the short form -t option for > --style, you have to edit your settings(_local).py and change > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > to > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass --style compressed {infile} {outfile}'), > ('text/x-sass', 'sass --style compressed {infile} {outfile}'), > ) I had to do a new installation of Mailman 3 with Postorius/Hyperkitty today and these directions were very helpful. Thank you, Mark.

4 years, 11 months

[MM3-users] Re: Template for Password Reset Email

by Mark

On 2024-11-18 01:38, Mark Sapiro wrote: > On 11/17/24 16:57, Mark wrote: >> >> I can see the French text for the "Password Reset Email" in the >> django.po file. And running the compilemessages command reports the >> "django.po" for French is okay and up to date. Should I be recompiling >> the ".mo" file? > > No, It's fine. The issue is the language context for this message has > nothing to do with any Mailman list's preferred language. > > Again, see > https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… > > If all the lists on your server are French, you could set > > LANGUAGE_CODE = 'fr' > > in your Django settings. Otherwise, the user's browser has to include > an Accept-Language: header specifying French as the most preferred > language in it's request. > > Also note the ordering of SessionMiddleware, LocaleMiddleware and > CommonMiddleware in the above doc. I have recently updated the various > places where we suggest or supply MIDDLEWARE settings, but you may > find that your settings have LocaleMiddleware after CommonMiddleware > and you should fix that. It's just the one list that is using French. Others are in English I've edited the order of the middleware settings in this file ... /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/settings/base.py I reordered as below, restarted everything but no joy :-( ... at Line 76 ... MIDDLEWARE = ( 'allauth.account.middleware.AccountMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.middleware.common.CommonMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ... I'm thinking this is not the file I'm looking for. Apologies for my cluelessness here.

1 year, 2 months

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gilles Filippini

Mark Sapiro a écrit le 23/04/2020 à 19:02 : > On 4/23/20 2:48 AM, Gelpi Andrea wrote: >> >> I saw the change in the file. >> >> As I'm not a programmer How can I test your fix? >> >> My system was installed via Debian 10 stable repository. >> >> I upgrade with testing repository postorius, django and mailmanclinet >> >> Postorius V 1.3.2 >> Django V. 2.2.12 >> Django filters V 2.1.0 >> Djanog mailman V 1.3.2 >> mailmanclient V 3.3.0 > > > I don't know where the Debian package puts things, but you have to find > the location of postorius/views/list.py. Something like > > locate views/list.py On debian this file is part of the python3-django-postorius package, and is installed here: /usr/lib/python3/dist-packages/postorius/views/list.py > > should find it. Then you need to download > <https://gitlab.com/mailman/postorius/-/merge_requests/500.diff> and > edit it to remove the first 15 lines so the first remaining line is the > > diff --git a/src/postorius/views/list.py b/src/postorius/views/list.py > > line. Then make a backup copy of postorius/views/list.py and run the command > > patch postorius/views/list.py path/to/500.diff > > where postorius/views/list.py is actually the full path to > postorius/views/list.py and 500.diff is the edited file you downloaded. You'll have also to remove the compiled files from the __pycache__ directory: $ sudo rm /usr/lib/python3/dist-packages/postorius/views/__pycache__/list.cpython-*.pyc > Then restart uWSGI. If anything goes wrong, restore your backup copy of > postorius/views/list.py and restart uWSGI. The best way to restore is to force the re-installation of the package: $ sudo apt-get install --reinstall python3-django-postorius It will take care of the compilation part. _g.

5 years, 8 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Tue, Dec 27, 2022 at 11:23 AM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > El 26/12/22 a las 23:57, Mark Sapiro escribió: > > ... > >> I don't want to put more noise in the list. But I'm confused because > >> I always updated via pip the apache mod_wsgi thinking is was needed > >> for my configuration. If it is not, I will stop updating it. > > > > Based on the above you ARE using Apache mod_wsgi and if you are still > > also running uwsgi as > > > > /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & > > > > that is unnecessary. > > It clarifies a pair of things. Thanks a lot. > > I'll try deactivating that in one of my servers (the "quieter" one) and > see how it goes. > > Again, thanks for your kind support. > I have actually deactivated mine, and life is still good with my MM3. And just so that my mind is in the clear, there are three ways of getting the full MM3 functionality, viz: 1. Mailman core, Django's cluster, and Gunicorn 2. Mailman core, Django's cluster, and uWSGI 3. Mailman core, Django's cluster, and mod_wsgi And something that has not been quite clear to me: What is the purpose of Django's cluster in all this? I am asking because on my FreeBSD server, I usually see not less than 30 PIDs for: /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/django-admin qcluster --pythonpath /opt/mailman/mm/ --settings settings (python3.9) And there is a time I found it having 240 PIDs. Would there be a problem if I limit the number of workers to "8"? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

Search results for query "sapiro"