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

[MM3-users] Re: Which documentation to follow for installation

by Abhilash Raj

On Fri, 18 Aug 2017 09:40:37 -0000 ribanez(a)sciops.esa.int wrote: > Hi everyone, > > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to > look for documentation. I found two different sites: > > https://mailman.readthedocs.io/en/latest/ > http://docs.mailman3.org/en/latest/ Both of the above are actually latest documentation, docs.mailman3.org should be the one to look for installations guidelines for the entire Mailman 3.x Suite, mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles the mail. http://docs.mailman3.org/en/latest/prodsetup.html This should be the best place to start, be sure to look at the Pre-Installation Guide if you are new to the Python ecosystem. > > Do you know which one should be followed? Both at the same time? I find it > quite unclear... and this installation will be for an operational environment. > > Also, there are some (official?...) docker images, but all images are for > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. It is meant for Mailman 3.X series and is maintained by me. It currently includes the latest releases for all the Mailman's sub-projects, also Mailman 3.1. Hope that helps! -- thanks, Abhilash Raj

8 years, 2 months

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Mark Sapiro a écrit le 15/06/2020 à 21:58 : > On 6/15/20 12:37 PM, Gilles Filippini wrote: >> >> There are 4 emails stored into this folder. 3 of them are spam, and the >> last one is a legitimate email. This is annoying that such emails could >> accumulate and stay into var/archives/hyperkitty/spool/ forever, causing >> more and more hyperkitty errors. >> >> Any idea how to make their processing more error proof? > > > Change the offending .encode() method to add errors='replace'. > > The traceback from the error should tell you where it is. > > You could also open an issue at > <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If > you do that, please include an error traceback if possible. If there is > not a traceback in mailman.log associated with the error, there might be > one in HyperKitty's log (configured in Django's settings). Also, > including enough of a message to duplicate the issue is very helpful. I've now deleted the offending messages. Will open an issue with related details the next time this error occurs. Thanks a lot, _g.

5 years, 4 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/ >

4 years, 1 month

[MM3-users] Re: Moderation request email from a non existing user

by Mark Sapiro

On 6/1/22 00:45, David Lopez via Mailman-users wrote: > I'm on postorius 1.3.4 so I tried to do via shell but after logging it shows a syntax error. > > mailman shell -l mylist@mydomain(dot)com > pendingsdb = getUtility(IPendings) >>>> for token, data in pendingsdb.find(m, pend_type='unsubscription'): > ... ... if data['token_owner'] == 'moderator': > File "<console>", line 2 > ... if data['token_owner'] == 'moderator': > ^ > IndentationError: expected an indented block >>>> ... pendingsdb.confirm(token) > File "<console>", line 1 > ... pendingsdb.confirm(token) You are entering the `... ` prompts that I showed in my example. You show ``` ... ... if data['token_owner'] == 'moderator': ``` the first `... ` is the actual prompt from mailman shell. The second `... ` is the prompt from my example which you shouldn't enter. You should only be entering ``` pendingsdb = getUtility(IPendings) for token, data in pendingsdb.find(m, pend_type='unsubscription'): if data['token_owner'] == 'moderator': pendingsdb.confirm(token) commit() ``` Indentation is important. After `pendingsdb.confirm(token)` enter an empty line at the last `... ` prompt. -- 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] How to enable VERP?

by Andy Smith

Hi, I'm a little confused as to how to enable VERP. mailman3 Debian package, version 3.3.3-1, using Exim 4 MTA. In /etc/mailman3/mailman.cfg I added: [mailman] … verp_delivery_interval: 1 verp_probes: yes and restarted mailman3.service. The list's "Alter Messages / Personalize" setting is "Individual" (but I tried "Full" as well and saw no difference in VERP behaviour). I can see the MTA is doing an individual delivery for each recipient, and the list's custom footer tells the recipient which address they are subscribed under, so I know that part is working. With VERP enabled I was expecting the Return-Path header in the delivered list mail to include a cookie to identify the individual subscriber, but instead it is "listname-bounces(a)example.com" like always. In mailman.cfg my MTA-related settings are: [mta] incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.exim4 And the Exim configuration itself has ther macros, router and transport files from the "Exim" section of here: https://docs.mailman3.org/en/latest/config-core.html#configuring-mta edited only for correct paths. That's been working for months for delivering list email in and out, but I'm just now trying to enable VERP and it's not happening. Is there something I'm missing? Thanks, Andy

3 years

[MM3-users] Re: mailman3 3.2.2 python3.8 problem on focal

by Thomas Stein

Answering my own post for now. Replacing time.clock() with time.process_time() in /usr/lib/python3/dist-packages/mailman/utilities/uid.py seems to fix the current issue for me. Don't know what else I broke with it though. :) cheers! t. Am 2024-03-20 12:54, schrieb Thomas Stein: > Hello list! > > I saw a few posts regarding the "Uncaught runner exception: module > 'time' has no attribute 'clock'" problem but no solution to that. It > seems this issue sneaked in at some point. I was getting aware of it > when suddenly notifications to non-member posts did not work anymore. > Everything else seems still to work. > > So, what is the prefered solution here? Is it possible to "repair" > focal? There is python2.7, python3.6 and python3.8 installed currently. > Or do I need to switch to a supported distribution like debian > something? Wait for ubuntu 24.04? > > Any hints are really appreciated. > cheers! t. > _______________________________________________ > 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 himbeere(a)meine-oma.de

1 year, 7 months

[MM3-users] Re: Welcome message template errors

by Mark

>> On 2024-04-23 11:33, Mark Sapiro wrote: >> That URI should have been; >> >> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… > I think you are saying the what you reported originally was not > correct and the URL in the template table was in fact the latter URL. I meant when I typed the URL in my first email I had unintentionally omitted the name of the list (mytestlist) when I redacted the real domain name to 'lists.mydomain.com'. ...emplates/list/lists.mydomain.com/list:user:noti... I should have written ...emplates/list/mytestlist.lists.mydomain.com/list:user:noti... >> If I go to the above URL, the text of the list's Custom welcome >> message displays on an otherwise empty webpage. > > > And that's what is expected. So you can go to that URL and get the > template, but when Mailman Core tries to do the same thing, it gets a > timeout. Is there some firewall or other security software blocking > this access? #ufw disable Firewall stopped and disabled on system startup Then restarted everything... # ufw status verbose Status: inactive And still getting the error in the Postorius webpage ... HTTP Error 400: HTTPSConnectionPool(host='lists.mydomain.com', port=443): Read timed out. (read timeout=5)

1 year, 6 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

Now I'm on one of the lists in digest mode and I can see that it's a mess. Periodic digests are definitely NOT working, so I'll lay that out here. root@host2:/# cat /etc/cron.d/mailman # This goes in /etc/cron.d/mailman # Replace "apache" by your webserver user ("www-data" on Debian systems) and # set the path to the Django project directory 0 23 * * * lists /usr/local/bin/mailman digests --periodic 0 23 * * * lists /usr/local/bin/mailman notify root@host2:/# grep digests /var/log/cron.log Jun 11 23:00:01 host2 CRON[1632765]: (lists) CMD (/usr/local/bin/mailman digests --periodic) Jun 12 23:00:01 host2 CRON[2177286]: (lists) CMD (/usr/local/bin/mailman digests --periodic) root@host2:/home/members/directory# su - lists lists@host2:~$ /usr/local/bin/mailman digests --periodic lists@host2:~$ ls var/lists/<list>/ digest.mmdf In this case I've got /usr/local/bin/mailman as a symlink to the mailman binary inside the venv's bin directory, just for simplicity. That digest.mmdf file is dated June 9th and clearly ought to have been cleared out on any of the nightly runs between then and today but has not. There are no errors anywhere I can find. How can I try and track this down? -Joel On 6/4/2023 10:15 PM, Joel Lord wrote: > The May 4th digest that went out was _also_ size-triggered, so this may > have nothing to do with periodic digests at all, and possibly my > periodic digests aren't working. I'm not on any of my own lists in > digest mode, I'm slowly extracting diagnostic information out of people > who are. Also, since this is a ~2 month cycle, it's really difficult to > get data points to work with. I'll need to remember to go in and look > when this settles down again (new cycle of activity started last night) > to see if there's anything left pending. > > (venv) root@host2:/home/lists/mailman/venv/bin# pip freeze | grep -i hyper > HyperKitty==1.3.7 > > On 6/4/2023 10:05 PM, Mark Sapiro wrote: >> On 6/4/23 18:35, Joel Lord wrote: >>> >>> The periodic digests do seem to be coming out. I also now have >>> confirmation that the one message in this morning's digest that was >>> from May 4th was also included in the last digest back on May 4th, so >>> it seems that the one message was left behind in the digest queue >>> when the periodic digest was sent. >> >> I don't see how that can happen. The process that sends a digest >> renames the var/lists/<list-id>/digest.mmdf mailbox file in which the >> messages are accumulated to >> var/lists/<list-id>/digest.<volume>.<issue>.mmdf, where <volume> and >> <issue> are the volume and issue numbers of that digest, and then >> queues a message in the `digest` queue to tell the digest runner to >> create the digest from the messages in that mbox and send it. Thus, it >> leaves no var/lists/<list-id>/digest.mmdf mailbox file behind and that >> is created anew when the next post arrives. Further, if there is a >> non-empty digest.mmdf file, its messages should be sent no later than >> the next 11 PM `cron digests`. >> >> >>> There was one earlier message to the list back on May 4th, before the >>> one that got duplicated, but I can't tell if that triggered a >>> size-based digest to be sent: the logs aren't clear enough on that >>> detail for me to tell > >> >> OK >> >> >>> Just to inform things: >>> >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman >>> django-mailman3==1.3.9 >>> mailman==3.3.8 >>> mailman-hyperkitty==1.2.1 >>> mailman-web==0.0.6 >>> mailmanclient==3.3.5 >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper >>> mailman-hyperkitty==1.2.1 >> >> Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is >> up to date as are the others. >> >>> (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post >>> postorius==1.3.8 >>> >>> >> > -- Joel Lord

2 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Nice you opened a new issue, ok then... About this: Ideally, you want to use paths.fhs which is based on Filesystem Hierarchy Standard . To use this add the following to your configuration: [mailman] layout: fhs Should I do it???? is that for production?? Sometimes I wish the install process was easier, sorry for disturbing you guys but believe me I've been more than 2 weeks trying and it's been difficult El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 10:29 AM, Rafael Mora wrote: > > Can we modify the docs? > > > > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > >> > >> However, that said, the doc is wrong. The lines should be added to > >> main.cf, not master.cf. See > >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. > > > That's what the above issue and associated MR are for. > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

[MM3-users] Change settings via mailman shell

by kk＠eco.cept.org

I am trying to find a way to set some parameters on the lists from a shell script. One specific parameter - max_message_size is not presented through the REST interface apparantly, and i found a way to set this with mailman shell command. Continuing this path i seem not to be able to set any other parameters like this: m.archive_policy = 'never' m.subject_prefix = '' m.dmarc_mitigate_action = 'munge_from' m.dmarc_mitigate_unconditionally = True commit() However i end up with this error: sqlalchemy.exc.StatementError: (builtins.AttributeError) 'str' object has no attribute 'value' [SQL: 'UPDATE mailinglist SET archive_policy=?, dmarc_mitigate_action=?, dmarc_mitigate_unconditionally=?, subject_prefix=? WHERE mailinglist.id = ?'] [parameters: [{'dmarc_mitigate_unconditionally': 'True', 'dmarc_mitigate_action': 'munge_from', 'subject_prefix': '', 'archive_policy': 'never', 'mailinglist_id': 65}]] Not sure what to make of it, but it seems like the fields are not there. I then proceed to get a list of all parameters with information found here: http://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclient… and the parameters seems to exist - however this list is made with the REST interface - so my question are - are there a difference in parameters in "mailman shell" command and REST interface - and how do i then get a list of parameter and possible settings in the "mailman shell" command ? Thanks in advance Kenneth Denmark

6 years, 7 months

[MM3-users] Current status and issue deleting Archives in Mailman3

by bob B

So just want to make sure I have the latest information after searching this list and googling or have I missed something? It appears there is no way in mailman3 to delete archives. There has been discussion on implementing this, but it has not been developed? is that correct? I saw references to: >>> from hyperkitty.models import MailingList >>> ml = MailingList.objects.get(name="test2(a)freeculture.org") >>> ml.delete() But how do I run this? I believe it is run in mailman-core (I am in a docker environment but that should not matter). I can get into the mailman shell, but that command does not work I did the following: bash-5.0# 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. >>> from hyperkitty.models import MailingList Traceback (most recent call last): File "<console>", line 1, in <module> ModuleNotFoundError: No module named 'hyperkitty' >>> What am I missing? ************** Question 2 What about pruning archives? I use to run a script for mailman2 to prune archives of messages older than X days for a list, Is that possible in mailman3

4 years

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Mark Sapiro

On 6/10/25 09:40, Dan Caballero wrote: > > I've done some testing and this is close to what we need. However, I seem to be having an issue with the option for "Explicit Reply-to set; no Cc added". The messages are still including a Cc field with the sender's email. Is there another setting that affects the Cc field? The difference between "Explicit Reply-to header set" and "Explicit Reply-to set; no Cc added" only affects lists with Personalize = Full. For those cases, the To: in delivered posts is replaced with the recipient's address which means in some cases, the list's posting address is not exposed so we put it in Cc: unless Reply goes to list is "Explicit Reply-to set; no Cc added". This setting is intended for announce type lists where members normally do not post to the list. If DMARC mitigations are applied and Reply goes to list is anything other than No Munging, the original From: will always be added to Cc:. There is no setting to avoid this. This is so reply-all will include the original sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/19/20 11:32 PM, Mark Sapiro wrote: > 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. Mailman 2 made this so easy and Mailman 3 made it impossible. I >> will let someone else file the bug report. You don't really think that >> this is an issue which means it will be years before it is addressed. So >> I will save me some time. I will learn to live with it. > > I didn't say I didn't think it was a real issue. I mostly questioned > whether a new subscription should change an existing display_name. I > agree that there should be a way for a user to change the display_name > associated with her address. I'm not so sure about a list admin. Respectively, I think you are asking the wrong question here. The real question is why isn't a display_name being removed when a list subscriber is unsubscribed. Also list members being forced into a powerless role by Mailman 3's architecture have no way of changing a name except through a list owner unless they register an account but then again, *even that doesn't allow them to change their display name*. There are also other use cases in which a list owner will want to identify portions of their membership roster through the use of the display_name. Most list members interact with a Mailing list program via email. I know you understand that. However it is List owners that are the "real" power users of Mailman and so the admin interface should be designed in such a way that empowers List owners. Taking the ability away from List owners (and List members to make), what should be a simple name change, weakens them. > And in any case, I'm only one person. I'm not the only one deciding > what's important and what's not. I only decide what I want to work on, > not what anyone else thinks is important or wants to work on, so even if > I think something is not worth doing, that doesn't mean it won't get > done, and once again for emphasis, I do thing a user should be able to > change the display name associated with her address(es). Again I think we are missing something here from this conversation: data is not being removed. A list subscriber being removed (unsubscribed) should have their information totally removed. It is not. I now have one list owner who realizes this and it is not good. How does this not violate GDPR? This is why I think all the mailman developers ought to make this issue a high priority. It is creepy to see a name returned out of nowhere when someone resubscribes to a list without associating a name with a second resubscribing. I think this puts List owners at a disadvantage. > > Mailman 3 is totally different from Mailman 2.1 in this respect. Mailman > 2.1 had no concept of user. All it knew was addresses subscribed to > lists and an address subscribed to one list had no connection to the > same address subscribed to another list or being an owner or moderator > of a list. I think this should still be the case for non-registered list members. List owners/moderators are different. They HAVE to be registered users of Postorius/Affinity in order to manage/moderate a list. I wonder what the majority of list members' scenarios are. Is the majority scenario in play today the one where most list members are only subscribed to a single list on a single mailman instance? Or is it the scenario that is in majority use the one where a single list member is subscribed to multiple lists? I think that it is important to find out because it should govern the development process to a certain degree. This single approach of having registered user account with multiple associated email accounts elevates one scenario at the expense of the other. It also assumes/requires that list members have a registered user account and I can tell you from my experience that is not going to happen. The majority of mailman 2 users will not registered with a Mailman 3 admin interface. Some will of course, the majority will not. Maybe the behavior should and will change but it will take years for that to happen. So what I am challenging and questioning here is the approach where such assumptions are being made already that results in the weakening of list owners. > > Mailman 3 does have a concept of user and addresses belonging to a user. > This complicates things in some ways. In Mailman 2.1 we could have "The > Boss <user(a)example.com" as a member of one list and "Just a Peon > <user(a)example.com>" as a member of another list. In Mailman 3 that is > not possible unless the addresses are tweaked in some way to make them > different. Perhaps there is a better approach here to handle single member w/multiple subscriptions that doesn't hurt the ability of List owners to serve the needs of list members who do not have a registered user account and prevents the removal of data when a SINGLE user unsubscribes from a list. > > You don't seem to be concerned about the case where I subscribe to a > second list with a different display name and am surprised to find my > display name changed on the first list, but it's something that I have > to consider. I am not concerned because I think such cases are in the extreme minority. Are you saying that people are now going to be using different real names associated with their other subscriptions as well and that is going to be so needed it warrants this complex system that you have come up with? If someone whats to have a different name associated with a different subscription/email address then I am going to tell them create a new user account and use a good password management program to keep track of their logins. Right now I think this minority use case scenario is negatively impacting other administrative tasks of Mailman, particularly in the removal of user data when someone unsubscribes from a list. Its the use of a square peg being forced into a round hole. Except in this case most of the holes are round but by golly, we are going to use that square peg regardless! > > As far as filing or not filing an issue, issues in the GitLab trackers > are how we track these things. Threads on mailing lists are appropriate > for discussion of issues, but if something is going to get changed or > fixed, an issue in the tracker is the way to ensure it doesn't get put > aside and forgotten. If this is as important to you as it seems to be, > please file the issue. I will but what is disturbing is that you don't think that the non-removal of user data in cases of unsubscribing is not important or even an issue. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Re: Mailman3 on FreeBSD

by Barry Warsaw

Thanks for the reference John, > On Aug 13, 2017, at 06:52, John Poltorak <karotlopj(a)gmail.com> wrote: > > Regarding location of mailman.cfg...FreeBSD adopt a strict directory > hierachy > > https://www.freebsd.org/cgi/man.cgi?hier(7) > > Anything installed outside the base OS belongs in /usr/local I looked over that page. Does this mean that even if you were to install Mailman 3 via the FreeBSD package manager (i.e. ports), you’d still want mailman.cfg in /usr/local/etc instead of /etc? That would differ from most Linux distributions where package manager installed packages would have their configuration files in /etc, and where “third party” packages would have them in /usr/local/etc. > I guess that issue is something for the FreeBSD porters of Mailman3… I think so. I think for now I don’t want to support /usr/local/etc/mailman.cfg out of the box, although I’m open to persuasion if there are some more generic use cases. OTOH, the internal function that calculates the search paths could be refactored to make it easy for distributions to carry small deltas to add that as a search path (it really wouldn’t be that hard to do now, but it’s a little icky). Of course, you can’t add a configuration file to find a configuration file. :) Cheers, -Barry

8 years, 2 months

[MM3-users] Re: Postorius performance with over 1000 pending users

by Nick W

On 06/08/19 at 12:13, Nick W <mail(a)nickwynja.com> wrote: > Could it be that these requests are being submitted through Postorius? I'd > assume there would be some sort of honeypot input to prevent abuse. I'll > continue investigating and follow up with any insight I can on the cause of The > Problem. Some follow up here: cat /var/log/nginx/access.log | grep "POST /postorius/lists/mylist.exmple.com/" shows only a recent manual attempt I made to subscribe but not much else, which leads me to believe these requests aren't coming through Postorius. Now the more embarrassing part. The likely culprit is my stupidity. In an attempt to have subscription forms embedded on my static websites, I created this flask app to handle POSTs and subscribe people the the specified lists. https://github.com/nickwynja/fmmss/ I included a menial honeypot feature to handle spam requests, which I thought was working. It must not be but it appeared like it was, likely because I made the honeypot for my app at the same time I changed the subscription policy to 'confirm' and upgraded from Postorius 1.2.3 (when pending user subscriptions were no longer shown). Seems like I have some homework to do to prevent spam subscriptions through my app.

6 years, 4 months

[MM3-users] Re: Gmail problems?

by Odhiambo Washington

On Sat, Apr 22, 2023 at 6:03 PM Stephen Daniel <swd(a)pobox.com> wrote: > Mailman Gurus -- > > I run a number of small lists for my neighborhood association. The largest > of these is ~120 users. Typical volumes are about 2 messages/day. > > In the past week or so a number of users who use gmail as their email > client have complained that list emails have been going to spam or > "promotions" folders. I've always had 1 or 2 users who had trouble > receiving mails, but this seems to be a significant percentage of all gmail > users. > > I have DMARC mitigation set to unconditional, and the DMARC action set to > "Replace From: with list address". > > My emails are sent using google workspace as my SMTP relay. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Does the above mean that your MM3 instance uses Google Workspace to relay the e-mails to subscribers? If that is the case, then I do not see how Gmail would put perfectly authenticated email in spam/promotion folders, unless something is not quite right with the content of those emails. -- 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]

2 years, 6 months

[MM3-users] How to fix: [Django] ERROR (EXTERNAL IP)

by Jigme Datse

This feels like something that I should have working. I know I've not been attending to things all that well, so the thing that has happened, that's got us from, "possibly doing nothing," to throwing this error is that I went to update my mail server, and in the update, Mailman3 stopped working entirely (it was a variety of things), but now it's launching, and will load the main web interface... but Going to any of the list pages, gives the above Error. Well, not exactly the above error, Django is in square brackets. OK, that will work better for me with the how to fix. How to fix, probably isn't quite what I'm looking for, it's how to diagnose. The error tells me that the IP address is 127.0.0.1 and that 127.0.0.1 is in the ALLOWED_HOSTS. I *mostly* see this coming from Google, but when I go and look at the webpage, I get: normal page at /mailman3/lists/ But my lists, all give me... Something went wrong HTTP error 500: {"title": "500 Internal Server Error"} I've tried to figure out where to go from here, and right now I'm not making any progress, so I thought I'd ask here.

1 year

[MM3-users] Re: Sendgrid experiences (now Office 365)

by Stephen Daniel

I am running mailman3 in google's cloud. I have a google workspace account with a single authorized user. ($8/month) I use those account credentials and have mailman3 using google's smtp servers as the outbound relay. Works OK. There are still some members of my organization who don't receive list emails, for reasons I've never been able to debug. On Sun, Sep 28, 2025 at 7:43 AM <tom(a)tomsmyth.ca> wrote: > Reviving this old thread... > > Are folks still using Google Workspace or Sendgrid for Mailman? > > For Sendgrid, don't all sending addresses have to be verified? How do you > get around that? Surely you don't have all list members go through the > verification process? > > Does Google not have this restriction? > > Or am I missing something about how this works? Are people just having all > list emails come from the list email address and using the Reply To header > or something? > _______________________________________________ > 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 swd(a)pobox.com >

1 month, 1 week

[MM3-users] OS update 18.04 -> 20.04 with Python 3.6 -> 3.8

by Torge Riedel

Hi, just want to report that updating my server's OS from Ubuntu 18.04 to 20.04 including an upgrade from Python 3.6 to 3.8 worked 75% on the mailman3 installation. Stopping and disabling the service before prevented most of the problems, but I forget to disable the cron jobs. **sigh** So whenever you have to upgrade your OS including python, don't forget the cron jobs. After OS upgrade I renamed both "venv" directories and rebuild them from my notes. Worked. Starting up mailman-core was easy. Getting mailman-web back to work was a little tricky: 1. After rebuild I forgot to run the post-update script, overseen that in my notes. **sigh #2** 2. My uwsgi-emperor was totally confused and needed some guidance and manual remove of .sock file 3. Finally I got this in the logs: /opt/mailman/web/venv/lib/python3.8/site-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. Seehttps://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( I checked the reference file from here: |https://gitlab.com/mailman/mailman-suite/raw/master/mailman-suite_project/settings.py?inline=false| and it misses the "retry" value. After adding it to Q_CLUSTER everything works fine. Kind regards Torge

4 years, 4 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/18/22 08:43, gordon(a)dickens.com wrote: > > My only remaining problem is that I cannot access the individual mailing lists. That is, when I navigate a list and click on the list name then my browser displays: > > "Server error > An error occurred while processing your request." > > Concurrent with the above browser display, mailman3 sends an email to the system admin with the subject: > > "[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/list_local_name.domain.tld" > > This email and my logs now complain about: > > "Internal Server Error: /mailman3/lists/list_local_name.domain.tld/ > MultipleObjectsReturned at /mailman3/lists/list_local_name.domain.tld/ > get() returned more than one EmailAddress -- it returned 3!" > > Also, I get the same errors after I create a new mailing list as well. > > I hope that Mark and/or somebody here can offer up suggestions on what I need to do to fix this. Any suggestions would be very much appreciated! It seems like a database issue. I would like to help. What is the Traceback from that error? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/23/24 14:59, Mark wrote: > > The welcome message is returned. > > root@hel:~# sudo -u mailman curl > https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… > Test Welcome message for new subscribers.root@hel:~# I don't know what the issue is. curl, running as user mailman, is able to get the url, but Mailman core, presumably running as user mailman, times out trying to get the url. I can't explain why. Try the following in `mailman shell` running as user mailman ``` (venv) $ 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. >>> import requests >>> r = requests.get( ... 'https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD…', ... timeout=5) >>> t.text ``` Note the URL above is all on one line. This is exactly what Mailman core is doing to get the template assuming the `uri` in the template` table entry is the argument of the requests.get(). If this times out, try increasing the timeout= value. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Stephen J. Turnbull

Barry Warsaw writes: > >I can also work on Postorius. Also in this vein I have a question. > >Should the DMARC settings be added to the Alter Messages tab in the List > >Settings view or would it be better to have a separate DMARC Mitigations > >tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I would find it more natural to have "Posting Policy" (which would include posting filters on size and list membership, as well as message alterations such as removing .exe files and enforcing plain text by removing or rendering HTML parts), and "Malware Mitigation", which would include IP, domain, and mailbox filters as well as DMARC. I think DMARC mitigation is probably too special to deserve its own tab. Probably this is way too much reorganization to do at this point, but I'd like to keep this point in mind. We are already getting reports that configuration options are hard to find just because it's different from Mailman 2. I suspect that the REST API is sufficiently flexible and regular that we'll be tempted to proliferate options, so let's try to keep them organized. Steve

8 years, 10 months

[MM3-users] Re: mailman-web: ResponseNotReady

by Dmitry Makovey

On 10/18/2017 01:41 PM, Abhilash Raj wrote: > Hi, > > $ docker-compose rm -f mailman-web > $ docker-compose up -d mailman-web > > This will basically create a new container for Mailman-web, but, since > the state of mailman-web is stored completely in database (database > container), I am not sure how to reset *just* mailman-web without > dropping mailman-core related tables too (they share the same database > but have their own separate tables). The above command will get you a > fresh copy of code running. > > You can potentially get the list of tables and drop them, or maybe > Diango has some way to reset it's state from Django shell (python > manage.py <http://manage.py> shell, from inside mailman-web will get you > shell). I may have to look it up. > > Also, just by looking at the traceback, I am not sure about the exact > error. I may have to debug more to arrive at a better conclusion, which > I won't able to do until after this weekend. thanks for the suggestions. I'll try to dig in direction outlined by you, may end up producing some code to automate such task in the future :) -- Sr System and DevOps Engineer SoM IRT

8 years

[MM3-users] Re: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > 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/ >

