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

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 2:10 PM, Marco Marinello wrote: > Dear Mark, > > configuration needed much troubleshooting so I'm sure I always restarted mailman core along apache2 but since it's still a testing environment, I took the liberty to test it again for you. > > # pip install https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip > # pip install https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… It appears that https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… is the latest mailman-hyperkitty, but https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip is missing some commits. It has https://gitlab.com/mailman/hyperkitty/-/commit/79b22a23d3390db741a8233fa1ff… but is missing https://gitlab.com/mailman/hyperkitty/-/commit/ec9c8ed18798cf8f7e89dfaba001… which is very strange because it does seem to have https://gitlab.com/mailman/hyperkitty/-/commit/705bdbb2fb27be60d17ada7cba84… I Suggest you do pip install -U HyperKitty pip install -U mailman-hyperkitty which will get the latest packages from PyPI or if you want the heads from gitlab, pip install git+https://gitlab.com/mailman/HyperKitty.git pip install git+https://gitlab.com/mailman/mailman-hyperkitty.git -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 1/31/23 23:33, Odhiambo Washington wrote: > Is this a race condition? > > <CUT> > ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) > Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django_extensions/management/commands/runjobs.py", > line 40, in runjobs > job().execute() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/jobs/update_and_clean_index.py", > line 37, in execute > run_with_lock(update_index, remove=True) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/lib/utils.py", > line 181, in run_with_lock > log.exception("Failed to update the fulltext index: %s", e) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > line 470, in __exit__ > self.unlock() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > line 420, in unlock > raise NotLockedError('Already unlocked') > flufl.lock._lockfile.NotLockedError: Already unlocked > <CUT> Yes, it is a race between the monthly hyperkitty update_and_clean_index job and the hourly hyperkitty update_index job -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: cannot import name 'parse_header' from 'django.http.multipartparser

by Mark Sapiro

On 2/26/25 07:40, Stefan Bauer via Mailman-users wrote: > Dear Users, > > i recently tried to upgrade to latest MM3 and followed this[1] steps. > > However > > (venv) $ mailman-web migrate > > fails with: > > from rest_framework import mixins, views > File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/views.py", > line 15, in <module> > from rest_framework.request import Request > File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/request.py", > line 17, in <module> > from django.http.multipartparser import parse_header > ImportError: cannot import name 'parse_header' from > 'django.http.multipartparser' > (/opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py) > (venv) mailman@edmmal03$ vi > /opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py > > Could this be a broken dependency? You have an incompatible configuration. django.http.multipartparser.parse_header was removed in Django 4.2. See https://docs.djangoproject.com/en/5.1/releases/4.2/#miscellaneous Your version of djangorestframework is incompatible with Django>=4.2. Try in your venv ``` pip install --upgrade djangorestframework ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 10/20/25 23:21, Stephen J. Turnbull wrote: > > I agree with Mark -- I don't see how to do this without changes to the > code. Also, note that even if you could configure this as you desire, > the CC addresses will be delivered. But people who subscribe but > aren't CC'd will receive the post only if and when the post is > released from hold. Only you can decide whether that's desirable, but > it's likely some subscribers will be unhappy about it. This is an important point. If your goal is to prevent exposing those non-member addresses in Cc:, etc. in posts from the list, then all this may help, but if your goal is to prevent list posts from going to non-members, you can't accomplish that. by the time mailman receives and perhaps holds the post, it will already have been sent to all the directly addressed To:, Cc: and Bcc: recipients. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:11 PM, David Newman wrote: > On 1/14/22 4:54 PM, Mark Sapiro wrote: >> >> It should work. I suspect you need to go to the list's Settings -> >> Automatic Responses and set `Admin immed notify` to Yes. > > > It's enabled. I think this triggers notifications only for new > subscription requests, not pending ones. Yes. That will send a single notification at the time of the request using the `list:admin:action:subscribe.txt` template. Notices of pending requests are sent by the `mailman notify` command using the `list:admin:notice:pending.txt` template. ... >> You can test `mailman notify` at any time by running it by hand. > > > Thanks. This still isn't working as intended. I took these steps: > > 1. Created the file > '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' The template name is `list:admin:notice:pending.txt`, not `list:admin:action:pending.txt`. Thats why it didn't work. ... > 2. Restarted the mailman3 and mailmanweb services You only needed to restart Mailman core. ... > What I'm trying to do here is replicate a feature from MM2.1, where > pending notifications had URLs embedded in the message. That's not > available out of the box in MM3, and if there's a place for feature > requests I'd be glad to ask that this be made the default. The place for feature requests for Mailman core (which this is) is https://gitlab.com/mailman/mailman/-/issues, however, this is not straightforward as Mailman core doesn't know if you even have Postorius or some other web management UI installed or what the URL to access it might be. Thus it's not just a simple matter of editing templates. It would also require a configuration setting for the base URL for the web admin UI and changes in logic to provide an appropriate replacement depending on whether or not the base URL was configured. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Which crontab?

