Search results for "Postorius" - Mailman-users

Re: Problem updating mailman

by Brian Carpenter

Mark Sapiro wrote: > On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't > > remember consciously > > installing that because it was never in the guide I followed (which is your > > own writeup). > > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update > > > > '[' False == False ']' > > mkdir -p /opt/mailman/mm/static > > /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > /opt/mailman/mm/bin/django-admin compress > > CommandError: An error occurred during rendering > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > > /bin/sh: sass: not found > > > > You can't just uninstall rubygem-sass. You have to replace it. Here's > one recipe for Ubuntu > cd /usr/local/lib > # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the > # appropriate version. > wget > https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5-... > sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz > sudo chmod -R o-w dart-sass > sudo ln -s dart-sass/sass /usr/local/bin/sass > rm dart-sass-1.32.5-linux-x64.tar.gz > Then you should see the command > sass --version > prints > 1.32.5 > Then, because dart-sass doesn't recognize the short form -t option for > --style, you have to edit your settings(_local).py and change > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > to > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass --style compressed {infile} {outfile}'), > ('text/x-sass', 'sass --style compressed {infile} {outfile}'), > ) I had to do a new installation of Mailman 3 with Postorius/Hyperkitty today and these directions were very helpful. Thank you, Mark.

5 years, 4 months

Re: Template for Password Reset Email

by Mark