7 years, 6 months

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/24/19 4:53 AM, Franklin Weng wrote: > > Thanks for your help. I did what you said above, but then I still got the > same result even after restarting mailman3 services. > > ~# mailman shell -l zh-l10n.lists.linux.org.tw > Welcome to the GNU Mailman shell > The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list >>>> m.preferred_language > <Language [zh_TW] Chinese (Taiwan)> >>>> quit() The issue is the list welcome message is sent in the character set of the new member's preferred language and if that is not set in the subscription request, and it's not possible to do that in Postorius, it defaults to the installation's preferred language. It should probably default to the list's preferred language. See <https://gitlab.com/mailman/mailman/issues/608> You have two choices: You can set the installation's default language by putting [mailman] default_language: zh_TW in your mailman.cfg, or you can leave the default language English and set the character set for English to utf-8 by putting [language.en] charset: utf-8 in your mailman.cfg. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

Mailman3 users -- I am in the process of migrating a set of mailing lists from a very old privately operated server running mailman2 to a VM in Google's cloud (GCP) running mailman3. I have mailman3 up and running in GCP. However, VM's in GCP are not permitted to send emails. To work around this I configured postfix relay SMTP traffic through sendgrid.com. I chose Sendgrid because they offer a free service for low volume users. This works well for emails generated by the mailman3 system. However, it does not work for the list traffic itself. Sendgrid requires that the "From:" address on any email reference an authenticated domain. In the old mailman2 implementation, emails sent by mailman are listed as From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org Reply-to: <human name> sender(a)senderdomain.com (the original email's sender) Sendgrid would be happy with this, because LISTDOMAIN.org is a validated domain. However, in my mailman3 implementation, the From: header lists the original email's sender. Sendgrid rejects this because the original email's sender's address is not one of the validated domains. How do I configure mailman3 to generate headers in the same style as the old mailman2 implementation? Thanks! -- Stephen Daniel

3 years, 9 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Mark Sapiro

On 4/12/22 03:33, Torsten R. wrote: > > But when I try to send a message (as a member of a list) to a list I always get a 401 in mailman.log and the message that I should check if I provided MAILMAN_ARCHIVER_KEY and if it is correct. > So far, I can say that the key is the same in mailman-web.py (with single quotes) and mailman-hyperkitty.cfg (without quotes). > in mailman-web.py I have: > MAILMAN_ARCHIVER_KEY = 'somesecretkeywithlotsofcharacters' > and in mailman-hyperkitty I have this: > api_key: somesecretkeywithlotsofcharacters > > I have some messages in $var_dir/archives/hyperkitty/spool but mailman qfile <messagefile> doesn't show anything that would catch my eye. The issue is not related to message content. One possibility is that there is an incompatibility between mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause this. What are your versions? What is your setting in mailman-hyperkitty.cfg for base_url: if you append `api/` to that and do something like curl base_url/api/ it should return a page of documentation of the API. If that is the case, the issue is almost certainly communicating the api key between mailman-hyperkitty and HyperKitty -- 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] 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, 9 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 19:25, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:50 PM, Odhiambo Washington wrote: > > > Now that has clarified the matter for me. That even when I am logged out, > > the scripts do the neccessary > > to activate the venv to run things. > > > As mentioned before, a virtualenv is not like a container. It is only a > directory that contains among other things a bin/ directory with > activate scripts and easy_install, python, pip and wheel commands. > > When you activate a virtualenv in your shell, all it really does is add > a deactivate command, modify the command prompt and insert its bin/ > directory at the beginning of its PATH. > > What this means is whether or not a virtualenv is "active", running a > command from the bin/ directory in the virtualenv is using the virtualenv. > Thank you very much for the elaboration. What used to confuse me was the early stage documents which detailed how to run MM3 in a virtual environment - I am talking about the BETA days. I think from this point onward, I have the complete foundation information to move forward. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 9 months

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 5/12/20 3:02 PM, Mark Dadgar wrote: > > The second patch did not work either. Ahh, well. I think you need to do something like this: $ mm/bin/django-admin shell Python 3.7.1 (default, Dec 14 2018, 13:17:01) [GCC 5.4.0 20160609] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email >>> emails = Email.objects.all() >>> for email in emails: ... if email.content.find('\u200b'*5) >= 0: ... print('Found in ml {}, hash {}'.format( ... email.mailinglist.name, ... email.message_id_hash)) ... >>> _NAME/message/HASH/ This will print the mailing list and message id hash for messages found that contain at least 5 U+200B Unicodes in a row. You may need to adjust the '\u200b'*5 if it doesn't find anything. Once you know the list and hash you can go to something like https://example.com/hyperkitty/lists/LIST_NAME/message/HASH/ to see the message in the archive and delete it. Before deleting it, you might want to 'download' it. I'd be interested in seeing that to see if I can understand the issue better and why the patches don't work to solve it. -- 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: Topics - Tags

by Mark

On 2024-03-23 23:21, Stephen J. Turnbull wrote: > Mark writes: > > > >> In Mailman 2 there is an Admin web UI for "Topics". Is there > > >> such a web UI that can be enabled in Mailman 3 so that the list > > >> owners can create topics (tags) in their lists? > > Do you specifically want topics, that is, a way for users to select > subsets of the list posts based on themes set by the administrator? That's what I was referring to. One of the list admins was asking about it after I moved the list from Mailman 2 to Mailman 3. > There is (was?) an alternative specification implemented by the > Systers, which they call "dynamic sublists". > > If that sounds as good as Mailman-2-style topics to you, I can > add/emphasize it on our GSoC task list. Although that sounds good (and I don't think the use of email commands would be onerous to people who would value sublists), I am the wrong person to have an opinion on it as I haven't really used Topics in earnest and most likely would not use sublists. That said Steve, thank you for your considered reply. A font of useful (and much appreciated) information as always. Best, Mark

1 year, 7 months

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Stephen J. Turnbull

Mark Sapiro writes: > One of the runners has died, most likely the `out` runner, but > possibly another. The missing messages are stuck in a queue. Do ``` > ls -laR /opt/mailman/core/var/queue ``` to see in which queue the > messages are. The runner that processes that queue is gone or > possibly stuck. I have seen "stuck", in a multisite installation where Mailman's smarthost ended up being about 1000 miles from Mailman. I'm not sure what the issue is (we fixed the DNS, not Mailman :-), but every once in the while the connection would hang. In that case nothing showed up in the log. The only symptoms were the buildup in the out queue and a stale connection to port 25 on the smarthost. If your smarthost is not "network far" from the Mailman host, this is quite unlikely from my experience, although Mark may know better. In any case, I think the best way to start diagnosis is to check the Mailman and MTA queues for stuck messages. Of course in normal operation you will often see messages in the queue, but long queues or messages older than a minute are 99% a dead or stuck queue runner. Steve

1 year, 7 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Mark Sapiro

On 08/04/2017 02:54 AM, Cyprian Laskowski wrote: > Hi, > > On our new installation of Mailman 3, which seems to be otherwise working fine (thanks!), the "More..." link doesn't work, such that the list continues to only show 5 posts, even though it's clear that hyperkitty is aware of more (if I click on August, for example). This is <https://gitlab.com/mailman/hyperkitty/issues/134>. The fix is a one-liner at <https://gitlab.com/mailman/hyperkitty/commit/2034b937c438f66b465d86bebbbc12…> > Also, nothing is shown in the grey box under Activity Summary (the <svg class="chart-data"> element), although I'm not sure what's supposed to be shown there. The public archived list is here: http://seznami.cjvt.si/hyperkitty/list/test@seznami.cjvt.si/. I'd appreciate any pointers. The box is a bar graph of posts by day. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> for what it should look like. I'm not sure why it's empty in your case. Do you have cron running all the Django minutely, quarter-hourly, ... tasks? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

[MM3-users] Re: Hyperkitty Archives - Sidebar years/months

by Mark Sapiro

On 11/7/18 4:18 PM, Enrique Terrazas wrote: > Thank you Mark > I don't think the periodic Django jobs are running. I do see the cron job executing the jobs as scheduled but I am seeing errors being sent to /var/spool/mail/mailman (thats the user that runs the MM3 application) that say: > /bin/sh: django-admin: command not found So whatever django-admin you are trying to run is not in the path of the cron job. Try an absolute path to django-admin instead. > If I run: > django-admin --help > > I get the following: > > Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). I install Mailman in a virtualenv and the django-admin file I run contains #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ The main things are the directory containing settings.py is /opt/mailman/mm and I export that as PYTHONPATH so my settings module can be found. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Emergency Moderation

by Mark Sapiro

On 5/24/20 10:59 AM, Allan Hansen wrote: > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ If you imported your MM 2.1 lists with `mailman import21`, `emergency` was set appropriately for the imported list and should be working to hold posts regardless of other settings. > My own current top-of-the-list issues: > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. Editing membership beyond what could be done via the admindb interface (i.e. clearing a moderated poster's mod flag) was never allowed for a moderator in MM 2.1. In MM 3, a moderator can set a member's moderation when handling a held post. Do you think a non-owner moderator should be able to make other changes to a member? > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're working on it. -- 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: Disable Sign-up per domain

by Mark

On 2025-07-31 03:31, Mark Sapiro wrote: > Anything is possible, it's only code ;) > > You could make your own user_adapter.py which is modified like > > and set that as the ACCOUNT_ADAPTER. This depends on whatever is > proxying to Django setting the appropriate HTTP_HOST header. Thank you Mark. It's so close. After wrangling your solution a bit it's working a treat on my test server (wrangled solution below) . When I add it to the production server (same OS, MM installation, etc) I'm getting a "Bad gateway" error page and the log reports ... ... raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. I cannot for the life of me get my head around that. I suspect it's something to do with what you said -- "whatever is proxying to Django setting the appropriate HTTP_HOST header." -- which I don't understand. Any additional advice gratefully received. ================================== /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py ================================== COMMENT OUT THESE 2 LINES... # def is_open_for_signup(self, req): # return False REPLACE WITH THE FOLLOWING... def is_open_for_signup(self, req): if req.META['HTTP_HOST'] == 'lists.mydomain.com': return False else: return True ================================== /etc/mailman3/settings.py ================================== Append the following ... ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' ================================== systemctl restart mailman3 systemctl restart mailmanweb ==================================

3 months

[MM3-users] Re: redirecting -bounces replies

by Hirayama, Pat

Sorry, I knew that. Thanks for your assistance today. Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, June 26, 2025 16:36 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 6/26/25 15:29, Hirayama, Pat wrote: > Well ... each list has 9 email addresses — the list address, the -bounces, the -confirm, the -join, the -leave, the -owner, the -request, the -subscribe and the -unsubscribe ... I think I'm around 4500 listservs right now..... 4500 lists is a lot, but not unheard of, but please don't call them listservs. See https://urldefense.com/v3/__https://wiki.list.org/DOC/Mailman*20is*20not*20… -- 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

4 months, 1 week

[MM3-users] Re: Installing MM3 via pip fails…

by Patrick Ben Koetter

* Mark Sapiro <mark(a)msapiro.net>: > On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > > > I followed the instructions at > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > > As soon as I get to the Django part things get hairy. It seems Django requires > > something that was removed from it. > > > What exactly is the issue? I just tried following the doc starting at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> > and doing everything through > > (venv)$ python3 manage.py runserver > > and I encountered no issues. One possibility is the Ubuntu 18.04 box on > which I did this already had ruby-sass and python3-dev globally installed. > > sudo apt install ruby-sass > sudo apt install python3-dev > > Did you install these? Yes, I did. But to be sure I'll try on a vanilla VM and see how it goes if I install ruby-sass and python3-dev beforehand. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 years, 8 months

[MM3-users] Re: Backups & disaster recovery of mailman3

by Mark Sapiro

On 3/7/21 11:07 AM, David Partain via Mailman-users wrote: > Hi, > > So now I have a running mailman3 installation. Whew... > > Is there documentation of things like thorough backups and disaster recovery? I haven't yet found it. > > Backups: Obviously, I understand that I need to have datbase (mysql, in my case) dumps, and I'll have file system backups onto something that our IT folks will backup. Is there more I should think of? No, backing up the database with dumps and backing up Mailman's var/ directory and the various settings and mailman.cfg files should be sufficient. Backing up the entire Mailman installation might be useful should you need to restore it on a new server. > Disaster recovery: So, let's say my server (which is cloud-y) gets trashed and I need to get mailman back on a new server. Is this process described somewhere? I don't think so, but assuming you get all the Mailman pieces together on the new server, loading the database from a backup dump and restoring the var/ directory and the various settings and mailman.cfg files should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Any possible way to reduce robot spam accounts?

by Franklin Weng

Hi Mark, Mark Sapiro 於 2023/7/21 12:01 寫道: > On 7/20/23 20:42, Franklin Weng wrote: >> >> Thank you. When I set it in my settings_local.py, I clicked register >> and got an error: >> >> ModuleNotFoundError at/accounts/signup/ >> No module named 'django_mailman3.views.user_adapter' >> >> (In the document the path is /etc/mailman3/settings.py but I >> installed it with Debian packages so I guess the path is somewhat >> different, and I thought setting in setting_local.py should work >> too. It seems work since it gave me the error above.) >> >> Do I have to install something else? Or disable some other options? > > > What is the version of django_mailman3 in your Debian package? As it > says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for > these settings to work." > Debian Bullseye goes with 1.3.5, and Debian Bookworm goes with 1.3.9 but as I have said in another thread it has problems in django admin. So I downloaded the 1.3.9 source code, extracted it, and copied django-mailman3/views/user_adapter.py to /usr/lib/python3/dist-packages/django_mailman3/views. It worked! For a record here. Thanks for your help. Thanks, Franklin

2 years, 3 months

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

by Roland Giesler

On 2024/07/30 22:39, Mark Sapiro wrote: > It appears you have a situation where the MX for the Mailman domains > is not the Mailman server. You need to configure the MTA on > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > You can to this by configuring that MTA to use transport_maps, etc as > if it were the Mailman server. In order to get Mailman's generated > files on the other server, you need to create a process to do that. > When Mailman makes changes by adding or deleting lists or when it is > started, it updates the postfix_lmtp and postfix_domains files and > calls a command (normally postmap) to update the corresponding .db > files. The command can be set by setting `postmap_command` in the > `[postfix]` section in mailman.cfg. I'm not able to find any documentation about `postmap_command`, not even in the schema.cfg. If I have to provide method to update the postfix_lmtp and postfix_domains on another server, then it would have to something like sftp? mailman changes the files on the mailman server (in a location I set) and then postmap_command copies those files to the destination on the MTA server. Is that in principle what needs to be done? thanks again! Roland

1 year, 3 months

[MM3-users] Re: Installation Wooes

by Mark Sapiro

On 5/3/20 7:14 PM, Samir Faci wrote: > > Here's my next question. Hopefully this isn't off topic, but trying to get > postfix to work with mailman and I keep on getting relay denied issues. ... > These are the changes I have in postfix that seem relevant. > > /etc/postfix/master.cf > > mailman unix - n n - - pipe > flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > ${nexthop} ${user} postfix-to-mailman.py is Mailman 2.1 only. It doesn't work with Mailman3. > /etc/postfix/main.cf > > compatibility_level = 2 > > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains These mostly have to do with delivery of mail to Mailman rather than from Mailman. > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated > defer_unauth_destination > myhostname = lists.domain.org > mydestination = $myhostname, localhost.localdomain, localhost, $mydomain, > lists.domain.org The entire output from `postconf -n` might be helpful. Also the postfix log messages for the the failed deliveries would be helpful. Can you send mail to csgeek(a)domain.com in other ways, e.g. mutt or mail or sendmail? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

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

by Mark Sapiro

On 5/18/21 7:28 PM, Mark Dadgar wrote: > > 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? First, the Django users are separate from Mailman core users and don't have anything directly to do with list subscriptions. As far as how there got to be one User in Django with two EmailAddresses differing only in case, that's probably a bug in Django allauth. The page at accounts/email/ doesn't allow adding an address that differs only in case from an existing address, but possibly adding via a social auth provider bypasses that check. I couldn't find an issue at https://github.com/pennersr/django-allauth/issues but that doesn't mean there isn't one. In case you haven't done it, I think just deleting one of the addresses (the non-primary one) in Django's Email Addresses section will solve your issue. -- 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: Mailman3-Web lots of database queries

by Abhilash Raj

On Mon, Dec 3, 2018, at 11:44 AM, Stefan Tatschner wrote: > On Mon, 2018-12-03 at 10:01 -0800, Abhilash Raj wrote: > > So, if you are using Django's ORM to keep the task states in Django Q, this > > is bound to happen depending on how frequently do you run tasks. In Hyperkitty, > > we have some minutely tasks, which means the polling is going to be high. > > > > You can however, configure Django Q to store the tasks outside of database > > in a better high-speed in-memory database like Redis for example[1] for queuing > > the tasks. Other options like MongoDB, Amazon SQS is also available. > > Is it really necessary to have these high complexity? Reducing database > load by introducing another database seems wrong to me. Redis is not exactly a database, it is used as a message broker. The ORM backend in DjangoQ exists for low performance workloads where you can afford to poll the database that frequently and not have negative affects on rest of your system. It also lets you avoid installing a message broker like Redis. If your system does handle a ton of traffic, then it is recommended to use Redis or similar higher-performant systems. -- thanks, Abhilash Raj (maxking)

6 years, 11 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Mark Sapiro

On 11/12/20 6:59 AM, Brian Carpenter wrote: > On 11/11/20 7:40 PM, Mark Sapiro wrote: >> >> The message has been delivered to the list, but it is not archived. The >> list post has an Archived-At: header with a URL, but the message isn't >> there at all. The only way to get it archived is to correct the message >> defect. > > Does the problematic message (null character) make it to the > hyperkitty_thread table? I thought that saying it is not archived would answer that, but no, nothing about that message is stored in any hyperkitty table. > Can a message with a null character be repaired with an automatic process? Probably, but I don't think HyperKitty should be in the business of attempting to repair message defects. This one issue of a null byte is arguably not a defective message, but rather an issue of storing a null byte in a database field, so maybe something could be done to `cleanse` that data before storing it. If I were going to look at doing that, I would need an example of a problem message, and ideally, an issue in the tracker. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: redirecting -bounces replies

by Stephen J. Turnbull

Hirayama, Pat writes: > So, when I try adding entries to a separate vmap file, like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24, user(a)gmail.com > > It only goes through normal bounce processing. IIRC the usual configuration uses the virtual map as a transport file. The transport file format allows only one result, which must be a transport of the form protocol:host:port. I'm surprised that either of those works at all, as both are syntax errors. (Unless possibly 'lmtp:[mailman-core]:24' is being interpreted as a local but undeliverable address? I forget whether colons and square brackets are allowed in local-parts.) What are your Postfix logs saying about all this mischief? > I'm thinking that I can't combine two methods of delivery (LMTP + > email address). Do you know if that is correct? It's not impossible, I think, but it's probably both tricky and ugly. :^) You need one virtual alias mapping'list-bounces(a)lists.domain.info' to 'user(a)gmail.com' and another address (probably with a "fake" domain such as 'bounces.lists.domain.info'), and the latter address gets mapped in a transport to lmtp:[mailman-core]:24. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 1 week

[MM3-users] Re: HyperKitty failure: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400)

by Stephen J. Turnbull

armin.schoeffmann(a)aegaeon.de writes: > > What version of Django is installed? > 4.1.2 If your main priority is to get mailman-web working, I suggest trying a downgrade of Django to 3.2.x. (Probably x=16 is current but any x in double digits should be OK). We just a couple weeks ago merged patches from a 3rd party to support Django 4. So quite a bit of risk here, I don't think any of the core devs are running Django 4 systems yet, and I know none of the production systems at python.org and mailman3.org do yet. If you're willing to help us get our code in shape for Django 4, of course we'd love to have a beta tester. :-) But to be honest, I have no idea what's going on with that error, and I don't know if either Abhilash or Mark would either. So it may take a while (or Mark could pop up in 10 minutes and wave his magic wand and all will be well -- that's life in the beta lane ;-). Steve

3 years

[MM3-users] Re: Database problem after system upgrade

by Lars Bjørndal

I managed to upgrade the database. However, Mailman3 won't start: × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: failed (Result: exit-code) since Wed 2023-11-15 06:49:38 CET; 44min ago Process: 28224 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 948ms nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: return self.loaded_dbapi.connect(*cargs, **cparams) nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: File "/opt/mailman3/venv/lib64/python3.11/site-packages/psycopg2/__init__.py", line 122, in connect nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: conn = _connect(dsn, connection_factory=connection_factory, **kwasync) nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication failed for user "mailman" nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: (Background on this error at: https://sqlalche.me/e/20/e3q8) nov. 15 06:49:38 dalen.lamasti.net systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE nov. 15 06:49:38 dalen.lamasti.net systemd[1]: mailman3.service: Failed with result 'exit-code'. nov. 15 06:49:38 dalen.lamasti.net systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. Mailman.log doesn't contain any info. How do I find the cause of this problem? Lars

1 year, 11 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Phil Thompson

On 07/08/2019 17:04, Abhilash Raj wrote: > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: >> On 06/08/2019 09:48, Phil Thompson wrote: >> > On 06/08/2019 03:38, Abhilash Raj wrote: >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >> >>> I'm in the process of setting up mailman3. The only problem I seem to >> >>> be >> >>> having is getting Hyperkitty to archive messages. Rather than the >> >>> authorisation problems people have previously asked about on the >> >>> list, I >> >>> am getting a 403 error... >> >>> >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >> >>> <html><title>Forbidden</title><body> >> >>> <h1>Access is forbidden</h1></body></html> (403) >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >> >>> <html><title>Forbidden</title><body> >> >>> <h1>Access is forbidden</h1></body></html> (403) >> >>> >> >>> Any suggestions would be appreciated. >> >> >> >> How did you install Hyperkitty? >> > >> > On Ubuntu... >> > >> > apt-get install mailman3-full >> > >> >> You probably need to the set the API key correctly in both Core and >> >> Hyperkitty. >> >> >> >> Have you looked at documentation here[1]? >> >> >> >> [1]: >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… >> >> >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in >> >> quotes, single or double, doesn't matter) in your settings.py for Web >> >> (Django) should be same as the `api_key : value` (without quotes here >> >> in hyperkitty.cfg config file). >> > >> > That's all correct. I'm familiar with the authorisation issues that >> > other people have had. >> > >> > The only thing I'm doing differently (as far as I am aware) is that >> > I'm using a URL prefixed with /mailman3 which is stripped off in my >> > nginx configuration... >> > >> > # mailman3. >> > location /mailman3/ { >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; >> > include uwsgi_params; >> > uwsgi_param SERVER_ADDR $server_addr; >> > uwsgi_modifier1 30; >> > uwsgi_param SCRIPT_NAME /mailman3; >> > } >> > >> > location /mailman3/static { >> > alias /var/lib/mailman3/web/static; >> > } >> > >> > location /mailman3/static/favicon.ico { >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; >> > } >> > >> > ...but I don't see this affecting the mailman to Hyperkitty >> > communication. Posting to lists and the Postorius and Hyperkitty >> > frontends seem to work fine. >> >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my >> public IP address). However I now get a 400 Bad Request error. >> >> I have traced this to the archive() function in >> hyperkitty/views/mailman.py which is expect a POST but is actually >> getting a GET, specifically... >> >> GET '/mailman3/hyperkitty/api/mailman/archive?key=...' >> >> ...which seems to be a fairly fundamental problem. >> >> Again, any suggestions would be welcome. > > It should be sending POST request to archive emails[1]. How did you > grab the above request? Was it from logs? Yes, I added DEBUG=True in mailman-web.py and captured the HTML from mailman.log. > Do you have anything else in the logs? There should be something in > the Mailman Core or web logs should have something. There's nothing useful in the core log. There are 3 preceding entries in the web log... GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&key=... GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... There is one item in the spool directory. These were all (apparently) successful. It seems odd that the last two entries were identical. Phil

6 years, 2 months

[MM3-users] Re: Bad Signature with Gmail

by Mark Sapiro

On 9/19/20 12:33 PM, Massimo Zappalà wrote: > Hi Mark, thanks for the reply. > > my /etc/opendkim.conf > AutoRestart Yes > AutoRestartRate 10/1h > UMask 002 > Syslog yes > SyslogSuccess Yes > LogWhy Yes > Canonicalization relaxed/simple > ExternalIgnoreList refile:/etc/opendkim/TrustedHosts > InternalHosts refile:/etc/opendkim/TrustedHosts > KeyTable refile:/etc/opendkim/KeyTable > SigningTable refile:/etc/opendkim/SigningTable > Mode sv > PidFile /var/run/opendkim/opendkim.pid > SignatureAlgorithm rsa-sha256 > UserID opendkim:opendkim > Socket inet:12301@localhost > > > my /etc/opendkim/SigningTable > *(a)catania.linux.it mailselector._domainkey.catania.linux.it Assuminng your list's domain is catania.linux.it, what you need to do to enable DKIM signing of this message is add SenderHeaders List-Post,Sender,From to /etc/opendkim.conf > full email django error > Internal Server Error: /hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\xB1\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") Unfortunately, the rest of the detail doesn't help. What we need to see is the raw message. You should be able to find it in Mailman's var/archives/prototype/<list_address/new/ directory, perhaps by timestamp or something in the headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Re-enable member after bouce processed disable

by Mark Sapiro

On 12/9/21 6:07 AM, Henrik Rasmussen wrote: > Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. > > When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. You are looking at the user's list based preferences. If one of these is unset, it falls back to address based preferences and from there to the user's global preferences. You can see all of these for yourself at the Mailman settings choice in the dropdown at your user name, but for another list member you only see the list based preferences. > How do I or the list admins re-enable a bounce-disabled member? Just set the member's delivery status on the page you see to Enabled. Even though it was not previously shown as Disabled by Bounces, it will be enabled. Likewise the member can set her Delivery status to Enabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] nginx configuration on a multitasking server

by David Newman

