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

[MM3-users] Re: MM3 templates

by Odhiambo Washington

On Wed, Feb 15, 2023 at 6:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 05:22, Odhiambo Washington wrote: > > > > 1. Where is this template that the system used and can I edit it? > > > /opt/mailman/mm/venv/lib/<python_version>/site-packages/mailman/templates/en/list:user:action:subscribe.txt > > You can edit it, but your edits will be overwritten if you upgrade. > I will not touch that. > > 2. Why is it not using the template I created? > > Is the template you placed in > /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > named list:user:action:subscribe.txt and does Mailman have permission to > read it? > Yes. [18:47 ~ ]$ ls -al /opt/mailman/mm/var/templates/lists/ kictanet.lists.kictanet.or.ke/en/ total 48 drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . drwxr-xr-x 3 mailman mailman 512 Feb 14 08:54 .. -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt > Did you try to create a template in Postorius? If you did, that one will > take precedence. > Not at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: customized welcome message

by Nils

Forget the previous message. Thank you very much for your help, Mark. I looked at the configuration files once more, and changing POSTORIUS_TEMPLATE_BASE_URL in mailman-web.py fixed the issue for me. Kind regards On 12/7/23 23:09, Nils wrote: > On 12/7/23 22:40, Mark Sapiro wrote: >> How and to what did you set the URL for the template? What does the >> database query >> >> SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; >> >> show? > http://localhost/postorius/api/templates/list/testliste.lists.DOMAIN.TLD > > This value can't work. Now it makes sense that it gets redirected and > the use of localhost also explains why it didn't show in any of the > virtual hosts log files that I was checking until it was redirected. > > However, I didn't set that value. I edited the template at > postorius/lists/testliste.lists.DOMAIN.TLD/templates and there I can > just select a template type and then I get one textarea input field > for the content. > The value in the database is set automatically, when I create a > template in postorius (and is also automatically removed when I delete > a template there). I can't edit this value without manually changing > it in the database. > >> This is very old. Current Postorius is 1.3.10. 1.2.4 is from February >> 2019. The Debian/Ubuntu packages are out of date. We recommend >> installing via the doc at >> https://docs.mailman3.org/en/latest/install/virtualenv.html > > The server will be updated from Ubuntu 20.04 (focal) to 22.04 (jammy) > very soon. The Debian/Ubuntu packages sure have their downsides but > once they work, they update automatically and require very little > maintenance.

2 years

[MM3-users] Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 3:13 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/5/24 1:52 PM, advorkin(a)cs.princeton.edu wrote: > > > > I went with the apache/uswgi configuration. The site is up and running, > but if I click Postorius, it gets redirected to > https://mysite.com/postorius/lists and I get not found error message. > > > > The same goes for Lists and Archives. > > Compare your urls.py to > < > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re…>. > > Some of the `path` settings are probably not in the same order as in > that file. The > > ``` > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > ``` > settings should come after the > ``` > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > ``` > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > order). Or you can just delete the 'postorius/' and 'hyperkitty/' ones > or you can add > ``` > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ``` > to your Apache config. > The odd thing is that the HOWTO that he followed never involves the manipulation of any urls.py at all - it's not even mentioned at any point. So obviously the issue is caused by something else and I suspect something within Apache needs to be re-evaluated in the guide. -- 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, 9 months

[MM3-users] Re: spanish localization

by Abhilash Raj

On Sat, Feb 13, 2021 at 11:00, Mark Sapiro <mark(a)msapiro.net> 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. > > 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. You can actually translate the templates in Weblate too. That is actually the whole reason to go with monolingual template format in Mailman Core. Mailman uses the template file's name as the msgid for translations and all in-tree templates are copied into English's .po file when we re-generate them. For example in here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… The english .po file is considered as reference in Weblate and used for source string. Abhilash

4 years, 9 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Andy Smith

