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

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote: > > If the manage.py in the directory in which you ran this is the > correct one for your Mailman Django project, I don't know why it > didn't work. Me neither :-( That's why I asked, and probably Guillermo, as well. > Is your Mailman installed in a virtualenv? If so, was the virtualenv > activated? No virtualenv. Mine is deployed using system python on a CentOS 7 system, toghether with another in house developed low requirements Django project, both served by uWSGI vassals. And then, all of a sudden, while I was writting this, it dawned on me! Postorius, Hyperkitty and django-mailman are installed with pip, so, the end up in the site-packages directory (usually /usr/local/lib/python3.x/site-packages), but, normally, django projects are deployed somewhere in the web server hierarchy (/var/ww/django in my case, due to old personal tastes), and applications properly defined in the settings.py for the project. So, the message files are out of reach for manage.py. Changing to /usr/local/lib/python3.x/site-packages/X (with X being postorius, hyperkitty and django_mailman3) and using django-admin compilemessages all works! Thanks for pushing my thoughts in the right direction! -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 6 months

[MM3-users] Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > Because those aren't the settings that matter for this. > What if anything are your settings in the mailman.cfg [webservice] > section for > hostname: > port: > admin_user: > admin_pass: > use_https: > (defaults in our distribution are localhost, 8001, restadmin, restpass > and no respectively - I don't know if Debian changes these). > These need to match the Django settings > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = 'restpass' They do match. Even the port (still on 8001). > > The REST API is apparently not listening on the host/port this is trying > to connest to. Apparently. The question is why. > > What is executing the manage.py command to start Django. Is it user list? Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root. > > 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 too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx.

4 years

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Brian Carpenter

On 11/10/20 4:40 PM, Mark Sapiro wrote: > On 11/10/20 1:22 PM, Mark Dadgar wrote: >> Brian specified: >> >> verp_personalized_deliveries: no >> >> Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? > > That depends on the setting of verp_delivery_interval. If > verp_delivery_interval = 1, every message will be VERPed regardless of > verp_personalized_deliveries. If verp_delivery_interval = 0 and > verp_personalized_deliveries = no, deliveries won't be VERPed as you > note. If verp_delivery_interval = 0 and verp_personalized_deliveries = > yes, only personalized deliveries (i.e. individual messages, not > digests, from lists with Personalization enabled) will be VERPed. > > The theory is VERPing has a cost because it requires a separate message > sent to each recipient rather than a single message with multiple > recipients, but personalization also requires a separate message sent to > each recipient, so those can be VERPed at no extra cost. > > But to be clear, automated bounce processing does not require VERP. It > just works a tiny bit more reliably with VERP. We actually enable VERP by default on all new installations of Mailman 3 as we don't see a real performance hit and its benefits are generally very good. This new list however was a whole different beast. Also due to the nature of the list, the benefits of VERPing pales in comparison to the timeliness of the mail being sent. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:36 -0800, Mark Sapiro wrote: > > Why do you say the .mo files are old. The timestamps are all Feb 3 > 02:47 which is when the package was built for PyPI. Because my brain goes faster than my fingers and I say the reverse of what I mean. I meant .mo files, all .po where properly dated, and I reversed the meaning of my thoughs while typing. Thanks for brining my confussion to my (and everybody's) attention, and my appologies for the noise. > When things are changed on weblate, we get automatically generated > merge requests to update our source. We don't always merge them > immediately, but we certainly do merge all the outstanding ones > before making a release. I'm 95% certain that I edited messages after Nov 7th in the Spanish translation of both mailman, postorius and hyperkitty, but the .po file is dated Nov 7h. Actually, I did a review of outstanding strings when Abhilash annonced the RC for the current version. That is why I was bit surprised. But then, it may be me and my faint memory. And, of course, I'm very grateful and happy with all the work that is being done on Mailman3. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 6 months

[MM3-users] Re: aborted connection

by Sandor Dibuz

On 2/20/22 01:56, Mark Sapiro wrote: > > First, If your Mailman core version is >= 3.3.5, you shouldn't be > running gatenews via cron. Mailman's nntp runner runs it. See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > But, that probably isn't it because in Mailman >= 3.3.5, running > gatenews via cron should produce this error > > The gatenews command is run periodically by the nntp runner. > If you are running it via cron, you should remove it from the crontab. > If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the > environment. > > > However, since you have no lists using a news->mail gateway, you don't > need to run gatenews at all so just remove it from the crontab. I installed Mm3 from Debian stable distro packages as one of the suggested installations methods in Mm3 docs. It's a bit of dated though I know but it was the easiest and fastest. Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] So I disabled gatenews cron job. Maybe later I bite the bullet and upgrade to a recent version (either venv or docker haven't decided yet) but will have to learn how to avoid conflicts with already installed deb packages first. So far so good and everything works, have to check changelogs if an upgrade is worth it. Thank you all your help, Mark. Sanyi

3 years, 6 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-27 08:01, Mark Sapiro wrote: > On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > > > – but the existing directory /opt/mailman/fulltext_index (and its > > contents) are readable and writeable by mailman:mailman: > > > > > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > > > > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > > > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > > > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > > > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > > > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > > > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > > > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > > > I fail to see where haystack tries (and fails) to create the directory. > > FWIW, deleting threads is not a problem. > > It is uwsgi trying to do this. What user is it running as? Maybe you need to > add that user to the `mailman` group. That's what baffles me – uwsgi is run as the mailman user: mailman 3904667 1.3 0.5 129516 62188 ? Ss 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini mailman 3904668 0.0 0.3 203248 48796 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini mailman 3904670 0.8 0.6 220436 74464 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini - Jan