Couple of questions about the sample nginx configuration given in the venv doc and the Mailman Mailman Suite Documentation v. 3.3 PDF: server { listen 443 ssl default_server; listen [::]:443 ssl default_server; server_name MY_SERVER_NAME; location /static/ { alias /opt/mailman/web/static/; } location / { proxy_pass 127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ssl_certificate /path-to-ssl-certs/cert.pem; ssl_certificate_key /path-to-ssl-certs/privkey.pem; } 1. At least on my system, the proxy_pass statement will only run without errors if I change this to a fully formed URL, e.g., 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs? 2. What document root(s) and alias(es) to use for Postorius and Hyperkitty and the Django admin on a server that also runs other services (e.g., Postfix for non-list mail and Roundcubemail)? With MM2, I use location statements with their own root and aliases: location /mailman { root /usr/lib/cgi-bin; fastcgi_split_path_info (^/mailman/[^/]+)(/.*)$; fastcgi_pass unix:///var/run/fcgiwrap.socket; include /etc/nginx/fastcgi_params; fastcgi_param SCRIPT_FILENAME \ $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_path_info; } location /images/mailman { alias /var/lib/mailman/icons; } location /icons { alias /var/lib/mailman/icons; } location /pipermail { alias /var/lib/mailman/archives/public; autoindex on; } What is the MM3 equivalent way to do this? I think root would be somewhere under /opt/mailman but don't know exactly where, or which locations to point to. Many thanks! dn

3 years, 10 months

[MM3-users] Re: RFC-2369 List-Unsubscribe header missing

by Stephen J. Turnbull

Hi Paul Glad you got that sorted! I wonder why those filters were in there? Not really the kind of thing I'd expect Postfix to be doing out of the box! Looks like you didn't send to the list (at least, I got my copy via personal mail, not the list). Replying for the benefit of Mailman-Users (nothing new to you here). Sparks, Paul writes: > Postfix was filtering the headers. I was not familiar with this > postfix functionality. > > For others who might see this, the filter lines were in /etc/postfix/header_checks > /^List-Unsubscribe:/ IGNORE > /^List-Subscribe:/ IGNORE > > How are you capturing mail at postfix? > > For capturing the email at postifx I used the following to defer SMTP sending. > postconf -e defer_transports=smtp; postfix reload That swooshing sound is that concept returning to hover over my head. > # send the email to the server > mailq > # Use ID from mailq to examine the email using postcat > postcat -vq C23D82B60024 > # Re-enable SMTP sending > postconf -e defer_transports=; postfix reload; postfix flush That's potentially useful in a lot of situations! Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 3 weeks

[MM3-users] Re: Relay Access Denied

by jkoral＠luc.edu

lstprdls01:/var/log # postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no compatibility_level = 3.6 inet_interfaces = all inet_protocols = all local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp mailbox_size_limit = 0 mydestination = $myhostname, localhost.$mydomain, listservnew.luc.edu lists.luc.edu myhostname = lstprdls01.svr.luc.edu mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname owner_request_special = no readme_directory = no recipient_delimiter = + relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains relayhost = smtp_tls_ciphers = high smtpd_tls_ciphers = high smtp_tls_exclude_ciphers = EXP, MEDIUM, LOW, DES, 3DES, SSLv2 smtpd_tls_exclude_ciphers = EXP, MEDIUM, LOW, DES, 3DES, SSLv2 smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination smtpd_tls_mandatory_protocols = !TLSv1.1 TLSv1.2 TLSv1.3 tls_high_cipherlist = TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384:TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 So, you helped me with this before and I think I got the mail to go through now, but now I am getting a different error, which I think may have to do with the aliases. The old server is using lists.luc.edu and the new server is using listservnew.luc.edu, but we still want people to use lists.luc.edu, but it be forwarded to the new server. I am getting this now. 2025-07-22T12:16:14.551521-05:00 lstprdls01 postfix/smtpd[190496]: NOQUEUE: reject: RCPT from unknown[10.18.3.105]: 550 5.1.1 <joetest(a)lists.luc.edu>: Recipient address rejected: User unknown in local recipient table; from=<jkoral(a)luc.edu> to=<joetest(a)lists.luc.edu> proto=ESMTP helo=<DM1PR04CU001.outbound.protection.outlook.com>

3 months, 1 week

[MM3-users] Re: list footer questions

by Mark Sapiro

On 6/7/20 3:22 PM, kelly.close(a)lrewater.com wrote: > Well, Glory Be! My .cfg settings were fine but the public.template table was empty (I'm using PostgreSQL and accessing it with pgAdmin). I had not considered that there needed to be database content representing the template but it makes sense. Everything else is in there, which is the whole reason why we went with Mailman3 in the first place. > > After manually creating this record in the public.template table it WORKED!!! > name = list:member:regular:footer > context = f2p2-test.udfcd-lists.org > uri = file:////var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/list… > (username and password were left blank) username and password are only required for basic auth to the URI if needed so blank is correct. However, you shouldn't have needed to do that. I only mentioned it in case there was an entry for the name and context with a URI pointing elsewhere. The default if there is no entry is to use Mailman's normal search rules which include templates/lists/<list-id>/en/list:member:regular:footer.txt. So I have to think that without that entry, it was searching a different templates/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/29/20 11:26 AM, Mark Sapiro wrote: > On 10/29/20 5:17 AM, Brian Carpenter wrote: >> On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >>> On 29/10/2020 01:57, Brian Carpenter wrote: >>>> With Mailman 3, every list owner has the ability to remove a reply in >>>> a thread, a complete thread, and even the entire archives. That is a >>>> welcome difference from MM2 in my opinion. >>> A very welcome difference, only I don't see this option in the web >>> interface of my debian 3.2.1 installation. Is this a shell only >>> option, 3.3 feature or configuration option I have missed? >> It is not a shell option. It can be done via Hyperkitty but I am not >> sure when that feature showed up. > > Actually, with current HyperKitty, only site admins can remove messages > or threads or the archive. The ability for list owners to do it is > <https://gitlab.com/mailman/hyperkitty/-/issues/261>. Thanks Mark. To clarify more, we have this ability for List owners with our own custom admin interface (Affinity). I thought Postorius had that. When I checked out Postorius, I was indeed logged in as server owner. Sorry for the incorrect info. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by samuel.d.darwin＠gmail.com

> the fourth paragraph: "Because the REST server has full administrative access, it should never be exposed to the public internet. By default it only listens to connections on localhost. Don’t change this unless you really know what you’re doing." Let's say that you are trying to embed Hyperkitty into a larger Django project that's horizontally deployed in an autoscaling group or K8S. The mailman-core component would be better served from a fixed IP address and a single server. In order for mailman-web to communicate with mailman-core, it needs to listen on a network interface, not localhost. So, you'd like to have a config field, and listen on a reachable interface and then configure the AWS Security Groups or Firewall to limit access. The proposed "listen" field is optional, and in its absence, it defaults to the current behavior, which is localhost. This scenario matches the "really know what you’re doing" case. You'd be facilitating a more advanced architecture, although not requiring it, and still default to localhost. However, again I say "theoretical", because we ran into other difficulties with embedding Hyperkitty in a larger Django project. It seems easier to break that into a bite sized pieces, and only address them one at a time.

1 year, 9 months

[MM3-users] Re: WEB UI fail to reply and create new thread

by Mark Sapiro

On 12/19/20 3:02 AM, Carlo Landmeter wrote: > We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. > I also doubt the shown error is the problem as I see more template errors. > I have also tried to run the official docker images mailman-docker but im having the same issue. > > When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email. > > PS emails are send just fine via smtp posting. The error reported from hyperkitty/ajax/temp_message.html in the OP has nothing to do with the replies not being sent or archived. hyperkitty/templates/hyperkitty/ajax/temp_message.html is called to build the HTML response sent to the web browser after the reply has been sent to Mailman core. Abhilash's fix at <https://gitlab.com/mailman/hyperkitty/-/merge_requests/299> will get rid of that error, but I would be very surprised if it fixes the problem. -- 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: is there a mailman command/setting to periodically clean archives?

by David Newman

On 12/29/21 4:11 PM, Mark Sapiro wrote: > On 12/29/21 3:58 PM, William Oliver wrote: >> >> I'd like to delete all my archives that are more than a certain age, >> e.g. more than a week old. I can easily do that with a cron job, >> deleting old files in >> >> >> /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* >> >> which is, as far as I can see the only place archive emails live. > > > Those are emails archived in the prototype archiver. That's all the > prototype archiver does - store the mail there. The HyperKitty archived > emails are stored in the mailmanweb database in the hyperkitty_email > table. Attachments are in the hyperkitty_attachment table and other > tables are also involved. As a followup: Is there any need or advantage to running both the prototype and hyperkitty archivers? I did an installation following the venv directions, and it looks as though the system now uses both archivers. If this is a duplication of effort and storage, is it safe to disable the prototype archiver like this: # /etc/mailman3/mailman.cfg .. [archiver.prototype] enable: no and then delete anything under here? /opt/mailman/mm/var/archives/prototype/ Thanks dn

3 years, 10 months

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

by Stephen J. Turnbull

Brian Carpenter writes: > 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. Oh, no question about that whatsoever. I'm quite surprised that this facility isn't present yet. (I rarely make mistakes in mass subscribe and the defaults work fine for my subscribers -- or they make their own changes -- so I can't recall ever encountering this need.) I wonder if in Mailman 3 where user profiles exist and are clearly *not* subject to control by *list* admins in the same way that subscriptions are, and in this day of GDPR etc if maybe we need to restrict admin access to various user properties. This sounds like a rather difficult design problem. > I don't see this functionality built into Mailman 3 nowhere near > the extent that Mailman 2 has. Web interfaces are supposed :-( to be easy enough for Great-Grandma to use, so I imagine the designers didn't think much admin intervention would be needed. > My approach with Affinity is definite leaning very heavy on the > needs of list admins atm. Perhaps that's a good division of responsibility between Postorius and Affinity dev processes. Something to think about. Steve

5 years, 7 months

[MM3-users] Re: Problem with list creation

by Abhilash Raj

On Thu, Sep 17, 2020, at 4:17 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > > > We increased timeout in mailman.cfg > > This looks like the issue in Shashikanth's post, too: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > They are also creating more than 1000 lists. > > Do we know why these timeouts are happening? (Search for "list > creation times out" returns no results in either core or Postorius > issues.) This is the first time I am actually seeing this. I tried hammering a local server with default number of workers, 2, and created 5000 lists in a loop and went through pretty smooth. I am probably not replicating the exact situation, I am using the sqlite database (which I presumed would be slow and choke up faster but...it didn't). Creating list isn't one of the slow operations AFAIK, so I am actually surprised that it needs increasing timeout. It could be the interaction with database layer maybe, but I can't be sure without more debugging. > _______________________________________________ > 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)

5 years, 1 month

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 2:18 AM, marcus--- via Mailman-users wrote: > > The problem, however, is that it does not send out any mails, nor do they appear in the archive. > > When I look in the Mailman-Log I find: > > May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 This is a misleading error message. It can occur when Mailman's out runner can't read a template. You need to check ownership and permissions on mailman/templates in the code tree and Mailman's var/templates directory which probably has permissions errors from running inport21 as root. Also, if you've set any templates in Postorius, they may not be accessable if your setting for POSTORIUS_TEMPLATE_BASE_URL is not good. > May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost > [Errno 111] Connection refused > May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: > [Errno 111] Connection refused Are you gating messages to/from usenet for this list? If so, you have to set host: and port: and maybe user: and password in the nntp section of mailman.cfg -- 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: Hyperkitty: Error when rebuilding Index

by Mark Sapiro

On 11/26/21 4:35 AM, M4tze wrote: > Dear list members, > > if there is any Hyperkitty expert here, I have issues in Hyperkitty > (just updated Maxkings Docker images) when rebuilding the Index. > > Unfortunately, there are more than 25,000 mails and I do not know which > one is/might be broken. Does the error mean that the rebuilding process > is incomplete or does it simply skip the erroneous message? It means the process is incomplete. > Traceback (most recent call last): ... > return self._result.fetch_row(size, self._fetch_type) > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position > 3209: invalid continuation byte I'm not sure what's going on here. I suspect the issue is withe the `content` of some message in the hyperkitty_email table in the database. You could try a database query like ``` SELECT * FROM hyperkitty_email WHERE LEN(content) >= 3209; ``` If you're lucky, that may just return a few messages and enable you to find the problem one. Otherwise, you could try first running `mailman-web clear_index` and then run `mailman-web update_index` with --start and --end options to specify a date range and zero in on the offending message. -- 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: Should I try to install mailman3 on Kubuntu 20.04?

by Sam Darwin

Ubuntu 20.04 will be end-of-life, from a standard perspective, in a year. If you possibly can, prefer to install on the latest version which is Ubuntu 24.04. Another option is upgrading the original server to 22.04. And then, 24.04. Upgrade procedures usually go fine. On Fri, Oct 4, 2024 at 4:31 PM Bill Oliver <billo(a)billoblog.com> wrote: > > I have been a happy camper running mailman3 on a vps I rent from a > vendor, running CentOS 7. CentOS 7 is past end of life, so I moving > over to a new machine running Kubuntu 20.04 LTS. I have been searching > the intertubes and have seen a bunch of people having headaches trying > it. So... > > Is Ubuntu 20.04 cool with mailman3? Should I go ahead and give it a > shot or use a different distro? > > Should I do the apt install, the virtualenv install, or try the docker > install? > > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to samuel.d.darwin(a)gmail.com >

1 year, 1 month

[MM3-users] Re: Finding a mailman3 installation description that works

by Andrew Hodgson

Abhilash Raj wrote: >On Tue, Mar 31, 2020, at 11:28 AM, Andrew Hodgson wrote: >> ralf.wiegand(a)tena-sda.org wrote: >> >> >WE are currently using mailman2. I have the task to setup and install a maiman3 server. Postfix is installed and working. Can anybody point me to a link where the actual installation is described using RHEL 7 or RHEL 8. This will be a >hardened DISA compliant server, so I am trying to avoid installing compilers and tools that are not part of the standard RHEL 7 repos. > >> Have you looked at creating a development environment using a Python3 >> venv somewhere else (eg another server or container) then copying the >> venv out to the production server? >Python virtualenvs are really not movable because of the paths that are in there. It is tricky to get that working right, I would caution against doing that. Thanks for this, I actually did this work over the weekend to test a restore on a new server using the same paths because I was worried about this being an issue. It did work, but the paths were exactly the same. I may have to re-investigate quick restore options (probably writing a script to create the venv and re-constitute the packages). Andrew.

5 years, 7 months

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Gilles Filippini

Hi, Brian Carpenter a écrit le 14/07/2020 à 12:54 : > On 7/14/20 6:49 AM, Gilles Filippini wrote: >> Mailman Core logs: >> [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) >> [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) >> [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 > > I am pretty sure that timeout is related to gunicorn. If it is, then > increasing the worker out timeout setting for gunicorn should work. You > tend to get such errors when doing an export of a large membership > roster. This is the first time I have seen it related to a held message. > > I have this in my setup: > > mailman.cfg: > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > gunicorn.cfg: > > [gunicorn] > workers = 4 > timeout = 900 > > You will need to restart gunicorn after adjusting the timeout setting. Sorry for the late answer, I was afk the last 24 hours. I can confirm that this solution works. Thanks a lot! And thanks to Mark for the added details. But it sounds weird that printing out the number of held messages could timeout because of these messages' size. Best, _g.

5 years, 3 months

[MM3-users] Re: How to change the language in mailman3

by Mark Sapiro

On 7/17/20 8:22 AM, maszap(a)tin.it wrote: > Hi everyone, > from here: > https://hosted.weblate.org/projects/gnu-mailman/hyperkitty/it/ > I see that there is a way to change the language of mailman3, postorius and hyperkitty > But I don't find how. > I read that you can download the .po files for the chosen language, but I didn't understand how to use these files. > Could anyone show me how to do it? The various message catalogs for Mailman core are in mailman/messages/ and those for hyperkitty, django-mailman3 and postorius are respectively in hyperkitty/locale/, django-mailman3/locale/ and postorius/locale/. The translations from weblate are incorporated in the distribution, but depending on how Mailman is installed, may be out of date. To set language for Django (i.e. hyperkitty and postorius) see <https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#how-django-d…>. For Mailman core, set `[mailman] default_language:` in mailman.cfg. You also need to (re)generate the .mo file which can be done with the generate_mo.sh script. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/inter…> For Django, you need to generate .mo files with `django_admin compilemessages` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it

by Mark Sapiro

On 5/17/24 12:06 PM, Keith Christian wrote: > The path to the mailman3.py file is: > /home/mailman3/mailman/src/mailman/bin/mailman.py > I created a mailman3 user, then, set the ownership on all directories > and files in /home/mailman3 and below to mailman3:mailman3. You need to install all the dependencies and also have /home/mailman3/mailman/src/mailman in your PYTHONPATH. If you just want Mailman Core and given that you've already cloned it from gitlab, I suggest creating a Python virtual environment as the mailman3 user with `python3 -m venv /path/to/your/venv` and then as the mailman3 user activate the venv, `source /path/to/your/venv/bin/activate`, and do `pip install /home/mailman3/mailman` to install Mailman and it's dependencies in the venv. Then you can just run `mailman info`. I suggest a venv for this to isolate the dependencies from things that might already be installed system wide with differing versions. To install the whole suite including the Postorius web UI for list management and the HyperKitty archiver, see https://docs.mailman3.org/en/latest/install/virtualenv.html -- 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: New installation, new issue: mailman3 migrate -- no module CommonMark

by Bill Oliver

On Sun, 2024-10-27 at 10:01 -0700, Mark Sapiro wrote: > On 10/27/24 05:13, Bill Oliver wrote: > > > > (venv) mailman@mail:~$ pip freeze | grep readme > > readme-renderer==17.4 > > > Which is over 6 years old. Howat did that get installed? Current > version > is 44.0. There may or may not be an issue with the current version as > it > imports cmarkgfm which is in the venv of all the MM 3 installations I > support, but I don't know how it gets there as even though > readme_renderer imports it, it is not listed as required by > readme_renderer or anything else. > > In any case, in your venv, do > ``` > pip install --update readme_renderer cmarkgfm > ``` > That did the trick, though I had to use --upgrade instead of --update. Thanks... Now on to the next step. I don't know about the libraries. Here's my mailman info. It seems like the right version of python. (venv) mailman@mail:~$ mailman info GNU Mailman 3.3.10 (Tom Sawyer) Python 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:qazASD%401cko@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Thanks for your help! billo

1 year

[MM3-users] Re: MTA setup

by Mark Sapiro

On 11/17/24 19:32, Arte Chambers via Mailman-users wrote: > > Mailman is successfully sending invite emails however user messages sent to > the list are not being sent to subscribers. Also in Hyperkitty none of my > test messages to the list are showing up in the archive. Are there messages in Mailman's shunt queue? Check for errors in mailman.log. Are there messages for hyperkitty queued in Mailman's var/archives/hyperkitty/spool/ directory? > I am using Postfix with an SMTP relay hosted at Brevo.com (formally > sendinblue). Brevo's logs show the message getting rejected > > > Log from brevo.com (SMPT Relay) > Sent on 17-11-2024 21:49:16 >>From listmember(a)gmail.com > To listmember(a)gmail.com > Message ID<CAPesOD1y0fEaG=GFodz=Lgs1m_hqRErPnQcpXCNtKsBbJ= > BJ7Q(a)mail.gmail.com> > > 17-11-2024 21:49:16 > Sending has been rejected because the sender you used listmember(a)gmail.com > is not valid. Validate your sender or authenticate your domain This appears to be something you need to do for the MTA at smtp-relay.sendinblue.com, or possibly something more is needed in /etc/postfix/sasl_passwd. > #SMPT Relay Brevo > relayhost = [smtp-relay.sendinblue.com]:587 > smtp_sasl_auth_enable = yes > smtp_sasl_security_options = noanonymous > smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Mailman3 upgrades

by Stephen J. Turnbull

dancab(a)caltech.edu writes: > "Loading failed for the <script> with source > “https://mailman3.caltech.edu/static/hyperkitty/libs/jquery/jquery-1.10.1.min.js” > > Sure enough, I do not have that script. In fairly freshly updated sources, I have references to one or the other of > -rw-r--r-- 1 gunicorn root 117370 Oct 19 14:55 jquery-ui-1.10.3.custom.js > -rw-r--r-- 1 gunicorn root 58173 Oct 19 14:55 jquery-ui-1.10.3.custom.min.js in hyperkitty/hyperkitty/static/hyperkitty/libs/popper/popper.min.js.map hyperkitty/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bunudle.min.js.map hyperkitty/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js hyperkitty/hyperkitty/templates/hyperkitty/base.html The last file also refers to hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css My guess is all the files you listed are from a recent installation or upgrade, but somehow base.html didn't get upgraded. Based on the principle "always blame the user" ;-), I'd start by checking if our version is shadowed by your local version? Anyway, I bet the version number is wrong in base.html and if you fix that everything else will fall in line. If not, check if popper and boostrap are either older versions or perhaps shadowed by older versions somewhere. A word to the wise: grep(1)ing the .min.js.map files is not advised. They're huge and all one line it seems. Better to use an editor's search function.

4 years

[MM3-users] Re: Weird startup problem after upgrade

by Mark Sapiro

On 12/2/22 08:21, Odhiambo Washington wrote: > I am facing an odd situation in which MM3 doesn't start successfully on > reboot, but I can start it manually. > This is a venv install. > This started after I did an upgrade (pip install --upgrade mailman > postorius hyperkitty mailman-hyperkitty) followed by the requisite > collectstatic|compress|compilemessages|migrate > post-update commands. Was the venv activated when you ran pip? You should also include django-mailman3 and mailmanclient in the packages to be upgraded although they are dependencies and "should" upgrade anyway. Also, at least one person has noted that --force-reinstall was required to get all dependencies upgraded <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > Secondly, it appears that the upgrade did NOT change the versions for the > upgraded components - postorius=1.3.6, hyperkitty=1.3.5, > Mailman Core Version=3.3.5. I was expecting the version to all bump up to > the latest. What does `pip freeze` in the venv show for versions? > Thanks in advance for any insights into what could be causing this. How do you start it manually? `mailman start` or `systemctl start mailman3`? What's the content of /etc/systemd/system/mailman3.service? -- 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: Installing Mailman3 under a Python Virtual environment running on RHEL9

by Odhiambo Washington

On Wed, May 22, 2024 at 6:17 PM Andy Macheta <andy.macheta(a)gmail.com> wrote: > Hi Odhiambo, > Well; looks like I'm much further on thanks to your tips - thanks!! > > So now I can get my local web browser pointing at > http://localhost:8000/mailman3/lists/ and I can see my test list. > But, the webpage does not seem right, i.e. the text has loaded but not the > images and wondering if anyone has any tips on how to resolve. > > I've checked ownership/group ownership of the /opt/mailman/web/ directory > and sub-directories and all is owned by mailman:mailman which I ?think it > should be. Not sure what else to check/do as definitely not a web developer. > The web pages have already been developed for you :-) What webserver are you using? Hopefully you can check the general log or you could log requests/errors specifically for your virtualhost and check those. Also try: venv> mailman-web clear_cache -- 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, 5 months

[MM3-users] Re: default language ignored

by Mark Sapiro

On 10/02/2017 05:46 AM, Marc Sluiter wrote: > Hi, > > one last question for now: how do switch the language of the mails sent by mailman? > I have this in my configuration, but without effect: > > [language.de] charset: iso-8859-1 > [language.de] description: German > [language.de] enabled: yes > > [mailman] default_language: de It has no effect because there are as yet no translations in Mailman 3. You need to create templates in the desired language. See <http://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html> That refers to setting URLs for templates which does work, but the easiest way is to put them in the default search path in Mailman's file hierarchy at $var-dir/templates/. Sitewide ones in $var-dir/templates/site/, Domain specific in $var-dir/templates/domains/ and list specific ones in $var-dir/templates/lists/. For example, a list specific, English language regular (non-digest) message footer might go in $var-dir/templates/lists/mymaillist.example.com/en/list:member:regular:footer > Is it also possible to change the language for a single list? Yes, although that is not yet exposed in Postorius. The list has a preferred_language attribute which you can set via REST or 'mailman withlist' aka 'mailman shell'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Stephen J. Turnbull

Peter Münster writes: > On Thu, Sep 01 2022, Stephen J. Turnbull wrote: > > I'm not very familiar with Django's handling of such files, > > I don't think, that Django is involved here. Ah, you're right. My GSoC student is working on Postorius so I have Django on the brain. > My language setting is "fr", so I've copied templates/site/en > templates/site/fr and now it works. > > So no real problem, but the question remains: why did it not work > with "en"? The template to be used is determined by the language setting of the user, or the default if the user is anonymous. You have to repeat the process with all of the templates that might be used on your system due to users' language settings. Presumably it *would* have worked for any user whose language setting was "en". But if you do have "de" users, you'll need to replace the "de" template as well. If you mean that you switched your language setting to "en" or have an "en" user, and tested it, we can take a look at it, but as I understand the situation, you have a "fr" setting so you saw the "fr" template. Steve

3 years, 2 months

[MM3-users] Re: Retrieve users from a list

by Odhiambo Washington

On Tue, Feb 6, 2024 at 5:40 PM <pau.baiges(a)csuc.cat> wrote: > A moderator has deleted all the users from a list, is there a way to > recover them? > Adding my 0.1 cents. If all options fail, you can fall back to your MTA logs. 1. Look for a recent post to that list. 2. Head over to the MTA logs. 3. grep for the subject of that recent post from the mainlog or whatever you call it. In Exim we generally call it mainlog (or main.log). If you were logging subjects, then you can tie the subject to the recipients of the mail. Everyone logs the recipient details, right? And we keep logs for at least a month, no? I do. Once you get the file resulting from the grep, you can use some regexp or text manipulation tools to extract all the addresses that the post was sent to. It looks not too difficult from Exim mainlog. Not sure about Postfix and other MTAs. I am very sure this will give you the list of subscribers. -- 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, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello, This is what I've got in /var/lib/mailman/var/data: [root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 100 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db -rw-rw---- 1 mailman mailman 315 Jul 24 10:41 postfix_domains -rw-r----- 1 mailman mailman 12288 Jul 24 10:41 postfix_domains.db -rw-rw---- 1 mailman mailman 318 Jul 24 10:41 postfix_lmtp -rw-r----- 1 mailman mailman 12288 Jul 24 10:41 postfix_lmtp.db What should be the next step? El dom., 23 jul. 2017 a las 20:22, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 06:00 PM, Rafael Mora wrote: > > Hello guys, > > > > This is what I've got on ../var/data: > > > > [root@localhost data]# pwd > > /var/lib/mailman/var/data > > [root@localhost data]# ls -l > > total 76 > > -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db > > > > > > What should I do in order to let mailman install the DB files? > > > Run > > bin/mailman aliases > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

[MM3-users] Re: Mailman3 on FreeBSD

by Mark Sapiro

On 08/12/2017 04:51 PM, Barry Warsaw wrote: > On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> wrote: >> >> On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however I don't >> see any indication as to what I should put in this file and if it was in >> /usr/local/etc/mailman.cfg then how would mailman find it? > > It wouldn’t by default. Right now Mailman does not search for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult change to add. I’m not sure whether that would makes sense as a general default or not. I’m not up on the FreeBSD conventions and standards here; can you explain why /usr/local/etc is preferred over /etc on that distro? I was hoping Abhilash would chime in here, because I think John is using the docker image and there's probably a specific path for mailman.cfg. As far as what goes in it, it could even be empty if you want to accept all the defaults, but you probably want at least [mailman] site_owner: real_person(a)example.com I expect if you do find -name mailman.cfg in your installation, you'll find at least examples. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: mailman3 admin from mailman2 & File location questions

by Mark Sapiro

On 11/3/21 1:38 PM, bob B wrote: > Question1 > We use help users with list settings, so we would log into mailman2 with the master password. So what is the best way to duplicate this for mailman3. I assume I can just use the admin account and share that password with my other admins. But I see the domain owners, but is that working? I added someone as a domain owner, and they do not see private email lists and it looks like that can not edit any list settings? There was a post that this had not yet been implemented? Any other options? Domain owners should be able to manage lists in their domains, but currently they can't. You can go to the Django admin interface and give any user superuser status, and then they will be 'admins'. You don't have to share passwords. > Question2 > Where are all the emails/archives stored? are they in /opt/mailman/...., or are they in the database? It depends on the archiver. For the prototype archiver they are in the archives/prototype/ directory in Mailman's var directory. For HyperKitty they are in the database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Archive search failing on one list

by Mark

On 2023-09-24 13:28, Mark Sapiro wrote: > On 9/23/23 19:19, Mark wrote: >> >> Yes, the query returns a result and the case in "name" matches that in >> the query ... >> >> select * from hyperkitty_mailinglist where name like >> 'listname(a)domain.com' >> >> id | 91 >> name | listname(a)domain.com >> display_name | Listname >> description | ... >> subject_prefix | [Listname] >> archive_policy | 1 >> created_at | 2023-09-21 08:55:36.385239+2 >> list_id | listname(a)domain.com > > Is that really what you get for list_id? It should have a dot, not at > as listname.domain.com. > > What if you do something like the following where django-admin is > whatever command you use for the Django admin command. > ``` > $ django-admin shell > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models.mailinglist import MailingList >>>> mlist_name = 'listname(a)domain.com' >>>> mlist = MailingList.objects.get(name=mlist_name) >>>> mlist > <MailingList listname(a)domain.com (listname.domain.com)> >>>> > ``` My bad. I was in too much of a hurry when redacting. The list_id is as you say: listname.domain.com

2 years, 1 month

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/21/23 09:58, Mark Sapiro wrote: > You can verify this by activating your > venv and doing > ``` > >>> MAILMAN_REST_API_USER > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > NameError: name 'MAILMAN_REST_API_USER' is not defined > >>> MAILMAN_REST_API_USER > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > NameError: name 'MAILMAN_REST_API_USER' is not defined > >>> MAILMAN_REST_API_PASS > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > NameError: name 'MAILMAN_REST_API_PASS' is not defined > >>> from mailman_web.settings.mailman import * > >>> MAILMAN_REST_API_USER > 'restadmin' > >>> MAILMAN_REST_API_PASS > 'restpass' > >>> > ``` Omitted in the above was invoking Python as in ``` (venv) mark@msapiro:~$ python Python 3.9.16 (main, Dec 11 2022, 12:49:23) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> MAILMAN_REST_API_USER etc, as above ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Any suggestions over my earlier email? I am waiting for your reply. <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> On Tue, Oct 27, 2020 at 1:16 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Hi Mark, > > Thank you for your help. I have traced the versions of > different components of mailman 3. I am downloading through GIT LAB because > I need to modify the code according to my organization's requirements like > to add SMS notifications when a mail is waiting for pending approval and so. > > With your help, I have found out the commits I am using in my > environment. I got them using the way you suggested "git log". That may be > helpful for you to help dummies like me. > > *### Mailman Core Version ###* > > *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* > *Merge: 98cf97b 0bca998* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Thu Oct 15 14:02:36 2020 -0700* > > * Merge branch 'template' into 'master'* > > * Clarify the posting instruction in the list welcome message.* > > * See merge request mailman/mailman!723* > > *### django-mailman3 Version ###* > > *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* > *Merge: ea2b33a c091e43* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:40:51 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/django-mailman3!108* > > *### Hyperkitty Version ###* > > *commit 36f43466763c2686cf4d69c982ea64b956c30939* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Mon Oct 5 04:54:44 2020 +0000* > > * Use GH registry to pull CI image.* > > *### Mailmanclient Version ###* > > *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* > *Merge: ff39dd8 8670751* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 01:09:32 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/mailmanclient!130* > > *### Mailman Hyperkitty Version ###* > > *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* > *Merge: 35ff801 04deff5* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Fri Jun 19 18:15:57 2020 +0000* > > * Merge branch 'fix_25' into 'master'* > > * Add a test for the presence of surrogates in the stringified message.* > > * Closes #25* > > * See merge request mailman/mailman-hyperkitty!7* > > *### Mailman-suite Version ###* > > *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* > *Merge: 74e7927 4463b31* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Sat May 30 00:32:40 2020 +0000* > > * Merge branch 'doc_mb4' into 'master'* > > * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* > > * See merge request mailman/mailman-suite!8* > > *### Postorius Version ###* > > *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* > *Merge: 61242d2 321310c* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:43:14 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use the GHCR registry for CI image.* > > * See merge request mailman/postorius!549* > > I have removed only mailmanclient and re-cloned it from gitlab and > ran the python setup.py develop command. But still the same error. > > Is there anything else I can do to get rid of that error. > > Thanks in advance. > > > <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…> > <#m_6854939421424022049_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Tue, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: >> > >> > How to find out the versions of the each and every component >> > of the mailman 3 like mailman core, mailmancilent, postorius, >> > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, >> > after installation? >> >> >> cd to the directory in which you cloned the gitlab project for the >> component and do `git log` >> >> >> > If I am running an old mailmanclient or older version of any >> > other mailman component, please suggest how to upgrade either one or >> > multiple components based on the requirement. Is there any link that >> > would help me to upgrade ? >> > >> > I have used the >> > link https://docs.mailman3.org/en/latest/devsetup.html to install the >> > mailman 3 components. I expected that the procedure followed in this >> > link would install the latest versions of the mailman 3 components. >> > Please correct me if I am wrong. Is there any latest version >> > compatibility table ? >> >> >> If you installed each of mailman, mailmanclient, django-mailman3, >> postorius and hyperkitty according to instructions like >> >> $ cd ~/mailman >> $ git clone https://gitlab.com/mailman/mailmanclient.git >> >> Then set up mailmanclient: >> >> $ cd mailmanclient >> $ python setup.py develop >> $ cd .. >> >> from that document, you should have the latest version. If that is the >> case, `git log` in the mailmanclient directory should begin like >> >> commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, >> origin/master, origin/HEAD) >> Merge: ff39dd8 8670751 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Thu Oct 15 01:09:32 2020 +0000 >> >> Merge branch 'fix-ci' into 'master' >> >> Use GHCR for the CI image >> >> See merge request mailman/mailmanclient!130 >> >> commit 8670751caff689733751ef323ef521c4a3fa1237 >> Author: Abhilash Raj <raj.abhilash1(a)gmail.com> >> Date: Wed Oct 14 17:36:58 2020 -0700 >> >> Use GHCR for the CI image >> >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> Merge: 80ebed4 76d44e1 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Fri Aug 7 19:35:05 2020 +0000 >> >> Merge branch 'invite' into 'master' >> >> Add support for inviting an email address to join a list. >> >> See merge request mailman/mailmanclient!129 >> >> or if you did this before Oct 15, maybe it starts with >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> >> The particular commit you need for your issue is >> >> commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 >> Merge: c8dcb1e 28d1c3a >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Sat May 16 08:02:21 2020 +0000 >> >> Merge branch 'held-count' into 'master' >> >> Add a new get_held_count() API to get a count of held messages. >> >> See merge request mailman/mailmanclient!122 >> >> >> >> Note that unless you intend to do actual development of Mailman 3, you >> should be following >> <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather >> than <https://docs.mailman3.org/en/latest/devsetup.html>. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years

[MM3-users] SQL Schema request

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > Is there any way to get a copy of the mysql/mariadb table schema that I > can then pour the existing data into (i.e. I don't want to reinitialise > the db)? I suspect you alread know this, but the backend database schema is entirely implicit in the SQLAlchemy models. There is no function in Mailman to dump out the backend schema, although SQLAlchemy may have one. AAAAaaaannnnddd ... bingo! https://docs.sqlalchemy.org/en/14/faq/metadata_schema.html#how-can-i-get-th… Don't know if that does what you need, but it's the best I can come up with without reading tons of code. :-) There's probably a similar function that allows you to dump all the data in an SQLAlchemy-specific format that you can load back in to a different backend and SQLAlchemy will do the schema translation. Also, have you considered that Django keeps an independent set of tables for HyperKitty and/or Postorius? Same comments apply, except that Django has its own ORM. https://docs.djangoproject.com/en/3.2/ref/django-admin/#dumpdata Finally, don't the backend databases have some sort of "dump schema" command? That might be more useful. Note that I got lucky (yay, Google-fu!) with "DBM dump schema" on the first try so "dump" seems to be the right search term.

4 years

[MM3-users] Re: Unable to get mailman3 working on Ubuntu 20.04 LTS

by Shawn Heisey

On 10/27/2021 9:51 PM, John Covici wrote: > I am interested in your docr instructions. I don't use postfix, > instead I use sendmail, but I think I can figure that out, but I have > been having lots of problems installing without docr, and I do have > apache, so this would be great. Send off list if you think that would > not be of general use. The instructions found here are most of what is needed: https://github.com/maxking/docker-mailman/#running Here's the issue where I provided my Apache config: https://github.com/maxking/docker-mailman/issues/525 For each of my mailing lists, I created the list and then imported a mailman 2.1 config. I had problems with the footer being appended to list messages ... it took me a while to figure out how to fix that! You have to delete the footer config file, restart the container, and then if the resulting default footer is insufficent, use the admin web page to redefine it. Instructions for exim and postfix are included on the project page. I haven't used sendmail in many years, so I wouldn't have any idea how to get that working. Even when I was using it, I found the config to be extremely arcane and difficult. Thanks, Shawn

4 years

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, I forgot to mention that, but there is no mailman-web on ubuntu packages on 18.04. So I can't find a way to run it. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 14 Dec 2023 at 18:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/23 10:19, Jered Floyd wrote: > > > > Did you run the upgrade steps? > > > > https://docs.mailman3.org/en/latest/upgrade-guide.html > > > > For schema upgrades you will at least need to do "mailman-web migrate", > but please read the entire section as 3.1.1 to 3.3.9 is a big step. > > > These are all important and necessary steps, but "mailman-web migrate" > updates schemas for the mailman-web database. It does not update the > alembic migrations for the mailman database. > > -- > 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 helio(a)loureiro.eng.br >

1 year, 10 months

[MM3-users] Re: mailman import21 passwords

by Mark Sapiro

On 9/16/24 16:25, Sam Darwin via Mailman-users wrote: > > Why can't passwords be imported from mailman2 to mailman3? How difficult would it be to do? > (is there a link to where this is already explained? ) Mailman 3 users have a _password attribute which isn't actually used for anything. The importer used to set this from the MM 2.1 member's password, but this was dropped by <https://gitlab.com/mailman/mailman/-/merge_requests/565>. See <https://mail.python.org/archives/list/mailman-developers@python.org/thread/…> for a discussion of this. Also note that since member passwords were stored in plain text in MM 2.1 and periodically emailed, those passwords are inherently not secure and have possibly been exposed so setting that password, even though encrypted in MM 3, is not a good idea. As far as creating a Django user for an imported member, whether or not with the member's MM 2.1 password, it is at least as expensive as just encrypting the password and would result in poor performance. Further, and perhaps more importantly, Mailman 3 is modular. There is no guarantee that any Mailman Core installation into which a MM 2.1 list is imported actually also supports Django users for Postorius and/or HyperKitty. -- 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: How to limit numbers of outgoing emails per connection

by Jeremy Stanley

On 2025-02-10 12:57:24 +0000 (+0000), Alain D D Williams wrote: > Exim tells me "no immediate delivery: more than 30 messages received in one connection" > > The emails then sit in the exim queue until a queue runner kicks in - which > happens once every 30 minutes. The result is considerable delays which makes > list email conversations bouncy. > > Question: how do I tell MM3 to send no more than 30 emails in one connection to > exim (via SMTP to localhost port 25) ? [...] There are corresponding configuration options in Mailman and Exim, where you need to make sure that the batch size used by the former is less than the limit set for the latter. In your mailman configuration (we use a mailman-extra.cfg in our deployment to selectively extend the default mailman.cfg) add a `[mta]` section with a `max_recipients: some_integer_value` line. This value needs to be explicitly less than the `smtp_accept_queue_per_connection` global setting in your exim4.conf file. It seems to me that the config option in Exim is poorly named and documented, as I've observed that batches of exactly `smtp_accept_queue_per_connection` result in queued processing rather than immediate delivery, which is why `mta.max_recipients` must be strictly less, not set equal to it. Hope that helps! -- Jeremy Stanley

8 months, 3 weeks

[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

7 years, 1 month

[MM3-users] Re: New Mailman 3 installation issues

by Mark Sapiro

On 5/19/21 11:50 AM, Sarah H wrote: > Hi Mark, > > I wanted to make another note on the documentation, the migration documents (https://docs.mailman3.org/en/latest/migration.html#fn2) reference using > > 'python manage.py hyperkitty_import' > > it should be > > 'mailman-web hyperkitty_import' That is a can of worms. It all depends on how you installed Mailman 3. If you follow the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html, the django management command will be `mailman-web`, but installation in other ways can result in its being `manage.py` or `django-admin` or almost anything. For example, https://docs.mailman3.org/en/latest/pre-installation-guide.html#what-do-i-n… refers to a typical Django project in which the management command is `manage.py`. https://docs.mailman3.org/en/latest/config-web.html is inconsistent in itself in that it uses `mailman-web` in most places except the note about qcluster at https://docs.mailman3.org/en/latest/config-web.html#running-the-task-queue which also links to http://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks which uses `django-admin`. I'm thinking that we should put a note about this near the top of https://docs.mailman3.org/en/latest/ and let it go at that. -- 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: Block members from sending cc's and bcc's

by Mark Sapiro

On 7/18/25 5:37 PM, Cathryn McGuire wrote: > > The .* pattern did not do the job of blocking cc's and bcc's in the Header Filters of Affinity. It lets them go through, even as hold for moderation has been chosen. First, you can't filter on Bcc because Bcc is removed from the message before being sent. That's the whole point of Bcc. In otherwords, if I mail To: the list with Bcc: to others, the list never sees that Bcc: header and can't filter on it. As far as Cc is concerned, if in Header filters you have a rule with 'cc' in the header box and '.*' in the pattern box, the action box action should be applied to any message with a Cc: header. > I've asked EMWD to advise me because I think Affinity is very new, even though Brian Carpenter was developing it in 2020, is that correct? Affinity is not new, but it is a proprietary product of EMWD. If you have set the header filter as above and it is not working, only EMWD can help with that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: Trying to configure a list (hosted)

by paul＠arenson.org

I guess my message wasn't clear? Let me try again. I have not made any list settings or sent mails because I do not want my archive filled with a lot of test mails. I am simply trying to understand a) why there are supposed to be two ways to sign up--one where you just get the messages by email and one where you are able to interact with the archives and send from the web interface. Example, as seen here---> https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… 1) I was told that Subscription / Unsubscription lets you truly register and that just below that 2) "You can also subscribe without creating an account" lLets you just receive emails but not interact with the archives.post from the web. CONFUSION --> Aside from the confusing use of "subscribe/subscription for both, when I tried testing both options, BOTH sets of emails ended up in my members list. If there is a guide (I was told it is not ready), it would help, but anyway: 3) Can anyone help me understand the problem above? 4) Will it go away if I enter my settings? Will my users (this who truly register with a password) be able to get the archives and post from the interface? The next post is about the other issue:

6 years, 2 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by megabrutal＠gmail.com

> Is your login a member of the list? It's supposed to be – when I click „Manage subscription” in the very same thread, it reveals that I'm subscribed. This is why I can't subscribe again. Yet I still can't post from HyperKitty, however I can by e-mail. However, when I checked the member list, I also found my address as a „nonmember” (besides being listed as „member” too). I removed myself as „nonmember”, but I still can't post to the list from HyperKitty. It looks like if HyperKitty would try to use a different „token” when I try to post to the list than the one it shows when I manage my subscription. > How did you add that email? When you find yourself at > https://example.com/mailman3/users and click Manage, do you see the > expected addresses? Yes! I see three of my addresses, actually. > This is normal. Hyperkitty lists participants by address whether or not > the addresses are linked to the same user. Yes, that's right, but I see the very same addresses listed twice, when in reality I only posted with 2 different addresses (of which the second is an entirely different account that by the way can post through HyperKitty).

6 months, 4 weeks

[MM3-users] Re: Whitelist non subscriber

by Stephan Krinetzki

Mark Sapiro wrote: > On 08/06/2018 06:43 AM, Stephan Krinetzki wrote: > > > The steps are as follows, right? > > - Add users to the list and give the role "nonmember" > > - Set moderation action ('defer' or 'accept') > > Right. Good. So i understand it :) > > > > The only thing missing in the documentation is a note on how to do > > this via the Admin API. Who can explain that to me? > > Can you be more specific about what you are looking for? If by "Admin > API" you mean the REST API, are you asking how to interact with it or > what specific POST/PUT/PATCH commands to send? > > Or are you asking about the 'mailman shell' command? > With Admin API I mean the REST API from the localhost. Whether it's the REST API, the Mailman shell or the Admin API, I personally don't care. The only important thing is that we can set and use this role. However, I think that's settled anyway, since you're writing > > Also, we want to expose the nonmember role in Postorius and enable > setting moderation action for nonmembers, but we didn't get that in MM > 3.2/Postorius 1.2. So the whitelistening is not working at the moment, right?

7 years, 2 months

[MM3-users] Re: Specifying hold reason: non-member, header filter number/regex

by Duane Raymond

> This is because in the chain of rules being tested for the post, the header matching rules are tested before non-member moderation. <snip> > For this one, member moderation holds come before header matches, so I think your issue is only for non-members. If you want that check to come first reorder these lines Great - I'll take that approach and see how it goes and then might tinker with the code so it isn't just a simple first-come-first-server result but can tell me if it matches both a non-member/moderated member filter and a header filter. I'll share for peer feedback and testing (since I'm new to this) as I go. I guess I should join the developers list for this or more just fork the code, make changes and make a merge request? > You've seen the code and the comments in mailman/chains/headers.py. We would welcome a merge request to implement this. I'll give it a go :-) I might need some guidance for my first contributions....but should improve from there as get familiar with the code base and making changes (coding isn't my day-job but I seem to do a lot of hacky stuff for myself so can keep learning). Cheers, Duane

4 years, 7 months

[MM3-users] Re: Archive import fails: "IndexError: list index out of range"

by Mark Sapiro

On 1/4/24 9:42 PM, Stephen J. Turnbull wrote: > Dan Caballero writes: > > > I've got a message that keeps getting re-queued to the > > /hyperkitty/spool/ folder. > [...] > > "During handling of the above exception (expected atom at a start > > of dot-atom-text but found > > '[1db292f04b54496ab40544b0989a2122-JFBVALKQOJXWILKNK4YVA7CPNZSVMZLUPRCW2YLJNRKGK43UPRCXQ32TNV2HA===(a)microsoft.com]>')" > > This is arguably a HyperKitty bug. The email package is correctly > refusing to parse that as a Message-ID (it's been illegal syntax since > RFC 822 if I remember correctly), but something, presumably > HyperKitty, should catch the error and do something to sanitize it to > message-id syntax. On the other hand, I never heard of a message > trigger that exception before a couple months ago, so maybe it's the > responsibility of spam filters. This is <https://gitlab.com/mailman/mailman/-/issues/1065> fixed in Mailman 3.3.9 by <https://gitlab.com/mailman/mailman/-/merge_requests/1099>. > In a later post you say that message came back, but I suspect it isn't > the same message, but a new one likely from the same source. I agree. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Hyperkitty Missing Theme/Style Sheets?

by Abhilash Raj

Hi Andrew, On Wed, Nov 1, 2017, at 12:43 PM, Andrew Hodder wrote: > Well, that can't be true, I'm running DEBUG = False and Django is > certainly > trying to provide static files (as you'll see below): > > I found the issue in the nginx logs (it's connecting to both postorius > and > hyperkitty via uwsgi), it appears when I'm only viewing Hyperkitty's > pages, > I'm getting these type of errors (some changes inserted to hide my server > details): > > 2017/11/01 19:22:04 [error] 64082#0: *75 open() "/opt/mailman/postorius/ > example_project/static/CACHE/js/4ce1260ef558.js" failed (2: No such file > or > directory), client: 10.10.44.29, server: blah.blah.blah, request: "GET > /static/CACHE/js/4ce1260ef558.js HTTP/1.1", host: "blah.blah.blah", > referrer: "https://blah.blah.blah/hyperkitty/hyperkitty/list/ > mailinglist(a)domain.com/2017/10/" I see here that you are running Postorius and Hyperkitty a bit differently that presented in our docs. Settings inside example_project for each repositories are just examples, we use it for testing, and may not work best in production. We recommend that you instead use the mailman-suite[1] to run Postorius & Hyperkitty using a single Django installation. The process for doing so is documented here[2]. [1]: https://gitlab.com/mailman/mailman-suite [2]: http://docs.mailman3.org/en/latest/prodsetup.html#installing-web-ui > So it appears Hyperkitty is attempting to load static files from > postorius's side instead of it's own (I have postorius running under > https://domain.tld and hyperkitty running under > https://domain.tld/hyperkitty/ via nginx). I checked and confirmed the > variables in settings.py: > > STATIC_ROOT = os.path.join(BASE_DIR, 'static') > STATIC_URL = '/hyperkitty/static/' > STATICFILES_DIRS = ('/opt/mailman/hyperkitty/example_project/static/') > > And for good measure, here's the nginx config: > > ------------------------------ > > > > server { > listen 80; > server_name DOMAIN.TLD; > #Redirect to SSL > if ($scheme = http) { > return 301 https://$server_name$request_uri; > } > } > > server { > listen 443 ssl http2 default_server; > listen [::]:443 ssl http2 default_server; > server_name DOMAIN.TLD; > > ssl_certificate "/etc/pki/nginx/DOMAIN.TLD.crt"; > ssl_certificate_key "/etc/pki/nginx/private/DOMAIN.TLD.key"; > ssl_session_cache shared:SSL:1m; > ssl_session_timeout 10m; > ssl_ciphers HIGH:!aNULL:!MD5; > ssl_prefer_server_ciphers on; > > location / { > include uwsgi_params; > uwsgi_pass unix:/opt/mailman/postorius.sock; > } > > location ~ /hyperkitty(?<path_info>/.*|$) { > include uwsgi_params; > uwsgi_pass unix:/opt/mailman/hyperkitty.sock; > uwsgi_param PATH_INFO $path_info; > uwsgi_param SCRIPT_NAME /hyperkitty; > } > > #Make nginx aware of postorius static > location /static/ { > alias /opt/mailman/postorius/example_project/static/; > } > > #for hyperkitty static > location /hyperkitty/static/ { > alias /opt/mailman/hyperkitty/example_project/static/; > } I believe static files are all supposed be rooted at `/static` instead of `/hyperkitty/static`. > > error_page 404 /404.html; > location = /40x.html { > } > > error_page 500 502 503 504 /50x.html; > location = /50x.html { > } > } > > Any thoughts would be appreciated, I'm getting stumped on this one. I have never tried to run 'example_project' in production before, so I am not exactly sure about the reason. This seems overly complicated and I strongly recommend that you run Postorius and Hyperkitty from a single installation, unless you have a very good use case to run them separately. > > > Sincerely, > > Andrew Hodder > Systems Administrator > Support Operations, Afilias > E-mail: drew(a)afilias.info > Phone: +1 416.673.4164 > Fax: +1 416.646.1541 > > On Fri, Oct 27, 2017 at 11:01 AM, Simon Hanna <simon(a)hannaweb.eu> wrote: > > > > > On 10/27/2017 04:58 PM, Andrew Hodder wrote: > > > >> Sure thing: > >> > >> https://imgur.com/a/EXv3B > >> > >> Looks like your stylesheets aren't loaded. > > > > if you are running in production (with DEBUG=False) django won't serve > > static files > > You need to configure your webserver to do that. > > You need to make sure to load all the static files using > > `python manage.py collectstatic` > > to gather everything and put them in one directory that can then be served > > by your webserver > > > > > > > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years

[MM3-users] Re: Mailman3 via Docker and NGINX

by Hagen Bauer

is this the complete sitename.conf? I had a situation where I had a location / definition for caching before the mailman one. On 19.12.18 16:03, brian(a)emwd.com wrote: > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. > > It seems I am stuck with the nginx setup. I created a sitename.com.conf file in the /etc/nginx/conf.d folder. I have the following inputted there: > > server { > listen 80; > server_name `sitename.com`; > > location /static/ { > alias /opt/mailman/web/static/; > } > > location / { > include uwsgi_params; > uwsgi_pass 172.19.199.3:8000; > uwsgi_read_timeout 300; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > } > > However when I go to http://sitename.com (obviously using an alias here for privacy reasons) I get the default nginx index page. Do I need to add anything to the main nginx.conf file to be able to see my mailman3 installation? > > Thank you for any assistance, > Brian Carpenter > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 10 months

[MM3-users] Re: Issues installing postorius and hyperkitty

by Mark Sapiro

On 10/23/19 6:43 AM, thushantha.lakmal(a)arm.com wrote: > Hi All. > > Im trying to install the mailmain suite with the postorius and hyperkitty . Mailman installation completed successfully but for postorius and hyperkitty Im getting the following errors .. > > Please can someone help me .. > > > > For postorius (Using pip3 install postorius ) > > ERROR: django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have django 2.2.6 which is incompatible. How is Django 2.2.6 installed? If you are only using Django for Mailman (Postorius and HyperKitty), just do pip3 install Django<2.2 > For hyperkitty (Using pip3 install hyperkitty ) All of the below is saying that the install of hyperkitty is trying to install rcssmin, that in turn requires building '_rcssmin' extension which requires gcc. Do you have some other C compiler not named gcc? If so, you might be able to work around this by creating a symlink to your C compiler from /usr/bin/gcc, but it would be better to install gcc using apt, rpm, or whatever your package manager is. > > de41118f448bcb3b8df405c5228e1 > Stored in directory: /root/.cache/pip/wheels/79/50/a5/9410f4b2e62e35c285de46ffa88c2562403cb576e1e7859d68 > Building wheel for rcssmin (setup.py) ... error > ERROR: Command errored out with exit status 1: > command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-491rzr5s --python-tag cp36 > cwd: /tmp/pip-install-563o314q/rcssmin/ > Complete output (12 lines): > running bdist_wheel > running build > running build_py > creating build > creating build/lib.linux-x86_64-3.6 > copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 > running build_ext > building '_rcssmin' extension > creating build/temp.linux-x86_64-3.6 > gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o > unable to execute 'gcc': No such file or directory > error: command 'gcc' failed with exit status 1 > ---------------------------------------- > ERROR: Failed building wheel for rcssmin > Running setup.py clean for rcssmin > Successfully built robot-detection django-haystack > Failed to build rcssmin > Installing collected packages: rjsmin, django-appconf, rcssmin, django-compressor, robot-detection, django-haystack, djangorestframework, decorator, networkx, django-extensions, wcwidth, blessed, arrow, django-picklefield, django-q, hyperkitty > Running setup.py install for rcssmin ... error > ERROR: Command errored out with exit status 1: > command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile > cwd: /tmp/pip-install-563o314q/rcssmin/ > Complete output (12 lines): > running install > running build > running build_py > creating build > creating build/lib.linux-x86_64-3.6 > copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 > running build_ext > building '_rcssmin' extension > creating build/temp.linux-x86_64-3.6 > gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o > unable to execute 'gcc': No such file or directory > error: command 'gcc' failed with exit status 1 > ---------------------------------------- > ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile Check the logs for full command output. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Failed first login

by Mark Sapiro

On 8/31/20 6:59 AM, Massimo Zappalà wrote: > Hi everyone, > i installed mailman3-full on debian 10. > During installation, it asks me to enter the admin user credentials. > After configuration, I restart mailman3 and mailman3-web. > When I try to log in for the first time by entering the admin credentials, a message warns me that the credentials are incorrect. > I looked at the mailman logs, but I find nothing. > It seems that it is a django authentication problem, because even in the django admin panel I can't log in. > Looking at the mailman3web db, in the auth_user table, I see the admin user. > How can I see why it does not accept the credentials? > Thank you in advance I have no idea what the Debian package is doing, but you can see the superuser(s) with the database query select * from auth_user where is_superuser; and you can change the user's password with the django admin changepassword command and/or create a superuser with the django admin createsuperuser command. Give the commands with a --help option for more info. Since you can see the user in the auth_user table, try the django admin changepassword command to change the password. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Abhilash Raj

> On Mar 27, 2021, at 3:03 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/27/21 2:08 PM, Brian Carpenter wrote: >> I was testing out the process of rejecting an incoming subscription >> request. Choosing the reject option for a moderated subscription request >> does send out a rejection notice but it gives no reason for the >> rejection. > ... >> Is there a place somewhere in Postorius to provide a rejection reasons >> for moderated subscription requests? Does Mailman 3 core provide this >> via its REST api but it is just not revealed in Postorius yet? > > > It's in Postorius since 1.3.3. If in the held message view, you click > the subject of a held message, you get a popup dialog the shows the > message with options to also show headers or the raw message. There is > also a dropdown t=o set the poster's moderation action and a box for a > reject reason if you click the reject button in the dialog. > > Do you not see this? I guess Brian was asking about Subscription Requests. Support for specifying reason when rejecting subscription requests has been added in master and will be a part of next release, 1.3.5 most probably. -- thanks, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/5/24 07:04, Odhiambo Washington via Mailman-users wrote: > I am having an ugly-looking https://mm3-lists.kictanet.or.ke/archives/ page > because of cached content: > > ``` > 2024/08/05 17:00:31 [error] 694#694: *9562 open() > "/opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No > such file or directory), client: 172.70.111.39, server: > mm3-lists.kictanet.or.ke, request: "GET > /static/CACHE/css/output.6dab123e4897.css HTTP/2.0", host: " > mm3-lists.kictanet.or.ke", referrer: " > https://mm3-lists.kictanet.or.ke/archives/" > 2024/08/05 17:00:31 [error] 694#694: *9564 open() ... > That IP address appearing there is not my actual IP, but Cloudflare's, > which is acting as proxy for the site. I **think** you may have something like location /static/ { alias /opt/mailman/web/static/; } in nginx on cloudflare, but since cloudflare is not the Mailman server, /opt/mailman/web/static/ doesn't exist there. I can't be sure on how to configure this without knowing the details of how requests get from cloudflare to mm3-lists.kictanet.or.ke and from there to the wsgi server. However, if cloudflare just proxies the request for /static/ to the Mailman server and nginx on that server has the above `location` directive, that may do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Postorius admin/user guide

by Odhiambo Washington

On Fri, Nov 8, 2024 at 5:55 PM Florin Pasăre via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hello, > We're trying to update mailman to version 3 from version 2, and I can't > seem to find some non-technical guide for Postorius, something like an > owners manual for all the configurations available in Postorius. > Is there such a thing? > > Thank you, > > Florin > Hi Florin, You cannot "update" Mailman from version 2 to version 3. You will install version 3 and then migrate your lists/archives from version 2 into the version 3 install. That, I think is an "upgrade". The recommended installation method is documented here: https://docs.mailman3.org/en/latest/install/virtualenv.html Once you've completed the installation, you need to create the superuser. The command is: ``` mailman-web createsuperuser ``` The username you create here will be used to log in to Postorius. You can also use the same username/password to login to the Django Admin web UI - https://list-url/admin/ What goes on in Postoirius isn't complex, so do not fear. -- 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]

11 months, 3 weeks

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Florian Schulze

On 29 Jun 2020, at 23:40, Mark Sapiro wrote: > On 6/29/20 1:38 AM, Florian Schulze wrote: >> Hi! >> >> After upgrading to HyperKitty 1.3.x I get the following error for >> qcluster: >> >> File ".../lib/python3.7/site-packages/django_q/cluster.py", line >> 300, >> in pusher >> task = SignedPackage.loads(task[1]) >> File ".../lib/python3.7/site-packages/django_q/signing.py", line >> 31, >> in loads >> serializer=PickleSerializer) >> File ".../lib/python3.7/site-packages/django_q/core_signing.py", >> line >> 38, in loads >> return serializer().loads(data) >> File ".../lib/python3.7/site-packages/django_q/signing.py", line >> 44, >> in loads >> return pickle.loads(data) >> AttributeError: Can't get attribute 'process_task_result' on <module >> 'hyperkitty.tasks' from >> '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> >> >> How do I recover from that? It seems like there are still persisted >> tasks in the qcluster queue using the old code from 1.2.x with the >> old >> locking implementation. > > Have you stopped ans started qcluster since upgrading? Yes > Are you running the Django periodic jobs? They were disabled because of the errors (someone else did the upgrade). I have enabled them again and will watch it and report back. Regards, Florian Schulze

5 years, 4 months

[MM3-users] Re: Update a member's display_name

by Mark Sapiro

On 7/8/20 11:08 AM, rongxinliu(a)cs50.harvard.edu wrote: > Hi Mark, I'm not the only developer on this list. > I would like to know if there is a way to update the display_name of the member in a mailing list via REST API? > > Having tried updating the display_name of a user but did not seem to work. The display_name did change, but the mailing list still displaying the old name. By "the mailing list still displaying the old name" do you mean the membership list in Postorius or something else? And to what REST endpoint did you post the display_name? The bottom line is a user can have multiple display names. Each user has a User record with a display_name attribute, one or more 'addresses', one of which is it's preferred_address. Each one of the addresses is an Address record with it's own email address and display_name. Now, a member of a list can be either a User or an Address. If it's a User, its display_name is that of the user and it's email address is that of the preferred_address, but if it's an Address, its email and display_name are those of the Address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: How to turn off Emergency Moderation for imported MM2 lists?

by Mark Sapiro

Mark Sapiro wrote: > On 7/28/20 5:40 AM, Brian Carpenter wrote: > > > > This is the client that I asking about in my post. > > She said what I > > did, did not work. This is what I did: > > > > Get into a venv as user mailman > > > > #mailman shell > > from mailman.model.mailinglist import MailingList > > mlist = MailingList('listname(a)listdomain.org') > > mlist.emergency = False > > commit() > > ctrl-d (just to be on the safe side) I half understand why this didn't work. Instantiating the list via ``` from mailman.model.mailinglist import MailingList mlist = MailingList('listname(a)listdomain.org') ``` for some reason (that's the half I don't understand) does not get the actual list object so changes you make to it don't affect the actual list. In `mailman shell` you need to do ``` mlist = getUtility(IListManager).get('listname(a)listdomain.org') ``` `getUtility` and `IListManager` are in the namespace in `mailman shell`, but outside of that, e.g. just in `python` in your virtualenv, you also need ``` from mailman.interfaces.listmanager import IListManager from zope.component import getUtility ``` -- 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: 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Prasanth Nair

Thank you, Stephen. Kind regards, Prasanth On Thu, 14 Oct 2021 at 17:04, Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Prasanth Nair writes: > > > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec > can't > > encode character '\ufffd' in position 252: ordinal not in range(128).* > > This is the Unicode REPLACEMENT CHARACTER, which means that something > along the line, possibly Mailman, could not decode some bytes, and > replaced them with that character. The message about "ASCII" codec > usually means that this occurred in the header of the email, which is > typical of spam. The message ID was generated by Mailman not by the > originating system, which is also indicative of spam. > > If it is spam, you can identify the message and delete it from the > archive. If it's not, you will need to find the text that is being > replaced and delete it or replace it with ASCII yourself. > > > I ran the check_hk_import script before migrating and it was not > > giving any error. > > In order to catch this kind of error, the check script would have to > pretty much do the import but throw it away. >

4 years

[MM3-users] Re: How to Personalise Email Content with Usernames in Mailman 3

by Mark Sapiro

On 11/17/23 07:03, Zaheer Abbas wrote: > Hello, > > I am currently working with Mailman 3 and looking to enhance the > personalization of the emails sent through our mailing list. Specifically, > I wish to include the recipient's username in the email content, similar to > a personalized greeting (e.g., "Dear [username]"). > > My questions are: > > 1. Does Mailman 3 support the inclusion of personalized data (like > usernames)? You can enable full personalization which will put the recipient's address in the To: header. In addition both Individual and Full personalization allow personalized information in message headers and footers, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…. This could be used to add a personalized header, but depending on the MIME structure of the message after content filtering, these may be added as separate MIME parts rather than prepended/appended to the message body. See https://wiki.list.org/x/4030707 for more on this. Mailman has no facility other than the above for modifying message bodies. > 2. If yes, how can I do that? Is there any placeholder for that? See the above links. -- 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 store additional information about lists?

by Stephen J. Turnbull

Andreas Barth writes: > Currently it is "list public" vs "subscribers only". I need something > inbetween, so that some (i.e. most) people have access to the > restricted audience lists but not just everybody. That much is clear. The problem is that "access to list" can mean a lot of things: can subscribe, can post, can admin, can view archives, can view list in listinfo, can view subscriber list, and there are probably others. What permissions are needed for what general classes of users? > Just as an idea, how about always one "custom attributes" field. So > that from a database pov this field is always there. We could do that, but then we'd have to support it. I'm thinking of situations like admin A populates the field, then leaves the organization, and we add (some of) the supported features, and admin B wants to migrate that. I don't see any good coming of that for us. As Mark says, a separate table seems like the way to go for custom attributes. > It could be done in postorius - the restriction that subscribing by > mail needs moderators action would be ok (or if it annoys me, this > part be move to a cron job). OK. I'll think about this. Steve

4 years, 5 months

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

by bob B

/opt/mailman/core/mailman-extra.cfg. now has #lmtp_host: localhost lmtp_host: 127.0.0.1 lmtp_port: 8024 But but mail log shows 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: DDF5D3083EC2: from=<user(a)user.com>, size=8181, nrcpt=1 (queue active) 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting) Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? ----------------------------- lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 ----------------------------- here is my docker-compose.yaml strip out -------------------------------- version: '2' services: mailman-core: image: maxking/mailman-core:0.3 container_name: mailman-core hostname: mailman-core volumes: - /opt/mailman/core:/opt/mailman/ stop_grace_period: 30s links: - database:database depends_on: - database environment: - DATABASE_URL=postgres://@@@######$:@@@######$@database/mailmandb - DATABASE_TYPE=postgres - DATABASE_CLASS=@@@######$.database.postgresql.PostgreSQLDatabase - HYPERKITTY_API_KEY=@@@######$ ports: - "127.0.0.1:8001:8001" # API - "127.0.0.1:8024:8024" # LMTP - incoming emails networks: mailman: mailman-web: image: maxking/mailman-web:0.3 container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - MAILMAN_ADMIN_USER=@@@######$ - MAILMAN_ADMIN_EMAIL=@@@######$@@@@######$ - SERVE-FROM_DOMAIN=@@@######$.@@@######$.org - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static - DATABASE_TYPE=postgres - DATABASE_URL=postgres://@@@######$:@@@######$@database/mailmandb - SECRET_KEY=@@@######$ - HYPERKITTY_API_KEY=@@@######$ ports: - "127.0.0.1:8000:8000" # HTTP - "127.0.0.1:8080:8080" # uwsgi networks: mailman: database: environment: - POSTGRES_DB=@@@######$ - POSTGRES_USER=@@@######$ - POSTGRES_PASSWORD=@@@######$ image: postgres:9.6-alpine volumes: - /opt/mailman/database:/var/lib/postgresql/data networks: mailman: networks: -------------------------------- So not sure where to go next?

4 years, 2 months

[MM3-users] Re: Question: What happens if I delete a user from all lists and that user is sole owner of some list?

by Odhiambo Washington

On Wed, Apr 3, 2024 at 6:58 PM David Partain <david.partain(a)ericsson.com> wrote: > On Wed, 2024-04-03 at 15:14 +0300, Odhiambo Washington wrote: > > > My question is: If one of these users is the sole owner of a list, what > > > will happen? Will the user be deleted and that list now owner-less? > > > Will mailman refuse to delete that user until I add a new owner? > > > > > > Thanks in advance for your feedback. > > > > 1. Create a testlist > > 2. Assign an owner to it > > 3. Delete the owner via the CLI or Postorius > > > > Give us your feedback :) > > I'll happily do so, and thanks for the idea. Try stuff, David! > > Cheers, > > Daudi Mwisho, as my mom liked to call me > Aah. Mswahili :-) -- 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, 7 months

[MM3-users] db migration from mailman3.2.2 to mailman3.3.9 (sqlite3 to postgres16)

by Stephen J. Turnbull

Peter Thornton via Mailman-users writes: > We have a legacy environment with: > there are two sqlite3 dbs for mailman core and mailman web. > > I've staged a new environment > there is a single postgres db here for both core and web. This is known to be problematic. Try searching the archives https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ for "sqlite postgres migration" (or maybe use "sqlite3" and/or "postgresql", and don't surround the phrase with quotes). I would start by configuring the postgres db on the new host with separate databases. If you decide you want a single db, I guess it's easier to add the tables from the mailmanweb db to the mailman db than it is to get pgloader to do the right thing. ISTR that the most straightforward approach was rather than using pgloader, you should create the databases in Postgres then dump the databases (text) and load them. You probably need to edit them. (This is very unreliable advice!) It's almost 2am here, so I'm off to bed. You should consider all of the above advice except "known problematic" to be unreliable. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months, 3 weeks

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/20/23 05:43, Wikinaut wrote: > it has: > > # Mailman Web configuration file. > # /etc/mailman3/settings.py > > # Get the default settings. > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * As I said, I don't know what caused your original authentication failure or what fixed it, but it wasn't the addition of ``` MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' ``` to /etc/mailman3/settings.py. You can verify this by activating your venv and doing ``` >>> MAILMAN_REST_API_USER Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'MAILMAN_REST_API_USER' is not defined >>> MAILMAN_REST_API_USER Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'MAILMAN_REST_API_USER' is not defined >>> MAILMAN_REST_API_PASS Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'MAILMAN_REST_API_PASS' is not defined >>> from mailman_web.settings.mailman import * >>> MAILMAN_REST_API_USER 'restadmin' >>> MAILMAN_REST_API_PASS 'restpass' >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: 502 bad gateway when unsubscribing users

