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

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Stephen J. Turnbull

Mark Sapiro writes: > I have had some contact [with EMWD], but not much. As far as I > know, they are still in business and offering list hosting > including Mailman 3 lists with Affinity and Empathy. They no longer > offer support for installation and maintenance of Mailman on other > people's servers. That exactly describes my experience. To jaboyib556, I recommend you contact them directly and make your own judgment. I do not know the current operators of EMWD, but I do know that the Carpenter family carefully vetted several bids. And their concentration on servers they run suggests they know what they're good at and have focus. I think they're a good bet, but only you can judge. > As far as I know, it was only EMWD that did this and for business > reasons, kept it proprietary. I corresponded with Brian about this.[1] He said that a third-party consultant (not sure if they're related to the current operators) built the Affinity and Empathy applications in PHP on a limited budget, and he felt that he needed to keep them proprietary as a temporary "no competition" measure until they could build up a nest egg to support on-going development. He said, and I have no reason to disbelieve him, that he thought it would take a year to build the reputation, another year to recoup the investment, and within that time frame he planned an open source release. I suspect he planned a Aladdin Ghostscript-like strategy: with the publication of release N, he would release N-1 as open source. He made no commitments, but I believe that was his aspiration. He was always a great supporter of Mailman, giving generously of his time and expertise to people on our lists including those hosting with other businesses. We miss him a lot. Footnotes: [1] On friendly terms: "hope for an open-source release" is not a matter of moral imperative with me, and I believe I speak for all Mailman developers on that.

2 years, 3 months

[MM3-users] Re: Message does not appear in archive

by Paul Arenson

Recently I asked my server administrator (large educational organization with many accounts for various sub groups). I pointed out that it might be a while before MM3 is on CPanel. I showed him the documentation at http://docs.list.org/en/latest/migration.html to show how to go from Mailman 2 to 3 manually. He said he might be willing to give it a whirl. He said he might be willing to make our group (GALE) a test case (we have about 60 people in two not-so-active lists). He asked: "I'd need to look into this a bit more to see what's possible. One issue is whether CPanel updates would overwrite any changes made. If you have any more details about it, let me know. We could try it out on the GALE site if you wanted, but I couldn't guarantee that it would work." I take it he can migrate from MM2 following the directions above in the URL. I guess what he means is, once it becomes available in Channel, would it mean more work to get it to work and to update than if we waited for the CPanel version to debut. Since I don't understand much of the install stuff, he would presumably be doing it. Thanks for anything I could relay to him. Paul

6 years, 7 months

[MM3-users] Re: MM 3 and cPanel - was: Message does not appear in archive

by Mark Sapiro

On 09/14/2018 03:07 AM, Paul Arenson wrote: > Recently I asked my server administrator (large educational organization with many accounts for various sub groups). > > I pointed out that it might be a while before MM3 is on CPanel. I showed him the documentation at http://docs.list.org/en/latest/migration.html to show how to go from Mailman 2 to 3 manually. He said he might be willing to give it a whirl. > > He said he might be willing to make our group (GALE) a test case (we have about 60 people in two not-so-active lists). He asked: > > "I'd need to look into this a bit more to see what's possible. One issue is whether CPanel updates would overwrite any changes made. If you have any more details about it, let me know. We could try it out on the GALE site if you wanted, but I couldn't guarantee that it would work." The initial step is to install a working Mailman 3 on the server. This can be done in a couple of ways. See <http://docs.list.org/en/latest/prodsetup.html> for more detail. It is not clear to me because I don't know much at all about cPanel whether MM 3 can be installed outside of cPanel on the same server or not, and if it has to be installed within cPanel, how that would be affected by cPanel updates if it can even be done at all. > I take it he can migrate from MM2 following the directions above in the URL. I guess what he means is, once it becomes available in Channel, would it mean more work to get it to work and to update than if we waited for the CPanel version to debut. Since I don't understand much of the install stuff, he would presumably be doing it. The info at <http://docs.list.org/en/latest/migration.html> covers migration of Mailman 2.1 lists to Mailman 3. The big hurdle is the installation of Mailman 3 which is not covered in that doc. As far as how to migrate from a 'custom' install to an eventual cPanel Mailman 3, that would depend at least in part on the database manager (SQLite, MySQL or PostgreSQL) used. I.e. if your custom install used SQLite and cPanel's used only MySQL, you would have a database migration issue. Some of these questions would be better directed to cPanel itself. Only they can tell you what their Mailman 3 timeline might be or if they even have one. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: templates

by Mark Sapiro

On 5/4/23 12:44, Odhiambo Washington wrote: > If you don't have any templates in the file system and none in the DB > table, then you must go to Jerusalem and pray, because you don't have any > and nothing will work the way you want. > It's either or! He didn't say he didn't have templates in the file system. He said he didn't have any custom templates in Mailman's var/templates/lists/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: templates

by Odhiambo Washington

Isn't that the same thing as not having them in the FS? I read (and asked questions about) templates almost 10x before I got to understand the locations and how MM uses them. It's not easy to understand the ones in the FS while the ones in the DB are easy. Then again, one needs to know that Postorius only writes to the DB. On Thu, May 4, 2023, 22:59 Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/23 12:44, Odhiambo Washington wrote: > > If you don't have any templates in the file system and none in the DB > > table, then you must go to Jerusalem and pray, because you don't have any > > and nothing will work the way you want. > > It's either or! > > > He didn't say he didn't have templates in the file system. He said he > didn't have any custom templates in Mailman's var/templates/lists/ > directory. > > -- > 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 odhiambo(a)gmail.com >

1 year, 11 months

[MM3-users] Re: TypeError: authenticate() takes exactly 0 arguments (3 given)

by Bjoern Franke

Hi, > Not sure how debian handles dependencies, but it sounds like the allauth > package doesn't correctly depend on a minimum django version. > Might be worth a bug report, but then again I'm in archlinux where you > update all or update nothing :D Yep, I've created a bugreport for mailman3-suite and the maintainer says he thought he had set the dependency on python-django from backports, but he fixed it now. No idea if it's also a bug for python-django-allauth, as an Arch user I have no clue about the Debian package workflow :D Regards Bjoern

7 years, 1 month

[MM3-users] Re: Sad news - Brian Carpenter

by Odhiambo Washington

On Wed, May 12, 2021 at 10:45 PM <smorytko(a)gmail.com> wrote: > > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > > I mentioned some "unfortunate circumstances" in a recent post. An inquiry > from Mark Sapiro prompted me to do a search and I sadly found this. > > Brian's company managed our list and on 4/22 we became aware that he was > hospitalized with Covid. > I have known Brian for many years mainly from the Mailman lists and he was a great resource. For a while now I have been meaning to check on the HOWTO he was writing for installing Mailm3 on Debian and yesterday I actually wanted to check on it. What a sad turn of events. May his soul rest in peace. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

3 years, 11 months

[MM3-users] Re: Sad news - Brian Carpenter

by Steven Clift

Yes, very sad news. E-Democracy.org was plotting with Brian (due to his passion for pushing the envelope on making Mailman list much more web-friendly) a move to his services. He had great spunk and passion for online communities. Steven Clift <http://stevenclift.com> - Founder and Volunteer, E-Democracy.org clift(a)e-democracy.org - +1 612 234 7072 @Democracy <http://twitter.com/democracy> - Facebook <https://www.facebook.com/stevenlclift> - LinkedIn <http://linkedin.com/in/netclift> On Thu, May 13, 2021 at 12:37 PM Duane Raymond <duane(a)fairsay.com> wrote: > Thanks for letting us know. > > Brian was fantastic help on getting me up and going with mailman3 a few > months ago...and his work on friendlier interfaces for mm3 is excellent. > He will definitely be missed in this community and by me. He was always > helpful off list as well as on list. It was brilliant support to have. > > I hope his legacy at emwd.com and Harmony Lists continues. > > Rest in peace Brian. > _______________________________________________ > 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, 11 months

[MM3-users] Re: Sad news - Brian Carpenter

by Kevin Hurtley

Agreed. Brian was fabulous in getting us setup with Mailman services at his company and continued to provide great and friendly service at a reasonable price. I was always pleased to see his participation on this list knowing he was continually working on improving a good product. (after trying to set up MM3 on my own, I eventually decided to rely on an expert like Brian. It was a very wise decision). Very sad news indeed. Kevin -----Original Message----- From: Duane Raymond <duane(a)fairsay.com> Sent: Thursday, May 13, 2021 9:38 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Sad news - Brian Carpenter Thanks for letting us know. Brian was fantastic help on getting me up and going with mailman3 a few months ago...and his work on friendlier interfaces for mm3 is excellent. He will definitely be missed in this community and by me. He was always helpful off list as well as on list. It was brilliant support to have. I hope his legacy at emwd.com and Harmony Lists continues. Rest in peace Brian. _______________________________________________ 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, 11 months

[MM3-users] Re: Unknown templates being used

by Brian Carpenter

On 2/14/21 1:31 PM, Mark Sapiro wrote: > On 2/14/21 5:44 AM, Tom Stoddard wrote: >> I'm a list owner who has recently (within the last week) had my lists >> migrated from mailman 2 to mailman 3. The UI that we are using is >> Affinity. > So you should be getting your support from EMWD. > > >> I've reviewed all of the list templates and begun to customize >> some of them. My issue is that I'm receiving messages that don't match >> any of the templates. Here is an example of one that I just received >> this morning. (The x's are inserted by me. The actual message provided >> valid addresses.) >> >> Thexxxxxxxxxx(a)xxxxxxxxxx.org list has 1 moderation requests waiting. >> >> >> Held Subscriptions: >> User:xxxxxxxxxx@gmail.com >> >> Please attend to this at your earliest convenience. Yeah, the funny thing here Mark is he is not asking for support for the interface. He is wanting to know why isn't there a way for List Owners to modify moderation notices. It had nothing to do with Affinity. BTW - I told this client CLEARLY there was no template for that notification but he was welcome to join the list to ask for the source of it since I did not know. Geez. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Member Issue Discovered

by Jörg Schulz

So, the issue seems to be, like in the following scenario We imagine a list server for the domains fruiteaters and meateaters. We have two listadmins, anna (fruit) and carl (meat). They don't share anything. We have a user who subscribes to fruiteaters and meateaters using his address hunger(a)eatall.com He wants to show up in the fruiteaters list as fullname wormy wonder, but in the meateaters list as fritz the cat. While he can do so using two different email addresses, he cannot do so using wormy wonder <hunger(a)eatall.com> fritz the cat <hunger(a)eatall.com> as from: addresses because all requests will be matched to the one email address. Worse, if Carl would be able to change the name to from wormy wonder to fritz the cat, Anna would see that name change and like to change it back because the user she had known, user has been identified as wormy wonder. So, if these user properties are stored somewhere not related to the lists, we don't seem to have a chance of display name changes by list admins as long as the data model isn't changed. This doesn't seem to be easy. So, only some kind of super-Admin should currently be able to change these display names, and these changes would be visible for all lists, and one email address can only have one display name for all lists. Not optimal for some rare conditions - that's the way it seems to be???

4 years, 6 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/21/20 4:43 AM, Jörg Schulz wrote: > So, the issue seems to be, like in the following scenario > > We imagine a list server for the domains fruiteaters and meateaters. > We have two listadmins, anna (fruit) and carl (meat). They don't share anything. > We have a user who subscribes to fruiteaters and meateaters using his addresshunger(a)eatall.com > > He wants to show up in the fruiteaters list as fullname wormy wonder, but in the meateaters list as fritz the cat. > While he can do so using two different email addresses, he cannot do so using > > wormy wonder<hunger(a)eatall.com> > fritz the cat<hunger(a)eatall.com> > > as from: addresses because all requests will be matched to the one email address. > > Worse, if Carl would be able to change the name to from wormy wonder to fritz the cat, Anna would see that name change and like to change it back because the user she had known, user has been identified as wormy wonder. > > So, if these user properties are stored somewhere not related to the lists, we don't seem to have a chance of display name changes by list admins as long as the data model isn't changed. This doesn't seem to be easy. > > So, only some kind of super-Admin should currently be able to change these display names, and these changes would be visible for all lists, and one email address can only have one display name for all lists. > > Not optimal for some rare conditions - that's the way it seems to be??? You should add that the name can't be changed at all nor ever removed. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Ken Alker

We have been experiencing a strange anomaly. We are running a small-ish list. When a particular subscriber to the list sends an email to the list, a couple of dozen (or more) of the recipient's of the message end up with their bounce scores incrementing. This particular subscriber uses about three different email addresses when he sends his messages and every one of them causes this behavior. There is another subscriber who also causes this behavior when he sends an email to the list, but only one of the two email addresses he sends from causes this behavior. There is a third person who causes this behavior every time. There are dozens of other subscribes who don't generate this behavior when they send to the list. I can't figure out why this is occurring. I *assume* that Mailman re-writes the headers to add DKIM, etc., before sending them to the list recipients but it sure seems like something in the header from the original sender is ending up in the final header (or something is LACKING) which is not liked by the recipient's MTA's. It doesn't seem like a subscriber sending an email to the list should be able to cause this behavior - but I'm no expert. The recipients appear to be using many different mail platforms (ie. their addresses are not all, or even mostly, @google.com or some other domain; the recipients appear to be a pretty good cross section of platforms). This has been going on all year (maybe longer). Any help or troubleshooting suggestions would be greatly appreciated.

8 months

[MM3-users] Re: Listing/Exporting member list error: Mailman REST API not available. Please start Mailman core.

by Brian Carpenter

Hi Abhilash, Thomas is one of my clients and I helped install the Mailman 3 setup he is using. I installed MM3 using your docker images. He is currently running version 3.1. Lists with a smaller amount of members are exporting fine. However on a list with around 1100 members, the request is timing out. Brian

5 years, 3 months

[MM3-users] List invisible to moderator

by Olaf Zaplinski

I just have promoted a member to a moderator. Now when he logs in to Postorius, he gets the message "There are currently no mailing lists.". I have set "Show list on index page" to "no" before. But as a moderator, the list should be shown, right? I mean, all lists are shown to the administrator also. When I manually enter the complete URL, the moderator can see the list. I think this is a bug. Moderators should see their lists. What do you thing? Olaf

4 years, 10 months

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Brian Carpenter

On 3/25/21 2:51 PM, Jim Popovitch via Mailman-users wrote: > 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....;) Would be nice if Danil could let the list know and in that same communication, he can explain why he is promoting Mailman 4 when there is no Mailman 4. We can then move to the discussion of him charitably giving mailman3.com to the Mailman 3 developers. How about it Danil? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 1 month

[MM3-users] Re: Sad news - Brian Carpenter

by Duane Raymond

Thanks for letting us know. Brian was fantastic help on getting me up and going with mailman3 a few months ago...and his work on friendlier interfaces for mm3 is excellent. He will definitely be missed in this community and by me. He was always helpful off list as well as on list. It was brilliant support to have. I hope his legacy at emwd.com and Harmony Lists continues. Rest in peace Brian.

3 years, 11 months

[MM3-users] Problem user

by Itay Malka

Hello everyone, I use mailman3 And I have one user who every time receives reports on a mailing list that he is not the administrator of, he is only registered to it How can I cancel it? could not find This is the email Message-ID: <CABPnsAo5vT8YKXiaHk0E2qs8CRs8nP13B9T9n5x4Yc8n7iLV3Q(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="00000000000069e01c05fbde1416" --00000000000069e01c05fbde1416 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 16rXldeT15QNCg== --00000000000069e01c05fbde1416 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: base64 PGRpdiBkaXI9ImF1dG8iPteq15XXk9eUPC9kaXY+DQo= --00000000000069e01c05fbde1416-- End of Dental-medicine-faculty-council Digest, Vol 1, Issue 1 ************************************************************* Regards

1 year, 11 months

[MM3-users] Re: Installing Mailman for the first time

by Mark Dale

On 2023-03-24 23:43, comprepair_jimberg--- via Mailman-users wrote: > I am running Debian 11 Server and wanting to install Mailman 3 > > Will this work for what I am trying to do? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > If not is there a shorter list of steps to accomplish what I am trying to do? > > Jim In Tom Kisner's article: "Installing Mailman3 on Debian 11" he uses "Mailman 3 Setup Using Ubuntu Bionic" by Kelly Close. He notes a couple of differences to take heed of. The instructions worked first time around for me (ie. Mailman 3 up and running on Debian 11). https://kn6q.org/installing-mailman-3-on-debian-11/ https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…

2 years, 1 month

[MM3-users] Re: Unknown templates being used

by Mark Sapiro

On 2/14/21 1:47 PM, Tom Stoddard wrote: > > On 2/14/2021 1:31 PM, Mark Sapiro wrote: >> >> I.e., we know it should be a template, but it currently isn't. > > That's fine but it doesn't explain why I have received messages that > were built by a template for some subscription requests. In other words, > why is there a template being used in some instances and on others a > "mailman notify command" is being used? The notice sent at the time the request is generated is built from a template. The `mailman notify` command is intended to be run periodically via cron set up by the site admins to send a summary of then outstanding requests to the list admins. You should receive the initial notice built from a template of each request as it is generated as long as the list is sent to send immediate notices. The notice sent by `mailman notify` is a summary of all requests outstanding at that time. If all the requests have been handled by the time `mailman notify` is run, it won't send you anything. > Are there different methods for people to use to request a subscription? Yes, but that's not the explanation for your question. Subscription can be requested via a web UI or via email to the list-join or list-subscribe address or via a join or subscribe command sent to the list-request address, but all methods result in the same notices to the admin. > By the way, Brian at EMWD has been extremely helpful to me already and, > as he stated, he informed me that this is an issue with Mailman 3 so I > thought I'd try getting the answer directly from this group. I agree and appreciate that Brian is very supportive. In my initial reply, it was not clear to me that Brian had referred you here which is the only reason I pointed out that he was your primary line of support. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Different Mail Domain Cause Key Error

by Brian Carpenter

I have a client that requires his list address to be list(a)domain.com. But since he is using domain.com for an external website, he has to access his list via Postorius using list.domain.com. So here is what I did: Django Admin Add Site: list.domain.com Add Mail Domain: domain.com (Site selected is list.domain.com) Postorius Add Domain: Mailhost is domain.com. Web Host is list.domain.com (list.domain.com) I have list.domain.com listed in the allowed hosts in settings_local.py. I even added domain.com there as well. When I try to access Postorius using list.domain.com I get a "An error occurred while processing your request." message and the logs shows the dreaded: ``` 'Internal Server Error: /mailman3/lists/ KeyError at /mailman3/lists/ 'file' ``` Did I miss a step here? Thanks, Brian

5 years

[MM3-users] Re: List invisible to moderator

by Mark Sapiro

On 6/16/20 3:43 AM, Olaf Zaplinski via Mailman-users wrote: > I just have promoted a member to a moderator. Now when he logs in to > Postorius, he gets the message "There are currently no mailing lists.". > > I have set "Show list on index page" to "no" before. But as a moderator, > the list should be shown, right? I mean, all lists are shown to the > administrator also. > > When I manually enter the complete URL, the moderator can see the list. > I think this is a bug. Moderators should see their lists. What do you > thing? What Postorius version is this? It works for me in Postorius 1.3.3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Add rule to auto-discard "AutoReply" messages from list members

by Stephen J. Turnbull

Odhiambo Washington writes: > If you have lists using different email addresses, then you just > substitute the $h_to in another filter rule. > > But then maybe Mr. Thomas Ward uses Postfix or Sendmail, in which case this > is all useless/greek to him :) If he's done any MTA configuration, I'm sure he'll treat it as pseudo-code and translate to the language he needs without trouble. So please don't hesistate to provide code from your site (appropriately redacted, of course) even if you know the OP uses different software. The big question about the usefulness of these posts is whether his users have RFC 3834 conforming vacation programs that know about the Auto-Submitted field. I didn't know my homework bot was conformant until I just checked -- thank you Exim4! Steve

1 year, 5 months

[MM3-users] Questions regarding message acceptance

by Pawel Grzywaczewski

Hello, I have few questions regarding usage of Mailman3: 1) We have list1 and list2 with members. Can we specify that all members of list1 can post messages to list2? We could potentially write a script that would synchronize members of another list to “Accept these non-members” of another list, but with thousands of lists it will be difficult to maintain lists in synchro. So perhaps there is a concept of adding another list to “Accept these non-members” and mailman real-time evaluate membership of another list upon message arrival? 2) In explanation of “Accept these non-members” it’s written: “While non-regexp addresses can be entered here, it is preferred to add the address as a nonmember and set the nonmember's Moderation to Default Processing”. I noticed that if someone posts to a list then he is added automatically to non-members. Which means that next time he will be able to post. My understanding is that it’s better to use the feature “Accept these non-members”. Am I correct? Thank you, Paweł

4 years, 8 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Stephen J. Turnbull

Lars Schimmer writes: > On 27/02/2021 04:02, Stephen J. Turnbull wrote: > > It's not necessary to "keep up" to be very helpful to our users, of > > course. But I think Brian's document is likely to be the "gold > > standard" for a while. I understand why Abhilash wants it in the > > official docs. :-) > > If it should be a gold standard, it should mention the default setup of > a standard debian system (which is exim4, btw) and not assuming a > special setup debian system. "Gold standard" means it does what it sets out to *really* *well*. "Gold standard" does not mean it does everything everybody wants. In particular, much of the appeal of Brian's guide is that it's how he sets up a Mailman 3 host, and he's proved it's repeatable, many times. Anything that he doesn't use himself doesn't belong in his guide. We already have a descriptions of Exim (which I wrote the original) and Apache setups in the "official" docs. There's no good reason to treat Debian specially, since we don't distribute .debs ourselves. It's not even clear that we should recommend apt-get mailman! And surely no need, as that is the obvious (but not necessarily best for any given server!) way to set up a Debian Mailman installation. But there is good reason to believe that typical Debian installations will be quite out of date, because most admins prefer to run a server based on stable or LTS distros, not bleeding edge (Debian "sid") or even beta (Debian "testing") distributions, while updates to Mailman continue to be frequent and important to many or even most users. Regards, Steve

4 years, 1 month

[MM3-users] Re: Problem user

by Mark Sapiro

On 5/18/23 04:33, Itay Malka wrote: > Hello everyone, > > I use mailman3 > And I have one user who every time receives reports on a mailing list that he is not the administrator of, he is only registered to it > How can I cancel it? > could not find > > This is the email > Message-ID: > <CABPnsAo5vT8YKXiaHk0E2qs8CRs8nP13B9T9n5x4Yc8n7iLV3Q(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="00000000000069e01c05fbde1416" > > --00000000000069e01c05fbde1416 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: base64 > > 16rXldeT15QNCg== > --00000000000069e01c05fbde1416 > Content-Type: text/html; charset="UTF-8" > Content-Transfer-Encoding: base64 > > PGRpdiBkaXI9ImF1dG8iPteq15XXk9eUPC9kaXY+DQo= > --00000000000069e01c05fbde1416-- The message above is not from Mailman. It is simply a message originally from Gmail that says :"Thank you" in hebrew. I can't say much more without seeing the entire raw email. > End of Dental-medicine-faculty-council Digest, Vol 1, Issue 1 > ************************************************************* This is the final part of a plain format digest. Was it part of what was received? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Allan Hansen

My 2 cents’ worth: When moving to MM3 from MM2, the latter of which I (relatively) easily installed myself, I read what I could find and went on installing MM3. I soon ran into trouble, namely somewhere around the hooking up of the web server. I ran into a thicket that I could not decipher. Then I asked the person who now hosts the server. He soon ran into trouble at around the same place (as far as I remember). I then asked someone who had been very helpful with MM2 to do the installation. He's a professional. He soon ran into trouble. I don’t know where, but he tried over several weeks to get it going. The trouble? Finding the correct documentation. Understanding the documentation, which is not exactly clear. Doing what the documentation says, if it says it, and things not working as they should. I then asked Brian, who has helped a lot of people (like many of you have). He did the installation very quickly and with no trouble. Don’t tell him this, but it was money well spent! :-) Yours, Allan Hansen hansen(a)rc.org > On Feb 25, 2021, at 18:38 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 2/25/21 8:28 PM, Abhilash Raj wrote: >> Thanks Brian, this looks quite comprehensive in the details. The only >> thing I am a bit concerned about is granting sudo privileges to the >> Mailman user. It really shouldn't have sudo given that Mailman and >> Django are supposed to run as mailman user. Any compromise of >> the Django application will provide the attacker root on the machine. > > Thanks for pointing that out. I have removed that step. It really wasn't needed. > >> Is there a specific reason that you chose to go with an entirely new doc > > Yes. Just from observing the communications on this list, there are multiple ways to install Mailman 3 which produces installation issues, database problems, outdated apps, etc. My document produces a VERY stable installation of Mailman 3 and one that is easy to maintain and update. It is also very comprehensive covering not just Mailman Suite, but the configuration of an entire server environment. Personally I think the choice of Debian, NGINX, Postfix, and PostgreSQL makes for a long and loving relationship with Mailman 3 but I do understand everyone has their own environment that they want to work with. My guide represents a very stable and easily maintained environment for me and hopefully others. > >> rather than helping to improve the existing one? Several parts of it (at >> least the ones that official guide covers) seems similar to me and is >> duplicate information that at least two people are going to spend time >> writing and maintaining in future. > > Is there an official guide? See that is the problem. I did not know there was an official guide. Because every time I tried finding documentation in the past using Google searches, I got fed outdated information. So for me the guide that I came up with, works great for me and if no one else uses it, I certainly will. > > Your guide, by nature has to be minimalistic to accommodate all the various server environments out there. My is meant to be narrow but comprehensive. > > >> Is it something about the contribution process to the official documentation >> that makes it hard for people to contribute? Most of the pages at >> docs.mailman3.org or come from this[1] repo and use Sphinx to build and >> REsT formatting (.rst). >> >> [1]:https://gitlab.com/mailman/mailman-suite-doc > > Well I don't know much about any of the above approach to documentation. So I would say that is a hindrance. > > >> I am just trying to understand how can we lower the barrier for community >> members to help contribute to existing docs instead of them having to create >> new ones. Specifically around installation, since that tends to get stale often >> when depedent packages change or a new dependency is added that >> breaks the installation. > > I had to update my guide twice due to recent changes made to the installation process such as the addition of the Dart Sass section and the problem with the cryptography module when installing Hyperkitty. While my guide covers these new hurdles to a new installation, I don't think yours says anything about them. The Dart Sass section came from Mark's comments on this list. > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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, 2 months

[MM3-users] Re: The future is here?

by Stephen J. Turnbull

Hans-Martin Mosner writes: > I'm pretty comfortable with docker containers, mailman and postfix > in somewhat unsual configurations, and would like to help out there > (with limited time, though, but I can justify some on job work > time). Cool! > What would be the most helpful contribution? I see that there are > some pull requests that are not yet integrated, but didn't check > whether they require additional QA to be integrated or are just > backlogged. > Would you rather like assistance in integrating existing pull > requests, QA work to make them integration-ready, or work on > untackled issues to create more pull requests? :-) Abhilash is busy, so in case he doesn't answer quickly, I offer my thoughts. But Abhilash he is the most important developer on the containers. If you are considering formal membership in the core (ie, direct commit privilege, with an informal expectation of review from "more senior" core devs), integrating existing pull requests might be top priority, to get practice in that. Otherwise, reviews and triage on all container issues, and QA on existing pull requests, are probably top priorities IMO. Steve

4 years, 3 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? >

3 years

[MM3-users] Re: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Schulz

if this particular subscriber uses apple mail on iphone, and the mails in questions are _answers_ to existing mails, it might be the known issue that the References: header grows beyond a limit given by exim. This is the fault of apple mail and violates standards, historically also microsoft didn't care about that limit. I haven't found a workaround yet; postfix mailer allows to split this line. Best! Am 24. August 2024 um 10:53 schrieb "Odhiambo Washington via Mailman-users" <mailman-users(a)mailman3.org>: > > On Sat, Aug 24, 2024 at 6:32 AM Ken Alker <mailman3.org(a)alker.net> wrote: > > > > > We have been experiencing a strange anomaly. We are running a small-ish > > list. When a particular subscriber to the list sends an email to the list, > > a couple of dozen (or more) of the recipient's of the message end up with > > their bounce scores incrementing. This particular subscriber uses about > > three different email addresses when he sends his messages and every one of > > them causes this behavior. There is another subscriber who also causes > > this behavior when he sends an email to the list, but only one of the two > > email addresses he sends from causes this behavior. There is a third > > person who causes this behavior every time. There are dozens of other > > subscribes who don't generate this behavior when they send to the list. > > > > I can't figure out why this is occurring. I *assume* that Mailman > > re-writes the headers to add DKIM, etc., before sending them to the list > > recipients but it sure seems like something in the header from the original > > sender is ending up in the final header (or something is LACKING) which is > > not liked by the recipient's MTA's. It doesn't seem like a subscriber > > sending an email to the list should be able to cause this behavior - but > > I'm no expert. > > > > The recipients appear to be using many different mail platforms (ie. their > > addresses are not all, or even mostly, @google.com or some other domain; > > the recipients appear to be a pretty good cross section of platforms). > > > > This has been going on all year (maybe longer). Any help or > > troubleshooting suggestions would be greatly appreciated. > > > (...) >

8 months

[MM3-users] Re: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Odhiambo Washington

On Sat, Aug 24, 2024 at 6:32 AM Ken Alker <mailman3.org(a)alker.net> wrote: > We have been experiencing a strange anomaly. We are running a small-ish > list. When a particular subscriber to the list sends an email to the list, > a couple of dozen (or more) of the recipient's of the message end up with > their bounce scores incrementing. This particular subscriber uses about > three different email addresses when he sends his messages and every one of > them causes this behavior. There is another subscriber who also causes > this behavior when he sends an email to the list, but only one of the two > email addresses he sends from causes this behavior. There is a third > person who causes this behavior every time. There are dozens of other > subscribes who don't generate this behavior when they send to the list. > > I can't figure out why this is occurring. I *assume* that Mailman > re-writes the headers to add DKIM, etc., before sending them to the list > recipients but it sure seems like something in the header from the original > sender is ending up in the final header (or something is LACKING) which is > not liked by the recipient's MTA's. It doesn't seem like a subscriber > sending an email to the list should be able to cause this behavior - but > I'm no expert. > > The recipients appear to be using many different mail platforms (ie. their > addresses are not all, or even mostly, @google.com or some other domain; > the recipients appear to be a pretty good cross section of platforms). > > This has been going on all year (maybe longer). Any help or > troubleshooting suggestions would be greatly appreciated. > When you say "I *assume* that Mailman re-writes the headers to add DKIM, etc., before sending them to the list recipients", I think there lies the issue. It's either you have configured MM3 to do the DKIM bit or it's done by your MTA. Only one is enough. But even DKIM is not the issue, but DMARC. So my lists are configured this: https://imgur.com/a/Wk82b7Z And I think with proper DKIM+SPF for your MM3s mail host, there should be no such phenomenon you're observing. -- 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]

8 months

[MM3-users] Re: Member Issue Discovered

by Apollinaris Schöll

There might be a handful of these. But the bigger problem is a user can’t be removed entirely. User can delete account and unsubscribe from all lists. But the email and user name is still kept in the db. Just tested with Affinity List admin can’t do it either. I am admin for a list. Users got subscribed with bulk import during transition from MM2 to MM3. So in a sense I am responsible for adding these to a db. BUT there is no way for me to remove them. Only mailman admin with access to the db can do it manually. I think the correct action is to remove all records if a email is unsubscribed from all lists and that user has not registered for an account. If a user has registered for an account all information including display name must be removed from that particular list subscription. It should not matter if a user unsubscribes or a list admin unsubscribes. There shouldn’t be any data kept. > On Oct 21, 2020, at 1:43 AM, Jörg Schulz <info(a)joergschulz.de> wrote: > > So, the issue seems to be, like in the following scenario > > We imagine a list server for the domains fruiteaters and meateaters. > We have two listadmins, anna (fruit) and carl (meat). They don't share anything. > We have a user who subscribes to fruiteaters and meateaters using his address hunger(a)eatall.com > > He wants to show up in the fruiteaters list as fullname wormy wonder, but in the meateaters list as fritz the cat. > While he can do so using two different email addresses, he cannot do so using > > wormy wonder <hunger(a)eatall.com> > fritz the cat <hunger(a)eatall.com> > > as from: addresses because all requests will be matched to the one email address. > > Worse, if Carl would be able to change the name to from wormy wonder to fritz the cat, Anna would see that name change and like to change it back because the user she had known, user has been identified as wormy wonder. > > So, if these user properties are stored somewhere not related to the lists, we don't seem to have a chance of display name changes by list admins as long as the data model isn't changed. This doesn't seem to be easy. > > So, only some kind of super-Admin should currently be able to change these display names, and these changes would be visible for all lists, and one email address can only have one display name for all lists. > > Not optimal for some rare conditions - that's the way it seems to be??? > _______________________________________________ > 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, 6 months

