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

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-25 01:37, Mark Sapiro wrote: > I think the difference is http vs https, not the IP vs domain name. > > Also, with either of these, you are addressing the web server and not > the wsgi server. The wsgi server is presumable listening on port 8000 > and in the beginning when you had the default > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' With this default, the template URI is in the format of http://localhost:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… Looking at this URI in lynx (on the same server as Mailman) it returns the text of the custom Welcome template, as does curl and wget. And it's the same if 127.0.0.1 is used in place of localhost -- ie. http://127.0.0.1:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… And the same result if the domain name is used with https -- ie. https://mydomain.com/mailman3/api/templates/list/mytestlist.mydomain.com/li… So, the template is all good, it can be accessed by Lynx, but the part of the Mailman suite that sends out the custom Welcome message cannot access it and spits out the error. Where are the custom templates stored? Is there a permissions issue perhaps? A grep for the text of my Welcome message turns up zero results. # grep -Rnw '/' -e 'Test two million for welcome' By the way, in Lynx when the template's URI uses the public ip adress -- ie. http://my-public-ip-address/mailman3/api/templates/list/mytestlist.mydomain… ... it returns a "404 page not found" in Lynx. Given that this is pretty much an out-of-the-box installation (venv installation as per the docs) and everything else works perfectly I'm thinking surely others have encountered this. Or is it just me? It's completely done my head in, so if anyone can offer a glimmer of light I'll grab it. > <REDACTED-PUBLIC-IPv4-ADDRESS> instead of 127.0.0.1. Also, > Have you set > ALLOWED_HOSTS in your settings.py? It should be something like > ``` > ALLOWED_HOSTS = [ > "localhost", # Archiving API from Mailman, keep it. > "127.0.0.1", > "<REDACTED-PUBLIC-IPv4-ADDRESS>", > "MYDOMAIN.COM", > ] Yes.

1 year, 5 months

[MM3-users] Re: Monthly Password Reminders

by Odhiambo Washington