by Jered Floyd

Hi Laura, This indicates a problem an error occurring within the specific install of Mailman that your university is running, and it will be very difficult to diagnose without access to the error logs. Is this something you can escalate with an IT administrator? They'll be in the best situation to figure out what's wrong -- it's definitely not anything that you are doing as a moderator. Regards, --Jered ----- On Aug 21, 2024, at 12:02 PM, laura thomas laura_thomas(a)fas.harvard.edu wrote: > Hi everyone, > > I moderate several email lists for a university using Postorius 1.3.4.1. I've > been trying to update our lists by removing members who have left the > department. However, when I click on a name and then "Unsubscribe Selected," I > always get a 502 Bad Gateway message, and I'm unable to remove any users from > the list. This has happened on every attempt across multiple users on multiple > mailing lists. Does anyone know what might be going on? I appreciate the help! > _______________________________________________ > 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 jered(a)convivian.com

1 year, 2 months

[MM3-users] leaving Sympa for MM3

by rance.hall＠esu10.org

Our shop is an educational shop and left mailman many years ago for Sympa because of features in Sympa not in mailman. Currently Sympa is showing its age, and is relying on perl modules that have been EOL's and the Sympa community has not discussed (within in ear-shot of me at least) what to do about it. We found that we are not using the extra features Sympa provides anymore and with MM3 already dockerized it seems that MM3 is a much better fit for our organization for the foreseeable future. So I got a dockerized setup up and running in a test environment and am pleased with the results except for now I have to start thinking about migration from Sympa to MM3. The API is useful in this effort as there are python wrappers already done and I didn't have any trouble scripting list creation with the API tools to migrate list owners, moderators and users. Now for the question/hard part. Migrating list archives. In Sympa the list archive is just a maildir format directory structure reflecting month/year. In MM3 the Archive is stored in the db with attributes that are likely only available as the message is processed. I'd really rather not loose the archive data if I can help it. Does anyone have any thoughts on how I could perhaps import this?