by Mark Sapiro

On 11/03/2017 11:43 AM, Pierre Abbat wrote: > According to http://docs.mailman3.org/en/latest/config-core.html, I have to > add "@daily mailman digests --send" to the crontab. Which crontab does it go > in? In the system crontab, the thing after the time is the username, and > there's no user named "mailman" in /etc/passwd. Or should I put a script in / > etc/cron.daily/? The partucular "@daily mailman digests --send" would have to go in the user crontab for the Mailman user. If this is not 'mailman' it is what ever user "owns" Mailman. Further it would require that the path to Mailman's bin/mailman command be in that users $PATH. If it were to go in the system /etc/crontab it would need to be something like @daily user /path/to/bin/mailman digests --send where 'user' is the Mailman user as above. That could also go in a file in /etc/cron.d/ Or you could put an executable script to run '/path/to/bin/mailman digests --send' in /etc/cron.daily Your choice. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: spf/dkim/dmarc

by Mark Sapiro

On 5/19/23 09:10, Christian via Mailman-users wrote: > > May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: > to=<billb6951(a)gmail.com>, > relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, > delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host > gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM > domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard > fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: > [192.46.218.224]. To best protect our users from spam and 550-5.7.26 > phishing, the message has been blocked. Please visit 550-5.7.26 > https://support.google.com/mail/answer/81126#authentication for more 550 > 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - > gsmtp (in reply to end of DATA command)) `dig txt lists.ccalternatives.org` reports "v=spf1 a mx ip4=192.46.218.224 -all" It should be "v=spf1 a mx ip4:192.46.218.224 -all" i.e. :, not = > Could the hard fail policy be implicated in the gmail rejection? Yes but only because the ip4 is not effective due to the syntax error. ~all could help, but I suspect replacing the = with : will do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: List mails blocked from GMX - web.de > Spamfolder

by Mark Sapiro

On 7/19/23 10:45, Stephen J. Turnbull wrote: > > % host -t TXT _dmarc.gmx.net > _dmarc.gmx.net descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@gmx.net" > % host -t TXT _dmarc.web.de > _dmarc.web.de descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@web.de" > > The important part is "p=none", which says that GMX does not reject or > quarantine *solely* because of a DMARC fail.[1] Not exactly. These DMARC records specify policies suggested to be applied by any recipient server to mail From: addresses in these domains. They don't say anything about mail To: addresses in these domains From: addresses in other domains. > Footnotes: > [1] IIRC, the "sp=quarantine" means that some fraction of DMARC > failing mail should be quarantined for testing purposes, but the > default fraction is 0 so that is ignored. Actually "sp" is subdomain policy and specifies the policy to be applied to mail From: sub-domains of the main domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Mark Sapiro

On 07/18/2018 02:07 AM, Sebastian Hagedorn wrote: > > I have only now started playing around with Mailman 3.2, because I never > managed to get the earlier releases to work, and reading through the > documentation I thought that such situations could be handled with > Alembic, as described here under "Database Migrations": > > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> > > Is that not the case, and if not, in what cases can or should it be used? Alembic is used by Mailman core to migrate changes in Mailman's data models (database schema). It interfaces with SQLAlchemy <https://www.sqlalchemy.org/> which is used by Mailman core to interface with the underlying SQL database. Alembic is used by mailman developers to create migrations when table and column definitions are modified for some reason. It is not used by end users unless they are actually modifying Mailman's code and database schema. Alembic does not do migrations based on a change in the underlying database engine, e.g. SQLite -> PostgreSQL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

Search results for query "sapiro"