[MM3-users] When mass subscribing using format John Doe <john.doe@example.com>, "Members" show some with real name, others without.

by Henrik Rasmussen

GNU Mailman 3.2.0 (La Villa Strangiato): A list administrator asked me why some people is subscribed with full name and some are not, when he is mass subscribing people using the format John Doe john.doe(a)example.com. He had experienced this a lot of times. I tested this several times on my test lists, and one member, who already had his name registrered in Account (Postorius top right), and thus also in Django, kept being subscribed without real name, while the others was subscribed with full name in Members -> Subscribers. It seems (I’m not certain about this) that the one’s without real name is the one’s already having an account and thus registred in Django (admin/auth/user/), while the ones subscribed with full name associated is the ones not having an account already. However, as soon as the member (the one with the account) went to Account and changed his real name, the name was immediately associated with the subscription in Members -> Subscribers. I expect this to be by design, but why isn’t the name associated with the subscription when mass subscribing in the first place, taken from the account? Henrik Rasmussen

5 years, 5 months

[MM3-users] Re: Questions regarding message acceptance

by Mark Sapiro

On 7/28/20 6:35 AM, Pawel Grzywaczewski wrote: > Hello, > > I have few questions regarding usage of Mailman3: > > 1) We have list1 and list2 with members. Can we specify that all members of list1 can post messages to list2? This is a Mailman 2.1 feature that does not currently exist in Mailman 3. > 2) In explanation of “Accept these non-members” it’s written: “While non-regexp addresses can be entered here, it is preferred to add the address as a nonmember and set the nonmember's Moderation to Default Processing”. > > I noticed that if someone posts to a list then he is added automatically to non-members. Which means that next time he will be able to post. > My understanding is that it’s better to use the feature “Accept these non-members”. Am I correct? You are mistaken. When a non-member attempts to post to a list she is automatically added to non-members with a moderation action of list default, which means that this and subsequent posts will be handled according to the list's "Default action to take when a non-member posts to the list" If you want to accept a non-member's posts you need to set that non-member's moderation action to "Default Processing" to still apply other tests that might hold the message or to "Accept" if you want to accept anything from that non-member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Finding a user to delete them

by Quanah Gibson-Mount

--On Saturday, March 14, 2020 7:03 PM +0900 "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > For alternatives to Postorius and the Mailman shell, Brian Carpenter > (follow Allan's subthread) is working on a new management UI (using > PHP), and I believe there's a working node.js API "out there > somewhere". Please be very considerate of Brian's time; he and EMWD > constitute a bulwark of the Mailman ecosystem and will be even busier > with the UI project. But do pass on your suggestions to him as well > as to us, he's indicated he's open to that. Thanks Steve, Generally I just found the mailman shell examples in the documentation lacking, as: * it used functions not available without loading additional modules not listed in the documentation * the steps to find accounts is lacking, since they don't work for email addresses that are not yet verified * I could find no documentation on what fields are available in the user object, so I was unable to find the account via other methods, including the actual username created by mailman3 (which seems odd, wouldn't this be a standard way to find users..?) The Django UI is the only thing that let me find the miscreated user and delete it. Hopefully the bug I filed about github user integration being badly broken will receive some priority, given the bug causes new accounts to incorrectly be created for existing users. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 1 month

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Hi Mark, thanks for correcting my assumption. Based on your information I have been able to identify the suspect message file in /var/lib/mailman3/messages, replace the suspect file with another file, update the file permissions and successfully load the held messages page. This allowed me to discard the suspect message and other held messages are then available for review again. In case the steps below help someone else who is having this issue here are the steps I followed with my initial search string redacted: Searched all files in messages folder for matching string: cd /var/lib/mailman3/messages grep -ir [REDACTED] * Finds string in one file: Binary file HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV matches Check whether file can be parsed using mailman command: mailman qfile ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Throws a matching error: [----- start pickle -----] <----- start object 1 -----> Traceback (most recent call last): File "/usr/bin/mailman", line 11, in <module> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 97, in main args.func(args) File "/usr/lib/python3/dist-packages/mailman/commands/cli_qfile.py", line 81, in process printer.pprint(obj) File "/usr/lib/python3.6/pprint.py", line 139, in pprint self._format(object, self._stream, 0, 0, {}, 0) File "/usr/lib/python3.6/pprint.py", line 161, in _format rep = self._repr(object, context, level) File "/usr/lib/python3.6/pprint.py", line 393, in _repr self._depth, level) File "/usr/lib/python3.6/pprint.py", line 405, in format return _safe_repr(object, context, maxlevels, level) File "/usr/lib/python3.6/pprint.py", line 555, in _safe_repr rep = repr(object) File "/usr/lib/python3/dist-packages/mailman/email/message.py", line 45, in __repr__ return self.__str__() File "/usr/lib/python3.6/email/message.py", line 135, in __str__ return self.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart g.flatten(part, unixfrom=False, linesep=self._NL) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) Move suspicious file out of messages: mv ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV /root/20200914/ held_messages page still throws 500 error. Checking debug log, it is now because the database references a file that is no longer there. Can I just copy a parseable file to the path of the bad file so I can delete it or do I need to remove the reference from the database? Copy some other file: cp ZZ/B2/ZZB24ADTZ2BOKBWTQWI7KG4XACGR6DTJ HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Still throws an error but this time it's a permissions error. mailman can't access the copied file: ls -l HE/D7/ -rw-r----- 1 root root 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chown list:list HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chmod g+w HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV ls -l HE/D7/ -rw-rw---- 1 list list 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV held_messages now loads OK. Cheers, Simon. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, 12 September 2020 06:17 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius On 9/6/20 3:39 PM, Simon Handfield via Mailman-users wrote: > Thanks for your advice, Stephen. > > As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. > > I've confirmed the error is not cached in the browser. > > If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? As Steve said, messages in the shunt queue have nothing to do with the held messages view in postorius. Held messages are in Mailman's var/messages/ directory and referenced by entries in the message table in the database which in turn are referenced by entries in the pendedkeyvalue table. -- 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

4 years, 7 months

[MM3-users] Re: Finding a user to delete them

by Stephen J. Turnbull

Quanah Gibson-Mount writes: > But really, the documentation needs to be updated further to point > out the the Django ADMIN INTERFACE as the best way to do user > management, and not the python shell. The Django admin interface is something that most sites are not going to want to expose in addition to Postorius, and Postorius is needed for the users. If you have access to the host (another thing that most sites are not going to want to expose to list owners, who are most relevant to user management), you want to use the Mailman shell, not the Python shell (I assume Mailman shell is what you meant, but other readers may not). The bundled administrative interface *is* Postorius. The Mailman shell is basically a quick hack (sorry Abhilash; if you want to call it a masterwork and say the speed of development is testimony to your skills, I won't deny it ;-) to give more convenient access to internals to experienced Mailman hackers. More administrative features is something we plan to work on, but the Mailman project will focus on Postorius for the forseeable future. For alternatives to Postorius and the Mailman shell, Brian Carpenter (follow Allan's subthread) is working on a new management UI (using PHP), and I believe there's a working node.js API "out there somewhere". Please be very considerate of Brian's time; he and EMWD constitute a bulwark of the Mailman ecosystem and will be even busier with the UI project. But do pass on your suggestions to him as well as to us, he's indicated he's open to that. Steve

5 years, 1 month

[MM3-users] Re: Strange messages after upgrading Mailman3

by Mark Sapiro

On 12/5/22 14:46, Allan Hansen wrote: > I asked the poster of one message what he had done. > Apparently, he had put the list address (just one list, according to him) in the Bcc: field. > The message was then held for moderator approval and, when approved, sent out without a body. > > Another message was stopped because it did not have a subject field. > Again, it was approved and then sent out without a body. I just did a test of a message with no Subject. It was held for no subject and when accepted was delivered. in all cases, the notice to the admin, the message in the held message view, the message delivered to the list members and the archived message; the message body was intact I did the same test with implicit destination with the same result. I even tried posting the same message to list(a)example.com and list+z(a)example.com resulting in two held messages which I accepted one at a time and the only difference was only the first accepted message was archived by HyperKitty because of the duplicate Message-ID:. Both were archived with content in the prototype archive. If you are really on Mailman 3.3.7, your result should be the same. Even on 3.3.5 which first introduced the possibility of content being lost, this shouldn't happen on posts to a single list You could try these same tests on a test list on your installation. I would be interested in your result. If it is the same as mine, there must be some other condition affecting this although I don't know what it would be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Unknown templates being used

by Tom Stoddard

On 2/14/2021 1:31 PM, Mark Sapiro wrote: > That message is not built from a template. It comas from the `mailman > notify` command which currently says > ```> def _send_notice(mlist, count, detail): >> """Creates and sends the notice to the list administrators.""" >> subject = _('The {} list has {} moderation requests waiting.').format( >> mlist.fqdn_listname, count) >> # XXX This should be a template. >> text = _("""The {} list has {} moderation requests waiting. > ``` > I.e., we know it should be a template, but it currently isn't. That's fine but it doesn't explain why I have received messages that were built by a template for some subscription requests. In other words, why is there a template being used in some instances and on others a "mailman notify command" is being used? Are there different methods for people to use to request a subscription? Please understand that I'm new to mailman 3 and don't have knowledge of its source code. From reading some of the messages that have been sent by this list, I assume it's written in python, which is a language I have not year learned. I'm asking this because I help to administer several different lists and there are some other moderators who have very limited technical skills. I try to help them the best I can, which is why I'm trying to understand why these messages seem to differ so that I can explain it to others. By the way, Brian at EMWD has been extremely helpful to me already and, as he stated, he informed me that this is an issue with Mailman 3 so I thought I'd try getting the answer directly from this group. Thank you for your time. I do recognize and appreciate the time and effort that goes into creating and maintaining open source software.

4 years, 2 months

[MM3-users] Re: Mailman backend maintenance task

by Abhilash Raj

> On Aug 24, 2021, at 8:33 AM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Hi, Eugenio, > > I wrote this earlier but am in the middle of moving my office so my > mail has been intermittent. I have been following your discussion > with Abhilash, and he's definitely the expert, especially if you are > using the containers he creates and distributes. But there's some > information here he hasn't mentioned yet. > > Please consider the following discussion to be background that allows > you to understand some of the considerations. I've only run the > Mailman 3 suite with all three running constantly on the same host, so > I have no experience with this kind of issue. > > eugenio.jordan(a)esa.int writes: > >> Our customer is currently using PostGRESQL as backend, and we would >> like to perform some maintenance tasks, namely running vacuum full, >> or at least trying to rebuild hyperkitty_email primary key related >> index. We have been asked on the real impact of putting in place >> such initiative. Though the latter is related to archiving, I >> haven't found a way to stop just Hyperkitty or Django related >> processes other than stopping Mailman's core, hence preventing >> mails addressed to distribution lists from being delivered, could >> you please confirm if I am correct? > > Mailman core can certainly run without either Postorius or HyperKitty. > Controlling Mailman core (moderation, helping users) without Postorius > is annoying, but it can be done. If you stop the HyperKitty process, > what should happen, I believe, is that posts for archiving will > accumulate in the 'archive' queue until HyperKitty is available again. > > It's been a while since I studied this so I could be completely wrong, > but as I understand it HyperKitty and Postorius are not daemon > processes. Rather, they are WSGI applications, which means they are > subprocesses spawned by your webserver, and controlled by it. In > order to keep them from running, you would reconfigure the webserver > to not call those WSGI applications. How that is done is specific to > the webserver and the WSGI module. If you are running from Docker > containers, most likely, you can just stop their containers. Yeah, Postorius and Hyperkitty themselves aren’t daemons, but they run inside WSGI servers like uwsgi/gunicorn which are typically separate daemons than webserver like Nginx which sits in the front. However there are common webserver modules like mod_wsgi (for apache2) which will let you run without managing a separate WSGI server. So, it depends on the setup, you can either just stop the WSGI server or stop the web server. For, containers, the WSGI server (uwsgi) runs in the container and you can just stop the mailman-web container. -- thanks, Abhilash Raj (maxking)

3 years, 8 months

[MM3-users] GNU Mailman condemns reinstatement of RMS

by Abhilash Raj

To the Mailman community, The GNU Mailman Steering Committee condemns the reinstatement of Richard M. Stallman (RMS) to the Board of the Free Software Foundation (FSF), and has taken the following actions: 1. On behalf of the GNU Mailman project, signed the letter on GitHub[1] calling for the removal of the entire FSF Board, as well as RMS himself. 2. Started exploring ways to move our financial assets, for decades managed by the FSF, to new management. The management fees are small, but this is an important symbolic protest. 3. Started exploring how to leave the GNU Project. On the one hand, if we leave but GNU wants to maintain a "GNU Mailman" project, we cannot stop them, confusing users. On the other hand, RMS is leader of the GNU Project, and has intervened in Mailman affairs on many occasions. We should forestall this in the future. We wish to explain our actions to the community. Although free exchange of software among users is a practice that goes back to days of the earliest general purpose computers, RMS was the first to propose a complete free software distribution, and is the acknowledged founder of the Free Software movement. Even leaders of the Berkeley Software Distribution (BSD) acknowledge this. We all owe him a debt for this. Nevertheless, the movement has matured and thrived, spawning the competitive open source movement, with whose philosophy Mailman is more closely aligned. While we acknowledge our debt to RMS, we don't need him any longer. And unfortunately, he has become both a symbol and a source of the toxicity in tech communities. The FSF Board did the right thing by accepting RMS's resignation. They did the wrong thing by reinstating him. RMS has a long history of abusive behavior and toxic political positions. A small part of it is described in the open letter on GitHub[1] and its references[2], and several members of the Steering Committee have observed it directly. All of us have heard stories directly from those who were abused or observed it directly. His political positions are public, for example his support of pedophiles. He claims that he in no way supports abusive relationships with children, yet refuses to acknowledge that children are generally in no position to provide consent, an evasive and highly toxic position. There is no question: RMS is toxic. We came for mailing list management, but we stayed for the community. We have a right to protect our community by dissociating it from toxic influences. We do not want our project associated with such a person, nor to provide economic resources to organizations that promote him to leadership positions. We are taking these actions to protect our community, both the narrow community of Mailman developers and users, and the broader open source community, from his toxic behavior and from the reputational damage that will come from helping to enable him. While we have no information suggesting that other members of the FSF Board are similarly toxic as individuals, as a group they enabled RMS for decades, and now have taken an explicit step in enabling him again. If they want to regain their position of respect and acceptance in our community, they must acknowledge their error, and we don't see -- given their reinstatement of RMS himself -- how they can do so convincingly while maintaining their positions on the Board. They must resign, and a new Board composed, to demonstrate their sincerity. What they do is up to them, of course, but if they do not take radical steps, we will continue to consider association with the FSF a threat to our community. For the Mailman community, Abhilash Raj (project leader) Mark Sapiro Stephen J. Turnbull Aurélien Bompard Terri Oda Barry Warsaw John Viega (founder) [1] Text and signatures: https://rms-open-letter.github.io [2] Appendix to the letter: https://rms-open-letter.github.io/appendix Related statements: https://rms-open-letter.github.io/statements

4 years

[MM3-users] Time Stand Still

by Barry Warsaw

Somewhen in the dark recesses of intarweb history, I found myself as the project leader for both Jython (née JPython) and GNU Mailman. I'd been involved with Jython since it was invented by Jim Hugunin around the time he came to work with us at Pythonlabs. I'd been contributing to Mailman since we inherited John Viega's Python-based Dave Matthews Band list server, and put it to use replacing python.org's Majordomo installation. I'd enjoyed both projects, but knew I could not lead both, so I had to make a choice. I chose to turn over Jython to a team that's done a much better job over the years than I ever could have. Something about email, and especially the communication and collaboration patterns that it facilitates, really fascinated me. I know, I know, but we all have our lapses of sanity. Mine has lasted almost 20 years, a bit more than "momentary" perhaps. I've rarely gotten paid to work on Mailman, but it did provide me some great opportunities. Most notably it led to my 10 year stint at Canonical. I was originally hired on there to integrate mailing lists with Launchpad, and Mailman was the obvious choice. I learned a ton doing that project, and working within the constraints of integrating the two Python-based systems, especially since Launchpad was originally not free software and Mailman was GPL'd. Later, the Zope-based Launchpad source code was released under the AGPL, making much of the monkeypatching unnecessary, but by then the system was solid and reliable, and you don't fix what's not broken. Except, I guess I did. I took a lot of the lessons from that work, along with a good hard look at all the problems with Mailman 2, and began to break another cardinal rule of software development: second system syndrome. The result is Mailman 3. It took forever, and we're still not at complete feature parity with Mailman 2, but at least it's Real Enough to be used at many Real Sites, including python.org and lists.fedoraprojects.org. It would be ridiculous for me to take significant credit for this. I have to acknowledge the amazing user community -- you! -- for all the support, patches, suggestions, feedback, patience, criticism, donations, and contributions that you've given to the project, and to me personally over the years. And my deepest gratitude goes to all the core developers that have stayed or come and gone, but most especially the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and every one of them is truly awesome, both in what they contribute technically, and in their amazing friendships. Mailman is infinitely better because of their involvement, and I've loved spending time with them over the years at the Pycon sprints, making releases and sharing teas and meals. My blog is called We Fear Change, and that's humorously taken from a 90's bit in Mike Myer's excellent Wayne's World movie (a phrase actually uttered by the brilliant Dana Carvey as Garth). The irony of course is that while we all may fear change, it's the one constant thing we can count on. And in fact, we *require* change to thrive, because if you aren't changing, you aren't alive. Time, and being engaged with life's vagaries, means there's no alternative to change; it must be embraced. And so, with a vague reference to the many (good!) changes in my personal and professional life, I'm announcing that I'm stepping down from the project leadership role of GNU Mailman, effective... nowish! And it's with unanimous agreement among the GNU Mailman Steering Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash Raj as the new project leader. If you don't recognize Abhilash's name, you probably aren't paying attention, at least to Mailman 3. Abhilash came to us in 2013 as a Google Summer of Code student, and he's become one of the project's most valuable contributors. His list of accomplishments is long, and it includes everything from redesigning the website, to integrating CI with our GitLab build system, porting our code to the SQLAlchemy ORM, adding MySQL support, revving up adoption through his Docker images, along with his great coding work on Core, Postorius, HyperKitty, and mailmanclient. This transition is good for the project too. Email, its defining protocols and standards, and its role in our daily lives, has changed profoundly since the early days of Mailman. A fresh perspective and enthusiasm will help keep Mailman relevant to the changing ways we -- especially the FLOSS and tech communities -- communicate. Please join me in supporting Abhilash in every way possible as he takes over in this new role as project leader. I'll be here when and if needed, even as I create space in my "spare" time for... Something Else. I look forward to the vision that Abhilash will bring to the project, and I know that he will do a great job. To me, Mailman has always been about collaboration, and the best way for it to succeed is for you to continue to contribute your insights, experiences, opinions, and skills with positive intention. -Barry https://www.wefearchange.org/

7 years, 5 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Stephen J. Turnbull

Lars Schimmer writes: > Hm, it completely ignores the standard way for Debian: > apt-get install mailman3-full > also exim4 as standard mailer. > And apache2. Right. The idea is that Debian is a *component* of *Brian's* system, not that Brian is installing a Debian system. One problem is that a lot of people like to run Debian Stable, which lags our releases by many months, sometimes a couple of years. A lot of people run a Debian Stable system plus a couple of mission-critical apps from source or from upstream repositories. We'd be happy to promote your "standard Debian" installation documentation as we will Brian's. :-) One thing about Brian's, though: as he says, he's going to use it himself, and will be keeping it updated because it's part of his business. It will take a pretty dedicated soul to keep up with him. It's not necessary to "keep up" to be very helpful to our users, of course. But I think Brian's document is likely to be the "gold standard" for a while. I understand why Abhilash wants it in the official docs. :-) Steve

4 years, 2 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Stephen J. Turnbull

jonathan.mailing.lists(a)gmail.com writes: > I just need instructions I can follow to start from scratch on a new VPS. I > don't mind whether it is for Linode and Debian, Digital Ocean and Ubuntu, or > whatever. Brian's guide is exactly what it sounds like you want, then. It's battle-tested in a large commercial service that has been around for a long time. He hasn't been using Mailman 3 at scale for very long (about three years, I think) but (almost) nobody else has used it at scale either.[1] Even Mark has only three or four separate systems (although he's probably up to about 100 or 150 lists running on Mailman 3; Brian has mentioned at least that many separate installations just this past week. > If this is the "idiot-proof" guide I mentioned in an earlier thread > then it's a very welcome development for Mailman 3. Be warned: nothing is proof against Internet mail. But with Brian's guide you'll be armored with a well-documented baseline. Footnotes: [1] fedoraproject is huge, but I think they run all their lists out of one server, or server farm. Not the same level of experience as multiple installations.

4 years, 1 month

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Abhilash Raj

On Tue, Mar 2, 2021, at 9:12 AM, Stephen J. Turnbull wrote: > Lars Schimmer writes: > > On 27/02/2021 04:02, Stephen J. Turnbull wrote: > > > > It's not necessary to "keep up" to be very helpful to our users, of > > > course. But I think Brian's document is likely to be the "gold > > > standard" for a while. I understand why Abhilash wants it in the > > > official docs. :-) > > > > If it should be a gold standard, it should mention the default setup of > > a standard debian system (which is exim4, btw) and not assuming a > > special setup debian system. > > "Gold standard" means it does what it sets out to *really* *well*. > "Gold standard" does not mean it does everything everybody wants. > In particular, much of the appeal of Brian's guide is that it's how he > sets up a Mailman 3 host, and he's proved it's repeatable, many times. > Anything that he doesn't use himself doesn't belong in his guide. > > We already have a descriptions of Exim (which I wrote the original) > and Apache setups in the "official" docs. There's no good reason to > treat Debian specially, since we don't distribute .debs ourselves. > It's not even clear that we should recommend apt-get mailman! And > surely no need, as that is the obvious (but not necessarily best for > any given server!) way to set up a Debian Mailman installation. But > there is good reason to believe that typical Debian installations will > be quite out of date, because most admins prefer to run a server based > on stable or LTS distros, not bleeding edge (Debian "sid") or even > beta (Debian "testing") distributions, while updates to Mailman > continue to be frequent and important to many or even most users. Also, FWIW, we do point users to Debian packages in the docs[1] and don't mind pointing users to other distro packages either. One thing I do want to clear out is that in my emails when I say "official install guide", my focus is primarily on installation using "pip". There are some distro level packages that even "pip" cannot install where we have to get specific and say, install this package when on debian/ubuntu and such. Like Steve mentioned earlier, Debian is just a part of the setup process because we rely on some packages like Postfix, Nginx, GCC etc. It is _relatively_ easy to update/maintain the "pip" installation guide for more distros where we provide instructions specific to Mailman and ask users to install the system packages that Mailman needs. My mantra with this[2] specific install guide is to be thorough enough for someone to setup latest Mailman 3, but doesn't care about which Linux distro they use, using pip on a Debian system (because that's what many of the developers use) but have enough pointers for someone using a different distro. The "default" choices are simply based on what we run and can provide some level of support for on this list. [1]: https://docs.mailman3.org/en/latest/install/install.html [2]: https://docs.mailman3.org/en/latest/install/virtualenv.html -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] Re: Time Stand Still

by Fabian A. Santiago

On November 23, 2017 11:38:00 AM EST, Barry Warsaw <barry(a)list.org> wrote: >Somewhen in the dark recesses of intarweb history, I found myself as >the project leader for both Jython (née JPython) and GNU Mailman. I'd >been involved with Jython since it was invented by Jim Hugunin around >the time he came to work with us at Pythonlabs. I'd been contributing >to Mailman since we inherited John Viega's Python-based Dave Matthews >Band list server, and put it to use replacing python.org's Majordomo >installation. > >I'd enjoyed both projects, but knew I could not lead both, so I had to >make a choice. I chose to turn over Jython to a team that's done a >much better job over the years than I ever could have. Something about >email, and especially the communication and collaboration patterns that >it facilitates, really fascinated me. I know, I know, but we all have >our lapses of sanity. Mine has lasted almost 20 years, a bit more than >"momentary" perhaps. > >I've rarely gotten paid to work on Mailman, but it did provide me some >great opportunities. Most notably it led to my 10 year stint at >Canonical. I was originally hired on there to integrate mailing lists >with Launchpad, and Mailman was the obvious choice. I learned a ton >doing that project, and working within the constraints of integrating >the two Python-based systems, especially since Launchpad was originally >not free software and Mailman was GPL'd. Later, the Zope-based >Launchpad source code was released under the AGPL, making much of the >monkeypatching unnecessary, but by then the system was solid and >reliable, and you don't fix what's not broken. > >Except, I guess I did. I took a lot of the lessons from that work, >along with a good hard look at all the problems with Mailman 2, and >began to break another cardinal rule of software development: second >system syndrome. The result is Mailman 3. It took forever, and we're >still not at complete feature parity with Mailman 2, but at least it's >Real Enough to be used at many Real Sites, including python.org and >lists.fedoraprojects.org. > >It would be ridiculous for me to take significant credit for this. I >have to acknowledge the amazing user community -- you! -- for all the >support, patches, suggestions, feedback, patience, criticism, >donations, and contributions that you've given to the project, and to >me personally over the years. And my deepest gratitude goes to all the >core developers that have stayed or come and gone, but most especially >the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark >Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and >every one of them is truly awesome, both in what they contribute >technically, and in their amazing friendships. Mailman is infinitely >better because of their involvement, and I've loved spending time with >them over the years at the Pycon sprints, making releases and sharing >teas and meals. > >My blog is called We Fear Change, and that's humorously taken from a >90's bit in Mike Myer's excellent Wayne's World movie (a phrase >actually uttered by the brilliant Dana Carvey as Garth). The irony of >course is that while we all may fear change, it's the one constant >thing we can count on. And in fact, we *require* change to thrive, >because if you aren't changing, you aren't alive. Time, and being >engaged with life's vagaries, means there's no alternative to change; >it must be embraced. > >And so, with a vague reference to the many (good!) changes in my >personal and professional life, I'm announcing that I'm stepping down >from the project leadership role of GNU Mailman, effective... nowish! >And it's with unanimous agreement among the GNU Mailman Steering >Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash >Raj as the new project leader. > >If you don't recognize Abhilash's name, you probably aren't paying >attention, at least to Mailman 3. Abhilash came to us in 2013 as a >Google Summer of Code student, and he's become one of the project's >most valuable contributors. His list of accomplishments is long, and >it includes everything from redesigning the website, to integrating CI >with our GitLab build system, porting our code to the SQLAlchemy ORM, >adding MySQL support, revving up adoption through his Docker images, >along with his great coding work on Core, Postorius, HyperKitty, and >mailmanclient. > >This transition is good for the project too. Email, its defining >protocols and standards, and its role in our daily lives, has changed >profoundly since the early days of Mailman. A fresh perspective and >enthusiasm will help keep Mailman relevant to the changing ways we -- >especially the FLOSS and tech communities -- communicate. > >Please join me in supporting Abhilash in every way possible as he takes >over in this new role as project leader. I'll be here when and if >needed, even as I create space in my "spare" time for... Something >Else. I look forward to the vision that Abhilash will bring to the >project, and I know that he will do a great job. To me, Mailman has >always been about collaboration, and the best >way for it to succeed is for you to continue to contribute your >insights, experiences, opinions, and skills with positive intention. > >-Barry > >https://www.wefearchange.org/ Congrats Abhilash! Love the docker images! Thank you Barry! Mailman rocks! -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

7 years, 5 months

[MM3-users] Re: Finding a user to delete them

by Brian Carpenter

On 3/14/20 5:03 AM, Stephen J. Turnbull wrote: > The bundled administrative interface*is* Postorius. The Mailman > shell is basically a quick hack (sorry Abhilash; if you want to call > it a masterwork and say the speed of development is testimony to your > skills, I won't deny it;-) to give more convenient access to > internals to experienced Mailman hackers. More administrative > features is something we plan to work on, but the Mailman project will > focus on Postorius for the forseeable future. I do think List Admins would want an interface to help "manage" a user account on behalf of a user then what is currently available in Postorius. I see this come up with my Mailman 2 clients frequently. For instance, a mm2 list member asked their list admin to subscribe them to a list topic to limit the amount of messages they receive. The list admin was new and open up a ticket to find out how they do that in which I replied showing them how they as a list admin, can go in and change options on behalf of a list member. I don't see this functionality built into Mailman 3 nowhere near the extent that Mailman 2 has. Last night a Mailman 3 client wanted to know how they can add a real name to a list member. I said you can't, not as list admin. I directed them to instead of unsubscribe the member and mass subscribe them so they can include a real name along with the email address of the list member. > For alternatives to Postorius and the Mailman shell, Brian Carpenter > (follow Allan's subthread) is working on a new management UI (using > PHP), and I believe there's a working node.js API "out there > somewhere". Please be very considerate of Brian's time; he and EMWD > constitute a bulwark of the Mailman ecosystem and will be even busier > with the UI project. But do pass on your suggestions to him as well > as to us, he's indicated he's open to that. There were some very good suggestions that were brought out in this thread and I had already passed them on to my developer. My approach with Affinity is definite leaning very heavy on the needs of list admins atm. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 1 month

[MM3-users] Re: The future is here?

by Abhilash Raj

On Sat, Jan 9, 2021, at 9:49 AM, Stephen J. Turnbull wrote: > Hans-Martin Mosner writes: > > > I'm pretty comfortable with docker containers, mailman and postfix > > in somewhat unsual configurations, and would like to help out there > > (with limited time, though, but I can justify some on job work > > time). > > Cool! > > > What would be the most helpful contribution? I see that there are > > some pull requests that are not yet integrated, but didn't check > > whether they require additional QA to be integrated or are just > > backlogged. > > > Would you rather like assistance in integrating existing pull > > requests, QA work to make them integration-ready, or work on > > untackled issues to create more pull requests? :-) > > Abhilash is busy, so in case he doesn't answer quickly, I offer my > thoughts. But Abhilash he is the most important developer on the > containers. > > If you are considering formal membership in the core (ie, direct > commit privilege, with an informal expectation of review from "more > senior" core devs), integrating existing pull requests might be top > priority, to get practice in that. Otherwise, reviews and triage on > all container issues, and QA on existing pull requests, are probably top > priorities IMO. Thanks Steve for the quick response! I agree with Steve that most help would be with QA on existing issues and PRs. There aren’t many PRs pending, but some of them are pending because I am a bit weary of existing users breaking due to things like upgrading database versions etc. I don’t think there is a good way to handle those, other than just minor/major bumping versions of the release. I’ve been debating it in my head for a while whether it makes sense to bump a minor version for a ‘sample configuration’ (docker-compose.yaml file) bumping the version of a database. Perhaps caution in documentation to verify the side-effects to simply applying the configuration from the git repo is enough? There are a lot of tickets labelled ‘documentation’ that are rather low hanging fruits to be tackled easily. If you want to tackle something bigger, you help create a new compose configuration that adds a web server and MTA for a rather ‘complete setup’. I’ve just started labelling important issues with ‘priority p0’, so that might also be a good starting point. There aren’t many issues, but some tracker grooming/prioritization is needed too ;-) Abhilash > Steve > _______________________________________________ > 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, Abhilash Raj (maxking)

4 years, 3 months

[MM3-users] Mailman backend maintenance task

by Stephen J. Turnbull