5 years, 8 months

[MM3-users] Re: add custom styles to postorius list creation menu

by Mark Sapiro

On 5/2/22 06:39, Michael Hazan wrote: > Hello, > > When creating a list via postorius, i can see 3 style appear (announce, discussion, private). Is it possible to either create a new style and add it to that list or modify one of those style ? See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Also, coming from mailman2, you could directly set the members post moderation action when subscribing, now you can only do it via the user menu, is there a way to automate this in mm3 ? I don't understand what you mean here. In MM 2.1 a member had only one setting - moderated yes or no and if moderated there was a list setting for the moderation action. There was also a list setting for whether new members were moderated by default. How were you setting the new member's moderation when subscribing? You are correct that when subscribing a new member, the member gets the default action for members and different action has to be set in a separate operation. I don't think this is significantly different from MM 2.1. Also, can you describe what you mean by "automate this". -- 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] Making "Mass subscribe" and "Mass removal" their own buttons in list_nav.html What stupid thing have I done wrong?

by mrl＠psfc.mit.edu

I want "Mass subscribe" and "Mass removal" as their own buttons, since I use them so much. I modified nav_list.html. See below. While the new buttons go to the correct page, the buttons don't get highlighted. I believe ootstrap navbar should be assigning "nav-link.active" class to the button that is clicked. But it doesn't. All the other buttons below work correctly. Any idea what I'm doing wrong? Thanks. - Mark <li role="tab" class="nav-item"><a href="/mailman3/lists/mark.lists1.psfc.mit.edu/templates" class="nav-link ">Templates</a></li> <li role="tab" class="nav-item"><a href="/mailman3/lists/mark.lists1.psfc.mit.edu/mass_subscribe/" class="nav-link ">Mass subscribe</a></li> <li role="tab" class="nav-item"><a href="/mailman3/lists/mark.lists1.psfc.mit.edu/mass_removal/" class="nav-link ">Mass removal</a></li> <li role="tab" class="nav-item"><a href="/mailman3/lists/mark.lists1.psfc.mit.edu/header-matches/" class="nav-link ">Header filters</a></li> <li role="tab" class="nav-item"><a href="/mailman3/lists/mark.lists1.psfc.mit.edu/delete" class=" nav-link">Delete</a></li>

2 years, 5 months

[MM3-users] outgoing messages not sent in a busy loop

by Igor Serebryany

incoming messages are showing up in hyperkitty but not going out as emails to list members. i've tried enabling the following debug logging: format: %(asctime)s (%(process)d) %(message)s datefmt: %b %d %H:%M:%S %Y propagate: no level: info path: mailman.log [logging.smtp] level: DEBUG [logging.smtp-failure] level: DEBUG [logging.runner] level: DEBUG [logging.debug] level: debug [logging.smtp-failure] level: debug with these options, if i run `tail -f *` in the `log` directory of mailman, i get the following in essentially a busy loop: ``` ==> smtp.log <== Mar 13 19:08:46 2024 (18) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fef1c9ad050> ==> debug.log <== Mar 13 19:08:46 2024 (17) [NNTPRunner] starting oneloop Mar 13 19:08:46 2024 (17) [NNTPRunner] ending oneloop: 0 Mar 13 19:08:46 2024 (18) [OutgoingRunner] finishing filebase: 1710356926.1738262+0a50dc0e393ba4de10bcdadb5376d4330f670c77 Mar 13 19:08:46 2024 (18) [OutgoingRunner] doing periodic Mar 13 19:08:46 2024 (18) [OutgoingRunner] committing transaction Mar 13 19:08:46 2024 (18) [OutgoingRunner] checking short circuit Mar 13 19:08:46 2024 (18) [OutgoingRunner] processing filebase: 1710356926.2733445+d044aeb93be86fbf662b6e0feffc89d0f2e4eb66 Mar 13 19:08:46 2024 (18) [OutgoingRunner] processing onefile Mar 13 19:08:46 2024 (18) [outgoing] <function deliver at 0x7fef1cda27a0>: <CADJyiOV1RAth=3CkNoHJ1qTVzedzX8BG0k6iwe019jXau30pLw(a)mail.gmail.com> ==> smtp.log <== Mar 13 19:08:46 2024 (18) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fef1cb0f390> ``` which doesn't give me a lot to go on. anyone know what could be causing this or any way to get additional debug information?

1 year, 7 months

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Andrew Bernard

Hi Mark, Thanks for your great help. But despite decades of UNIX experience, my area is not Django (yet). The nub of my question is that I thought you have to have a manage.py file for Django to be able to set up the various affairs, such as making the database migrations and so on. It is that that is eluding me. Apologies for this hopelessly newbie question. I was impressed with your method of installation in the page referenced, and I have foolwed that closely. But I am puzzled about the build script. If I run as user mailman, not root, it wanted to install under /usr. which of course results in permission denied. I had to modify the script to say this: python setup.py install --prefix /opt/mailman/mm/venv I am concerned that I have also misunderstood something here. A On Sun, 9 Jun 2019 at 00:57, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/8/19 4:04 AM, Andrew Bernard wrote: > > > > Where is the Django config area for the > > pip installed modules? It is this that I find obscure. > > The short answer is wherever you put it. If you look at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > which Abhilash mentioned, you'll see what I do. > > >

6 years, 4 months

[MM3-users] Re: Database read only error on mailman_sync job

by Ugnius

Thank You, Mark for guideline. I accidentally posted here. I wanted to start new thread and just replaced subject of messages. Message was sent to this thread anyway. The reason of this issue was very simple. I creadet symlink in /usr/local/bin/django-admin to /project/home/manage.py, because I was unable to set original django-admin file to work as it should to work. Later I decided to run mailman project under other user and forgot about that symbolic link. So it was normal, that previous user had no privileges on database file. Thank You for helping. > On 12 Sep 2019, at 21:50, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/1/19 1:02 AM, Ugnius S wrote: >> >> I guess that issue is hyperkitty database, but I even do not know the name >> and location of that database. > > See the DATABASES definition in your Django settings. The default is a > sqlite3 database named mailmansuite.db in the same directory as the > Django settings. > > -- > 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/

6 years, 1 month

[MM3-users] Re: How to promote non-members to members?

by Quanah Gibson-Mount

--On Thursday, March 17, 2022 12:06 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > This says that there is no Address object with the email > xxxxxxxx(a)xxxxx.org > > What do you get in `mailman shell` for > ``` > >>> um = getUtility(IUserManager) > >>> um.get_address('xxxxxxxx(a)xxxxx.org') > >>> um.get_user('xxxxxxxx(a)xxxxx.org') > ``` > These should return an Address and a User respectively. If they don't, > did you perhaps run some process to delete the user? I've done nothing in regard to this user. Neither command returns anything. I see it return my user object if I test with my own email address. > If the user is gone, you should be able to replace > ``` > ... sub_mgr.confirm(token) > ``` > in the above with > ``` > ... wfm = getUtility(IWorkflowStateManager) > ... pendings.confirm(token, expunge=True) > ... wfm.discard(token) > ``` > to clear the pending subscription and workflow and then be able to mass > subscribe the user. I did this, and can confirm that they no longer show up in the list of pending subscriptions via the mailman shell interface for that list. However, if I go to mass subscribe them via the interface, I get: HTTP Error 409: b'Subscription request already pending' Regards, Quanah

3 years, 7 months

[MM3-users] Re: Immediate notification to the administrator

by Stephen J. Turnbull

pau.baiges(a)csuc.cat writes: > mailman3.2.2 ... > Is there no other option? Yes. Get yourself a system where the packaged software is upgraded on a timely basis, or install the recent release yourself. Until then, here's the crontab template distributed with Mailman 3.2.2: # At 8AM every day, mail reminders to admins as to pending requests. 0 8 * * * @PYTHON@ -S @prefix@/cron/checkdbs # # At 9AM, send notifications to disabled members 0 9 * * * @PYTHON@ -S @prefix@/cron/disabled # # Noon, mail digests for lists that do periodic delivery. 0 12 * * * @PYTHON@ -S @prefix@/cron/senddigests # # Every 5 mins, try to gate news to mail. */5 * * * * @PYTHON@ -S @prefix@/cron/gate_news # # At 3:27am every night, regenerate the gzip'd archive file. Only # turn this on if the internal archiver is used and # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py 27 3 * * * @PYTHON@ -S @prefix@/cron/nightly_gzip Take the parts you need. These scripts should be installed on your system somewhere. @PYTHON@ is the path to the Python 3 binary which is used by Mailman. It's probably not terribly sensitive if you have multiple Pythons installed, but it's a good idea to use the same one. @prefix@ is where your Mailman code is installed, typically something like /var/lib/mailman, /var/local/lib/mailman, or /opt/mailman. cron should be a neighbor to queue, lists, and other such directories. Steve

2 years

[MM3-users] Re: bounce handling in mm3 available?

by Mark Sapiro

On 1/24/22 05:20, Stefan Bauer wrote: > Hi, > > what happens with bounce-mails that are processed by mailmans postfix > instance? What Mailman core version? Prior to 3.3.1, bounce events were recorded in the bounceevent table but not otherwise processed. Subsequent to that, they are scored if recognized and what notices are sent depends on list settings. > Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: > to=<company-newsletter-bounces(a)lists.company.tld>, > relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, > dsn=2.0.0, status=sent (250 Ok) > > But the list-owner does not get any notification, nor do i see any > bounce-information in the pistorious-gui. What are you expecting to see in Postorius? All you can see is if a member's delivery status is Disabled by Bounces. Things like Bounce score are not available in Postorius. What notices are sent depends on the settings in the Bounce Processing section in Postorius. For example, if your message logged by postfix was spam to the <company-newsletter-bounces(a)lists.company.tld> address that is not recognized as a DSN and `Forward unrecognized bounces` is Discard, the message will be silently discarded. Also, if that message was a non-fatal, message-delayed type of DSN, it will be ignored. -- 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

[MM3-users] Re: List nonmembers

by Mark Sapiro

On 7/8/19 6:50 PM, Andrew Bernard wrote: > Under Users for a list, there is a category for List nonmembers. What does this term mean? [It's rather curious philosophically when you think about it, because I would have thought that the category [all humans - list members] fits that category term.] > > But seriously, I don't understand it. I have several email addresses there and I don't know what do with them, if anything. Non-members are email addresses that are not members but have some connection to a list. Mailman 2.1 lists have attributes named accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers and discard_these_nonmembers. These are lists of non-member addresses and regexps matching addresses, and posts from a non-member address in one of the lists will be accepted, held, rejected or discarded respectively. Mailman 3 does this differently. An address can be a non-member and that non-member record has a moderation setting to determine how a post from that non-member is handled. An address can become a non-member by being imported from Mailman 2.1 or by posting to the list. If a non-member posts to the list, a non-member record is created regardless of the disposition of the post. See <https://mailman.readthedocs.io/en/latest/src/mailman/chains/docs/moderation…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Advice on migrating to Mailman 3

by Mark Dadgar

On Feb 20, 2020, at 8:47 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >>> The only problem is that our list runs on Mailman 2. We would like to >>> move to Mailman 3 > >> Why? > > I'll echo this. We don't need to know (unless there's a specific > technical challenge to Mailman 2 that you hope Mailman 3 can resolve, > and then we can tell you whether Mailman 3 has it, will have it soon, > or won't have it soon if ever), and don't really care (happy to help > and all that). But you need to ask yourself that question because > it's rarely a good idea to fix what ain't broke. And Mailman 3 is > sure to become more robust, easier to install, and easier to migrate > Mailman 2 lists over time. Don't do it until you forsee a near- > future *need* to migrate, is my advice. I’ll weigh in here. In my case, I moved an almost 20 year old MM2 installation to MM3 primarily to get archiving that actually worked well. The poor searching of the list archives was easily the #1 complaint I got about my mailing list. MM3 is awesome. Finicky to get running, but awesome. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 8 months

[MM3-users] Mailman Core 3.3.1 release

by Abhilash Raj

Hey Everyone, I am pleased to announce Mailman Core 3.3.1 is now out. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1/ To install this release via pip, you can run: $ pip install --upgrade mailman -- thanks, Abhilash Raj (maxking)

5 years, 6 months

[MM3-users] Re: problem with postorius initial setup

by Abhilash Raj

Hi John, > On Mar 16, 2021, at 6:58 AM, John Covici <covici(a)ccs.covici.com> wrote: > > Hi. I am trying to setup postorius, but I have run into a problem. I > am using the example project, except I am using postgresql instead of > sqlite3. I ran python manage.py migrate which was successful. Are you trying to setup locally for development or are you setting up a production installation? > > On running the development server I get: > Exception in thread django-main-thread: > Traceback (most recent call last): > File > "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", > line 20, in import_string > return getattr(module, class_name) > AttributeError: module 'postorius.middleware' has no attribute > ‘APICountingMiddleware' APICountingMiddleware is from a development branch of Postorius, so unless you are installing from git, this won’t be present since it hasn’t been released. If you are actually doing development, you want to install from the Git source tree by running: ``` $ pip install -e . ``` You can skip the `-e` if you want to install from git but not develop. From the top level directory of Postorius (where setup.py is, one level above example_project). If you are trying to setup a production installation, you want settings from https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web.sett… This is for both Postorius and Hyperkitty. thanks, Abhilash

4 years, 7 months

[MM3-users] Re: auto-away notices as bounces

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210830 04:30]: > On 8/24/21 11:17 AM, Andreas Barth wrote: > > > >Well, the mail adress got disabled, and the user got warning mails > >("Your subscription for list mailing list has been disabled"). As none > >of the list owners did that, I don't think there is any other > >explanation. Please note that individualsation was enabled, so all > >mails are sent out with per-subscriber mail envelope address, which > >then makes bounce detection quite straight-forward. > > > If by 'individualsation was enabled' you mean messages were VERPed, > there could be a bug here. Yes, that's what happens. > There are a couple of considerations. First the vacation responder > should not respond to list messages. See > <https://www.rfc-editor.org/rfc/rfc5230.html#section-4.6>. I fully agree with you, and already responded with the same remark to the user before sending my initial mail here. > That said, bounce processing should treat even a VERPed message as > unrecognized if it doesn't look like some kind of DSN. This may not > be the case in MM 3. Thanks, that's what I also think. Looking at the returned mail, they definitly don't look like DSNs / bounces to me. Anything I should be doing re this topic? Thanks, Andi

4 years, 2 months

[MM3-users] Re: How to approve moderated messages via email?

by Brian Carpenter

On 1/23/21 4:33 AM, Stephen J. Turnbull wrote: > Is this capability important to you or your clients? If so, what is > the context? I ask because, as you know, email is rather insecure by > default. Making it highly secure would require a lot of effort and > sophistication for the moderator, eg, PGP signatures, but there might > be intermediate levels that would be appropriate for many lists. > > For example, the Mailman 2 mechanism. I forget exactly what Mailman 2 > does, but if the post to be approved were identified by a one-time > key, then a spammer would have to have both the moderation password > and the key (presumably by intercepting the moderation email) to > approve their own spam. That's still a plausible scenario in > principle[1] so I don't much like it (and I bet that's why Barry > didn't implement it), but it would be straightforward to implement. Hi Steve, Happy New Year! I hope you are doing well. The question was asked of me by a new client coming from Mailman 2 into Mailman 3. I wasn't sure what the current mechanism in place was and according to Mark, none. Honestly I don't think it is a big deal. Thank you for answering. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: Set Postorius interface locale

