Search results for "2021" - Mailman-users

Re: How to modify system preferences

by Allan Hansen

The other way is to tell all your users to use gmail, as that is how they handle messages from email lists, no matter how much I and others have complained to them about it. :-) Yours, Allan Hansen hansen(a)rc.org > On Feb 19, 2021, at 9:50 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/19/21 5:15 AM, Jack Lenox via Mailman-users wrote: >> >> The documentation states that these are only accessible in a read-only >> format via the REST API, but presumably there is a way of modifying >> these somewhere? I can't find a way of specifying this in my config and >> can't find a relevant example in the sample schema.cfg. >> >> At this stage, all I want to do is set the default for >> "receive_own_postings" to False. Can anyone point me in the right >> direction here? > > > The defaults for settings like this are not directly configurable. You > need to patch the relevant entry in mailman/core/constants.py > > I have just filed <https://gitlab.com/mailman/mailman/-/issues/832> for > this. > > -- > 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/

4 years, 4 months

Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 5 Nov 2021, at 6:30 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: > Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. Thanks for filing the issue. I'll work on a solution. My current thinking is to add a `count` column to the message table, set the count to 1 when initially adding a message-id, increment the count when adding an existing message-id, decrement the count when deleting a message-id and only delete the entry and message when the count reaches 0. That should work well. I’m happy to do some testing of any patches you create in our test environment if you need extra testing. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> —Simon

3 years, 8 months

Re: Mixing Mailman 3 with AWS SES

by Jim Popovitch

On Wed, 2021-03-24 at 10:57 -0700, Mark Sapiro wrote: > On 3/24/21 7:58 AM, Brian Carpenter wrote: > > On 3/24/21 9:54 AM, Ralph Weber wrote: > > > Comments received directly from one of the people who developed the > > > AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively > > > established that AWS Mailman is *not* intended to interact with AWS > > > SES when receiving email messages > > > > I don't think there is a Mailman 4 and the person who is marketing his > > services under that name is sending a confusing message to the public. > > Danil Smirnov owns both the mailman3.com and mailman4.com domains. > Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". > In response to our request, the following is included at the bottom of > <https://mailman3.com/>;: > > Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain > used to coordinate development of the Mailman 3 free software suite. The > Mailman 3 core developers are not involved with Mailman3.com, and cannot > answer any questions or provide any support related to its operations. > If you are looking for resources for development of the Mailman 3 free > software suite, please see mailman3.org. > > Yes, this is all ripe for confusion ... Just to add, Danil also owns mailman2.com, and I own (and parked) mailman2.org. -Jim P.

4 years, 3 months

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Lars Schimmer

On 26/02/2021 00:55, Brian Carpenter wrote: > I have finished my how-to install Mailman 3 on Debian 10 completed to > the point where you can use it to get a fully functional Mailman 3 > environment up and running. This is a comprehensive guide that walks you > through installing EVERYTHING (currently!) that Mailman 3 needs to run. > It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have > not added the update directions yet but will very soon. I also plan on > adding a section on setting up DKIM and Xapian with Mailman 3. > > I hope this helps those who wish to get a Mailman 3 server up and > running quickly and brings a sense of sanity to the confusion regarding > the various documentation out there concerning the installation of > Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20 > at some point. > > Without further ado: > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > I am sure the above guide can use improvements. Feel free to contact me > off-list to point out mistakes/improvements, etc. > Hm, it completely ignores the standard way for Debian: apt-get install mailman3-full also exim4 as standard mailer. And apache2. But thats just my 2 cent. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years, 4 months

Re: Core, Hyperkitty and Postorius releases

by Abhilash Raj

On Thu, May 13, 2021, at 7:18 AM, Torge Riedel wrote: > Am 03.02.21 um 02:59 schrieb Abhilash Raj: > > Mailman Core 3.3.3:https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs… > > Postorius 1.3.4https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4 :https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Dear MM3 releasers, > > after successful update to latest versions I realized that Mailman Core > change log links are stable (I requested this some time ago and it was > changed - thanks for that), but Postorius and Hyperkitty change logs do > not have stable header ids. > > Can this be changed too? > > It makes it easier for me (and hopefully for others) when communicating > changes to the users. At the moment they see the upcoming changes for > Postorius first, which always introduces confusion for some of them. > The stable headers are sometimes missed when creating a new NEWS section. There isn't an automation that I've found to add a new section in the news.rst file yet which will do that for me. So I just forget sometimes :-) Adding headers is a trivial thing though. If you find one missing on any project please feel free to submit a MR to fix that. It can be done after the release has been made too. See this[1] that Mark just made to fix it for Postorius. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/636/diffs -- thanks, Abhilash Raj (maxking)

4 years, 1 month

Re: Mailman 3 Installation

by Andreas Barth