Hi, Eugenio, I wrote this earlier but am in the middle of moving my office so my mail has been intermittent. I have been following your discussion with Abhilash, and he's definitely the expert, especially if you are using the containers he creates and distributes. But there's some information here he hasn't mentioned yet. Please consider the following discussion to be background that allows you to understand some of the considerations. I've only run the Mailman 3 suite with all three running constantly on the same host, so I have no experience with this kind of issue. eugenio.jordan(a)esa.int writes: > Our customer is currently using PostGRESQL as backend, and we would > like to perform some maintenance tasks, namely running vacuum full, > or at least trying to rebuild hyperkitty_email primary key related > index. We have been asked on the real impact of putting in place > such initiative. Though the latter is related to archiving, I > haven't found a way to stop just Hyperkitty or Django related > processes other than stopping Mailman's core, hence preventing > mails addressed to distribution lists from being delivered, could > you please confirm if I am correct? Mailman core can certainly run without either Postorius or HyperKitty. Controlling Mailman core (moderation, helping users) without Postorius is annoying, but it can be done. If you stop the HyperKitty process, what should happen, I believe, is that posts for archiving will accumulate in the 'archive' queue until HyperKitty is available again. It's been a while since I studied this so I could be completely wrong, but as I understand it HyperKitty and Postorius are not daemon processes. Rather, they are WSGI applications, which means they are subprocesses spawned by your webserver, and controlled by it. In order to keep them from running, you would reconfigure the webserver to not call those WSGI applications. How that is done is specific to the webserver and the WSGI module. If you are running from Docker containers, most likely, you can just stop their containers. The larger problem is that Mailman core uses a RDBMS. Normally both Django and Mailman are referring to the same RDBMS, PostgreSQL in your case. I'm not familiar with the vaccuum operation; if it requires taking the whole RDBMS down, and Mailman is running on that RDBMS, you're out of luck. Mailman can accept posts and queue them, but it can't deliver them to subscribers without access to the RDBMS tables. If it's just a matter of locking some tables while other are available, then it should work because the tables used by core and HyperKitty are disjoint as far as I know. (I think Postorius and HyperKitty both use Django's user tables for authorization, so at least for those tables both Postorius and HyperKitty will have to be down, but core can continue running because its database is completely separate.) > Regarding the former, as far as I have read, the "mappings" lists > -> addresses are stored just in the database, so if we run some > kind of procedure or task like vacuum which will lock exclusively > tables, or want anyway to have the database stopped for a cold > backup or whatever, Mailman willl not work, that is, again the > mails addressed to the distribution lists will not be > delivered. Will you please confirm this point, too? That depends on how "vacuum" works. If you can tell the RDBMS not to lock Mailman core's tables, it can continue to run. Definitely if the database is not running, Mailman will continue to receive and store the posts, but it won't be able to distribute mail to subscribers until its tables are available again. At that point the queued posts will be processed normally, except that if there's a large backlog, they won't go out in a quick burst, it may take a while. One possible worry, depending on how you are connected to the Internet, is that your provider may interpret the sudden burst of outgoing mail when Mailman comes back on line as spam or some other sort of mischief. Mailman has no way to throttle this: it feeds messages to the MTA until the MTA says "stop". Then it waits until the MTA is ready again. Regards, Steve

3 years, 8 months

[MM3-users] Re: Strange messages after upgrading Mailman3

by Allan Hansen

I asked the poster of one message what he had done. Apparently, he had put the list address (just one list, according to him) in the Bcc: field. The message was then held for moderator approval and, when approved, sent out without a body. Another message was stopped because it did not have a subject field. Again, it was approved and then sent out without a body. From what I can see (the hold messages are sent to me as well), the messages were stripped after approval, as the approval messages have the message bodies. I will try to ask my moderators not to approve messages that are held by the server and instead reply to the senders and discard the messages. Yours, Allan P.S.: I had hoped that the upgrade would now allow the moderators to see the list of members, as that is enabled for each of my lists. It's now our top issue, with the change-of-address issue made easier. If moderators should not see the members list then maybe a third option on the menu should be 'Only list owners.' But it would be good for the moderators to see the list, as well as being able to subscribe and unsubscribe members. On 12/5/22, 9:39 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 12/5/22 08:56, Allan Hansen wrote: > Thank you, Mark, as always. > > We upgraded to the latest versions: > > Mailman Core Version GNU Mailman 3.3.7 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.9.2 (default, Feb 28, 2021, 17:03:44) [GCC 10.2.1 20210110] > > Also, I don't have any umbrella lists. I need more information about this. As far as I know, this can only happen with messages that are cross posted to multiple lists and held for moderator approval on more than one list. This should have been fixed in Mailman 3.3.6 by <https://gitlab.com/mailman/mailman/-/merge_requests/932>. This should never happen with a post that is delivered to members without being held. Also, I think when this happens to a delivered post, the post in the archive will also have the content lost message. I would like to get as much information as possible about the circumstances when this happens. In particular, was the post held for moderation, was it posted to multiple lists, for how many lists was the content lost. Also, it may help to see the full raw message with the content lost notice. (If there are privacy concerns you can send these to me off list) -- 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: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/33OOQ4DNXTJUNT65CD2KHMOSCAIMRSLL/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/jpeg Name: members.jpg

2 years, 4 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Brian Carpenter

On 11/21/20 10:39 AM, Stephen J. Turnbull wrote: > Rob Jenson writes: > > > I need to strip DKIM headers on the inbound messages to my list or > > to my domain. > > Why do you need to strip DKIM headers? The standard specifies that an > invalid DKIM signature must be treated the same as if there were no > signature at all. So an invalid DKIM signature may be treated as > spammier than a message with a valid signature, but that should not be > treated differently from an unsigned message (as would appear after > removing those header fields). > > I know this feature is in demand from list admins, but I've never seen > convincing evidence that it's actually effective for any of the usual > suspects (Yahoo!, AOL, Gmail), only for small domains with pigheaded > admins who are proud of their non-conforming configurations, and > announce that they are discarding messages which have invalid DKIM > signatures. This person is a client of ours for now. There is no evidence at all that I can see from our outgoing SMTP logs for such a requirement. In fact mail delivery to Yahoo and its other domains (verizon, aol) has been great. There are some small deferrals that occur over a small period of time (which is strange) daily but those clear out of the queue within an hour. I was personally shocked when he brought these concerns to this list without asking or informing us. > > We are munging the text of the message in Mailman, so the DKIM > > headers from the original poster are invalid. > > As I explained above, both DKIM and DMARC are specified so that "no > signature" == "invalid signature" for the purposes of spam processing. > Are you sure that Yahoo! (or any other provider used by your > subscribers) is treating invalid signatures differently from absence > of signatures? The person responsible for Yahoo! MTA configuration is > a well-known mail security expert who participated actively in the > specification of all these protocols (and she also gave me a kitten, > so I may be biased). I have the same question Steve. I see no proof for such a practice nor came across any documentation regarding such. The number one reason why Yahoo defers mail is mail volume from what I see. I don't even think they are hard on SPF violations as other ISPs such as Google. > > > As far as I can see, our service provider is using ARC in our > > Mailman configuration, but not signing the outbound messages with > > DKIM. > > That surprises me. ARC isn't really a substitute for the MTA's own > DKIM signature, at least not yet. It ought to surprise you because we are not using ARC. His comment surprised me as well. Again I have no idea where he gets that from. He certainly did not bring that to my attention nor presented proof. > > Therefore the DKIM signature from the poster's mail service > > provider is sent out with their DKIM header, which seems to be > > problematic. > > It shouldn't be. I agree. It shouldn't be and it's not. Otherwise this would impact all lists that are DMARC munging their Mailman 3 lists unconditionally. It's not. > > > If I understand ARC correctly, it is validating the DKIM signature > > from the poster, creating a new signature and metadata indicating > > that what it received was properly signed. > > That is correct. As far as I know, Yahoo! does participate in the ARC > protocol and used to have conforming implementations of DKIM and > DMARC. That doesn't mean you get a free ride: they may still have > your IP on a blacklist from former owners of the IP, for example. Or > your posts may "look like" spam for some other reason, or your lists > may need more time to build up a clean reputation. But I need > evidence more convincing than "list posts are recognized as spam" to > believe that removing DKIM headers will help. (For example, my > employer's filters regularly recognize messages from department heads > as spam, even with DKIM signatures intact. ;-) This particular client did bring up some Yahoo issues a week ago which I looked into it. The conclusion was Yahoo is deferring a small percentage of outbound mail for a small period of time due to mail volume. Overall we have great successful deliveries to Yahoo addresses on our Affinity server. So I am simply surprised at his communication sent to this list. Yahoo delivery always improves when mail volume becomes more consistent. That week we have moved over a moderate amount of lists that had a few dozen Yahoo members. That caused our SenderScore.org rep score to drop from 98 to 96 (which is still a very high reputation). It's back up to 98 (pats myself on the back) because the new outgoing mail volume has become more consistent. Eventually we will fill up the server and will bring up a new server to add new lists to. This approach has worked well for all of our servers for years. So conclusion: broken DKIM signatures are not playing a part with his issues at all. At least from the evidence I have seen. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Found error in docker-container

by Alexander Klotz

Hi, one of our developers wanted to point out an error he found in mailman 3.1, docker container maxking/mailman-core-0.1 The entries in /opt/mailman/core/var/data/postfix_lmtp are not set correctly, example: /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP Address of mailman-core container]:8024 this actually should look like this: /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 Regards, Alex

7 years, 9 months

[MM3-users] Re: Disabling Gravatar

by Stephen J. Turnbull

Daniel writes: > I meant that it is against RFCs to use this IP address range in the real > internet. It's also against RFC 5737 to use it locally: it should *never* resolve to a real host. So if the purpose is to substitute a non-working address, this would do (especially if you implement the RFC's suggested restriction that it be filtered locally, but packets to that addressed should be rejected, not discarded by such a filter). On the other hand, if Marvin wants to implement a GDPR and Gravatar- compatible server, he should use a private address outside of the reserved ranges listed in RFC 5737. Steve

7 years

[MM3-users] Mailman3 and Exim setup

by brian＠emwd.com

I am installing Mailman3 via the Docker image provided by maxking. In his instructions he says: "To use Exim4, it should be setup to relay emails from 172.19.199.3 and 172.19.199.2." I am not sure where in the exim.conf file this is done. I took a guess at: hostlist relay_from_hosts = localhost : 172.19.199.3 : 172.19.199.2 Was my guess wrong?

6 years, 4 months

[MM3-users] Logging of unsubscribe process

by Johannes Winter

Dear MM3 list, I was wondering whether the unsubscribe process is logged. One user accidentally hit "unsubscribe all" aborted the process but is now unsure whether he accidentally deleted users. Is there a easy way to check? Best regards, Johannes Winter

6 years, 2 months

[MM3-users] Re: How to run 'manage.py update_index_one_list' command.

by Mark Sapiro

On 2/25/20 3:46 PM, Brian Carpenter wrote: > On 2/25/20 6:26 PM, Frank van den Heuvel wrote: >> What can I do to get the newly imported posts indexed? > > I am not sure if this would be helpful but you can try running: > > /opt/mailman/mm/bin/mailman-post-update That won't help for this, although the contents of that script, if he has it, will point to the correct Django management command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by kelly.close＠lrewater.com

I got this one figured out - earlier in this post Robert Lister provided the answer in fact, but I didn't quite "get" what he was saying at first. Please see my reply to his post in this thread. ~Kelly

4 years, 10 months

[MM3-users] Unsubscribe Notifications Clarification

by Brian Carpenter

I am trying to understand how Mailman 3 handles unsubscribe notifications. From my testing I see the following behavior: 1. If list member sends email to listname-leave@listname, an unsubscribe notification is sent to both list owner and list member if list settings have them enabled. 2. If list list member is a registered user of Postorius and he uses Postorius to unsubscribe, then no notification is sent out to either list owner or list member, even if list settings has unsubscribe notifications enabled. Is this correct? Brian

4 years, 7 months

[MM3-users] Implicit Destination Meaning

by Brian Carpenter

I just migrated a MM2 list to MM3. The client had no problem sending posts to his list with MM2. However when he posted to his MM3 list, it showed up in the moderation queue: ============ Your mail to 'dogs(a)lists.redacted.org' with the subject mailing list changes Is being held until the list moderator can review it for approval. The message is being held because: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. =========== Is there a List Setting somewhere that needs to be adjusted to allow this sender to post without moderation? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Moderation Action Changed After Import

by Brian Carpenter

I migrated a Mailman 2 list using import21 and the list's config.pck into a Mailman 3 list. The list owner reported back that about 98% of the list members had their moderation setting changed to Reject (with notification). He said the previous moderation was the list's default which was hold for moderation. Is such a thing possible with an import job? Is this perhaps a bug that has been reported previously? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Unknown templates being used

by Brian Carpenter

On 2/14/21 8:15 PM, Mark Sapiro wrote: > I agree and appreciate that Brian is very supportive. In my initial > reply, it was not clear to me that Brian had referred you here which is > the only reason I pointed out that he was your primary line of support. It really didn't matter as the question by Tom was clearly related to Mailman 3 and not to Affinity. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Domain ownership issues

by peter＠chubb.wattle.id.au

>>>>> "peter" == peter <peter(a)chubb.wattle.id.au> writes: peter> Hi, I wanted to give another user the ability to create lists, peter> so added that user as 'owner' of the domain. But he does not peter> see the 'create list' button. peter> I decided to try deleting him as owner, and the result is a peter> python exception: The 'error on deletion' goes away after upgrading to Mailman 3.3. But the original issue (domain owners can't create lists) is still there. Peter C

4 years, 1 month

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Brian Carpenter

On 3/24/21 2:00 PM, Jim Popovitch via Mailman-users wrote: > 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/>;: Has anyone asked Danil if he is willing to hand over the mailman3.com domain to the Mailman 3 development team? I think that would be a nice gesture. Same with Mailman4.com. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 1 month

[MM3-users] Re: ModuleNotFoundError: No module named 'settings'

by mm3＠steele.com

I just joined this list a few minutes ago to ask about he exact same issue. Hopefully someone will be able to help both of us.

3 years, 11 months

[MM3-users] Sad news - Brian Carpenter

by smorytko＠gmail.com

https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… I mentioned some "unfortunate circumstances" in a recent post. An inquiry from Mark Sapiro prompted me to do a search and I sadly found this. Brian's company managed our list and on 4/22 we became aware that he was hospitalized with Covid. Rest in peace Brian. Steve Morytko

3 years, 11 months

[MM3-users] Sad news - Brian Carpenter

by blackout69

Il 12/05/21 21:45, smorytko(a)gmail.com ha scritto: > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > I mentioned some "unfortunate circumstances" in a recent post. An inquiry from Mark Sapiro prompted me to do a search and I sadly found this. > Brian's company managed our list and on 4/22 we became aware that he was hospitalized with Covid. > Rest in peace Brian. I knew Brian from this list. I read his posts with great interest because I considered him a person of great competence and seriousness. We will miss him very much. Rest in peace Brian. 😞 -- blackout69

3 years, 11 months

[MM3-users] domain owner role

by Rainer Herbst

Dear all, recently, I have added one account to a domain as domain owner. I did expect the new owner to see all lists in that domain in Postorius, but he sees no list at all. Is this the way it should be? How can I add administrators able to perform administrative tasks on all lists in Postorius? Viele Grüße, Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 -----------------------------------------------------------------------------------------------

3 years, 7 months

[MM3-users] Docker container issues.

by Mark Sapiro

There have been a few recent requests for help with the Mailman Docker container images. These are packaged by Abhilash and I have no experience with Docker at all. The doc at https://docs.mailman3.org/en/latest/install/docker.html points to detailed docs at https://asynchronous.in/docker-mailman/ and suggest that issues should be reported on GitHub https://github.com/maxking/docker-mailman/issues where Abhilash will respond as he can. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Equivalent of listadmin Perl script for Mailman 3?

by Philip Colmer

Hi We're preparing to migrate about 4 Mailman 2 servers to Mailman 3. In doing so, one of our list administrators has informed us that he uses "listadmin" (Petter Reinholdtsen: listadmin, the quick way to moderate mailman lists - nice free software (skolelinux.org) <http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate…> ) Does anyone know if there is an equivalent tool that works with Mailman 3? Thank you. Regards Philip

3 years, 5 months

[MM3-users] How can I remove anything added by Mailman 3 to the forwarded email

by gscaglia＠ksdata.it

I need to use Mailman 3 exclusively for forwarding emails to my customers divided by type. The emails must arrive exactly as they are, without any additions, and the lists are managed only by me: the customer ignores that he is subscribed to a list and receives the message as if it were one to one. How can I remove anything added by Mailman 3 to the forwarded message, therefore also the links for managing my membership (unsubscribe and modify)? Thanks a lot, Luca

2 years, 11 months

[MM3-users] Need help getting MM3 up and running on Ubuntu 20.04

by Marisa Giancarla

I asked for help before and someone helped me, but I couldn't pay the amount he requested right away and all my contact info for hoim seemed toi disappear so I am asking again. I can't afford to pay but I can provide monthly data center hosting in return. I need it running on Ubuntu 20.04. If you can help please email me at fstltna(a)yahoo.com. Thanks! Marisa

1 year, 11 months

[MM3-users] Re: Setting up on ubuntu server 22.04

by Stephen J. Turnbull

Odhiambo Washington writes: > And I think the 'slightly more complex way' is a better choice as > it lets one not get stuck with old software versions :) It may also cause other dependency problems, though. Unless you know what you're doing enough to be willing to try to diagnose and handle them yourself, we'd generally prefer you stick to the currently released Mailman suite. I guess Mark's recommendation signals that he believes that 3.3.9b1 is pretty much ready for prime time, so in this particular case it's a reasonable option. I wouldn't say it's "better" though. Steve

1 year, 6 months

[MM3-users] Default templates

by Steve Brown

I'm new to this list and newly a Mailman list administrator. I know I can customize message templates and have done so for my list's Welcome message. My problem is knowing what I'm replacing when I create a "new" template. How/where can I see he default content? Steve Brown

1 year, 5 months

[MM3-users] Re: Sad news - Brian Carpenter

by Mark Dadgar

On May 12, 2021, at 12:45 PM, smorytko(a)gmail.com wrote: > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > > I mentioned some "unfortunate circumstances" in a recent post. An inquiry from Mark Sapiro prompted me to do a search and I sadly found this. > > Brian's company managed our list and on 4/22 we became aware that he was hospitalized with Covid. > > Rest in peace Brian. That’s awful. Brian was a great help to me in setting up a solid MM3 installation after my mess of a self-install and he’s been a constant source of assistance on this list. RIP Brian. 😞 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 11 months

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by Mark Sapiro

On 4/13/22 05:23, Paul Ssekamatte via Mailman-users wrote: > hi William, > please clarify what you mean by this step > 8. You need to manually set the local virtual host for mailman3 > Thank you He means that if you are going to use the alias domain feature discussed at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… you need to actually set the value you choose for the alias_domain in the Postorius domains view or via REST or `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Mailman3 and Exim setup

by Abhilash Raj

On Wed, Dec 19, 2018, at 12:59 PM, brian(a)emwd.com wrote: > I am installing Mailman3 via the Docker image provided by maxking. In > his instructions he says: > > "To use Exim4, it should be setup to relay emails from 172.19.199.3 and > 172.19.199.2." > > I am not sure where in the exim.conf file this is done. I took a guess at: > > hostlist relay_from_hosts = localhost : 172.19.199.3 : 172.19.199.2 I think this is correct. > > Was my guess wrong? > _______________________________________________ > 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, Abhilash Raj (maxking)

6 years, 4 months

[MM3-users] installing a new instance of mm3

by Stephen J. Turnbull

It should be, except possibly for configuring new features added since he last updated that document. But there aren't that many of those. Christian Stalberg via Mailman-users writes: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > Brian installed my instance. Now its broken. My lists are down. I'm getting > nowhere with diagnostics and troubleshooting (which was easier with mailman > 2). > > I'm considering a new install, hence the question. > > Thanks! > > _______________________________________________ > 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, 6 months

[MM3-users] Re: Trying to set up mailman3 on my mail server

by Mark Sapiro

On 10/15/21 9:32 AM, Mark Dadgar wrote: > > That’s actually why I paid someone to do in the initial install. While I have 3+ decades of UNIX-like admin experience, I am not even remotely well-versed in Python and its ecosystem and/or Docker. > > Unfortunately, the person I hired, who did a great job and has contributed mightily to this community, is no longer with us. He did however post a writeup at <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10>. There is also <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…> from another user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Logging of unsubscribe process

by Abhilash Raj

On Fri, Feb 15, 2019, at 3:41 AM, Johannes Winter wrote: > Dear MM3 list, > > I was wondering whether the unsubscribe process is logged. One user > accidentally hit "unsubscribe all" aborted the process but is now > unsure whether he accidentally deleted users. Is there a easy way to > check? I don't think so, but there is a REST API query generated for every single email address. So, you might be able to check your WSGI/web server logs for requests. > Best regards, > > Johannes Winter > _______________________________________________ > 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, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: Adding users

by horvath.arpad.szfvar＠gmail.com

Hi All, From Mark Dale, I've got a suggestion to use mass subscription. I've tried it before without success, but it worked now. I've done it before, but the user from the yahoo.fr domain didn't get the email, we've not found it neither in the normal folder nor in the spam. He is still hanging. And now this new member wrote to me, that she replied to the email, but it didn't work. But it worked in the end when she tried it next time. In mailman 2 there was an option to just add users without sending email out and trusting the users to do exactly what they need to do. I miss it very much. Thanks, Arpad

2 years, 5 months

[MM3-users] Re: Default templates

by Mark Sapiro

On 11/8/23 16:01, Steve Brown wrote: > I'm new to this list and newly a Mailman list administrator. I know I can customize message templates and have done so for my list's Welcome message. My problem is knowing what I'm replacing when I create a "new" template. How/where can I see he default content? The fact that Postorius doesn't show it to you is https://gitlab.com/mailman/postorius/-/issues/366 The defaults are in your installation at mailman/templates/en/ or in GitLab at https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en or in the directory https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/ for other languages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Equivalent of listadmin Perl script for Mailman 3?

by Mark Sapiro

On 11/16/21 11:48 PM, Philip Colmer wrote: > Hi > > We're preparing to migrate about 4 Mailman 2 servers to Mailman 3. In doing > so, one of our list administrators has informed us that he uses "listadmin" > (Petter Reinholdtsen: listadmin, the quick way to moderate mailman lists - > nice free software (skolelinux.org) > <http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate…> > ) > > Does anyone know if there is an equivalent tool that works with Mailman 3? I'm not aware of any, but others might be (I wasn't aware of `listadmin` before reading this post). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: How to store additional information about lists?

by Stephen J. Turnbull

Mark Sapiro writes: > On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > Membership adapter is a Mailman 2 feature that allowed use of an > > external membership database (such as a corporate LDAP system). I > > thought it was ported to Mailman 3 but maybe not. > Actually, it's not quite that simple. Mailman 2.1 defines a > MemberAdaptor class, [...]. > The Mailman 3 analog of this is the IMember interface defined in > mailman/interfaces/member.py and implemented in mailman/model/member.py OK, but for Andi it is "simple" in the sense that he doesn't have an existing MemberAdapter, so the plan is "Implement the IMember interface". Easy to say, maybe not so easy to do. ;-) Steve

3 years, 10 months

[MM3-users] How to import mailman2 into mailman3 in Docker, getting error with archives.

by bob B

I know you can't run mailman commands in the docker images and I have to copy the data to an area where he docker images can access it, but in looking that the commands I got the list settings to import docker exec -it mailman-core mailman import21 [REDACTED](a)REDACTED].REDACTED].org /opt/mailman/migration/config.pck *** this worked But having issues importing the archives? do i run this on mailman-core OR mailman-web? I tried both but it does not like python? docker exec -it mailman-core python manage.py hyperkitty_import -l [REDACTED](a)REDACTED].REDACTED].org /opt/mailman/migration/[REDACTED].mbox OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "python": executable file not found in $PATH: unknown

3 years, 7 months

[MM3-users] Re: Easiest way to install a new mailman3 deployment?

by Mark Dadgar

On Jan 1, 2021, at 12:20 PM, Allan Hansen <hansen(a)rc.org> wrote: > I asked Brian to help with the installation of Mailman after I and 2 experts each made attempts and got bogged down in incomprehensible installation instructions and gave up. Brian did it in short order and has been extremely helpful since. I did the same, even after running MM2 for ~20 years and actually successfully getting the mm3 Debian packages running on my own (but wanting to migrate off them because they are quite far behind the state of the art). > No, he is not paying me for this. No, I have not invested in EMWD. > Yes, I just want to recommend a service that is more than worth it. +1 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 3 months

[MM3-users] Re: Python is updated

by Mark Sapiro

On 4/29/23 01:44, Odhiambo Washington wrote: > On Sat, Apr 29, 2023 at 8:25 AM Lars Bjørndal <lars(a)lamasti.net> wrote: > >> So you have settings.py in /opt/mailman/mm rather than in /etc/mailman3? >> > > That's right - based on an earlier installation method before the official > virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> > one was put together, and that's why he has that shell file. > For a virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> > setup, your settings should live in /etc/mailman3 as stated. If you are interested in background on prior installation methods and their evolution, see https://wiki.list.org/x/17891998 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: How to delete non-users

by Mark Sapiro

On 9/16/22 16:40, Allan Hansen wrote: > Hi Mark, > > Thank you for looking into it. > > We are very strict about memberships, which we are because of spam, bots and malicious contributors and because we don't want anyone to think that our lists are used for spam: > > When a user applies, the server sends a message to the moderator. > The moderator communicates with the potential member and accepts or does not accept the application. So Subscription policy is Moderate or Confirm, then moderate. > At this point, if the user has not been accepted, but tried to send a message to the list, a non-member membership is created. Yes. This is expected. > When he/she logs in to list his/her account, the list to which he/she holds non-memberships will be listed and the user will think that he/she has been properly subscribed (why else are the lists listed). I'm guessing you are talking about the https://www.example.com/mailman3/accounts/subscriptions/ page. On that page, all membership roles (owner, moderator, member, nonmember) are listed. Note that if the user goes instead to info page for the list, appropriate pronoun will be presented with a subscribe form. > Noone notices the column that shows the role as 'nonmember.' So he/she thinks that the subscription request has been accepted, but nothing is working. That's why the 'non-member' record is an issue. I also don't see why non-members are automatically added, filling up the database with junk (at least from our point of view, with all respect). That's the way Mailman 3 is designed. Changing it would be a major undertaking. Consider the case where default nonmember action is hold rather than discard. Then when handling a nonmember post, the moderator can set the nonmember's moderation to default processing to essentially accept future posts from that nonmember if the nonmember has a legitimate reason to post, or to discard if the nonmember is a spammer. If you think it would help, you might consider colorizing the roles on that page so perhaps nonmember could be in red. This should be a simple patch to Postorius. > But our lists don't accept messages from non-members. Such messages are quietly discarded, as most are spam, as mentioned above. > So now the user is neither getting emails from the lists nor is unable to send messages to the list. > The next step for the user is to complain to me. ☹ Why didn't you (or the moderator) accept the held subscription at the beginning? > I have looked for a template that could be used to warn someone when he/she is added as a non-member, but did not find one. It's also not clear that I'd want one, as most of these non-subscriptions are by spammers and I prefer not to reply to spammers. __ > > I tried your suggestion below, Mark. > Here's my transcript: > > ********** > 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. > >>>> lm = getUtility(IListManager) >>>> for l in lm: > ... for nm in l.nonmembers.members: > ... nm.unsubscribe() > ... >>>> > ********** > I did this twice, once with commit() and once typing ctrl/d (ctrl/D) just gave me a beep. > Calling commit() did not return to the ... as in your example, but showed the >>> prompt, so I tried ctrl/D (beep) and then ctrl/d (exit). My example did not show a `...` in response to commit(). Commit() was followed by three backticks which is markup for the end if the literal text. The >>> following commit() is expected. Either calling commit() explicitly or exiting with ctrl-D should commit the changes. > I then went to the Postorius page for one of the lists and found that all the non-members were still present. I don't know why this would be. I tested that script and it worked for me. My original point is the presence of a nonmember role should not prevent the user from subscribing. If there is an issue with subscribing it is probably because of the outstanding subscription request waiting moderator approval. I understand that you would like the nonmember role to disappear, but that isn't going to happen in the distribution, and I can't undertake the extensive effort required to figure out how you can do it for your site. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users]Re: Installation issues

by Hellings Simon (EAST KENT HOSPITALS UNIVERSITY NHS FOUNDATION TRUST)

Hi Simon I have tried to re-install MM3 this morning but am now facing a different error message: Output from DJANGO log as follows: ERROR Internal Server Error: /mailman3/lists/ Traceback (most recent call last): File "/opt/mailman/mailman-bundler/eggs/Django-1.8.12-py2.7.egg/django/core/ha ndlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/vi ews/list.py", line 511, in list_index lists = sorted(List.objects.all(only_public=only_public), File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/mo dels.py", line 144, in all objects = getattr(get_client(), self.resource_name_plural) File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 158, in lists response, content = self._connection.call('lists') File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 105, in call response, content = Http().request(url, method, data, headers) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1609, in request (response, content) = self._request(conn, authority, uri, request_uri, metho d, body, headers, redirections, cachekey) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1351, in _request (response, content) = self._conn_request(conn, request_uri, method, body, he aders) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1307, in _conn_request response = conn.getresponse() File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse response.begin() File "/usr/lib/python2.7/httplib.py", line 415, in begin version, status, reason = self._read_status() File "/usr/lib/python2.7/httplib.py", line 379, in _read_status raise BadStatusLine(line) BadStatusLine: '' ERROR Internal Server Error: /mailman3/lists/ Traceback (most recent call last): File "/opt/mailman/mailman-bundler/eggs/Django-1.8.12-py2.7.egg/django/core/ha ndlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/vi ews/list.py", line 511, in list_index lists = sorted(List.objects.all(only_public=only_public), File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/mo dels.py", line 144, in all objects = getattr(get_client(), self.resource_name_plural) File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 158, in lists response, content = self._connection.call('lists') File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 105, in call response, content = Http().request(url, method, data, headers) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1609, in request (response, content) = self._request(conn, authority, uri, request_uri, metho d, body, headers, redirections, cachekey) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1351, in _request (response, content) = self._conn_request(conn, request_uri, method, body, he aders) File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1307, in _conn_request response = conn.getresponse() File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse response.begin() File "/usr/lib/python2.7/httplib.py", line 415, in begin version, status, reason = self._read_status() File "/usr/lib/python2.7/httplib.py", line 379, in _read_status raise BadStatusLine(line) BadStatusLine: '' [25/Apr/2016 06:21:10] "GET /mailman3/lists/ HTTP/1.1" 500 121854 Any ideas? Kind regards Simon ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ********************************************************************************************************************

9 years

[MM3-users]Re: Installation issues

by Simon Hanna

On 04/25/2016 03:50 PM, Hellings Simon (EAST KENT HOSPITALS UNIVERSITY NHS FOUNDATION TRUST) wrote: > Hi Simon > > I have tried to re-install MM3 this morning but am now facing a different error message: > > Output from DJANGO log as follows: > > ERROR Internal Server Error: /mailman3/lists/ > Traceback (most recent call last): > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.12-py2.7.egg/django/core/ha ndlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/vi ews/list.py", line 511, in list_index > lists = sorted(List.objects.all(only_public=only_public), > File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/mo dels.py", line 144, in all > objects = getattr(get_client(), self.resource_name_plural) > File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 158, in lists > response, content = self._connection.call('lists') > File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 105, in call > response, content = Http().request(url, method, data, headers) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1609, in request > (response, content) = self._request(conn, authority, uri, request_uri, metho d, body, headers, redirections, cachekey) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1351, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, he aders) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1307, in _conn_request > response = conn.getresponse() > File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse > response.begin() > File "/usr/lib/python2.7/httplib.py", line 415, in begin > version, status, reason = self._read_status() > File "/usr/lib/python2.7/httplib.py", line 379, in _read_status > raise BadStatusLine(line) > BadStatusLine: '' > ERROR Internal Server Error: /mailman3/lists/ > Traceback (most recent call last): > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.12-py2.7.egg/django/core/ha ndlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/vi ews/list.py", line 511, in list_index > lists = sorted(List.objects.all(only_public=only_public), > File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/mo dels.py", line 144, in all > objects = getattr(get_client(), self.resource_name_plural) > File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 158, in lists > response, content = self._connection.call('lists') > File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 105, in call > response, content = Http().request(url, method, data, headers) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1609, in request > (response, content) = self._request(conn, authority, uri, request_uri, metho d, body, headers, redirections, cachekey) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1351, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, he aders) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1307, in _conn_request > response = conn.getresponse() > File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse > response.begin() > File "/usr/lib/python2.7/httplib.py", line 415, in begin > version, status, reason = self._read_status() > File "/usr/lib/python2.7/httplib.py", line 379, in _read_status > raise BadStatusLine(line) > BadStatusLine: '' > [25/Apr/2016 06:21:10] "GET /mailman3/lists/ HTTP/1.1" 500 121854 I'm sorry I respond so late. Somehow lost this message in my inbox. I'm not sure what that error means... If you're still suffering from this issue, could you post the exact versions of all the components you are using in your virtualenvironments? And also the exact python versions you are using. Did you modify any files during the mailman-bundler installation?

8 years, 11 months

[MM3-users] Re: Invalid confirm text

by w.schoener＠alp.dillingen.de

One thing I forgot to mention: a week ago, the confirmation-mails still worked. And now: All attempts to confirm the subscribe message failed. I used the list-request(a)list.domain and sent text-only message with the "confirm token" in the subject and/or in the body. So today I tried and used the Mailman shell to change the pending state to "confirmed", as you described here: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… After I submitted the command util.confirm('hex_token') and restarted mailman with mailman stop mailman start the pending user wasnt confirmed but cleared, as if he never sent a subscribe-message. The only way to subscribe seems to be by logging in and using there the subscribe-form. Do you have any idea, whats going wrong here? I dont know what to do any more. Thank you :-) Wolfgang

4 years, 8 months

[MM3-users] Sorry to repeat a question, but how do I permanently delete messages, again?

by William Oliver

I askled this question some months ago, but for the life of me cannot find the response (though there is one). I want to purge some specific emails from the list archives. A user posted what he thought was a personal message to the list, and is embarrased by it, so I told him I couldn't delete emails that were already downloaded onto client machines, but I can delete it so that new users won't be able to see it. But... I can't figure out how to do it. I asked this once before, some months ago, and as I remember there is a command line way of doing it, but not a GUI way. But i can't remember what it was. Thanks! billo

2 years, 9 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/20/22 07:54, Rainer Herbst wrote: > Dear all, > > my first post was to optimistic - the user tested some other > combinations and when he tries to send a signed HTML mail, the server > again refuses to accept it with "Diagnostic-Code: smtp; 501 Message has > defects". > > The user suggested that the problem is caused by a line containing only > "-- " somewhere in the text, but I can not confirm this. > > Please find enclosed the refused mail (anonymized). That message has no defects. ``` >>> import email >>> from mailman.email.message import Message >>> txt = b""" (the testmail-abgelehnt.txt contents) """ >>> msg = email.message_from_bytes(txt, Message) >>> msg.defects [] >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

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