by Duane Raymond

Thanks - here is where that got ne so far... I have set the modest goal of changing a string on the list subscription page from the form label "Your name (optional)" to "Your name (and organisation)" What I did was 1) I edited /opt/mailman/mm/settings.py and changed the LANGUAGE_CODE from 'en-us' to 'en-gb' (or should I do it at /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/dj/settings.py or another location?) 2) Then I switched user using "su mailman" and started the venv environment (using: source /opt/mailman/mm/venv/bin/activate) 3) I edit the po file at /opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/locale/ and specifically I am testing it on editing en_GB/LC_MESSAGES/django.po - is this the correct location? 4) I run: mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py compilemessages - is this the correct one to run? After this, nothing changed on the list page yet. 5) After that I changed directory into "/opt/mailman/mm/static" and run python ./mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py collectstatic - but this produces an error about ROOT_STATIC not being set ...and I didn't want to fiddle too much in case I overwrote the current functioning site ;-) Is the collectstatic static necessary after running compilemessages? Am I using the right files to run it? Am I editing them in the right location? Cheers, Duane

4 years, 8 months

[MM3-users] Re: Good MM hosts for customized code?

by Brian Carpenter

On 3/19/21 10:30 AM, Steven Clift wrote: > E-Democracy.org is plotting a test move from GroupServer.org (end of life > coming) to MM3. > > We have certain technologies we've embedded into GroupServer, like volume > based posting limits on our political forums (no more than X posts in y > hours per member ... typically 2 or 3 posts in 24 hours), inserting > standard "who made this post" in the email footer with links to the user > profile for context assuming email is forwarded as well as the web archive > url to that post. > > We know that we do not want to be in charge of email deliverability and we > don't yet have an Mailman aficionado in our volunteer team. > > So ideally, we'd find the right Mailman host where we can use our own > selected domain (@opengroups.org perhaps) and whether we hire coders to > help out with custom tech OR have volunteer coders (interested in local > online communities? AKA hate that Facebook and NextDoor host most of these, > let me know:-) ), we'd like to have the right set up to allow us to > experiment. > > Advice? Thoughts? > > Thanks, > Steve Hi Steve, I just sent you a reply off-list. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Patrick Brückner

Hi everyone, one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back. What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list. The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain. Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again. According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) but none of my lists have that set after the migration - the field is not even there when accessing the REST API. Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)? Thanks in advance, Patrick

4 years, 1 month

[MM3-users] Re: Error while running mailman-web compilemessages

by Stephen J. Turnbull

Philip Colmer writes: > Looking at the packaging for mailman-web and mailman-hyperkitty, the former > (https://gitlab.com/mailman/mailman-web) specifies "django >=2.2, !=3.0, > <4" This is the relevant requirement, mailman-web is what actually configures django for use by HyperKitty and Postorius. > and the latter (https://gitlab.com/mailman/mailman-hyperkitty/) doesn't > seem to specify a django version requirement. IIRC, mailman-hyperkitty is the small Python module that enables core to send posts to a hyperkitty. That module has nothing to do with Django. > There is a separate Hyperkitty project > (https://gitlab.com/mailman/hyperkitty) which has added support for > Django 4 but that doesn't seem to be what is installed by following > the instructions at > https://docs.mailman3.org/en/latest/install/virtualenv.html This is all very confused (lots of duplication across several project and multiple documented configurations requiring slightly different lists of projects for installation), and we need to clean it up. We're aware of it, but cleaning up is hard because it means that sources for people's existing installations are going to disappear. Also, mailman/hyperkitty is the actual implementation of HyperKitty, and I don't think Django 4 support is considered anything like stable yet, which is why mailman-web doesn't allow it. Volunteers to identify duplication and help with deduplication welcome! ;-)

3 years, 3 months

[MM3-users] Re: Mailman 3 Social Auth Configuration

by Mark Sapiro

On 10/12/2016 08:09 PM, emonical(a)misfitlabs.org wrote: > > I am a new Mailman 3 user and have just gotten an environment configured using the Mailman bundler. The setup is almost complete, but, there's still Persona authorization. Mailman bundler installs the latest releases from PyPI, but those are behind the latest development branches. > I was reading the your setup here from (https://wiki.list.org/DOC/Mailman%203%20installation%20experience) and was wondering if someone might have some insight as to how to remove the Persona log in to keep it locked down entirely to localized user registration. With the latest gitlab branches, you will have Django Allauth. This includes login by verified email and password, and if you choose to not use any of the supported Oauth2 providers, that will be the only method. To do this without waiting for the Mailman 3.1 release and an updated bundler, you will need to install the latest master branches from <https://gitlab.com/groups/mailman> for Mailman, Postorius, HyperKitty, MailmanClient, django-mailman3 and HyperKitty - Mailman plugin. The wiki article <https://gitlab.com/groups/mailman> will give some insight into the process, but it isn't fully current. I will be updating it. Meanwhile, ask your specific questions here and we will try to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/8/21 10:50 PM, Kimmo L wrote: > Okay, i will try to explain the overall situation as far as I can understand: > Its a CentOS 7 host without any virtualenv. Mailman_suite_project git repo has been cloned to the host and after that some packages have been installed with the help of pip: > > # pip2 install django==1.10 postorius==1.1.0 hyperkitty whoosh xapian-haystack > # pip3.5 install mailman mailman-hyperkitty For current Mailman the minimum Python version is 3.6 and all components are Python 3. Nothing is Python 2. You should be installing the latest versions of everything. Do not install Django explicitly with pip. It will be installed as a dependency of Postorius and Hyperkitty. If you are going to use Xapian, you don't need whoosh. Also, you need to install Xapian itself, either from source or with yum if there is a yum package. > And now Im in trouble, what would be the right steps from here. I'm not that competent to use pip, so im confused - should i install python36 packages and try to upgrade pip2 and pip3 mailman packages after that or should i install these pip2 packages with pip3 and remove from pip2 list? There are no pip2 packages. Everything is Python >=3.6. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Problems after update to mailman 3.3.7

by Guillermo Hernandez (Oldno7)

I've getting the most strange behaviour after update to last releases. In one of my mailman3 servers, the messages doesnt reach for some lists (the five last ones) the update have not showed any error but in the var/data for the lmtp and vmap postfix files mailman does not create aliases for that last 5 lists. Any message addressed to them is returned with a "no such user" error. If I create a new list the system or restart mailman runners it shows this error: Generating MTA alias maps /usr/local/lib/python3.9/site-packages/pymysql/connections.py:799: UserWarning: Previous unbuffered result was left incomplete warnings.warn("Previous unbuffered result was left incomplete") I did a CHECK TABLE on mailinglists table but all seems ok. I tried reinstalling PyMySQL, but has no effect. (well, I tried reinstalling all) It seems to me that something is preventing creation of that aliases, an then the that last five lists are unreachable. I have no clue of what to do now and I'm driving crazy. Some direction to look for will be much apreciated. Thanks in advance. P.S.: I can access via postorius/hyperkitty to the archives of the lists that are unreacheable. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 10 months

[MM3-users] Re: lists.mailman3.org web site.

by Mark Sapiro

On 08/27/2016 09:15 PM, Mark Sapiro wrote: > I have just upgraded the lists.mailman3.org Mailman 3 installation to > the heads of the GitLab mailman* branches. A major change is the switch > from Persona to Django Allauth. This requires some configuration which > isn't yet complete. Hopefully it will all be working very soon. > > In the mean time if you want to log in to Hyperkitty/Postorius you > should be able to log in with your email address. The first time you do > this, Mailman probably won't even know your password so you'll have to > request a reset. Once you have reset your password, you should be able > to log in. > > I hope to have several social auth choices working very soon. Update: Django Allauth is now properly configured and working on lists.mailman3.org. You can log in by email/password as noted above or via OAuth2 with a GitHub, GitLab, Google or Facebook identity. If you are an existing user, in order to use one of the OAuth2 providers, you must first log in with email and password and go to the Account Connections tab in your account settings and add the 3rd party account(s) you wish. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

[MM3-users] Re: Shorted Subjects in Mailman

by Stephen J. Turnbull

Stephan Krinetzki writes: > Yes, it doesn't matter which cleint they are using. The cutted > subject was reported multiple times. That doesn't tell me that they use different clients, though. Hundreds of millions of people use Gmail, for one. All of them would report the same problem if it occurred, but that could be a Gmail bug. > > Of course if you look at the original text and there is no second > > line, that's a Mailman bug. > > And here we are: There is no second line! The subject header only > contains the displayed value, no new line or other things. But the > mailman subject line is intact. Only the regular Subject: is > truncated. I don't understand what you mean by "mailman subject line" and "regular Subject:". Are you talking about a digest that contains multiple messages? If so, explain more completely what you mean by those terms. It would help a lot if you would forward to us a complete raw message that shows the problem. Most mail clients have a "forward" function that will do this. A "reply" with the mail quoted does not help very much. A screenshot does not help very much. We need to see some information that is normally hidden by clients and not including in quoted replies. Steve

3 years, 3 months

[MM3-users] Re: postfix malformed address with confirm replies

by Stephen J. Turnbull

Hi Stephen, Mark says that matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu is legal, and I think that most servers will accept it, but RFC 5321 sets a limit of 64 octets on mailboxes[1], and your confirmation mailbox is 67 octets. (There are also limits on domain length and total address length.) Note that although the '+' has a special meaning to the final recipient, and it will be delivered to the mailbox "matsmats-mm3-test1-confirm", which is only 26 octets, intermediate MTAs don't know anything about this convention, they just see the 67-octet mailbox. I suspect that in a modern server it should be possible to configure a larger value. What is the host with IP 172.19.199.2, do you know? Is it under your control? Footnotes: [1] https://tools.ietf.org/html/rfc5321 4.5.3.1. Size Limits and Minimums There are several objects that have required minimum/maximum sizes. Every implementation MUST be able to receive objects of at least these sizes. Objects larger than these sizes SHOULD be avoided when possible. However, some Internet mail constructs such as encoded X.400 addresses (RFC 2156 [35]) will often require larger objects. Clients MAY attempt to transmit these, but MUST be prepared for a server to reject them if they cannot be handled by it. 4.5.3.1.1. Local-part The maximum total length of a user name or other local-part is 64 octets.

4 years, 8 months

[MM3-users] Re: [Mailman-Users] Web interface for users (not admins)?

by Stephen J. Turnbull

Mark Sapiro writes: > No, Posting from HyperKitty without using the "Use email software" > button is plain text only. That surprised me. There is the possibility of enabling Markdown in the viewer, but that's not a real solution for atechnical users who are used to mousing around, and by itself doesn't enable attachments. > There is no plan to add any sort of rich text capability. That doesn't surprise me. A number of things are possible, but I think that providing the mailto link give the atechnical user the best of both worlds: a quick text-based response or the comfort (? :-þ) of their usual mail client. One constraint that we have is that many of our users value "no Javascript" quite highly, so just dropping in the Electron-based editor du jour is something we don't want to do. By the way, Skip, if you decide that richtext followups are an important feature, earlier I mentioned EMWD's commercial offerings Affinity (for admin) and Empathy (for archiving). I don't know if Empathy offers more features for posting than HyperKitty does, but I encourage you to check with Brian Carpenter <brian(a)emwd.com>. These are commercial, closed-source (at least for now) offerings, but I believe rates are reasonable and support has a very good reputation. Regards, Steve

4 years, 5 months

[MM3-users] Re: Postorius install - missing python modules

by Odhiambo Washington

On Wed, May 3, 2023 at 7:13 PM Marco F <marco.ferrufino(a)webpros.com> wrote: > Hello, > > On AlmaLinux 8.7, after Configuring Mailman and Setting up my database > (postgres), and hooking up my mailserver (Exim), the instructions proceed > to Set up Postorius: > https://docs.mailman3.org/projects/postorius/en/latest/setup.html Hello Marco, Please abandon that method completely and follow the recommended method. https://docs.mailman3.org/en/latest/install/virtualenv.html > I've tried `pip install postorius`, as well as the latest version, cloning > and `pip install -e .`. I've tried with multiple python versions, all with > the results: ModuleNotFoundError. Here's highlights of one example: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Don't do the above!! > ``` > dnf update -y > dnf upgrade -y > dnf install -y python39 > alternatives --config python3 > » python3 -V > Python 3.9.13 > ^^^^^^^^^^^^^^^^^^ From here, proceed to: https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… And continue with everything below it. The above method is universal across all OSes. And with it, it will be easier for most of us to help you. We don't even have to think about your OS if you follow the above method :) -- 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]

2 years, 6 months

[MM3-users] Re: Set domain inactive / archive import from other domain.

by Mark Sapiro

On 09/15/2018 07:15 AM, Johannes Winter wrote: > > we've migrated a list from another domain and would like to keep the > archives. Hyperkitty doesn't recognize the emails in the mbox archive > during import due to the other domain name. I don't understand the problem. I just ran a test where I imported a mbox containing 3 messages which were not even list posts and in which I had changed all the domain names to 'example.com'. I.e., in the mbox I imported, the headers containing domain names looked like From root(a)example.com Sun Aug 26 09:12:06 2018 Return-Path: <root(a)example.com> Delivered-To: root(a)example.com Received: by example.com (Postfix, from userid 0) From: Anacron <root(a)example.com> To: root(a)example.com Message-Id: <20180826161158.F154D34010C(a)example.com> X-msapiro-MailScanner-From: root(a)example.com and the 3 messages were all added to the archive. Why do you think the domain name is an issue? Perhaps the issue is there is already one or more messages in the archive and the messages you are importing are older. If you don't specify --since to hyperkitty_import it won't import messages older than the newest message in the existing archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

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

by Mark Sapiro

On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > There won't be a membership adapter in Systers Mailman if there isn't > one in GNU Mailman, because they used the stock user database and > added fields to the User record to implement their membership > extensions. > > 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 methods of which are used for everything to do with list members and memberships and are all documented in the base definition in Mailman/MemberAdaptor.py and all raise `NotImplementedError`. Also included in Mailman 2.1 is Mailman/OldStyleMemberships.py which subclasses MemberAdaptor and actually implements the methods, storing the data in the same config.pck pickle as the list settings. Various people have implemented various other MemberAdaptor classes for various purposes. https://bugs.launchpad.net/mailman/+bug/558106 contains several revisions of one using LDAP for the (read only) membership data. The Mailman 3 analog of this is the IMember interface defined in mailman/interfaces/member.py and implemented in mailman/model/member.py -- 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: Can't subscribe on new site/domain

by Mark Sapiro

On 10/11/25 4:58 AM, Flo via Mailman-users wrote: > On 10/11/25 04:45, Mark Sapiro wrote: >> >> The fields in order are: >> >> 1. the id of the django_mailman3_maildomain entry >> 2. the mail_domain in the django_mailman3_maildomain entry >> 3. the site_id the django_mailman3_maildomain entry >> 4. the id of the django-site entry >> 5. the domain name in the django-site entry >> 6. the display name in the django-site entry >> > > For me it looks like that 5 is the display name and 6 the domain name Possibly sqlite displays them in a different order. To be sure you could do SELECT mail_domain, domain FROM django_mailman3_maildomain JOIN django_site ON site_id = django_site.id; which will display only the mail_domain and the site domain. > For each of the lines mail_domain (field 2) is the same as the domain > name (field 6, if I am right). > Any domain name (and mail_domain, which has the same value) differs from > the ones in any other line. > > So they are unique. Anyway, if all 3 mail_domain values are unique, that doesn't explain the issue. I can only guess that this is a Debian package issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks, 3 days

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 9:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/25/22 01:14, Odhiambo Washington wrote: > > On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > >> > > > > I have uncommented the line "WSGIScriptAlias /user-profile > > /opt/mailman/mm/wsgi.py", > > I don't see any definition for it in urls.py as well. Perhaps that's the > > issue? > > > It is defined in django_mailman3/urls.py which is referenced by > > re_path(r'', include('django_mailman3.urls')), > I have seen that now. > > When I uncomment /user-profile, I end up with an ugly URL: > > https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ > > > > So instead of aliasing the /user-profile, I have decided to add another > > definition to urls.py: > > re_path(r'^user-profile/', include('allauth.urls')), > > Which I think gives me a cleaner URL: > > https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ > > It shouldn't include `allauth.urls`. That URL is appropriate if you > aren't logged in, but what do you get when you are? > > Go to https://lists.mailman3.org/user-profile/ and log in if necessary > and you'll see what it should look like. > Here when I log in. I land on the /archives ( https://lists.mailman3.org/archives/?sort=popular) I then head to the dropdown and click "Account " and I am taken to https://lists.mailman3.org/user-profile/ (very clean URL!) and that's the same thing I am seeing on my server at the moment.. When I comment out the edit I had on /etc/mailman3/urls.py and uncomment to /user-profile alias in the VHOST, I end up with 1. https://mm3-lists.kictanet.or.ke/user-profile/mailman3/lists/ - once I am logged in 2. https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ - when I click on "Account " # I hope you can see the duplication of /user-profile, which is ugly. However, your server isn't using mod_wsgi, I believe, so I shouldn't be comparing it to mine. I just don't like the extra URLs being added. > I also had to alias /accounts, which then brings me to: > > https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I > believe > > is fine because one gets the > > option to either login or signup. > > > > And I think that "/account" and "/user-profile" are synonymous. > > They are in your instance because of > > re_path(r'^user-profile/', include('allauth.urls')), > > but they should not be. > I have changed that, as already pointed out, but with consequences :) There must be a way to not have "/user-profile/user-profile" > >> It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time > >> (I now use gunicorn on all the sites I manage), but when I did I think I > >> had > > > > > >> WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > >> > >> and all the URLs were like https://example.com/mm3/mailman3/..., > >> https://example.com/mm3/archives/..., etc. > >> > > > > I already had gunicorn working too, but I just need to also figure out > this > > mod_wsgi. > > > Why? Intellectual curiosity or do you have an actual need. > It's out of intellectual curiosity actually. The bottom line is with mod_wsgi, whatever you have in your > WSGIScriptAlias is going to be prepended to the URL path. If you don't > want anything prepended, you need > ``` > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > ``` > but then in order for user-profile to work, you need to replace > ``` > re_path(r'', include('django_mailman3.urls')), > ``` > in urls.py with the urlpatterns from django_mailman3/urls.py > ``` > re_path(r'^user-profile/delete$', delete_account, > name='mm_user_account_delete'), > re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), > ``` > and also add > ``` > from django_mailman3.views.profile import delete_account, user_profile > ``` > to the imports in urls.py > And with that, I am now happy with what I am seeing. Again, thank you very much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 6/13/20 6:30 PM, Kareem Zidane wrote: > Hi Mark, > > Sorry to bother you! Just wanted to loop back on the above to see if you might have any thoughts on that by chance? I'm sorry, I thought I had replied, but clearly I hadn't. So as I understand it, you have multiple lists in this Mailman 3 installation, and only one list has this issue, and mail to this list gets archived, but not delivered but is queued in var/queue/out and remains there. This is hard to understand. When Mailman's out runner processes its queue, it processes messages in chronological order without regard to which list they are from, so it must be at least attempting to deliver these messages, and somehow failing and requeueing them. I do see this Jun 09 17:36:31 2020 (82) Cannot connect to SMTP server postfix on port 25 in the log excerpt you posted. What's in Mailman's smtp.log and the postfix mail.log that might be related to this? It's hard to understand how an MTA connect issue could affect only one list. If it is accepting the connict and then dropping the connection for too many invalid RCPT addresses, that's a possibility. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: MM3+Python3.11

by Odhiambo Washington

On Mon, Mar 6, 2023 at 7:52 PM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Mon, Mar 6, 2023 at 7:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 3/6/23 08:23, Odhiambo Washington wrote: >> > >> > I install Python3.11 manually on Debian12 (maybe this is the issue!) VM >> > using the script below: >> > #!/bin/bash >> > cd Python-3.11.2 >> > ./configure --enable-optimizations >> >> You also want --enable-shared >> > > I had done that, but somehow the build had failed with it. I will try it > again. > I managed to reinstall Python3.11 the correct way: <CUT> #!/bin/bash cd Python-3.11.2 ./configure --enable-optimizations --enable-shared make altinstall # Set Python 3.11 as the Default update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.11 1 # Install PIP using the following command if you do not have it. curl -sS https://bootstrap.pypa.io/get-pip.py | python3.11 </CUT> After this, I installed a fresh venv, activated and installed everything according to ``` https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… ``` MM3 is running fine with uwsgi as documented. I have not deviated even a single step from the documentation above. Now I will test with mod_wsgi and gunicorn and report back. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: mail host choices when creating a new list

by Andrew Hodder

Abhilash, I'm not sure what you're referring to, there's no "web hosts" in the admin panel and I already added the "mail hosts" there (of the four added, only the first one shows up in the postorius drop down). Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Tue, Oct 24, 2017 at 3:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi Andrew, > > On Tue, Oct 24, 2017, at 11:58 AM, Andrew Hodder wrote: > > Hi! > > > > So, I'm trying to create a new list and pick one of the other mail > > domains > > we have configured (from the django admin panel), yet in the "Create New > > List" page in postorius, I see only a single option (the first domain > > we'd > > added/set as the default) in the drop-down under "Mail Host". Am I > > missing > > somewhere else I need to add alternative mail domains to? Thanks in > > advance! > > Yes, you can add new 'Web Hosts' from the Django's Admin console > (admin/django_mailman3/maildomain/). Note that you need to be a > superuser to do this. > > > -- > Abhilash Raj > maxking(a)asynchronous.in >

8 years

[MM3-users] Re: 501 Message has defects

by Mark Sapiro

On 10/25/24 08:06, jgn1980--- via Mailman-users wrote: > Hi > > I'm using GNU Mailman 3.3.8 (Tom Sawyer) on debian 12, and I have this issue on a scheduled e-mail, every day: > > 2024-10-25T04:00:04.874081+01:00 XXXXXXX postfix/lmtp[29258]: CEB32100F44: to=<XXX(a)XXX.XX>, relay=localhost[127.0.0.1]:8024, delay=0.02, delays=0.01/0/0.01/0.01, dsn=5.0.0, status=bounced (host localhost[127.0.0.1] said: 501 Message has defects (in reply to end of DATA command)) Mailman's LMTP runner is parsing the incoming message and it has defects. To see what the defects are, put the raw message in a file and do the following in `mailman shell` ``` $ 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. >>> import email >>> from mailman.email.message import Message >>> msg = email.message_from_binary_file(open('test.eml', 'rb'), Message) >>> msg.defects ``` This should display the defects. Once you know what the defects are, you may be able to adjust the process that produces the scheduled email to create a message without defects. Also see https://gitlab.com/mailman/mailman/-/issues/351 which we should fix to report and/or log the defects. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Exception when rendering certain emails ([Django] ERROR (EXTERNAL IP): Internal Server Error...)

by Stephen J. Turnbull

Matt Blissett via Mailman-users writes: > Thanks ? it's version 3.1.3, so it's these lines: > https://github.com/lepture/mistune/blob/v3.1.3/src/mistune/core.py#L212-L216 OK. The version bump and the assert suggest to me that they've made significant changes. I don't know much about docker, but if you can arrange for the container to be built with "mistune<3.1" in the requirements.txt file or other file specifying the Python packages, that might work better as I cannot recall reports of this kind of problem. (No promises, just going on the "significant changes" guess.) > > If you do not need the Markdown rendering, you can disable it (per > > list). > > "Archive Rendering Mode" for this list is already set to "Plain > text". That's probably something Abhilash Raj <maxking(a)asynchronous.in> needs to look at, as I would think the mistune code should not be called at all in that case. Although the exception seems likely to be a mistune issue, this seems rather a HyperKitty bug. Mark may have some ideas, but I'm pretty sure this is Abhilash's code. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months

[MM3-users]Re: Installation issues

by Andrew Hodgson

Mark Sapiro wrote: >On 04/19/2016 11:40 AM, Andrew Hodgson wrote: > >> I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow? >Sort of, but it's not (yet) public. The process I followed is very >convoluted and not what I would recommend anyone follow. Part of the >issue is I started with mailman-bundler not using a venv, but bundler >still installs a lot of stuff in Python 2 and Python 3 venvs. I then >proceeded to install the git master branches of mailman, >mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their >dependencies system wide and ripped out most of the venv stuff. I started off without using venvs and ran into several issues, though one of them I think was due to the bundler pulling down an outdated dependency. My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. My main thing when looking at this is how package managers are likely to package Mailman3, especially from a Debian point of view. I know I can't second guess what is going to be done, but would like to try to build using similar goals if possible. Thanks. Andrew.

9 years, 6 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/22/21 5:47 PM, dancab(a)caltech.edu wrote: > I've imported a list from Mailman2 and had the owner send a message for testing purposes. > > His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held. > > However if we attempt to view the message in Postorius web UI then an error is thrown. Can you see the message in the held messages view and only get the error when you click the message, or can you not see the held messages view at all? Is it only this list that has an issue? Can you visit other pages for this list? > In the web interface the error is simply "Mailman REST API not available. Please start Mailman core." > > But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below. > > [Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages > > Does "Service Unavailable" mean I'm missing something in the configuration? Possibly, but I don't think so. What is the Traceback from the message Django sends to the server admin? -- 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: Easiest way to install a new mailman3 deployment?

by Allan Hansen

All, 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. 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. Happy New Year to all. Especially to the tireless people who have supported Mailman installations for decades, including my own installations. Without you, not many installations would be humming. Yours, Allan Hansen hansen(a)rc.org > On Dec 31, 2020, at 17:28 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > > > On 12/31/20 8:13 PM, ieso(a)johnwillson.com wrote: >> So I've been trying for the last two weeks to get a new mailman3 server running on a virtualized server (any server), and I'm turning to this list after having failed many times and running out of holiday time. >> >> I started trying a non-docker installation on Ubuntu 18.04 (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) , which got me the closest. Except I had a problem with inbound email only being triggered when it came from certain accounts. But that clearly wasn't good enough for production, so after many attempts to figure out where it was failing, I decided to turn to docker as a solution that should be cleaner. >> >> A few attempts at doing a docker installation on digitalocean.com failed, which I realized might be due to it not routing private IP addresses, so I moved to AWS after checking that their VPC policy would fit mailman's docker requirements. I found a great but slightly outdated guide on how to do this (https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) By this point I knew enough to correct a number of places where the environment had changed since the procedure was written, but postorius still failed at the curl test. >> >> The challenge for me has been the difficulty to know how to troubleshoot the different different systems and network infrastructure that are used to keep mailman3 humming. I've tried about 7 different installation walkthroughs (there are no recent ones on Youtube by the way, in case anyone wants to seize that opportunity!), and the good guides provide ways to check each stage to try to help you a bit on that front. >> >> Nonetheless, I feel stuck and thought I'd ask the simple question... for a completely basic, barebones new installation, what's the easiest way to get a mailman3 installation up-and running? (e.g. Which server provider? Which operating system and version? Docker or otherwise?) >> >> Any pointers highly appreciated. Google Groups is clearly on its way out, as it no longer allows for people to easily join groups by sending an email or clicking a link, so that should be a big opportunity for mailman3 to step up and help give those mailing list migrants a new home... which is what we're looking for. We're just not quite as smart as you guys. ;-) >> _______________________________________________ >> 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/ > > If you are looking for commercial assistance, please visit our Mailman 3 hosting site at https://mailmanhost.com (Harmony Lists). Feel free to contact me off list if you have any questions. > > For us, we chose Debian 10, Postfix, Nginx, and PostgreSQL as the server environment for Mailman 3. We used PIP via a Python virtual environment to install Mailman 3 from source. The Debian packages I believe have older versions of Mailman 3/Postorius/Hyperkitty which is why we went with source. I have a walk-through that is a work in project at: > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > I am available to hire to install Mailman 3 for you if you want to run your own server. > > With Harmony Lists, we went a step further with Mailman 3 and created our own custom interfaces: Affinity (admin) and Empathy (forum/archive). However they are only available to our own Mailman 3 clients. > > Have a Happy New Year. > > -- > 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, 10 months

[MM3-users] Installation Help on Ubuntu 18

by joseverde＠gmail.com

Hi folks, I spent many hours last night trying to get Mailman 3 up and running. I am using Ubuntu on a Digital Ocean LAMP droplet (so PHP, Apache, Sql, and Postfix are already installed). The LAMP stack works as I have a successful installation of YOURLS going on. So, I tried to use this guide (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) to install the Mailman3 package and got to the configuration screen (the one with all the DOS-esque GUI). I ran it but it kept saying the DB wasn't installed. Was I supposed to create SQL databases and users before running that and use those usernames/databases in the credentials it asks for? It doesn't seem like that in the way it asks the questions (since it asks to create a password) but I wasn't sure. Anywho, I tried to remove the package completely and restart but I keep spinning my wheels. So my questions: 1. Does that guide actually work? Did I just foul up the database part? 2. Is there a better way to install mailman3 with some nice step-by-step directions to follow? 3. Is there a way to completely wipe my previous installs without wiping the server? ( I didn't back up...silly I know ). I used apt-get --purge remove to uninstall mailman3 and mailman to start over, did that do the trick? Sorry for all the questions.

5 years, 3 months

[MM3-users] Re: Announce Only List

by hansen＠rc.org

Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 8/13/20 9:49 AM, joseverde(a)gmail.com wrote: > > So if we want to make a list announce only (e.g. > > only specific > > folks) can post, I've found I can set the list settings to > > automatically discard messages from members and non-members. Then > > I go into the individual permissions on each user to be allowed > > to post without moderation. This works fine, however it seems > > cumbersome. > > Don't we have a list style for announce lists? If we don't, we > should.... > I don't see what's "cumbersome" about the individual permissions. You > need to do something per allowed user, if only sending email to > their individual addresses to tell them the password in the anternate > method: > > There is an alternative. Set a moderator_password for > > the list. Then > > anyone can successfully post with an Approved: <password> header or > > pseudo header if they know the password. > > Steve I have a few lists that I set up as announce-only lists by simply dumping all email but that from a couple of authorized members. It's a one-off deal and was trivial to set up. There are more urgent things to spend time on, IMHO. :-)