On Fri, Feb 3, 2023 at 3:05 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > On Thu, Feb 2, 2023 at 8:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 2/2/23 06:29, Odhiambo Washington wrote: > > > > Does MM3 send these monthly subscription reminders the way MM2 used > to > > > do? > > > > I am looking for the setting, but can't find that in the list > settings. > > > > > > No, it does not. > > > > The rationale behind the decision to toss away that feature? Security?? > > For the passwords, yes. It was frequently reported as a bug, in fact. > Mostly the reminders generate requests to know how to shut them off. > You're the first in probably a decade who's asked how to turn them on! > It's because I only recently migrated to MM3 after watching from the periphery for years :) I have been on MM2, and even there I disabled it. I was just curious. While in theory we could protect in transit with SMTP over TLS, we > can't guarantee end-to-end encryption (eg, if there's a .forward at > the subscribed address), and while TLS is widely implemented, it's > still not universal. And there's no way to protect unencrypted email > from admins at the receiving host. Receiving encrypted email is > pretty much not implemented at all, except in some specialized > communities. Also, now that passwords (if they're used) are > attributes of Users who may have several Addresses and worse, they may > have admin privileges. So Mailman 3 passwords are generally higher > value than in Mailman 2. > > I can imagine a use for the list of subscriptions part that a few > users might like, but most folks would prefer not to get another > regular mailing. > > Steve > That makes complete sense, and I am satisfied with the decision. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On May 12, 2020, at 3:46 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/12/20 3:02 PM, Mark Dadgar wrote: >> >> The second patch did not work either. Ahh, well. > > > I think you need to do something like this: > > $ mm/bin/django-admin shell > Python 3.7.1 (default, Dec 14 2018, 13:17:01) > [GCC 5.4.0 20160609] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import Email >>>> emails = Email.objects.all() >>>> for email in emails: > ... if email.content.find('\u200b'*5) >= 0: > ... print('Found in ml {}, hash {}'.format( > ... email.mailinglist.name, > ... email.message_id_hash)) > ... >>>> _NAME/message/HASH/ Finally getting around to looking into this now that I’ve migrated from sqlite3 to postgres (writeup on that coming soon for the archives). Here’s what I get when I attempt the above commands: root@mail:/usr/lib/mailman3/bin# sudo -u list django-admin shell Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email Traceback (most recent call last): File "/usr/lib/python3.8/code.py", line 90, in runcode exec(code, self.locals) File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/hyperkitty/models/__init__.py", line 25, in <module> from .category import ThreadCategory File "/usr/lib/python3/dist-packages/hyperkitty/models/category.py", line 61, in <module> class ThreadCategory(models.Model): File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 103, in __new__ app_config = apps.get_containing_app_config(module) File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 252, in get_containing_app_config self.check_apps_ready() File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 134, in check_apps_ready settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 79, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 60, in _setup raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. >>> I am in no way a django expert. Thoughts? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 4 months

[MM3-users] urllib.error --was: Re: No module named 'mailman3hyperkitty'

by Axel Rau

> Am 17.01.2022 um 00:19 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/16/22 10:24 AM, Axel Rau wrote: >> ModuleNotFoundError: No module named 'mailman3hyperkitty' > > This comes from mailman.cfg from the class: definition in the [archiver.hyperkitty] section you probable have something like > > class: mailman3hyperkitty.Archiver > > instead of > > class: mailman_hyperkitty.Archiver Correcting this, does not stop server errors. While selecting a list in the browser, I’m getting: - - - Traceback (most recent call last): File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get 'hyperkitty' in archivers and # noqa: W504 File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ self[key] File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} - - - Question: Am I missing aliases in my nginx.conf? I just have: - - - location / { uwsgi_pass unix:///tmp/uwsgi.sock; include /usr/local/etc/nginx/uwsgi_params; } location /static { alias /usr/local/mailman3/static; } location /static/favicon.ico { alias /usr/local/mailman3/static/postorius/img/favicon.ico; } - - - Any help appreciated, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 8 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

On 6/4/2023 9:25 PM, Mark Sapiro wrote: > On 6/4/23 11:45, Joel Lord wrote: Thanks for the explanation on size-triggered digests. >> Periodic is much more complicated, even to explain. I have the cron >> job running nightly at 11:00 PM and it certainly seems to be working, >> except for one really odd thing. The list also definitely has >> periodic digests enabled in the web UI. This is a very bursty list, >> so it will go mad with traffic for a few weeks and then will go mostly >> idle for a month or so. The first digest of a burst is definitely >> size-triggered, but pretty reliably it has the last few messages from >> the previous burst in there. So the one I got today had three >> messages from today and one message from May 4th. But that May 4th >> message should have gone out at 11:00 PM on May 4th with the daily >> digest and then gotten flushed from the pending digest queue, right? > > That's correct. Do you ever get periodic digests sent at 11:00 PM? If > not, there is some issue either with configuration or something. If you > get them sometimes, I don't know what could be wrong. The periodic digests do seem to be coming out. I also now have confirmation that the one message in this morning's digest that was from May 4th was also included in the last digest back on May 4th, so it seems that the one message was left behind in the digest queue when the periodic digest was sent. There was one earlier message to the list back on May 4th, before the one that got duplicated, but I can't tell if that triggered a size-based digest to be sent: the logs aren't clear enough on that detail for me to tell. Just to inform things: (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman django-mailman3==1.3.9 mailman==3.3.8 mailman-hyperkitty==1.2.1 mailman-web==0.0.6 mailmanclient==3.3.5 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper mailman-hyperkitty==1.2.1 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post postorius==1.3.8 -- Joel Lord

2 years, 4 months

[MM3-users] Re: Turn off social logins?

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/14/19 11:10 PM, Stephen J. Turnbull wrote: > > Torge Riedel writes: > > > > > - there is a way to do this now via settings_local.py, but feels > > > a little bit risky if default configuration changes on update of > > > mailman > > > > This should not be true. If it is, we need to fix that. Will check. > > > It is more or less true [...] the only way settings_local.py can > change something like INSTALLED_APPS is to redefine INSTALLED_APPS > in it's entirety which leads to the possibility of INSTALLED_APPS > changing in settings.py and those changes not being picked up in > settings_local.py. That's a different issue from the one I believe Torge is worried about, which is an update overwriting settings_local.py. But it's not good. > The way around this is to remove the import of settings_local from > settings.py and then put > > from settings import * > > at the beginning of settings_local.py and then point Django at > settings_local rather than settings. I don't understand the ramifications of making this change (presumably Barry or somebody had a reason for the change from Mailman 2's method), but at first glance it looks like a big step in the right direction. > Then you can do things like > > try: > INSTALLED_APPS.remove('allauth.socialaccount.providers.google') > except ValueError: > pass > > in settings_local.py except there are still issues because, e.g., > INSTALLED_APPS is defined as a tuple (immutable) and not a list in > settings.py. Given the concerns of privacy advocates, I would say that it would be better to have a separate AUTH_PROVIDERS = ['allauth.socialaccount.providers.google', ...] in settings_local.py, and merge that in to INSTALLED_APPS. Of course removing specific providers would be OK too, but I think that this is a place where "deny all / accept what you want" is appropriate. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 7 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Ruth Ivimey-Cook

Marcus, I'm with you in not understanding Mark's instructions -- I think there is a typo somewhere :-) To create a non-member user in Mailman, Go to the List Settings page in Postorius, select Non-members from the User menu, and add a user there. Of course, that does nothing for your email system, which must also be configured. I would very strongly encourage you to have the no-reply address be 'real' in the sense that the email system will agree it is valid and deliverable, or some recipient email servers will refuse to accept email from that address, either. The right thing is for email to that address accepted as normal and then immediately discarded. You could send back a message "this address is not monitored" but there is an issue with spam backscattering which makes that less good than it first seems. Regards, Ruth On 06/04/2021 10:00, marcus.granath(a)gmail.com wrote: > Thank you @Mark Sapiro for you quick reply. > > So by doing the following settings, then ALL the messages sent to the list will be hold for moderation: > > Settings -> Message Acceptance > > "Default action to take when a member posts to the list": "Hold for moderation" > "Default action to take when a non-member posts to thelist": "Hold for moderation" > > Members -> Administration options -> Moderation: "List default" > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? > > Also, how do I create a "non-member" user "no-reply(a)abc.com"? > Do you mean that I do that under the "Mass operations -> Mass subscriptions" ? Can I add a "fake address" there? > _______________________________________________ > 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/ -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 6 months

[MM3-users] Re: slow restart time for mailmanweb

by William Oliver

On Tue, 2021-12-28 at 13:52 -0800, Mark Sapiro wrote: > On 12/28/21 1:28 PM, William Oliver wrote: > > > > > > > These log entries are from restarting mailman, not mailmanweb Damn. Sorry about that. Brain fart. Yep, it's still slow with mailmanweb: Dec 28 17:41:00 emergenus systemd[1]: Stopping GNU Mailman Web UI... Dec 28 17:41:01 emergenus uwsgi[20860]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Dec 28 17:41:01 emergenus CRON[44474]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) Dec 28 17:41:06 emergenus kernel: [12494.670812] [UFW BLOCK] IN=eth0 Dec 28 17:42:01 emergenus CRON[44755]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) Dec 28 17:42:07 emergenus kernel: [12555.550730] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3e:ef:72:96:00:23:9c:9e:9f:c0:08:00 SRC=92.63.197.112 DST=203.159.80.234 LEN=40 TOS=0x00 PREC=0x00 TTL=253 ID=9540 PROTO=TCP SPT=57024 DPT=25238 WINDOW=1024 RES=0x00 SYN URGP=0 Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: State 'stop- sigterm' timed out. Killing. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 20860 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44476 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44477 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44478 (sh) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44480 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44483 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44484 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44485 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44486 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44487 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44479 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44481 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Main process exited, code=killed, status=9/KILL Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Failed with result 'timeout'. Dec 28 17:42:30 emergenus systemd[1]: Stopped GNU Mailman Web UI. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Consumed 2min 27.819s CPU time. >

3 years, 9 months

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

by Andy Smith

On Mon, Jul 11, 2022 at 02:44:59AM +0000, Andy Smith wrote: > 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. This just happened again. As a refresher, the issue I'm seeing is that Mailman registers a bounce against addresses that aren't subscribed, including addresses for the list itself and for the -leave address that is in some footer text. Here's the bounce.log: Sep 30 17:12:25 2022 (8428) Member [elided1](a)[elided1].force9.co.uk on list users.mailman.bitfolk.com, bounce score = 1. Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email mailto:[elided2]@gmail.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Member [elided2](a)gmail.com on list users.mailman.bitfolk.com, bounce score = 1. Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users-leave(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Member [elided3](a)[elided3].org.uk on list users.mailman.bitfolk.com, bounce score = 1. I have elided parts of the email addresses of real subscribers. Attached is the actual non-delivery report from the MTA that triggered this. In it I have done my best to elide the names and addresses of real people, but nothing else. They match the same elisions from the bounce log. Any ideas why Mailman is interpreting this NDR so over-zealously? It seems like a pretty standard one. [elided1].force9.co.uk is the subscriber who rejected the mail, yet also users(a)mailman.bitfolk.com, [elided2](a)gmail.com, users-leave(a)mailman.bitfolk.com and [elided3](a)[elided3].org.uk (sender) were punished. Thanks, Andy

3 years

[MM3-users] Re: Does hyperkitty show JPEGs in line and what about attachments?

by Jason Glazer

Mark Thanks for the link to the test archive. That and your information has clarified things a lot. Jason On 7/12/2017 11:39 AM, Mark Sapiro wrote: > On 07/12/2017 04:47 AM, Jason Glazer wrote: >> Does anyone know if Hyperkitty can be configured to allow for inline >> images to be maintained so that an HTML file looks like a normal HTML >> message? >> >> Also, can attachments to a message under Hyperkitty preserve their name >> rather than being "scrubbed" into "attachment-*.*" files? > > The answer to some of this is at > <https://lists.mailman3.org/archives/list/test@mailman3.org/message/N3XVN3DC…>. > > One question unanswered by that post is what happens with an inline > image in an HTML message body. In the original message, the image is > referenced by an IMG tag with "src=" pointing to the image MIME part. > Since this structure is not maintained in HyperKitty, inline images > probably don't work. > > Also, with respect to Mailman 2.1, if you want the scrubber to preserve > file names and extensions, set the following in mm_cfg.py > > SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False > SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True > > and if you want scrubbed HTML to not be HTML escaped so it renders > rather than looking like raw html, set > > ARCHIVE_HTML_SANITIZER = 3 > > but note this comment from Defaults.py > >> # 3 - Remove text/html as attachments but don't HTML-escape them. Note: this >> # is very dangerous because it essentially means anybody can send an HTML >> # email to your site containing evil JavaScript or web bugs, or other >> # nasty things, and folks viewing your archives will be susceptible. You >> # should only consider this option if you do heavy moderation of your list >> # postings. > > This is an issue with HyperKitty as it appears this is what HyperKitty > does and there's no way to turn it off. > -- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

8 years, 3 months

Search results for query "sapiro"