by Mark Sapiro

On 2/12/21 11:26 AM, Brian Carpenter wrote: > I migrated a Mailman 2 list using import21 and the list's config.pck > into a Mailman 3 list. The list owner reported back that about 98% of > the list members had their moderation setting changed to Reject (with > notification). He said the previous moderation was the list's default > which was hold for moderation. Is such a thing possible with an import > job? Is this perhaps a bug that has been reported previously? > It seems you imported to an existing list with import21. This is probably not a good idea. Those members who were moderated members of the MM 2.1 list will have their moderation action set to Hold, Reject or Discard based on the 2.1 list setting. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: domain owner role

by Abhilash Raj

> On Sep 1, 2021, at 7:52 AM, Rainer Herbst <rainer.herbst(a)aip.de> wrote: > > Dear all, > > recently, I have added one account to a domain as domain owner. I did expect the new owner to see all lists in that domain in Postorius, but he sees no list at all. > > Is this the way it should be? How can I add administrators able to perform administrative tasks on all lists in Postorius? > Domain owner role isn’t currently very useful in Postorius, they can so far only edit the domain templates. If you want to grant the user ability to manage lists in Postorius, you’d have to grant the user superuser privileges which will allow them to manage all the domains. I was thinking there is an open issue for it, but apparently there isn’t one so I opened a new one. https://gitlab.com/mailman/postorius/-/issues/533 -- thanks, Abhilash Raj (maxking)

3 years, 7 months

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Danil Smirnov

Hey Brian! On Thu, Mar 25, 2021 at 10:36 PM Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > On 3/25/21 2:51 PM, Jim Popovitch via Mailman-users wrote: > > 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....;) > > Would be nice if Danil could let the list know and in that same > communication, he can explain why he is promoting Mailman 4 when there > is no Mailman 4. We can then move to the discussion of him charitably > giving mailman3.com to the Mailman 3 developers. How about it Danil? > This is a great question. Thank you. No, there are no plans to pass domains I own to you, or any other party (unless you offer a very good price, of course). They are in use of commercial services, which are based on the Mailman 3 open-source software and listed in the directory of Mailman hosting services <https://wiki.list.org/COM/Mailman%20hosting%20services> (just as your company). *Mailman3.com* is Mailman 3 commercial hosting service (that, I think, is perfectly reflected in the domain name). It uses a shared hosting approach, which allows you to get a full-fledged Mailman 3 server for as little as *8.25 EUR* (monthly fee). Mailman3.com has also declared an open-source support initiative to provide a *free Mailman 3 hosting to OSS projects*. (To apply, send the OSS project URL and approximate monthly volume to hostmaster(a)mailman3.com.) *Mailman4.com* is a marketing initiative to emphasize the unique possibility to install *Mailman 3 in AWS* infrastructure with a few clicks to leverage all the features of AWS Marketplace, AWS customer protection, and pay-as-you-go billing scheme. (Being a bit provocative, the initiative was named while taking into consideration that the fourth version of Mailman does not exist yet and is hardly expected soon. After the version released, the appropriate business decision will be undertaken immediately.) With Mailman4.com you get your Mailman 3 server in the dedicated EC2 instance for the same price which you would pay if you deploy it to your own EC2. *Reliable mail relay*, which is carefully groomed to fit into email delivery best practices, is *included for free*. Mailman4.com is especially useful for *educational and evaluation purposes* as it allows to deploy a fully functional Mailman 3 server just in one minute and be charged *from 2 to 4 cents hourly* (depend on Hyperkitty presence). And then cancel it instantly when not needed anymore. For both Mailman3.com and Mailman4.com services it's possible to develop a *custom integration of Mailman Core API with third-party services* via publicly (but securely) exposed endpoints - the option which some of our customers are enjoying already. For example, one might create mailing lists and manage their subscribers list programmatically in order to sync it with some internal user directory. (Performance issues, which occured when a number of users is large, have been discovered and fixed already.) --- The existence of the services, described above, is already bringing benefits to Mailman 3 development community in several areas, i.e. additional paid promotion of the software (e.g to attract more GSoC students), extensive testing in the real world (which is particularly useful for dockerized setup), and contributions to the code. I hope this helps and best luck with *your* Mailman business. With my best regards, Danil Smirnov Mailman3.com proud owner > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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, 1 month

[MM3-users] Subscription issue with ghost confirmations

by Brian Carpenter

I have a list owner who had his subscription policy set to confirm. Apparently that was too hard for his list members to handle so he changed it to moderate only. If someone sent a subscription request that needed to be confirm, did not respond to it, and then tried subscribing again after the member policy changed to moderate, their 2nd subscription attempt still shows up in the confirmation queue. Is that normal behavior. My understanding is it is. Please let me know if I am wrong here. The real mystery here is when someone tried subscribing again (listname-subscribe@listdomain) hours after the subscription policy was changed to moderate and they still showed up in the confirm queue. How is that possible? I tested the list with two of my addresses and both showed up in the moderation queue as expected. As far as I can tell from the mailman logs, this was the person's first attempt at subscribing. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: Hyperkitty performance problem

by Odhiambo Washington

On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: > 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 > The official documentation specifies two DBs - one for Mailman Core and the other for Mailmanweb. As far as I know, there are no conflicts in the tables so you could use the same DB for both. -- 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]

5 months

[MM3-users] Equivalent of listadmin Perl script for Mailman 3?

by Stephen J. Turnbull

Philip Colmer writes: > We're preparing to migrate about 4 Mailman 2 servers to Mailman 3. In doing > so, one of our list administrators has informed us that he uses "listadmin" > Does anyone know if there is an equivalent tool that works with Mailman 3? I don't know of one, but perhaps someone does. It probably wouldn't be hard to write a bare-bones workalike if the admin has shell access to the mailman host. UIn theory, shell access could be restricted to running the tool by using a 'command' option in the sshd authorized_keys file for the user's key. But I'm not competent to judge how secure that could be in principle, and of course if the tool is buggy in certain ways, all bets are off.) I can't estimate how hard it would be to write one without shell access, as I'm not sure how amenable the Postorius web UI is to scripting. Steve

3 years, 5 months

[MM3-users] Re: How to delete non-users

by Allan Hansen

Hi Mark, Thank you for looking into it. We are very strict about memberships, which we are because of spam, bots and malicious contributors and because we don't want anyone to think that our lists are used for spam: When a user applies, the server sends a message to the moderator. The moderator communicates with the potential member and accepts or does not accept the application. At this point, if the user has not been accepted, but tried to send a message to the list, a non-member membership is created. When he/she logs in to list his/her account, the list to which he/she holds non-memberships will be listed and the user will think that he/she has been properly subscribed (why else are the lists listed). Noone notices the column that shows the role as 'nonmember.' So he/she thinks that the subscription request has been accepted, but nothing is working. That's why the 'non-member' record is an issue. I also don't see why non-members are automatically added, filling up the database with junk (at least from our point of view, with all respect). But our lists don't accept messages from non-members. Such messages are quietly discarded, as most are spam, as mentioned above. So now the user is neither getting emails from the lists nor is unable to send messages to the list. The next step for the user is to complain to me. ☹ I have looked for a template that could be used to warn someone when he/she is added as a non-member, but did not find one. It's also not clear that I'd want one, as most of these non-subscriptions are by spammers and I prefer not to reply to spammers. __ I tried your suggestion below, Mark. Here's my transcript: ********** 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. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> ********** I did this twice, once with commit() and once typing ctrl/d (ctrl/D) just gave me a beep. Calling commit() did not return to the ... as in your example, but showed the >>> prompt, so I tried ctrl/D (beep) and then ctrl/d (exit). I then went to the Postorius page for one of the lists and found that all the non-members were still present. Yours, Allan On 9/16/22, 15:01 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/16/22 11:19, Allan Hansen wrote: > Hi all, > > This is a bit of an emergency: > > I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. > For individuals I have been able to delete their non-membership and they then could subscribe properly. I don't understand. the fact that an address is a non-member of a list should not impact subscribing that address as a member. > I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. What is actually happening when the non-member attempts to subscribe as a member? What do they do and what it the result? > I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). > > Can anyone help me find out how to > a. delete all non-members of all my lists If you have access to `mailman shell` you could do: ``` $ 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. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> commit() ``` > b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) nonmembers are an integral part of Mailman 3's architecture. The basic idea is a nonmember has a moderation action and setting a nonmembers moderation replaces MM 2.1's adding that address to one of *_these_nonmembers (The legacy *_these_nonmembers attributes still exist, but only to support regexps). It would require extensive modification to not create nonmembers. However, I still don't understand why the presence of a nonmember record is an issue. -- 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/

2 years, 7 months

[MM3-users] Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail

by Torge Riedel

Hi, we migrated successfully to mailman3 so far. I have some questions regarding handling of SPAM mails in mailman, here is the first, second comes in a separate post: The list moderator currently receives a copy of the original mail in the info mail he gets for moderation. This is bad in case it was a SPAM mail, cause we have seen that such an info mail is detected also as SPAM. That might rise problems cause other mail servers might block the info mail as SPAM and if this happens too often blocking the whole server. I fear. At least I see that my rspamd starts learning the info mail as SPAM. I don't want that to happen. I searched mailman web interface for a setting to disable adding a copy to the info mail. But have not found it. Is it missing or where do I have to look? Best regards Torge

5 years, 3 months

[MM3-users] Re: Add rule to auto-discard "AutoReply" messages from list members

by Thomas Krichel

Thomas Ward via Mailman-users writes > Unfortunately, this is bad behavior and appears to not be caught by default. I deal with that at the exim level. At this time I only have one list root@tagol/etc/mail# cat exim.filter # Exim filter # Auto-Submitted: auto-replied if $h_to: contains "bibnez(a)folks.email" and $h_Auto-Submitted: contains "auto-replied" then headers add "Old-Subject: $h_subject:" headers remove "Subject" headers add "Subject: RAUS ($h_old-subject:)" headers remove "Old-Subject" deliver "juergen.plieninger(a)uni-tuebingen.de" endif Thus if the header Auto_Submitted contains auto-replied, I forward it to Jürgen, my list boss, just in case it is actually ham, but I change the subject so that he can easily spot that it was filtered. This is not 100% tight, as there are bad auto-reply agents creating mails that don't have an auto-submitted header. Hope this helps somebody out there. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21349th day.

1 year, 5 months

[MM3-users] spam filtering (was: Re: list of subscribers)

by Peter Münster

On Sun, Feb 04 2018, Mark Sapiro wrote: > This would seem to be specific to your use case. I think in general what > we would want to display is the display_name from the list's member record. Ok, I see. Now I know, how to generate such list (email + full name) as site administrator, so it's ok for me. > We tried to send your copy of your post to you, but your MTA called it spam. > > Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: > to=<pmlists(a)free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, > delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host > mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of > DATA command)) IMO, spam filtering should be done at user level, every user should be free to filter what he likes, not the MTA. Perhaps I should do it like you, and manage my own email relay host? I've tried to subscribe with an address at orange.fr but it does not seem to work, probably the same problem as with free.fr... -- Peter

7 years, 2 months

[MM3-users] Re: Unsubscribe Notifications Clarification

by Abhilash Raj

On Wed, Sep 2, 2020, at 7:32 AM, Brian Carpenter wrote: > I am trying to understand how Mailman 3 handles unsubscribe > notifications. From my testing I see the following behavior: > > 1. If list member sends email to listname-leave@listname, an > unsubscribe notification is sent to both list owner and list member if > list settings have them enabled. > > 2. If list list member is a registered user of Postorius and he uses > Postorius to unsubscribe, then no notification is sent out to either > list owner or list member, even if list settings has unsubscribe > notifications enabled. > > Is this correct? This is a bug in Core, for which I have opened https://gitlab.com/mailman/mailman/-/issues/759 It seems like the Unsubscriptions via the API do not follow the right codepath and just unsubscribe the user. It also does not seem to take the unsubscription policy into account. > Brian > _______________________________________________ > 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, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] mm3 floods syslog

by Wolfgang Bock

Dear friends, I got another problem: mailman floods my syslog. I deleted a domain/webdomain (further mentioned as deleted.org) in postorius, django web. No entries are now in /var/lib/mailman3/data/postfix_domains or postfix_lmtp or /var/lib/mailman3/lists. Here an extract of my syslog (anonymized): Oct 31 10:49:02 myserver mailman3[1284]: Oct 31 10:49:02 2021 (1284) Certificate did not match expected hostname: localhost. Certificate: {'subject': ((('commonName', 'deleteted.org'),),), 'issuer': ((('countryName', 'US'),), (('or ganizationName', "Let's Encrypt"),), (('commonName', 'R3'),)), 'version': 3, 'serialNumber': '0326A733CA7B16D13C830EE707EA614E25F9', 'notBefore': 'Oct 30 20:21:08 2021 GMT', 'notAfter': 'Jan 28 20:21:07 2022 GMT', 'subjectAltName': (('DN S', 'deleteted.org'), ('DNS', 'lists.deleteted.org'), ('DNS', 'mail.deleteted.org'), ('DNS', 'ns.deleteted.org'), ('DNS', 'www.deleteted.org')), 'OCSP': ('http://r3.o.lencr.org',), 'caIssuers': ('http:/ /r3.i.lencr.org/',)} This appears nonstop. I now stopped the cronjob fort he moment: "[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely" and others Does mailman or django store any information about domains in another place/file. If yes, how this can be deleted?? Thanks for your reply in advance. Regards Wolfgang

3 years, 5 months

[MM3-users] Re: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Ken Alker

I probably should have said DMARC and not DKIM (I was spam combatant policies all together as if they were all the same/similar, but I should not have done that; too many "new" acronyms to keep straight). Thank you for providing the screen-shot showing List Settings/Settings/DMARC Mitigations with "DMARC mitigation action" set to "Replace From: with list address" and "DMARC Mitigate unconditionally" set to "Yes". I tried this and it cleared up the problem (at least with one sender tested so far). I also noticed the my colleague was already using these settings in a list he manages on the same server. Unfortunately, now when I respond to list emails (with the re-written From address) my (very old) email client (I still use Mulberry!) defaults to responding to the sender instead of the list, as it had before. I'm hoping this is a nuance of my client and isn't something the other members are going to have to grapple with.

7 months, 3 weeks