Hi Mark, On Sat, Jul 09, 2022 at 12:05:32PM -0700, Mark Sapiro wrote: > If the original post was the message delivered to > users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or > another recognizer parsed those addresses from the message body. For now I've configured a copy of all mails to -bounces addresses, so if/when it happens again I can inspect the actual email that triggered it. In case anyone else ever wants to do that, this is one way to do it on Exim: # This goes in your "routers" section. # Add a router, before every other router that you would want to # tap messages for. traffic_tap: unseen no_expn no_verify transport = local_copy_outgoing driver = accept # "mm_domains" is a list of domain names for mailman, e.g. # "lists.example.com"; it's set as part of the usual Mailman install on # Debian. domains = +mm_domains # Only do this for bounce addresses. So between this and the above, this # router will only happen for *-bounces*@your-mailman. local_part_suffix = -bounces : -bounces+* # This goes in your "transports" section. # Add a transport for taking a local copy. Mail to Mailman is "outgoing" as it # is delivered by LMTP over a socket. But the name is not important. local_copy_outgoing: driver = appendfile # Simply store it all in a maildir. If you're expecting a lot of # messages then you'll want a directory structure by date and/or # recipient or something. directory = /var/mail/archive/.outgoing/ delivery_date_add envelope_to_add return_path_add # If not on Debian then your exim probably runs as a different user/.group. group = Debian-exim user = Debian-exim mode = 0660 maildir_format = true create_directory = true Cheers, Andy

3 years, 4 months

[MM3-users] Re: Auth question

by Simon Hanna

On 03/31/2017 08:10 AM, David Krantz wrote: > On Fri, Mar 31, 2017 at 3:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> We're really working on getting a consistent, workable installation >> story and even getting some packaged solutions. I know we're not yet >> there, but we're here to help when people run into problems. > The site now works, but not the / url for the site. I get this error > in the mailman-web.log (with a very long stacktrace before it) > > NoReverseMatch: Reverse for 'hyperkitty.views.index.index' not found. > 'hyperkitty.views.index.index' is not a valid view function or pattern > name. > > I think that would correspond to this line in urls.py > > url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), Yes, that's the culprit. Replace it with the following: url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), You can also update whatever guide you were using... > but this corresponds exactly to what the example config says and I > know of no other name for hyperkitty. Probably it is dependent upon > understanding the url dispatching in Django but that takes some time > to read up on. The interesting thing is that /archives works so it is > just this redirect that has problems. I can probably get apache to do > the redirect instead but that is not the most elegant solution. > > Then I of course have things to do on getting social logins to work. I > currently get "DoesNotExist: SocialApp matching query does not exist." > if trying to connect an account to google (which I started with). Not > a showstopper as passwords do work. Did you follow django-allauth's guide on setting them up?

8 years, 8 months

[MM3-users] Re: Blocked by Hotmail

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/22/21 4:11 PM, Tom @ Gather wrote: > > My mail server is on Digital Ocean if that makes any difference. > > It may. All of my recent blocks have been DigitalOcean servers including > mail.python.org, but I think I've had this in the past from non- > DigitalOcean servers. My (very limited) experience with DigitalOcean is that they harbor bad actors. That's probably only because they're a very large provider, but YMMV (more important, Microsoft's mileage apparently does). Details follow for the curious. I need to find out who was knocking over my webserver every so often, so I did some cave-diving in the logs. In the process, I discovered that about 95% of vulnerability probes (attempts access to scripts not installed on my server averaging 5X/day) were coming from DigitalOcean netblocks, almost all of those from something called stretchoid.com. I've blocked the whole /18 where stretchoid lives: DROP tcp -- 192.241.192.0/18 0.0.0.0/0 Security analysts on the web have different opinions of stretchoid; some classify them as "malicious activity", others seem to think they're some sort of researcher. I think they're a PITA, and there are zero legit connections from that netblock in my logs, so "bye-bye". Now I see unexpected access attempts about 1/5 days. :-) Oh, and who *was* knocking over my server? It turned out that once a month my employer tried about 9000 different hacks in rapid sequence and it took a couple hours for the backlog to clear, so my students couldn't access their wiki accounts or my schedule page during that period. Blocked connections from the vulnerability probing host, and there have been no black helicopters over my office, so I guess that's that. :-) Steve

4 years, 10 months

[MM3-users] Re: MM2 -> MM3 Migration

by Odhiambo Washington