5 years, 2 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

ok Thank you Mark for your valuable time. I will try this method and let you know the status. Thanks once again. <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> On Wed, Oct 28, 2020 at 12:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/28/20 12:08 AM, Shashikanth Komandoor wrote: > > I tried this way but in this method I don't find any files to edit for my > > customizations like > > 1. Removal of social accounts, > > 2. Addition of SMS integration and so. > > > > If I can do my required customizations through pip installation I am fine > > with that. > > If you follow the instructions for installing in a virtualenv, in say > /opt/mailman/venv, all the component files will be in > /opt/mailman/venv/lib/python3.x/site-packages > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years

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

by Danil Smirnov

Hi Andrew, пт, 26 мар. 2021 г., 23:29 Andrew Hodgson <andrew(a)hodgson.io>: > Danil Smirnov wrote: > > [...] > > >*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. > > Getting this back on topic, would you be willing to share how you are > sending outbound mail through AWS servers without it being marked as spam > by nearly every blacklist out there? I know AWS let you set reverse DNS on > elastic Ips, however whenever I send outbound mail via MX lookups directly > on AWS servers it always gets blacklisted. My solution has been to use an > expensive outbound relay. > > Any suggestions on how you are doing this for users who purchase your > Mailman marketplace image? > I suspect you are talking about ESPs marking incoming mails as spam rather than anti-spam blacklists here. I've posted an article on the topic a while ago: https://blog.smirnov.la/how-to-send-emails-in-2020-3ad76a31a7cc Also, there is a "warm-up" of a new IP for some ESPs (but not for all of them) - 1-2 weeks - that you just need to wait out. Best, Danil > > Thanks. > Andrew. >

4 years, 7 months

[MM3-users] Default Setting for 'Results per Page' and other Web Pull-downs

by Dave Hall

Hello. For the past several months I've been in the process of migrating from Mailman2 to Mailman3 (along with many other tasks). I've just started to use the web interface heavily as I am finally doing the full migration of all my 2.1 lists. Before I ask my question, I am currently running Debian 10 which supplies mailman-3.2.1 and mailman-web 0+20180916, which are definitely old at this point. Although I will soon move to Debian 11, I am still constrained to stick to Debian packages. So if this has been fixed or enhanced in a future version I'm sorry for asking an old question. My question: when I go to any page that has a list (of lists, of members, or archives), there are pulldowns like 'Results per page' that seem to reset to the minimum number when I refresh the page. There are others like 'Hide inactive' on the Archives page. What I'm looking for is a per-user way to customize these values so I don't have to keep on setting them to the value I prefer. If that is available in a later release then I have something to look forward to. If not, it sure would be nice to have. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 years, 5 months

[MM3-users] Re: Process on migrating mailman

by Odhiambo Washington

Once you dump and replace DOMAIN1 with DOMAIN2, everything else should remain the same. PS: Could you please try and not top-post? Put your replies below the ones you receive. On Tue, Jan 23, 2024 at 9:57 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > Just like to confirm when doing this dumping process. Nothing will change > on the current mailing list? > [snip] Once you dump and replace DOMAIN1 with DOMAIN2 globally, everything else should remain the same. Stop both Mailman's processes: ``` systemctl stop mailman3 systemctl stop mailmanweb ``` Assuming that Mailman core and Mailman web were using the same DB (named mailman3), dump the DB and replace DOMAIN1 with DOMAIN2 in the sump file: ``` mysqldump mailman3 > mailman3-DOMAIN1.sql sed "s/DOMAIN1/DOMAIN2/g" mailman3-DOMAIN1.sql > mailman3-DOMAIN2.sql mysql mailman3 < mailman3-DOMAIN2.sql ``` Run the migrations as documented in https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… Restart the processes ``` systemctl start mailman3 systemctl start mailmanweb ``` Of course, check your logs for anything strange and fix it :) PS: Could you please try and not top-post? Put your replies below the ones you receive. -- 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, 9 months

[MM3-users] Re: Search function returning results from another list

by Marco van Tol

Hi there, We actually found that if you look for "*" it will find exclusively messages from the other list, from the first looks of it. But if you "show the archive" in the normal way, without using the search function, it will work as expected. Other lists on the same server show the correct messages when you search for "*", I wonder what went bad with this list. It originally came from a mailman2 server and was imported from that. Thanks! Marco van Tol RIPE NCC On Mon, 14 Oct 2024 at 16:06, Marco van Tol <mvantol(a)ripe.net> wrote: > Hi there, > > We have several lists on our list server here, and noticed that if we do > this: > - go to the archive of public list x > - type in "minutes" in the search bar > > If will: > - show a screen: list-x search results for query "minutes" > - have 3 results in there for another private list > - show a message that you need to login to view the message if you click > on one > > Our current mailman core version is: 3.3.9 > Our current hyperkitty version is: 1.3.10 > Our index engine is: xapian_backend.XapianEngine > > Does this make sense? > > Thanks! > > Marco van Tol > RIPE NCC >

1 year

[MM3-users] Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/16/25 13:43, via Mailman-users wrote: > HI Mark, > > I simply tested by unsubsribing to the mailing list and then re-subscribing to receive the welcome message. > > How do you test using the mailman command with user list? sudo -u list mailman addmembers -h or in your case, you may not have that subcommand in which case see sudo -u list mailman members -h However, that is all irrelevant. I only thought you might be testing by using `mailman` commands to add a member and if so and if the command is not run as user `list`, it might not have access to read the template. If you are (un)subscribing via Postorius or via email these are handled by Mailman runner processes which should all be running as user `list` and should have access to the template. So, as I said, I don't know what the issue is unless it is something with your Debian package which is ancient. Even Debian buster has mailman core 3.2.1. Does your empty list:member:generic:footer.txt work to not add any footer to list messages? If so, I can't think of any reason why your list:user:notice:welcome.txt wouldn't be used. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Re: There are currently no mailing lists!?

by Christian

I meant to say I updated Buster. When I ran 'sudo systemctl start mailman' I get Job for mailman.service failed because the control process exited with error code. See "systemctl status mailman.service" and "journalctl -xe" for details. root@lists:~# systemctl status mailman.service ● mailman.service - GNU Mailing List Manager Loaded: loaded (/lib/systemd/system/mailman.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2024-07-23 04:15:47 PDT; 10s ago Process: 1357 ExecStart=/opt/mailman/mm/bin/mailman start (code=exited, status=2) Jul 23 04:15:46 lists.gaiapacha.ie systemd[1]: Starting GNU Mailing List Manager... Jul 23 04:15:47 lists.gaiapacha.ie mailman[1357]: Usage: mailman start [OPTIONS] Jul 23 04:15:47 lists.gaiapacha.ie mailman[1357]: Try 'mailman start -h' for help. Jul 23 04:15:47 lists.gaiapacha.ie mailman[1357]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: mailman.service: Control process exited, code=exited, status=2/INVALIDARGUMENT Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: mailman.service: Failed with result 'exit-code'. Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: Failed to start GNU Mailing List Manager. root@lists:~# journalctl -xe Jul 23 04:14:54 lists.gaiapacha.ie postfix/smtpd[1042]: 591AD2403D7: client=localhost[127.0.0.1] Jul 23 04:14:54 lists.gaiapacha.ie postfix/cleanup[1046]: 591AD2403D7: warning: header Subject: [Django] ERROR (EXTERNAL IP): Service Unavailable: /mailman3/system/ from localhost[127 Jul 23 04:14:54 lists.gaiapacha.ie postfix/cleanup[1046]: 591AD2403D7: message-id=<172173329436.628.16645057357232267420(a)lists.gaiapacha.ie> Jul 23 04:14:54 lists.gaiapacha.ie postfix/qmgr[744]: 591AD2403D7: from=<noreply(a)lists.gaiapacha.ie>, size=19287, nrcpt=1 (queue active) Jul 23 04:14:54 lists.gaiapacha.ie postfix/smtpd[1042]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Jul 23 04:14:54 lists.gaiapacha.ie postfix/smtp[1047]: 591AD2403D7: to=<csa(a)web-analysts.net>, relay=box.ecovillage.cc[45.79.28.18]:25, delay=0.15, delays=0/0/0/0.14, dsn=2.0.0, statu Jul 23 04:14:54 lists.gaiapacha.ie postfix/qmgr[744]: 591AD2403D7: removed Jul 23 04:14:54 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=104.156.155.36 DST=192.46.218.224 LEN=40 TOS=0x00 PREC=0x00 TTL=2 Jul 23 04:14:55 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=3.142.189.15 DST=192.46.218.224 LEN=40 TOS=0x00 PREC=0x00 TTL=234 Jul 23 04:14:56 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=103.99.1.78 DST=192.46.218.224 LEN=40 TOS=0x00 PREC=0x00 TTL=238 Jul 23 04:14:57 lists.gaiapacha.ie python[621]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory Jul 23 04:14:58 lists.gaiapacha.ie python[639]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory Jul 23 04:14:59 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=45.227.253.131 DST=192.46.218.224 LEN=40 TOS=0x08 PREC=0x20 TTL=2 Jul 23 04:14:59 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=104.156.155.36 DST=192.46.218.224 LEN=40 TOS=0x00 PREC=0x00 TTL=2 Jul 23 04:15:01 lists.gaiapacha.ie CRON[1135]: pam_unix(cron:session): session opened for user root by (uid=0) Jul 23 04:15:01 lists.gaiapacha.ie CRON[1136]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Jul 23 04:15:01 lists.gaiapacha.ie CRON[1135]: pam_unix(cron:session): session closed for user root Jul 23 04:15:03 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=79.110.62.133 DST=192.46.218.224 LEN=40 TOS=0x00 PREC=0x00 TTL=23 Jul 23 04:15:25 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=104.156.155.36 DST=192.46.218.224 LEN=40 TOS=0x00 PREC=0x00 TTL=2 Jul 23 04:15:46 lists.gaiapacha.ie systemd[1]: Starting GNU Mailing List Manager... -- Subject: A start job for unit mailman.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit mailman.service has begun execution. -- -- The job identifier is 239. Jul 23 04:15:47 lists.gaiapacha.ie mailman[1357]: Usage: mailman start [OPTIONS] Jul 23 04:15:47 lists.gaiapacha.ie mailman[1357]: Try 'mailman start -h' for help. Jul 23 04:15:47 lists.gaiapacha.ie mailman[1357]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force Jul 23 04:15:47 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=172.206.148.147 DST=192.46.218.224 LEN=40 TOS=0x00 PREC=0x00 TTL= Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: mailman.service: Control process exited, code=exited, status=2/INVALIDARGUMENT -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit mailman.service has exited. -- -- The process' exit code is 'exited' and its exit status is 2. Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: mailman.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit mailman.service has entered the 'failed' state with result 'exit-code'. Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: Failed to start GNU Mailing List Manager. -- Subject: A start job for unit mailman.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit mailman.service has finished with a failure. -- -- The job identifier is 239 and the job result is failed. Jul 23 04:16:04 lists.gaiapacha.ie kernel: [UFW BLOCK] IN=eth0 OUT= MAC=f2:3c:94:e9:54:57:00:00:0c:9f:f0:1e:08:00 SRC=79.110.62.213 DST=192.46.218.224 LEN=40 TOS=0x00 PREC=0x00 TTL=23 lines 1745-1798/1798 (END) -----Original Message----- From: Odhiambo Washington via Mailman-users <mailman-users(a)mailman3.org> Sent: Monday, July 22, 2024 3:48 PM To: csa(a)web-analysts.net Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Re: There are currently no mailing lists!? On Mon, Jul 22, 2024 at 9:06 PM Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > I recently upgraded Debian 10 'buster' and when I logged in to > Postorius in the browser I got the ' Mailman REST API not available. > Please start Mailman core' message. So I started it up from the > command line doing 'sudo -u mailman /opt/mailman/mm/venv/bin/mailman > start -f' which yielded > You upgraded Debian from Buster to what??? Bullseye or Bookworm? Why not just 'sudo systemctl start mailman'? > Starting Mailman's master runner > Generating MTA alias maps > mailman@lists: > > Now when I do ' > https://lists.ccalternatives.org/mailman3/lists/?all-lists > ' > in my browser I get the message ' There are currently no mailing lists.' > Meanwhile their archives exist. Are the lists actually gone or ? > The lists are there since your DB is intact and your venv is intact as well. > > What am I doing wrong/what's going on here please? Thank you in advance. > I suspect your Python was upgraded to a version different than the one you use to create your virtualenv in the 1st place. If that is the case, you'll need to create a new virtualenv and migrate the data. > One more thing...I am running mailman core version GNU Mailman 3.3.5, > Core API Version 3.1, and Core Python Version 3.7.3. > Is there a reason you did not upgrade MM3 core and MM3 Web all this time? Anyway, check the version of Python used to build your virtualenv against the system version after you upgraded: # cat /opt/mailman/mm/venv/pyvenv.cfg home = /usr/local/bin include-system-site-packages = false version = 3.11.2 executable = /usr/local/bin/python3.11 command = /usr/local/bin/python -m venv /opt/mailman/mm/venv If older than the system version, you just need to build a new virtualenv and migrate the data. HTH. -- 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] _______________________________________________ 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 csa(a)web-analysts.net

1 year, 3 months

[MM3-users] Re: User management page [was: Changing subscription address]

by Abhilash Raj