[MM3-users] Question about message bounce stats

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > Does Mailman3 keep such stats, and if so is there any way to get > access to them, even if only API? I would think it useful to do so > (and yes, for individual outgoing messages at least for a period). In released versions, it currently does not, as far as I know. This kind of thing should be available from your MTA, of course, and I think there was a visceral opposition to keeping track of people's behavior that way from the early days. So those are our excuses. However, it's something that comes up occasionally on the list as well as as a GSoC proposal, and I think there's some code on a branch for this that Abhilash has been threatening to release. And of course HyperKitty now publishes stats on posting behavior. So there's really no reason to oppose it, now it's just a matter of time to implement. Abhilash's participation has been kind of spotty recently (and apologetic about it, he's not going anywhere), but hopefully he'll pick up the thread shortly and at least confirm or deny what I wrote here. Steve

3 years, 7 months

[MM3-users] Re: How can I remove anything added by Mailman 3 to the forwarded email

by Mark Sapiro

On 5/9/22 06:00, gscaglia(a)ksdata.it wrote: > I need to use Mailman 3 exclusively for forwarding emails to my customers divided by type. > > The emails must arrive exactly as they are, without any additions, and the lists are managed only by me: the customer ignores that he is subscribed to a list and receives the message as if it were one to one. > > How can I remove anything added by Mailman 3 to the forwarded message, therefore also the links for managing my membership (unsubscribe and modify)? In Postorius do the following: In Templates set list:member:regular:footer empty In Settings: in List Identity set Subject prefix empty in Alter Messages set Personalize None Filter content No Anonymous list No Include RFC2369 headers No Include the list post header No First strip reply to No Reply goes to list No Munging in DMARC Mitigations set DMARC mitigation action No DMARC mitigations in Archiving set Archive policy Do not archive this list -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Change language to welcome message in mailman3

by Massimo Zappalà

> What is the ownership of the other directories in > /usr/lib/python3/dist-packages/mailman/? They are probably also owned by > root and that should be OK as long as they are world readable. I have checked the permissions and properties of the it directory. They are the same as the en directory. > Please tell me what messages. Do you mean if I subscribe to the list, I > get a welcome message in English, but the list owner gets the > notification of a new member in Italian? Not exactly. If you subscribe a user to a list, the Welcome email arrives in English. On the other hand, if an admin is registered for a list, he receives the email in Italian. But I solved it by changing the value "en" with "it" in the mailman3 database, the mailinglist table, the preferred_language column. Now those who subscribe to the list receive a Welcome email in Italian. > I think you need to set the system default_language. In mailman.cfg, set > [mailman] > default_language: it I had changed this value from the beginning. Thank you very much for your valuable advice and patience Max

4 years, 8 months

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Sapiro

On 2/15/21 9:07 PM, Mark Dadgar wrote: > So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. > > The resulted in a broken web interface. > > Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. > > Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. > > Anyone got a solution to this? From the tracebacks it looks like Django is broken. I would suggest starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ aside and create a new venv virtualenv /opt/mailman/mm/venv/ and then activate it and pip install everything. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Python is updated

by Odhiambo Washington

On Sat, Apr 29, 2023 at 8:25 AM Lars Bjørndal <lars(a)lamasti.net> wrote: > Thank you very much. You wrote: > > [...] > > > > I tried `django-admin migrate --pythonpath /etc/mailman3`, and got the > same result. > > > > > > Then you may need > > > > `django-admin migrate --pythonpath /etc/mailman3 --settings settings` > > Yes, that worked! > > > What I have is this shell file that I use to invoke django-admin > > ``` > > #!/bin/bash > > . /opt/mailman/mm/venv/bin/activate > > cd /opt/mailman/mm > > export PYTHONPATH=/opt/mailman/mm > > So you have settings.py in /opt/mailman/mm rather than in /etc/mailman3? > That's right - based on an earlier installation method before the official virtualenv <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> one was put together, and that's why he has that shell file. For a virtualenv <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> setup, your settings should live in /etc/mailman3 as stated. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 11 months

[MM3-users] Re: Found error in docker-container

by Abhilash Raj

Hi Alex, On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote: > Hi, > > one of our developers wanted to point out an error he found in mailman > 3.1, docker container maxking/mailman-core-0.1 > > The entries in /opt/mailman/core/var/data/postfix_lmtp are not set > correctly, example: > > /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP > Address of mailman-core container]:8024 > > this actually should look like this: > > /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 Can you send a copy of your Mailman configuration that you added at `/opt/mailman/core/mailman-extra.cfg`? I think this is mostly because the configuration parser doesn't understand the in-line comments. So, if you are using the configuration exactly as it is mentioned in the documentation, it could be the cause of this problem. Solution to that would be to just remove all the in-line comments. [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 # IP Address of mailman-core container lmtp_port: 8024 smtp_host: 172.19.199.1 # IP Address of host where postfix is. smtp_port: 25 configuration: /etc/postfix-mailman.cfg Like the two comments seen in the configuration above. I will update the documentation too so that others don't get caught in something like this. Thanks! -- thanks, Abhilash Raj

7 years, 9 months

[MM3-users] A few more MM3 questions

by Marc SCHAEFER

Hello, My migration from MM2 to MM3 seems near completion: I will do a few more tests and then tell the list admins to start testing. I have a few questions: 1) persistence: as I can regenerate the configuration files (mailman, mailman-web, hyperkitty), is all what's useful in the DB, or are some things in /var/lib/mailman3 worth saving? obviously messages to be moderated, hyperkitty failed messages, etc are stored there, but shall I assume that all mailing-lists configuration, all users configuration and all archives are in the DB? 2) I imported a list and all messages get a footer of: %(web_page_url)slistinfo/%(_internal_name)s which I guess changed between MM2 and MM3; however when I look at that list configuration in the web interface of MM3, I see no templates defined, nor any clue where this is configured: where may I change this? 3) is there a configuration somewhere that can allow someone to create a mailman web account ONLY if he is already referenced somewhere in a mailing-list, and not otherwise? (or to create accounts that need approvals from an admin before being usable?) also, can a non-yet-referenced e-mail From: still subscribe to a private list (confirm+moderate) via e-mail regardless of the above? Thank you for any pointers!

10 months, 4 weeks

[MM3-users] Re: mailman import21

by Brian Carpenter

On 10/11/20 11:06 AM, Mark Sapiro wrote: > On 10/11/20 7:41 AM, Brian Carpenter wrote: >> Does the import21 script also import custom templates? > No. > > >> Are these custom >> templates contained in the config.pck file? > No. They are in the same MM 2.1 directory as the config.pck, but in a > sub-directory for the language code, i.e. lists/LISTNAME/LC/ > > >> Are there any known issues >> with the importing of mm2 templates into a mm3 environment? > > The replacements are different. i.e., things like %(email)s and > %(listname)s become $user_email and $short_listname. > > Also, there are some MM 2.1 templates that have no MM 3 equivalent. > Also, things like message and digest headers and footers that are MM 2.1 > list attributes that are templates in MM 3, although import21 tries to > handle those. So are how these templates showing up on my Mailman 3 servers? They show up in /opt/mailman/mm/var/templates/lists/listname/en/. I have a client whose old footer template from Mailman 2 still showing up in list messages. He then created a custom footer template via Affinity (same thing happen in Postorius) and both custom footers were being included in list messages. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] Re: How to import mailman2 into mailman3 in Docker, getting error with archives.

by Jens Günther

For importing the archives, it's the mailman-web container. For me it was like: python manage.py hyperkitty_import -l listxy(a)somedomain.org /opt/mailman-web-data/listxy.mbox Before I connected into container as the user mailman! Hope this helps. Am 15.09.21 um 19:36 schrieb bob B: > I know you can't run mailman commands in the docker images and I have to copy the data to an area where he docker images can access it, but in looking that the commands I got the list settings to import > > docker exec -it mailman-core mailman import21 [REDACTED](a)REDACTED].REDACTED].org /opt/mailman/migration/config.pck *** this worked > > > But having issues importing the archives? do i run this on mailman-core OR mailman-web? I tried both but it does not like python? > > docker exec -it mailman-core python manage.py hyperkitty_import -l [REDACTED](a)REDACTED].REDACTED].org /opt/mailman/migration/[REDACTED].mbox > OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "python": executable file not found in $PATH: unknown > _______________________________________________ > 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, 7 months

[MM3-users] changeaddress command and nonmembers

by Mike Wertheim

I recently upgraded a Mailman 2 installation (which included a number of email lists) to Mailman 3.3.3. There is one human user who in the past has used two different email addresses. Let's call them oldaddress(a)hotmail.com and newaddress(a)gmail.com. This person used to participate on an email list using oldaddress(a)hotmail.com (both posting and receiving). He then unsubscribed oldaddress(a)hotmail.com from the list and then subscribed to the email list as newaddress(a)gmail.com. All of this happened while using Mailman 2. Now that we're on Mailman 3 and the email list was migrated from MM2 to MM3, we see that newaddress(a)gmail.com is a Member of the list, and we see that oldaddress(a)hotmail.com is a NonMember of the list. That all makes sense. But now, this person has decided that they actually want to go back to using the old address. So I ran the command "mailman changeaddress newaddress(a)gmail.com oldaddress(a)hotmail.com". But that gave me this output: Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS Try 'mailman changeaddress -h' for help. Error: Address oldaddress(a)hotmail.com already exists; can't change. Can anyone explain how I can do what I'm trying to accomplish? (Also, why is this error displaying the usage message? That seems odd, since the number and type of arguments was correct.)

2 years, 2 months

[MM3-users] Re: Post-installation documentation?

by Mark Sapiro

On 11/24/21 7:50 PM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > Here are the steps to migrate a 2.1 list named `alist(a)example.com` and > > its archives. > > This is documented at https://docs.list.org/en/latest/ (prominent link > in sidebar). This appears to be completely different from > https://docs.mailman3.org/ (and https://mailman.readthedocs.io/ which > I guess is just a redirect). But it looks like the sources are in the > some gitlab repo?! Both docs.list.org and docs.mailman3.org are CNAMEs the resolve ultimately to readthedocs.io. I.e. they both get to the same readthedocs pages the source for which is the https://gitlab.com/mailman/mailman-suite-doc project. https://mailman.readthedocs.io/ also goes readthedocs.io, but to the documentation for Mailman core rather than that for Mailman Suite. > > Did you specify the list's fqdn as in > > https://www.example.com/archives/list/list@example.com/ > > That's not an FQDN, though. "example.com" might be one, but that > whole thing is the URL to the archive. I meant did he go to a url like https://www.example.com/archives/list/list@example.com/ as opposed to https://www.example.com/archives/list/list/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: mailman import21

by Mark Sapiro

On 10/11/20 8:26 AM, Brian Carpenter wrote: > > On 10/11/20 11:06 AM, Mark Sapiro wrote: >> Also, things like message and digest headers and footers that are MM 2.1 >> list attributes that are templates in MM 3, although import21 tries to >> handle those. > > So are how these templates showing up on my Mailman 3 servers? They show > up in /opt/mailman/mm/var/templates/lists/listname/en/. I have a client > whose old footer template from Mailman 2 still showing up in list > messages. He then created a custom footer template via Affinity (same > thing happen in Postorius) and both custom footers were being included > in list messages. As I said, (msg|digest)_(header|footer) are MM 2.1 list attributes, not templates. Those, and I think only those, are converted to var/templates/lists/listname/lc/ templates by import21. If I understand you correctly, after creating a custom template in Postorius or Affinity, both that and the old template were included in delivered posts. I don't understand that. For Postorius at least, when a custom template is created, it sets the URI for the template in core to point to Postorius to get the template. the old template in var/templates/lists/listname/lc/ should not be referenced. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Sorry to repeat a question, but how do I permanently delete messages, again?

by Tim Cutts

It can be done in the GUI. See this historical thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> T > On 8 Jul 2022, at 13:48, William Oliver <billo(a)billoblog.com> wrote: > > > I askled this question some months ago, but for the life of me cannot > find the response (though there is one). I want to purge some > specific emails from the list archives. A user posted what he thought > was a personal message to the list, and is embarrased by it, so I told > him I couldn't delete emails that were already downloaded onto client > machines, but I can delete it so that new users won't be able to see > it. > > But... I can't figure out how to do it. > > I asked this once before, some months ago, and as I remember there is a > command line way of doing it, but not a GUI way. But i can't remember > what it was. > > Thanks! > > billo > _______________________________________________ > 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/

2 years, 9 months

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Dadgar

On Feb 15, 2021, at 10:14 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. >> >> The resulted in a broken web interface. >> >> Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. >> >> Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. >> >> Anyone got a solution to this? > > > From the tracebacks it looks like Django is broken. I would suggest > starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ > aside and create a new venv > > virtualenv /opt/mailman/mm/venv/ > > and then activate it and pip install everything. Ok, that worked. THANK YOU. My lists are back up. The CPUs getting pounded by some failing process is back, though. I’ll post about that separately. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 2 months

[MM3-users] Re: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210530 09:19]: > Mark Sapiro writes: > > On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > > > Membership adapter is a Mailman 2 feature that allowed use of an > > > external membership database (such as a corporate LDAP system). I > > > thought it was ported to Mailman 3 but maybe not. > > > Actually, it's not quite that simple. Mailman 2.1 defines a > > MemberAdaptor class, [...]. > > The Mailman 3 analog of this is the IMember interface defined in > > mailman/interfaces/member.py and implemented in mailman/model/member.py > > OK, but for Andi it is "simple" in the sense that he doesn't have an > existing MemberAdapter, so the plan is "Implement the IMember interface". Not sure if this is the right approach, or if it wouldn't be more appropriate to "just" replace the dependency on allauth in postorius, and do all the magic in the frontend only (because that's where people actually subscribe). Whoever subscribes by mail needs some admin action, or some cron job, or is unsupported - for my case the main interface is the web interface, not the email commands. That of course would imply that e.g. cleaning up mailing lists happens by a cron job with rest, but why not? Andi

3 years, 10 months

[MM3-users] Re: multiple sites on a mailman3 server question

by David Newman

On 12/28/21 6:15 PM, William Oliver wrote: > So, I have successfully installed mailman3 and it's working great. > However, the way it works now, if someone goes to the domain website, > he or she will get the mailman page. I'd prefer that it work something > like: > My > www.example.com goes to a home page > lists.example.com goes to the mailman3 page > mail.example.com goes to a roundcube page > > > I'm using nginx I'd asked about this a few weeks ago for a MM3 host running Ngnix with a few virtual domains, one of which runs Roundcubemail as its default. Mark Sapiro suggested the following, and it seems to be working OK. You'll need these lines in the Nginx config file for each virtual host you define. # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff dn

3 years, 3 months

[MM3-users] [Mailman-Users] Mailman 3 Ready?

by Stephen J. Turnbull

Reply-To set to mailman-users(a)mailman3.org. Allan Hansen writes: > I need to upgrade from Mailman 2.1 - my hardware needs upgrading > (badly) and the address mangling is having my subscribers rip their > hair out. That's not going to go away. We have ARC support in Mailman 3, but (a) like most envelope manipulation, that should be done in boundary MTAs, not in Mailman, and (b) ARC implementation is not universal. *Very likely* some of your subscribers are going to lose mail if you depend on ARC, rather than munge from. > I need to get this done before they start on my already thinning > hair! I sympathize. I tell the little kids I meet that my hair grows out of the bottom of my face, not the top (it's very alliterative in Japanese[1], the kids frequently don't get it but the accompanying adults usually laugh). > I’m ready and eager to move on to MM3 on a Linux box. The obvious "turn-key" installation is to use the Docker containers, which Abhilash keeps fairly up-to-date. But see comment below about universal working solutions. Which distro do you have? Are you using the distro's packages of Mailman 3 (not yet a good idea, unfortunately), or installing from source? > I have looked into it a few times now and I keep running into the > same blocks. I don't see much moving either. I was hoping someone > (Mailman developing community) would come up with a better working > solution. It's email. There are no universal working solutions. > [Some third party wrote:] My concern is that the Mailman3 is not > ready. There are too many dead ends and undocumented stuff. Who is this guy and has he consulted us? I'd like to do an archive search if he's done so to see what the issues are. > For Mailman2 I have a working integration with iRedMail, that does > not seem to work with 3. What's iRedMail? How does it fit into the community your lists serve? > So, is MM3 ready for the big screen? Works for us, for values of us including python.org. > If so, is there some way/how/where/when that my friend can get help > helping me with the installation other than the published > installation docs, which did not work for us? mailman-users(a)mailman3.org is the Mailman 3 version of this list. If your friend is the type to get his hands dirty with code, and has the time for development activity, mailman-developers(a)python.org would also be useful. You might be better off getting bids from consultants. There's a page listing them on wiki.list.org. > I have looked for both free and commercial alternatives to MM, There are sites that support MM commercially. I think the prices are reasonable, of course YMMV on that. Again, there's a page for those services on wiki.list.org. Footnotes: [1] "hage dakara hige o" -- the vowels are pronounced as Spanish or Italian, the consonants as in English.

5 years, 5 months

[MM3-users] Re: Member Issue Discovered

by Abhilash Raj

I am a bit late to this thread, but I am going to try to respond to some of the points raised in the thread. On 10/19/20 7:42 PM, Brian Carpenter wrote: > On 10/19/20 10:23 PM, Mark Sapiro wrote: >> And the import21 created the user and address records for this user. > Does the same thing for a new subscriber as well. So there is no pathway > to change a real name that is associated with an email address. None. > Zilch. Yes, this is a limitation of the REST API, the display_name attribute can't be updated. Hence, Postorius can't provide a way for anyone to update the name. I have opened an issue for this[1] and I think it should be allowed. [1]: https://gitlab.com/mailman/mailman/-/issues/786 > I am admin for a list. Users got subscribed with bulk import during > transition from MM2 to MM3. > So in a sense I am responsible for adding these to a db. BUT there is > no way for me to remove them. Only mailman admin with access to the db > can do it manually. The fact that a user's memberships & User as an entity that owns email address is a design choice that Mailman developers made after some experience of using and administering Mailing lists running on Mailman 2. It was annoying to have to manage several different passwords and accounts to manage membership on same mailing list server. The policy decision that Mailman would allow a user/address to exist even if there are no subscriptions on it isn't un-resonable in certain environments and maybe it is in some. I don't think anyone here denies that either of those behavior could be an expectation from someone using Mailman. But Mailman is an open source project with decent amount of extensibility via HTTP API & Python plugin system. If the default policy doesn't match the expectations of some users, I don't think it is difficult to cleanup users/address with 0 subscriptions in a nightly cron script. It is trivial with some basic scripting and we are happy to help out with such a mechanism. I wouldn't be opposed to directly adding a command in Core that lets you clean up all sorts of stuff. On Wed, Oct 21, 2020, at 10:20 AM, Apollinaris Schöll wrote: > There might be a handful of these. > > But the bigger problem is a user can’t be removed entirely. > > User can delete account and unsubscribe from all lists. But the email > and user name is still kept in the db. Just tested with Affinity > List admin can’t do it either. Front-ends like Affinity should be able to implement such a policy by checking subscriptions of an address on every un-subscription call and delete the user & address if it comes out to be 0. The API is documented here[2], but if there are gaps in there like I mentioned above in my email, please open issues so we know about them. [2]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > I think the correct action is to remove all records if a email is > unsubscribed from all lists and that user has not registered for an > account. > If a user has registered for an account all information including > display name must be removed from that particular list subscription. > It should not matter if a user unsubscribes or a list admin > unsubscribes. There shouldn’t be any data kept. Also, like mentioned above, as a list admin, you can request the Site Admin to get the address fully scrubbed or if this is an expectation from all list admins, the Site Admin has the ability to automate such a task. The fact the Mailman doesn't do it by default is because the definition of "correct" action is different. User should have the ability to delete themselves from the system and if it doesn't wipe everything yet from database, it should be considered a bug in Postorius and be fixed. Postorius track users separately than Core, so the it should make sure to delete in both places and there are appropriate APIs in core to delete Users and Addresses. Now, the ability in Postorius to edit the display_name. The side effect of the model where User is a Site level thing, makes it impossible to customize user's display_name on a per-list basis, for both list admin and the user themselves. That is a trade-off and it is possible that there were use-cases where that was desirable in Mailman 2, but with the superior subscription management functionality in Postorius, I feel the decision is justified. I respect that some of y'all think that it probably isn't if it doesn't suit you particular use cases. From the thread, I gather than folks mostly agree that a list admin shouldn't be allowed to edit a user's display name. Site Admins however should be able to edit that, which brings me to next point. Like Mark brought up, there is definitely a big missing feature of User management in Postorius. This future management page would be for Site Admins (Superusers) to manage Users and have the ability to change pretty much everything about users including their addresses, memberships and preferences and also be able to wipe off the users from all the databases if they want to. If there are more features than that which folks think should be a part of this, please feel free to add to it. As it is hopefully implied from the description, it is a big task and needs substantial chunk of time, part of which this hasn't been picked up yet. > > > > > > > > On Oct 21, 2020, at 1:43 AM, Jörg Schulz <info(a)joergschulz.de> wrote: > > > > So, the issue seems to be, like in the following scenario > > > > We imagine a list server for the domains fruiteaters and meateaters. > > We have two listadmins, anna (fruit) and carl (meat). They don't share anything. > > We have a user who subscribes to fruiteaters and meateaters using his address hunger(a)eatall.com > > > > He wants to show up in the fruiteaters list as fullname wormy wonder, but in the meateaters list as fritz the cat. > > While he can do so using two different email addresses, he cannot do so using > > > > wormy wonder <hunger(a)eatall.com> > > fritz the cat <hunger(a)eatall.com> > > > > as from: addresses because all requests will be matched to the one email address. > > > > Worse, if Carl would be able to change the name to from wormy wonder to fritz the cat, Anna would see that name change and like to change it back because the user she had known, user has been identified as wormy wonder. > > > > So, if these user properties are stored somewhere not related to the lists, we don't seem to have a chance of display name changes by list admins as long as the data model isn't changed. This doesn't seem to be easy. > > > > So, only some kind of super-Admin should currently be able to change these display names, and these changes would be visible for all lists, and one email address can only have one display name for all lists. > > > > Not optimal for some rare conditions - that's the way it seems to be??? > > _______________________________________________ > > 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/ > _______________________________________________ > 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, Abhilash Raj (maxking)

4 years, 6 months

[MM3-users] Re: Uncaught runner exception

by Mark Sapiro

On 4/8/20 1:17 PM, Wolfgang Bock via Mailman-users wrote: > > Checked the ownership .... > ls -la: > /var/lib/mailman3/cache > drwxrwx--- 3 root root 4096 Nov 9 22:27 61 > drwxrwx--- 3 root root 4096 Feb 3 17:37 6c > drwxrwx--- 3 root root 4096 Nov 12 11:59 71 > drwxrwx--- 3 root root 4096 Nov 6 12:01 72 > drwxrwx--- 3 root root 4096 Feb 5 21:52 7d > drwxrwx--- 3 root root 4096 Feb 5 23:05 8b > drwxrwx--- 3 root root 4096 Nov 12 23:41 94 > drwxrwx--- 3 root root 4096 Nov 7 08:31 ae > drwxrwx--- 3 root root 4096 Nov 12 23:40 fa It seems at some point Mailman core was run as 'root' rather than 'list'. ... > Changed the ownership for /var/lib/mailman3/cache to list:list and from that point my lists are responding. > > Same problem occurs before fort he list-directory, which I corrected some days ago. > > Is the ownship misconfiguration a coincidence or did I made a mistake somewhere?? This is a Debian/Ubuntu package question. I'm guessing but all of Mailman core and Mailman web should always be run as user:group list:list in your case. It appears that at some point these were started as root. Whether this is something you did wrong or an issue with whatever init/systemd scripts run these things, I can't say. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Domain ownership issues

by peter＠chubb.wattle.id.au

Hi, I wanted to give another user the ability to create lists, so added that user as 'owner' of the domain. But he does not see the 'create list' button. I decided to try deleting him as owner, and the result is a python exception: KeyError: 'file' ERROR 2021-03-01 20:35:07,195 550 django.request Internal Server Error: /postori us/domains/sel4.systems/owners/b55d58c434c94f6dbd19ae338502dd2e/remove Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py", line 40 , in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/auth/decorators.py", line 75, i n wrapper return fn(*args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/domain.py", line 182, in remove_owners remove_email = client.get_user(user_id).addresses[0].email File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 324, in get_user display_name=display_name)) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 111, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 404: 404 Not Found Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.9.0+ (default, Oct 19 2020, 09:51:18) [GCC 10.2.0] Peter C

4 years, 1 month

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 5:39 PM, Mark Sapiro wrote: > On 10/21/20 12:14 PM, Brian Carpenter wrote: >> >> Well I can't dictate that to my list owners and there is no confirm >> token sent with the moderation notice. Why include this option in >> Postorius when it can't be properly handled? > > Postorius is still a work in progress. The unsubscription policies are > in core and are exposed in Postorius. Certainly the ability to moderate > an unsubscription should be in Postorius, but it isn't yet. We are an > all volunteer project and there aren't that many of us, and perhaps I'm > overreacting, but the tone of some of your recent posts seems a bit > demanding. I apologize. I didn't think I was coming across demanding but I am somewhat exasperated at some of these issues. I have a list owner who is now going to get a moderated request notice everyday that he can't do anything about it. But my question still remains: why is this option in Postorius when it can't be handled properly? Surely the option can be easily removed, right? Is the ability to list (via the pending moderation notices tab) and handle (as in the List owner can decide a moderation response) an unsubscribe moderation request there in Mailman core so that I can properly address it via Affinity? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] Re: DKIM header not added to subscribe/unsubscribe notification email

by Philip Colmer

On Fri, 19 Aug 2022 at 18:11, Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > My guess is that the address Mailman uses for From in those messages > is not in OpenDKIM's SigningTable. This is probably the > $LIST-owner@$LISTDOMAIN address. You should also add the > mailman@$LISTDOMAIN address. > Thank you - it was precisely this bit (the Signing Table) that I was missing. Adding that configuration has fixed it. > Neither can we, although for a different reason. ;-) Please don't > hesitate to send full configuration files to us on the grounds of > absolute size or bandwidth. Such reports are relatively rare, they're > not actually that big, and almost everybody on our lists are admins > who know that it could be them tomorrow. Unfortunately at present I > don't think you can send it as attachments. > > If you're worried about system security, you can either redact > sensitive information such as passwords, domain names, mailboxes, and > IP addresses, or you can send it to one of the developers directly > (me, at the moment; Mark, when he gets back in a few weeks -- I > believe Mark prefers a zipfile if there are multiple files, and I know > I do) if you're willing to trust us. > Thanks, Steve. I appreciate that gesture. Thanks again for your help. Very much appreciated. Regards Philip

2 years, 8 months

[MM3-users] Message shows up individually but not in the thread

by Marvin Gülker

Hi, I've just observed something weird. While some users were testing the new mailman setup, the reply did not make it into the corresponding thread, but is still associated with it. That is, the message does not show up in the thread page at[1]. However, the reply is visible if requested individually[2]. Now what's weird is that in [2] there's a link at the top that says "< thread" that takes one to [1], so there is some kind of association appearently made but only in one direction (the reverse one). mailman.log has this to say: Nov 03 17:22:31 2017 (498) ACCEPT: <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> Nov 03 17:22:32 2017 (507) 127.0.0.1 - - "GET /3.0/users/sydneyjd(a)openmailbox.org HTTP/1.1" 200 305 Nov 03 17:22:32 2017 (495) HyperKitty archived message <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> to https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… The mailman-suite log contains: INFO 2017-11-03 17:22:32,910 14330 hyperkitty.views.mailman Archived message <1fa6f9e1-254c-e999-42d0-9a6cc263020d(a)openmailbox.org> to https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… This looks to me like a bug. The OP of that thread sent the same message to our other mailinglist[3] (where he did not get a reply), so Mailman may has been confused by that. Marvin [1]: https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… [2]: https://lists.secretchronicles.org/hyperkitty/list/tsc-users@lists.secretch… [3]: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 5 months

[MM3-users] DKIM header not added to subscribe/unsubscribe notification email

by Stephen J. Turnbull

Philip Colmer writes: > Everything seems to be working fine *except* when the system sends a > notification email to the list owners of someone subscribing or > unsubscribing. *Those* emails do not have the DKIM header added and are > getting trapped by anti-spam systems as a result. My guess is that the address Mailman uses for From in those messages is not in OpenDKIM's SigningTable. This is probably the $LIST-owner@$LISTDOMAIN address. You should also add the mailman@$LISTDOMAIN address. > I cannot see anything in the configuration for OpenDKIM or Postfix > that might allow just those messages to go out unsigned. Neither can we, although for a different reason. ;-) Please don't hesitate to send full configuration files to us on the grounds of absolute size or bandwidth. Such reports are relatively rare, they're not actually that big, and almost everybody on our lists are admins who know that it could be them tomorrow. Unfortunately at present I don't think you can send it as attachments. If you're worried about system security, you can either redact sensitive information such as passwords, domain names, mailboxes, and IP addresses, or you can send it to one of the developers directly (me, at the moment; Mark, when he gets back in a few weeks -- I believe Mark prefers a zipfile if there are multiple files, and I know I do) if you're willing to trust us. Steve

2 years, 8 months

[MM3-users] Re: Fwd: Re: Removing a mail addresses and users

by Brian Carpenter

Allan Hansen wrote: > Some dedicated and skilled developers are currently investing heavily in a replacement > for Postorius, but I really believe that any work is better spent transforming Mailman > Core etc. into a true account-based system. Then, and only then, will it make sense to > build new and better interfaces on top, as, without a healthy core, such interface will > currently may have to inherit the confusion and disconnect that currently is so > aggravating. Mark said it well. The problem is not with core (which I love very much). The issue you are having is with the decision to use Django. With Affinity, I believe we are using Mailman 3 core to it's (almost) full potential. For instance, the server owner (site admin in Postorius terms) can delete a user with one button and that user is really gone. You can immediately register again with Affinity using the same email and you will have no problems re-registering. If the deleted user was subscribed to multiple lists and were not unsubscribed, then those lists will be waiting for him if/when he re-registers. So our decision to go with a new admin U.I. for Mailman 3 core, imo, has been a great decision. Mailman core is wonderful. One improvement we made is a user can delete their Affinity account but still remain subscribed. They also have the choice to unsubscribe from all their lists at the time of account deletion as well.

4 years, 10 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Sapiro

On 5/18/21 4:06 PM, Mark Dadgar wrote: > I have a user attempting to access the list archives and he’s generating this login error. I have verified that he does have a django account. I’ve never seen this one before and I didn’t find anything relevant in the lit archives. > > Any ideas what’s going on here? ... > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 134, in _has_verified_for_login > emailaddress = EmailAddress.objects.get_for_user(user, email) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/managers.py", line 54, in get_for_user > ret = self.get(user=user, email__iexact=email) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/query.py", line 419, in get > raise self.model.MultipleObjectsReturned( > > Exception Type: MultipleObjectsReturned at /accounts/login/ > Exception Value: get() returned more than one EmailAddress -- it returned 2! > Request information: > USER: AnonymousUser Go to the Django admin users page - something like http(s)://example.com/admin/auth/user/ - and search for the email address. This search is case-insensitive and I'm guessing it will find two users differing in case. In any event, django allauth is trying to find this user and is finding multiple EmailAddress.objects for this address or username. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Rubén Rivero Capriles

Hi! sorry for updating one last piece of info provided by Thomas Woerner of firewalld. He seems interested in our issue of python 2 / python 3: Thomas Woerner <notifications(a)github.com> 4:12 (hace 3 horas) para t-woerner/fire., mí, Author Do you want to use python2 or python3? In the firewalld repo there is a firewalld.spec file. With this it is simply to generate packages for Fedora and also RHEL >= 7. For RHEL-7 it is still using python2, for Fedora >= 23 python3. TO build a package with it you can simple do the following in the root directory of the firewalld source tree: ./autogen.sh make test-rpm Or you can use rpmbuild -ta firewalld-0.4.2.tar.gz with a release from https://fedorahosted.org/released/firewalld/ or https://github.com/t-woerner/firewalld/releases I am still stuck with awstats. Have been able to watch them through lynx linux browser, but stats are not being generated. I enrolled in a local linux academy where I will take an apache course and maybe they''ll be of help. However I don't like software that does not provide support themselves, especially if good folks such as mailman or firewalld team are around. Is there any alternative statistics generation package for apache that you could recommend and I would be able to use without so many installation issues Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining)

8 years, 10 months

[MM3-users] Re: The future is here?

by Jonathan M

On 8 Jan 2021, at 04:18, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Discourse is a different kettle of fish. They concentrate on the much > more straightforward (from a network and interapp communication > configuration standpoint) web service because that's what their users > expect. Mail is a lot more baroque from that standpoint. > > We shouldn't hope to successfully "encourage" hosts to do things our > way. Maybe Mail-in-a-Box is a useful comparator in terms of complexity (though it appears to be less configurable than Discourse, and the software itself is not comparable). Maybe my experience hasn’t been typical. I’ve mainly used a shared server which didn’t have Mailman installed, but of course had email set up. It was relatively easy to install Mailman 2 but impossible to install Mailman 3. I could probably install Mailman 3 on Digital Ocean or similar, but get the feeling that the mail server is the hardest part. If I ever can set aside enough time to get it working I should write the idiot’s guide that I needed. It would be great if there were a “Mailman-in-a-Box” including everything necessary to get Mailman working from scratch on a VPS (in addition to the primary, flexible way that allows experts to use Mailman 3 according to their personal preference). I will look into Abhilash’s Docker container setup. I think the first time I saw that I didn’t know he was “maxking” and assumed it was a third-party thing that would likely be abandoned. Best wishes Jonathan

4 years, 3 months

[MM3-users] The email confirming the registration of an account on postorius is not correctly translated in Italian

by Massimo Zappalà

Hi everyone, thanks to the files.po on Weblate, I have translated all Mailman-Core, Postorius, Hyperkitty and Django_mailman3. I have also translated the confirmation message to subscribe to a list. Everything works, except for this: When I register a new account on postorius, he sends me a confirmation email totally in English, except the following final block which is sent in Italian: in my /usr/lib/python3/dist-packages/allauth/locale/it/LC_MESSAGES/django.po #: templates/account/email/email_confirmation_message.txt:7 #, python-format msgid "" "Thank you from %(site_name)s!\n" "%(site_domain)s" msgstr "" "Grazie da %(site_name)s!\n" "%(site_domain)s" By carefully analyzing the same file .po, I notice that the Italian translation of the whole text already exists. Why does the confirmation email arrive in English? #: templates/account/email/email_confirmation_message.txt:1 #, fuzzy, python-format #| msgid "" #| "User %(user_display)s at %(site_name)s has given this as an email " #| "address.\n" #| "\n" #| "To confirm this is correct, go to %(activate_url)s\n" msgid "" "Hello from %(site_name)s!\n" "\n" "You're receiving this e-mail because user %(user_display)s has given yours " "as an e-mail address to connect their account.\n" "\n" "To confirm this is correct, go to %(activate_url)s\n" msgstr "" "Ciao da %(site_name)s!\n" "\n" "L'Utente %(user_display)s di %(site_name)s ha registrato questo indirizzo e-" "mail.\n" "Per confermare, clicca qui %(activate_url)s\n" Thanks Max

4 years, 8 months

[MM3-users] Re: can't get mail into mailman3 in docker

by Stephen J. Turnbull

bob B writes: > Anyone have any ideas? First, what docker configuration are you using? One supplied by the Mailman project? If not, you need to tell us more about what's going on. If so, are there any containers other than those running the Mailman suite (Mailman 3 core, Postorius, HyperKitty)? In mydestination you have mydestination = $myhostname, localhost.$mydomain, localhost, mydomain.mydomain.com I do not understand the "localhost.$mydomain" entry. I guess that's a Postfix-ism, but I can't find any documentation about it. You could try taking it out (this is a very random suggestion). You say you have no /etc/postfix-mailman.cfg. Where are you looking for it? That file will only exist in the container, not in the host OS. (If it were in the host OS, it would be located somewhere like /opt/mailman/core/postfix-mailman.cfg.) Try `find /opt/mailman/core -name postfix-mailman.cfg`, although "automatically" might mean it's generated in the container when it starts. Abhilash would know, but he doesn't seem to be available. I really don't think it's the issue because I assume "bmimailmandr1" is the Docker container running Mailman core. If so Postfix is connecting to the configured LMTP port on localhost which is what it's supposed to do from the configuration. Since the container's Postfix appears to be connecting to the right place but the connection is refused, that Mailman core may not be running. For more help you'll have to wait for Abhilash. Steve

3 years, 8 months

[MM3-users] Re: Using REST with CLI using curl .... help needed

by Stephen J. Turnbull

Michael Bakonyi writes: > allright, thx a lot for your quick answer! After fiddling around > some more time, I guess I had some misunderstandings regarding the > REST-API. I guess if we reach the API correctly, we will not be > confronted with the CSRF-Error. We will continue to try but > nevertheless: What would be a cleaner approach to reach the API > from an external IP? I didn't found any examples in the web so far. If you mean the core REST API, you won't find any useful examples on the Internet. Anything you do find should be considered a form of self-harm and/or an insider threat. Access to the REST API is not securely authenticated, and therefore should never be exposed to the Internet. This API is expected to be contained either to localhost, or to a subnet behind a firewall that prohibits access to that port except from the host(s) serving HyperKitty and/or Postorius. If that's what you're trying to do, I would suggest a secure tunnel (not a generic VPN, but a specific tunnel to the API port). If you're talking about the Django administrative API to Postorius, you'll probably get a better answer faster from Django channels. Mark may know but he won't be available until mid-September most likely. As I wrote earlier, as far as I know you need to access the Postorius port, provide credentials, get the CSRF token, and then access Django. Regards, Steve

2 years, 8 months

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

Victoriano Giralt writes: > El vie, 23-10-2020 a las 08:19 -0700, Mark Sapiro escribió: > > > > This would be more difficult for Postorius/Hyperkitty because those > > users are Django users, but that isn't an issue for Affinity. > > > > All of a sudden, an idea has dawned on me ... Wouldn't it be possible for > Postorius/Hyperkitty, both Django applications, to use Mailman core user > model as their User model? It is just a setting for Django > (AUTH_USER_MODEL). I find the "just a setting" claim a bit implausible. I suspect a certain amount of replumbing of Postorius and HyperKitty will be necessary to get it to work. Most important, the "AUTH_" is pretty scary. Mailman core has *no* authentication built in. It is assumed to be firewalled off from the rest of the world with only access from Postorius and HyperKitty permitted. Can you expand on how hard it would be to do this? Remember that some Mailman instances are either big targets (eg, Apple) or require good security for content reasons (lists for doctors' patient support groups, domestic violence support groups). This is not a great authn/authz model in the modern Internet, but as far as I can see changing it is going to be quite a lot of work, and none of us are authentication specialists (although Abhilash did study security, I don't think he specialized in authentication tech) -- providing reasonably reliable and secure authentication services, especially "social auth" (OpenAuth, OpenID etc) is an important reason we went with Django in the first place. Steve

4 years, 5 months

[MM3-users] Re: starting gunicorn per mailman.log yet gunicorn not installed

by Odhiambo Washington

On Mon, Jun 26, 2023 at 9:29 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Ken Alker writes: > > > I see the below in my mailman.log, yet I installed uwsgi and NOT > > gunicorn. My mainmanweb.service file includes > > "ExecStart=/opt/mailman/venv/bin/uwsgi --ini > > /etc/mailman3/uwsgi.ini" and not the gunicorn equivalent. Does > > this log entry make sense in my case? > > > > [2023-06-22 12:44:36 -0700] [411132] [INFO] Starting gunicorn 20.1.0 > > Yes, it makes sense. Mailman 3 core is basically an application which > manages a webserver that provides the REST API, a database of domains, > users, and lists, an LMTP server for incoming posts and an SMTP client > for outgoing distribution. Mailman uses gunicorn to provide the > webserver. > > Installation of gunicorn is handled as a package dependency, so you > probably wouldn't notice unless you were watching the installation > process very carefully. > It doesn't make sense, IMHO, because as the OP says, 1. his ExecStart is: ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" *and not* ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application. 2. He has not knowingly created any gunicorn.conf Why would Gunicorn be Exec-ing itself? :-) This being a virtualenv install, I find it very weird. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] Re: Hyperkitty message threading

by Stephen J. Turnbull

andrew.bernard(a)gmail.com writes: > So the issue is, how do I stop my users from this practice of > replying and changing the subject? This is frequently called "thread hijacking." But be thankful that they at least change the Subject! My worry is more people who start in on a completely new subject without doing it, and then complain that they get ignored because they're off-topic for the thread. > I suppose there is no way except education. That's right. If you had the resources of a major AI lab, you could probably train up a classifier to do the job fairly well, but in practice it's a matter for human judgment. Eg, I know that I frequently change the Subject: several posts after others have, eh, "evolved" the subject into a completely different thing :-), so it's useful to have proper threading across the subject change.[1] One practice I found effective was to impose moderation on people who just couldn't practice proper netiquette, then reduce moderation frequency to once a week. ;-) A week is probably overkill. :-þ (I happened to be in a period of frequent travel for two weeks and at the beginning of that period there was this jerk.... He learned.) Once-a-day moderation is sufficiently frustrating for most people to be an effective re-education tool. Steve Footnotes: [1] There was a day and age *sigh* when educated people would *frequently* change the subject to reflect the subject of the *message* rather than the subject of the *thread*. That's gone the way of traditional inlined replies are going, though.

5 years, 9 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/13/21 12:54 AM, Abhilash Raj wrote: > I don't have any strong opinions on treating all disabled options as just > disabled for the user. Would List admins be interested in knowing more > details about that or should it be the same for them? I feel they might > be interested in such details. Brian mentioned that Affinity actually > details explicit value of the delivery_status, so maybe it is useful > for them? > I think treating all disabled options the same is short-sighted. They are all not the same. -- Some list members will disable their subscription for good reasons and will be really upset if a List Owner renables it through ignorance. So it is important to know a disable member is done by the member itself. -- Some mailing lists will have multiple list owners managing them. So it is important for one List Owner to know when a subscription has been disabled by the actions of another List Owner. -- A List Owner may not know that some of his List Members are bouncing messages for various reasons, so reviewing their Membership roster, they see that they have some list members disabled due to bounces and can then address those particular problematic members. @Abhilash, I highly recommend that you contact me off list about getting access to Affinity so you can see what I am talking about. I would love to show you what I have done for Member Management. I offered the same to Steve but he never was interested in taking a look. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail

by Terri Oda

I don't *think* we have a checkbox for this, but I've definitely seen this behaviour in Mailman 2 and had trouble with Mailman getting blocked as a result, so I think this would be a very nice feature request. Terri On January 16, 2020 10:49:38 a.m. PST, Torge Riedel <torgeriedel(a)gmx.de> wrote: >Hi, > >we migrated successfully to mailman3 so far. I have some questions >regarding handling of SPAM mails in mailman, here is the first, second >comes in a separate post: > > >The list moderator currently receives a copy of the original mail in >the info mail he gets for moderation. This is bad in case it was a SPAM >mail, cause we have seen that such an info mail is detected also as >SPAM. That might rise problems cause other mail servers might block the >info mail as SPAM and if this happens too often blocking the whole >server. I fear. At least I see that my rspamd starts learning the info >mail as SPAM. I don't want that to happen. > >I searched mailman web interface for a setting to disable adding a copy >to the info mail. But have not found it. Is it missing or where do I >have to look? > > >Best regards >Torge >_______________________________________________ >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/

5 years, 3 months

[MM3-users] Re: starting gunicorn per mailman.log yet gunicorn not installed

by Mark Sapiro

On 6/26/23 1:15 AM, Odhiambo Washington wrote: > On Mon, Jun 26, 2023 at 9:29 AM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Yes, it makes sense. Mailman 3 core is basically an application which >> manages a webserver that provides the REST API, a database of domains, >> users, and lists, an LMTP server for incoming posts and an SMTP client >> for outgoing distribution. Mailman uses gunicorn to provide the >> webserver. >> >> Installation of gunicorn is handled as a package dependency, so you >> probably wouldn't notice unless you were watching the installation >> process very carefully. >> > > It doesn't make sense, IMHO, because as the OP says, > 1. his ExecStart is: > ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" *and > not* > ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf > mailman_web.wsgi:application. > > 2. He has not knowingly created any gunicorn.conf > > Why would Gunicorn be Exec-ing itself? :-) As Steve says, Mailman core uses Gunicorn to manage it's REST API. This has nothing to do with whatever WSGI server (uWSGI, Gunicorn, Apache mod_wsgi, ...) is used to support the Django applications (django-mailman3, hyperkitty and postorius). I.e., there is always a Gunicorn instance configured and started by Mailman core, regardless of whatever WSGI server supports Django or even if one isn't running Django at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Mark Sapiro

On 10/29/20 5:23 AM, Brian Carpenter wrote: > I have a list owner who had his subscription policy set to confirm. > Apparently that was too hard for his list members to handle so he > changed it to moderate only. If someone sent a subscription request that > needed to be confirm, did not respond to it, and then tried subscribing > again after the member policy changed to moderate, their 2nd > subscription attempt still shows up in the confirmation queue. Is that > normal behavior. My understanding is it is. Please let me know if I am > wrong here. Are you certain that the request waiting confirmation is the second one and not the first? > The real mystery here is when someone tried subscribing again > (listname-subscribe@listdomain) hours after the subscription policy was > changed to moderate and they still showed up in the confirm queue. How > is that possible? I tested the list with two of my addresses and both > showed up in the moderation queue as expected. As far as I can tell from > the mailman logs, this was the person's first attempt at subscribing. I suspect it was not the first attempt and that the subscription waiting confirmation was requested when the policy was confirm. The real question is if a user has a subscription waiting confirmation and the policy is changed to moderate, is a second request rejected because of the request waiting confirmation. If so, I think this is a bug which should be fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Invalid confirm text

by Mark Sapiro

On 8/17/20 4:53 AM, w.schoener(a)alp.dillingen.de wrote: > One thing I forgot to mention: > a week ago, the confirmation-mails still worked. > > And now: > All attempts to confirm the subscribe message failed. I used the list-request(a)list.domain and sent text-only message with the "confirm token" in the subject and/or in the body. This should work. What's in your MTA's logs? > So today I tried and used the Mailman shell to change the pending state to "confirmed", as you described here: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > After I submitted the command util.confirm('hex_token') and restarted mailman with > mailman stop > mailman start It isn't necessary to stop/star/ or restart mailman. How did you exit mailman shell. You must exit with ctrl-D or issue commit() or your transactions won't be committed. In particular, if you exit with exit() without first issuing commit(), nothing will be done. > the pending user wasnt confirmed but cleared, as if he never sent a subscribe-message. The only way to subscribe seems to be by logging in and using there the subscribe-form. What is the list's subscription_policy? It seems you successfully confirmed that token, but that may not be the last step if the list's subscription_policy is confirm_then_moderate. > Do you have any idea, whats going wrong here? I dont know what to do any more. Clearly something is broken, but I don't know what unless it is some permissions issue on the template directories/files you created. Have you looked at Mailman's mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: A few more MM3 questions

by Mark Sapiro

On 5/29/24 9:02 AM, Marc SCHAEFER wrote: > > I have a few questions: > > 1) persistence: as I can regenerate the configuration files (mailman, > mailman-web, hyperkitty), is all what's useful in the DB, or are some > things in /var/lib/mailman3 worth saving? > > obviously messages to be moderated, hyperkitty failed messages, > etc are stored there, but shall I assume that all mailing-lists > configuration, all users configuration and all archives are > in the DB? I don't know the details of where the Debian package puts things, but there may be Postfix related files in /var/lib/mailman3/data, but yes, all mailing-lists configuration, all users configuration and all HyperKitty archives are in the DB? > 2) I imported a list and all messages get a footer of: > %(web_page_url)slistinfo/%(_internal_name)s > which I guess changed between MM2 and MM3; however when I > look at that list configuration in the web interface of MM3, > I see no templates defined, nor any clue where this is > configured: where may I change this? import21 creates these templates in (I think in your case) /var/lib/mailman3/templates. > 3) is there a configuration somewhere that can allow someone to > create a mailman web account ONLY if he is already referenced > somewhere in a mailing-list, and not otherwise? (or to > create accounts that need approvals from an admin > before being usable?) No. > also, can a non-yet-referenced e-mail From: still subscribe to > a private list (confirm+moderate) via e-mail regardless of > the above? Yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

[MM3-users] Re: The future is here?

by Hans-Martin Mosner

Am 08.01.21 um 12:06 schrieb Jonathan M: > > It would be great if there were a “Mailman-in-a-Box” including everything necessary to get Mailman working from scratch on a VPS (in addition to the primary, flexible way that allows experts to use Mailman 3 according to their personal preference). That would certainly be best, but the spectrum of possible environments has been widened in recent years due to containerization (which encourages splitting a service into microservices) and there would be a number of possible “Mailman-in-a-Box” variants. The simplest variant installable on a VPS should indeed be relatively straightforward, but even there you have several mail system options, several ways of running Python, several possible databases and web servers, all of which are outside of the Mailman-in-a-Box package. If you integrate with an existing postfix installation using virtual alias domains, you will need to follow the instructions at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… which can be a bit daunting if you don't know your postfix installation really well. > I will look into Abhilash’s Docker container setup. I think the first time I saw that I didn’t know he was “maxking” and assumed it was a third-party thing that would likely be abandoned. This is certainly a good option, although it has still some rough edges IMHO. In theory, it allows a much more coherent packaging, but in practice, you still need to integrate it into your mail and web server environment. Sharing files as a communication mechanism is fragile, and for example getting the postfix maps generated by Mailman into your postfix installation which may be in another container, on the docker host, or on another server, can be tricky. Cheers, Hans-Martin

4 years, 3 months

[MM3-users] Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 3:13 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/5/24 1:52 PM, advorkin(a)cs.princeton.edu wrote: > > > > I went with the apache/uswgi configuration. The site is up and running, > but if I click Postorius, it gets redirected to > https://mysite.com/postorius/lists and I get not found error message. > > > > The same goes for Lists and Archives. > > Compare your urls.py to > < > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re…>. > > Some of the `path` settings are probably not in the same order as in > that file. The > > ``` > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > ``` > settings should come after the > ``` > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > ``` > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > order). Or you can just delete the 'postorius/' and 'hyperkitty/' ones > or you can add > ``` > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ``` > to your Apache config. > The odd thing is that the HOWTO that he followed never involves the manipulation of any urls.py at all - it's not even mentioned at any point. So obviously the issue is caused by something else and I suspect something within Apache needs to be re-evaluated in the guide. -- 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, 1 month

[MM3-users] Re: Question about message bounce stats

by Ruth Ivimey-Cook

Stephen, Thanks for your comments. I kinda-thought that was the state of affairs but am glad there is at least some work on it in the pipeline. If Abhilash has a starting point, and there is acceptance from others to integrate something of this sort, then I could possibly help make it happen. Ruth On 30/08/2021 16:46, Stephen J. Turnbull wrote: > Ruth Ivimey-Cook writes: > > > Does Mailman3 keep such stats, and if so is there any way to get > > access to them, even if only API? I would think it useful to do so > > (and yes, for individual outgoing messages at least for a period). > > In released versions, it currently does not, as far as I know. This > kind of thing should be available from your MTA, of course, and I > think there was a visceral opposition to keeping track of people's > behavior that way from the early days. So those are our excuses. > > However, it's something that comes up occasionally on the list as well > as as a GSoC proposal, and I think there's some code on a branch for > this that Abhilash has been threatening to release. And of course > HyperKitty now publishes stats on posting behavior. So there's really > no reason to oppose it, now it's just a matter of time to implement. > > Abhilash's participation has been kind of spotty recently (and > apologetic about it, he's not going anywhere), but hopefully he'll > pick up the thread shortly and at least confirm or deny what I wrote > here. > > Steve -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years, 7 months

[MM3-users] Re: Change digest frequency and default threshold

by Henrik Rasmussen

Thanks for the hints. It looks to be a file permission problem. I am not sure what the right persommions should be inside he container. Is there a command for checking file permissions, like the Mailman 2's command check_perms? I couldn't file one. Mark Sapiro wrote: > Something is going wrong in this process in DigestRunner. Is > DigestRunner running? Yes: 43 mailman 2:05 /usr/local/bin/python /usr/local/bin/runner -C /etc/mailman.cfg --runner=digest:0:1 > Is there anything in Mailman's digest or shunt > queues? As of /opt/mailman/core/var/queue/digest/ and /opt/mailman/core/var/queue/shunt/ no, but there is three files in /opt/mailman/core/var/queue/bad/ -rw-rw---- 1 root root 398 Oct 10 14:42 1539175326.8246331+4b7e80db0d22f01c2d4363e323320fcd34560657.psv -rw-rw---- 1 root root 398 Oct 11 12:11 1539252672.3947155+ae2631d9f6514d74c77a38f09f821ee71515f9d9.psv -rw-rw---- 1 root root 398 Oct 11 12:24 1539253469.5928977+15b0842462ddd3abcac8d688e5bbb195b07409bc.psv They seems to be binary, buy strings reveal: mailman.email.message Message policy email._policybase Compat32 _headers _unixfrom _payload _charset preamble epilogue defects _default_type text/plain listid test.lists.example.com digest_path =/opt/mailman/var/lists/test.lists.example.com/digest.1.9.mmdf volume digest_number version _parsemsg If that reveals anything. > Is there anything logged in Mailman's 'mailman' log? It seem to say PermissionError: [Errno 13] Permission denied, but inside the container, the directoried in /opt/mailman/var/queue is drwxrwx--- 2 mailman root 4096 Mar 14 2018 archive drwxrwx--- 2 mailman root 4096 Oct 12 10:14 bad drwxrwx--- 2 mailman root 4096 Mar 14 2018 bounces drwxrwx--- 2 mailman root 4096 Mar 14 2018 command drwxrwx--- 2 mailman root 4096 Oct 11 10:24 digest drwxrwx--- 2 mailman root 4096 Oct 12 10:07 in drwxrwx--- 2 mailman root 4096 Mar 14 2018 nntp drwxrwx--- 2 mailman root 4096 Oct 12 10:07 out drwxrwx--- 2 mailman root 4096 Oct 12 10:07 pipeline drwxrwx--- 2 mailman root 4096 Mar 26 2018 retry drwxrwx--- 2 mailman root 4096 Mar 14 2018 shunt drwxrwx--- 2 mailman root 4096 Oct 10 12:32 virgin Henrik Rasmussen

6 years, 6 months

[MM3-users] Mail going to Held Messaging even the moderation is set to Accept Immediately

by Shashikanth Komandoor

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in built postfix version 2.10.1-6 on RHEL 7.5 in production environment from the past 2 months almost. Recently I observed a peculiar case. There is a list say testlist(a)lists.testdom.com has a member say testuser(a)testdom.com whose Moderation attribute is set to "Accept immediately (bypass all other rules)". It is expected that the mail should be delivered to the recipients without being held irrespective of the body content as per my knowledge. (Correct me if I am wrong). But the mail went to "held messages" and is waiting for pending approval. The same user if he sends a normal and simple test mail, it is getting delivered automatically without coming to the "held message". And the same mail (which went to "held messages") is tried to be sent by another member whose moderation attribute is also set to "Accept immediately" only but observed the same effect as the message going to the "held messages". As per my understanding on Mailman 3, if the moderation attribute is set to "Accept immediately (bypass all other rules)" then without checking any rules, it should be delivered to the recipients of the list irrespective of the message or body of the message but is there any such checking if the body content or subject or any thing else is checked even if the moderation bit is set to "Accept immediately". Please help me to resolve this issue. Also, please let me know if I need to share any details. -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

4 years, 9 months

[MM3-users] Re: How to import mailman2 into mailman3 in Docker, getting error with archives.

by Abhilash Raj

On 9/15/21 11:30 AM, Jens Günther wrote: > For importing the archives, it's the mailman-web container. For me it > was like: > > python manage.py hyperkitty_import -l listxy(a)somedomain.org > /opt/mailman-web-data/listxy.mbox > > Before I connected into container as the user mailman! Also, you want to add the listxy.mbox at /opt/mailman/web/listxy.mbox on your host for the above command to work. > > Hope this helps. > > Am 15.09.21 um 19:36 schrieb bob B: >> I know you can't run mailman commands in the docker images and I have >> to copy the data to an area where he docker images can access it, but >> in looking that the commands I got the list settings to import >> >> docker exec -it mailman-core mailman import21 >> [REDACTED](a)REDACTED].REDACTED].org >> /opt/mailman/migration/config.pck *** this worked >> >> >> But having issues importing the archives? do i run this on >> mailman-core OR mailman-web? I tried both but it does not like >> python? >> >> docker exec -it mailman-core python manage.py hyperkitty_import -l >> [REDACTED](a)REDACTED].REDACTED].org /opt/mailman/migration/[REDACTED].mbox >> OCI runtime exec failed: exec failed: container_linux.go:380: starting >> container process caused: exec: "python": executable file not found in >> $PATH: unknown >> _______________________________________________ >> 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/ >> > _______________________________________________ > 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, Abhilash Raj (maxking)

3 years, 7 months

[MM3-users] Re: Python is updated

by Lars Bjørndal

Thanks to all! My installation now works again. Lars On Sat, Apr 29, 2023 at 11:44:34AM +0300, Odhiambo Washington wrote: > On Sat, Apr 29, 2023 at 8:25 AM Lars Bjørndal <lars(a)lamasti.net> wrote: > > > Thank you very much. You wrote: > > > > [...] > > > > > > I tried `django-admin migrate --pythonpath /etc/mailman3`, and got the > > same result. > > > > > > > > > Then you may need > > > > > > `django-admin migrate --pythonpath /etc/mailman3 --settings settings` > > > > Yes, that worked! > > > > > What I have is this shell file that I use to invoke django-admin > > > ``` > > > #!/bin/bash > > > . /opt/mailman/mm/venv/bin/activate > > > cd /opt/mailman/mm > > > export PYTHONPATH=/opt/mailman/mm > > > > So you have settings.py in /opt/mailman/mm rather than in /etc/mailman3? > > > > That's right - based on an earlier installation method before the official > virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> > one was put together, and that's why he has that shell file. > For a virtualenv > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…> > setup, your settings should live in /etc/mailman3 as stated. > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] > _______________________________________________ > 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

1 year, 11 months

[MM3-users] Re: To what extent can mailman 3 handle images and html?

by paul＠arenson.org

THIS IS A TEST as explained in the previous message. Note that all is embedded except the very last URL, which has brackets around it. Click titles to read NEWEST STORIES/最新の記事 October 21, 2019 <https://www.tokyoprogressive.org/i-was-exposed-to-nerve-agent-on-okinawa-us…>October 21, 2019 “I was exposed to nerve agent on Okinawa” – US soldier sickened by chemical weapon leak at Chibana Ammunition Depot in 1969 breaks silence on what happened that day. <https://www.tokyoprogressive.org/i-was-exposed-to-nerve-agent-on-okinawa-us…> By Jon Mitchell (Japan Focus) On July 8 1969, 19-year old US soldier Daniel Plemons was working at Chibana Ammunition Depot, Okinawa, in one of the most dangerous – and secretive – jobs in the US military: the maintenance of chemical weapons. “There were 500-pound (227 kg) bombs filled with nerve agent and we were... October 17, 2019 <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%b7…>October 17, 2019 多摩川河川敷に男性の遺体、増水した川に流されたか <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%b7…> 1４日午後、東京・日野市の多摩川の河川敷でホームレスとみられる男性の遺体が見つかり、警視庁は、台風で増水した川に流されたとみて調べています... October 16, 2019 <https://www.tokyoprogressive.org/%e5%8f%b0%e6%9d%b1%e5%8c%ba%e3%81%ae%e8%87…>October 16, 2019 台東区の自主避難所、ホームレス男性の避難断る <https://www.tokyoprogressive.org/%e5%8f%b0%e6%9d%b1%e5%8c%ba%e3%81%ae%e8%87…> 台風１９号が接近、上陸した１２日、東京都台東区が、自主避難所を訪れたホームレスの男性２人を受け入れなかったことが、区や関係者への取材でわかった。区側は、避難所は区民を対象としたもので、２人が住所不定であることを理由に受け入れを断ったという。区は「住所不定者をどうするかとの観点が抜けていた」と説明し、「反省点とし、今後、住所不定者をどう援助できるかを検討する」としている。 October 16, 2019 <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapist-…>October 16, 2019 Journalist Ito Shiori Sues Alleged Rapist for 11 Million Yen <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapist-…> 「…性暴力の被害を受けた方々に対して世間があたたかい温度にできるように、ポジティブな言葉だったり、『あなただけじゃない』というメッセージをどんどん発信していただけたら、と思います」 “I hope that victims of sexual violence will receive words of encouragement and messages like “You’re not the only one” so that the world can understand them.” October 16, 2019 <https://www.tokyoprogressive.org/freedom-fighting-nagoyas-censored-art-exhi…>October 16, 2019 Freedom Fighting: Nagoya’s censored art exhibition and the “comfort women” controversy <https://www.tokyoprogressive.org/freedom-fighting-nagoyas-censored-art-exhi…> By David McNeil An exhibition of censored artwork in Nagoya city triggers a furious debate on artistic expression. The artistic director of the Aichi Triennale 2019 had few illusions when he planned an exhibition called “After Freedom of Expression”. By choosing items that poked painfully at some of Japan’s most tender spots – war crimes, […] October 10, 2019 <https://www.tokyoprogressive.org/bread-roses-is-your-attending-physician-wo…>October 10, 2019 Bread & Roses: Is Your Attending Physician Working for Free? <https://www.tokyoprogressive.org/bread-roses-is-your-attending-physician-wo…> by Hifumi Okunuki (Shingetsu News Agency) Medical professionals, even doctors themselves, often accept this anachronistic apprenticeship system as a necessary evil or as shikataganai (unavoidable). This recalls how many in the medical profession readily accepted the inevitability of robbing young women of their spots in medical school while practicing some grotesque form of affirmative action […] Plus Bread & Roses: Is Your Attending Physician Working for Free? <https://www.tokyoprogressive.org/bread-roses-is-your-attending-physician-wo…> <https://www.tokyoprogressive.org/bread-roses-is-your-attending-physician-wo…> by Hifumi Okunuki (Shingetsu News Agency) Medical professionals, even doctors themselves, often accept this anachronistic apprenticeship system as a necessary evil or as shikataganai (unavoidable). This recalls how many in the medical profession readily accepted the inevitability of robbing young women of their spots in medical school while practicing some grotesque form of … <https://www.tokyoprogressive.org/bread-roses-is-your-attending-physician-wo…>[Read more...] <https://www.tokyoprogressive.org/bread-roses-is-your-attending-physician-wo…> Bread and Roses: A Leftist Case Against Hate Speech Laws in Japan <https://www.tokyoprogressive.org/bread-and-roses-a-leftist-case-against-hat…> <https://www.tokyoprogressive.org/bread-and-roses-a-leftist-case-against-hat…> by Hifumi Okunuki, Shingetsu News Agency ...I was in a café with a friend who has little interest in politics. She turned to me and said, “South Korea really pisses me off.” Another friend of mine returned home to her octogenarian parents. During dinner her father started going off on Korea and Koreans. This shocked my friend because he had never before expressed any sort of … <https://www.tokyoprogressive.org/bread-and-roses-a-leftist-case-against-hat…>[Read more...] <https://www.tokyoprogressive.org/bread-and-roses-a-leftist-case-against-hat…> Support the Waseda Chronicle <https://www.tokyoprogressive.org/a-finger-in-the-eye-of-the-powers-that-be-…> <https://www.tokyoprogressive.org/a-finger-in-the-eye-of-the-powers-that-be-…> By David McNeill (Foreign Correspondents Club of Japan) One autumn day five years ago, journalists at the Asahi Shimbun looked up from their desks to see their boss holding an impromptu press conference on the newsroom TV screens. For months, the newspaper had been taking flak over an article about the Fukushima nuclear accident. Now Tadakazu Kimura, its president, was … <https://www.tokyoprogressive.org/a-finger-in-the-eye-of-the-powers-that-be-…>[Read more...] <https://www.tokyoprogressive.org/a-finger-in-the-eye-of-the-powers-that-be-…> Slow burn: Dirt, Radiation, and Power in Fukushima <https://www.tokyoprogressive.org/slow-burn-dirt-radiation-and-power-in-fuku…>) <https://www.tokyoprogressive.org/wp-admin/post.php?post=111058&action=edit> <https://www.tokyoprogressive.org/slow-burn-dirt-radiation-and-power-in-fuku…> From Peter Wynn Kirby, Japan Focus. The record earthquake and tsunami that struck Japan on 11 March 2011 ushered in a highly mediated disaster as Japanese grappled with the triple-meltdowns and radiation crisis at Fukushima Daiichi Nuclear Power Station. Largely out of sight of international camera crews and probing journalists, the Japanese state and multiple municipalities … <https://www.tokyoprogressive.org/slow-burn-dirt-radiation-and-power-in-fuku…>[Read more...] <https://www.tokyoprogressive.org/slow-burn-dirt-radiation-and-power-in-fuku…> And COMMENT BY A READER ============================================ Remembering the Tsushima Maru Disaster 75 Years Later ============================================ See the bottom of the article < https://www.tokyoprogressive.org/remembering-the-tsushima-maru-disaster-75-… <https://www.tokyoprogressive.org/remembering-the-tsushima-maru-disaster-75-…> >

5 years, 6 months

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Cameron Smith

I would suggest that there is something very broken here: there seems to be a problem with communication between the email system (mailman core…?) and HyperKitty. On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. So, what’s going on? What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > On 2017.11.21, at 06:31 , Cameron Smith <ccsmith(a)mail2.cetsi.com> wrote: > > Thor, > > I, too, have been struggling with messages not showing up [1], although the conditions are somewhat different. > > What I have found works to make all of the messages appear is the following, which you might try: > > sudo docker-compose exec mailman-web ./manage.py runjobs yearly > > > [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > >> On 2017.11.21, at 04:41 , Thor Atle Rustad <thor.rustad(a)gmail.com> wrote: >> >>> >>> >>>> When I send a message from the Postorius interface, it is neither sent >>> out >>>> or stored. I briefly see this message: "Your reply has been sent and is >>>> being processed.", and then nothing happens. Cameron Smith Nanaimo, BC tel:1.604.803.0051

7 years, 4 months

[MM3-users] Re: moving lists to another server

by Stephen J. Turnbull

Odhiambo Washington writes: > I use the utf8mb4 character set as default, unless something wants a > different one. > MySQL and MariaDB are almost similar. I have encountered very few > significant differences since I switched to MariaDB. OK, then that would not be a problem. > On Mon, Nov 20, 2023 at 7:56?AM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Isn't one installation using 'mailman' and 'mailmanweb' databases, > > while the other only 'mailman'? You'll need to deal with that at > > least I suppose. > > This is true. However, I was hoping that I could merge the two foreign DBs > into one. I am yet to test it though. Yes. The point is that when you dump 'mailman' and 'mailmanweb' on the old host the name of the database will occur in at least the SQL CREATE DATABASE and CONNECT commands. You will need to edit that for mailmanweb. > I had to Google who he was :-) One of my favorites! > In my case, I did not delete the original example.com. I finally > get to use SITE_ID=0. I suppose that it should be accompanied by > FILTER_VHOST=True Yes, I think so. > I am going to try [the create and configure lists manually and add > subscribers] method. It looks safer for me. If there are only a few, it's little more time spent than writing scripts. And you can be sure you'll have basically working lists that you can fix any inadvertant configuration changes later. The only thing I would double and triple check is privacy settings (reply-to munging, archives, and subscriber rosters) and DMARC settings. In the MTA of course you want to be very careful about getting SPF and DKIM right for the new domain. Steve

1 year, 5 months

[MM3-users] 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

5 months

[MM3-users] Re: Changing subscription address

by Stephen J. Turnbull

Abhilash Raj writes: > > There does need to be a way to revert each option to inherit, and > > there currently doesn't seem to be one. The 'Preferences' interface I > > described in the previous post doesn't provide it either. I will > > think about that. > > The implementation of this isn’t very difficult, but the UX of this is > something I don’t know how to implement in that page to be very > honest. Oh, I can play Liz Warren on that one! :-) "I have a plan for that." > We do already have ability to switch from an explicit address to Primary > Address subscription. I would imagine it would be more than just a > button, but more like a dropdown to choose an email or primary address > and switch all subscriptions to that. Allan's situation is that for some reason he has a lot of users (or at least suspects he does) who would be happy to have only one address that there's only one place to change, but for some reason that address is copied to (not inherited by) each of several subscriptions. We should address that, because I'm pretty sure his suspicion is correct. For example, until I changed one of them -- and got two emails about it for my discard pile :-) -- all of my python.org Mailman 3 subscriptions were explicit. I still have about 8 to go. :-) > This is how Core actually does work[1] if you subscribe via Email > and you already have a primary address. It will lookup a user using > the address and if the address is the primary address of the user, > it will subscribe the primary address. If you say so, I guess it's true. Nevertheless, both Allan and I have observed users with only one address, with that address subscribed literally each time to several (~10) lists. > However, if it isn’t the primary address, and this is a new address, it will > subscribe the address instead of user because the address isn’t > verified at this point and hence can’t be a primary address. We could > extend the subscription workflow to add an additional step to set this > address as primary and subscribe the primary address. Yes, please, I think. Users who don't want this for subscriptions to the primary address are going to be (rare) edge cases. If we need an additional attribute on the user to handle the case of an unverified primary address, I think that's an acceptable cost. Note that to "claim" this User as her own, she has to verify that address. And if she *can* verify that address, we can't stop her from doing so, we can just make it more annoying. > Postorius has the full ability to define its own workflow because > REST API provides full expression capability and doesn’t enforce > anything. Previous versions didn’t had support for subscribing as > Primary Address, but that has since changed and is the default one > in the dropdown. > > This is for authenticated subscription, the anonymous subscribe works > similar to email -join command. Mass-subscribe is probably working the > same way. All of these should unify all subscriptions-by-this-address to one User, in my opinion. > Like mentioned above, it should be possible to do what you suggest. I > am getting into the implementation details here, but the Subscription > workflow would need an additional flag that would verify an address > and use the flag to determine if it should subscribe the address or > addresses’s user if an address is provided to the workflow. I don't think so. Just do the lookup, if it succeeds and matches primary address, use inherit. If it doesn't succeed, create a User and use inherit. If it does succeed, and doesn't match, use the explicit address. It seems to me that this flag would be impractical for email subscriptions (email commands with parameters are generally beyond the kind of user this is most important for) or mass subscriptions (how does the list owner know what the user wants?) anyway. If somebody really wants all their subscriptions via primary address to be copies of the primary address rather than user, I'm sorry, but they'll have to deal with that. I can't imagine that it's the usual case, and there's an easy workaround: make your primary address something other than your usual subscription address! If you disagree with me about the relative burden, then maybe we shouldn't do this at all, but I'm pretty sure this is something we should either do for all subscriptions, or for none. > Primary Address is also an attribute of the Mailman User, so it > should be possible for an admin to set that for a user if the user > doesn’t have an account. When they sign up, they’d be able to > manage and update accordingly. True, but AIUI Allan has a *lot* of users and on average they're relatively needy compared to, say, my user population. The point of his request is to smooth workflows for admins with user populations where the admin *wants* to do many things for their users, or to have smooth user workflows when they teach their users to do it for themselves. That's why I'm focusing on the "I have one address and if it changes I want to change it once" case. I think it's both extremely common, and extremely annoying :-) to admins who have to deal with the current situation. Steve