On Thu, Dec 29, 2022 at 10:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/29/22 05:25, Odhiambo Washington wrote: > > I looked at my list archives and saw that the latest post was on Dec 8, > > 2022. > > Then, because I wanted to import any posts that happened from 8th to > now(), > > I looked at two posts: > > 1. > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This talks about 'hyperkitty_import *--since=01.01.2022* -l > mylist@mydomain > > my-mbox-file' > > > > 2. https://mail.python.org/pipermail/mailman-users/2018-July/083607.html > > Which talks about 'hyperkitty_import *--since='1990-01-01'* -l > > mylist@mydomain my-mbox-file' > > > The default without the since= option is to import only those messages > from the mbox which are newer than the newest message in the existing > archive which is exactly what you want. > So I ended up using this and I can see the list metrics indicating that the last post was on 29Dec22, but I don't seem to be able to see those posts in the archives. I have compared these two: 1. https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… 2. With - https://posts.kictanet.or.ke/ - a WordPress website where I also display those same posts - I am a little confused. Must I re-index for the new posts to display? > hyperkitty_import uses python-dateutil > <https://dateutil.readthedocs.io/en/stable/> to parse the since date. > See <https://dateutil.readthedocs.io/en/stable/parser.html> for info on > formats. > Thanks. Will look at this. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 28, 2020, at 4:22 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > If I'm reading the above correctly, it appears that there is a message > in the archive database whose message_id value is > 'BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>'. > The trailing '>' is causing HyperKitty's Email.as_message() method to > try to set a value of > '<BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>>'. > > Or maybe there's leading white space in the value, or both. > > Try the following patch. > > > --- a/hyperkitty/models/email.py > +++ b/hyperkitty/models/email.py > @@ -24,7 +24,7 @@ import logging > import os > import re > from email.message import EmailMessage > -from email.utils import formataddr > +from email.utils import formataddr, make_msgid > > from django.conf import settings > from django.db import IntegrityError, models > @@ -175,7 +175,12 @@ class Email(models.Model): > header_date = self.date.astimezone(tz).replace(microsecond=0) > # Date format: http://tools.ietf.org/html/rfc5322#section-3.3 > msg["Date"] = header_date.strftime("%a, %d %b %Y %H:%M:%S %z") > - msg["Message-ID"] = "<%s>" % self.message_id > + try: > + msg["Message-ID"] = "<%s>" % re.sub('[<>\s]', '', > + self.message_id) > + except: > + msg["Message-ID"] = make_msgid() > if self.in_reply_to: > msg["In-Reply-To"] = unfold(self.in_reply_to) > The patch does not apply cleanly against /usr/lib/python3/dist-packages/hyperkitty/models/email.py patching file email.py patch: **** malformed patch at line 4: import os I am assuming that this is because I am running the Ubuntu packages, which are a year down-rev: Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: Timeout error on anonymous subscribe

by Gerald Vogt

On 23.10.24 21:35, Mark Sapiro wrote: > On 10/22/24 23:07, Gerald Vogt wrote: >> >> For testing I have set >> >> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' >> >> to the URL of our main domain, however, if I test an anonymous >> subscribe through the list info page I still get the timeout error > > This will have no effect unless you delete and recreate the template in > Postorius because simple changing the setting won't change the `uri` in > the template table. O.K. Did that. Now the uri in mailman.template is https://lists.example.org/mailman3/api/templates/list/community.lists.examp… However, it doesn't change the timeout issue, except now the error is HTTPSConnectionPool(host='lists.example.org', port=443): Read timed out. (read timeout=5) instead of localhost:8000. >> I can access http://localhost:8000/mailman3/api/templates/list/ >> community.lists.example.com/list:user:action:subscribe with curl and >> immediately get the response. > > Can you do that as the Mailman user?, e.g. > ``` > sudo -u mailman curl http://localhost:8000/mailman3/api/templates/list/ > community.lists.example.com/list:user:action:subscribe > ``` > assuming the Mailman user is `mailman`. I don't quite understand the relevance of the user accessing the localhost tcp port. Any local user can do that. I can access the template content with curl http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… as well as curl http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… as any user on the mailman server. And I can use the latter to access the template from anywhere as it's a public server. In any case, curl immediately returns the content. There is no delay. Thanks, Gerald

1 year, 1 month

Search results for query "sapiro"