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

[MM3-users] Re: Hyperkitty messages stuck in spool

by Mark Dadgar

On Nov 19, 2021, at 5:47 AM, Andrew Hodgson <andrew(a)hodgson.io> wrote: > Stephen J. Turnbull wrote: > >> Mark Sapiro writes: >>> On 11/18/21 6:38 AM, Andrew Hodgson wrote: >>>> >>>> Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? >>> >>> I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. >> >> If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. > > Thanks for this it was due to changing cloud providers. My old provider I installed Debian from an ISO file which created the swap partition but on the new provider I used their cloud image with no swap. Swap now created and everything is back to normal. Its running on an instance with 2GB of RAM and based on how I am seeing the usage running I would see this as an absolute minimum for a standard Mailman 3 stack. I had this same experience on Digital Ocean. The short-term fix was enabling swap and the long-term fix was upping my service level to something with more memory. Without swap, I don’t think 2GB is realistically sufficient to run a full mm3 instance. The cloud providers really don’t like you to run swap because it hammers their SSDs. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 11 months

[MM3-users] Re: mailman-web: ResponseNotReady

by Abhilash Raj

Hi, $ docker-compose rm -f mailman-web $ docker-compose up -d mailman-web This will basically create a new container for Mailman-web, but, since the state of mailman-web is stored completely in database (database container), I am not sure how to reset *just* mailman-web without dropping mailman-core related tables too (they share the same database but have their own separate tables). The above command will get you a fresh copy of code running. You can potentially get the list of tables and drop them, or maybe Diango has some way to reset it's state from Django shell (python manage.py shell, from inside mailman-web will get you shell). I may have to look it up. Also, just by looking at the traceback, I am not sure about the exact error. I may have to debug more to arrive at a better conclusion, which I won't able to do until after this weekend. Thanks, Abhilash On October 18, 2017 1:27:21 PM PDT, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >On 10/18/2017 12:28 PM, Mark Sapiro wrote: >> On 10/18/2017 09:00 AM, Dmitry Makovey wrote: >>> >>> It seems like mailman-core is still operating properly, but for some >>> reason mailman-web is not. Can I reset mailman-web somehow to >re-initiate? >> >> >> I'm not very well versed in the docker images, but I think >mailman-web >> uses uWsgi and sending the uwsgi process a SIGHUP should do it. > >I think I didn't express myself clearly - I want to reset any saved >state for mailman-web - not just in-memory stuff. I've restarted my >setup several times with mailman-web having exact same problem every >time. > >-- >Sr System and DevOps Engineer SoM IRT -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 14/2/21 18:42, Mark Sapiro wrote: > On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I did some exploration this morning (Spain time) in the weblate >> statistics and archives and I found that the changes done from >> Victoriano and me were recorded. I did a screencopy of all that if >> someone has any doubt about it. I downloaded this files: >> >> -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po >> -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po >> -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po >> -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po >> >> The thing is that they differ from the .po installed via pip upgrade. >> Mostly, as said, postorius, hyperkitty and django_mailman3. > > The latest packages in PyPI (pip) were released on Feb 2 except for > django-mailman3 which was released on Jan 15. They don't include updates > after those dates. > And I say that I (and others ) have made translations in postorius, hyperkitty an Django_mailman3 in January. Yes, I've made some changes in february 10th, but It were a pair of messages. But that's all about this from me. If in the next upgrade I find that there is any translation missing, I know, thanks to you and Victoriano, how to handle it. And if some new admin installs mailman 3 and try to localize it to spanish and comes to this list to ask how to do a more complete translation... well, these messages can point him or her to the right direction. My postorius web access to the lists is now almost completely translated to spanish and now I can help the users without hesitating language problems. Thanks. Thanks a lot.

4 years, 8 months

[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

3 years, 10 months

[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, 8 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, 8 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, 7 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, 3 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, 7 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, 9 months

Search results for query "sapiro"