4 years, 1 month

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Dadgar

On May 18, 2021, at 5:34 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/18/21 4:06 PM, Mark Dadgar wrote: >> I have a user attempting to access the list archives and he’s generating this login error. I have verified that he does have a django account. I’ve never seen this one before and I didn’t find anything relevant in the lit archives. >> >> Any ideas what’s going on here? > ... >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 134, in _has_verified_for_login >> emailaddress = EmailAddress.objects.get_for_user(user, email) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/managers.py", line 54, in get_for_user >> ret = self.get(user=user, email__iexact=email) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 82, in manager_method >> return getattr(self.get_queryset(), name)(*args, **kwargs) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/query.py", line 419, in get >> raise self.model.MultipleObjectsReturned( >> >> Exception Type: MultipleObjectsReturned at /accounts/login/ >> Exception Value: get() returned more than one EmailAddress -- it returned 2! >> Request information: >> USER: AnonymousUser > > > Go to the Django admin users page - something like > http(s)://example.com/admin/auth/user/ - and search for the email > address. This search is case-insensitive and I'm guessing it will find > two users differing in case. > > In any event, django allauth is trying to find this user and is finding > multiple EmailAddress.objects for this address or username. I had actually done this but checked the Users section and had overlooked the Email Addresses section. It was as you suggested - duplicate emails differing only in case. Given that there was only one user account, how does this happen? List subscription without associated user account creation with slightly different case? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 11 months

[MM3-users] Re: Mailman backend maintenance task

by Eugenio Jordan (external)

Dear Steve: I really appreciate you also took your time to provide more insights on how Mailman works, and how their different components interact each other. There are two "minor" tasks and one major task that we would need to accomplish within PostGRESQL, namely rebuilding the index related to hyperkitty_email table primary key, rebuilding also another index on the very same table supporting an uniqueness constraint (these would be the minor); and running vacuum full on the whole database to effectively reduce the size of precisely hyperkitty_email table, which is the largest table in this database, and if possible retrieve back to the SAN the extra space we had to add to cope with that very table size increasing. The way vacuum full locks the tables are, among all the locking mechanisms provided by PostGRESQL to guarantee the transactional integrity, one of the strongest, if not the strongest one (as far as I know, the tables are more ore less recreated when running vacuum full). The idea we were considering was more or less stopping all of the components, then starting up only PostGRESQL, and then performing each one of the mentioned tasks. Actually our PG release allow "online" indices rebuild (drop + rebuild concurrently), but we did not want to assume the risk if, for whatever reason, new records were added to the table breaking the uniqueness of both constraints (fixing this cases turns out to be a real pain in most cases). Alternatively, we could lock the table ourselves to get more or less the same effect, true, although, after all, the final impact on potential connections willing to run DML would be the same. In other words, rather than having lots of transactions coming from whether core component processes or web component processes fail, we prefer to stop everything. But it's got of course the worst downside: we would receive Let me please now go back to your kind explanation to see if I did get things correctly. You mention that regardless the connectivity that Mailman's core processes might have with the database, the emails will be received by and queued until the connection is back again and they can be delivered to the distribution lists' members. Could you please confirm whether this task would be actually delegated to Postfix (or any MTA integrated with Mailman)? If so, this is actually what we need: we could afford delaying the reception a couple of days, whilst we are sure that no mail will be lost. Once more, thanks a lot for your kind help. Best regards. -----"Stephen J. Turnbull" <[1]stephenjturnbull(a)gmail.com> wrote: ----- To: [2]eugenio.jordan(a)esa.int From: "Stephen J. Turnbull" <[3]stephenjturnbull(a)gmail.com> Date: 08/24/2021 05:33PM Cc: [4]mailman-users(a)mailman3.org Subject: [MM3-users] Mailman backend maintenance task Hi, Eugenio, I wrote this earlier but am in the middle of moving my office so my mail has been intermittent. I have been following your discussion with Abhilash, and he's definitely the expert, especially if you are using the containers he creates and distributes. But there's some information here he hasn't mentioned yet. Please consider the following discussion to be background that allows you to understand some of the considerations. I've only run the Mailman 3 suite with all three running constantly on the same host, so I have no experience with this kind of issue. [5]eugenio.jordan(a)esa.int writes: > Our customer is currently using PostGRESQL as backend, and we would > like to perform some maintenance tasks, namely running vacuum full, > or at least trying to rebuild hyperkitty_email primary key related > index. We have been asked on the real impact of putting in place > such initiative. Though the latter is related to archiving, I > haven't found a way to stop just Hyperkitty or Django related > processes other than stopping Mailman's core, hence preventing > mails addressed to distribution lists from being delivered, could > you please confirm if I am correct? Mailman core can certainly run without either Postorius or HyperKitty. Controlling Mailman core (moderation, helping users) without Postorius is annoying, but it can be done. If you stop the HyperKitty process, what should happen, I believe, is that posts for archiving will accumulate in the 'archive' queue until HyperKitty is available again. It's been a while since I studied this so I could be completely wrong, but as I understand it HyperKitty and Postorius are not daemon processes. Rather, they are WSGI applications, which means they are subprocesses spawned by your webserver, and controlled by it. In order to keep them from running, you would reconfigure the webserver to not call those WSGI applications. How that is done is specific to the webserver and the WSGI module. If you are running from Docker containers, most likely, you can just stop their containers. The larger problem is that Mailman core uses a RDBMS. Normally both Django and Mailman are referring to the same RDBMS, PostgreSQL in your case. I'm not familiar with the vaccuum operation; if it requires taking the whole RDBMS down, and Mailman is running on that RDBMS, you're out of luck. Mailman can accept posts and queue them, but it can't deliver them to subscribers without access to the RDBMS tables. If it's just a matter of locking some tables while other are available, then it should work because the tables used by core and HyperKitty are disjoint as far as I know. (I think Postorius and HyperKitty both use Django's user tables for authorization, so at least for those tables both Postorius and HyperKitty will have to be down, but core can continue running because its database is completely separate.) > Regarding the former, as far as I have read, the "mappings" lists > -> addresses are stored just in the database, so if we run some > kind of procedure or task like vacuum which will lock exclusively > tables, or want anyway to have the database stopped for a cold > backup or whatever, Mailman willl not work, that is, again the > mails addressed to the distribution lists will not be > delivered. Will you please confirm this point, too? That depends on how "vacuum" works. If you can tell the RDBMS not to lock Mailman core's tables, it can continue to run. Definitely if the database is not running, Mailman will continue to receive and store the posts, but it won't be able to distribute mail to subscribers until its tables are available again. At that point the queued posts will be processed normally, except that if there's a large backlog, they won't go out in a quick burst, it may take a while. One possible worry, depending on how you are connected to the Internet, is that your provider may interpret the sudden burst of outgoing mail when Mailman comes back on line as spam or some other sort of mischief. Mailman has no way to throttle this: it feeds messages to the MTA until the MTA says "stop". Then it waits until the MTA is ready again. Regards, Steve This message is intended only for the recipient(s) named above. It may contain p roprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropri ate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Prot ection Officer (dpo(a)esa.int) References 1. mailto:stephenjturnbull@gmail.com 2. mailto:eugenio.jordan@esa.int 3. mailto:stephenjturnbull@gmail.com 4. mailto:mailman-users@mailman3.org 5. mailto:eugenio.jordan@esa.int

3 years, 8 months

[MM3-users] Re: Sorry to repeat a question, but how do I permanently delete messages, again?

by William Oliver

Thanks!!! That's exactly what I needed. billo On Fri, 2022-07-08 at 15:12 +0100, Tim Cutts wrote: > It can be done in the GUI. See this historical thread: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > > T > > > On 8 Jul 2022, at 13:48, William Oliver <billo(a)billoblog.com> > > wrote: > > > > > > I askled this question some months ago, but for the life of me > > cannot > > find the response (though there is one). I want to purge some > > specific emails from the list archives. A user posted what he > > thought > > was a personal message to the list, and is embarrased by it, so I > > told > > him I couldn't delete emails that were already downloaded onto > > client > > machines, but I can delete it so that new users won't be able to > > see > > it. > > > > But... I can't figure out how to do it. > > > > I asked this once before, some months ago, and as I remember there > > is a > > command line way of doing it, but not a GUI way. But i can't > > remember > > what it was. > > > > Thanks! > > > > billo > > _______________________________________________ > > 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/ > > _______________________________________________ > 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/

2 years, 9 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/07/31 13:47, Odhiambo Washington via Mailman-users wrote: > Read this thread and take a keen look at the solution provided by @Stephen > J. Turnbull<turnbull.stephen.fw(a)u.tsukuba.ac.jp> : > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > The reason why he got the error is indeed because of fs permissions. I added a line into usr/lib/python3/dist-packages/mailman/utilities/filesystem.py at line 69 to print the directory and it said: Jul 31 18:02:01 mailman mailman3[1029]: ls: cannot access '/var/lib/mailman3': Permission denied So I changed the permissions to the user that mailman runs under (on both servers uid 38). sshfs -o uid=38,gid=38 -o allow_other root@box2.gtahardware.co.za:/etc/mailman3/data /var/lib/mailman3/data Now mailman3 starts without errors and I have a remote directory into which the domains can be written by mailman3's django admin interface. I needed to put these files at these locations: transport_maps = hash:/etc/mailman3/data/postfix_lmtp local_recipient_maps = hash:/etc/mailman3/data/postfix_lmtp relay_domains = hash:/etc/mailman3/data/postfix_domains However, since I'm using power-mailinabox, Postfix is configured to use sqlite already and has these lines by default: virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf virtual_mailbox_maps=sqlite:/etc/postfix/virtual-mailbox-maps.cf virtual_alias_maps=sqlite:/etc/postfix/virtual-alias-maps.cf local_recipient_maps=$virtual_mailbox_maps So I have only added this line to postfix's main.cf: # Add postfix_domains path so mailman can add domains to it for lists relay_domains=hash://etc/mailman3/data/postfix_domains The local_recepient_maps are set my power-mailinabox already, so I'm ignoring what mailman creates. However, in the process I have also change the list domain to be different from the MTA's. Postfix accepts mail for fast.za.net, so I created lists.fast.za.net for the list server. I have changed the domain in django to reflect this, but now I get the original error again, since mailman-web tries to authenticate as lists.fast.za.net, which the MTA doesn't know. I'll have to dig a little to see why this is.

8 months, 3 weeks

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

On Mi, 20 Apr 2022 10:01:55 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/20/22 07:54, Rainer Herbst wrote: >> Dear all, >> >> my first post was to optimistic - the user tested some other >>combinations and when he tries to send a signed HTML mail, the server >>again refuses to accept it with "Diagnostic-Code: smtp; 501 Message >>has defects". >> >> The user suggested that the problem is caused by a line containing >>only "-- " somewhere in the text, but I can not confirm this. >> >> Please find enclosed the refused mail (anonymized). > > That message has no defects. > ``` > >>> import email > >>> from mailman.email.message import Message > >>> txt = b""" (the testmail-abgelehnt.txt contents) """ > >>> msg = email.message_from_bytes(txt, Message) > >>> msg.defects > [] > >>> > ``` > Maybe I have deleted to much when anonymizing the message... I tested the whole message and it gave me: >>> msg.defects [InvalidMultipartContentTransferEncodingDefect()] Than I reduced the message content. The minimal message that provoked the defect is attached. When I delete line 12 ("Content-Transfer-Encoding: quoted-printable") from the message, the defect disapears. > -- > 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/ > Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years

[MM3-users] Deactivate list without deleting it?

by Colin Watson

Hi, I'm experimenting with a port of Launchpad's mailing list infrastructure to Mailman 3. If Barry's reading, he may remember that this is no trivial task, so I'm very definitely not promising that it will be done any time soon. :-) However, for the most part it looks relatively tractable with the aid of the plugin improvements in Mailman 3.2.0; I have the rough outline of a plugin that implements much the same feature set as our current pile of monkey-patches against Mailman 2.1 in a much nicer way. One of the major things I haven't figured out yet is list deactivation and reactivation. In our current 2.1-based code, you can deactivate a list in a reversible way, which basically tars up the list directory so that the list archives can be restored later. This isn't a native operation in 2.1, but it could be done because everything lived on the filesystem. In 3, it's less trivial. We could go to some effort to dump things out of the HyperKitty database and restore it on reactivation, but that seems rather complex and a bit silly. Ideally, I'd like mailing lists to have a "deactivated" state in addition to full deletion. In this state, the list would appear nonexistent for most purposes: incoming email would be rejected, Postorius would deny its existence, etc. There'd need to be corresponding extensions to the IArchiver interface which caused the archiver to put its archives of that list into a corresponding deactivated state, in which it would retain the messages but queries for them would return 404 or similar; these extensions would need to be optional, since while it should be relatively easy to do this in HyperKitty it could be hard or impossible for other archivers, and perhaps this should be a separate operation from deactivating the list itself since people may want to close a list while leaving its archives accessible. Has there been any discussion of this in the past, or any advice as to implementation strategy? Thanks, -- Colin Watson [cjwatson(a)ubuntu.com]

7 years, 3 months

[MM3-users] Re: Found error in docker-container

by Alexander Klotz

Hi, unfortunately I have to get back to this topic, since there's still a problem. We already removed the comments as you suggested, but we still have to make manual corrections when creating a new list, because the alias information is safed incorrectly in the tables of the postfix host. There is a port indication with a "]" in the comments, but it is incomplete. The proper address has to be inserted here. Regards, Alex > On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote: >> Hi, >> >> one of our developers wanted to point out an error he found in mailman >> 3.1, docker container maxking/mailman-core-0.1 >> >> The entries in /opt/mailman/core/var/data/postfix_lmtp are not set >> correctly, example: >> >> /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP >> Address of mailman-core container]:8024 >> >> this actually should look like this: >> >> /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 > > > Can you send a copy of your Mailman configuration that you added at > `/opt/mailman/core/mailman-extra.cfg`? > > I think this is mostly because the configuration parser doesn't > understand the in-line comments. So, if you are using the configuration > exactly as it is mentioned in the documentation, it could be the cause > of this problem. > > Solution to that would be to just remove all the in-line comments. > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 172.19.199.2 # IP Address of mailman-core > container > lmtp_port: 8024 > smtp_host: 172.19.199.1 # IP Address of host where > postfix is. > smtp_port: 25 > configuration: /etc/postfix-mailman.cfg > > > > Like the two comments seen in the configuration above. > > I will update the documentation too so that others don't get caught in > something like this. > > Thanks! > -- Mit freundlichen Grüßen, Alexander Klotz (redaktion kulturserver) mailto:alexk@kulturserver.de Stiftung kulturserver.de gGmbH Lothringerstraße 23 D-52062 Aachen http://ggmbh.kulturserver.de Geschäftsführer: Wolfgang Knauff Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 Umsatzsteuer-Identifikations-Nr.:DE DE 230868040

7 years, 9 months

[MM3-users] Re: The email confirming the registration of an account on postorius is not correctly translated in Italian

by Mark Sapiro

On 7/30/20 9:43 AM, Massimo Zappalà wrote: > > Everything works, except for this: > > When I register a new account on postorius, he sends me a confirmation email totally in English, except the following final block which is sent in Italian: > > in my /usr/lib/python3/dist-packages/allauth/locale/it/LC_MESSAGES/django.po > > #: templates/account/email/email_confirmation_message.txt:7 > #, python-format > msgid "" > "Thank you from %(site_name)s!\n" > "%(site_domain)s" > msgstr "" > "Grazie da %(site_name)s!\n" > "%(site_domain)s" OK. > By carefully analyzing the same file .po, I notice that the Italian translation of the whole text already exists. > Why does the confirmation email arrive in English? > > #: templates/account/email/email_confirmation_message.txt:1 > #, fuzzy, python-format This is marked fuzzy so it isn't used. If you believe the translation is correct, remove the above line (or remove ' fuzzy,' from it) and then recompile the django.mo with msgfmt. Note that the current HEAD on github <https://github.com/pennersr/django-allauth/blob/master/allauth/locale/it/LC…> has the above line as just #, python-format > #| msgid "" > #| "User %(user_display)s at %(site_name)s has given this as an email " > #| "address.\n" > #| "\n" > #| "To confirm this is correct, go to %(activate_url)s\n" > msgid "" > "Hello from %(site_name)s!\n" > "\n" > "You're receiving this e-mail because user %(user_display)s has given yours " > "as an e-mail address to connect their account.\n" > "\n" > "To confirm this is correct, go to %(activate_url)s\n" > msgstr "" > "Ciao da %(site_name)s!\n" > "\n" > "L'Utente %(user_display)s di %(site_name)s ha registrato questo indirizzo e-" > "mail.\n" > "Per confermare, clicca qui %(activate_url)s\n" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Implicit Destination Meaning

by Mark Sapiro

On 2/8/21 6:41 PM, Brian Carpenter wrote: > I just migrated a MM2 list to MM3. The client had no problem sending > posts to his list with MM2. However when he posted to his MM3 list, it > showed up in the moderation queue: > > ============ > Your mail to 'dogs(a)lists.redacted.org' with the subject > > mailing list changes > > Is being held until the list moderator can review it for approval. > > The message is being held because: > > Message has implicit destination > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. > =========== > > Is there a List Setting somewhere that needs to be adjusted to allow > this sender to post without moderation? There are a few things going on here. First, the list setting is require_explicit_destination. This is in Postorius under Settings -> Message Acceptance. If this is False or No, the implicit destination rule will never hit, but clearly it is Yes/True and should have been imported from the 2.1 list so it was probably True there too. When True, it means the list posting address or an acceptable alias must be explicitly addressed (in To:, Cc:, Resent-To: or Resent-Cc: of the post. An acceptable alias is a literal address or pattern matching addresses. These are also in Settings -> Message Acceptance and should have been imported from MM 2.1. For example, if the list's posting address is list(a)example.com, but you can also post to list(a)lists.example.com, list(a)lists.example.com should be in acceptable aliases. The most likely explanation here is that the post is being sent to a subdomain which is not the list's canonical posting address or vice versa. The reason this worked in MM 2.1 but not in MM 3 is in MM 2.1 if the list name matched, the check passed even if the domains didn't, but that is not the case in MM 3. The solution is to add the 'other' addresses to Acceptable aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Only held_messages for 1 (of 3) list has "Mailman REST API not available" message.

by Mark Sapiro

On 1/7/22 4:51 AM, Duane Raymond wrote: > Thanks Mark. > > This sounds like a database problem. What's in Mailman >> core's var/logs/mailman.log ? > > > In the var/logs/mailman.log there was a permission error for the messages/ > store folders. I noticed that some of the mm file and directories were > owned by root vs 'mailman' user (what Brian uses when he set up the mm3 > server). So after resetting all to mailman (I believe others use 'list') `list` is used by the Debian/Ubuntu packages. We recommend `mailman`. These ownership issues are often caused by running Mailman core as `root`. This causes certain things to be created/owned by `root` and when Mailman core is later run as `mailman`, it can't access these things. To guard against this, Mailman core >=3.3.5 will refuse to run Mailman as `root` unless a `--run_as_root` option is specified. > Now I get the error below with the error from mailman.log. ... > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/post_moderation.py", > line 77, in _make_resource > resource['msg'] = msg.as_string() > AttributeError: 'NoneType' object has no attribute 'as_string' This is https://gitlab.com/mailman/mailman/-/issues/856, fixed in Mailman 3.3.5 by https://gitlab.com/mailman/mailman/-/merge_requests/819. You can apply this patch to avoid the issue. ``` --- a/src/mailman/rest/post_moderation.py +++ b/src/mailman/rest/post_moderation.py @@ -74,7 +74,15 @@ class _HeldMessageBase(_ModerationBase): # resource. XXX See LP: #967954 key = resource.pop('key') msg = getUtility(IMessageStore).get_message_by_id(key) - resource['msg'] = msg.as_string() + if msg is None: + resource['msg'] = """\ +Subject: Message content lost +Message-ID: {} + +This held message has been lost. +""".format(key) + else: + resource['msg'] = msg.as_string() # Some of the _mod_* keys we want to rename and place into the JSON # resource. Others we can drop. Since we're mutating the dictionary, # we need to make a copy of the keys. When you port this to Python 3, ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: mm3 installation question

by Stephen J. Turnbull

Odhiambo Washington writes: > Mark Sapiro writes: > > Some of the `path` settings are probably not in the same order as > > in that file. The > > > > ``` > > path('mailman3/', include('postorius.urls')), > > path('archives/', include('hyperkitty.urls')), > > ``` > > settings should come after the > > ``` > > path('postorius/', include('postorius.urls')), > > path('hyperkitty/', include('hyperkitty.urls')), > > ``` > > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > > order). Or you can just delete the 'postorius/' and 'hyperkitty/' > > ones or you can add > > ``` > > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > > ``` > > to your Apache config. > The odd thing is that the HOWTO that he followed never involves the > manipulation of any urls.py at all - it's not even mentioned at any > point. So obviously the issue is caused by something else and I > suspect something within Apache needs to be re-evaluated in the > guide. I believe this is the Apache configuration the OP is using: <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/admin" "http://127.0.0.1:8000/admin" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" </IfModule> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" URI paths. It is quite unclear to me how this works at all with either the path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), version of urls.py or the reverse order version path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), I think Mark must have a configuration with ProxyPass "/" "http://127.0.0.1:8000/" in the Apache configuration in mind? Or an alias or rewrite rule. Otherwise I don't see how "/postorius" and "/hyperkitty" paths ever get transmitted to the WSGI server. Steve

1 year, 1 month

[MM3-users] Docker mailman3 delete social logins, did something change?

by bob B

I want to remove the social logins from mailman3 in docker. I found this info https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… but the link to the default shows *************** INSTALLED_APPS = [] DEFAULT_APPS = [ 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', ] ***************** However when I go to the bug https://github.com/maxking/docker-mailman/issues/283 it shows ********* INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', ) ******** The two examples are different so what should it be? I tried to add it in both ways and when I do I get bad gateway and he mailman website is broke. I have not setup any domains yet, just setup the admin password,. For example this breaks my website cat /opt/mailman/web/settings_local.py ALLOWED_HOSTS = ['127.0.0.1','localhost','REDACTED','REDACTED','REDACTED','REDACTED','REDACTED'] #ALLOWED_HOSTS = ['*'] DEBUG = True #DEBUG = False EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'REDACTED' EMAIL_PORT = 25 INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', ) ************************************************************************* And I have even removed anything? What should my /opt/mailman/web/settings_local.py look like?

3 years, 7 months

[MM3-users] Re: Docker Support Sucks

by Mark Sapiro

On 7/21/20 5:40 PM, Brian Carpenter wrote: > Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. Abhilash (@maxking) is one person and he has a $DayJob. We're all doing the best we can. > I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. This is not a Docker issue per se. It is a consequence of upgrading Mailman core to 3.3.1+ and processing many old, stale, previously unprocessed bounces. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. > > I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: > > ### > The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: > > [webservice] > configuration: /path/to/gunicorn.cfg > > and then in the gunicorn.cfg you can add > > [gunicorn] > timeout = 90 > graceful_timeout = 30 > ### > > I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. > > After restarting docker-mailman, I can't access Postorius due to the following error: > > ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available Is Mailman core running? If not, whats in core's mailman.log as to why not? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Archives visible to all

by worik

tl;dr location ~ ^/hyperkitty { # Turn off archiving for Mailman3 allow 1.2.3.4; deny all; } There should be a better way (https://gitlab.com/mailman/hyperkitty/issues/219) Problem fixed, but at he cost of no archives and a broken "archives" link. On 22/02/19 9:03 PM, Johannes Winter wrote: > Am Thu, 21 Feb 2019 12:23:41 +1300 > schrieb worik <root(a)worik.org>: > >> When I load my new mailing list system, before I log in, I can see the >> archives of all the lists. Without logging in. Even lists with >> archives set to private archives. >> >> What can I do about that? > Are you sure that you really can see the list contents? In my case only > the listnames are shown, which is not nice, but bearable. Yes, that is true. Since I made my first post on this thread (which was a bit premature) I have researched this further. All messages posted before the archives are made private are displayed for all to ee, and I can find no ay of changing that except by making hyperkitty a dead link, as above. Displaying all lists on the server is unacceptable for my users. My users are involved in political activism and displaying the names of all the lists is a political risk. (As distinct from privacy or security risks). > > There is an open issue about that: > https://gitlab.com/mailman/hyperkitty/issues/197 > > Would be happy for workaround ideas, too. Yes. It has been open for half a year, https://gitlab.com/mailman/hyperkitty/issues/129 for a year. The problem is that Hyperkitty does not "...use the list's |advertised| setting to show or hide it...". IMO this is also a bug in Mailman core. Clearly Archivers need to respect changes in the statius of a list and change the status of archives already collected (not a trivial matter) but Mailman should not hand over the names of lists where archives are turned off. As I write I realise I have not tested creating a list with archives off from the get go... Worik > > > Johannes Winter > -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 2 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 11:33 AM, Mark Sapiro wrote: > On 10/29/20 5:23 AM, Brian Carpenter wrote: >> I have a list owner who had his subscription policy set to confirm. >> Apparently that was too hard for his list members to handle so he >> changed it to moderate only. If someone sent a subscription request that >> needed to be confirm, did not respond to it, and then tried subscribing >> again after the member policy changed to moderate, their 2nd >> subscription attempt still shows up in the confirmation queue. Is that >> normal behavior. My understanding is it is. Please let me know if I am >> wrong here. > > Are you certain that the request waiting confirmation is the second one > and not the first? Good point and I am not sure. I will try to note that if this pops up again. > > >> The real mystery here is when someone tried subscribing again >> (listname-subscribe@listdomain) hours after the subscription policy was >> changed to moderate and they still showed up in the confirm queue. How >> is that possible? I tested the list with two of my addresses and both >> showed up in the moderation queue as expected. As far as I can tell from >> the mailman logs, this was the person's first attempt at subscribing. > > I suspect it was not the first attempt and that the subscription waiting > confirmation was requested when the policy was confirm. The confirmation moderation notice had the date-time stamp that came a few hours AFTER the subscription policy was changed. Also I only saw one confirmation request sent out via Postfix' mail.log. I saw no other for this subscriber. Same thing with the smtp.log. I cannot duplicate this behavior when I try to subscribe. My subscription attempts went straight to moderation. > > The real question is if a user has a subscription waiting confirmation > and the policy is changed to moderate, is a second request rejected > because of the request waiting confirmation. If so, I think this is a > bug which should be fixed. > Do you think this is a bug with Mailman core or my system? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] posting bounced with 501 Message has defects

by Stephen J. Turnbull

Hitashi mancho via Mailman-users writes: > One of our users posted an email using a Bluemail Desktop client on one of > the mailing lists. This email bounced with the reason "501 Message has > defects". Bouncing the message is arguably an overreaction to this particular defect, but in fact Bluemail is violating a "MUST NOT" in RFC 2045. Mailman takes the position that in principle we should not forward non-conforming mail. At least one expert has told me he considers this defect harmless, but (a) it's not clear to me that it is harmless (especially in the hands of a malicious actor targeting carelessly- written applications) and (b) it's hard to get excited about adding complicated logic to the code to make life easier for an application that doesn't conform to a trivial 30-year-old restriction. > However, it gets accepted if the same user posts the same email > on the same mailing list using Webmail (RoundCube) or Thunderbird. I'm not familiar with the maintainers of RoundCube, but Thunderbird has a long history of respect for Internet standards. > There is nothing in mailman.log and bounce.log, even in debug mode. Since this is happening during receipt of the message I would guess that all messages related to the problem would be in Mailman's smtp.log. I don't think you'd see anything about this in mailman.log unless the defect managed to crash the lmtp runner or all of Mailman. bounce.log reports bounces *received* by Mailman, not bounces caused by Mailman. > Apr 21 18:00:47 2025 (1979121) ('127.0.0.1', 44502) << b'501 Message has defects' I seem to recall that Mark submitted a patch to add the defect list to this message. I will follow up on that (although it doesn't help get the message delivered to subscribers, it will make diagnosis a lot easier and faster). > Content-Type: multipart/alternative; > boundary="----sinikael-?=_1-17452386441150.6962994414278503" > Content-Transfer-Encoding: quoted-printable This the problem. When Content-Type is 'multipart', the only values allowed for Content-Transfer-Encoding are '7-bit', '8-bit' and 'binary'. This is a "what were they thinking?!" level bug. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 days

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Mark Sapiro

On 11/29/2017 05:05 PM, Cameron Smith wrote: > > On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. Your post was received: Nov 21 14:31:20 mailman postfix/cleanup[15735]: 2B3798008D: message-id=<836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> Nov 21 14:31:20 mailman postfix/qmgr[20545]: 2B3798008D: from=<ccsmith(a)mail2.cetsi.com>, size=10048, nrcpt=1 (queue active) delivered to Mailman core: Nov 21 14:31:20 mailman postfix/lmtp[15737]: 2B3798008D: to=<mailman-users(a)mailman3.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.28/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) and immediately discarded: Nov 21 14:31:21 2017 (19106) DISCARD: <836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. Possibly you never received a list copy of his message because you were directly addressed and your list option "Receive list copies (possible duplicates)" is set to No. > So, what’s going on? As to why your post was discarded, unfortunately, the logs don't give more info. There are a couple of possibilities. If your post contained an attachment with Content=Type: application/subtype where sub-type doesn't contain 'signature' it would have been discarded by a header filter rule. Also it looks like you sent the message From: <ccsmith(a)mail2.cetsi.com>. If that is not an address on your <ccsmith(a)cetsi.com> account, it would have been discarded as a non-member post. > What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. I see nothing so far to indicate anything at lists.mailman3.org is broken in this respect. The only "unusual" thing is this is now a new thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, but presumably that is because your post was in reply to your earlier post which wasn't archived. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: hello， Discussion on how to subscribe to themailing list

