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

[MM3-users] Re: User cannot reset password

by Greg Newby

On Sun, Aug 11, 2024 at 11:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/11/24 10:56, Greg Newby wrote: > > I imported MM2.1 lists to Mailman3 (using import21 - details are in my > > previous messages to mailman-users), and have had a couple of reports of > > people for whom the password reset function via "Forgot password" on the > > list login screen doesn't work as expected. > > > Django (web) accounts (Postorius and HyperKitty) are separate from > Mailman core. Users inported from MM 2.1 do not have web accounts. They > have to sign up, not request a password reset. > 1. Will the new (Django) and imported (Postorius) usernames automatically be matched to the same email address? The goal is for someone to use the web-based front end to manage their migrated subscriptions. 2. How can I customize the email that went to users who selected "Forgot password?" ( You are receiving this email because you, or someone else, tried to access an account with email I didn't find that string in the source code. Thanks as always! ~ Greg

10 months, 3 weeks

[MM3-users] Re: Search problem in 3.2.1?

by Mark Dadgar

On Oct 22, 2019, at 6:44 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/22/19 7:51 AM, Mark Dadgar wrote: >> Anyone seen this before? This is the result of any search query I run. I installed ElasticSearch as the search engine yesterday and this is the result. It is still indexing (large archives). > > > How did you install ElasticSearch. What ElasticSearch version? From .deb, version 5.6.16. > This is a bug in HyperKitty. We've never encountered it, but the code at > <https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/views/search.p…> > only considers the whoosh and xapian backends and needs to be updated > for elasticsearch. I've reported that at > <https://gitlab.com/mailman/hyperkitty/issues/263>. Hmm, maybe I’ll take another shot at getting Xapian running then. Whoosh ran for 5+ days trying to index my archive of 556,000+ messages before I gave up. Thanks for your help, Mark. Much appreciated. If we ever bump into each other here in the Valley, I owe you a beer or 9 for all the value I’ve gotten from mailman over the years. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 8 months

[MM3-users] Re: Moderation Action Changed After Import

by Brian Carpenter

On 2/12/21 4:21 PM, Mark Sapiro wrote: > Yes, You did the right thing. I was mislead by "He said the previous > moderation was the list's default which was hold for moderation." which > is Mailman 3 terminology. > > The list does need to be created first, but it should be a new list with > no members, owners, etc., not an operational Mailman 3 list. > > So, it seems that most of the members of the MM 2.1 list were moderated > and the list's member_moderation_action was Reject. Is this not the case? Sorry for the wrong terminology I can't confirm what was set on the old MM2 list as it is no longer accessible. I am just going on the word of the List Owner. My opinion is that the moderation for those list members were set to Reject on the previous MM2 list. I am mainly interested to see if you know of this happening to anyone else and/or perhaps there is an existing bug that could impact the moderation settings of imported MM2 lists. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Am 2024-04-25 22:03, schrieb Mark Sapiro: > On 4/25/24 12:34, Thomas Stein wrote: >> >> I'm not sure how to add that to my django settings. Adding: >> >> x = list(MIDDLEWARE) >> x.insert(0, 'allauth.account.middleware.AccountMiddleware') >> MIDDLEWARE = x >> >> did not help. Any hints? > > I don't know how things are arranged in the Debian/Ubuntu package, but > you may have a settings.py which at the end does something like > ``` > try: > from settings_local import * > except ImportError: > pass > ``` > If that is the case, adding the above snippet to the end of > settings_local.py should work. Yes, that's the case. I added the snippet in question to settings_local.py but this leads to another error: File "/usr/share/mailman3-web/settings.py", line 503, in <module> from settings_local import * File "/usr/share/mailman3-web/settings_local.py", line 194, in <module> x = list(MIDDLEWARE) ^^^^^^^^^^ NameError: name 'MIDDLEWARE' is not defined dpkg: error processing package mailman3-web (--configure): I hope you can helo again. cheers, t.

1 year, 2 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by mark＠suburbia.org.au