On 2024-11-18 01:38, Mark Sapiro wrote: > On 11/17/24 16:57, Mark wrote: >> >> I can see the French text for the "Password Reset Email" in the >> django.po file. And running the compilemessages command reports the >> "django.po" for French is okay and up to date. Should I be recompiling >> the ".mo" file? > > No, It's fine. The issue is the language context for this message has > nothing to do with any Mailman list's preferred language. > > Again, see > https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… > > If all the lists on your server are French, you could set > > LANGUAGE_CODE = 'fr' > > in your Django settings. Otherwise, the user's browser has to include > an Accept-Language: header specifying French as the most preferred > language in it's request. > > Also note the ordering of SessionMiddleware, LocaleMiddleware and > CommonMiddleware in the above doc. I have recently updated the various > places where we suggest or supply MIDDLEWARE settings, but you may > find that your settings have LocaleMiddleware after CommonMiddleware > and you should fix that. It's just the one list that is using French. Others are in English I've edited the order of the middleware settings in this file ... /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/settings/base.py I reordered as below, restarted everything but no joy :-( ... at Line 76 ... MIDDLEWARE = ( 'allauth.account.middleware.AccountMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.middleware.common.CommonMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ... I'm thinking this is not the file I'm looking for. Apologies for my cluelessness here.

1 year, 6 months

Can creating too many Django accounts crash Mailman3 server?

by Stephen J. Turnbull

Mohsen Masoudfar writes: > It seems anybody can go to the site: > https://LISTSERVNAME/mailman3/postorius/lists/ > and click on the [Sign up] on the top-right corner and create an > account. Yes. > This can easily be automated, even though the next step, confirming > the email address, being ignored. I believe it can be used as a > target for a DOS attack by creating so many accounts, that > eventually causes an 'out of space' error. > > Is this a justified concern? "Justified" depends on who you think the attacker is. Theoretically it's a real possibility, but the space used by an unverified account is not large. I suspect there are always much more painful DoS attacks to worry about. > Is there a way to manage this feature in a secure way? In some sense, I don't think there is. The point of the feature is to allow anybody to sign up without authentication beyond having a usable email address. Either you allow the DoS attack or anything you do is likely to deny service to legitimate users. Brian's approach (cron job purging unverified users) is generally good hygiene, but I don't think it would do much against an deliberate attack. And it shouldn't be hard to automate the confirmation process. I guess you could handle that by purging accounts with no subscriptions or other roles on any lists, but that might annoy a few legitimate users. Probably the best you could do for an open server would be to throttle user creation to say 1 per minute (adjustable to the scale of your site). I don't know if there is currently a way to require admin approval for account creation (as opposed to list subscription). Perhaps we should add that if we don't have it. Steve

5 years, 8 months

Mailman 3 deployment: ok to use same database instance for core, web, and hyperkitty tables?

by Stephen J. Turnbull

Hi Serban, s.dobrau(a)ucl.ac.uk writes: > We are currently working on a migration plan for Mailman -> Mailman > 3. We have around over 3000 mailing lists with a total of 50K > members Medium-size. I guess a 2-CPU/4GB Linode or similar should handle the Mailman load (including Postorius and HyperKitty), you might want more memory and maybe more CPUs if you're running the RDBMS on the same host. In the 23k lists/50k users/100k inbound messages/day migration described below, we ended up reconfiguring the VMs 3 times before declaring the system stable. IMO the 2 x 8CPU/16GB final setup was way overpowered for the need, but we didn't try to calibrate finer than that. > and 500 worth of archived data. 500 whats? 500MB, 500GB, 500TB? Assuming 500GB, > Our plan is to have core+web (instance 1) and Hyperkitty (instance > 2). With the archives on the FS local to the Hyperkitty. The archives are in the database as BLOBs. There's no reason to have a separate instance for HyperKitty. It's not obvious to me that you need more than that 2x4 Linode for both Mailman and RDBMS, but if you're going to split it's Mailman vs RDMBS, not Mailman vs HyperKitty. > And all 3 tables (core, web, Hyperkitty) pointing to the same > database on a remote SQL (mysql-enterprise) instance. Using class > mailman.database.mysql.MySQLDatabase (and whatever necessary on the > Django/Hyperkitty instance). Make sure your MySQL database(s) for Mailman are configured with the utf8mb4 option for 4 byte UTF-8 support, or it will choke on emojis and the like. I don't think there are any other gotchas for MySQL. Note there are a lot more than 3 tables in Mailman's databases. The "traditional" configuration is a "mailman" database for core and a "mailmanweb" database for Django and the archives, but Mark says that as the tables are disjoint across Mailman, Django, and the archives there's no reason not to use a single "mailman" database for all of them. I believe that's how this list's host is configured. > Is this feasible, Yes. > if so what would be the recommended compute/storage > requirements. I would start with the spec above (2CPU/4GB). If that doesn't perform, bump it to taste. Mailman itself uses about a GB of RAM for all its runner processes. (I'm not a cloud expert, I just assume you can do that the way we did, very simply.) The Python code (including compiled .pycs) is about 300MB. The database storage requirements are nominal for Mailman and Django (maybe 100MB total in the database for a 23k lists, 50k users installation I worked on recently), and I think the database usage for the archives was approximately 1:1 vs. the Mailman2 mboxes. Mark may have a better estimate on that. There is also the full-text search index for the archives. I recommend Xapian, in my experience Whoosh is really slow.[1] I don't recall offhand how big those were but I would assume they're no smaller than 1/10 the size of the mboxes, and maybe quite a bit bigger. Importing list configurations, users, and subscriptions into Mailman 3 is pretty fast, as long as you're not using the stock Postfix support.[2] The problem is that generating the Postfix alias files for the lists seems to be noticably linear in number of lists, which means it's quadratic for the mass import. IIRC with 5000 lists you'd be looking at >1m/list just to keep regenerating Postfix's alias database, ie 5000 minutes. I found two solutions, both of which required patching Mailman. I hope to get both into the next release. I think we got it down to <5s/list, for 5000 lists that's < 1hr. Importing archives is ... yeeech. The client decided they didn't want a ton of archives anyway (you know corporations, if it's not required by law, shred it after 6 months). I don't recall the size estimate accurately but we kept 6 months X 4500 lists, maybe 100GB out of 2.3TB of mboxes. That took 24 hours to import into HyperKitty, without doing the full-text indexing. I do know the original conservative estimate was 20 days to import the whole 2,3 TB. The full-text indexing took more than a week if I remember correctly. The easiest thing to do is to just do no migration, keep the old archive online, and start populating the new archive when you switch over. It's possible to do both the HyperKitty import and full-text indexing incrementally with a bit of planning. It's also quite possible to migrate incrementally, a few lists at a time. Mailman 2 and Mailman 3 can coexist happily on the same host. Mark can advise on that, I think. The only other advice I remember offhand is that Mailman's outgoing smart host should be in the same datacenter as Mailman. We never did debug it, but the system described above with 23k lists had problems with the out queue stalling when smtp.client.com resolved to a different datacenter 500km away. :-) The problem went away as soon as they pinned the MX to the MTAs in the same datacenter. Footnotes: [1] If you're familiar with another full-text search engine, check the django-haystack docs. Haystack supports several other engines, your preference may be among them. [2] Exim4 does not have this problem. I don't know about other supported MTAs.

2 years, 7 months

Ansible role to install Mailman3

by samuel.d.darwin＠gmail.com

Hi, Before installing the Mailman Suite, I searched on https://galaxy.ansible.com/ for Ansible roles that might automate the whole process. https://github.com/galaxyproject/ansible-mailman3 turned out to be quite good. However, it was slightly out-of-date. I cloned it, made a few bug fixes, and corrected linting errors. Then, going further, added optional basic installations of Nginx, Postfix, PostgreSQL into the role. If anyone is installing Mailman they are welcome to try it out. https://github.com/cppalliance/ansible-mailman3 Now, I see there was a discussion on this very list about https://github.com/rivimey/ansible-mailman3 which was also a fork of natefoo's repo. What are the differences? As Stephen Turnbull wrote: "her (rivimey's) setup may be more complicated than most folks need (IIRC, she has a multi-homed setup with Mailman core, Postorius, and HyperKitty on three separate IPs on a separate subnet in the DMZ, while Mailman was really designed for three Mailman applications running on the same host, along with the database server and MTA)." My version of the role didn't follow the tactic of "three separate IPs on a separate subnet in the DMZ". Mainly, it adds postfix and postgres. Fixes small errors. Also, in a git branch of the repository named mailman3-core, I removed all the web code, so there is a version of the role that only installs core. We will use that while bundling the web components into another Django app, already deployed with docker. There is an open question about maintenance. Among the three roles mentioned here, which is being actively kept up-to-date? Perhaps there are no guarantees from any of them. At this instant in time, https://github.com/cppalliance/ansible-mailman3 is the most recent. Would it make sense to mention these roles in the official documentation? Not sure. Installing mailman3 is complicated and because of that, is a good fit for Ansible.

2 years, 10 months

Re: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > I don't understand the question? Are you asking why the log contains > "invalid FilterAction: discard. Treating as discard"? If so, that's a No, that was just log messages I thought would help explain the problem. > If you are asking why the message is empty after filtering and > discarded, It is presumably because it is a text/html message as opposed > to a multipart/alternative message with text/plain and text/html > alternative parts. The Content-Type of the mail sent to the list is multipart/mixed From: SENDER <sender(a)senderdep.example.com> To: "LISTNAME(a)lists.example.com" <LISTNAME(a)lists.example.com> Subject: =?utf-8?B?QW50cm9wb2xvZ2VyIGkgcHJha3NpczogVGlsbWVsZGluZyDDpWJlbg==?= Thread-Topic: =?utf-8?B?QW50cm9wb2xvZ2VyIGkgcHJha3NpczogVGlsbWVsZGluZyDDpWJlbg==?= Thread-Index: AdT/QIb18JA+6hcSTYycFCI+5NuYoQEwPZ/Q Date: Mon, 6 May 2019 13:53:23 +0200 Message-ID: <250E794B36C1E646AF3D81E1F15348C79DA8CA83(a)P2KITMBX06WC03.unicph.domain> Content-Language: en-US X-MS-Has-Attach: yes X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: Content-Type: multipart/mixed; boundary="_006_250E794B36C1E646AF3D81E1F15348C79DA8CA83P2KITMBX06WC03u_" MIME-Version: 1.0 > There are list attributes filter_types and pass_types (also > filter_extensions and pass_extensions, but those probably aren't My Python isn't that great, but this looks like i'm missing something >>> m.filter_content True >>> m.pass_types <generator object pass_types at 0x7f66d407bba0> >>> m.filter_extensions <generator object filter_extensions at 0x7f66d407bdb0> m.pass_extensions <generator object pass_extensions at 0x7f66d407be08> > Presumably, the combination of filter_types and pass_types is not > allowing text/html. I am thinking that as the "Filter content" (postorius) refers to "the settings below", this setting is needed in case list admin wants an explicit reply-to address or change other switches in Alter Messages. But this shouldn't affect the content, even it is text/html, I think, at least not emptying the mail, I think. > You need to examine these settings in mailman shell, e.g. > > list(m.pass_types) >>> list(m.pass_types) ['multipart/mixed', 'multipart/alternative', 'text/plain'] -- Henrik Rasmussen

7 years, 1 month

Re: Two Questions: One General, the Other Specific

by Brian Carpenter

On 2/26/21 12:10 PM, David Wilson wrote: > For context, I have been lurking on this site for a number of years > now, in order to track the progress of this wonderful mailman3 project. > > Further context, I am chair of a 66 unit condominium and pay for two > lists provided by EMWD.com and get a hands on feel from an mailman3 > operations perspective. > > *Is there another site that might best communicate the future goals, > plans, objectives, and time frames for mailman3 or is the status of > the project at the state of being primarily reacting to problems, as > evidenced in this problem solving forum, at least as it seems to me, > with no offense meant or intended?* > > Something I find surprising is a problem described in an image grab > below relating to an inability to amend a list entry to include a name > to be associated with an email address, as if the data needs to be > immutable. When a workaround was unsuccessfully explored to delete > the entry and then resubmit an amended entry but with the same already > deleted email address, that was still refused, presumably because of > pointers to archived data don't permit, but this seems like a > particularly onerous restriction, or perhaps even a bug, or at least a > severe design constraint. *Is this item on an existing to do list?* The server that David's lists is on, is running the latest stable versions of Mailman 3, Postorius, and Hyperkitty in case that helps. @David, we have the issue that you ran into mitigated to a great extent with our Affinity user interface. Just contact me via our support ticket system if you want to explore have your lists migrated to our Mailman 3 Affinity platform. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

Re: Changing web access

by Ralf Wiegand

Thank You - that helped. tcp 0 0 192.168.0.27:8001 0.0.0.0:* LISTEN 2054/python tcp 0 0 192.168.0.27:8000 192.168.0.174:50348 ESTABLISHED 2108/python but I am getting : mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'localhost\', port=8001): Max retries exceeded with url: /3.0/lists?advertised=true&count=0&page=1 (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection object at 0x7f88fe4cb4e0>: Failed to establish a new connection: [Errno 111] Connection refused\',))",),)') when starting "python manage.py runserver 0.0.0.0:8000" Sorry for all the questions, it isn't easy to put this together. greatly appreciate your help. Ralf On 4/22/20 12:40 PM, Abhilash Raj wrote: > On Wed, Apr 22, 2020, at 7:22 AM, Ralf Wiegand wrote: >> Hello Members, I am testing mailman3 in a test environment. >> >> python manage.py runserver >> Performing system checks... >> >> System check identified no issues (0 silenced). >> April 22, 2020 - 14:13:57 >> Django version 2.2.12, using settings 'settings' >> Starting development server at http://127.0.0.1:8000/ >> Quit the server with CONTROL-C. >> >> tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN >> 6497/python >> tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN >> 6404/python >> >> >> How can I change this to have access from any host on my local network. >> The server running mailman3+hyperkitty+postorius is a rhel7 server >> without a GUI interface. I also need to give access to our developer on >> the same subnet. > Have a look at the docs for `runserver`: > > https://docs.djangoproject.com/en/3.0/ref/django-admin/#runserver > > You basically need to run: > > python manage.py runserver 0.0.0.0:8000 > > >> Thank You, >> >> Best regards, >> >> Ralf Wiegand >> >> _______________________________________________ >> 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/ >>

6 years, 1 month

Re: Link to account

by Lars Bjørndal

Thanks a lot. Maybe I've done a mistake, it doesn.t work. At the bottom of /etc/mailman3/settings.py I have: ROOT_URLCONF = 'urls' `cat /etc/mailman3/urls.py` [...] urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('lists/mailman3/', include('postorius.urls')), path('lists/archives/', include('hyperkitty.urls')), path('lists/', include('django_mailman3.urls')), path('lists/accounts/', include('allauth.urls')), path('lists/admin/', admin.site.urls), ] In Apache config for the domain, I now have: <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "lists/mailman3" "http://127.0.0.1:8000/lists/mailman3" ProxyPass "lists/archives" "http://127.0.0.1:8000/lists/archives" ProxyPass "lists/accounts" "http://127.0.0.1:8000/lists/accounts" ProxyPass "lists/admin" "http://127.0.0.1:8000/lists/admin" ProxyPass "lists/user-profile" "http://127.0.0.1:8000/lists/user-profile" </IfModule> Restarted mailmanweb, httpd and mailman3. If I go to list.punktskriftutvalget.no/mailman3/, I get a 404 Not Found response in browser. So what's wrong, do you think? Thanks Lars On Tue, Apr 11, 2023 at 10:52:47AM -0700, Mark Sapiro wrote: > On 4/11/23 10:46, Lars Bjørndal wrote: > > Hi, list! > > > > On one of my sites, I want to have all Mailman3 links to go under > > /mailman3. Even though, the Login link goes to a URL like: > > > > https://list.punktskriftutvalget.no/accounts/login/ > > > > How can I ensure it goes to > > https://list.punktskriftutvalget.no/mailman3/accounts/login/ > > > See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

3 years, 2 months

Re: Hyperkitty performance problem

by Tobias Diekershoff

Hey all, so far we could not find the reason behind the problem. However while reviewing the installation process one one our team mentioned that he read the installation instructions for Hyperkitty different then the rest of the team. Are Mailman3/Postorius and Hyperkitty supposed to run in separated databases, or are they supposed to use the same database? Thanks in advance for clarification! Tobias On 06.11.24 08:18, Tobias Diekershoff wrote: > Hey all, > > last week we caught some AI bots causing high LOAD on our mailman3 > servers archive, that we blocked with nginx rules. > > I'm not sure if it is related to this incident, but we noticed this > when analyzing the log files at the time. In the mailman.log > hyperkitty is listed 10k times and more to archive a single mail over > the time of 2h, seemingly all with the same process ID > > > (1186) HyperKitty archived message [...] > > The mailman3-web.log has matching log entries that the mail was archived > > > hyperkitty.views.mailman Archived message > > every 0.5 seconds. > > In the web interface to the archive, the mail is only listed once though. > > My suspicion is, that these archiving processes are now overloading > the system, preventing a timely catching up work of the queued > messages. I could not find anything in the Mailman3 nor Hyperkitty > documentation to better distribute the system resources to the Mailman > runner or prevent Hyperkitty to restart archiving a mail over and over > again. > > Any hint about where to look for the reason of this is highly > appreciated. > > Best, > Tobias > -- Tobias Diekershoff >>> System Hacker Free Software Foundation Europe Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290 Registered at Amtsgericht Hamburg, VR 17030 | fsfe.org/support OpenPGP-Key ID ... 0x25FE376FF17694A1 Fingerprint ...... 23EE F484 FDF8 291C BA09 A406 25FE 376F F176 94A1

1 year, 6 months

Mailman-users search results for query "Postorius"