by Stephen J. Turnbull

朱超 writes: > 1. It is not the MTA that refuses to send emails because the > recipient's mailbox is too long, but the MUA that refuses to > send the email because the recipient's mailbox is too long. That's still non-conforming to RFC 821, published in 1982. Seriously, those mail clients are garbage and I have no sympathy for their users. We're certainly willing to make some changes to Mailman to make things a little easier for mailing list owners who have to deal with such users, but there's no excuse for using those MUAs in 2023. > https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token, > but he reported 404. If you mean that literally, of course it did. example.com, and its siblings in the org, net, and edu domains, as well as all subdomains, are domains reserved for examples in documentation. They all resolve to the same IP (owned by IANA), which simply provides a web page explaining what those domains are for. There's no Mailman there. :-) For that to get a response from Postorius, at minimum you need to substitute your Mailman web host for "www.example.com", and the list's ID (usually the same as the posting address with "." substituted for the "@") for $list_id. You may also need to change the URL path, depending on the top-level urls.py you use for Postorius. > 2. It is recommended to modify postorius, in order to keep the > logic function of the underlying mailman-core unchanged, More important than the detailed functions of mailman-core are the original requirements and design. Core should handle email (both in and out), and Postorius should handle web requests. It's asking for trouble to have core send mail to confirm subscription requests by mail, and Postorius to send mail to confirm subscription requests by web. Among other things it violates "Don't Repeat Yourself": if we (or you) change the confirmation template in core, we (or you) need to also change the confirmation template in Postorius. But it's very easy to forget, and an annoyance for reviewers to check. It's possible that the other core devs will overrule me on this, but you shouldn't hold your breath waiting for that. I've been very good at channeling the consensus of the devs for around 20 years now. :-) Steve

2 years, 3 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Dadgar

On Mar 2, 2021, at 9:31 AM, Quanah Gibson-Mount <quanah(a)symas.com> wrote: > --On Tuesday, March 2, 2021 9:09 AM +0100 Lars Schimmer <l.schimmer(a)cgv.tugraz.at> wrote: > >> On 01/03/2021 13:15, Brian Carpenter wrote: >>> On 3/1/21 3:10 AM, Lars Schimmer wrote: >>>> If it should be a gold standard, it should mention the default setup >>>> of a standard debian system (which is exim4, btw) and not assuming a >>>> special setup debian system. >>> >>> So why don't you write up your own how-to for your so-call ''standard >>> debian system". Remember this is a forum for Mailman 3, not a forum for >>> the users of a "standard debian system". So far your comments are not >>> helpful at all. >> >> Install debian >> >> apt-get install mailman3-full > > As someone who is stuck using the ancient version of mailman3 in debian, I have to disagree. 99.9999% of the time I hit an issue, it turns out it was fixed years ago, but because I use the debian maintained version, I don't have those fixes. It's horrible. +100 I originally installed mailman3 via the ubuntu packages and I eventually replaced that setup (read: paid Brian to re-install mailman3 “correctly") for 2 key reasons: 1) The ubuntu (and presumably debian) packages are 1+ years out of date - Quanah is correct in that most of the bugs you hit have been fixed already but haven’t made it through the package maintainer process yet. 2) The package installs are non-standard with respect to the way the mailman3 community tends to install them, which makes getting support here on this list much, much harder. You can see evidence of that periodically when someone asks a question and Mark’s response starts with “I’m not entirely sure how the <distro> package sets things up, but …”, which is no slight on Mark because he has his hands full with mm3 already and tracking every distro install layout is just not going to happen. It also means that the official mm3 docs don’t match what came out of your package. It’s just not good all the way around. > Distribution packages tend to be useful for really basic things like libraries. For constantly evolving projects where you need to be current, they're more of a detriment. So much this. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 1 month

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Abhilash Raj

On Wed, Oct 21, 2020, at 3:35 PM, Brian Carpenter wrote: > > On 10/21/20 5:39 PM, Mark Sapiro wrote: > > On 10/21/20 12:14 PM, Brian Carpenter wrote: > >> > >> Well I can't dictate that to my list owners and there is no confirm > >> token sent with the moderation notice. Why include this option in > >> Postorius when it can't be properly handled? > > > > Postorius is still a work in progress. The unsubscription policies are > > in core and are exposed in Postorius. Certainly the ability to moderate > > an unsubscription should be in Postorius, but it isn't yet. We are an > > all volunteer project and there aren't that many of us, and perhaps I'm > > overreacting, but the tone of some of your recent posts seems a bit > > demanding. > > I apologize. I didn't think I was coming across demanding but I am > somewhat exasperated at some of these issues. I have a list owner who is > now going to get a moderated request notice everyday that he can't do > anything about it. > > But my question still remains: why is this option in Postorius when it > can't be handled properly? Surely the option can be easily removed, right? I added the option in my drive to expose every possible Mailinglist settings via Postorius and missed the fact that we weren't actually able to moderate those requests. Yes, this option can be hidden if it doesn't work until the next stable release. I hid one of the list settings in Postorius exactly because it didn't work, but this one slipped. > > Is the ability to list (via the pending moderation notices tab) and > handle (as in the List owner can decide a moderation response) an > unsubscribe moderation request there in Mailman core so that I can > properly address it via Affinity? Unfortunately no, there is a bug report open for it though and I have some done some analysis on root cause[1]. The bug turned out to be a more than a trivial one and I haven't been able to get to it yet. [1]: https://gitlab.com/mailman/mailman/-/issues/768 > > -- > > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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, Abhilash Raj (maxking)

4 years, 6 months

[MM3-users] Disabling Gravatar

by Marvin Gülker

Hi everyone, I want to make you aware of a potential privacy problem in Mailman's Hyperkitty. Under the upcoming EU General Data Protection Regulation (GDPR)[1], which will be in force as of 2018-05-25, it is illegal to transmit data to third parties without a right to do so. Without going into the details, the inclusion of third party services into one's website is usually deemed such a transmission, and unless one has explicit consent of the user (e.g., by an optional (!), unticked ticking box) this is normally illegal (if one targets EU users). The GDPR does not affect private and family use (Art. 2(2)(c) GDPR), but the exact reach of that clause is yet to be determined; it certainly does not exclude company use of Mailman. I've found it's possible to disable the social login providers quite easily (we had this discussion here on the mailinglist recently), but I don't see an option to disable Gravatar. If there is one, please enlighten me, but anyway I want to propose this as a feature request against Hyperkitty. A GDPR-compliant implementation of Gravatar in Mailman would look like this: * In order to not transmit website visitor's data (IP address, browser info, etc) to Gravatar, Hyperkitty has to request the avatar image itself and not leave that to the user's browsers to do. In other words, the HTTP GET request needs to come from the server running Hyperkitty and the user's browser then just requests the avatar from the Hyperkitty server. Most likely easiest way to do this is to pre-download the avatar when an email is archived. * In order to not transmit the subscribers' data (email address, allows Gravatar to track the subscriber) to Gravatar illegally, the retrieval of the avatar image from Gravatar has to be disabled by default. Instead, an option needs to be added to the subscriber's control panel which he has to actively enable in order to have his Gravatar downloaded and thus used (privacy-by-default rule). I'm not saying Gravatar tracks people and sells the information gathered, though I have doubts on how Automattic makes money with the service. I'm just outlining the legal duties under the upcoming GDPR for service owners, which are independant of how Automattic processes the data in this specific case. Please don't dismiss this as some side feature not needed. The fines that can be imposed on service owners due to violation of the GDPR are very high (up to 20,000,000 € [that's 20 million euros, really]). Marvin [1]: http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1510481733260&uri=CELEX:… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 5 months

[MM3-users] Re: Installation Questions [Installation}

by Odhiambo Washington

On Mon, Nov 4, 2024 at 12:36 PM Gerald Vogt <vogt(a)spamcop.net> wrote: > On 04.11.24 09:13, Odhiambo Washington via Mailman-users wrote: > > On Mon, Nov 4, 2024 at 10:34 AM Gerald Vogt <vogt(a)spamcop.net> wrote: > >> On your server it looks like this: > >> > >> # ls -la /etc/mailman3 > >> total 28 > >> drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . > >> drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. > >> -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf > >> -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg > >> -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg > >> -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py > >> > >> and it works just fine. > >> > > > > True, but making the mailman user own the files makes life easier when > you > > operate from the virtualenv - > > you do not have to exit the virtualenv to edit the files in > /etc/mailman3, > > and then re-enter the virtualenv. > > The virtualenv doesn't change the current uid. That doesn't make a > difference. > > > You do not have to give the mailman user sudoer rights. That's the whole > > point about the below: > > > > ``` > > sudo mkdir /etc/mailman3 > > sudo chown mailman:mailman /etc/mailman3 > > sudo chmod 755 /etc/mailman3 > > ``` > > Well, that essentially was my question: why does the mailman user > require sudo rights? Mark did not say that the mailman user required sudo access. Please re-read what he said. > Why does it need to be able to write or change > those files/directories? Except for the convenience which isn't a reason > to weaken security. > Make me understand how the security is weakened. The Mailman user account has no password so cannot login from outside. Even if it was able to login, it will still end up only accessing $home and /etc/mailman3, no? > In respect to security, i.e. separation of the service user from write > access to it's core configuration files, it should not be done unless > absolutely necessary. Sorry, I didn't understand that. -- 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]

5 months, 3 weeks

[MM3-users] Re: parallel processing of out queue messages

by Stephen J. Turnbull

