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

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Jered Floyd

I believe this is correct, and will need to be fixed on the Mailman side. The practical effects seem to be -- for me at least -- that any of the pages for social logins fail to receive any template styling. --Jered ----- On Nov 8, 2023, at 10:01 AM, Jeremy Stanley fungi(a)yuggoth.org wrote: > On 2023-11-07 19:46:01 -0800 (-0800), Mark Sapiro wrote: > [...] >> I don't think this is fatal, but I have reported it at >> https://github.com/pennersr/django-allauth/issues/3513 > > We've been seeing the same thing in our deployment, I just hadn't > found the time to look into it yet. Looks like upstream won't-fixed > it, so I guess it was an intentionally backward-incompatible change > and the template files will need some minor reworking? > -- > Jeremy Stanley > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years, 10 months

[MM3-users] Re: CPU usage when idle

by roughnecks

Il 28/05/2025 23:42, Mark Sapiro ha scritto: > On 5/28/25 08:27, roughnecks via Mailman-users wrote: >> >> It's the manage.py qcluster whatever is called. I have shut down MM >> for the time being, because I'm not fully motivated to have it >> running, so I can't be more accurate right now. > > I don't know how qcluster is configured in the Debian packages (which > are out of date and possibly buggy anyway). You may be using django-q > <https://django-q.readthedocs.io/en/latest/> and if so, you should > migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both > typically use memcached as a backend. I wouldn't know how to migrate and if that means doing anything not in the debian-way (haven't opened any link so far). About qcluster configs, yes, all correct but there is no configuration for caches, so probably it's the default one you specified. I can look into this. > You can get info about what qcluster is doing with `manage.py qinfo` and > monitor things with `manage.py qmemory` and `manage.py qmonitor`. Thanks, helpful.

1 year, 4 months

[MM3-users] Re: Multiple domain problem

by Lars Bjørndal

On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > I have lists on two domains, example1.com and example2.com. The mail > > interface works perfectly. However, connecting a browser to > > example1.com, I get the title List index - example1.com, and the web > > interface seems to work fine. > > > > If I connect to example2.com, the title is example2.com, without the > > preceding List index. And the body says Page not found. > > > What's in the browser's address bar for that page? It's https://example2.com/mailman3/lists/ For the domain that works, it is https://example1.com/mailman3/lists/ Please note that I've changed mailman to mailman3 for the complete installation. > What's in Postorius domains view? I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). > What's in the Django admin sites view. Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. Thanks Lars

