Search results for "2021" - Mailman-users

Re: Mixing Mailman 3 with AWS SES

by Jim Popovitch

On Wed, 2021-03-24 at 14:00 -0400, Jim Popovitch via Mailman-users wrote: > 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. Apologies to this list and Danil who has informed me that mailman2.com is not theirs. This of course means that there is another stakeholder out there somewhere.... ;) -Jim P.

4 years, 3 months

Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark, Then I will try to upgrade the version Thank you once again. On Fri, Jun 18, 2021 at 8:01 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/21 6:48 AM, Shashikanth Komandoor wrote: > > Dear Mark, > > > > FYI, I observed this issue with the postfix that receives the > > mails from the previous MTA and hands it over to the mailman. But I fixed > > at postfix by upgrading it to the version postfix 3. > > > > But still Mailman is not able to understand Hindi (Indian > local > > language) in which language the display names of the email ids are there. > > > > So, now what to do at Mailman so that it can also understand > > local languages or any work around or other alternate solutions for these > > sort of cases. > > > As noted in my reply at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > the issue is a Mailman bug which is fixed in the next release. It has to > do with the fact that the display names are RFC 2047 encoded and not the > particular encoding. > > Actually, the fix at > https://gitlab.com/mailman/mailman/-/merge_requests/841 depends on > https://gitlab.com/mailman/mailman/-/merge_requests/652 which was > released in Mailman 3.3.2. A complete patch for versions < 3.3.2 is > attached. > > -- > 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 & Regards, Shashi Kanth.K 9052671936

4 years

Re: 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Prasanth Nair

Thank you, Mark. Kind regards, Prasanth On Thu, 14 Oct 2021 at 19:17, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/14/21 9:04 AM, Stephen J. Turnbull wrote: > > Prasanth Nair writes: > > > > > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec > can't > > > encode character '\ufffd' in position 252: ordinal not in > range(128).* > ... > > > I ran the check_hk_import script before migrating and it was not > > > giving any error. > > > > In order to catch this kind of error, the check script would have to > > pretty much do the import but throw it away. > > > The check_hk_import script > <https://www.msapiro.net/scripts/check_hk_import> is designed to detect > and report conditions which would cause the django hyperkitty_import > process to abort and stop processing the mbox. It doesn't catch errors > like the above, but these are non-fatal and just cause the offending > message to be skipped. > > As Steve says, the Message-ID was reported so find it in the mbox and if > you want it in the archive, extract it from the mbox, fix it and then > just rerun the import with just that message as input[1] and a > --since=1970-01-01 option. > > Note the issue could be in a header, but also could be in a body part > implicitly or explicitly declared as charset="us-ascii". > > -- > 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, 8 months

Re: A new issue with installation

by Abhilash Raj

On Sat, Feb 20, 2021, at 9:53 AM, Brian Carpenter wrote: > 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-wi… 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 Could it be an issue with your PATH not set correctly for mailman user? Install Rust - Rust Programming Language (rust-lang.org) <https://www.rust-lang.org/tools/install> See the setting the PATH environment. > 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 -- thanks, Abhilash Raj (maxking)

4 years, 4 months

Re: Equivalent of listadmin Perl script for Mailman 3?

by Stephen J. Turnbull

Philip Colmer writes: > On Fri, 19 Nov 2021 at 09:13, Stephen J. Turnbull < > stephenjturnbull(a)gmail.com> wrote: > > > It probably wouldn't be hard to write a bare-bones workalike if the > > admin has shell access to the mailman host. > > > > I was hoping that I could write an alternative using the REST API, but I'd > overlooked the fact that there is a single username and password protecting > the API. Correct. That's why I suggested ssh's command= parameter in authorized_keys. > Unfortunately, even trying to solve this via shell access would have a > similar problem because I can't see how one person running the command can > be restricted to just the lists they administer. You could create a system user per list admin, make authorized_keys for each user owned by somebody else (root or list or domain_admin, maybe?), and put command=list_admin.py as an option. Alternatively, it must be possible to determine which public key was authorized (sorry, not that familiar with sshd), and register that with list_admin.py, which would live in a single list_admin account. Either way, list_admin.py would manage authz permissions based on the authn data, including access to lists and which REST (or mailmanclient) APIs are allowed. This stuff is not easy to do really well, but if you are mostly worried about accidental damage or kids-will-be-kids mischief rather than actively malicious admins, could be good enough. > Oh well ... maybe something for the project to consider as an > improvement in the future, particularly for the REST API. There's a project called "lemme" which is a proof-of-concept program to put some authn/authz in front of the REST API. I was never involved, so I don't know if it got any farther than a PoC. It was a few years ago.

3 years, 7 months

Re: Trying to get mailman3 in docker working with external Mysql database

by matthew＠alberti.us