Answering previous two messages in one reply. Dan Caballero writes: > Yesterday we processed just over 60,000 messages to > recipients. Some of our lists have 2000+ subscribers. > We currently run Mailman as a Docker container in AWS on a > t3.xlarge instance. > 4 CPU > 16GB RAM OK, so that's the same order of magnitude. Interesting that 4CPUs seems to be enough. > 90% of the time the system is handling incoming messages and the > backlog of .pck files in the out queue doesn't last more than 10-15 > minutes. Even if a single message may take longer to process others > move through via other runners. Right, but the thing is this is not a single-queue multiserver model. In queue theory terms, it's a queue-per-slice model. Load balancing is done by pseudorandomizing queue assignment. So if the head of the queue gets stuff, the whole slice is stuck, but the queue manager keeps adding to that slice. It does sound like you're not seeing the stalling problem we did. I wonder why not, it looks like you're using Postfix, too. > So is there a 1:1 relationship between the number of runners and > the maximum number of messages that may be processed with .bak > files in the out queue? I don't know about the relationship to the .bak files. I don't remember offhand how they get cleaned up. But runners handle only one message at a time. If you have 32 runners, there will be at most 32 messages being processed at a time. However, normally a runner can process several messages per second. So given 2 hours offline or whatever, 60k/12 = 5k messages would showing up at once. A single runner should be able to handle that in another two hours, so I think this indeed explained by outgoing gateway throttling. Again, Dan Caballero writes: > We relay the list messages through an external SMTP host. The > administrator tried increasing the limit on the number of client > connections as they had set it fairly low. > > smtpd_client_connection_count_limit Oops, forgot about this. My client on the large site had already tweaked that because they had that setting for the Mailman 2 site we were migrating. He mentioned it but it wasn't top of mind for me because I didn't have access to the SMTP gateway host. > They've increased the threshold and that seems to have helped as I > immediately saw an increasing both via lsof -i:25 and the number of > .bak files in the out queue directory. Yay! Regards, Steve

1 year, 6 months

[MM3-users] Re: Mailman3 on python3.13 debian testing package

by Thomas Krichel

Thomas Krichel writes > No email reaches the list. I did not notice, but now the listowner > has written to me. Here I try to document how I change from the mailman Debian package to the virtualenv. The change appears necessary because Debian testing's default python is 3.13 and Mailman is not ready for that. root@server:/usr/local# rm -rf mailman/ root@server:/usr/local# mkdir mailman root@server:/usr/local# cd mailman Not sure whether my default python3.13 can be used so I explicitly call python3.12 root@server:/usr/local/mailman# python3.12 -m venv venv source /usr/local/mailman/venv/bin/activate I used sqlite as the database, so I don't install psycopg2-binary (venv) root@server:/usr/local/mailman# pip install wheel mailman Now look at systemd root@server:/lib/systemd# find . -name *mailman* ./system/mailman3-web.service ./system/mailman3.service After examining mailman-web I guess it does not need changing. root@server:/lib/systemd# systemctl stop mailman3 root@server:/lib/systemd# systemctl disable mailman3 Synchronizing state of mailman3.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install disable mailman3 Removed '/etc/systemd/system/multi-user.target.wants/mailman3.service'. root@server:/lib/systemd/system# cp -a mailman3.service mailman3_debian.service Let's reference the the virtual environment's mailman root@server:/lib/systemd/system# diff mailman3.service mailman3_debian.service 12,14c12,14 < ExecStart=/usr/local/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg start --force < ExecReload=/usr/local/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg restart < ExecStop=/usr/local/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg stop --- > ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force > ExecReload=/usr/bin/mailman -C /etc/mailman3/mailman.cfg restart > ExecStop=/usr/bin/mailman -C /etc/mailman3/mailman.cfg stop root@server:/lib/systemd/system# systemctl enable mailman3.service Synchronizing state of mailman3.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable mailman3 root@server:/lib/systemd/system# systemctl start mailman3 Seems to start. A test mail to the list yields Feb 13 09:36:37 2025 (872373) Uncaught runner exception: No module named 'mailman_hyperkitty' Even though I did not see this at https://docs.mailman3.org/en/latest/install/virtualenv.html It looks like I need to get mailman_hyperkitty. root@server~# systemctl stop mailman3 root@server~# source /usr/local/mailman/venv/bin/activate (venv) root@server~# pip install mailman_hyperkitty root@server~# systemctl start mailman3 Now my test email seems to be starting to be delivered to the list. I am particularly grateful to Stephen J. Turnbull's contribution, especially when he wrote > (I think Debian puts mailman3 configs there and that's what we recommend) So in fact there is no need to fiddle with configs apart from the systemd file. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21804th day.

2 months, 2 weeks

[MM3-users] Re: mm3 installation question

by Mark Sapiro

On 3/6/24 1:33 AM, Odhiambo Washington wrote: > On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Odhiambo Washington writes: >> >> > The odd thing is that the HOWTO that he followed never involves the >> > manipulation of any urls.py at all - it's not even mentioned at any >> > point. So obviously the issue is caused by something else and I >> > suspect something within Apache needs to be re-evaluated in the >> > guide. The HOWTO installs mailman-web which contains a urls.py. >> >> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" >> URI paths. It is quite unclear to me how this works at all with >> either the >> >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> >> version of urls.py or the reverse order version >> >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), This is an issue with Django. I'm not sure of the exact mechanism, but consider the first of the above two sets. If you go to the mailman3/ URL that gets redirected to the postorius/ URL. I.e. two paths that ultimately reference the same thing wind up considering the second path as the canonical path and redirecting the first path to the second. I was not initially aware of this when I added the postorius/ and hyperkitty/ paths to mailman_web/urls.py. I did this with the intent of making either set of paths work, and I added those paths after the mailman3/ and archives/ paths, and this version got released as mailman-web 0.0.8. That caused the recommended Apache config to fail because now the mailman3/ and archives/ paths were redirected to the postorius/ and hyperkitty/ URLs which are not in the recommended Apache config. I have since reordered the paths in mailman_web/urls.py, but that version isn't yet released. Thus the issue. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for some background. > My thinking then is that the documentation at > https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration > needs to be fixed by adding the missing bits, What needs to be done is a mailmab-web 0.0.9 release in PyPI. This will fix the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 9:39 PM, Abhilash Raj wrote: > > On Wed, Oct 21, 2020, at 3:35 PM, Brian Carpenter wrote: >> On 10/21/20 5:39 PM, Mark Sapiro wrote: >>> On 10/21/20 12:14 PM, Brian Carpenter wrote: >>>> Well I can't dictate that to my list owners and there is no confirm >>>> token sent with the moderation notice. Why include this option in >>>> Postorius when it can't be properly handled? >>> Postorius is still a work in progress. The unsubscription policies are >>> in core and are exposed in Postorius. Certainly the ability to moderate >>> an unsubscription should be in Postorius, but it isn't yet. We are an >>> all volunteer project and there aren't that many of us, and perhaps I'm >>> overreacting, but the tone of some of your recent posts seems a bit >>> demanding. >> I apologize. I didn't think I was coming across demanding but I am >> somewhat exasperated at some of these issues. I have a list owner who is >> now going to get a moderated request notice everyday that he can't do >> anything about it. >> >> But my question still remains: why is this option in Postorius when it >> can't be handled properly? Surely the option can be easily removed, right? > I added the option in my drive to expose every possible Mailinglist settings via Postorius and missed the fact that we weren't actually able to moderate those requests. > > Yes, this option can be hidden if it doesn't work until the next stable release. I hid one of the list settings in Postorius exactly because it didn't work, but this one slipped. Thank you. I will go ahead and remove the option within Affinity. >> Is the ability to list (via the pending moderation notices tab) and >> handle (as in the List owner can decide a moderation response) an >> unsubscribe moderation request there in Mailman core so that I can >> properly address it via Affinity? > Unfortunately no, there is a bug report open for it though and I have some done some analysis on root cause[1]. The bug turned out to be a more than a trivial one and I haven't been able to get to it yet. > > [1]: https://gitlab.com/mailman/mailman/-/issues/768 > > This is good information to have at least so I appreciate letting me know. I probably need to spend more time looking through the outstanding issues for Mailman core and Postorius before launching a nuclear strike of epic and catastrophic proportions upon Mark. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] Re: Found error in docker-container

by Abhilash Raj

Hi Alex, On Mon, Jul 17, 2017, at 06:32 AM, Alexander Klotz wrote: > Hi, > > unfortunately I have to get back to this topic, since there's still a > problem. We already removed the comments as you suggested, but we still > have to make manual corrections when creating a new list, because the > alias information is safed incorrectly in the tables of the postfix > host. There is a port indication with a "]" in the comments, but it is > incomplete. The proper address has to be inserted here. Let me do some testing before I answer this, so I will get back to you with some better answers than "it should not be happening". > Regards, > Alex > > > > > On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote: > >> Hi, > >> > >> one of our developers wanted to point out an error he found in mailman > >> 3.1, docker container maxking/mailman-core-0.1 > >> > >> The entries in /opt/mailman/core/var/data/postfix_lmtp are not set > >> correctly, example: > >> > >> /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP > >> Address of mailman-core container]:8024 > >> > >> this actually should look like this: > >> > >> /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 > > > > > > Can you send a copy of your Mailman configuration that you added at > > `/opt/mailman/core/mailman-extra.cfg`? > > > > I think this is mostly because the configuration parser doesn't > > understand the in-line comments. So, if you are using the configuration > > exactly as it is mentioned in the documentation, it could be the cause > > of this problem. > > > > Solution to that would be to just remove all the in-line comments. > > > > [mta] > > incoming: mailman.mta.postfix.LMTP > > outgoing: mailman.mta.deliver.deliver > > lmtp_host: 172.19.199.2 # IP Address of mailman-core > > container > > lmtp_port: 8024 > > smtp_host: 172.19.199.1 # IP Address of host where > > postfix is. > > smtp_port: 25 > > configuration: /etc/postfix-mailman.cfg > > > > > > > > Like the two comments seen in the configuration above. > > > > I will update the documentation too so that others don't get caught in > > something like this. > > > > Thanks! > > > > > -- > Mit freundlichen Grüßen, > Alexander Klotz > > (redaktion kulturserver) > > mailto:alexk@kulturserver.de > > Stiftung kulturserver.de gGmbH > > Lothringerstraße 23 > D-52062 Aachen > http://ggmbh.kulturserver.de > > Geschäftsführer: Wolfgang Knauff > > Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 > Umsatzsteuer-Identifikations-Nr.:DE DE 230868040 -- thanks, Abhilash Raj

7 years, 9 months

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/14/19 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > On my server are several virtual hosts running with different lists per > host. The appropriate webaddress is in general: > https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. > My domains: > [domain-1] starts with a b* > [domain-2] starts with a s* > [domain-3] starts with a t* > > If I use the webadress > https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… > and I do a click on the https-symbol in the address line of my browser I > get the secury-information " every thing is ok" and the > certificate-information is about the wildcard-certificate I just created > for the right domain. > > Different result is for the webadress > https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. > In this case I get an information like "you are using a wrong > certificate" clicking on the https-symbol references tot he certificate > of [domain-1] > > I set in my apache2 configuration a symbolic link to apache.conf in the > /etc/mailman3/directory and made this active. > > What did I wrong?? Your Apache config needs to define separate a VirtualHost for each domain, either by IP address or ServerName, and each VirtualHost points to its own SSL certificates. > If I set use_https to yes in mailman.cfg I get on the website for all > lists: > > postorius: Something went wrong > Mailman REST API not available. Please start Mailman core. > > In the logs I found … ... > mailman-web.log > ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", > line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, > in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, > in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, > in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, > in connect > self.sock = self._context.wrap_socket(sock, server_hostname=self.host) > File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket > session=session > File "/usr/lib/python3.7/ssl.py", line 853, in _create > self.do_handshake() > File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake > self._sslobj.do_handshake() > ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number > (_ssl.c:1056) Does your setting in settings(_local).py for MAILMAN_REST_API_URL have an https scheme? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 09/28/2017 06:11 AM, Henrik Rasmussen wrote: > When held mails are released in Mailman (maybe also mails which are not held) they are sometimes not sent nor archived, as mentioned in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > One of my list admins reported that he released two mails on Sep 25 07:20:48 2017 UTC, and only the first was sent to the members. In the mailman.log I found the following from that particular release: > ... I will look at the above as time permits, but ... > Sep 27 13:23:02 2017 (32) Uncaught runner exception: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 358, in _handle_message > g.flatten(msg.get_payload(0), unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 189, in _write > msg.replace_header('content-transfer-encoding', munge_cte[0]) > File "/usr/local/lib/python3.6/email/message.py", line 558, in replace_header > raise KeyError(_name) > KeyError: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) SHUNTING: 1506518582.300981+aa68949ca566c7170a81a0bd643cee803f29c312 This one at least is a known issue. See <https://gitlab.com/mailman/mailman/issues/256>. As noted there, the underlying cause is <https://bugs.python.org/issue27321>, a bug in the Python email library (not yet fixed as of Python 3.6.2, but there are references to patches in the bug report). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, my first post was to optimistic - the user tested some other combinations and when he tries to send a signed HTML mail, the server again refuses to accept it with "Diagnostic-Code: smtp; 501 Message has defects". The user suggested that the problem is caused by a line containing only "-- " somewhere in the text, but I can not confirm this. Please find enclosed the refused mail (anonymized). Regards Rainer On Mi, 20 Apr 2022 10:51:38 +0200 Rainer Herbst <rainer.herbst(a)aip.de> wrote: > Dear all, > > as the original poster, I have asked the user to send a test mail >through our mailman3 system (docker image > maxking/mailman-core:0.4.2) and the mail passed. > > The user is now on Apple Mail 16, maybe that does the trick. Please >find enclosed the anonymizied mail source. > > Best regards and thanks for caring even if the problems seems to >affect only a small number of users! > Rainer > > On Fr, 15 Apr 2022 09:03:41 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: >> On 4/14/22 21:33, Stephen J. Turnbull wrote: >>> >>> Whether we *want* to do that depends on how much trouble that causes >>> for our main constituency (list and site admins), and whether we can >>> provide discoverable documentation of the problem. My take is that >>> this seems to be an extremely rare problem, and at least some MUAs >>>are >>> able to read the message, so we should let it through. >> >>First, we are not silently dropping this message. We are rejecting it >>at LMTP time so the sender should be notified. >> >> Then the broader question is should we accept all messages with >>defects, almost all of which are spam, or only certain defects and >>which ones. >> >> I note that Apple has now released Mail 16 so maybe they've fixed >>this. My macs are still on Big Sur, so I can't test 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/ >> > > Viele Grüße > > Rainer Herbst > Leiter IT-Service > Phone: +49 331 7499-257 > e-mail: rainer.herbst(a)aip.de > https://www.aip.de > > ----------------------------------------------------------------------------------------------- > Leibniz-Institut für Astrophysik Potsdam (AIP) > An der Sternwarte 16, 14482 Potsdam > > Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach > Stiftung bürgerlichen Rechts > Stiftungsverzeichnis Brandenburg: 26 742-00/7026 > ----------------------------------------------------------------------------------------------- Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 -----------------------------------------------------------------------------------------------

3 years

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

Allan Hansen writes: > If he/she has never created an account, then I see no problem > cleaning up the system when the user deletes the last subscription, Without an account (ie, a User object), the user can't authenticate themselves as owner of the subscription, and therefore can't delete any subscriptions. What scenario are you thinking of here?

4 years, 5 months

[MM3-users] Editing a Subscriber's Mailman 3 list Settings

by Terry Earley

Admin users can edit subscriber's Mailman list settings. Once that subscriber registers as a user, then only he/she can edit. Admin no longer has permission to change these settings. [image: editSubscriberByAdmin.gif] Terry Earley

3 years, 9 months

[MM3-users] 2 postfix instances and 1 mailman instance possible?

by charlie derr

Greetings, We will be (temporarily) splitting our single postfix instance and running two separate instances on our email server. Can we configure mailman to listen to one of them and send to the other? If so, please do direct us towards how we would go about configuring mailman to do this. versions: mailman: 2.1.15-30.el7_9.2 postfix: 2.10.1-9.el7 (both via rh/centos repo(s)) thanks so very much for any assistance/direction you're able to provide, ~c -- Charlie Derr Director of Instructional Technology Bard College at Simon's Rock https://simons-rock.edu Encryption key: http://hope.simons-rock.edu/~cderr/ 413-528-7344 Pronouns: he/him/his

2 years, 6 months

[MM3-users] Setting moderation_action when approving a message from a non-member fails

by Tom Smyth

Hello! When a message is held due to it being from a non-member, I notice that Mailman creates a non-member record for the sender automatically. This is great! But if I try to set their moderation action while approving the message in Postorius, I get: Failed to set moderation action: xxx(a)gmail.com is not a member address of xxx(a)xxx.org Is this expected? I would like to be able to set the moderation action for the non-member that has already been created. I am on Postorius v1.3.2. Thanks! -- Tom Smyth (he/him)

1 year, 10 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Tom Smyth

Reviving this super old thread b/c it has good Google page rank for "mailman 3 see bounce emails"... Could this please be added as a config option so we don't have to patch the server code? Seems like a very useful feature for debugging odd bounce behaviors such as I'm doing right now. Thanks for considering! -- Tom Smyth (he/him)

1 year, 9 months

[MM3-users] Viewing/editing bounce score/status in Postorius

by Tom Smyth

Is this possible? As of 1.3.2 I can't find it. Perhaps it's in a newer version? I'm working on upgrading. Thanks! -- Tom Smyth (he/him)

1 year, 9 months

[MM3-users] redirecting -bounces replies

by Hirayama, Pat

Greetings, Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? In Mailman2, I know that I could do that by modifying the aliases table. I've been poking around in Mailman3, but haven't managed to figure out which container I need to be looking at. And rather than keep spinning, I figured that I'd ask the hive mind, since I'm sure one of you can quickly point me to the correct location. Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

5 months, 3 weeks

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Cameron Smith

Mark, My apologies for not investigating more thoroughly before opening my mouth (so to speak). You are, of course, correct in your analysis of what happened to my emails, and this is not the first time that my email setup has caused me problems. I’ve added my alternate email address to my lists.mailman3.org user profile, so hopefully it won’t happen again. > On 2017.11.29, at 18:09 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/29/2017 05:05 PM, Cameron Smith wrote: >> >> On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. > > > Your post was received: > > Nov 21 14:31:20 mailman postfix/cleanup[15735]: 2B3798008D: > message-id=<836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > Nov 21 14:31:20 mailman postfix/qmgr[20545]: 2B3798008D: > from=<ccsmith(a)mail2.cetsi.com>, size=10048, nrcpt=1 (queue active) > > delivered to Mailman core: > > Nov 21 14:31:20 mailman postfix/lmtp[15737]: 2B3798008D: > to=<mailman-users(a)mailman3.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.31, delays=0.28/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) > > and immediately discarded: > > Nov 21 14:31:21 2017 (19106) DISCARD: > <836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > > >> Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. > > > Possibly you never received a list copy of his message because you were > directly addressed and your list option "Receive list copies (possible > duplicates)" is set to No. > > >> So, what’s going on? > > > As to why your post was discarded, unfortunately, the logs don't give > more info. There are a couple of possibilities. If your post contained > an attachment with Content=Type: application/subtype where sub-type > doesn't contain 'signature' it would have been discarded by a header > filter rule. Also it looks like you sent the message From: > <ccsmith(a)mail2.cetsi.com>. If that is not an address on your > <ccsmith(a)cetsi.com> account, it would have been discarded as a > non-member post. > > >> What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. > > > I see nothing so far to indicate anything at lists.mailman3.org is > broken in this respect. The only "unusual" thing is this is now a new > thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, > but presumably that is because your post was in reply to your earlier > post which wasn't archived. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Cameron Smith Nanaimo, BC tel:1.604.803.0051

7 years, 4 months

[MM3-users] Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > Mark Sapiro writes: > > > > Some of the `path` settings are probably not in the same order as > > > in that file. The > > > > > > ``` > > > path('mailman3/', include('postorius.urls')), > > > path('archives/', include('hyperkitty.urls')), > > > ``` > > > settings should come after the > > > ``` > > > path('postorius/', include('postorius.urls')), > > > path('hyperkitty/', include('hyperkitty.urls')), > > > ``` > > > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > > > order). Or you can just delete the 'postorius/' and 'hyperkitty/' > > > ones or you can add > > > ``` > > > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > > > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > > > ``` > > > to your Apache config. > > > The odd thing is that the HOWTO that he followed never involves the > > manipulation of any urls.py at all - it's not even mentioned at any > > point. So obviously the issue is caused by something else and I > > suspect something within Apache needs to be re-evaluated in the > > guide. > > I believe this is the Apache configuration the OP is using: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/admin" "http://127.0.0.1:8000/admin" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > </IfModule> > > Note that Apache doesn't know about the "/postorius" and "/hyperkitty" > URI paths. It is quite unclear to me how this works at all with > either the > > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > > version of urls.py or the reverse order version > > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > > I think Mark must have a configuration with > > ProxyPass "/" "http://127.0.0.1:8000/" > > in the Apache configuration in mind? Or an alias or rewrite rule. > Otherwise I don't see how "/postorius" and "/hyperkitty" paths ever > get transmitted to the WSGI server. > My thinking then is that the documentation at https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration needs to be fixed by adding the missing bits, or a urls.py be provided for inclusion in /etc/mailman3/ and which sysadmins can edit to their liking. For example, I'd prefer to have /mm3 instead of /mailman3 to save on transmitted bytes and not clog the Internet pipes :-) -- 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, 1 month

[MM3-users] Re: hello， Discussion on how to subscribe to themailing list

by 朱超

thank you for your reply 1. It is not the MTA that refuses to send emails because the recipient's mailbox is too long, but the MUA that refuses to send the email because the recipient's mailbox is too long. Of course, you can use the confirm $token message to dev-request@domain for confirmation. This is a comparison Troublesome process, by visiting https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token, but he reported 404. 2. It is recommended to modify postorius, in order to keep the logic function of the underlying mailman-core unchanged, and optimize postorius at the application layer to increase user experience; even if there is no mailman-web service or postorius service, mailman-core can still run normally. If you look at the separation of the application layer and the underlying software, I think it is possible From: Tom At 2023-01-17 19:44:20, "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: >朱超 writes: > > > Yes, You got it. It is too cumbersome to ask the user to write a > > reply email for email confirmation. > >Surely clicking on "reply" then "send" is not cumbersome (unless >there's a way to get rid of confirmation altogether). Your problem is >that some of your subscribers can't do that. > >I have not previously heard of a MTA that refuses to *send* mail >because the addressee's mailbox is too long. IIRC there's a limit of >256 characters on domains, but only the (long-obsolete) recommendation >that lines in the message be 998 bytes or less restricts the length of >the local-part. > >I don't really see a good reason to change this default because there >are a number of configurations where there is no web service >available. I suggest a partial remediation in the issue I just filed. >(I think dealing with the rest of the issue is a Simple Matter of >Programming, but the question of determining existence and status of >an appropriate web service is more complex so I did address that.) > > > Why do you need to modify the mailman-core service， > >I suggest we should modify the code of the postorius, > >We are not going to do that, because >1. Mailman provides no guarantee that any web service is present, and > we're not going to make changes that require one. >2. Mailman provids no guarantee that the web service is Postorius > even if there is one, and we are definitely not going to make > creating compatible implementations more annoying than necessary. > > > Currently I have achieved it this way。 > >We encourage you to use your code. ;-) But using it exclusively to >accomplish this change would go against several of our goals in term >of separation of concerns. If we can do it in an alternative way that >serves those goals, there's no point in complexifying Postorius in >this way as well. > >Regards, >Steve >_______________________________________________ >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 tom_toworld(a)163.com

2 years, 3 months

[MM3-users] Re: Changing subscription address

by Abhilash Raj

> On Mar 20, 2021, at 4:36 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Abhilash Raj writes: > >>> There does need to be a way to revert each option to inherit, and >>> there currently doesn't seem to be one. The 'Preferences' interface I >>> described in the previous post doesn't provide it either. I will >>> think about that. >> >> The implementation of this isn’t very difficult, but the UX of this is >> something I don’t know how to implement in that page to be very >> honest. > > Oh, I can play Liz Warren on that one! :-) "I have a plan for that." > >> We do already have ability to switch from an explicit address to Primary >> Address subscription. I would imagine it would be more than just a >> button, but more like a dropdown to choose an email or primary address >> and switch all subscriptions to that. > > Allan's situation is that for some reason he has a lot of users (or at > least suspects he does) who would be happy to have only one address > that there's only one place to change, but for some reason that > address is copied to (not inherited by) each of several subscriptions. This is a common situation actually, given that Postorius until recently only allowed subscribing individual addresses. Also, any subscriptions imported from Mailman 2.1 are also subscribed as address. > > We should address that, because I'm pretty sure his suspicion is > correct. For example, until I changed one of them -- and got two > emails about it for my discard pile :-) -- all of my python.org > Mailman 3 subscriptions were explicit. I still have about 8 to > go. :-) +1 >> This is how Core actually does work[1] if you subscribe via Email >> and you already have a primary address. It will lookup a user using >> the address and if the address is the primary address of the user, >> it will subscribe the primary address. > > If you say so, I guess it's true. Nevertheless, both Allan and I have > observed users with only one address, with that address subscribed > literally each time to several (~10) lists. Well a couple of stars have to align for it to work unfortunately. I realized that Core will use the primary address if you *already* have one set during email -join command processing. Add to that you can’t set an address as primary using just email commands, you end up with what you are seeing. Also, like I mentioned above, imported subscriptions are always address based. Another thing I thought I should clarify is that when I said subscribed via Primary Address in this or previous emails, I really meant that the User was subscribed and subscription inherits whatever the primary address of the user is. As opposed to explicit address itself (which could also be the email address currently set as primary address). > >> However, if it isn’t the primary address, and this is a new address, it will >> subscribe the address instead of user because the address isn’t >> verified at this point and hence can’t be a primary address. We could >> extend the subscription workflow to add an additional step to set this >> address as primary and subscribe the primary address. > > Yes, please, I think. Users who don't want this for subscriptions to > the primary address are going to be (rare) edge cases. If we need an > additional attribute on the user to handle the case of an unverified > primary address, I think that's an acceptable cost. Note that to > "claim" this User as her own, she has to verify that address. And if > she *can* verify that address, we can't stop her from doing so, we can > just make it more annoying. We don’t necessarily need the flag on user to set an unverified primary address, we might be able to get away without that. We could set the address as primary *after* we verify it. We always verify addresses regardless of the choice of the subscription mode (user or address). > >> Postorius has the full ability to define its own workflow because >> REST API provides full expression capability and doesn’t enforce >> anything. Previous versions didn’t had support for subscribing as >> Primary Address, but that has since changed and is the default one >> in the dropdown. >> >> This is for authenticated subscription, the anonymous subscribe works >> similar to email -join command. Mass-subscribe is probably working the >> same way. > > All of these should unify all subscriptions-by-this-address to one > User, in my opinion. +1 > >> Like mentioned above, it should be possible to do what you suggest. I >> am getting into the implementation details here, but the Subscription >> workflow would need an additional flag that would verify an address >> and use the flag to determine if it should subscribe the address or >> addresses’s user if an address is provided to the workflow. > > I don't think so. Just do the lookup, if it succeeds and matches > primary address, use inherit. If it doesn't succeed, create a User > and use inherit. If it does succeed, and doesn't match, use the > explicit address. Right now, P is explicit about it. You can choose if you want Primary Address or one of the explicit addresses added to your account. The primary address is the pre-selected choice, so if you go and just click on subscribe button, you get the primary address being subscribed. If you choose the explicit address then we subscribe the explicit address. Is that something you think needs modifying? The email join command does the first part you suggested, (if the lookup succeed and matches primary address, use inherit) but doesn’t do the second part (it will create a user, add the address to it and then use the address to subscribe). We can and should fix that. > It seems to me that this flag would be impractical for email > subscriptions (email commands with parameters are generally beyond the > kind of user this is most important for) or mass subscriptions (how > does the list owner know what the user wants?) anyway. If somebody > really wants all their subscriptions via primary address to be copies > of the primary address rather than user, I'm sorry, but they'll have > to deal with that. I can't imagine that it's the usual case, and > there's an easy workaround: make your primary address something other > than your usual subscription address! The flag I was talking was not really a user visible one but just thinking code flow. It might have to be a flag in API though to differentiate between the “verify this address and subscribe it” vs “verify this address, set it to primary and subscribe the User” cases. I agree that in situations where we just have an address to subscribe and no user exists, we create a user, add the address and verify and set it to primary and then use inherit. This should apply to, mass subscribe, anonymous subscribe and -join command. > If you disagree with me about the relative burden, then maybe we > shouldn't do this at all, but I'm pretty sure this is something we > should either do for all subscriptions, or for none. No, I think it shouldn’t be a big burden. > >> Primary Address is also an attribute of the Mailman User, so it >> should be possible for an admin to set that for a user if the user >> doesn’t have an account. When they sign up, they’d be able to >> manage and update accordingly. > > True, but AIUI Allan has a *lot* of users and on average they're > relatively needy compared to, say, my user population. The point of > his request is to smooth workflows for admins with user populations > where the admin *wants* to do many things for their users, or to have > smooth user workflows when they teach their users to do it for > themselves. That's why I'm focusing on the "I have one address and if > it changes I want to change it once" case. Makes sense. -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] Re: Only held_messages for 1 (of 3) list has "Mailman REST API not available" message.

by Duane Raymond

Thanks Mark. This sounds like a database problem. What's in Mailman > core's var/logs/mailman.log ? In the var/logs/mailman.log there was a permission error for the messages/ store folders. I noticed that some of the mm file and directories were owned by root vs 'mailman' user (what Brian uses when he set up the mm3 server). So after resetting all to mailman (I believe others use 'list') the error had changed (and other lists still seem to work fine). I checked the database, but wasn't sure what to look for. It is accessible and works for other lists on the same server. Now I get the error below with the error from mailman.log. I've already restarted nginx and mailman gunicorn qcluster on the server. Any further suggestions to resolve this? Anyone out there wish to take a look as paid work? Something went wrong HTTP Error 500: <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> [07/Jan/2022:12:39:11 +0000] "GET /3.1/lists/listname(a)mylist.com/requests HTTP/1.1" 200 26760 "-" "GNU Mailman REST client v3.3.2" [07/Jan/2022:12:39:11 +0000] "GET /3.1/lists/ listname.mylist.com/member/duane.raymond%40fairsay.com HTTP/1.1" 200 533 "-" "GNU Mailman REST client v3.3.2" [07/Jan/2022:12:39:11 +0000] "GET /3.1/users/daaca246222e4eb595db826e8af776c2 HTTP/1.1" 200 292 "-" "GNU Mailman REST client v3.3.2" [07/Jan/2022:12:39:11 +0000] "GET /3.1/users/daaca246222e4eb595db826e8af776c2/preferred_address HTTP/1.1" 200 425 "-" "GNU Mailman REST client v3.3.2" [07/Jan/2022:12:39:11 +0000] "GET /3.1/lists/ listname(a)mylist.com/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [07/Jan/2022:12:39:11 +0000] "GET /3.1/lists/listname(a)mylist.com/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [07/Jan/2022:12:39:13 +0000] "GET /3.1/lists/listname.mylist.com HTTP/1.1" 200 438 "-" "GNU Mailman REST client v3.3.2" [07/Jan/2022:12:39:13 +0000] "GET /3.1/lists/ listname(a)mylist.com/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.2" [2022-01-07 12:39:13 +0000] [32130] [ERROR] Error handling request /3.1/lists/listname(a)mylist.com/held?count=10&page=1 Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 134, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 175, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/post_moderation.py", line 174, in on_get resource = self._make_collection(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/helpers.py", line 182, in _make_collection entries = [as_dict(resource) for resource in collection] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> entries = [as_dict(resource) for resource in collection] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/post_moderation.py", line 164, in _resource_as_dict resource = self._make_resource(request.id) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/post_moderation.py", line 77, in _make_resource resource['msg'] = msg.as_string() AttributeError: 'NoneType' object has no attribute 'as_string' [07/Jan/2022:12:39:13 +0000] "GET /3.1/lists/ listname(a)mylist.com/held?count=10&page=1 HTTP/1.1" 500 0 "-" "-"

3 years, 3 months

[MM3-users] Re: Editing a Subscriber's Mailman 3 list Settings

by Mark Sapiro

On 7/1/21 11:08 AM, Terry Earley wrote: > Admin users can edit subscriber's Mailman list settings. Once that > subscriber registers as a user, then only he/she can edit. Admin no longer > has permission to change these settings. > [image: editSubscriberByAdmin.gif] The image removed by this list's content filtering was a partial screenshot of a Postorius member options page with the error message "Cannot convert parameters: acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings" What Postorius version is this? I am unable to duplicate this either as a site admin or a non-site-admin list owner with Postorius from the head of the gitlab branch (1.3.5b1). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Search results for query "He"