Once again, thanks for taking time to reply. Mark Sapiro wrote: > On 11/18/24 04:12, mark(a)suburbia.org.au wrote: > This should not happen. In the message as delivered to the list what do > you see in the X-Mailman-Rule-Misses: header and the > X-Mailman-Rule-Hits: header if any? ``` X-Mailman-Version: 3.3.8 X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address X-Mailman-Rule-Hits: member-moderation ``` > What if anything is in the lists Accept these non-members setting? Default action to take when a member posts to the list: Hold for moderation Default action to take when a non-member posts to the list: Hold for moderation Emergency Moderation: No Accept these non-members: (none listed) Hold these non-members: (none listed) If you would like me to enable debugging and do another test, I'm happy to. I will admit given the odd behaviour that there's a (small, unexpected) chance that there were settings changed or made during the process by another moderator, but that is not the belief at the moment. cheers, Mark

7 months, 2 weeks

[MM3-users] Re: High memory usage

by Philip Colmer

One small correction: > The largest is 15K messages, then 2K then 1K. That should be *discussions*, not messages. The message count is way higher than the discussion count. Philip On Wed, 16 Feb 2022 at 08:18, Philip Colmer <philip.colmer(a)linaro.org> wrote: > Thank you for the replies from Mark and Stephen. > > One of the reasons why Prasanth & I are concerned with this specific > system is because the first time memory usage crept up, it got to the point > where oomkiller stepped in and, as is usual for that particular mechanism, > one of the processes it killed was sshd, thus removing access to the system > :(. I know that oomkiller can be tuned to stop it killing processes like > sshd but it will, nevertheless, start killing *some* processes if it sees > an out of memory situation. > > So, as Prasanth said, we doubled the memory available and stuck an alarm > on it to trigger when usage exceeded 85% for 5 minutes. I've saved a > screenshot of the monitored memory usage over the last couple of weeks: > > https://1drv.ms/u/s!Aq7dn8GDGLdCodsU-pybJBdckxWU1A?e=BJY1UA > > (It is stored on OneDrive in case you don't recognise the URL format) > > We changed the server on 4th February to the larger memory size. On 11th > Feb, it triggered the alarm and we rebooted the server. Memory usage is > starting to climb again, albeit not at the pace that it was previously. > > What is particularly curious for us is that we have four Mailman 3 > servers. Two of them are single domain and two are hosting two domains. > This server is one of the servers hosting two domains, but it is also the > ONLY one of the four servers exhibiting this memory pattern. By comparison, > the memory usage for the other server hosting two domains looks like this: > > https://1drv.ms/u/s!Aq7dn8GDGLdCodsVyEufkeQqit_cGA?e=ifrJHs > > The biggest difference we are aware of with the "problematic" server is > that some of the list archives are quite large by comparison with our other > servers. The largest is 15K messages, then 2K then 1K. The other three > servers have lists with relatively small archives by comparison (double or > triple digits at worst). > > Finally, and just FYI, we're using PostgreSQL for the database and Xapian > for the indexing engine. > > Regards > > Philip > > On Tue, 15 Feb 2022 at 16:36, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 2/15/22 08:11, Stephen Daniel wrote: >> > TL;DR: quite likely your system has plenty of memory and is operating >> > normally. >> ... >> > On Tue, Feb 15, 2022 at 5:28 AM Prasanth Nair <prasanth.nair(a)linaro.org >> > >> > wrote: >> > >> >> Hi, >> >> >> >> We are having an issue with high memory usage on our Mailman3 server. >> >> Initially, our server had 16GB RAM and the memory usage went up from >> 5% to >> >> 92% within a week. So, we increased the memory capacity to 32GB RAM >> and we >> >> can see that the memory usage is going up in the same pattern. >> >> >> >> Any idea why it is happening? or any suggestions? >> >> >> Just for reference, mail.python.org supports 231 MM 2 lists and 182 MM 3 >> lists with 16 GB of ram and no swap. >> >> The server that supports this list and also the www.list.org web site >> has 4 GB of ram and no swap. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> 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/ >> >

3 years, 4 months

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

by Andy Smith