Bob, For mailman-core, I use this: environment: - DATABASE_URL=mysql+pymysql://mailman:[realstrongpassword]@database/mailmandb ?charset=utf8mb4&use_unicode=1 - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase - HYPERKITTY_API_KEY=[realstrongkey] - MTA=postfix For mailman-web, I use this: environment: - DATABASE_URL=mysql://mailman:[realstrongpassword]@database/mailmandb - DATABASE_TYPE=mysql Pymysql should be installed in the container(s) via the image. You shouldn't have to do it. If your environment variables are complete and correct in docker-compose.yaml, you should have to interactively configure anything within either container. It is all done at creation/boot time. You might want to run "docker logs mailman-core" after starting the container. Just to see what it is saying about the database connection. In my case, it wasn't working, due to an invalid character in the password. You'd never know unless you look at those logs. -----Original Message----- From: bob B <bader(a)cchmc.org> Sent: Saturday, October 9, 2021 1:45 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Trying to get mailman3 in docker working with external Mysql database Our database group has created the database with (charset=utf8mb4&use_unicode=1) and a user For my docker-compose.yaml I will only have two container sections mailman-core mailman-web which should have these database variables set under each: -DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database. server.ip]:[databseport]/[database_name] - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase Are these all correct? in looking at documentation should it be: DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database.s erver.ip]:[databseport]/[database_name]?charset=utf8mb4&use_unicode=1 Or/and should I also use? DATABASE_URL=mysql+pymysql://.... or DATABASE_URL=mysql://... or DATABASE_URL=pymysql://.... Do I have to install pymysql? or is it installed in the dock images? Do I have to run any other commands on the database first? I assume mailman does everything it needs for the database at first launch? _______________________________________________ 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, 8 months

Re: Does anyone have a working DKIM/ARC configuration?

by Philip Colmer

On Fri, 10 Sept 2021 at 14:52, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Philip Colmer writes: > > > However, in sending test messages to a mailbox hosted by Microsoft, > > I'm seeing a header like this: > > We need *all* the relevant fields (all the DKIM signatures, all the > ARC-* fields from both your server and Microsoft, and the From field, > and if possible all the trace fields like Received) to figure out > what's going on. I hadn't wanted to send too much information (initially, at least) if there was something obviously wrong and I appreciate your explanation of what I have shared. > dkim=fail (signature did not verify) header.d=sender.org; > > This is sender.org's DKIM signature, and it is expected to fail unless > Mailman is configured in pure pass-through mode where it does not > touch the body or any of the signed header fields. sender.org's DKIM > signature may as well not be there for a conforming MTA (I assume > Microsoft's does in this, I don't see any advantage to them in > breaking DKIM). I hadn't realised that "dkim=fail" applied to the original email that had been sent to Mailman 3, so that is a relief. > DKIM is all over the place, working fine. Mailman ARC was tested, and > passed, during the ARC development process at the IETF. I don't know > offhand if anybody is using that combination now. If you own the MTA, > we recommend doing ARC there if supported by the MTA (I think Postfix > does). I'm glad to see Microsoft supporting it! I will certainly have a go at adding OpenARC to our Postfix MTA. Presumably I then (re)configure the [ARC] section in Mailman 3 to not be enabled? Thanks again for the quick and detailed examination. Regards Philip

3 years, 9 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Jim Popovitch

On Sat, 2021-02-13 at 10:40 -0500, Brian Carpenter wrote: > On 2/13/21 10:37 AM, Jim Popovitch via Mailman-users wrote: > > On Sat, 2021-02-13 at 08:01 -0500, Brian Carpenter wrote: > > > Features are not the only thing about a modern UI, UX design plays a > > > MAJOR role in the modern UI. Postorius should have at least matched MM2 > > > in features in regards to something as important as Member management > > > but instead it took a step back into the dark ages. > > I'm gonna be a dick and remind you that less than 1 year ago you were > > trying to convince me that MM3 was a gift from god and that it was time > > for me to jump from MM2 to MM3 because it was sooo easy and such a time > > saver.. or something like that. The point being, you yourself just > > still aren't happy with MM3. Welcome to the club. > > I am very happy with MM3 just not with Postorius. MM3 allowed me to come > up with my own admin interface. Mailman 2 would never allowed me to do > that. So please leave your Mailman 2 bondage and come over to Mailman 3. > We have cookies! But how do you display a "Membership List page" for admins in MM3 (choice of wording is specific to other emails you've posted today) without third-party application(s), and isn't that too a shortcoming in MM3 due to that functionality being present in MM2? Look, without a doubt the REST API of MM3 Core is cool, but let's be honest, all the 3rd party wrapping and baggage is, well, not so cool. But, again being honest, you can't have a MM3 system without all of those things. With MM2 we have all those things, and we are happy with them. :) -Jim P.