> On Mar 20, 2021, at 6:22 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Core implementation details, so I beinging this here from Mailman > Users @ mailman3.org. > > Abhilash Raj writes: > >> I have started working on designing a User management page[2] in >> Core which should make it easy for superuser to manage several >> things about a User, including the ones that don’t have an account >> in Postorius to manage their own. > > I don't understand this design with a "page in Core”. Typo :( Page in Postorius is what I meant to say. > I was thinking > about this kind of problem, and tentatively came to the conclusion > that any reference to something that can be resolved to a User should > generate a Django account for that User in Postorius or HyperKitty. Is that necessarily required? Every user in Django has a corresponding user in Core, but the converse isn’t true and I am not sure if that is even required. The purpose of a Django account is to manage my own email addresses and subscriptions. An admin can manage a Core User that does or doesn’t have a Django account. The only thing that changes is what they can do with that user. See below for my thoughts on the actions an admin would be able to perform. The high level design of that user management page is that it will provide a list of Users straight from Core. When you go to an individual User’s management page, You will be able to see: - Does the user have a Django account? - All Subscriptions for the User - All addresses of the User You will be able to perform following actions: - Add or remove a user’s address - Verify or un-verify an address - Set any address as primary for the user - Update display name of the user - Update address on any of the subscriptions If the User has a Django account, you also be able to: - Manage the User’s password *if* they are using password for login and not social auth. - Reset “social login” for the user? - View some of the RO info about the Django User model, like last login, superuser status or few other attributes that we feel is useful for admin in any situation. What I am on fence about: - Provide a full blown preferences menu to the admin for that user. This will also make the UI extremely complex to see and implement. > Authorization to use that account would still require authentication > via the usual email verification dance, or some level of admin > privilege. > > The thing is that emails that have not been added to a User are > unique. They will be the only Address attached to User created to > manage them until authenticated, and transitively the only address > attached to an automatically-created Django account (since those are > 1-1 with core Users if they exist AFAIK). In Core, when a new address (email1) comes in, a Mailman User(user1) is created for it. But, when you have an account in Django with a different email (email2) and a different Mailman user (user2) and you add a second email (email1) to your account and are able to prove ownership by verifying the address, Django will ask Core to add that second address (email1) to your Mailman user (user2) and absorb “user1”. This process is already implemented. However, if two Django accounts are created for “user1” and “user2” then situation becomes more tricky and currently we don’t have a way to resolve that short of delete one of the accounts and add the addresses to other account. > What's missing here is the ability to merge core Users and their > corresponding Django accounts. Doing this with nothing more than the > usual email verification dance is not *obviously* provably secure to > me, so we need to be careful, but I think it probably will turn out to > be as secure as you can get. It seems to me that User merging is the > most pressing problem of this kind. (At least, it affects me on a > couple of list hosts, as well as on GitHub and GitLab.) > >> [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605 > > I'll take a look tomorrow or early next week. It is far from actually usable, so you can actually skip it for now ;-) I can announce it when it is in semi-usable state. -- thanks, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] Re: Upgrade Mailmam Core from

by sascha.rissel＠gmail.com

Hi all, as Mark suggested, I delete the venv and started anew, making sure that I do > sudo su mailman before creating the venv again. Executing > pip install wheel mailman psycopg2-binary\<2.9 led to the same error message as in my post https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… saying > error: invalid command 'bdist_wheel' six times, namely for: > ERROR: Failed building wheel for mailman > ERROR: Failed building wheel for authheaders > ERROR: Failed building wheel for authres > ERROR: Failed building wheel for lazr.config > ERROR: Failed building wheel for dkimpy > ERROR: Failed building wheel for lazr.delegates After this, I deleted the venv again and startet anew, again. But this time, I explicitly did (as Stephen suggested above) > pip install wheel prior to > pip install wheel mailman psycopg2-binary\<2.9 This time, it ran through without errors, although "wheel" is also contained in the latter command. Can you explain that? Second question: There is still no directory "/etc/mailman3" created, where I can create mailman.cfg in. Does this maybe result from the fact that in first instance, I tried to install mailman3-full via "apt-get install" and removed it again via "apt-get remove"; with manually deleting /etc/mailman3 afterwards. Shall I create /etc/mailman3 manually and adding "mailman" system user permissions? In advance, thanks again for your help!

3 years, 1 month

[MM3-users] Re: no mails to list members

by Thomas Stein

On 04.01.19 05:15, Stephen J. Turnbull wrote: > Thomas Stein writes: > > > Thanks for your answer. So the the file in queue/shunt contains > > information too? I will have a look. > > The file in queue/shunt is the message plus some Mailman metadata, as > a Python pickle. You can find out what is in it using "bin/mailman.py > qfile", but probably the log and traceback will tell you (or us) > everything needed to fix the problem. > > If it's a Mailman bug (somewhat unlikely), we send you a patch and you > use "bin/mailman.py unshunt" to reinject the message into the mail > system via Mailman. If it's a nonconforming mail message (somewhat > more likely -- typically this happens when you have raw UTF-8 or other > 8-bit characters in the message header), then the easiest thing to do > is to edit a saved copy of the message and resend from your mail > client. (It's theoretically possible to edit the pickle and use > "unshunt", but Mailman currently does not provide that feature.) Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe i missed something else but after adjusting the permissions of that template everything worked as expected. Again. Thanks for your help. t.

6 years, 10 months

[MM3-users] Re: Getting an error for every post made to any list

by Mark Sapiro

On 4/22/25 1:35 PM, sun zi via Mailman-users wrote: > As mentioned in the subject, I am getting the following error after every post. Any assistance would be much appreciated: The error is from an attempt to archive a message. Since it fails, the problem message is queued in Mailman's var/archives/hyperkitty/spool/ directory and is retried with each post. The message is in a Python pickle, *.pck, file in that directory. Yoy can examine the message by giving it to `mailman qfile`. From the tracebacks you posted, it appears that the issue is that the sender's address is longer than 255 bytes. Move the .pck file out of the var/archives/hyperkitty/spool/ directory and that will stop the recurring error. If the message is spam you can ignore it. If you want to archive it you need to edit the message's sender, but you can't edit the *.pck directly. You can use `mailman shell` and do something like ``` import pickle with open('path/to/the/pickle', 'rb') as fp: msg = pickle.load(fp) # code here to edit the sender with open('path/to/the/pickle', 'wb') as fp: msg = pickle.dump(msg, fp) ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: Internal Server Error: Reattach this thread

by Mark Sapiro

On 10/18/22 21:38, hasimoto(a)designet.co.jp wrote: > Hi, > > In the archive, clicking "Reconnect this thread" causes an internal server error. > I received the following email, but I don't know how to solve it, please help me. How big is the archive in which you are doing this? Are you running the periodic django-admin jobs via cron? See https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/crontab I ask because I've now seen this issue in a test installation, but only with an archive containing only one message. The particular steps I followed somewhat by accident were: Start with an archive containing only two messages in separate threads. Open one thread and `Delete this thread` leaving only one thread. Open that thread and click `Reattach this thread` - this produces the error. Restore the deleted message/thread with `hyperkitty_import` Clicking `Reattach this thread` in either thread produces the error. After running the hourly and daily django-admin jobs, clicking `Reattach this thread` in either thread works as expected. That scenario with deleting and restoring a thread was somewhat accidental, but did produce the error. in other list archives on the same server, even one containing only one message, clicking `Reattach this thread` in either thread works as expected. -- 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: lmtp runner not starting

by Mark Sapiro

On 4/1/23 12:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > El 1/4/23 a las 21:14, Mark Sapiro escribió: >> >> If you had completely stopped Mailman core and then started it, lmtp >> runner should have started. What are the complete log messages from >> mailman.log following the start? >> > I sent them before And there is no `lmtp runner started` message in the log, so it isn't being started at all. >> What does `mailman conf -s runner.lmtp` show? >> > Here it is: > > root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c > "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf > -s runner.lmtp" > [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner > [runner.lmtp] instances: 1 > [runner.lmtp] max_restarts: 10 > [runner.lmtp] path: > [runner.lmtp] sleep_time: 1s > [runner.lmtp] start: yes This says the runner should be started. That is the command that starts Mailman? is it /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg start" or is it something that perhaps uses a different config. What happens if you do /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" -- 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] more about spanish translations

by Guillermo Hernandez (Oldno7)

I've just made a test creating a user in postorius to change an address that already has a suscription (from mailman 2.1). It's a test address with the digest enabled to be aware from any problem in the digest sending messages (e.g. I had to change all digest addresses to mime whe I did the migration from 2.1) The fact is that I cannot find from which template or Weblate term chains it could be from, and the address confirmation email is a language mix in spanish and english. I copy it down. I would like to translate it all, but as said, I cannot find where to do it. I wonder if it's comes from another package as allauth or something like this. Here is the mail: Subject: =?utf-8?q?=5Bescepticos=2Ees=5D_Por_favor_confirmar_direcci=C3=B3n_de_correo?= =?utf-8?q?_electr=C3=B3nico?= From: postorius(a)XXXXXXXXXXX.es To: XXXXXXXX(a)gmail.com Date: Fri, 19 Feb 2021 10:26:26 -0000 Message-ID: <161373038620.5080.16387108004007982309(a)XXXXXXX.es> X-Spam-Status: No, score=-1.0 required=8.0 tests=ALL_TRUSTED=-1,URIBL_BLOCKED=0.001 <dns:XXXXXXXXX.es> [172.67.131.28, 104.21.3.190] <dns:XXXXXXXXXX.es?type=MX> [0 XXXXXXXXXXXX.es.] autolearn=unavailable autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on XXXXXXXXXXX.es Hello from XXXXXXXXXXX.es! You're receiving this e-mail because user XXXXXXXXXX(a)gmail.com has given your e-mail address to register an account on XXXXXXXXXXXXXXX.es. To confirm this is correct, go to https://XXXXXXXXXXX.es/mailman3/accounts/confirm-email/MTM:1lD2zR:3GpALYKI1… Muchas gracias por usar XXXXXXXXXX.es! XXXXXXXXXXX.es

4 years, 8 months

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

by Abhilash Raj

On Mon, Aug 30, 2021, at 8:46 AM, 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. I don't think we have any changes since last release related to enhancements in bounce processing, there have been some bug fixes through which occasionally can cause bounce runner to cause some issues by keeping open transactions for quite long. -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: Displaying addresses in emails from a Mailman 3 installation

by Steve Brown

Yes, I intended to post to the list. I now see that if I use the archives to post (as I'm doing now), I have to use "reply all". On my Outlook, it's the other way around. If I want to reply off-list, I have to click on reply all and then remove the list address. Sorry. I only use the Gmail address for a few limited purposes. I did set First Strip to a hard no. I' m going to have to think more about the unconditional DMARC. Given what you said, I may well cause more grief than I alleviate. Our list (lists.radg.us) has only about 60 members, but with a lot of different email configurations. Gmail, Yahoo/AOL, Hotmail and similar, academic .edu domains, corporate domains, email offered by ISPs, and personal domains like yours. I use two .us domains, one registered and hosted by TMD and one by Hostinger, because they were relatively cheap. I don't see any apple iCloud, but maybe that's because they use a domain alias. Many if not most of the subscribers to RADG are not very IT savvy, so I suspect that using the archive for search or posting would also seem like a PITA. But I may suggest it after he cools down. Thanks again for the help. Steve B

4 months

[MM3-users] Re: Mailman3-Web lots of database queries

by Abhilash Raj

On Thu, Nov 22, 2018, at 2:14 AM, Stefan Tatschner wrote: > On Sun, 2018-11-18 at 14:38 -0800, Mark Sapiro wrote: > > No. This is not normal. This is apparently coming from Django qcluster. > > At least it is qcluster that uses the django_q_ormq table, but these > > repeated queries are not normal, at least I don't see them in the sites > > I administer. > > These calls are normal, since qcluster polls the database at a high > rate: > > https://django-q.readthedocs.io/en/latest/configure.html#poll > > Fortunately this setting can be reduced, but yeah, polling happens > though. So, if you are using Django's ORM to keep the task states in Django Q, this is bound to happen depending on how frequently do you run tasks. In Hyperkitty, we have some minutely tasks, which means the polling is going to be high. You can however, configure Django Q to store the tasks outside of database in a better high-speed in-memory database like Redis for example[1] for queuing the tasks. Other options like MongoDB, Amazon SQS is also available. [1]: https://django-q.readthedocs.io/en/latest/configure.html#redis > > Stefan > _______________________________________________ > 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, 11 months

[MM3-users] Re: Separating Lists by Domain

by Abhilash Raj

On Sun, Dec 23, 2018, at 4:42 PM, brian(a)emwd.com wrote: > I have successfully setup a second domain with my Mailman3 setup. I > also created a list using the second domain. So I have two domains with > one list each. The issue I see at this point is all of the lists are > shown via Postorius regardless of the list domain used. Is it possible > to have only the lists to show that are part of the domain being used > to access? For example: > > http://domaina.com/postorius/lists/ > > Only listnames(a)domaina.com show up. > > http://domainb.com/postorius/lists/ > Only listnames(a)domainb.com show up. > > Right now both domaina AND domainb lists showup regardless of the > domain being used to access Postorius. The same goes for Hyperkitty as > well. You can do that this in Hyperkitty. Setting FILTER_VHOSTS = True in Django's settings.py (or settings_local.py, if you are using container images) will filter the lists for the current "Host:" header in the request. Postorius doesn't have this ability yet, but wouldn't be too much work to add that. Pull requests are welcome :) > > 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)

6 years, 10 months

[MM3-users] Re: Migrating Mailman 3 lists

by Andrew Hodgson

Brian Carpenter wrote: >I know how to migrate mailman 2 lists to a new mailman 3 server. However I do not know how to migrate a mailman 3 list from one mailman 3 server to another one. Are there any instructions or protocol on how to accomplish this? >The Mailman 3 server I want to migrate *from* was setup using Docker. The Mailman 3 server I want to migrate these lists *to* was setup using a python virtual environment via pip. I did this the other week, the difference I think we've got here is that I migrated the whole instance (Mailman Core's var files plus complete Postgresql database) over to the new server rather than trying to add the lists to an existing setup, which I couldn't work out either which is what prompted me to complete the server migration before adding more lists. The only issue I ran into was not copying the Mailman Core var files to the new server, this actually gave me a bit of trouble later on as firstly Mailman doesn't create the lists directory which is what I was checking with Exim for list existence, and also I had an issue where I was missing a moderated message from the messages directory which stopped the admin interface from displaying for that list. However if anything would help on my experience would be happy to share more info. Andrew.

5 years, 6 months

[MM3-users] AH01102: error reading status line from remote server 172.19.199.3:8000

by Henrik Rasmussen

I've just installed Mailman 3.1 on RHEL7 (Docker-Mailman3) and to get the right CSS layout I installed Apache on the Mailman server outside Docker, as advised by Abhilash Raj and Alexander Klotz. My Mailman server is on a secured network and the https connection from Internet will be handled by proxy servers, so I will be using http (port 80) between proxy-servers and Mailman server. But when I sign in (currently via an SSH tunnel to the Mailman server from my workstation) I get "Internal error: [client ::1:41912] AH01102: error reading status line from remote server 172.19.199.3:8000, referer: http://localhost/accounts/login/?next=%2Fpostorius%2Flists%2F" If I type a wrong password, I am just warned about that, so the problem appears when log in is accepted. I expect that it is because I connect to localhost:80 through SSH tunnel. What do I miss in my Apache configuration on the Mailman server to avoid this problem? <VirtualHost *:80> ErrorLog /var/log/httpd/error_log LogLevel warn CustomLog /var/log/httpd/access_log combined ServerAdmin root(a)example.foo ServerName list.foo.bar Alias /static /opt/mailman/web/static Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico ProxyPassMatch ^/static/.* ! ProxyPass / http://172.19.199.3:8000/ ProxyPassReverse / http://172.19.199.3:8000/ <Directory /> Allow from all Require all granted </Directory> <Directory /opt/mailman/web/static/hyperkitty/img/> Allow from all Require all granted </Directory> # ssl config here ... </VirtualHost> Thanks, Henrik Rasmussen

8 years, 3 months

[MM3-users] Re: ARC signing outgoing mails

by Mark Sapiro

On 11/1/19 4:04 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > in > https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign… > I found this hint > > "It is highly recommended that Mailman maintainers configure ARC siging > of their outgoing email. ..." > > So I added in my mailman.cfg: > " > [ARC] > privkey: /path/to/private.key > " > > > But I don't understand the meaning of > > > "... and located at: > " > #{config.ARC.selector}._domainkeys.#{config.ARC.domain} –ex.– > test._domainkeys.example.com > " This doesn't seem correct. The DNS TXT record should be added to #{config.ARC.selector}._domainkey.#{config.ARC.domain} (note _domainkey, not _domainkeys) I.e., this is a normal DNS TXT record containing the public key for DKIM signing. > Where can I find this string or where do I have to place it. I am using > bind9 as dns-handler. Read the entire ARC section beginning at <https://gitlab.com/mailman/mailman/blob/master/src/mailman/config/schema.cf…>. You have to configure more than just privkey. Once you have configured enabled: yes privkey: /some/location/yourprivatekey.pem selector: test (or whatever you want) domain: your_domain.com The substitutions for #{config.ARC.selector} and #{config.ARC.domain} should be more clear. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[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, 8 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Kimmo L

Hi Stephen! Thanks for trying to help me out! > > That's an unfamiliar format to me. Is this a Linux system running > systemd? Our mailman + hyperkitty runs on RHEL 8 and yes, all the services are systemd format. > How much swap do you have, and how much is in use? > What other daemons are running on the host besides Mailman? Host has 8GB swap at the moment ,which decreases in small steps if main memory is consumed. But if this happens, then something happens and there is again couple of hundreds free memory. In addition to the above mentioned services, there is also NGINX and postfix services as well. > Have you modified any web pages associated with Mailman, including any > of the Django templates? Are there any pages with unusually long load > times? No and usually all pages are very smooth. Only if i open archives, then sometimes it will load like sec or three. I also noticed that after midnight, if one of the mailman-web cronjob was finished, the free memory jumped from 100mb to 1gb. And then it will start to decrease again. I will try to investigate little bit more and play little bit with the services to be sure, that the issue is related with mailman or gunicorn or with something else.

3 years, 2 months

[MM3-users] Upgrading a Ubuntu Mailman 3 Installation

by Allan Hansen

Dear Mailman 3 wizards, Several years ago I tried upgrading to Mailman 3 (I did install Mailman 2), but quickly ran into a thicket too complex for me to get out of. Two others - way more experienced than me at system-level manipulations - tried as well but did not succeed. Brian Carpenter of EMWD installed the system seemingly effortlessly, and seemingly overnight. We had a good relationship, and I was a beta site for his new product, SAAS. Brian also did the system MM3 upgrades as they appeared and would check that all was well a couple of times a year. Unfortunately, and I respect that, the current management at EMWD "don't provide working hands service for foreign Mailman 3 installations." I do not dare touch it, based on my earlier attempts with the installation. With Brian's passing I'm thus faced with a system that has no capable system support (I manage the lists, not the core). I have 50+ lists with 10000+ subscription total, and a lot of people depend on this tool. (It's a non-profit organization). So, I'm interesting in hiring someone for part-time, occasional work (a few times a year). Update MM3 as new versions are made available. Diagnose and fix the system if anything goes awry. I will pay you, as I did Brian, out of my own pocket, for your time. Yours, Allan Hansen

2 years, 11 months

[MM3-users] Re: Must every Moderator/Admin be member of a list to be able to use Postorius?

by Mark Sapiro

On 1/31/23 10:25, mm3-omf(a)sh.werbittewas.de wrote: > we're using debian/devuan with distribution-mailman3 and tried to add > admin/mod for a list, but if logging in as this user, there's no item to > manage the list at all. That's strange. If the logged in user is a moderator she should see the Subscription requests and Held messages tabs and with Postorius >= 1.3.9b1 also the Members tab, and if she is an owner she should see the full admin UI without needing to be a member. Are you sure the logged in user is the same user that's an owner/moderator? Log in as a superuser and find the user in the User's view fron the top nav bar in Postorius, click Manage to see all that user's roles and web account. > do we have to add this user as member of this list? > (that wouldn't be nice, because the user doesn't want to get normal > Mails from List, but only admin-Mails) It shouldn't be necessary, but a delivery can always be disabled for a member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 09:19, Allan Hansen wrote: > Mark, > > I tried doing this. > I unsubscribed myself from a list, set the policy as you suggest and re-applied. > I got no confirmation messages but as moderator I got the moderate message. How did you reapply? with the subscribe policy confirm then moderate a new subscriber should get the list:user:action:subscribe message and have to confirm before the request waits moderation? However, see below. > I then tried a bogus email and saw that a message was sent to that and no moderator message to me. > Would the server skip the verification message because I'm a moderator/admin? It's not because you are an admin. It's because you were logged in when you subscribed from the list's info page. You will need to confirm if you subscribe anonymously without logging in or subscribe via email, but if you are logged in to Postorius when you request subscription, that is sufficient confirmation that the request really comes from you, so you don't get an email confirmation. So, depending on your circumstances, this may or may not work for you. -- 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: Can't subscribe on new site/domain

by Flo

On 10/9/25 17:06, Stephen J. Turnbull wrote: > Odhiambo Washington via Mailman-users writes: > > > You can remedy that by wiping away the packages and installing MM3 > > by following the guide below: > > > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > @Flo: It is possible to do this safely and preserve your existing > sites and lists. If we can't help you with your existing > installation, we can guide you through this process. The basic idea > is that because almost all the interesting data is in your database or > /etc/mailman3, you can just plug in the new Mailman system, point > things at the right places (probably the file system layout will > change so you'll need to change some things in mailman.cfg, > settings.py, and some related systems like logrotate and systemd). > Usually I avoid installing software directly as there is more maintenance effort than having installed it from OS-packages. In this case I see that I have permanently troubles with this software (OS-packages) so your suggestion is worth to consider. Is there a possibility to export all members including real names. It doesn't work with Postorius, yet, is there another possibility? If I have my user data exported, I could delete everything and start from scratch. Maybe this is the most reasonable ... Flo

3 weeks, 5 days

[MM3-users] Re: bounces with empty message-id

by Peter Münster

On Wed, Jan 31 2018, Mark Sapiro wrote: >> I have verp_delivery_interval = 10 ... > > Which says only every 10th message will be VERPed. You want > verp_delivery_interval = 1 to VERP every message. Hi, Why? The smtp relay host would get much more outgoing messages. With verp_delivery_interval = 10, only 10% of the messages would be personalized. Shouldn't this be enough to detect sooner or later, that a recipient address is no more valid? Or is it important, to detect such failure immediately? > The message does appear in the mail log, but until the issues below are > fixed, even if Mailman receives it, you won't see it. Ok. For now, I could do a grep of the syslog messages of Postfix, for example once per month, to check for DSNs. > They should be processed by Mailman and scored as bounces for the > recipient if recognized and forwarded if not (depending on settings), > but they currently are only stored. Ok. >> The question for me is: does the remote MTA needs a fix (i.e. the >> Message-ID is required by some RFC), or mailman (i.e. a DSN without >> Message-ID should be acceptable)? > > I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. Thanks! That means, that I won't need to teach Postfix to add a Message-ID to the DSNs. :) Kind regards, -- Peter

7 years, 9 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/9/21 4:05 PM, Duane Raymond wrote: >> As I said there, Mailman is going through the roster of regular >> (non-digest) list members to find those with delivery enabled and it >> finds a member that has no associated address. Can you view the members >> of this list? > > Yes - the list has three members (test list): me and two others. For my subscription I have gone through the membership options and explicitly set them. For the others their membership options are all unselected and thus I assume defaulting to a fallback value. (not sure if that matters) What matters is at least one of those members doesn't have an associated address record. If you have access to `mailman shell` do the following: mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for mbr in m.members.members: ... if mbr.address is None: ... print('user: {}, user.addresses: {}'.format( ''' mbr.user, mbr.user.addresses)) ... And see what that gives you. (At the last ... prompt just type `enter`) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

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

4 years, 5 months

[MM3-users] Hyperkitty django.request forbidden

by Stephen J. Turnbull

Arpad Horvath via Mailman-users writes: > I moved from mailman to mailman3 in 2021. I hadn't have the time to > fix the archiving. I can see the emails older then that in > Hyperkitty, but none of the once still there is mailman3. What can > be the problem? I don't understand "none of the once still there is mailman3". Do you mean none of the emails sent since the upgrade from Mailman 2 to Mailman 3 are not visible in HyperKitty? > It's a Debian 12, I use the packages from the repo. > ERROR 2025-02-26 06:47:31,705 861 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP xxx.xxx.xxx.xxx, your MAILMAN_ARCHIVER_FROM setting may be misconfigured [...] > I have this line in /etc/mailman3/mailman-web.py > > MAILMAN_ARCHIVER_FROM = ('https://lists.somewhere.xx/hyperkitty', '::1') Where did that line come from? Did you put it there? If so, don't worry about it, we'll figure out what goes there. If not, investigate a bit and if it seems like it came from debconf, you may want to report an issue to Debian. I think Django is failing to parse that. It expects hosts, not URLs. The default is: MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') I would just comment out that line in mailman-web.py and restart. If it starts working, then I suggest removing it entirely. Steve

8 months

[MM3-users] Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 14:37 GMT+01:00 Simon Hanna <simon(a)hannaweb.eu>: > On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > >> Imagine an installation with 500+ mailing lists and almost as many local >> admins that are supposed to maintain their own local lists with a few >> local >> members. As site admin, I see all 500+ lists, but I was expecting *local* >> admins to see only the lists they maintain. I have set all lists to >> "advertised = False", so they are hidden from ordinary view. Is there a >> way >> to show only relevant lists to local admins? >> > Are we talking about Postorius or Hyperkitty? > There is no way for users that do not have the django superuser permission, > to see unadvertised lists in the Postorius list index. I just > doublechecked the source. > There is an issue about list filtering/search for the index page. > I believe I wrote Postorius in the subject line, but it may not be so obvious. So yes, in Posterius I would like to hide the lists from email harvesters, while relatively "untrusted" admins should have access to basic operations on the one list he/she "owns" (and without having to browse through 50 pages of mailing lists). Somehow I don't think 500 superusers in our system is a good idea!

7 years, 9 months

[MM3-users] Re: Running Mailman3 under supervisord

by Abhilash Raj

On Mon, Jul 27, 2020, at 9:49 AM, Odhiambo Washington wrote: > > > On Mon, 27 Jul 2020 at 18:38, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> >> >> On Sun, Jul 26, 2020, at 6:08 AM, Odhiambo Washington wrote: >> > Hello world, >> > >> > Is it possible to run MM3 under supervisord? >> > What would I use for command= ?? >> >> >> If you want something that doesn't fork into the background, then you can run "master start" command. It will stay in the front and supervisord can monitor the pid. >> >> I do the same for the container images. > > > Hi Abilash, > > Might you be able to share your how you have configured that all that in supervisord.conf? I don’t use supervisord, I simply run “master —force” in the container images. Container managers often negate the need to have supervisord. Edit: Sorry for the wrong command in the last email, it is simply “master” and I run with “—force” to skip any issues with locks that happens when the container is stopped faster than Core can shut down cleanly. For refernce https://github.com/maxking/docker-mailman/blob/master/core/Dockerfile#L31 Abhilash > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) -- thanks, Abhilash Raj (maxking)

5 years, 3 months

[MM3-users] "The content of this message was lost."

by skenny＠scss.tcd.ie

I see that this issue has been discussed in a few other postings - it seems to be affecting us here at the moment. We're running Mailman 3.3.5 inside maxking's mailman-core/mailman-web Docker containers (version 0.4.3). This morning I composed a mail message and included two of our mailing lists in the To: field. On the first list I'm a member with address of the form my_addr_1(a)this.com. On the second I'm on it with a different address, my_addr_2(a)that.com. In the case of each list, Mailman held the message for moderation. As administrator, I accepted both. I then got the full message in my inbox at my_addr_1(a)this.com, but in my other inbox at my_addr_2(a)that.com, the body of the message was not present. Instead it read The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. I'm wondering what's the best thing to do here. Should I maybe downgrade to an earlier version of Mailman (i.e. an earlier version of maxking's Docker containers), pending resolution of this issue ...? Thanks for any advice. Stephen PS: The Mailman web interface "System Information" link reports: Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0]

3 years, 1 month

[MM3-users] migration from 2.1 - owners and moderators

by Alex Schuilenburg

We're migrating from 2.1 to 3.2.1 and an odd issue has popped up. It may be something different in the way mailman3 works, or a misconfiguration on my part. Most of the lists migrated so far don't have moderators, just owners. However, when these lists have messages requiring moderation, the owners dont get notified of held messages - unlike 2.1 where they did. Is this a change or is there something I am missing in the configuration? I have the minute/quarterly/hourly etc cron jobs running, although I have had to tune down the frequency of minute to hourly as it takes 6.5 minutes to run* - but I doubt this is the cause. While for the moment I have found the held messages in files in /var/lib/mailman3/messages and figured out which lists are in need of attention (and notified the owners), it seems I may have to do a bit of coding myself to walk through the lists and notify owners when their list is in need of attention. There must surely be something that does this already - or is this moderators only in mailman3? Guidance appreciated. Thanks -- Alex * From the list I realise this is because I am still using the default whoosh backend to haystack and need urgently to switch to xapian or solr, but the info on how to get this working for a noob like me is unfortunately lacking :-(

5 years

[MM3-users] Re: How to promote non-members to members?

by Mark Sapiro

On 3/17/22 12:25, Quanah Gibson-Mount wrote: > > I've done nothing in regard to this user. Neither command returns > anything. Well, something has deleted the user, but ... >> If the user is gone, you should be able to replace >> ``` >> ... sub_mgr.confirm(token) >> ``` >> in the above with >> ``` >> ... wfm = getUtility(IWorkflowStateManager) >> ... pendings.confirm(token, expunge=True) >> ... wfm.discard(token) >> ``` >> to clear the pending subscription and workflow and then be able to mass >> subscribe the user. > > I did this, and can confirm that they no longer show up in the list of > pending subscriptions via the mailman shell interface for that list. > > However, if I go to mass subscribe them via the interface, I get: > > HTTP Error 409: b'Subscription request already pending' I don't understand. If there is no entry for that address when you do ``` >>> for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['email'] != 'user(a)example.com': ... continue ... print(data['email']) ... ``` You should not be getting that 'Subscription request already pending' response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: running a script for the mailman-shell (to discard held messages) gives errors about a package argument for relative import

by Mark Sapiro

On 6/15/24 03:10, via Mailman-users wrote: > > Now, obviously, I put these exact lines in a script, so I don't have to type it out every single time, and try to run it using > >> sudo -u list mailman shell -l testlist.our-server.de -r ./mm_discard_held.py > > but that invariably gives me ... > TypeError: the 'package' argument is required to perform a relative import for './mm_discard_held' To run a script named mm_discard_held.py in that way, the script must define a function mm_discard held. The content needs to be something like ``` from mailman.app.moderator import handle_message from mailman.config import config from mailman.interfaces.action import Action from mailman.interfaces.request import IListRequests # The above are needed. These imports are done automatically when # running mailman shell interactively, but not when running a script. def mm_discard_held(mlist) rdb = IListRequests(mlist) for req in rdb.held_requests: if req.request_type == RequestType.held_message: config.db.commit() ``` See `mailman shell --details` > I've tried moving it to the path where the mailman binary lives, as suggested. That is what you should do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Mark Sapiro

On 4/13/20 3:22 AM, Andrew Hodgson wrote: > > I was working round my own backup strategy a few weeks ago as I discussed earlier on this list. One thing I found when the directory structure that Mailman Core uses is that the lists directories do not get re-created when Mailman Core starts if they don't already exist. Is this something that should happen, and when would those directories get created? Every other directory did get re-created. > > In my case I was moving from a Dockerised installation to one using venvs, and as the directories from the Docker installation were empty as there hadn't been any postings for a few days, I didn't transfer those over. I created the list directories myself and everything carried on. These var/lists/<list-id>/ directories hold the digest.mmdf files which are mailboxes containing the messages for the next digest. A list post will be added to the digest.mmdf file which will be created if necessary, but if the var/lists/<list-id>/ directory doesn't exist, the create will fail. Thus, the var/lists/<list-id>/ directories need to exist. Normally, they are created when the list is created so they need to be part of a backup. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Migrating to mailman-web and Ubuntu 22.04

by Andrew Hodgson

Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: >Andrew Hodgson via Mailman-users writes: > > I have instructions for Mailman-web for setting up Uwsgi but I > would prefer to keep Gunicorn working as per the instructions here: > > DOC/Mailman 3 installation experience - Mailman Wiki > (list.org)<https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > > > > Has anyone done this before? >I'm in the process of doing just that now. I'm not following that install exactly, but very closely, so far no problems. In particular, Apache to Gunicorn to Django and mailmanclient to Gunicorn to core are both working fine in light testing (we have a large number number of lists to migrate and a lot of >corporate QA to pass so things are going step-by-step). >Is there anything in particular you're worried about? I'm having trouble getting Gunicorn to see the Mailman-Web installation at mailman_web.wsgi:application. Note the installation documentation I linked to uses mailman-suite which is an older (deprecated?) method of getting the web interface hooked up. I'm trying to migrate to mailman-web so that I can take advantage of changes going forward with a simpler setup. I've potentially resolved to use Uwsgi for this and install another package which makes the installation more in line with this: https://docs.mailman3.org/en/latest/install/virtualenv.html Andrew.

2 years, 11 months

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Bill

Hi, All this is very helpful. Thank you. And it leads me to think about timelines. I'm aware that the freeze for Debian 9 (Stretch) is scheduled for the end of this year, and that we can expect it to be released sometime in mid-2017. (Don't quote me on that though ;) And I'm not sure about Centos, I didn't see a Mailman 3.0 package there or in Fedora. But is there any chance that a Mailman 3.0 or 3.1 package is going to make it into current release cycles? From what I can gather, we're very early to the table here, and nothing's going viral yet. As a Debian user, I certainly get the bit about "selling no wine before its time", so I completely understand long development cycles. But we're in the evaluation/design phase of this project and from the providers point of view it would be helpful to know if they should wait a few months for Mailman 3.0/3.1 or just go ahead now with 2.1.x and upgrade to 3.1 at some point down the road. While their list admins are experienced, they are new to Mailman and the fewer burps the better. Although they may very well take a run at 3.0 now and see how things work out. We just need some sort of timeline to consider. I'm not looking for firm dates of course, best guesstimates will do. Thanks, b.

9 years, 4 months

[MM3-users] Re: So near, and yet so far (Configuring Mailman)

by Jack Lenox

On 2021-01-29 19:52, Peter Chubb wrote: > On 30 January 2021 4:01:02 am LHDT, Jack Lenox via Mailman-users > <mailman-users(a)mailman3.org> wrote: >> Hello all, >> > >> >> This to me appears to be an issue with my DNS settings, but I can't >> work this out either. I have an A record for lists.fiftyshadesof.green >> pointing at my server, and an MX record pointing at that: >> >> lists.fiftyshadesof.green. 0 IN MX 0 >> lists.fiftyshadesof.green. >> lists.fiftyshadesof.green. 0 IN A 193.37.35.191 > > Why is the timeout on the names zero? > > When looking them up they'll always come up as expired and invalid. > > If you have static IP assignments I suggest setting the timeout to > 86400 rather than zero. If you're on a system that changes up address > more frequently, then 300 (five minutes) may be more appropriate. Thank you Pete, that's strange. The TTL is set to 86400 seconds. That might have just been a peculiarity of dig when I ran it. Good news everyone! I've got it working. It turns out my issue was with the mynetwork IP settings in my Postfix config. Things do now appear to be working. My only remaining issue is that the posts aren't appearing in the archive. Hmm.

4 years, 9 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 11/30/22 08:41, Jan Eden via Mailman-users wrote: > > Changing the PATH value to a full path (/opt/mailman/fulltext_index) > and restarting mailman-web generates a different error: Yes, it should be a full path. >> ERROR 2022-11-30 16:38:37,953 1028315 django.request Internal Server Error: /archives/list/testing@lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest >> Traceback (most recent call last): >> File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner >> response = get_response(request) >> File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response >> response = wrapped_callback(request, *callback_args, **callback_kwargs) >> File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner >> return func(request, *args, **kwargs) >> File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 454, in reattach_suggest >> sugg_thread = msg.object.thread >> AttributeError: 'NoneType' object has no attribute 'thread' This says that searching the archive for this list for messages matching the current message subject returns None. It is probably a bug that we don't test for this, but what exactly are you doing? See the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for the only way I've been able to create an error like this. -- 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: Hiding an ML from a site

by Odhiambo Washington

On Tue, Feb 6, 2024 at 2:22 PM Mark <imark(a)posteo.net> wrote: > > > On 2024-02-06 21:34, Odhiambo Washington wrote: > > I host two MLs on the same server/same MM3 instance. > > Under the Django Admin interface, I created two sites. I expected that > > each > > ML will belong to its own site and should not be visible on another > > site. > > On https://mm3-lists.kictanet.or.ke/mm/lists/, you can see the two > > lists. > > How do I stop the "Users" list from showing up on this site ( > > https://mm3-lists.kictanet.or.ke/mm/lists/) since it belongs to its own > > site - https://exim4u.org/mm/lists/ ? > > > In your settings file, add the line: FILTER_VHOST = True > > # Mailman Web configuration file. > # /etc/mailman3/settings.py > ... > #Filter visible Mailing Lists based on the current host being used to > serve. > FILTER_VHOST = True > I had this set to True in settings_local.py, but False in settings.py. So it seems to not make a difference in my setup. -- 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, 8 months

[MM3-users] Re: Strange URL in error message

by Mark Sapiro

On 7/17/24 11:47 PM, waps(a)tantalus.jena.thur.de wrote: > Hi Mark, > thanks for your patience. But now I get a little spinning wheel on the archive site, 3 "Error 500" in the Browser console and /var/log/mailman3/web/mailman-web.log shows repeatedly the error: > > ERROR 2024-07-18 08:34:38,261 1760 django.request Internal Server Error: /mailman3/hyperkitty/list/latex-team(a)latex-project.org/posted-to > Traceback (most recent call last): ...> File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 435, in get > raise self.model.DoesNotExist( > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. > > Since the archive is still quite empty and we have only one mailing lis, it would not be a big loss if it could resettet. But how I can do the, without resettinh the member data? Could it be that the Sqlite interface is not as stable as one the the "real databases"? As a superuser, you can go to /mailman3/hyperkitty/list/latex-team(a)latex-project.org/ and delete the archive. This will not delete the mailing list, and an empty archive will eventually be recreated, and new posts will be archived. Regarding the issue, see https://gitlab.com/mailman/hyperkitty/-/issues/504. Ensure that cron is running the Django hourly, daily, etc. tasks and that qcluster is running. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Archive import fails: "IndexError: list index out of range"

by Stephen J. Turnbull

Dan Caballero writes: > I've got a message that keeps getting re-queued to the > /hyperkitty/spool/ folder. [...] > "During handling of the above exception (expected atom at a start > of dot-atom-text but found > '[1db292f04b54496ab40544b0989a2122-JFBVALKQOJXWILKNK4YVA7CPNZSVMZLUPRCW2YLJNRKGK43UPRCXQ32TNV2HA===(a)microsoft.com]>')" This is arguably a HyperKitty bug. The email package is correctly refusing to parse that as a Message-ID (it's been illegal syntax since RFC 822 if I remember correctly), but something, presumably HyperKitty, should catch the error and do something to sanitize it to message-id syntax. On the other hand, I never heard of a message trigger that exception before a couple months ago, so maybe it's the responsibility of spam filters. I think when I ran into it, just moving it out of the HyperKitty archive queue fixed the queue. The client then put in a filter (it was indeed spam) in the MTA, and I haven't heard from them again. In a later post you say that message came back, but I suspect it isn't the same message, but a new one likely from the same source. I would say filter message-ids containing '[' either into /dev/null or a holding pen. Even Microsoft software knows how to generate syntacticly-valid message IDs, pretty sure that was not an @microsoft.com sender! Steve

1 year, 10 months

[MM3-users] Re: MM3 gateway errors and frequent reboot needs

by Brian Carpenter

On 4/19/20 4:38 PM, Mark Sapiro wrote: > On 4/19/20 1:21 PM, hansen(a)rc.org wrote: >> We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? > > We are not seeing an issue like this on either lists.mailman3.org (this > list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) > > What are you seeing in web server logs? > I concur with Mark. I am not seeing any such behavior on none of my MM3 servers. One server we were having similar problems and that was due to a bunch of bad behaving indexing bots (semrush, ahrefbot) hammering the server. So definitely check your web server log. -- 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, 6 months

Search results for query "dO"