3 years, 8 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 23 jan 2024, om 19:09 heeft Mark Sapiro <mark(a)msapiro.net> het volgende geschreven: > > On 1/23/24 05:49, Marco van Tol wrote: >> Small unfortunate twist, this leads to: >> --- >> [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... >> --- >> I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? > > This issue is discussed at <https://github.com/notanumber/xapian-haystack/pull/181>. > There are two patches for this issue. They are somewhat different approaches, but either one is OK. One patch is the one in the above PR <https://github.com/notanumber/xapian-haystack/pull/181/files>. The other is at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…>. > > I use the one from the PR, but it requires a substitution `s/force_text/str/`. Hi, thanks! Just to double check, do you mean `str` or `force_str` in the substitution? I found a comment on this topic regarding django-4 where they advice to use force_str. https://stackoverflow.com/questions/70382084/import-error-force-text-from-d… Thanks! Marco van Tol

2 years, 8 months

[MM3-users] Re: Hyperkitty error - not archiving

by Odhiambo Washington

On Sat, Jul 26, 2025 at 8:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/25 1:23 AM, Odhiambo Washington via Mailman-users wrote: > > I am seeing the error below and wondering what's the cause: > > The message has some issue which is causing HyperKitty to not be able to > archive the message. The message will be queued in Mailman's > var/archives/hyperkitty/spool/ directory and can be examined with > `mailman qfile`. If you do that and the cause is not clear, you can post > the message, and we will investigate. If the message is unwanted, you > can just remove the file from Mailman's var/archives/hyperkitty/spool/ > directory. > I had examined the message using 'mailman qfile', but did not see anything obvious. There were 3 files inside the spool/ directory. I have just checked again and they are no longer there. -- 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: Mailman3 reinstall fail, need some help

by Yvan ♞

Finally succeed to reinstall with a very precious help !!! /etc/mailman3 folder was removed before the mailman3 package was supressed, apt noticed it and he believed that it was a modification of the configuration of mailman that was wanted, so each time the debian mailman3 package was reinstalled, he did not put the conf in /etc/mailman3, which caused the package installation to crash, and therefore the app install on ynh Le 03/04/2022 à 12:53, Odhiambo Washington a écrit : > On Sun, Apr 3, 2022 at 12:06 PM Yvan ♞<elemac(a)free.fr> wrote: > >> Hello every body >> I have progress to try to reinstall mailman3 on yunohost server but I >> still have an error, if somebody can help me as I don't understand the log >> https://paste.yunohost.org/raw/ugijepuyuv >> Sincerely. >> Yvan >> > Hi Yvan, > > As previously advised by Mark Sapiro, you are better off taking to the > YunoHost support people for help. > They will most likely help you with the failing dependencies issue. > > But I also wonder - why don't you follow the virtualenv method to install? >

4 years, 6 months

[MM3-users] Re: Postfix SMTP REJECT non-subscribers

by Matthew Blissett

On 11/07/2024 04:11, Mark Sapiro wrote: > On 7/10/24 12:26 AM, Matthew Blissett via Mailman-users wrote: >> >> With Mailman 2, I have configuration and scripts to reject >> non-members from posting to lists _during the SMTP connection_. This >> is better than bouncing (no backscatter), better than discarding >> messages (the user finds out) and better than moderation (spammy >> messages aren't forwarded to external email systems). >> >> >> The configuration and scripts are described here: >> https://code.launchpad.net/~jimpop/mailman/check_subscriber >> >> >> Is anything like this built-in to Mailman 3? I cannot find it in >> Gitlab. > > No. nothing similar is built in to Mailman 3, but it shouldn't be > difficult to implement. It could be done with a milter as in the above > implementation, or it could be done by modifying the _handle_RCPT > function in mailman/runners/lmtp.py to check if the sender is a member > of the recipient list. Thanks. I have implemented it by adapting the Mailman 2 script to use the REST API of Mailman 3: https://gist.github.com/MattBlissett/c1f58dcc182423f48e2305b3d91ea44d -- Matt

2 years, 3 months

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

by Mark Dadgar

On Nov 10, 2020, at 1:40 PM, Mark Sapiro <mark(a)msapiro.net> 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. Great explanation - thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 11 months

[MM3-users] Re: Howto discard all pending unsubscription requests in a list?

by Andreas Vetter

On Tuesday, 19 May 2026 20:15:47 CEST Mark Sapiro wrote: > On 5/19/26 2:54 AM, Andreas Vetter wrote: > > Is there a script to discard all tose requests and get the members back on > > the list? > > A mailman shell interaction like this should do it. > > $ mailman shell > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > > >>> pendings = getUtility(IPendings) > > >>> for token, data in pendings.find(pend_type='unsubscription'): > ... if data and data['list_id'] == 'the_list.example.com': > ... pendings.confirm(token, expunge=True) > ... > > >>> commit() > > In the above, replace the_list.example.com with the actual list_id (the > list posting address with '@' replaced with '.') > > If there are no other lists with pending unsubscriptions, you can omit > the `and data['list_id'] == 'the_list.example.com'` check. This works like a charm. Thanks a lot, Andreas

4 months, 4 weeks

[MM3-users] Re: Footer from templates not working - DB issue?

by Hans Mayer

Hi Mark, many thanks for this hint. I updated table "template" and replaced "localhost" with the real name and it worked. // Hans -- On 25.09.22 19:28, Mark Sapiro wrote: > On 9/25/22 05:26, mailman--- via Mailman-users wrote: >> Dear All, >> I have a similar issue. Also on Debian 11. Also installed as Debian >> PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) >> I am using sqlite3. When I do the SQL-query I get an URI which is in >> multiple reasons wrong >> http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… >> > > The initial part of that URL is set from the Django setting > `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to > `http://localhost/mailman3/`, it should probably be just > `http://localhost/`. > > >> OK - the hostname could be changed but the path is not existing at all. >> There is no file "list:member:regular:footer" on the complete >> filesystem. > > It's not a file. It refers to an entry in the postorius_emailtemplate > table in the database which is retrieved via the Postorius API. >

4 years

Search results for query "sapiro"