2 years, 8 months

[MM3-users] Re: Strange password problem

by Eggert Ehmke

Am Freitag, 22. September 2023, 19:34:41 CEST schrieb Mark Sapiro: > On 9/22/23 09:50, Eggert Ehmke via Mailman-users wrote: > > -I try to log in as admin > > -rejected because of wrong password (password is stored in browser) > > -used forgotten password function, using my email address > > -reset password to the stored value from browser > > -login works now. Works also when logged out/in again > > -however, the next day this behaviour repeats. > > So apparently the issue is that although you reset your login password > to a known value, it doesn't stick and reverts overnight to some other > value. Yes that it looks like. > Is this the Debian package or installed following > https://docs.mailman3.org/en/latest/install/virtualenv.html or something > else. Yes it is a virtualenv installation following that guide. > All I can think of is some cron may be resetting the password. If that's > it, it's probably a Debian thing. Can you see if there's any cron > running the Django admin changepassword command? Will try to find that. > If you set the password with the Django admin changepassword command, > does it stick? Never tried that, how do I do that? > Can you create another superuser with the Django admin createsuperuser > command and does that user's password stick? Will try that. So I can create another superuser? Does it need a separate email address? I guess yes Thank you for your ideas.

1 year, 11 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Odhiambo Washington

On Thu, Jun 6, 2024 at 11:28 AM Marcus Bautze via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hallo, > > Am 27.05.2024 um 14:33 schrieb Mark Sapiro: > > Enabling archivers is done in mailman.cfg similarly to > > ``` > > [archiver.hyperkitty] > > class: mailman_hyperkitty.Archiver > > enable: yes > > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > > Thank you, archiver is now starting. Now there's another problem: > > In mailman.log i'm finding: > > "Jun 06 10:16:16 2024 (3556489) ACCEPT: > <d3072553-2f52-4bd7-b14a-2701863812c7@***> > Jun 06 10:16:17 2024 (3556492) HyperKitty failure on > https://[URL]/mailman3/hyperkitty/api/mailman/urls: <html> > <head><title>403 Forbidden</title></head> > <body> > <center><h1>403 Forbidden</h1></center> > <hr><center>nginx</center> > </body> > </html> > (403)" > > in mailman-hyperkitty.cfg there is: > > base_url: https://[URL]/mailman3/hyperkitty/api/mailman/urls > The documentation says that mailman-hyperkitty.cfg should contain: [general] base_url: https://[URL]/archives api_key: S0m3SecretArchiverAPIKey In settings.py, you should have: MAILMAN_ARCHIVER_KEY = 'S0m3SecretArchiverAPIKey' The KEY is quoted in settings.py,m but not in mailman-hyperkitty.cfg and it must be the same in both files. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 20:00, Mark Sapiro wrote: > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> But... here is a thing that I can not understand: If the source (the .po >> file) is from november 7th, it doesn't matter how many times you >> recompile it: the result will be the same. > Correct, but the point is if you download the latest > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file > in the distribution, you will find they are identical, so it it appears > that the weblate translation hasn't changed since that time. > > If there are issues in this mailman.po, they exist in weblate too and > need to be fixed there. That clarifies all. Thanks. As I said in my previous message, I'll wait for the next upgrade and hopingly the translations done after 7h of november (by others and me) will be there. > > Also note that the translations on weblate only affect strings in the > core code. The Mailman core templates are not currently translated in > weblate and there are currently no Spanish language templates. One would > need to create Spanish translations of all the templates in > <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> > and submit a merge request to add them to a mailman/templates/es/ directory. > I will make the template translations locally, test them, and then, if they are yet lacking in the main repo, follow your suggestion. Thanks.

4 years, 6 months

[MM3-users] Re: Issues with importing archives from a particular list

by Philip Colmer

On Thu, 13 Jan 2022 at 18:01, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/13/22 4:33 AM, Prasanth Nair wrote: > > Hello, > > > > We are trying to import archives from Mailman2 to Mailman3. For a > > particular list, it is not importing all of the messages. We can see that > > Mailman2 has archives from 2015 to 2022. But, it only imports messages > from > > 2018 to 2022 to the Mailman3 server. It was not giving any errors while > > importing. > > > The problem list probably already had an archived message from 2018. If > you don't specify a --since= date for hyperkitty_import, it only imports > messages newer than the newest existing message in the archive. > > You can run it again with, e.g., --since=2000-01-01. It won't reimport > the messages already imported because of duplicate message ids. > Thank you, Mark, for your reply. It turned out that this wasn't an issue with any part of the Mailman 3 suite. Unbeknownst to Prasanth, the affected list had previously been migrated from a different server in 2018 but, for some reason, the mbox file was not copied over - just the pipermail archive directory was. That explains the split between the pipermail archives and the mbox file. Thankfully, the original server still had the older mbox file so we've now been able to import all of the messages into HyperKitty. Apologies for the noise. Regards Philip

3 years, 7 months

Search results for query "sapiro"