4 years, 4 months

Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Just adding to this. I’ve found the outstanding holds in the pending DB: (venv) [mailman@mailman ~]$ mailman shell -l somelist.lists.example.com<http://somelist.lists.example.com> 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. The variable 'm' is the somelist.lists.example.com<http://somelist.lists.example.com> mailing list >>> from zope.component import getUtility >>> from mailman.interfaces.pending import IPendings >>> pendingsdb = getUtility(IPendings) >>> for token, data in pendingsdb.find(m): ... print(token, data) ... aabef620b654354311d3ad4a229df394560d5c66 {'type': 'unsubscription', 'list_id': 'somelist.lists.example.com<http://somelist.lists.example.com>', 'email': 'john.smith(a)maildomain.com<mailto:john.smith@maildomain.com>', 'display_name': '', 'when': '2021-05-04T00:03:01', 'token_owner': 'moderator'} 916265d88c14a02a63f8405318e25711cb3884d8 {'type': 'unsubscription', 'list_id': 'somelist.lists.example.com<http://somelist.lists.example.com>', 'email': 'john.smith(a)maildomain.com<mailto:john.smith@maildomain.com>', 'display_name': '', 'when': '2021-05-04T23:01:39', 'token_owner': 'moderator'} f931755050ecad9c315aba95daf36c39ab01526f {'type': 'unsubscription', 'list_id': 'somelist.lists.example.com<http://somelist.lists.example.com>', 'email': 'john.smith(a)maildomain.com<mailto:john.smith@maildomain.com>', 'display_name': '', 'when': '2021-04-23T00:14:48', 'token_owner': 'moderator'} 3a858fe31618dfe254398a33d1cb71bf224f5e6e {'type': 'unsubscription', 'list_id': 'somelist.lists.example.com<http://somelist.lists.example.com>', 'email': 'john.smith(a)maildomain.com<mailto:john.smith@maildomain.com>', 'display_name': '', 'when': '2021-04-23T00:15:39', 'token_owner': 'moderator'} What is the best way to clean these up? --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 11:11 am, Simon Coggins <s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au>> wrote: Hi, We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: -----Original Message----- From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com> Sent: Monday, 1 November 2021 8:10 AM To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com> Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com> list has 4 moderation requests waiting. The somelist(a)lists.example.com<mailto:somelist@lists.example.com> list has 4 moderation requests waiting. Held Unsubscriptions: User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> Please attend to this at your earliest convenience. I have multiple lists sending the same email (with the same user repeated 4 times). Where should I be looking in the internals of mailman to try and work out why this user has hidden unsubscription holds? -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939

3 years, 8 months

Re: Best guide for installing from pypi

by Duane Raymond

Thanks Jacob and Abhilash, I've had enough of trying to do it myself so I've asked Brian (I'd previously asked him but he only does it on vanilla machines and I wanted to use an existing setup). I'll learn from his work once it is running and see what I can do without a migration deadline looming over me ;-) Cheers, Duane On Wed, 24 Feb 2021 at 04:02, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi, > > > On Tue, Feb 23, 2021, at 10:00 AM, duane(a)fairsay.com wrote: > > Hi. > > > > I've got a partial mailman3 install done and, based on the > > documentation, am not sure how to complete it! (this is my first time) > > > > I've installed mailman3 (3.3.3) on a Debian 10 server using python3.7, > > mysql, postfix, apache, etc. and have run the install using pip3 > > install mailman. The "mailman info" command works, version shows > > "3.3.3 (Tom Sawyer)" the databases creates, tables, all exist, etc. So > > it seems the necessary services are running. I'm running froxlor on the > > server to configure the non-mailman services (apache, ssl, postfix, > > etc). I had also tried apt install mailman-full but it was an older > > version, so using the pypi route ensured I was on the latest version. > > I don't know anything about Froxlor, so I won't be able to help with > any issues caused due to that unfortunately. > > > > > Looking at https://docs.mailman3.org/en/latest/install/virtualenv.html, > > what I can't figure out is: > > 1) There is no /opt/mailman/ user - the user installed seems to be > > "list" > > The user recommended to create is "mailman" with "/opt/mailman" > as the home directory for the user. Debian systems use the "list" > user to run Mailman. You can simply substitute the user from > mailman to list, the name itself doesn't make a lot of different, just > make sure you do change the name in systemd config files and > sudo commands that you use. > > > 2) Is a virtual environment needed for a production environment? > > It is recommended by Linux distros that you don't install from pip > directly into the system's site-packages. This can *potentially* > have side effects and break other systems that rely on Python > packages installed on your system, some which you might not > even be aware of that relies on Python (like, Yum package manager > does in RHEL systems). > > Hence, if you aren't use the system packages to install Mailman, > it is recommended that you use an isolated Python virtualenv. > > > 3) if django is setup properly or the webservice is working > > 4) I've tried to connect to some web interface > > (posterious/hyperkitty/some mailman3 web frontend) via lynx to > > localhost:8001 on the local machine - but it has a 404 error > > 8001 is Mailman Core's API endpoint. To test Web Frontend, > you want to reach out to: https://<mydomain>/ after configuring > your Nginx to reverse-proxy the uwsgi. > > Uwsgi runs a custom protocol, also called uwsgi, which Nginx > understands and is able to reverse proxy. You can't use Lynx > to test that. However, if you do want to test your service > locally, you can add this line the uwsgi.init[1] after the > "uwsgi-socket" line: > > http-socket = 0.0.0.0:8080 > > This will make uwsgi also accept HTTP connections on Port > 8080 that you can use to test. > > > [1]: > https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws… > >

4 years, 4 months

Mailman-users search results for query "2021"