Hi Mark, On Fri, Sep 30, 2022 at 01:16:10PM -0700, Mark Sapiro wrote: > What is your version of flufl.bounce? I'm using Debian stable, and this is what is packaged: $ dpkg -l | grep flufl ii python3-flufl.bounce 3.0.1-1 all email bounce detectors (Python 3) > I suspect this is https://gitlab.com/warsaw/flufl.bounce/-/issues/12 which > was fixed in flufl.bounce 4.0 and upgrading to 4.0 will fix this. So that probably answers that then. Hmm, I wonder about the best way to proceed. The next stable release of Debian will have something that calls itself 4.0-2 and looks like it is fixed there: https://salsa.debian.org/python-team/packages/flufl.bounce/-/blob/master/fl… so maybe I can ask for that package to be put in stable-backports. I think the other option might be to remove system package python3-flufl.bounce, add it back with "equivbs" so that its system dependencies think it is present and then install the latest one from pip. I'll report the bug in Debian anyway. Thanks! Cheers, Andy

2 years, 9 months

[MM3-users] Re: mailman 3.x upgrade and downgrade

by C. Souza

On Tue, Jul 12, 2022 at 12:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/12/22 6:12 AM, skooperit(a)gmail.com wrote: > > Hi all, > > > > I have a few contradictory questions. > > > > 1. How to upgrade the 3.x version? > > > > 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to > 2.1? > > > > 3. If so, what would be the best way to do that? > > > > > > My mailing list server is running on a CenOS-7x with postgreSQL and the > following mailman packages: > > > > django-mailman3 1.3.5 > > mailman 3.3.2 > > mailman-hyperkitty 1.1.0 > > mailman-web 0.0.3 > > mailmanclient 3.3.2 > > postorius 1.3.3 > > > > We have ~200 lists with more than a decade of history. > > > So you have installed Mailman 3, apparently following > https://docs.mailman3.org/en/latest/install/virtualenv.html. There is a > caveat. Current released versions of HyperKitty (I don't see your > version above) don't work with mistune >= 2.0.0. > > This is https://gitlab.com/mailman/hyperkitty/-/issues/431, fixed by > https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 but not yet > released. > > If your installed mistune is not 2.0.0rc1, you can work around this with > this patch > ``` > --- a/hyperkitty/lib/renderer.py > +++ b/hyperkitty/lib/renderer.py > @@ -4,7 +4,7 @@ from django.conf import settings > > import mistune > from mistune.plugins.extra import plugin_url > -from mistune.scanner import escape_html, escape_url > +from mistune.util import escape_html, escape_url > > > class MyRenderer(mistune.HTMLRenderer): > ``` > Or you can downgrade mistune with > ``` > pip install mistune==2.0.0rc1 > ``` > in your virtualenv. > > To answer your questions, to migrate your lists, you use `mailman > import21` and to migrate archives, `mailman-web hyperkitty_import`. Give > these commands with the `--help` option for more info. > > Downgrading lists from Mailman 3 to Mailman 2.1 is not currently > possible. There is no inverse to `mailman import21`. You can export a > HyperKitty archive as a mbox to use as input to Mailman 2.1s bin/arch. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > 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/ Thanks Mark. You're right it was installed in a virtualenv using pip. I can't see the mistune package, maybe it wasn't a requirement for that version of mm3. 1 Package Version 2 ------------------- ---------- 3 aiosmtpd 1.2.4 4 alembic 1.5.3 5 arrow 0.17.0 6 asgiref 3.3.1 7 atpublic 2.1.2 8 authheaders 0.13.0 9 authres 1.2.0 10 bleach 3.3.0 11 blessed 1.17.12 12 certifi 2020.12.5 13 cffi 1.14.4 14 chardet 4.0.0 15 click 7.1.2 16 cmarkgfm 0.5.2 17 cryptography 3.3.1 18 decorator 4.4.2 19 defusedxml 0.6.0 20 Django 3.0.12 21 django-allauth 0.44.0 22 django-appconf 1.0.4 23 django-compressor 2.4 24 django-extensions 3.1.0 25 django-gravatar2 1.4.4 26 django-haystack 3.0 27 django-mailman3 1.3.5 28 django-picklefield 3.0.1 29 django-q 1.3.4 30 djangorestframework 3.12.2 31 dkimpy 1.0.5 32 dnspython 2.1.0 33 docutils 0.16 34 falcon 2.0.0 35 flufl.bounce 3.0.1 36 flufl.i18n 2.0.2 37 flufl.lock 3.2 38 gunicorn 20.0.4 39 HyperKitty 1.3.3 40 idna 2.10 41 importlib-resources 5.1.0 42 lazr.config 2.2.3 43 lazr.delegates 2.0.4 44 mailman 3.3.2 45 mailman-hyperkitty 1.1.0 46 mailman-web 0.0.3 47 mailmanclient 3.3.2 48 Mako 1.1.4 49 MarkupSafe 1.1.1 50 networkx 2.5 51 nose 1.3.7 52 oauthlib 3.1.0 53 packaging 20.9 54 passlib 1.7.4 55 pip 21.0.1 56 postorius 1.3.3 57 psycopg2-binary 2.8.6 58 publicsuffix2 2.20191221 59 pycparser 2.20 60 Pygments 2.7.4 61 PyJWT 2.0.1 62 pyparsing 2.4.7 63 python-dateutil 2.8.1 64 python-editor 1.0.4 65 python3-openid 3.2.0 66 pytz 2021.1 67 rcssmin 1.0.6 68 readme-renderer 28.0 69 requests 2.25.1 70 requests-oauthlib 1.3.0 71 rjsmin 1.1.0 72 robot-detection 0.4 73 setuptools 39.2.0 74 six 1.15.0 75 SQLAlchemy 1.3.23 76 sqlparse 0.4.1 77 typing-extensions 3.7.4.3 78 urllib3 1.26.3 79 uWSGI 2.0.19.1 80 wcwidth 0.2.5 81 webencodings 0.5.1 82 wheel 0.36.2 83 Whoosh 2.7.4 84 zipp 3.4.0 85 zope.component 4.6.2 86 zope.configuration 4.4.0 87 zope.deferredimport 4.3.1 88 zope.deprecation 4.4.0 89 zope.event 4.5.0 90 zope.hookable 5.0.1 91 zope.i18nmessageid 5.0.1 92 zope.interface 5.2.0 93 zope.proxy 4.3.5 94 zope.schema 6.0.1