* Mark Dadgar (mark(a)pdc-racing.net) [210117 20:27]: > On Jan 17, 2021, at 11:01 AM, Andreas Barth <aba(a)ayous.org> wrote: > Did you document it anywhere? I could not find evidence of a successful migration when I looked 6 months ago, including in this list’s archives. > > That would be great information for the community, if only as a cautionary tale. Stop all external connections to your systems for the whole migration. Loading the database with any of the tools from postgresql in a fresh database, e.g. pgloader. Setting up another database and dump both databases. Merge the data from the pgloader-database and structure (sequences etc) from the new database. Happy fixing of anything not loading into yet another database ( = the actual database), e.g. broken tables - especially the tables with intervals won't load without manual action. And make sure at least this database has encoding UTF8 (and especially not SQL_ASCII). E.g. by adding -E UTF8 to the createdb call. Or call your createcluster with e.g. --locale de_DE.UTF-8. That's recommended also if you start directly with postgresql as backend BTW :) And then, just look where you get exceptions and keep on fixing until there are no anymore. And continue to look at your logfiles. Reenable connections sometimes during that and see what great exceptions can happen if e.g. lmtp doesn't recognire an list because there are non-ascii characters somewhere and your locale is broken (see above). Or just avoid all of that and start directly with postgresql. Regards, Andi

4 years, 5 months

Re: A new issue with installation

by Brian Carpenter

On 2/20/21 12:35 PM, Abhilash Raj wrote: > Also, it is possible depending on your distro that packaged Rust compiler > is too old. cryptography requires a more recent version of Compiler, 1.45 > is the min supported version I think. > > FAQ:https://cryptography.io/en/latest/faq.html#installing-cryptography-fails-with-error-can-not-find-rust-compiler > > You can skip the Rust components by setting `CRYPTOGRAPHY_DONT_BUILD_RUST` > but that would work just for this release and you won't be able to > skip from the next release of cryptography. I am going to need further assistance here. It is easy enought to install the rust compiler using rustup but I am still getting the same error: =============================DEBUG ASSISTANCE============================= If you are seeing a compilation error please try the following steps to successfully install cryptography: 1) Upgrade to the latest pip and try again. This will fix errors for most users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip 2) Read https://cryptography.io/en/latest/installation.html for specific instructions for your platform. 3) Check our frequently asked questions for more information: https://cryptography.io/en/latest/faq.html 4) Ensure you have a recent Rust toolchain installed: https://cryptography.io/en/latest/installation.html#rust 5) If you are experiencing issues with Rust for *this release only* you may set the environment variable `CRYPTOGRAPHY_DONT_BUILD_RUST=1`. =============================DEBUG ASSISTANCE============================= error: Can not find Rust compiler Running root@list:/opt/mailman/mm# rustc --version returns: rustc 1.50.0 (cb75ad5db 2021-02-10) I am doing this as the mailman user using a virtual environment. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Mark Sapiro

On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py… is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py… and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote: > > If the manage.py in the directory in which you ran this is the > correct one for your Mailman Django project, I don't know why it > didn't work. Me neither :-( That's why I asked, and probably Guillermo, as well. > Is your Mailman installed in a virtualenv? If so, was the virtualenv > activated? No virtualenv. Mine is deployed using system python on a CentOS 7 system, toghether with another in house developed low requirements Django project, both served by uWSGI vassals. And then, all of a sudden, while I was writting this, it dawned on me! Postorius, Hyperkitty and django-mailman are installed with pip, so, the end up in the site-packages directory (usually /usr/local/lib/python3.x/site-packages), but, normally, django projects are deployed somewhere in the web server hierarchy (/var/ww/django in my case, due to old personal tastes), and applications properly defined in the settings.py for the project. So, the message files are out of reach for manage.py. Changing to /usr/local/lib/python3.x/site-packages/X (with X being postorius, hyperkitty and django_mailman3) and using django-admin compilemessages all works! Thanks for pushing my thoughts in the right direction! -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 4 months

Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:36 -0800, Mark Sapiro wrote: > > Why do you say the .mo files are old. The timestamps are all Feb 3 > 02:47 which is when the package was built for PyPI. Because my brain goes faster than my fingers and I say the reverse of what I mean. I meant .mo files, all .po where properly dated, and I reversed the meaning of my thoughs while typing. Thanks for brining my confussion to my (and everybody's) attention, and my appologies for the noise. > When things are changed on weblate, we get automatically generated > merge requests to update our source. We don't always merge them > immediately, but we certainly do merge all the outstanding ones > before making a release. I'm 95% certain that I edited messages after Nov 7th in the Spanish translation of both mailman, postorius and hyperkitty, but the .po file is dated Nov 7h. Actually, I did a review of outstanding strings when Abhilash annonced the RC for the current version. That is why I was bit surprised. But then, it may be me and my faint memory. And, of course, I'm very grateful and happy with all the work that is being done on Mailman3. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 4 months

Mailman-users search results for query "2021"