2 years, 11 months

[MM3-users] Re: Disable archives per list

by Bernd Wurst

Hello. Thank you for your answers. Am 25.02.21 um 22:01 schrieb Mark Sapiro: > Normally a list admin can select which of the enabled archivers is > active for that list via Postorius. To prevent this, you would have to > modify Postorius. It would be easy enough to just remove settings from > the relevant templates. This will take effect for all lists at once, I suppose. :( > I'm not sure what you mean by "custom archiver settings", but other than > enable/disable and public/private, probably not. Hyperkitty has a rather cool frontend but stores all messages from all lists together in one database table. Additionally, neither Mailman nor Hyperkitty seems to know or tell anything about archive sizes of a list. This is horribly for accounting. So I thought if I can have a separate hyperkitty installation per user without having to duplicate the whole mailman. Alternatively, I'd like to enable archiving only for some customers that buy a suitable plan. I did not really get into mailman plugins. Is is possible for plugins to hook into such settings? I could not really find examples for plugins. regards, Bernd

4 years, 4 months

[MM3-users] Re: ARC

by Marvin Gülker

Am 13. August 2019 um 05:42 Uhr -0700 schrieb Mark Sapiro: > The question is not whether they support ARC, but whether they will > trust you. Well. That's nothing new, given that GMail and Microsoft liberally reject e-mail from small providers for no reason anyway (I have experienced it myself). If this situation doesn't change with ARC, I can live with this (by paying for an SMTP relay provider that proxies my e-mail). However, I thought the entire point in ARC was fixing automatic rejections caused by DMARC invalidation by mailing lists, which are vital for so many open-source projects (including Mailman iself). If ARC falls short of solving that problem, because the large providers do not automatically trust ARC, then supporting ARC on my mailing list server is kind of void. Why should almighty Microsoft trust my small personal mailing list server? ARC can only achieve its goal with black-listing untrusted relays rather than white-listing known good ones, because it is simply unfeasable to manually maintain a list of all open-source project mailing lists in the entire world. I could set a new one up tomorrow, how should you know? -- Blog: https://mg.guelker.eu

5 years, 10 months

Search results for query "sapiro"