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

[MM3-users] Re: About the path forward [was: ... regarding message acceptance]

by kaos＠tecnologiaconsciente.es

Stephen J. Turnbull wrote: > > Any plans to implement message acceptance based on another list? > > I think that most Mailman 2.1 features are plausible proposals for > Mailman 3. While we don't make decisions based on user voting, we do > care about user requests. If you want to make a formal request, post > a request for enhancement (ie, issue) on our GitLab issue tracker, and > post a link here so other interested people can follow it. I am also quite interested in sibling lists feature for mailman 3 (regular_include_lists in mailman 2). Pawel, did you ever posted a request for enhancement in gitlab, as Stephen suggested? Thanks a lot for your answer!

3 years, 6 months

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

by Mark Sapiro

On 10/14/21 7:51 PM, Shawn Heisey wrote: > I'm having a lot of trouble with trying to set up mailman3 on my mail > server. > > It's on an AWS instance, running Ubuntu 20.04 LTS. All software is > installed from Ubuntu packages. Mailman version is 3.2.2. Please see <https://wiki.list.org/x/12812344>[1] > The problem I am trying to troubleshoot first is how this can be happening: > > Oct 14 11:27:26 2021 (2341) ACCEPT: > <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> > Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on > port 25 > > From the shell, I can "telnet localhost 25" successfully, even as the > "list" user. Apparmor is disabled. The UFW firewall is enabled, which > allows all traffic on the loopback interface. I disabled ipv6 at the > kernel level, but had the same problem with ipv6 enabled, so I don't > think ipv6 is related at all. I do not see any connections in the > postfix log that correspond to the mailman connection error. There's a long thread on this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. Your issue may not be the same, but that one had to do with templates, perhaps created in Postorius, that couldn't be accessed. > From a fresh install of mailman, I created two mailing lists. Once upon > a time I had those lists active on a Debian 6 machine running mailman > 2.1.13 ... I copied the mailing list config from that machine over and > used the "import21" facility to import the configuration into the new > mailman3 install. That worked without error and I can see the lists and > their members with the "mailman" command. I found instructions for > integration with postfix, and added the required three config lines to > the postfix config. > > When I try to send a message to the list, I get what I pasted above in > the mailman log. I think that means the postfix integration is working, > and is forwarding to mailman. Yes, and the message should be archived in whatever archivers are enabled. If the prototype archiver is enabled you should see the message in Mailman's var/archives/prototype/<list-id>/new/ directory and if HyperKitty is enabled, in mailman's database in the hyperkitty_email table. > I'm hoping somebody can give me some pointers, and if more information > is needed for troubleshooting, let me know what is needed. If your web UI isn't working, you probably haven't created any templates in Postorius, but import21 will create templates and if you ran import21 as root, you may have created templates and perhaps other things that can't be accessed by the Mailman user (`list` in your case). All Mailman related commands should be run only by the Mailman user. [1] This FAQ says you should be going to Debian/Ubuntu for support. If you've tried that and are not getting help there, I respectfully submit that you should purge the Debian/Ubuntu package and start over from here <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

3 years, 9 months

[MM3-users] Re: Mailman backend maintenance task

by Stephen J. Turnbull

Eugenio Jordan (external) writes: > The idea we were considering was more or less stopping all of the > components, then starting up only PostGRESQL, and then performing each > one of the mentioned tasks. In that case, your Mailman installation will basically be down (no web presence, no deliveries) for the duration of the database maintenance. > You mention that regardless the connectivity that > Mailman's core processes might have with the database, the emails will > be received by and queued until the connection is back again and they > can be delivered to the distribution lists' members. Could you please > confirm whether this task would be actually delegated to Postfix (or > any MTA integrated with Mailman)? If Mailman core is running, it will accept the mail and store it in its own queue. If not, the MTA will store it in its deferred queue until Mailman comes back up. The big problem with delegating this to the MTA is that after two days the MTA probably won't retry for whole days, but if you do an MTA queue flush, it will probably stop other mail delivery for quite a while, since it will be occupied with processing the Mailman backlog. The way Mailman works is that there is a master process, which manages a suite of runners. Each runner is responsible for a particular stage. The LMTP runner does nothing except accept messages from the MTA, and store each one in a file for the next runner in the chain. Each one does various things, then moves the file into the next runner's queue, until the message ends up in the outgoing queue, and Mailman's outgoing runner then picks it up and sends it to the MTA along with the list of RCPT TO addresses. When the MTA accepts the message, Mailman deletes it from its own queue. This is very much like the way that the MTA itself handles mail -- Mailman doesn't accept responsibility until the message is safe on disk, and it doesn't delete its copy until the outgoing MTA accepts responsibility. Then, at some point in the chain of runners, the current runner will need to access the database, it will fail, and block. Messages will pile up in this runner's incoming queue until the database comes back up, at which point it will continue as if nothing happened. The advantage to having Mailman accept and store the message is that the MTA doesn't have a backlog of its own that it keeps retrying, which can slow other mail, especially once Mailman comes back up, and the MTA gets tied up sending deferred mail to Mailman. Most MTAs can be configured to limit the rate at which they accept mail from individual users, which balances the load better. Mailman, on the other hand, just passes the deliveries to the MTA as fast as it can, which is normally what you want, and the MTA is in a better position to impose rate limits when needed. > If so, this is actually what we need: we could afford delaying > the reception a couple of days, whilst we are sure that no mail > will be lost. Mailman doesn't lose mail, because it operates on the same principle of read, store, acknowledge that MTAs do. Steve

3 years, 11 months

[MM3-users] Re: mailman 3 adding extraneous /var/ to pid path?

by Mark Sapiro

On 09/21/2017 01:29 PM, Andrew Hodder wrote: > > I keep getting around this by creating symlinks to the pid file and then > the stop works, but it's getting silly. It seems like mailman just assumes > CWD + /var/ + master.pid must be the location. Once I realized this, I > found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since > it'd then add /var/master.pid). But that seems a little nonsensical. That is the normal expected behavior if devmode is enabled. Check your configs for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] bounces with empty message-id

by Peter Münster

Hi, It seems, that mailman bounces the bounces, so that the list-owner never sees them: --8<---------------cut here---------------start------------->8--- postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] postfix/cleanup[11841]: 879D6F12E8: message-id=<> postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) postfix/qmgr[10092]: 879D6F12E8: removed --8<---------------cut here---------------end--------------->8--- What could I do please, to get the bounces? I would like to use VERP to identify wrong addresses... TIA for any hints, -- Peter

7 years, 6 months

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by brian＠emwd.com

Hi Kevin, I have been following this thread. You won't be able to use the mailman shell due to this being a shared mailman 3 server. Just let me know what the email address is of the user that has an outstanding pending request and I should be able to clear that out via Mark's instructions. You can do that via our support ticket system. I also wasn't aware of a setting for expiring pending requests. I will wait for Mark's response to look into that further. I can tell you from experiencing that making your subscription policy open will not allow those with pending requests to be added. I just tried that myself. Brian

6 years, 3 months

[MM3-users] New Mailman Core Release

by Mark Sapiro

We are pleased to announce the release of Mailman core 3.3.7. It is published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ The change log is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… - please note the `BREAKING CHANGE` documented there and due to our now using SQLAlchemy >-1.4. Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies (aiosmtpd) not supporting 3.10 yet. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: list of subscribers

by Simon Hanna

>> Displaying the names stored in django probably won't happen. >> Matching the names in django with the members in lists >> would require lots of code > Really? I don't know Python, but wouldn't it be possible (just as an > option) to do something like this: > > user = User.objects.get(email = ...) > if user is found then > print next to email address: user.first_name + user.last_name > Yeah, that way you make quite a lot of database queries. to make it perform better, you'd need to get all user accounts and match them to the subscribers. Since users can have multiple addresses you need to check all their addresses. Making this quite expensive for a very small use case.

7 years, 5 months

[MM3-users] Re: Suspend a list temporarily

by Mark Sapiro

On 8/31/19 7:20 PM, Andrew Bernard wrote: > I need a bit of handholding here. What settings do I have to make to reject with a message, and how to make or modify a template with my message containing the reason for temporary list processing suspension? The template to modify is list:user:notice:rejected. This does not seem to be one that can be customized via Postorius so you would need to make a templates/lists/<list.id>/en/list:user:notice:rejected.txt file in Mailman's var/ directory or set a URL for the template as in <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] apache2 security for mailman3 admin

by Lars Schimmer

Hi, I know it is not the perfect place to ask, but if onyone has a good idea, example, I would be happy. I do run mailman3 with apache ProxyPass in front. I did set: <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> as given as example to set it up. Now I want to limit the mailman3/admin area to a defined IP range. Anyone has a working example to limit only the /admin area to a IP range in Apache2, but everything else as it is now? Thank you, MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

3 years, 7 months

[MM3-users] Re: list footer questions

by Mohsen Masoudfar

Hi, Thanks again for your help. When I check the postorius version, it says 1.1.2-3: [509]# apt list | grep postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] It is on Ubuntu18.04 and has been installed with Ubuntu package Mailman-full. There is no update available yet. So it looks like I cannot use the easy way of modifying the templates. Question: Is there a way to achieve the same by updating the code? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, May 8, 2020 4:44 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: list footer questions [EXTERNAL EMAIL] On 5/8/20 12:52 PM, Mohsen Masoudfar wrote: > Hi, > > This seems to me like basic simple questions, I have tried FAQ and other resources, with not much success. > > I have two questions: > > 1. When I send an email to a list, in gmail and yahoo I see the following text with the links at the end of the email body: > _______________________________________________ > Testlist_dmark1 mailing list - > listname(a)domain.tlb<mailto:testlist_dmark1@newlistserv.aaas.org> > To unsubscribe send an email to listname-leave(a)domain.tlb > > In<mailto:listname-leave@domain.tlb%0b%0bIn> outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? There are a few things going on here. First, the actual footer is _______________________________________________ Testlist_dmark1 mailing list - listname(a)domain.tlb To unsubscribe send an email to listname-leave(a)domain.tlb The <mailto:...> links are added by the Mail client displaying the mail. > In outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? > > I know MS does it own stuff sometime and we have no impact on that, but I was thinking maybe we might change the footer in a way that outlooks sees that as part of email body. Yes, this is an outlook thing, but you do have some control. See the FAQ article at <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.list…> for a more detailed explanation, but the issue is that after any content filtering has been applied, the message is still multipart so Mailman adds the footer as a separate MIME text/plain part at the end of the message. You can avoid this by doing heavy content filtering on the messages. Namely, accept only multipart, text/plain and text/html, collapse alternatives and convert html to plain text. Note that some of this involves updating the list's pass_types which is not exposed in Postorius before 1.3.3 which is not yet released. > 2. How may I change the format and the text in footer? > I was expecting it under list > setting, in postorius, but I could not find it. It's the top level Templates tab in Postorius (just left of Settings). It was added in Postorius 1.2.1. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 2 months

[MM3-users] ANNOUNCE: Mailman 3.1.0 final!

by Barry Warsaw

Hello Mailpeople! On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line! Two years after the original release of Mailman 3.0, this version contains a huge number of improvements across the entire stack. Many bugs have been fixed and new features added in the Core, Postorius (web u/i), and HyperKitty (archiver). Upgrading from Mailman 2.1 should be better too. We are seeing more production sites adopt Mailman 3, and we've been getting great feedback as these have rolled out. Important: mailman-bundler, our previous recommended way of deploying Mailman 3, has been deprecated. Abhilash Raj is putting the finishing touches on Docker images to deploy everything, and he'll have a further announcement in a week or two. Feedback is welcome: https://github.com/maxking/docker-mailman What is GNU Mailman? GNU Mailman is free software for managing electronic mail discussion and e-newsletter lists. Mailman is integrated with the web, making it easy for users to manage their accounts and for list owners to administer their lists. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, and more. Mailman 3 is released under the terms of the GNU General Public License, version 3. The best places to start for all things related to this release: http://docs.mailman3.org/ http://www.list.org/ https://gitlab.com/mailman (Note: due to timezone skew, some of the tarballs may not be available on PyPI until tomorrow.) Happy Mailman Day, -Your friendly neighborhood cabal An overview of what's new in Mailman 3.1 ======================================== Feature parity with Mailman 2.1 ------------------------------- * You should be able to do just about everything that you could do in Mailman 2.1 *except* for topics and sibling/umbrella lists. Core ---- * Added support for Python 3.5 and 3.6 * MySQL is now an officially supported database * Many improvements with importing Mailman 2.1 lists * DMARC mitigations have been added, based on, but different than the same feature in Mailman 2.1 * The REST API requires HTTP/1.1 * A new REST API version (3.1) has been added which changes how UUIDs are interpreted, fixing the problem for some JavaScript libraries * Many new REST resources and methods have been added * Individual mailing lists can augment the system's header matching rules * `mailman create` now creates missing domains by default * `mailman digests` now has `--verbose` and `--dry-run` options * `mailman shell` now supports readline history * `mailman members` can filter members based on their subscription roles * A new template system has been added for all messages originating from inside Mailman. * The Message-ID-Hash header replaces X-Message-ID-Hash * New placeholders have been added for headers and footers * Unsubscriptions can now be confirmed and/or moderated Postorius/HyperKitty -------------------- * General U/I and U/X improvements * Many more features from the Core's have been plumbed through * We've adopted Django social auth logins and dropped Persona (since it's no longer supported upstream). You can now log in via Facebook, Google, GitHub, and GitLab. Backward incompatibilities -------------------------- * Core/REST: Held message resources now have an `original_subject` key that is not RFC 2047 decoded. `subject` is now RFC 2047 decoded. * Core/REST: If you've run pre-release versions from git head, and stored welcome and goodbye templates via REST, the template key names have changed backward incompatibility.

8 years, 2 months

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

by Mark Sapiro

On 8/5/22 10:13, Kimmo L wrote: > Okay. Maybe i should to the same and replace my existing configuration with gunicorn. > Is it complicated to do that change ? I ask because this gunicorn term is quite new for me. You already have gunicorn installed because Mailman core uses it to support the REST interface. For configuration see https://wiki.list.org/DOC/Mailman%203%20installation%20experience. In particular, see the `Recommended Configuration` section items labeled `if using Gunicorn:` for sample gunicorn.conf and Script to start Gunicorn. Also, the `Web Server` and `Running Things` sections. -- 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: Mailman-web showing "An error occurred while processing your request."

by Mark Sapiro

On 2/9/23 07:57, C. Souza wrote: > > Just for curiosity, does anyone know the reasons for this kind of problem > and how to avoid it? Cause: Something in the specific email message. Avoidance: Possibly if we knew what the specific issue was or could see the held messages as displayed by the mailman shell script I provided, we could detect the issue and do something about it. Possibly Postorius could catch this and be more graceful about it, but again we'd probably need a message that triggers this issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Hiding an ML from a site

by Odhiambo Washington

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/ ? -- 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: Auth question

by Barry Warsaw

On Mar 30, 2017, at 12:34 AM, David Krantz wrote: >When starting this as the recipe seems reasonable I find that I have >no reliable source for git links for the parts. Some of the git links >I find are marked with "do not use" so it is a bit hard having >confidence in selecting one of the others. All the Mailman 3 suite subprojects are listed here: https://gitlab.com/mailman Those project links will take you to the active git repositories. The only one you should not use is mailman-bundler. Releasing 3.1 and a better deployment story are top priorities for the Pycon sprints. I wish we'd been able to release 3.1 before Pycon, but it just seems unlikely. Plus we have a fine tradition to uphold. :) -Barry

8 years, 4 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Just checked again and saw: - in the setup it works perfectly in Hyperkitty, that's nice - for the first web host I have 2 mail domains registered, so it also matches (unfortunately) with what you said :-( Anyway, I dceleted one of it, still both lists are shown on either web host, so it's generally not working. If I can do something on this issue, please advise me. Thanks. Am 19.03.21 um 17:21 schrieb Mark Sapiro: > FILTER_VHOST is problematic. It works fairly well for HyperKitty, but > not so well for Postorius. In particular with Postorius it doesn't work > if there is more than one mail host domain with the current web host.

4 years, 4 months

[MM3-users] Re: See list of subscribers

by Mark Sapiro

On 3/27/24 00:38, Tom Yates wrote: > > I have a list, as admin under "Settings" -> "List Identity" -> "Members > List Visibility" I have it set to "Only Mailinglist Members". > > But a random subscriber, who's signed up and authenticated, when she > visits the list page she sees her subscription, but no option to list > the other subscribers. > > Is she looking in the wrong place? Do I need to open up more settings? > Am I just being an idiot? This is https://gitlab.com/mailman/postorius/-/issues/369 fixed in Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/770 -- 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] How to store additional information about lists?

by Andreas Barth

Hi together, I need to add custom attributes to the mailing lists: "responsible department": Free text field who is responsible from an organisational pov (not a person but an entity) Enhance the boolean public to a tri-state: public, restricted audience and private (restricted audience means: some people could subscribe themself - how that works is a different topic but w/o the information this can't be achived) - of course this could also be implemented as a second boolean that e.g. splits "not public" into "restricted audience" and "private" (means: nothing goes wrong for code that doesn't know this difference). Any hints how to do that best? Is it possible to store custom attributes, or should that be stored elsewhere? Andi

4 years, 2 months

[MM3-users] Re: username

by Jörg Schulz

The most recent version of Django-allauth has some nice changes, it's now straightforward to include oidc. Just include SOCIALACCOUNT_EMAIL_AUTHENTICATION=True ## This allows existing users to login MAILMAN_WEB_SOCIAL_AUTH = [ "allauth.socialaccount.providers.openid_connect"] in settings.py and use the Django admin to configure the socialauth. While it is _possible_ to add things like ---- SOCIALACCOUNT_PROVIDERS = { "openid_connect": { "APPS": [ { "provider_id": "mm3", "name": "TheNameThat shows up in the button", "client_id": "configuredID", "secret": "yourOIDCproviderGivesItToYou", "settings": { "server_url": "https://keycloak.wherever.com/realms/yourRealm/.well-known/openid-configura…", "token_auth_method": "client_secret_basic", }, } ] } } ---- I think it's preferable to do that within the Django Admin Gui. Does anybody dare to include this info in the documentation, or are we afraid the next django_allauth breaks things again (this time: Keycloak has been replaced by openid_connect)?

1 year, 9 months

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

by Abhilash Raj

On Thu, Feb 25, 2021, at 6:38 PM, Brian Carpenter wrote: > On 2/25/21 8:28 PM, Abhilash Raj wrote: > > Thanks Brian, this looks quite comprehensive in the details. The only > > thing I am a bit concerned about is granting sudo privileges to the > > Mailman user. It really shouldn't have sudo given that Mailman and > > Django are supposed to run as mailman user. Any compromise of > > the Django application will provide the attacker root on the machine. > > Thanks for pointing that out. I have removed that step. It really wasn't > needed. Great, thanks! > > > Is there a specific reason that you chose to go with an entirely new doc > > Yes. Just from observing the communications on this list, there are > multiple ways to install Mailman 3 which produces installation issues, > database problems, outdated apps, etc. My document produces a VERY > stable installation of Mailman 3 and one that is easy to maintain and > update. It is also very comprehensive covering not just Mailman Suite, > but the configuration of an entire server environment. Personally I > think the choice of Debian, NGINX, Postfix, and PostgreSQL makes for a > long and loving relationship with Mailman 3 but I do understand everyone > has their own environment that they want to work with. My guide > represents a very stable and easily maintained environment for me and > hopefully others. I think it is okay to be pick up a specific configuration and provide a guide to installation keeping that as the target technology. As it happens to be, the official doc uses the same set, Nginx, Postfix and PostgSQL. https://docs.mailman3.org/en/latest/install/virtualenv.html I don't see anything very specific to Debian in the doc except the package names and I think they are similar enough in Debian derivative distros that we can write up that assumption up front in the top. Given that most of the installation is based off on pip, I don't think there is going to be a *lot* of deviation for even RHEL/Fedora based distros when it comes to Mailman itself. Some minute deviations could occur with the behavior of certain commands, like `nano` doesn't exist, but I still expect 95% of the doc to be the same, except obviously the package names. > > > rather than helping to improve the existing one? Several parts of it (at > > least the ones that official guide covers) seems similar to me and is > > duplicate information that at least two people are going to spend time > > writing and maintaining in future. > > Is there an official guide? See that is the problem. I did not know > there was an official guide. Because every time I tried finding > documentation in the past using Google searches, I got fed outdated > information. So for me the guide that I came up with, works great for me > and if no one else uses it, I certainly will. I am not that well versed in SEO, but the official website https://list.org does point to it. Maybe not prominently enough for new users to discover? I'll see if we can make the discovery of docs.mailman3.org better. > > Your guide, by nature has to be minimalistic to accommodate all the > various server environments out there. My is meant to be narrow but > comprehensive. I guess it is fine to be opinionated about choosing the technologies but yet provide pointers to help people using other technologies. Right now, I do that using "Hints" and "Notes" and "See also" banners through out the documentation to point to different pages where they can lookup setup for other technologies. For example, how to setup MySQL if official doc recommends Postgres. > > > Is it something about the contribution process to the official documentation > > that makes it hard for people to contribute? Most of the pages at > > docs.mailman3.org or come from this[1] repo and use Sphinx to build and > > REsT formatting (.rst). > > > > [1]:https://gitlab.com/mailman/mailman-suite-doc > > Well I don't know much about any of the above approach to documentation. > So I would say that is a hindrance. Gitlab has a fairly good experience editing REsT files and you don't necessarily have to do much outside of a Web Browser actually. It lets you preview before saving like wiki.list.org and you can submit it for review and merging into main repo. Would you be more willing to contribute to official documentation if we documented the Gitlab contribution process better? > > I am just trying to understand how can we lower the barrier for community > > members to help contribute to existing docs instead of them having to create > > new ones. Specifically around installation, since that tends to get stale often > > when depedent packages change or a new dependency is added that > > breaks the installation. > > I had to update my guide twice due to recent changes made to the > installation process such as the addition of the Dart Sass section and > the problem with the cryptography module when installing Hyperkitty. > While my guide covers these new hurdles to a new installation, I don't > think yours says anything about them. The Dart Sass section came from > Mark's comments on this list. Because we haven't yet gotten to updating those in the official docs, unfortunately. And there are more things missing like Fulltext search (Xapian recommended) and more of the Email setup like SPF and DKIM. Very much aligned with your plans, which is why I suggested contributing updates to docs.mailman3.org instead :) -- thanks, Abhilash Raj (maxking)

4 years, 5 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 13:34 -0800, Mark Sapiro wrote: > On 12/25/21 12:42 PM, William Oliver wrote: > > > > Is there a "make-the-freaking-virtual- map-database" command in > > mailman3, or is this postfix thing? Should I just touch the thing > > and > > create an empty file? I'm a little scared to... The error message > > makes me think that it should be populated with something... > > > Did you add an Alias Domain (different from the Mail Host domain) to > the > entry for your domain? This is what triggers the creation of > postfix_vmap. > Well, I hope youi had/have/will have a great holiday. I just finished our dinner and I am now amusing myself by pretending to enjoy the Hallmark movies my wife is watching and debugging my mailman3 installation when she's not looking. It was either "The twelve cats of Christmas" or "Die Hard." I put my foot down and said we were watching Die Hard. So of course we are watching a movie about 12 kittens in a fire truck. In any case, I added a line for "virtual_alias_domains" in my main.cf for postfix. But it doesn't do anything, apparently, except generate another error line (see the syslog output below). So, just for a lark, I created an empty /opt/mailman/mm/var/data/postfix_vmap file and ran postmap on it to create a postfix_vmap.db file. Now, it no longer complains about there not being a postfix_vmap.db file. Instead it complains about it being empty. Here's what my mailmanweb.log has to say: smtplib.SMTPRecipientsRefused: {'redacted(a)libertyfp.org': (550, b'5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table')} I redacted the name because this is supposed to be the admin account -- and it fails on login. So, here's syslog: Dec 25 19:08:49 libertyfp postfix/smtpd[44664]: connect from localhost[::1] Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/smtpd[44664]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<redacted2(a)libertyfp.org> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: connect from localhost[::1] Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<root(a)localhost.local> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: disconnect from localhost[::1] ehlo=1 auth=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 where "redacted2" is the name in settings.py for EMAIL_HOST_USER and DEFAULT_FROM_EMAIL and "redacted" is the address for "Mailman Suite Admin" I don't know where "root(a)localhost.local" comes from. OK, it didn't work when I just had virtual_mailbox_domains defined, and it didn't work when I had both defined, so I commented out virtual_mailbox_domains and just left virtual_alias_domains. That didn't help, either, though it got rid of the warnings in syslog: Dec 25 19:43:33 libertyfp postfix/smtpd[55192]: connect from localhost[::1] Dec 25 19:43:33 libertyfp postfix/smtpd[55192]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<redacted2(a)libertyfp.org> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: connect from localhost[::1] Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<root(a)localhost.local> to=<reacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: disconnect from localhost[::1] ehlo=1 auth=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 Here's my postfix configuration: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases always_add_missing_headers = yes command_directory = /usr/sbin compatibility_level = 2 daemon_directory = /usr/lib/postfix/sbin data_directory = /var/lib/postfix debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 default_destination_concurrency_limit = 15 default_destination_recipient_limit = 30 header_checks = regexp:/etc/postfix/header_checks home_mailbox = Maildir/ inet_interfaces = all inet_protocols = all local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp mail_owner = postfix mailq_path = /usr/bin/mailq mydomain = libertyfp.org myhostname = mail.libertyfp.org mynetworks = 127.0.0.0/8 10.0.0.0/24 mynetworks_style = host myorigin = $mydomain newaliases_path = /usr/bin/newaliases owner_request_special = no relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains sendmail_path = /usr/sbin/postfix smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_banner = $myhostname ESMTP smtpd_recipient_restrictions = permit_mynetworks, permit_auth_destination, permit_sasl_authenticated, reject smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_cert_file = /etc/letsencrypt/live/libertyfp.org/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/libertyfp.org/privkey.pem smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 virtual_alias_domains = libertyfp.org virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap virtual_gid_maps = static:20000 virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 Here's my settings.py: # Mailman Web configuration file. # /etc/mailman3/settings.py from mailman_web.settings.base import * from mailman_web.settings.mailman import * #: Default list of admins who receive the emails from error logging. ADMINS = ( ('Mailman Suite Admin', 'redacted2(a)libertyfp.org'), ) # Postgresql database setup. DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman', 'USER': 'mailman', # TODO: Replace this with the password. 'PASSWORD': 'passwd', 'HOST': 'localhost', 'PORT': '5432', } } # 'collectstatic' command will copy all the static files here. # Alias this location from your webserver to `/static` STATIC_ROOT = '/opt/mailman/web/static' # Make sure that this directory is created or Django will fail on start. LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' #: See https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "www.libertyfp.org", "libertyfp.org", "mail.libertyfp.org", "list.libertyfp.org", "127.0.0.1", "2.56.57.28" # "lists.your-domain.org", # Add here all production domains you have. ] #: Current Django Site being served. This is used to customize the web host #: being used to serve the current website. For more details about Django #: site, see: https://docs.djangoproject.com/en/dev/ref/contrib/sites/ SITE_ID = 1 # Set this to a new secret value. SECRET_KEY = 'passwd' # Set this to match the api_key setting in # /opt/mailman/mm/mailman-hyperkitty.cfg (quoted here, not there). MAILMAN_ARCHIVER_KEY = 'passwd' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), }, } # To be added to Django's settings.py EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = 'redacted(a)libertyfp.org' EMAIL_HOST_PASSWORD = 'passwd' DEFAULT_FROM_EMAIL = 'redacted2(a)libertyfp.org' SITE_ID = 2 Here's my mailman.cfg: /etc/mailman3/mailman.cfg [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: redacted(a)libertyfp.org [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://redacted2:passwd@localhost/mailman [archiver.prototype] enable: yes # For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg # And, create the /opt/mailman/mm/mailman-hyperkitty.cfg file containing # these settings uncommented #[general] #base_url: http://127.0.0.1:8000/archives/ #api_key: Secret_Hyperkitty_API_Key [shell] history_file: $var_dir/history.py [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.libertyfp.org lmtp_port: 8024 smtp_host: mail.libertyfp.org smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no Here's uwsgi.ini # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. #http-socket = 127.0.0.1:8000 http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log And, last but not least here's mailman-hyperkitty.cfg: [general] base_url: http://127.0.0.1:8000/archives/ api_key: passwd

3 years, 7 months

[MM3-users] GDPR - save subscriptions confirmation emails

by contact＠maadix.net

Hi, I am new in the list. I have been looking for this topic in the archives in order to avoid duplicate, but I could not find any thread. According to the new GDPR rules, lists owners need to have a confirmation from subscribers, and this is easy to do with Mailman 3. What I can't figure out is how to save all the confirmation emails received from users. I only see the confirmations commands emails in the logs, Is there another place/way to store them? For GDPR compliance it is important to be able to demonstrate that you received the confirmation, in case you may need it in the future. Bests Maddish -- *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

7 years, 1 month

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

by Mark Sapiro

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

3 years, 8 months

[MM3-users] Importing mbox files into archive defect with lines with From

by andrew.bernard＠gmail.com

A curious problem, but seems to be well defined. I am importing mbox format files with 25 years worth of archives in 250 files from a Listserv list into hyperkitty. All is going swimmingly, except I get lots of partial emails with sender of None put into the current month, with text that has clearly been truncated. As I look at each one, I see that the line in the imported text is immediately after a line starting with 'From'. Clearly, 'From:' is an RCS-82 header, but 'From ' is not, and yet there is much evidence here that this is messing up the import. Is this a known bug? If not, how do I report it?

6 years, 1 month

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 6:19 PM, Mark Sapiro wrote: > > Otherwise, you can do this in mailman shell, e.g. > ``` > $ 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. > > >>> dm = getUtility(IDomainManager) > >>> d = dm.get('example.com') > >>> d.alias_domain = x.example.com > >>> commit() > ``` Ooops. That should be d.alias_domain = 'x.example.com' I.e., quoted -- 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: per domain SITE_ID views?

by Mark Sapiro

On 12/28/21 1:14 PM, David Newman wrote: > Using FILTER_VHOST, I have two domains set up and working with MM3, > Postorius and Hyperkitty. However, because SITE_ID in settings.py points > to one of the domains, that domain name always appears on Postorius and > Hyperkitty pages. ... > How to get the correct domain to appear on that domain's Postorius and > Hyperkitty pages? I don't think the domain is actually displayed on Postorius pages. If I'm wrong, on what Postorius view do you see it? As far as HyperKitty is concerned, please file an issue for this at https://gitlab.com/mailman/hyperkitty/-/issues/new -- 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: mail stuck in "out" queue

by Mark Sapiro

On 9/16/22 14:42, Dan Caballero wrote: > Thanks Mark. We're using an external host(s) for the outgoing MTA. See settings below. I can advise those sysadmins about your recommendations. Your settings seem fine. [mta] smtp_host: smtp.caltech.edu [mta] smtp_port: 25 sets your outgoing MTA, and [mta] verp_delivery_interval: 1 says VERP every message which impacts performance in that each recipient's message is delivered to the MTA in a separate transaction, but this is what I do as it makes bounce processing more reliable. You might find some of the hits from https://wiki.list.org/FrontPage?action=fullsearch&context=180&value=perform… to be useful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: localtime() cannot be applied to a naive datetime

by Mark Sapiro

On 3/1/24 3:09 AM, Freerk Bosscha via Mailman-users wrote: > Since yesterday I get the following error-message when I go to the webinterface: And what in your installation changed since yesterday? > ValueError at /admin/login/ > localtime() cannot be applied to a naive datetime > Request Method: GET > Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ > Django Version: 2.2.28 This Django version is quite old. > ... > mailman info > GNU Mailman 3.3.3 (Tom Sawyer) and so is this Mailman version. Do you have USE_TZ = True and a setting for TIME_ZONE in your Django settings? -- 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: Deleting A List

by Mark Sapiro

Mark Sapiro wrote: > update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; > update hyperkitty_mailinglist_owners set mailinglist_id = 2 where > mailinglist_id = 13; > update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where > mailinglist_id = 13; > update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = 13; > delete from hyperkitty_mailinglist where id = 13; > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > 'list.lists.nog.ke' where id = 2; Or instead of that you could just go to the new list(a)lists.nog.ke archive in HyperKitty and delete it and then just do the ``` update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = 'list.lists.nog.ke' where id = 2; ``` -- 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] ARC

by David Krantz

Hi all, Is the documentation correct that ARC should be as simple to configure in mailman 3 as to add the private DKIM key and restarting mailman? (https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign…) I've tried that without finding any effect in my so far limited tests. I have not found anything in logs although I might have missed looking in one. Are there any known limitations? I have previously a working DKIM signature on outgoing mail as well as correctly set up SPF in DNS and SPF-checking on received mail. The verification on incoming mail adds a few headers but I do not think that that should be an issue, neither would the DKIM signing change anything should mailman add new headers. I now run Mailman 3.2.3 (La Villa Strangiato) on Python 3.7.4. Cheers // David

5 years, 11 months

[MM3-users] Re: Docker or virtualenv?

by Stephen J. Turnbull

Tim Cutts writes: > Has anyone considered whether it’s feasible to turn it into a bunch > of Lambda functions with a serverless database behind it? ... you just did. I'm not sure if "patches welcome" is appropriate for what looks to me to be a pretty radical idea, but someone could give it a try. :-) I don't think anybody in Mailman core has thought about it though. I don't really see the advantage for most sites. Hosts, especially VMs, are cheap, and unless you're running the lists for a major university or the like, lowest tier hosts will do. As for "serverless databases", that depends on whether Django and SQLAlchemy support them. Mailman has a lot of code invested in those ORMs. Steve

2 years, 7 months

[MM3-users] Re: 120 gmail users removed from lists !

by Yvan ♞

I add an SPF entry on my web hosting, domain name: "v=spf1 mx ptr include:_spf.google.com -all" and it seems to fix the problem. Le 24/10/2023 à 12:51, Stephen J. Turnbull a écrit : > Yvan ? writes: > > > Any "handmaid" solution should be great. > > That *was* the handmade solution. The commit IDs are in my message. > You can get the corresponding patches from GitLab. There's a reason > why I wrote that I don't recommend this -- you're asking for a lot of > work. > > If you can't do it yourself, and you're in a hurry, there is a list of > consultants athttps://wiki.list.org/COM/Mailman%20consulting%20services. > > Steve >

1 year, 9 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Odhiambo Washington

On Sat, Oct 28, 2023 at 9:46 PM Mark Sapiro <mark(a)msapiro.net> wrote: > This is definitely an issue with django_allauth 0.58. See > https://github.com/pennersr/django-allauth/issues/3503 and > https://github.com/pennersr/django-allauth/pull/3504 Thank you for following up on the fix. Consequent upon this django-allauth issue and the previous issue with psycopg2, how likely is it that new MM3 installations will suffer the effects? I am asking because I am doing my tests on a relatively vanilla system and just following the official documentation sin any deviations. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

[MM3-users] Re: import21: A string literal cannot contain NUL (0x00) characters.

by Henrik Rasmussen

Stephen J. Turnbull writes: >> It seems that this issue is still unsolved. Is there any estimated >> date for a fix? https://gitlab.com/mailman/hyperkitty/issues/155 . >Why do you think this is a problem that Mailman should solve? >What is your desired treatment of this data? I was originally just asking for help and was asked by Berry Warsaw to submit the issue: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I tried to clean up the files as told by Simon Hannah. When that didn't work, I was simply just reporting that, thinking that there might be a problem somewhere else. I am sorry if I did anything wrong by asking for help. -- Henrik Rasmussen

7 years, 5 months

[MM3-users] Scheduled tasks

by Darren Smith

All, I am looking more through the documentation of the Mailman Suite here: https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf In section 3.2.5 it talks about the scheduled tasks that need to be run to do "specific routine functions" in hyperkitty. I installed through the easy install script found here: https://github.com/iomarmochtar/mailman3_ei/ However, I can't find anything in THAT documentation that talks about these cron jobs, and in fact the Mailman Suite isn't installed through that script. Can someone point me to any other documentation about the tasks that need to be run on a continual basis? Our hyperkitty installation seems to be bogging down more and more, and I am hoping that it will be as simple as just running some jobs that haven't been on our radar. Thoughts? -Darren

7 years, 1 month

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/9/21 10:14 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I have the apache24 and uwsgi working together. I did this way: > > For the apache24 part I decided to use the mod-wsgi (and uswgi binary). > did a > > pip install mod-wsgi > (with "mod_wsgi-express module-config" it shows the conf needed.) > > after that a > > pip install uwsgi mod_wsgi and uwsgi are two different, incompatible ways of doing the same thing. It appears from the rest of your post(s) that you are actually using mod_wsgi and (hopefully) not running uwsgi at all. -- 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: Migration from 2.1 to 3

by Mark Sapiro

On 12/26/19 5:22 AM, brunol(a)agro.uba.ar wrote: > > No errors/tracebacks in mailman.log. This is the output of debug.log configured as shown in my first post: > > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> to: lispruebas(a)mailman3.agro.uba.ar, list: lispruebas, sub: None, dom: mailman3.agro.uba.ar > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> subaddress: None, queue: in > Dec 26 10:02:37 2019 (696) b'250 Ok\r\n' > Dec 26 10:02:37 2019 (696) _handle_client readline: b'QUIT\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) Data: b'QUIT' > Dec 26 10:02:37 2019 (696) b'221 Bye\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) connection lost > Dec 26 10:02:37 2019 (696) Connection lost during _handle_client() > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbbb70> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f83fd0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483e0b8> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d8079438> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f70f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4a60f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981860> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483eda0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e2f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d80792b0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981e10> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e9780> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4d02c50> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbb550> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49cf048> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4983fd0> > > Those "Using agent: <mailman.mta.bulk.BulkDelivery object at " are constantly appearing, is this behavior normal due to the verbosity of the level? What do you mean by constantly appearing? Do you mean endlessly repeating or that they just repeat a number of times equal to the number of expected recipients of the post? On 12/26/19 10:24 AM, brunol(a)agro.uba.ar wrote: > I've also noticed that the messages are stuck in the "message" table (postgresql) and the corresponding files exists under /var/lib/mailman3/messages/ This indicates the held message has not been removed from the held message queue. You previously posted that you saw a log message > Dec 23 12:35:47 2019 (701) held message approved, message-id: CAOwJ5NX=_bUnfb5ZNqVLFeF3EeOP0GMJW7NeeOWZqVmn5ViyBg(a)mail.gmail.com This message comes from mailman.app.moderator.handle_message() (in mailman/app/moderator.py). After logging that message, it requeues it in the 'pipeline' queue for further processing and deletes it from the message table and /var/lib/mailman3/messages/. This indicates that possibly subsequent processing is holding the message again. > Is there any relevant logger i should look on debug too besides the ones i already configured? set [logging.debug] level: debug in mailman.cfg to get more in debug.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Sapiro

On 11/10/20 1:02 PM, Mark Dadgar wrote: > > The downside to this is that you lose automated bounce processing, of course. You don't lose bounce processing. It just becomes a bit less reliable. The VERPed envelope sender says exactly what address the message was sent to. Without this information, Mailman (actually flufl.bounce <https://fluflbounce.readthedocs.io/en/latest/README.html>) has to parse the returned bounce message to determine the bouncing address. There are many MTAs that do not send RFC 1894 compliant DSNs and we have several heuristic recognizers to try to parse these, but they can fail. -- 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] [Django] ERROR (EXTERNAL IP): Service Unavailable

by dancab＠caltech.edu

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. 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? Thanks for your help. ---- Dan Caballero

4 years, 5 months

[MM3-users] EMWD Mailing Lists Down

by Sherry Xie

Hi all, I am an EMWD Mailman 3 customer, and I recently realized my mailing lists are no longer working (the last email that went through was sent on December 25, 2021). Emails I send to the lists do not show up in archives or reach subscribers. It seems like others have had this issue before since ownership of the company was transferred following Brian Carpenter's passing – has anyone been able to get in touch with support or get their issues resolved? I've submitted a support ticket but have no idea if this is being monitored. I also have no way to contact the current management team, as only their names were announced in the November 5, 2021 email from Barbara Carpenter. Any help would be greatly appreciated – thanks in advance! Sherry

3 years, 6 months

[MM3-users] Re: Upgrade Mailmam Core from

by Mark Sapiro

On 9/27/22 05:42, sascha.rissel(a)gmail.com wrote: > For the moment, I ignored this error > error: invalid command 'bdist_wheel' > ---------------------------------------- > ERROR: Failed building wheel for mailman > > and carried on, with creating a configuration file at /etc/mailman3/mailman.cfg for Mailman Core. > I notice that directory /etc/mailman3 has not been creating during mailman setup from with venv. > > Is this correct? > Shall I manually create this directory or persist mailman.cfg at some other location where system user mailman has permissions to? I suggest you remove the venv and start over ensuring you do `sudo su mailman` before creating the venv. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: search this list searches more then just this list

by Mark Sapiro

On 1/26/24 13:55, Mark Sapiro wrote: > > Yes, presumably because no one sets `XAPIAN_LONG_TERM_METHOD=hash` in > the environment. Do you have a reason for this? Actually, it's not an enviroment setting. It's a django setting XAPIAN_LONG_TERM_METHOD = 'hash' but in any case, I don't know why anyone would want that. What it does is rather than truncate a long term in the index, it replaces that term with a sha224 hash of the term, but that raises the question of how/why one would be searching for the hash rather than the term. -- 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: cc'd e-mail addresses rewritten with @invalid.domain

by Williams, Peter B

Hi Mark, Thanks for the help with this! Other list members will also see the e-mail as coming from user(a)invalid.domain<mailto:user@invalid.domain>. I will continue testing the other scenarios and will reply back as soon as possible. Thanks again for the help with this and have a nice day! Peter On Mon, Sep 21, 2020 at 9:00 PM Mark Sapiro <mark(a)msapiro.net> wrote: On 9/21/20 10:49 AM, peterbw(a)gmail.com<mailto:peterbw@gmail.com> wrote: > Hi, > > We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. > > This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: > > To: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; > > "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: > > to: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, Williams(a)invalid.domain, Peter(a)invalid.domain Because apparently Outlook is sending the message with the literal > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; instead of something like > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, "Williams, Peter" <peters_real_address(a)example.com<mailto:peters_real_address@example.com>> Then some MTA in the chain is seeing the unqualified addresses Williams and Peter and appending its own local domain. > This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org<mailto:listserv@lists.test.org>. In this case, where do you see this? i.e., do other list members see it in the message they receive from the list? I don't know why that would be. I'm certain that Mailman is not involved in this and the Williams(a)invalid.domain and Peter(a)invalid.domain addresses are in the Cc: as received by Mailman. > This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org<mailto:listserv@lists.test.org>; it would route properly. Again, I think this is Outlook. What's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> receives directly? What happens if you send mail in this way with To: test_user(a)gmail.com<mailto:test_user@gmail.com> cc: other_user(a)gmail.com<mailto:other_user@gmail.com>; Williams, Peter; Again, what's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> and other_user(a)gmail.com<mailto:other_user@gmail.com> receive? Also, please see <https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv>. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 10 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Ralph Seichter

* Mark Sapiro: > It has nothing to do with the ssl certificate. In retrospect, that possibility seems unlikely indeed. Note to self: Don't write to public mailing lists at 01:43 local time... ;-) > What that means is the lists.example.com domain must first be known to > Django at <https://lists.example.com/admin/sites/site/ Ah, that's what I was missing, thank you. The headers in my test installation are now generated with the correct URLs. Could I suggest extending the documentation regarding web hosts? https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/domains.html briefly mentions "Domains are how Mailman interacts with email host names and web host names", but as far as I can tell that's pretty much it. -Ralph

6 years, 4 months

[MM3-users] Re: Receiving 8bit-clean mail

by Stephen J. Turnbull

On 10/17/19 3:02 PM, Alyssa Ross wrote: > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further quoted-printable / base64 / > etc. encoding. Based on the symptoms, I'm guessing this means the SMTPUTF8 extension. Mailman is not prepared for this as far as I know. That is, Mailman expects that the headers will be ASCII, possibly MIME-encoded. I'm guessing the problem is that either the host MTA or Mailman's LMTP server doesn't handle SMTPUTF8 negotiation correctly, but I do not have time to analyze for some days. Mark Sapiro writes: > It works for me. I created this message Your message doesn't have UTF-8 in the *header* as far as I can see. Steve

5 years, 9 months

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

by Ruth Ivimey-Cook

> IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed >hosts to get the right connectivity, too. >> I'm not clear on what you're saying. An address is a rendezvous point; if you're not listening on the address that others are using, you won't meet. What good does it do to split them up? > I agree with this, we need a setting for which interface for Gunicorn to listen on, and what Mailman Core sends out in the self_link attribute when responding to REST requests. > Exactly! :-) Ruth

5 years, 1 month

[MM3-users] Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by dave＠aasv.org

The concept of a Django user sounds like the big thing I was missing. Thank you; I believe I have resolved the immediate need. I'm thinking, then, that if I want to be able to programmatically create the Django users in parallel with our Mailman users (I don't want to have registration open to the world), I'm going to have to do some coding... either create some sort of Postorius API or perhaps better would be to make a social / OAuth plug-in that will use our existing membership site. (Once I get stuck on that, I'll switch to the developer list.) Thanks again.

3 years, 6 months

[MM3-users] Re: URLs in moderation messages

by Tim Cutts

Thank you - that was the ticket I think. I was using an apache config based on the one I used to have when using the Debian packages of mailman. I’ve just updated the config a bit based on the docs you just pointed me too, and all seems well. Thanks! Tim > On 3 Mar 2023, at 17:21, Mark Sapiro <mark(a)msapiro.net> wrote: > > That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… Apache.

2 years, 4 months

[MM3-users] Re: Thread IDs on messages incrementing per reply?

by Thomas Ward

On 10/18/23 20:25, Mark Sapiro wrote: > On 10/18/23 15:06, Thomas Ward via Mailman-users wrote: >> Is there a way to oerhaps custom-plugin my way through to set this up >> as an integration into Core? And specify the custom handler process >> or such to allow that integration? I see that there are ways to code >> plugins into existence so it may be a custom-processor plugin or such >> for this purpose. > > > The issue is Mailman core would have to keep track of the message-ids > and thread number of all prior posts to know whether the current post > is a reply to some other post or not. > > You would need a new database table or some other mechanism to keep > track of this and then you may need to keep everything forever because > you can't know that there won't be a future post in reply to some very > old post. > I think this is doable in our (read: Employer) use case, but without needing to modify Mailman Core much beyond a custom plugin and some fussing around. This is a side effect of a custom implementation of "Tagging" data by thread ID in a separate data / intel tagging system that reads from received emails in a custom intel processing mailbox. That has zero care as to how Mailman or Hyperkitty index items, and actually is pretty trivially implemented with `PREFIX` format being [ListName-NNNNNNN]: 1. If subject does not match `PREFIX` format: * Get next thread number from DB (In postgres, this is a serial matched to {list_id}_thread we call with nextval()) * Add subject prefix as [ListName-{ZeroPaddedThreadNumFromDB}] 2. If subject matches `PREFIX` form: * Do nothing As for how HyperKitty handles this, it replies entirely on RFC 5322 fields (see section 3.6.4 in that RFC) for identifying reply to, etc. to identify replies to things, which in turn it seems is fully capable of handling that. We simply need the message to be sent *with* a thread ID that members can hit reply to and keep the prefix in the subject line. We don't care how that's done in the Hyperkitty side of things, we only care about it being sent in the subject line. I noticed that Mailman3 has the capacity for external / custom plugins, and with some work I believe I can achieve this with a customized pipeline with a custom handler of `thread-prefix` instead of `subject-prefix`, otherwise calling the other handlers done by the traditional system, and just handle prefix differently in the thread-prefix handler in the custom pipeline. I'm following this attempt currently, but will keep it internal to employer. It'll also be kept internal to our use-case because it isn't easily exportable to other Mailman3 implementations. But yes, you're right it needs additional DB table to map list_id <--> thread_id and then would need some kind of "Subject prefix uses thread IDs instead of Post IDs config option", or only handle based on a custom pipeline. I"m going to deep dive into this on my end and see if I can come up with a solution that relies direct on the DB calls. Which hopefully should be safe to do, but we'll see in testing. Thomas

1 year, 9 months

[MM3-users] Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 17:07 schrieb Sebastian Hagedorn: > Am 27.08.20 um 16:41 schrieb Brian Carpenter: >> On 8/27/20 10:33 AM, Sebastian Hagedorn wrote: >>> In case it matters, I'm trying to moderate the list using the "root" >>> account. Discarding works, but when I try to either accept or reject a >>> message, there is a timeout. >> Is there an error message displaying in Postorius or do you receive an >> Apache timeout error? > Neither. The browser times out. > ... and when I realized that, I tried a different browser, where it works. Sorry for the noise. FWIW, Firefox isn't working (at least right now), Safari is.

4 years, 11 months

[MM3-users] Re: Importing archive from mm21

by Mark Sapiro

On 11/28/23 11:32, Lars Bjørndal wrote: > On Mon, Nov 27, 2023 at 01:26:03PM -0800, Mark Sapiro wrote: >> >> The messages are there. I went to >> https://hodr.no/archives/list/annonsering@hodr.no/ and only saw messages >> from 2023, but then I went to >> https://hodr.no/archives/list/annonsering@hodr.no/latest?count=200&page=2 >> and started seeing all the messages even at >> https://hodr.no/archives/list/annonsering@hodr.no/. >> >> What do you see now? > > Now, all messages are visible. I suspect this was fixed by one of the daily hyperkitty jobs which just coincidentally ran when I was looking. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 26, 2017 9:39:06 PM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > >> >> But in my testing, I replied to a subscription confirmation message >and received back an undeliverable looping email error message from >postfix. Any clues there you can offer? I can post to the list from any >email added via the admin console. The test subscriber address was >local to my server. From an outside address, same error. > > >This usually means that postfic is trying to deliver to an address and >the message already has a Delivered-To: header with that address. > >What are the headers of the "looping" message in the report? What are >the Postfix log messages related to that message? > > >> Once I registered the new email domain, I reverted my postfix config >back to the default suggested by maxking's docker instructions. >> >> https://github.com/maxking/docker-mailman > > >I have essentially no knowledge of the docker container images, so I >can't be much help with issues specific to them. Return-Path: <MAILER-DAEMON> Delivered-To: turtl(a)deviltracks.net Received: by mail.garden-life.org (Postfix) id 39F6C2055; Thu, 26 Oct 2017 21:02:17 -0400 (EDT) Date: Thu, 26 Oct 2017 21:02:17 -0400 (EDT) From: MAILER-DAEMON(a)mail.garden-life.org (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: turtl(a)deviltracks.net Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="2D7231948.1509066137/mail.garden-life.org" Content-Transfer-Encoding: 7bit Message-Id: <20171027010217.39F6C2055(a)mail.garden-life.org> This is a MIME-encapsulated message. --2D7231948.1509066137/mail.garden-life.org Content-Description: Notification Content-Type: text/plain; charset=us-ascii This is the mail system at host mail.garden-life.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>: mail for gjb-online.com loops back to myself --2D7231948.1509066137/mail.garden-life.org Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mail.garden-life.org X-Postfix-Queue-ID: 2D7231948 X-Postfix-Sender: rfc822; turtl(a)deviltracks.net Arrival-Date: Thu, 26 Oct 2017 21:02:17 -0400 (EDT) Final-Recipient: rfc822; test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com Original-Recipient: rfc822;test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com Action: failed Status: 5.4.6 Diagnostic-Code: X-Postfix; mail for gjb-online.com loops back to myself --2D7231948.1509066137/mail.garden-life.org Content-Description: Undelivered Message Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Return-Path: <turtl(a)deviltracks.net> Received: from mail.garden-life.org (localhost [127.0.0.1]) by mail.garden-life.org (Postfix) with ESMTP id 2D7231948 for <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>; Thu, 26 Oct 2017 21:02:17 -0400 (EDT) Authentication-Results: mail.garden-life.org (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=garden-life.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=garden-life.org; h=references:in-reply-to:to:subject:subject:message-id:from :from:x-mailer:content-transfer-encoding:content-type :content-type:date:date:mime-version; s=dkim; t=1509066135; x= 1509930136; bh=k85upIKMt3yA1zcaSrQxE349DcmKTq86MMRdi7hh2yw=; b=X 2phB5a1/LGy0J5YIHZTnbXOeoJ55wkcBrFax3cTvvXAAbfZEBsV3BLZ9Z25GdncT CK7b3FU8He/70UAKZtcjreE1AP/hB89yX63xNSqFu2iULKIYMOhWaE/eWl897VhN NIR1mONlrQxOUf5+o16As9WPdbAiEO/TKNMUpuyk+A= X-Virus-Scanned: amavisd-new at mail.garden-life.org X-Spam-Flag: NO X-Spam-Score: 6.117 X-Spam-Level: ****** X-Spam-Status: No, score=6.117 tagged_above=2 required=6.2 tests=[RCVD_IN_PBL=3.558, RCVD_IN_RP_RNBL=1.284, RCVD_IN_SORBS_DUL=0.001, RDNS_NONE=1.274] autolearn=no autolearn_force=no Received: from mail.garden-life.org ([127.0.0.1]) by mail.garden-life.org (mail.garden-life.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3zCxRxppUkZt for <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>; Thu, 26 Oct 2017 21:02:15 -0400 (EDT) Received: from rainmail.deviltracks.net (keys.fspproductions.biz [IPv6:2600:3c03::f03c:91ff:fe24:1eeb]) by mail.garden-life.org (Postfix) with ESMTPSA id 1116A2F1 for <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>; Thu, 26 Oct 2017 21:02:15 -0400 (EDT) Mime-Version: 1.0 Date: Fri, 27 Oct 2017 01:02:14 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: RainLoop/1.11.3 From: turtl(a)deviltracks.net Message-ID: <4e5829300419cfb7bf13d5a0d9ebebd1(a)deviltracks.net> Subject: Re: confirm b7322edad83ae7ec99cfc5100161c7062d2c7685 To: test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com In-Reply-To: <150906420646.31.12186705534373041145@mailman-core> References: <150906420646.31.12186705534373041145@mailman-core> X-Originating-IP: 108.53.239.102 October 26, 2017 8:30 PM, test123-confirm+b7322edad83ae7ec99cfc5100161c70= 62d2c7685@gjb-online.com=0Awrote:=0A=0A> Email Address Registration Confi= rmation=0A> =0A> Hello, this is the GNU Mailman server at gjb-online.com.= =0A> =0A> We have received a registration request for the email address= =0A> =0A> turtl(a)deviltracks.net=0A> =0A> Before you can start using GNU M= ailman at this site, you must first confirm=0A> that this is your email a= ddress. You can do this by replying to this message,=0A> keeping the Subj= ect header intact.=0A> =0A> If you do not wish to register this email add= ress, simply disregard this=0A> message. If you think you are being malic= iously subscribed to the list, or=0A> have any other questions, you may c= ontact=0A> =0A> test123-owner(a)gjb-online.com --2D7231948.1509066137/mail.garden-life.org-- Logs: mail amavis[1576]: (01576-09) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [2600:3c03::f03c:91ff:fe24:1eeb]:33512 [2600:3c03::f03c:91ff:fe24:1eeb] <turtl(a)deviltracks.net> -> <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>, Queue-ID: 15BD218EE, Message-ID: <09b6ea7c3203e7357e4e996c352223d0(a)deviltracks.net>, mail_id: UgTlYoHupO-Z, Hits: 6.117, size: 1663, queued_as: 928292055, dkim_new=dkim:garden-life.org, 451 ms, Tests: [RCVD_IN_PBL=3.558,RCVD_IN_RP_RNBL=1.284,RCVD_IN_SORBS_DUL=0.001,RDNS_NONE=1.274] Oct 26 21:47:44 mail postfix/smtp-amavis/smtp[19971]: 15BD218EE: to=<test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>, relay=127.0.0.1[127.0.0.1]:10026, delay=0.64, delays=0.18/0/0/0.46, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 928292055) Oct 26 21:47:44 mail postfix/qmgr[1240]: 15BD218EE: removed Oct 26 21:47:44 mail postfix/smtp[20025]: 928292055: to=<test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>, relay=none, delay=0.04, delays=0.01/0.02/0/0, dsn=5.4.6, status=bounced (mail for gjb-online.com loops back to myself) Oct 26 21:47:44 mail postfix/cleanup[19953]: 9E63E18EE: message-id=<20171027014744.9E63E18EE(a)mail.garden-life.org> Oct 26 21:47:44 mail postfix/qmgr[1240]: 9E63E18EE: from=<>, size=5273, nrcpt=1 (queue active) Oct 26 21:47:44 mail postfix/bounce[20027]: 928292055: sender non-delivery notification: 9E63E18EE Oct 26 21:47:44 mail postfix/qmgr[1240]: 928292055: removed Oct 26 21:47:44 mail postfix/pipe[19986]: 9E63E18EE: to=<turtl(a)deviltracks.net>, relay=dovecot, delay=0.03, delays=0/0/0/0.03, dsn=2.0.0, status=sent (delivered via dovecot service) Oct 26 21:47:44 mail postfix/qmgr[1240]: 9E63E18EE: removed [root@mail ~]# -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

7 years, 9 months

[MM3-users] Re: scheduled tasks in docker-based deployments

by Abhilash Raj

On Thu, Oct 26, 2017, at 02:42 PM, Dmitry Makovey wrote: > > I came across the section > http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required > that claims that crontab entries are *required* for normal MM3 > operations, but I do not see anything like that in docker-based > implementation. Should I add similar cron jobs manually to the host box? No, the container takes care of it. uwsgi process running inside the `mailman-web` container handles both cron and django_q processes within the container. See [1] for the configuration. [1]: https://github.com/maxking/docker-mailman/blob/master/web/mailman-web/uwsgi… > -- > Sr System and DevOps Engineer SoM IRT > > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

7 years, 9 months

[MM3-users] Re: Strange error in uwsgi-error.log

by Derek Lambert

Brian, When I was seeing this, new lists weren't showing in HyperKitty. I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from functioning. I had to drop the constraint to get the lists in. None of them have a description now. Was this working for you in the past? If so, did you do any updates recently? Derek Lambert On 2/6/19, 1:50 PM, "brian(a)emwd.com" <brian(a)emwd.com> wrote: Mark Sapiro wrote: > This looks like <https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_mailman_hyp…> Thanks Mark. It doesn't seem to impact the functionality of the mailing list in any way and the other lists are fine and producing no errors. Brian _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mai…

6 years, 5 months

[MM3-users] Re: Sudden increase in "***UNCHECKED***" in email subjects

by Peter Adebahr

On 7/18/20 7:46 PM, Mark Sapiro wrote: > On 7/18/20 9:30 AM, Dave Clements wrote: >> Hi all, >> >> I have just noticed a big jump in the number of emails going out with >> "***UNCHECKED***" added to the subject line. > > > This does not come from Mailman. Some milter or other process in your > MTA or elsewhere in the delivery chain is adding this to the Subject: > Hi Dave, I had experienced the same symptom a while ago. For me, it was amavis doing this. This behaviour could be corrected by adding this line to amavisd.conf: # $undecipherable_subject_tag = '[UNCHECKED] '; # undef disables it $undecipherable_subject_tag = undef; # Hope it helps :) Best regards, Peter

5 years

[MM3-users] Re: mailman3 OWNERS_CAN_ENABLE_PERSONALIZATION option

by Mark Sapiro

On 12/2/20 5:42 PM, Henry S via Mailman-users wrote: > I am trying to change email "To" field to user's email instead of > mailing list's email. e.g. "To: <user(a)gmail.com>" instead of "To: > <mailman-users(a)mailman3.org>" In Postorius set Settings -> Alter Messages -> Personalize to Full. > I looked around old mailman configs they mentioned about adding > > OWNERS_CAN_ENABLE_PERSONALIZATION option in mm_cfg.py > > is this feature still available in mailman3 ? Can I do it via Postorius > or REST API? There is no setting in Mailman 3 to control the ability to set personalization. It is always available. -- 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] hyperkitty url not found

by Eggert Ehmke

I installed mailman3 in a virtualenv following this guide: https://docs.mailman3.org/en/latest/install/virtualenv.html[1] The mailinglists work very good. However, I did not manage to set up hyperkitty archiving. Archiving is enabled in mailman.cfg. I can call the Archive site from my configuration page, but it is empty. In my /opt/mailman/mm/var/logs/mailman.log file I find error messages like: HyperKitty failure on http://localhost/mailman/hyperkitty/api/mailman/archive: The requested URL was not found on this server. Indeed I cannot access that url using curl. Do I have to set up a separate apache vhost? The documentation is not clear about this, or I missed it. My external visible url is https://lists.[2]<tld>_/mailman3/mailman3/lists/_ -------- [1] https://docs.mailman3.org/en/latest/install/virtualenv.html [2] https://lists.ftv-spandau.de/mailman3/mailman3/lists/

3 years, 4 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/22/24 17:06, Mark wrote: > > There was no line POSTORIUS_TEMPLATE_BASE_URL in /etc/mailman3/settings.py So presumably you were getting the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' from mailman-web/settings/mailman.py because of from mailman_web.settings.mailman import * in your settings.py. > Then, as site-owner, creating a new custom Welcome template (again via > the WebUI) I can see it correctly added to the database in > mailman.template.uri > > - > https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… And what happens if you go to that URL in a web browser? Also what do you get when going to https://lists.mydomain.com/mailman3? -- 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: Remove footer link

by Mark Sapiro

On 04/21/2017 02:14 AM, David Terni wrote: > Hi, > I need to remove footer message like "to unsubscribe etc etc" from all > lists. How i can do it or edit text? Assuming this is recent MM 3 with the "new" templating system implemented per commit dbde6231ec897379ed38ed4cd015b8ab20ed5fa1 Author: Barry Warsaw <barry(a)python.org> Date: Sat Jul 16 15:44:07 2016 -0400 New template system. Closes #249 The new template system is introduced for API 3.1. See ``src/mailman/rest/docs/templates.rst`` for details. and using English as an example, you can put a sitewide footer template in var/templates/site/en/list:member:generic:footer.txt. If this file is empty, the footer wont be added. -- 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: Running Mailman3 under supervisord

by Odhiambo Washington

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? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Torge Riedel

Am 03.02.21 um 02:59 schrieb Abhilash Raj: > Mailman Core 3.3.3:https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs… > Postorius 1.3.4https://docs.mailman3.org/projects/postorius/en/latest/news.html > Hyperkitty 1.3.4 :https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Dear MM3 releasers, after successful update to latest versions I realized that Mailman Core change log links are stable (I requested this some time ago and it was changed - thanks for that), but Postorius and Hyperkitty change logs do not have stable header ids. Can this be changed too? It makes it easier for me (and hopefully for others) when communicating changes to the users. At the moment they see the upcoming changes for Postorius first, which always introduces confusion for some of them. Thanks in advance and kind regards Torge

4 years, 2 months

[MM3-users] Re: Include receipant address as a variable

by Mark Sapiro

On 6/3/22 20:23, chucka(a)blackforest-co.com wrote: > I send out a monthly newsletter via MM. To keep traffic smaller the email has a link to the PDF of the newsletter. > I need to somehow include a variable (the To: email) as part of the link. > ie href = thewebsite/nl.pdf?tomjones(a)email.com That way I can tell A) who is reading the NL and B) popup a notice: Your membership dues have been paid through 2023. You can do this with a custom template for list:member:regular:header or list:member:regular:footer. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 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/19/23 05:02, Wikinaut wrote: > > (venv) mailman-web migrate > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.11/site-packages/django/contrib/postgres/search.py", line 1, in <module> > import psycopg2 > File "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line 51, in <module> > from psycopg2._psycopg import ( # noqa > SystemError: initialization of _psycopg raised unreported exception Since you are using MySql and not PostgreSQL, in your venv do ``` pip uninstall psycopg2_binary ``` -- 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: Problem with redirection when entering alias without a / at the end

by Abhilash Raj

> On Mar 19, 2021, at 4:10 PM, Jens Günther <jens.guenther(a)posteo.de> wrote: > > I did have the first setting, yes. > > The second one no, but activated it now, no change. Can you also share your uwsgi configuration? > > Am 20.03.21 um 00:00 schrieb Mark Sapiro: >> I don't use uwsgi so I can't advise on its configuration, but do you have >> USE_X_FORWARDED_HOST = True >> SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') >> in your Django settings? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: I did something stupid. Can i back out of it?

by William Oliver

On Sat, 2022-02-19 at 17:01 -0800, Mark Sapiro wrote: > On 2/19/22 14:06, William Oliver wrote: > > > > So.. as an aside, it was a bit of a hassle to copy and paste all > > the > > usernames from the "Users" list in Postorius to the "Mass > > subscribe." > > The only way I could see to do it was copy and paste them one at a > > time. > > > Postorius Users -> Members view has a CSV Export button. That exports > a > CSV with all the member addresses. It's actually just a flat list as > it > only has one column. > Thanks! billo

3 years, 5 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 2/2/23 21:25, Odhiambo Washington wrote: > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> See >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… >> for mitigation. > > > What is the danger of replacing my settings.py with this one, seeing as it > differs in a number of ways with mine? If your's works, don't do it. The danger is the differences might be significant and break things. Also, that one is for HyperKitty only and doesn't include Postorius settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: spf/dkim/dmarc

by Jeremy Stanley

On 2023-05-17 07:07:53 -0700 (-0700), Christian via Mailman-users wrote: > Thank you for your reply. I'm being driven mad by Gmail rejecting > my SPF record, this while I get SPF record approvals everywhere > else. > > I read that having two SPF records for the same server will > generate errors. Is this true? [...] I'm not an SPF expert (I don't even use it for my domains), but I do know how to query standards documents. IETF RFC 7208 "Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1" states in §3.2: "A domain name MUST NOT have multiple records that would cause an authorization check to select more than one record." https://www.rfc-editor.org/rfc/rfc7208#section-3.2 Hope that helps! -- Jeremy Stanley

2 years, 2 months

[MM3-users] Re: New installation, new issue: mailman3 migrate -- no module CommonMark

by Mark Sapiro

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. How 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 ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Stephen J. Turnbull

Mark Sapiro writes: > If you have content filtering Collapse alternatives = yes, it will become > > multipart/mixed > text/plain <- empty > image/jpeg > > after collapsing alternatives and that will trigger the error. See > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for a patch (not yet tested) that I think will fix this. I don't think that's the best we can do, though. Especially if Convert HTML to plain is also yes, we want to preserve the HTML part and convert it, don't we? I think a better (or additional) strategy would be to check the selected alternative for blank, and if so, drop it and try again for an appropriate type. Steve

6 months

[MM3-users] Re: Turn off social logins?

by Stephen J. Turnbull

Torge Riedel writes: > - there is a way to do this now via settings_local.py, but feels > a little bit risky if default configuration changes on update of > mailman This should not be true. If it is, we need to fix that. Will check. > Maybe there is a possibility for a simple approach via config file: > > EXTRA_LOGINS = no Insufficiently flexible, I think. ENABLED_EXTRA_LOGINS (more likely to be named ENABLED_AUTH_MODULES or similar) is more flexible. > ENABLED_EXTRA_LOGINS = [] Under consideration, it's been suggested in several forms already. Thank you for your suggestions. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 5 months

[MM3-users] Re: HTML email sent to lists migrated from Mailman 2.1

by Mark Sapiro

On 4/15/19 8:03 PM, Stephen J. Turnbull wrote: > > Lynx is not used in stripping. Do you have the HTML-to-text > conversion option on? If so I can imagine that lack of Lynx would > fall back to stripping (but that would be a bug, of course, and we'd > want to fix it). If convert_html_to_plaintext is True and html_to_plain_text_command fails for any of several reasons including the command not existing, the HTML part is left in the message. > How about spamming the "mailman" (ie, administrator's) list? I think > Mailman 3 still has that? Nope. -- 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: MM3 not starting afte an upgrade -addendum

by Mark Sapiro

On 7/27/20 12:38 AM, Gelpi Andrea wrote: > To solve the problem I had to remove VHOST parameter from config file. > I remember that Vhost was mandatory for my configuration when I set it > up two month ago. > So I don't understand why now I had to remove it to have MM3 working. Are you talking about FILTER_VHOST in your Django settings(_local).py or something else. If something else, I don't know what. If FILTER_VHOST, It has nothing to do with Mailman core. There is this issue with Postorius <https://gitlab.com/mailman/postorius/-/issues/394> which is fixed in Postorius 1.3.3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

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

by Stephen J. Turnbull

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

4 years, 2 months

[MM3-users] Re: Upgrading mailman 3 venv installation

by Morris Jones

On 9/29/2021 11:16 AM, Mark Sapiro wrote: > Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. Thank you! It appears that my installation predates the mailman-web package, as I don't have it installed. But if I understand the docs correctly, it serves to take care of the django-admin commands for migration, static files, js/css compression, etc. So I think I don't need to do anything special (like add mailman-web), except a database migration after the upgrades. Cheers, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

3 years, 10 months

[MM3-users] Re: Unable to ban users via mailman-shell

by Mark Sapiro

On 4/13/25 07:53, Mihai Moldovan wrote: > > That might be a bug in mailman 3.3.8, though, and indeed, there is > https://gitlab.com/mailman/mailman/-/issues/1062 which might be partly > relevant. While it is generally a fix for use_ipython: true (which I > don't use), it might have also fixed the banner issue for the > non-ipython case. This was added in Mailman 3.3.1 by https://gitlab.com/mailman/mailman/-/merge_requests/587 The fix for https://gitlab.com/mailman/mailman/-/issues/1062 doesn't affect this if you aren't using ipython. Do you have a setting for `banner` in the `[shell]` section of 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

3 months, 2 weeks

[MM3-users] Re: Best guide for installing from pypi

by Abhilash Raj

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

4 years, 5 months

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

by Abhilash Raj

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

4 years, 4 months

[MM3-users] Re: Mailman shell tutorial

by Mark Sapiro

On 1/15/20 11:03 AM, dancab(a)caltech.edu wrote: > > I'm now trying to do some simple injection testing via command line. But I seem to be missing something. > > I've tried using mailman inject with the filename option to one of the lists I've imported but still no luck. What is the command you are giving? It should be something like mailman inject -f your_file listname.example.com You could also specify `-q in` but that's the default. What does the message in your_file look like? Does it have a complete set of headers including To:, From:, Subject:, Date: and Message-ID:, and is To: the list posting 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, 6 months

[MM3-users] accept mails from several Users, not list members beside members, howto

by Lars Schimmer

Hi I do look out for a method to accept mails from list members and a number of 20-30 Email addresses (not list members) to a mailing list. All others should be denied to post to the list. I can add those as non-members, but AFAIK I cannot define a special rule for them in "message acceptance". Under "message acceptance" the line "non-members" is set to deny, but if I set it to "default procesessing" - will it allow ALL email addresses, or just the group of "non-member" users? Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years

[MM3-users] Gmail bounces as a result to high send rate

by Mohsen Masoudfar

I managed to receive the bounced emails to my mailbox and I can now see the stated reason for th eissue, the bulk of the emails are marked as "expired" due to the following response: "smtp; Message expired: unable to deliver in 840 minutes.< Our system has detected an unusual rate of unsolicited mail. To protect our users from spam, mail has been temporarily rate limited. Please visit https://support.google.com/mail/?p=UnsolicitedRateLimitError to review our Bulk Email Senders Guidelines." The issue is exclusive to Gmail, no other email provider responded with a comparable message. I followed their recommendation, but I am not sure how to reduce the rate on Postfix side. Can I do it per list? or once per server? Thanks.

1 year, 9 months

[MM3-users] Re: Hiding an ML from a site

by Mark

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

1 year, 5 months

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

by Andrew Hodgson

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? Thanks. Andrew.

4 years, 4 months

[MM3-users] Re: Postorius no connection to REST API

by Richard Rosner

postorius, admin, hyperkitty and user-profile work now, accounts doesn't WARNING 2021-08-21 10:52:41,931 3975 django.request Not Found: /accounts WARNING 2021-08-21 10:52:41,931 3975 django.request Not Found: /accounts [pid: 3975|app: 0|req: 26/26] 127.0.0.1 () {56 vars in 1208 bytes} [Sat Aug 21 10:52:41 2021] GET /accounts => generated 5651 bytes in 433 msecs (H\ TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) pid 3975 is /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini PS: now I seem to have done something stupid. I wanted to switch everything from example.com to the real domain. So I added it in admin and got rid of example.com. Seems there was some configuration missing, now nothing is working. How do I get everything back and have it use the right domain?

3 years, 11 months

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

by bob B

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

3 years, 10 months

[MM3-users] Re: installing a new instance of mm3

by Mark Sapiro

On 10/22/21 6:37 AM, Christian Stalberg via Mailman-users wrote: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 As Steve said, it should be. > Brian installed my instance. Now its broken. My lists are down. I'm getting > nowhere with diagnostics and troubleshooting (which was easier with mailman > 2). What's broken? Postorius, Hyperkitty, mail delivery, all of them? Do you find any clues in the logs at /opt/mailman/mm/var/logs/? Particularly mailman.log for core and mailmansuite.log for Postorius and Hyperkitty. We will try to help if we have information to help identify the problem. -- 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: Thread matching query does not exist

by Abhilash Raj

On Sun, Jun 30, 2019, at 6:05 PM, andrew.bernard(a)gmail.com wrote: > I still do not know what causes this, but today I purged all the queued > tasks using the Django admin page, and thankfully the issue seems to > have cleared. This is because of the delete process not clearing up the job queue, which is where this exception comes from. This should actually not be logged at all since they are harmless error and create more confusion than prove to be useful. I'll open a bug report for this. > > Andrew > _______________________________________________ > 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

[MM3-users] Re: Messages attached to probe messages

by Bjoern Franke

Hi, > > What do you think is wrong? Note the log says that the message was > refused during the SMTP connection. Normally if the message is > refused during SMTP, there is no delivery status notification (DSN) > sent to the -bounces address, the message is just returned to sender. > Mailman generates an artificial DSN which the system uses to keep > track of SMTP-time rejections. The message you included looks like > one of those to me. I was wondering about example.com, I thought it would have used the list where the issue appeared or at least SITE_ID or SERVE_FROM_DOMAIN. My impression was (without looking into the logs) that the mails got classified as spam and rejected because the were sent from example.com. Best Regards Bjoern

3 years

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

by Odhiambo Washington

On Mon, Mar 6, 2023 at 7:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/6/23 03:38, Odhiambo Washington wrote: > > Has MM3 been tested with Python3.11? > > Yes, but not with uWSGI which is not part of Mailman per se. > Are there any specific tests that are required to be done with respect to uWSGI and mod_wsgi? I could run some of those in my VM. I have switched from uWSGI to mod_wsgi and I don't have any errors - so far. Web UI running without issues in both cases. I believe I do not need to test anything with Gunicorn as that is what the Developers are using all the time :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: Mailman3 stopped sending out mail

by Mark Sapiro

On 11/22/23 6:39 AM, webmaster(a)orcas.de wrote: > as of now I think the same as here: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Just got it in the logs: "Uncaught runner exception: module 'time' has no attribute 'clock'". That specific issue is from using Mailman Core < 3.3.0 with Python >= 3.8. Note the current release of Mailman Core is 3.3.9. Releases less than 3.3.0 are over 4 years old. > Should we add another try catch because of circumstances like this? This is Python, not Perl or PHP. And we do catch exception and log them as we did in this case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: See list of subscribers

by Tom Yates

On Wed, 27 Mar 2024, Mark Sapiro wrote: > On 3/27/24 00:38, Tom Yates wrote: >> >> But a random subscriber, who's signed up and authenticated, when she >> visits the list page she sees her subscription, but no option to list the >> other subscribers. >> >> Is she looking in the wrong place? Do I need to open up more settings? Am >> I just being an idiot? > > This is https://gitlab.com/mailman/postorius/-/issues/369 fixed in Postorius > 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/770 Thank you enormously! I'd've looked for a bug myself, but I was by no means sure I was looking in the right place for the user list in the first place. -- Tom Yates - https://www.teaparty.net

1 year, 4 months

[MM3-users] Re: Help Setting Up Mailman 3 on an Ubuntu Server

by Jeremy Stanley

On 2024-09-26 12:28:34 -0000 (-0000), smith.ja1ck--- via Mailman-users wrote: [...] > As well, I found these resources when doing research on this; > https://REDACTED_LINK_TO_INNOCUOUS_POST_IN_ARCHIVE > https://REDACTED_OBVIOUS_LINKSPAM > If anyone have any resources, tutorials or personal experiences > please share with me, It would be greatly appreciated!! Wow, that one was pretty sneaky. I've been seeing a lot of similar linkspam attempts on mailing lists I moderate, recreating posts similar to ones found in archives or in some cases replying to very old threads, in an attempt to get past moderators. All seem to come with a whiff of having been composed by a chatbot too. I've resorted to closely inspecting links in every moderated post lately. -- Jeremy Stanley

10 months

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Stephen J. Turnbull

Mihai Moldovan writes: > Providing such wrappers as part of venv or the upstream repository > is hence not possible. We do provide them as Python scripts, which the wheels install in "some reasonable place" such as $VENV/bin. I imagine this works fine if you install to site-packages for the system Python, although most distros now make that very difficult. I imagine that these legacy wrappers continue to exist in Debian- family Mailman only because the maintainer is unable to devote time to modernizing the Debian package. IIRC they don't even provide systemd units, but have systemd autogenerate units from /etc/init.d scripts. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 2 weeks

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

by Frank van den Heuvel

Thank you Brian. This one works: had to respond yes in the end to get the actual indexing done. Kinds regards, Frank Op 26-02-2020 om 00:46 schreef Brian Carpenter: > On 2/25/20 6:26 PM, Frank van den Heuvel wrote: >> What can I do to get the newly imported posts indexed? > > I am not sure if this would be helpful but you can try running: > > /opt/mailman/mm/bin/mailman-post-update > -- Met vriendelijke groet, Frank van den Heuvel ------------------------------------------------------------------------ HeuvelTop ICT Diensten 030 602 22 22www.heuveltop.nl <http://www.heuveltop.nl> ------------------------------------------------------------------------ Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed. ------------------------------------------------------------------------ ------------------------------------------------------------------------ Sympathy is our strongest instinct - Darwin ------------------------------------------------------------------------ Sympathie is ons krachtigste instinct. - Darwin ------------------------------------------------------------------------

5 years, 5 months

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

by gordon＠dickens.com

Hi Mark, I think that I found a hint as to the cause of my problems. I changed the apache2 LogLevel to debug and the following was then generated in /var/log/apache2/ssl_error_log: [Fri Feb 11 15:40:18.325675 2022] [core:debug] [pid 3982011] core.c(5280): (95)Operation not supported: [remote /var/lib/mailman3/web/static/uwsgi.sock:12150] AH00139: apr_socket_opt_set(APR_TCP_NODELAY) Apparently, there appears to be a problem with uwsgi.sock. My uwsgi.ini file has the following: uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock Also, my apache.conf for mailman3 has the followig: ProxyPass /mailman3 unix:/var/lib/mailman3/web/static/uwsgi.sock|uwsgi://localhost So do you see a problem in my configuration files that would cause the Operation Not Supported error with the uwsgi.sock file. Thanks, Gordon

3 years, 5 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Hello, just made a try to install mailman 3 on yunohost unsuccessfully Sad... If some body can help me... Thanks https://paste.yunohost.org/raw/hujesebita Le 07/02/2022 à 15:57, Stephen J. Turnbull a écrit : > Yvan ♞ writes: > > > Just to know if I have a chance, do I have to unistall mailman before > > installing mailman 3 ? > > No. In fact, you can run both at the same time. Not for the same > list, obviously. And it requires a fair amount of planning and careful > attention to your web and MTA configurations. As far as I know there > are no naming conflicts in the default installations, Mailman 2 > installs into directory trees under directories named "mailman", while > Mailman 3 installs under "mailman3".

3 years, 4 months

[MM3-users] Re: Hacking attempts?

by Mark Sapiro

On 7/14/22 12:29 AM, Lists via Mailman-users wrote: > > Is this a problem with our setup? i.e. the “Internal Server Error” bit, or are the hackers just sending bad data that is causing the error? also how do we stop/block this? You have Fedora enabled as one of your social account oAuth providers, but it is may be misconfigured or just broken?. Is it possible to log in via fedora at all? If you don't want/need it, just remove it. I am curently traveling and on my way home and don't have time to provide details of removal, but if you need help, ask and I or someone will respond. -- 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: Is there a simple way to remove the footer without having to add a customized template?

by Odhiambo Washington

On Wed, Jun 14, 2023 at 9:30 PM Mark London <mrl(a)psfc.mit.edu> wrote: > I simply want to have no footer for a mailing list. Can I do that > without having to create a customized template? Thanks. > I hope you are good at RTF-Ming :-) https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… Then again, @Mark Sapiro <mark(a)msapiro.net> will tell you the real gospel, or ask you to submit a patch :-) -- 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, 1 month

[MM3-users] Re: howto reallow a banned email ?

by Mark Sapiro

On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: > > By mistake a user has been banned to post to mailman list. How can I > allow him not only to post but also to become a member of a list ? > > I have not found any info on the web, or I have been unable to search > correctly. Do you have the Postorius web UI in your installation? If so go to the list's Ban List and remove the unwanted entry. Or is this perhaps a Mailman 2 question? If so you'll find the ban_list in the web admin UI at Privacy options... -> Subscription rules. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] problems in setting up mailman3 containers.

by Steven Jones

Hi, Trying to setup the 2 mailman3 containers, they fail to start, config and failure messages are, ======== [root@rhel8-svr-001 mailman]# pwd /opt/mailman [root@rhel8-svr-001 mailman]# !269 more core/mailman-extra.cfg # mailman-extra.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg [mailman] site_owner: steven(a)xx.co.nz SECRET_KEY: testing123 [root@rhel8-svr-001 mailman]# !271 more web/settings_local.py SECRET_KEY: testing123 [root@rhel8-svr-001 mailman]# !272 podman run mailman-core DATABASE_URL is not defined. Using sqlite database... No MTA environment variable found, defaulting to Exim HYPERKITTY_API_KEY not defined, please set this environment variable... exiting... [root@rhel8-svr-001 mailman]# !273 podman run mailman-web SECRET_KEY is not defined. Aborting. [root@rhel8-svr-001 mailman]# ========= Could really do with some examples of these files as well... regards Steven

6 years, 1 month

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/26/20 12:00 AM, joseverde(a)gmail.com wrote: > Okay, so I got the webservice of Mailman3 up and running, but when I go to mailman3/postorius/lists/, I get the following error: > > Something went wrong > Mailman REST API not available. Please start Mailman core. Do your settings in the webservice section of mailman.cfg for things like: admin_pass: restpass admin_user: restadmin hostname: localhost port: 8001 (Defaults shoun) match your Django settings MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' MAILMAN_REST_API_URL = 'http://localhost:8001' Also, is Mailman's `rest` runner running ps -fwwA|grep runner=rest should show 3 processes. The runner and 2 workers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Upgrade to 3.3.2 fails

by Torge Riedel

Am 26.12.20 um 23:00 schrieb Joel Lord: > but now we're up and running Nice to hear, but I fear you could be hit by this issues again, depending on changes in the future on the table. Either when more columns are added or on runtime when rows are added / updated. I've read the following documentation, but I do not clearly understand whether innodb_page_size can be increased later via config or not: https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innod… @Mark: Would it be a good approach to split the table 'mailinglist'? I see some groups of columns like "bounce_*" or "dmarc_*" which could be managed in separate tables. Whereas reaching limits on upgrade is already annoying enough, reaching limits on runtime can be fatal. I guess. Kind regards Torge

4 years, 7 months

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

by Terri Oda

On 2016-12-08 9:45 AM, Florian Fuchs wrote: you have a traceback somewhere? If you're logging in for the first > time, it *might* have to do with allauth trying to verify your email > address by sending you an confirmation email (which probably fails if > you don't have smtp set up on your mac). > > If that's the case, we should probably try to catch this condition and > display a useful error message instead of just letting it break. The email *would* make sense, and would explain why I saw the error more often associated with macs. If that's the case it sounds like an error that should be caught and explained. I'll file a bug and dump the traceback there. Terri

8 years, 7 months

[MM3-users] Resetting users' password for them?

by Duane Raymond

Hi. I have quite a few users who when they reset their password, don't receive their password reset email. It works fine for many, so they are going out. But for those who they don't go out for, I was hoping to get their password reset key/token from the database tables and send it to them...only thing is I can't find it in there! )it may not be there). So what would you suggest for enabling people to reset their password when the system email isn't received: - Is there a way to get the reset token so I can send it manually - if so, where/how do I find it? - Would enabling social login be a work around for this problem? - Anything else you can suggest? Cheers, Duane

4 years, 3 months

[MM3-users] Re: Speed/progress of update_index_one_list?

by Mark Sapiro

On 1/14/22 12:38 AM, Philip Colmer wrote: > I have now switched to Xapian but, in a way, my original questions still > stand. Is there a way of monitoring the progress of > "update_index_one_list"? What can I do to the specification of the server > to make that process go (much) faster? HyperKitty does the indexing by calling the Haystack update_index command. See https://django-haystack.readthedocs.io/en/master/management_commands.html#u… This command has options such as --verbosity and --workers. I think verbosity is set from the option provided to update_index_one_list and if set to 2 will give some progress info. workers could increase parallelism but is unconditionally passed by hyperkitty as 0 -- 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] Active archivers and archiving and thread question.

by bob B

Digging into the mailman3 world, and want to check my logic... We normally don't use archives, so I have "archive policy" set to "Do not archive this list" for our lists. However, the "archives" button is still there on the list info page, and if users go into it, they don't see anything, But they can click "start a new thread" which sends a message to the list, but since archiving is turned off, that message does not show up there. Am I understanding that correctly? if I have "Active archivers" disabled, that hides that area from the users, correct? Any reason why these are separated? why have an active archiver, if archiving is turned off -OR- archives are turned on, but no active archiver?

3 years, 4 months

[MM3-users] Re: mailman shell

by Abhilash Raj

On Wed, Jan 2, 2019, at 10:45 PM, Alan So wrote: > Thanks for the advice. It works. > > Actually I am looking for ways to remove non-members since it seems > that we cannot do so through the mailman client. Any pointer to > related documentation? The closest one seems to be > https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/members.… but it only talk about adding members. You can remove non-members using Mailman Client, it is less documented though. https://mailmanclient.readthedocs.io/en/latest/src/mailmanclient/docs/apire… MailingList.remove_role('nonmember', 'email_address(a)example.com') This will remove the nonmember you want. > _______________________________________________ > 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, 6 months

[MM3-users] Re: Mass subscription in "file submit"

by Abhilash Raj

On Tue, Feb 5, 2019, at 2:57 AM, erlonmz(a)terra.com.br wrote: > We would like add members using "file submit" > > "class ListMassSubscription(forms.Form): > emails = forms.FileField( > label='Select File' > help_text='Select a file' > ) > " > What is your opinion about this change? Why do you prefer a file instead of just copy-pasting the contents? I am not sure about the complexity involved with handling files and how we restrict people from upload non-text files. It is definitely possible, but I am not convinced that it is needed. > _______________________________________________ > 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, 5 months

[MM3-users] How to modify system preferences

by Jack Lenox

Hello everyone, I've been making headway with getting Mailman 3 to run how I like it. However I've hit something of a road-block with system preferences. By that, I'm referring to the default set of preferences set out in the documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… The documentation states that these are only accessible in a read-only format via the REST API, but presumably there is a way of modifying these somewhere? I can't find a way of specifying this in my config and can't find a relevant example in the sample schema.cfg. At this stage, all I want to do is set the default for "receive_own_postings" to False. Can anyone point me in the right direction here? Many thanks! Jack

4 years, 5 months

[MM3-users] Re: remove non members from a list

by Mark Sapiro

On 8/6/21 10:28 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Thanks. Now it's no showing errors (and nothing at all) but apparently > it does nothing. The non mebers of the list (the few that remains: I've > been deleting one at a time from the web) aparently still are there.. > > Knowing the correct procedure will ease me to try tomorrow with a clean > head. It doesn't report anything, and if you don't commit() or exit with control-D, any changes will be rolled back. What does list(m.nonmembers.members) show before doing the unsubscribe() and commit() and then what after? -- 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: Join a Mailman 3 list?

by Stephen J. Turnbull

Hi, Although I'm replying to Thomas, I'm going to address this message to Cathy. Thomas Ward via Mailman-users writes: > You'll have to talk to EMWD to see if your archives will be kept > with the migration. They have a completely custom web interface for > archival. When I talked with Brian several years ago he emphasized that moving to Mailman 3 at EMWD would be seamless. Presumably that would include moving the archives, which is quite straightforward if you're starting from a stock Mailman 2.[1] > EMWD uses their **own custom UI** for management and archiving. > This means that we can't give you any real guidance on EMWD and > such for how it relates to user management, etc. This isn't really a problem though. Either way, the new UI will be new to your administrators, and EMWD has historically had an extremely good reputation for working with administrators on such things.[2] But your *subscribers* are *not* using the web interface. Perhaps that will change, but you aren't worried about that, rather that Mailman 3 will enforce use of a web UI. It won't -- if your users don't personalize their profiles in Mailman 2, there's no need for them to start in Mailman 3. The intermediate case is the moderators, but I bet you are doing little or no moderation, and again, EMWD is probably happy to help their clients with that level of education. Also, you did mention the archives. If users are using the archives, the UI will change (either EMWD or HyperKitty). I would expect that could be an issue. As far as that going, EMWD probably has client- focused lists that use their web UIs that you could subscribe to, or perhaps are already subscribed to! I haven't looked at the mockups of Affinity etc that Brian published in years, but at the time they seemed streamlined compared to Postorius and HyperKitty. Between the fact that the "email-only" day-to-day operation you have with Mailman 2 will continue without a hitch with either stock Mailman 3 web UIs or EMWD web UIs, and Brian's pride in his work, I think that you should run, not walk, to EMWD and ask them the same questions. Of course all of my estimates of what EMWD would or would not be happy to do should be confirmed by asking them! Moving to a different hosting service or setting up your own server would be another matter, but as long as you're continuing to work with EMWD whom you find trustworthy, the sooner you move the better. Steve Footnotes: [1] There were enough differences between the Mailman 2 and 3 web UIs that he wasn't going to force anyone to upgrade. Organizations that depend on using the web UIs for their daily workflow could have their efficiency degraded while people learned the new system. This is especially true for the new EMWD web UIs for configuration and archives. But he was confident that the transition would not cause long interruptions in service or changes in the way you send, receive, and work with mail. [2] Working with even dozens of users is another matter, and I can imagine that EMWD would draw the line there. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month, 4 weeks

[MM3-users] Re: Find a smtp server to send out emails

by Stephen J. Turnbull

Aside from the solutions Roni mentions, if alternative hosts are being considered, when I looked about 4 months ago Google Cloud was providing unrestricted outgoing mail to selected customers. No idea what the selection criteria are though. Roni Tim via Mailman-users writes: > Here are some possible solutions: > > Use a Generic Verified Address: Configure your list to use a > verified email address for sending, while allowing subscribers to > send emails under that address. This might work. On Sendgrid's free tier, that's what I do. All my users are at a single university system, hosted by Outlook365, though, so I can't promise that other systems or user agents don't look at the SMTP envelope From. This doesn't affect the incoming envelope From, of course -- Mailman can still use that to identify the sender if you configure it that way. Also it's mostly for announce lists, so generic traffic is probably untested (or maybe the students don't care if they don't get the messages. But I don't think it would work on AWS/SES, because Mailman already changes the return path to itself so it can handle bounce processing. So if SES is complaining about an unverified address, I guess that must mean the header From address. Have anybody actually tried this, and verified that SES checks header From? ISTR we tested this when we were trying to use SES, and it required the envelope sender to be verified, but not the header From. I don't recall if we tested for an issue with DMARC From alignment, though. (That wouldn't have been a problem because we DMARC-munge and then DKIM sign, so we may not have tested that.) In my experience, SES is a poor platform for hosting Mailman. It can be done, but they maintain their excellent reputation for "clean" mail flows with some of the most severe restrictions in the industry: - they replace Message-ID with one of their own, which clobbers both downstream users' local deduplication and HyperKitty threading (or any archiver that gets mail directly from a Mailman plugin rather than by subscribing to the list: mail-archive.com isn't affected) - they allow only one DKIM-Signature header - they restrict use of other headers (I forget offhand, the two above were most troublesome) - I don't think they provide ARC processing. While Mailman 3 can do it, it's better done at the MTA level (especially if the MTA pays for all the crypto processing, not you!) > SMTP Relay Providers: Services like SMTPmart, Mailgun, SMTPget or > Postmark may allow you to send emails from unverified addresses > through their systems, with proper configuration. The only one of the above we looked at was Mailgun. I don't remember why we preferred Sendgrid, though, so it wasn't a huge difference. > Email Forwarding: Set up a forwarding system to act as a middleman > for unverified senders. If this means translating the address in both directions, one of my clients does this for DMARC reasons, but it's a hairball. Among other things, it seems difficult to automate it in a way that doesn't provide a open relay. We hope it will not be exploitable (it hasn't been exploited yet), but we're not 100% sure it can never be. Steve

6 months, 2 weeks

[MM3-users] Re: Disable "confirmation emails"

by Mark Sapiro

On 09/18/2018 01:46 PM, Hagen Bauer wrote: > > even after a lot of google search I could not find a way to disable the > Confirmation Mails like > .... > The results of your email command are provided below. > > - Original message details: > ....... > > Is there a way to do this? I have users who would be irritated and I > dont want them to recieve this Where are you seeing these? There were changes in this area in Mailman core v. 3.2.0 and I think these now should only be sent in response to mail to the -request address that contains a command other than (un)subscribe or confirm. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: How to change rest APi password

by Mark Sapiro

On 10/25/21 11:05 AM, bob B wrote: > This is probably s stupid question but I have been searching for an answer. > > How do you set a different rest api password? > > The instructions say : > The credentials are set in the [webservice] section of the configuration using the admin_user and admin_pass properties. But what is that referring to? > > I am running docker, so is this in the docker.yaml file (I tried it there it did not work) or in the Django config file or someplace else? It's in mailman.cfg. Where that file is in the docker container, I don't know. -- 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: FYI: Django security releases issued: 4.0.6 and 3.2.14

by Mark Sapiro

On 7/7/22 12:56 AM, Stephen J. Turnbull wrote: > Thanks to Guillermo for the heads-up. > > As far as I can tell, neither of these functions is used in the > Mailman suite itself. That doesn't mean they aren't used in one of > our dependencies, but it does mean that we can't do much about what's > installed on your host. You should upgrade if you are using Django 3 > or 4. (Not sure we support Django 4.) We will keep a watch on this. I just upgraded from Django 3.2.11 to 3.2.14 on mail.python.org and lists.mailman3.org. -- 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] lists.mailman3.org web site.

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Alan So

Mark Sapiro wrote: > I haven't looked at the code to see exactly what's responsible here. I > do note that adding double quotes around a display name is not only > allowed, but is required if the display name contains "specials". So, it looks like that Outlook still consider the part (XYZ) as comment during folding even though it is within the double quotes. It is folded between DEF and (XYZ) quite often in our cases if there are four or more than four email addresses in the Cc header. Since we normally have full name in the format of "Firstname Lastname (Dept)" in our organization, we hit the issue quite easily if users send to a list with more than four addresses in the Cc header.

5 years, 2 months

[MM3-users] Re: Mailman automatic accept notification

by Stephen J. Turnbull

Tambet P via Mailman-users writes: > Yes the domain names are the same for example, they are > > mailman.mydomain.ee, oneofexamplelist(a)lists.mydomain.ee Time for bed but I'll try to take a look tomorrow. > Is it possible to totally disable list bounce messages to be sent at all? The messages you are reporting are not list bounce messages. They are messages from your mail server saying that your list is not working, which for reasons I do not understand are being sent to the list, and oddly enough being successfully delivered there. Once we figure out why that is happening, we can explain how to fix it and it will stop. We also need to figure out why mail to your Mailman list is bouncing in the first place. Regards,

4 years, 8 months

[MM3-users] Re: Postorius upgrade issue

by Joel Lord

So I tried to do this after upgrading, fortunately only from 1 point release back, and I get "ModuleNotFoundError: No module named 'paintstore'" from the collectstatic. Haven't tried to get past that point, and haven't really had the time to chase this down myself. It seems like that's referring to a requirement from several versions back, but this venv was built clean only 2 months ago so it strikes me as odd. On 2/8/2021 6:18 PM, Mark Sapiro wrote: > I neglected to mention `migrate`. All 4 Django management commands, `collectstatic`, > `compress`, `compilemessages` and `migrate` should be run after any upgrade. > _______________________________________________ > 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/ > -- Joel Lord

4 years, 5 months

[MM3-users] Re: How to change rest APi password

by Abhilash Raj

> On Oct 27, 2021, at 11:42 AM, bob B <bader(a)cchmc.org> wrote: > > I just tried to change the password in the docker image in /etc/mailman.cfg, but as suspected that file get regenerated when i restart docker mailman. > > Abhilash Raj, any idea on how to change the RESTAPI password in Docker? You can set the MAILMAN_REST_PASSWORD environment variable in your mailman-core container and it will set the API password. You can do the same with MAILMAN_REST_USER. For a list of supported env vars, please see the docs at https://asynchronous.in/docker-mailman/core/#configuration > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

3 years, 9 months

[MM3-users] Re: How to process emails with Mailman3?

by Mark Sapiro

Mark Sapiro wrote: > > The issue is you are not using nc correctly. > When you do > > $ nc localhost 8024 < /tmp/pbTw1oqmV1rZtHXV707Jcov264hr > > you are telling nc to take commands from the file > /tmp/pbTw1oqmV1rZtHXV707Jcov264hr. You need to give it a command to send > the file. Actually, what I said is not correct. The issue is you are just sending the data rather than engaging in an LMTP dialog. You need to send LMTP commands so you might prepend the message with ``` LHLO mymaillist.org MAIL FROM: <sender(a)example.com> RCPT TO: <all-request(a)mymaillist.org> DATA ``` and append to the message ``` . QUIT ``` -- 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: New Mailman Releases

by Odhiambo Washington

On Wed, Oct 26, 2022 at 10:16 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On 10/26/22 12:32, Odhiambo Washington wrote: > > > > > > On Wed, Oct 26, 2022 at 8:44 AM Abhilash Raj <maxking(a)asynchronous.in > > <mailto:maxking@asynchronous.in>> wrote: > > > > Hi, > > > > I am pleased to announce several new releases for GNU Mailman > project. > > > > 1. Mailman Core 3.3.6 [1] > > 2. Postorius 1.3.7 [2] > > 3. Hyperkitty 1.3.6 [3] > > 4. Mailmanclient 3.3.4 [4] > > 5. Django-mailman3 1.3.8 [5] [snip] > > > Finally, the minimum Python version required is 3.7 although, 3.9 is > > recommended if you are doing a new install for longest support. 3.10 > is > > supported for Django apps, but Mailman Core is missing that due to > one > > of the core dependencies not support 3.10 yet (aiosmtpd). > > > > > > > > Hello @Abhilash Raj <mailto:maxking@asynchronous.in> > > > > Thank you and the whole MM3 team for all the free work you do to make us > > have mailing lists :) > > > > I have a question regarding the Python version. > > I have a very recent installation of MM3, via the Virtual Environment > > method, running smoothly - so far. > > The Python version that got installed is 3.10.6 > > > > wash@lists:~$ sudo su - mailman > > (venv) mailman@lists:~$ which python > > /opt/mailman/mm/venv/bin/python > > (venv) mailman@lists:~$ /opt/mailman/mm/venv/bin/python -V > > Python 3.10.6 > > (venv) mailman@lists:~$ mailma > > mailmail3 mailman > > (venv) mailman@lists:~$ mailman --version > > GNU Mailman 3.3.5 (Tom Sawyer) > > (venv) mailman@lists:~$ > > > > 1. What does the incompatibility with Python-3.10 portend for my setup > > and anyone else with Python-3.10? > > The bug in aiosmtpd is a bit weird and has to do with how the test cases > in aiosmtpd and Python 3.10 changes interact with SSL. For the intents > and purposes of Mailman, we don't use SSL for the communication between > MTA and aiosmtpd, so there _shouldn't_ be any issuer with your setup. > Relief! > Ideally, `pip` shouldn't have allowed you to install aiosmtpd in a > Python venv with 3.10, but that depends on which version of pip you are > using since the newer versions have better support for such management. > I followed the HOWTO by the late BC <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> for my installation. I did not have to choose any specific version of pip. I just used what was in the system at that time, which was based on the Python version on the system. > > 2. Is it possible to downgrade the Python in a Venv down to 3.9 without > > breaking the installation? > > You can keep the current installation running and create a 2nd > installation by simply creating a 2nd venv with 3.9. Something like, > `/opt/mailman/mm/venv-3.9/`. You can install things into that venv and > when you are done and ready to switch, you can update all the paths in > various places to use update 'venv-3.9' instead of 'venv'. > That procedure seems way too much work for someone not so well versed with the PATHs used in MM3. Since I don't remember ever having to install aiosmtpd (not even sure what it is!) I believe I should not worry. 'pip3 list | grep smtpd' yielded nothing in my install. Is that expected? Or aiosmtpd is part of the core? In case you encounter any issues, you can always revert back to older > 'venv' in the paths wherever the are needed and bring back the old > install. Venvs are good for multiple installs so you can switch back and > forth pretty easily. > Talking of moving between VENVs, you did not mention about migrating the lists/list data between then :-) > > > > And finally, is there documentation/procedure to upgrade a VENV install > > in this case? > > You don't want to upgrade venv is what i've heard, you should always > create a new one if you are bumping python versions. > Noted. And only Python versions, right? Like 3.10 to 3.11? > If you are just upgrading packages in the existing venv, then you can > follow: > > https://docs.mailman3.org/en/latest/upgrade-3.2.html Thank you for this. I have a request: Is it possible for someone to update the HOWTO that was done by Brian to include the process of updating MM3? I can see that he created a heading that was supposed to have the procedure. I am assuming it should be a few simple additions - but I am not quite sure (see below): (1) Pre-upgrade First, you need to stop the running Mailman services before the upgrade to make sure that you don’t end up in a bad state. You can stop the three systemd services: $sudo systemctl stop mailman3 $sudo systemctl stop qcluster $sudo systemctl stop gunicorn (2) Then you need to switch to mailman user, activate the virtualenv: $ sudo su mailman $ source /opt/mailman/mm/venv/bin/activate (3) Upgrade package Finally, upgrade your packages: Here, I am a little confused. The official MM3 documentation says the below: *(venv) $ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web* However, thee howto by BC, there was no installation for django-mailman3 and mailman-web. So I am unable to map 1:1 what needs to be done to upgrade to these 5 components of 1. Mailman Core 3.3.6 [1] 2. Postorius 1.3.7 [2] 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5] What should I add to the command line below so that everything is updated? (venv) mailman@lists:~$ pip install -U mailman postorius hyperkitty mailman-hyperkitty Sorry to bother you so much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: 3rd Party Account is not working

by Matthew Alberti

I think each plugin has to be configured separately, such as with an API key from each service. It would be interesting to know if there is a recommended way to disable the third party logins completely. That was what I hoped to do after deciding against configuring each service. - Matt Alberti ⁣Get BlueMail for Android On Feb 16, 2021, 5:34 PM, at 5:34 PM, kwp.klein(a)gmail.com wrote: >I installed Mailman 3 with Postfix. I try to login with the 3rd Party >Account. It is not possible, because I get this error message: > >Server error >An error occurred while processing your request. >_______________________________________________ >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, 5 months

[MM3-users] Re: scheduled tasks in docker-based deployments

by Dmitry Makovey

On 10/26/2017 02:53 PM, Abhilash Raj wrote: > On Thu, Oct 26, 2017, at 02:42 PM, Dmitry Makovey wrote: >> >> I came across the section >> http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required >> that claims that crontab entries are *required* for normal MM3 >> operations, but I do not see anything like that in docker-based >> implementation. Should I add similar cron jobs manually to the host box? > > No, the container takes care of it. uwsgi process running inside the > `mailman-web` container handles both cron and django_q processes within > the container. See [1] for the configuration. > > > [1]: > https://github.com/maxking/docker-mailman/blob/master/web/mailman-web/uwsgi… thanks Abhilash! -- Sr System and DevOps Engineer SoM IRT

7 years, 9 months

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/6/22 4:25 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > In the last part of your suggestions you wrote: > > "I suggest you do > > pip install --upgrade hyperkitty mailman-hyperkitty > > and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0" > > But this is exactly what made me fall in this mess: Sorry, I was confused. I thought the error message you were seeing was changed before HyperKitty 1.3.5 was released, but that isn't correct. The problem is probably in Apache. See the last 2 posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: REST API authorization failed

by Mark Sapiro

On 1/10/22 1:58 AM, Axel Rau wrote: >> >> Anyway, the above is saying that restadmin:??? doesn't match what's configured in Mailman core and reported by `mailman info`. Please check carefully that these are the same in both mailman.cfg admin_pass and settings MAILMAN_REST_API_PASS. > > Yes, again with password disclosed: > - - - ... > (mailman_33) [root@lists5 /usr/local/mailman3]# grep admin var/etc/mailman.cfg > admin_user: restadmin > admin_pass: restpass Does `mailman info` show the same password? > What am I doing wrong? Nothing. > Is something wrong with my installed python packages? The relevant code is at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/rest/wsgiapp.p… Does that match yours? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: MTA authentication and smtpd_sender_login_maps

by Mark Sapiro

On 11/25/22 11:00, Jan Eden via Mailman-users wrote: > > I obviously do not want to add an entry to the map file for each mailing > list created by someone on the server. Is there a way to > programmatically create a sender login map with Mailman? You could modify mailman/src/mailman/mta/postfix.py to create a smtpd_sender_login_maps file with the desired content or you could create a script that creates the file using data in the generated var/data/postfix_lmtp. If the latter, you might be able to create a plugin <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do…> to run the script whenever a list is created or deleted -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: help for new installation.

by Dmitry Makovey

On 12/12/2017 01:49 PM, claudio.jofre(a)yandex.com wrote: > I only have two doubts left until now. > First: > where I find the file docker-compose.yaml, I could not find it anywhere. (Install the docker and docker-compose using yum and using the epel repositories. check out github repo: https://github.com/maxking/docker-mailman > second: > How do I access the mailman configuration files inside the docker? > Is there any way to mount it? as a unit, to make the modifications? this is quite the opposite - you mount directories with config files into your docker containers. Check out docker-compose.yaml in Git repo and follow the docs. You may need to re-adjust yaml file to your liking, but it's a reasonably good start -- Sr System and DevOps Engineer SoM IRT

7 years, 7 months

[MM3-users] Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Mark Sapiro

On 10/29/19 8:21 PM, Franklin Weng wrote: > Yes, it is checked. Have you checked Mailman's logs - Mailman's var/logs/mailman.log in particular? Do messages received from the list have an Archived-At: header? What's in /etc/mailman3/mailman-hyperkitty.cfg? In particular does the [general] setting base_url define a URL that accesses hyperkitty and does the [general] setting api_key match the MAILMAN_ARCHIVER_KEY setting in /etc/mailman3/mailman-web.py, but note that the MAILMAN_ARCHIVER_KEY setting is quotes because it is a Python string assignment and the api_key setting is not quoted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: at the finish line of mailman3 docker, but can't sign in.

by bob B

ok ./manage was the piece I was missing so getting closer :). I set the MAILMAN_ADMIN_EMAIL in the .yaml, but what url do I use to login ? http://mailman.domain.com/postorius/lists/. **This url does not like the email address I used for forget password. or http://mailman.domain.com/admin **** this url has no password reset option I added that environment variable "MAILMAN_ADMIN_EMAIL" after i already upped my containers, But I then ran "docker-compose down" then "docker-compse up -d". Does that reload and setup everything again? or could that be the issue? When I tried to send the test email it said "socket.gaierror: [Errno -2] Name does not resolve" sp maybe my mailman-web container can get dns???

4 years

[MM3-users] Re: I'm seeing a lot of database locked errors

by bryan.kartzman＠yu.edu

Its the same message because the professor sent the message to both class lists (the "To:" line): From: David Shatz <shatz(a)yu.edu> To: 202309-30660@lists.yu.edu;202309-31494@lists.yu.edu I don't mind deleting the message from the archives of both classes if its way to get rid of this problem quickly. I was thinking of deleting the entire archive for each of those two classes if necessary so this would be less destructive. Is this all I have to do to delete the messages? delete from hyperkitty_email where id = 1366; delete from hyperkitty_thread where starting_email_id = 1366; delete from hyperkitty_email where id = 1365; delete from hyperkitty_thread where starting_email_id = 1365; There is nothing else in the database that is dependent on these records?

1 year, 10 months

[MM3-users] Mailman 3 stops delivering to a domain after too many bounces

by Stephen J. Turnbull

Julian Kippels writes: > This was not a problem on Mailman 2, but has become a problem on > Mailman 3. It seems to me that for example Mailman 3 sends mails to > the first 5 existing member addresses from domain A, then > encounters several (20 or so seems to be the threshold) "dead" > member addresses from domain A that generate a bounce and then does > not even attempt to reach the remaining 800 member adresses from > domain A and only sends to members on domain B and domain C. "Seems to you"? Do you have logs and empty MTA queues etc as evidence for this, or just mail not arriving at the subscription addresses? What are the configuration settings for the list, most importantly, are messages personalized? In the default configuration without personalization, I think this is very unlikely to be Mailman's problem. Mailman will send a reasonably large number (specifically, 500) of recipients for the message, and then send the message itself once. In this case, if only a couple dozen recipients of 800 receive the message, it's either the recipient MTA or some interaction between your MTA and theirs, not Mailman. Check the MTA outgoing queue and MTA logs. If the list has enabled personalization, so that the footer (usually) contains subscriber-specific information, then there is only one recipient per message. However, the interaction you describe is unlikely to be due to Mailman's behavior in that case as well, as Mailman tracks bounces by individual address, not by domain. It's not useful to do so, as almost all bounces that reach are address-specific. If there is a problem in connecting to a remote host, that is almost always handled by the MTA and Mailman never finds out about it. Again, check the queue and the logs for the MTA as well as for Mailman. On the other hand, I was talking with the postmaster of a rather large site recently, who was complaining about freemail G. What happens is that with a very large list with many bouncing addresses, the sending MTA builds up a backlog of undelivered messages. The MTA tries to resend them at intervals (or for some MTAs the next time a message goes out to that domain). Of course since it's a mailing list, the same addresses bounce, and now you have *twice as many* undelivered messages waiting to be delivered. Pretty soon you have a very large number of attempts within a very short time (in the case of my postmaster acquaintance, an average of 3/second), and freemail G treats that as a DOS attack and starts refusing or delaying connections. That sounds a lot like what's happening to you. Without the log and configuration information it's not possible to be sure, but your hypothesis isn't very consistent with the way Mailman actually does its work. > Is there a way to globaly ignore bounces and No. That's one of the better ways I can think of to acquire a reputation as a spammer and generally bad actor. > send out mails to all members of a list, no matter what? That is what Mailman does. Only after it has received "enough" bounces for a particular user does it disable delivery to that user only. Mailman does not keep records of bounces per domain. Steve

3 years

[MM3-users] Re: Help on removing moderators

by Mark Sapiro

On 3/4/20 12:30 PM, sean_sullivan(a)rhoworld.com wrote: > Never mind, I was able to figure it out. If anyone else is searching for a similar issue. Here again, using mailmanclient can work, but it is very round about. I.e. you are calling client which makes a REST call via http to core to do what you want when you can talk to core directly. > from urllib.error import HTTPError > > def remove(mlist): > curr_list = mlist.fqdn_listname > my_list = client.get_list(curr_list) > r_addresses = ['test1(a)example.com', 'test2(a)example.com', 'test3(a)example.com'] > for email_addr in r_addresses: > try: > my_list.remove_owner(email_addr) > except HTTPError as err: > print (email_addr,my_list, err) -- 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] Migrating to mailman-web and Ubuntu 22.04

by Stephen J. Turnbull

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? Steve

2 years, 8 months

[MM3-users] Re: Editing "automatic responses" tab i Postorius does not work

by Mark Sapiro

On 5/21/17 12:49 PM, David Krantz wrote: > But this one is already exposed. But I cannot change it anyway as the > tab requires URIs for the different templates to allow saving. I do > not use those URIs as I have configured the defaults as I like them. I > tried once and it failed so I decided to set the defaults instead. I'm sorry for totally missing your point in my prior reply. I now understand. The page should not require entries in those fields. This is now reported at <https://gitlab.com/mailman/postorius/issues/186>, and we will fix it. -- 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: mail host choices when creating a new list

by Abhilash Raj

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

7 years, 9 months

[MM3-users] Re: Manual setup - permissions

by Stephen J. Turnbull

I submitted an issue to mailman-web summarizing this conversation, and suggesting documentation as a short-term approach. https://gitlab.com/mailman/mailman-web/issues/3 Abhilash Raj writes: > On Mon, Sep 23, 2019, at 3:02 AM, Tobias Hachmer via Mailman-users wrote: > > # chown -R nginx:mailman3 /opt/mailman3/web > > > > This works for all. But isn't it a security risk that e.g. manage.py and > > settings.py is read- and writeable by the webserver? > > You just need them to be readable, not writable. You could possibly > use xattrs to do just grant read privs. etc. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

5 years, 10 months

[MM3-users] High Server Load problem

by Brian Carpenter

For about a week now, I am seeing very high server loads and it seems to have something to do with the following process hanging: uwsgi --ini /opt/mailman-web/uwsgi.ini I am using the docker version of Mailman. When this process hangs, the server load just goes sky high and both Postorius and Hyperkitty no longer responds. I don't have very many sites on this server and I am running about 30 lists. I really need some assistance here as this needs to be fixed. I am seeing nothing in the logs that is explaining why this process is hanging and why the server load goes through the roof. Running docker-compose restart mailman-web kills the hanged process and the server load goes down. Postorius and Hyperkitty starts responding again. This seems to happen once a day. Brian

5 years, 9 months

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

by Mark Sapiro

On 7/27/20 6:22 PM, Mark Sapiro wrote: > > To do several lists: > > mailman shell > from mailman.models.mailinglist import MailingList > mlist = MailingList('first.list.id') > mlist.emergency = False > commit() > mlist = MailingList('second.list.id') > mlist.emergency = False > commit() > > And so on for more lists. > Ooops... The above is not correct. The correct import is from mailman.model.mailinglist import MailingList i.e. model, not models and the arguments to MailingList are the list posting address, not the list-id. I.e. mlist = MailingList('list(a)example.com') and not mlist = MailingList('list.example.com') -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/20/20 8:53 PM, Mark Dadgar wrote: > On Oct 20, 2020, at 8:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> Even in mailman 2.1, while a list admin could go to a user's options >> page for the list and change things, the "change globally" check boxes >> only worked for the user, not for the list admin. > > That was by design!? > > As an admin, that was so irritating. Yes, it was by design. Do you really think that list owners should be able to enable or disable mail delivery, set digest format, user's password, etc. for a user's subscription on lists that they don't own? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: The doubled entries issue

by Abhilash Raj

On Sat, 11 Nov 2023, at 10:15 PM, Stephen J. Turnbull wrote: > Lars Bjørndal writes: > > > raise ComponentLookupError(interface, name) > > zope.interface.interfaces.ComponentLookupError: > > (<InterfaceClass mailman.interfaces.listmanager.IListManager>, '') > > That says that "python scriptname.py" need the IListManager interface > but can't find it. You didn't provide enough information to explain > why that might be, so I'm not going to guess. This is mostly because of trying to run script with `python scriptname.py` but since it doesn’t initialize the mailman’s zope system. What you probably want to do is run the script using `mailman shell —run` command, which will ensure that it runs the script after initializing the zope components (and other mailman config and things are initialized too). -- thanks, Abhilash Raj (maxking)

1 year, 8 months

[MM3-users] Re: Mailman appears to send an email to a closed list, from a member who was removed from that list

by Odhiambo Washington

Even without reading your list config, I'm restraining myself from saying something about your PM. What is a MuA supposed to do? To tell you that it's refused to send an email? 😂 -- 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] On Fri, Jul 18, 2025, 21:08 Andy Matthews <andy(a)commadelimited.com> wrote: > My project is doing testing of our mailing lists and came across what > appears to be a bug. I believe it's not but she insists that it is. So > before I do a bunch of research I wanted to post my steps to reproduce and > ask for input. I'm including the full (redacted) mailing list config at the > bottom of this post for reference. > > * I have a closed mailing list, acme-closed(a)foo.com > * That mailing list has multiple subscribers, including user-1. I > confirmed this by shelling into our server and running `mailman members > acme-closed(a)foo.com --role=any` on the OS command line. This showed all > of the subscribers, including user-1. > * I sent an mail FROM user-1 TO acme-closed, and it was received. And by > that I mean I received an email TO acme-closed, FROM user-1. I also > received the same email emails sent to the other subscribers since I use a > catch all address for local testing. > * In our system I closed user-1's account (which removes that user from > the mailing list). I confirmed this by running the `mailman members` > command and noting that user-1 was no longer a subscriber. > * I sent another mail FROM user-1 TO acme-closed, and received two emails. > One showed what appears to be a successful send to the mailing list. It > showed acme-closed as the TO address, and user-1 as the sender. But I also > received a second email TO user-1 FROM acme-closed whose body reads "Your > message to the Acme-closed mailing-list was rejected for the following > reasons: The message is not from a list member. The original message as > received by Mailman is attached." > > So my PM is insistent that the first email is proof that there's a bug. > "No e-mail sent from an e-mail address for a closed account should be sent > to the mailing list." > I on the other hand am arguing that the second email is proof that the > email _wasn't_ actually sent to the list, and was instead a sort of > bounceback to the user, However it's tough to argue with her logic because > I agree the first email seems to have been incorrectly sent. > > Can you help me understand why the first email was sent, and if there's a > way to prove with certainty that Mailman is behaving correctly? > > > ``` > accept_these_nonmembers: [] > acceptablealias: [] > admin_immed_notify: True > admin_notify_mchanges: True > administrators: [5 <Members>] > administrivia: True > advertised: False > allow_list_posts: True > anonymous_list: False > archive_policy: ArchivePolicy.private > archive_rendering_mode: ArchiveRenderingMode.text > autorespond_owner: ResponseAction.none > autorespond_postings: ResponseAction.none > autorespond_requests: ResponseAction.none > autoresponse_grace_period: 90 days, 0:00:00 > autoresponse_owner_text: > autoresponse_postings_text: > autoresponse_request_text: > bounce_info_stale_after: 7 days, 0:00:00 > bounce_matching_headers: > > bounce_notify_owner_on_bounce_increment: False > bounce_notify_owner_on_disable: True > bounce_notify_owner_on_removal: True > bounce_score_threshold: 5 > bounce_you_are_disabled_warnings: 3 > bounce_you_are_disabled_warnings_interval: 7 days, 0:00:00 > bounces_address: acme-closed-bounces(a)foo.com > collapse_alternatives: True > convert_html_to_plaintext: False > created_at: 2025-07-18 17:22:54.921936 > data_path: /var/mailman/lists/acme-closed.(a)foo.com > default_member_action: Action.accept > default_nonmember_action: Action.reject > description: closed > digest_is_default: False > digest_last_sent_at: None > digest_members: [] > digest_send_periodic: True > digest_size_threshold: 30.0 > digest_volume_frequency: DigestFrequency.monthly > digests_enabled: True > discard_these_nonmembers: [] > display_name: Acme-closed > dmarc_addresses: [] > dmarc_mitigate_action: DMARCMitigateAction.munge_from > dmarc_mitigate_unconditionally: False > dmarc_moderation_notice: > dmarc_wrapped_message_text: > domain: <Domain @foo.com> > emergency: False > encode_ascii_prefixes: False > filter_action: FilterAction.discard > filter_content: False > filter_extensions: [] > filter_types: [] > first_strip_reply_to: None > forward_auto_discards: True > forward_unrecognized_bounces_to: UnrecognizedBounceDisposition.discard > fqdn_listname: acme-closed(a)foo.com > gateway_to_mail: False > gateway_to_news: False > hold_these_nonmembers: [] > id: 2 > include_rfc2369_headers: True > info: > join_address: acme-closed-join(a)foo.com > last_digest_recipients: [] > last_post_at: 2025-07-18 17:26:28.155475 > leave_address: acme-closed-leave(a)foo.com > linked_newsgroup: > list_id: acme-closed.(a)foo.com > list_name: acme-closed > mail_host: @foo.com > max_days_to_hold: 0 > max_message_size: 20000 > max_num_recipients: 0 > member_moderation_notice: > member_roster_visibility: RosterVisibility.moderators > members: [6 members] > metadata: MetaData() > moderator_password: None > moderators: [5 Members] > newsgroup_moderation: NewsgroupModeration.none > next_digest_number: 1 > next_request_id: 1 > nntp_prefix_subject_too: True > no_reply_address: noreply(a)foo.com > nonmember_rejection_notice: > nonmembers: [2 Members] > obscure_addresses: True > owner_address: acme-closed-owner(a)foo.com > owner_chain: default-owner-chain > owner_pipeline: default-owner-pipeline > owners: [] > pass_extensions: [] > pass_types: [] > personalize: Personalization.none > post_id: 2 > posting_address: acme-closed(a)foo.com > posting_chain: default-posting-chain > posting_pipeline: default-posting-pipeline > preferred_language: <Language [en] English (USA)> > process_bounces: False > regular_members: [6 Members] > reject_these_nonmembers: [] > reply_goes_to_list: ReplyToMunging.no_munging > reply_to_address: None > request_address: acme-closed-request(a)foo.com > require_explicit_destination: True > respond_to_post_requests: False > scrub_nondigest: False > send_goodbye_message: False > send_welcome_message: False > subject_prefix: [Acme-closed] > subscribe_address: acme-closed-subscribe(a)foo.com > subscribers: 13 Members] > subscription_policy: SubscriptionPolicy.moderate > topics: [] > topics_bodylines_limit: 5 > topics_enabled: False > unsubscribe_address: acme-closed-unsubscribe(a)foo.com > unsubscription_policy: SubscriptionPolicy.confirm > usenet_watermark: None > volume: 1 > ``` > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 weeks

[MM3-users] Re: list of subscribers

by Simon Hanna

On 02/06/2018 09:13 PM, Peter Münster wrote: > On Tue, Feb 06 2018, Simon Hanna wrote: > >>> user = User.objects.get(email = ...) >>> if user is found then >>> print next to email address: user.first_name + user.last_name >>> >> Yeah, that way you make quite a lot of database queries. > Is this a problem? Let's say, only moderators can see such a list. And I > guess, that they won't do it so often, that the server crashes... > > Could you please show me, where I should add these 3 lines, so that I can > patch my local mailman installation? > > TIA, You will need to patch the list_member_view in views/list.py to pass along all relevant information to the template which is templates/postorius/lists/members.html

7 years, 5 months

[MM3-users] Re: Announcing Mailman Suite 3.2 release

by Abhilash Raj

On Wed, Jul 11, 2018, at 2:20 AM, Alexander Klotz wrote: > Am 11.07.18 um 08:50 schrieb Abhilash Raj: > > I am very pleased to announce the release of Mailman Suite 3.2.23 > > Dear Abhilash, > > great! Thanks a lot to you and everyone involved! Is it already possible > to install the latest version? We tried doing so in the docker by > changing the tag of the image from 0.1 to 0.2, but that doesn't seem to > work. That is correct, they haven't been updated yet. > Or are we just a bit too impatient? ;) I will update the images to 0.2 soon, there are a few changes that I have planned for images, I will try to get to them as soon as I can :) -- thanks, Abhilash Raj (maxking)

7 years

[MM3-users] Re: Welcome Message

by Mark Sapiro

On April 16, 2019 7:30:11 PM CDT, brian(a)emwd.com wrote: >Mark Sapiro wrote: >> Can you do bin/mailman shell? >> >> That would be even better. > >bin/mailman shell >-bash: bin/mailman: No such file or directory It's Mailman's bin directory. It's the same bin/mailman that you invoke to start Mailman with 'mailman start'. >Apparently not. Again this is the Docker version. Would love to have >the Docker maintainer help out here. > >> If you're installing via pip you must have Python 3. Your tracebacks >show a Python 3 >> library in /usr/lib/python3.6/ > >/usr/lib/python3.6 >-bash: /usr/lib/python3.6: No such file or directory /usr/bin/python3 or just python3. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

6 years, 3 months

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

by Philip Colmer

I have a Mailman 3 server set up with OpenDKIM and Postfix. Each of the lists has been configured so that the DMARC mitigation is "Replace From: with list address" and DMARC Mitigate unconditionally is selected. Everything seems to be working fine *except* when the system sends a notification email to the list owners of someone subscribing or unsubscribing. *Those* emails do not have the DKIM header added and are getting trapped by anti-spam systems as a result. Any suggestions as to why this might be, please? I cannot see anything in the configuration for OpenDKIM or Postfix that might allow just those messages to go out unsigned. In case it is relevant/important, this system is running: mailman 3.3.5 mailman-hyperkitty 1.2.0 mailman-web 0.0.5 mailmanclient 3.3.3 Thank you. Regards Philip

2 years, 11 months

[MM3-users] Re: Members (and moderators) can't view the list of members.

by Mark Sapiro

On 11/7/24 13:34, mrl(a)psfc.mit.edu wrote: > I installed Mailman 3 almost 2 years ago. I only now noticed that members of a mailing list can't view the list of members. Even moderators can't see the list. Only Owners. The error message is "You do not have permissions to visit this page." > > Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] > Postorius Version 1.3.8 This is https://gitlab.com/mailman/postorius/-/issues/369 fixed by https://gitlab.com/mailman/postorius/-/merge_requests/770 in Postorius 1.3.9 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

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

by Simon Hanna

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.

7 years, 6 months

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stephen J. Turnbull

Stefan Bauer writes: > No matter what i try, mailman still only connects without STARTTLS: Earlier you wrote: > SMTPSenderRefused at /accounts/login/(530, b'5.7.0 Must issue a STARTTLS command first', 'postorius(a)lists.mydomain.tld') > Request Method: POST > Request URL: https://mm3.mydomain.tld/mailman3/accounts/login/ > Django Version: 2.2.12 This looks like Django errors, not Postorius (Mailman). So this is something Django is doing, not Mailman (including Postorius). I'm not sure why Django is sending email (somebody made a password reset request seems likely, but I'm not that familiar with Django authn stuff). Anyway, if it's internal to Django, it would not consult Mailman's configs. This recent StackOverflow seems relevant: https://stackoverflow.com/questions/60025730/530-5-7-0-must-issue-a-starttl… HTH Steve

3 years, 8 months

[MM3-users] Re: templates

by Christian

From bounce.log May 05 07:59:00 2023 (765) Member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 07:59:00 2023 (765) Member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:01:00 2023 (765) Member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 08:01:00 2023 (765) Member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:11:01 2023 (765) Member vortexanthony(a)hotmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 1. May 05 08:13:01 2023 (765) Member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 08:13:01 2023 (765) Member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:15:01 2023 (765) Probe bounce received for member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:01 2023 (765) Disabling delivery for juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:15:02 2023 (765) Probe bounce received for member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:02 2023 (765) Disabling delivery for alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:15:02 2023 (765) Probe bounce received for member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:02 2023 (765) Disabling delivery for baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:17:02 2023 (765) Residual bounce received for member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:17:02 2023 (765) Residual bounce received for member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:17:02 2023 (765) Residual bounce received for member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, May 5, 2023 4:39 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/5/23 15:27, Christian via Mailman-users wrote: > Okay I sent a test message this morning and subscribers are reporting > they did not receive it. The smtp.log shows 'smtp to > degrowcali(a)lists.ccalternatives.org for 25 recips, completed in > 3276.275292634964 seconds' (see below) I alone received it however and > it is listed in the archive. Below is the excerpt from smtp.log. Two > of my 5 lists are exhibiting this behavior, while > 2 other lists are working normally. Please advise. Thank you. That message says Mailman delivered the message for 25 recipients to the outgoing MTA. If only one recipient received it, you first need to check the outgoing MTA's logs to see whether the message was delivered to the recipient's mail servers or not. Those logs should indicate that either the message was delivered to each recipient's first hop mail server or not. If not, there should be a reason why in the logs. If the message was delivered, it could have been rejected by an MTA further down stream in which case a DSN message should be returned, but possibly not for days, or it could have been delivered to the user's spam/bulk/junk/promo/whatever folder or silently discarded. Do your list's do bounce processing? If so, what's in Mailman's bounce.log? -- 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/ XI52IZUTFWKEFTWELYVVG2MHQ53J65DF/ This message sent to csa(a)web-analysts.net

2 years, 2 months

[MM3-users] Re: ham-confirm+3ee85b006eeb5897ca6f53b093cb063672f6a784@example.com

by Mark Sapiro

On 2/17/21 1:27 AM, Jörg Klein wrote: > I want add some subscribers. When the I get this error message: > I have no address ham-request(a)example.com. Do I need for every mailing list more as the mailing list email address? How does your MTA deliver to Mailman? If you are using one of the Postfix or Exim configurations described at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>, things should work, but in any case, for every list you need to deliver all of the following to Mailman: LISTNAME(a)example.com LISTNAME-bounces(a)example.com LISTNAME-confirm(a)example.com LISTNAME-join(a)example.com LISTNAME-leave(a)example.com LISTNAME-owner(a)example.com LISTNAME-request(a)example.com LISTNAME-subscribe(a)example.com LISTNAME-unsubscribe(a)example.com -- 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] How to remove a nonmember from a list

by skenny＠scss.tcd.ie

Hi, I've been banging my head against the proverbial wall for more than a day trying to remove nonmembers from a list (I am a Mailman3 and Python novice so that might account for something, but anyway ...) According to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, it should be possible to do: MailingList.remove_role('nonmember', 'email_address(a)example.com') However I can't get this to work. I think I have manage to track down all the required imports. This is what I see: TypeError: remove_role() missing 1 required positional argument: 'address' More digging in the docs seems to indicate that a third parameter is required - "self". At this point though I am way out of my depth, and would appreciate any guidance. Thanks very much Stephen Kenny

5 years, 3 months

[MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface?

by Abhilash Raj

On Sat, Feb 1, 2020, at 5:27 AM, Shashikanth Komandoor wrote: > Hello Mark, > > Thanks for helping me for moving ahead in my project. > > Troubling you again, I would like to put another request at you. > > As per your suggestion, I am trying to configure my list > configuration through REST API for specially the parameter like > max_days_to_hold as it is not available through interface and I am > following the official links of mailman 3 i.e > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html > > But I am getting "name is not defined" sort of errors as below: > > > > > > *>>> dump_json('http://localhost:9001/3.0/lists/ > <http://localhost:9001/3.0/lists/>','ant(a)example.com/config > <http://ant@example.com/config>',dict(display_name='My > List'),'PATCH')Traceback (most recent call last): File "<stdin>", line 1, > in <module>NameError: name 'dump_json' is not defined>>>* > > Actually I am new to REST API but hope this is the only issue that > is preventing me to go ahead. > > Could you please help me by saying how should I handle this so that > I should be able to configure *max_days_to_hold* of a list or multiple ? > dump_json is basically a Python function which sends the request to the URL you add as the first parameter (GET, if any data isn't specified and uses POST if data is specified or explicitly define the PATCH or method like you have above) and prints the json response. You can easily do the same using curl with the right authorization headers, with something like: $ curl -u restadmin:restpass -X PATCH \ http://localhost:8001/3.1/lists/somelist.example.com/config -d display_name='Patched Name' Note that "restadmin:restpass" is the username password that you have set in your mailman.cfg. If you do want to use Python, you can just use a regular PATCH request using requests or standard library urllib3. Finally, dump_json is documented here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/documentation.htm… > On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: > > > > > > But I could see that parameter value configurable on MM2 GUI > > > interface in General Options but I don't see the same on the MM3 GUI > > > interface. > > > > > > There are many core settings not (yet) exposed in Postorius. > > max_days_to_hold. is one of them. It can be set via `mailman shell` or > > via the REST API > > < > > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re… > > >. > > > > -- > > 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 > _______________________________________________ > 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, 6 months

[MM3-users]Re: Is it possible to grant all users the ability to Create List

by Simon Hanna

On 05/27/2016 04:43 PM, knox(a)sgi.com wrote: > Hello, > > Our company is evaluating mailman3 as an option for company internal list serving. > One of the requirements is that anyone with access to the list server be allowed to create and manage lists. > Is this possible? If so, how? Is there a "create list" role that can be added for all registered users? Currently the only way to do so, would be to grant them django superuser permissions. This would require the use of local accounts. This would allow users to also manage domains (create, modify, delete) I went ahead and created the following feature request. Please add any information that you think is relevant. https://gitlab.com/mailman/postorius/issues/133

9 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I did that but I don't have a maillog for today 07.24.2017 Is there another place to look for? El lun., 24 jul. 2017 a las 16:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 07:41 AM, Rafael Mora wrote: > > Ok, I ran 'mailman aliases', what should I do now? > > > Assuming mail delivery is not working, look in /var/log/maillog for > messages with timestamps around the time that the mail was generated. > Then try to figure out what they are saying. > > -- > 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

[MM3-users] Re: Suspend a list temporarily

by Abhilash Raj

On Sat, Aug 31, 2019, at 1:47 AM, Andrew Bernard wrote: > Is there any way to do this, while keeping other lists running? What is your definition of disabled in this case though? 1. Mail server rejects the messages to it saying this list doesn't exist? 2. Mailman rejects the messages to it saying this list is suspended? While there is direct way to achieve this, you can configure your list to reject emails from everyone and the text to your response which says that this list has been temporarily suspended. There should be templates to configure the text sent when a message is rejected. > _______________________________________________ > 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, 11 months

[MM3-users] Re: Struggling with log rotation in Docker context

by Danil Smirnov

For an answer, please refer to my earlier email in this thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… On Fri, Sep 4, 2020 at 11:49 PM <skenny(a)scss.tcd.ie> wrote: > OK, but inside say the mailman-web container, doesn't mailman still have a > file descriptor open and pointing to the old (now rotated/renamed) log > file? - I don't see how doing the rotation on the Docker host aloneis > going to lead to mailman logging to a new log file. > > Sorry if I'm being a bit dumb here. Any enlightenment welcome. > > Stephen > _______________________________________________ > 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] Re: list footer web customization procedure

by Mark Sapiro

On 12/16/21 10:35 AM, dancab(a)caltech.edu wrote: > Mark, > > I updated mailman.cfg to point at our shared EFS mount. > > cache_dir: /mnt/var-mailman3/cache > > But I'm still getting reports of this issue. Is there somewhere else I need to set that location? If your layout is other than fhs, I would set var_dir: /mnt/var-mailman3/ For fhs layout, I would ensure that at a minimum, /var/lib/mailman, /var/spool/mailman and /var/lock/mailman are all shared. However for your issue with shared cache, you need to wait 7 days for all the old cache entries to expire or do getUtility(ICacheManager).clear() in `mailman shell` to clear the cache. -- 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: Postorius no connection to REST API

by Mark Sapiro

On 8/11/21 4:18 AM, Richard Rosner wrote: > Mark Sapiro wrote: >>> You are in a better position to answer that than am I. >> What does sudo netstat -lntp show? > > A lot. But since most of that isn't relevant here: > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 20241/master > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 14076/python3 > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20241/master > tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 14080/python3 So some python3 process is listening on port 8001 > tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 20241/master > tcp6 0 0 :::80 :::* LISTEN 13882/apache2 > tcp6 0 0 :::465 :::* LISTEN 20241/master > tcp6 0 0 :::25 :::* LISTEN 20241/master > tcp6 0 0 :::443 :::* LISTEN 13882/apache2 > tcp6 0 0 :::587 :::* LISTEN 20241/master > >> What does ps -fwwa|grep rest show? > > root 15055 14843 0 12:58 pts/1 00:00:00 grep rest > > So whatever it's supposed to find, it's not there But whatever is listening on port 8001 is apparently not Mailman's rest server. What does ps -fww 14080 or whatever PID is currently listening on port 8001 show. >>> mailman3-web.service must also run as list. > > I changed that. It didn't like it. OK. Perhaps instead you should have uid: list gid: list in your uwsgi configuration if you don't already. > >>> So, what do you have in your apache config for proxying to uwsgi and >> what's your uwsgi configuration. > > lists-ssl.conf: > <VirtualHost *:443> > ServerAdmin admin(a)domain.de > ServerName lists.domain.de > > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass "/mailman3" "unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost:8001/" I'm not familiar enough with this form of ProxyPass using sockets to understand what the localhost:8001 does in this context, but uwsgi should not be doing anything with port 8001. In a configuration using TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API server listens. uwsgi should receive connects in your case via the unix socket and then pass them to Django via the application in wsgi.py Also, you may want other paths proxied to uwsgi, namely at least some of hyperkitty, postorius, archives, accounts, admin and user-profile. > </IfModule> ... > I guess with uwsgi config you mean the /etc/mailman3/uwsgi.ini file? > [uwsgi] > # Port on which uwsgi will be listening. > uwsgi-socket = /run/mailman3-web/uwsgi.sock > > #Enable threading for python > enable-threads = true > > # Move to the directory wher the django files are. > chdir = /usr/share/mailman3-web > > # Use the wsgi file provided with the django project. > wsgi-file = wsgi.py > > # Setup default number of processes and threads per process. > master = true > process = 2 > threads = 2 > > # Drop privielges and don't run as root. > uid = www-data > gid = www-data These should be 'list', not 'www-data'. That's your permissions issue on settings.py -- 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: MM3 Docker

by Mark Sapiro

On 1/6/19 6:54 AM, Odhiambo Washington wrote: > > If I could run MM3 using the apt-get install method, perhaps that would > have made my life a bit easier, hoping that MM3 can actually be run in > parallel with MM2.1 on the same host. Is anyone doing that already?? Yes. I am on two production and one development machines. See, e.g. <https://mail.python.org/mailman/listinfo/> and <https://mail.python.org/mailman3/> One caveat here is I install both Mailman 2.1 and Mailman 3 from source on all these machines. I don't know for example if the Debian/Ubuntu packages play well together. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> for more on how I install MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

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

by Stephen J. Turnbull

Kimmo L writes: > Thanks to this i found the cause of concern - my mailman.cfg had > "empty anonymous_list_keep_headers:" option defined. > I commented out and now test email went through by using anonymous option successfully. > One small thing, but so much trouble. Great! > My bad that i didint notice it before. Please, don't say that. It's very difficult to judge what a user should notice in many cases. Especially in a case like this, where in fact much of the processing is hard-coded, you might assume that not only do we hard-code the fields to delete but we also hard code the RFC822-required fields. And we probably should: https://gitlab.com/mailman/mailman/-/issues/1031 Steve

2 years, 10 months

[MM3-users] Re: MM3 Docker

by Mark Sapiro

On 1/8/19 10:03 AM, Odhiambo Washington wrote: > > Thank you for clarifying. > So once I have a venv created, the services will just run as long as the > startup scripts are running even when I'm logged out of the system? As long as the startup scripts actually reference things in the venv. If you look at the samples in the Recommended Configuration section at <https://wiki.list.org/x/17891998> for /opt/mailman/mm/bin/django-admin (sample) Script to run Django management commands. /opt/mailman/mm/bin/mailman (sample) Script to run mailman commands. and /opt/mailman/mm/bin/gunicorn (sample) Script to start Gunicorn. You will see they all do things like activate the venv or run a command from venv/bin. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Cannot show archives

by Qiuhong.Su �K秋�t

Hi all, After I setup mailman3 and run mailman-suite, I can do: 1. Register user 2. Login 3. Create new Domain 4. Create new List 5. Subscribe to the list When I try to send email to the list by run command: echo ��test email�� | mail �Cs ��test email�� test(a)example.com<mailto:test@example.com> User test can receive this email, but I cannot find it on Archives, and other members cannot receive this email too. Can anyone help me? Thank you! Regards, Qiuhong ************************************************************************* This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. [Delta Electronics, INC. China] *************************************************************************

5 years, 10 months

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

by Michael Hazan

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 ? I’m using the virtual env setup and i have been trying to manipulate via the mailman-web shell but it doesn’t work when adding a new style. I need to delegate list creation to admins and I don’t want them to have to redo every list settings for every list they create when they are the same style. 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 ? Thanks for the help. Michael

3 years, 3 months

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 2/1/23 10:32, Allan Hansen wrote: > Thank you, Mark. > By > > "However, all of the above can be avoided without any DMARC changes by > enabling bounce probes." > > Do you mean that I can get rid of the 'From' mangling, which has been a frequent source of embarrassment because the list address is captured and reused by type-ahead when sending non-list messages and those messages instead going to 1000 subscribers. No. If you enable bounce probes, it will prevent users having delivery disabled and being unsubscribed by bounce if the only bounces are for DMARC policy reasons, but they will still be missing mail if you don't apply DMARC mitigations. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Bulk delivery status change?

by Odhiambo Washington

On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: > Mistakes were made, and for while every single outbound email bounced. > I've fixed the mistakes, but now in my largest and most active email list, > every single user's delivery status is "Disabled by Bounces". > > Is there a way to bulk fix this? Or do I have to go into each user, one at > a time, and fix them? <odhiambo(a)gmail.com> Please see this thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

8 months, 3 weeks

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

by Mark Sapiro

On 5/20/21 2:28 PM, Andreas Barth wrote: > > Any hints how to do that best? Is it possible to store custom > attributes, or should that be stored elsewhere? Storing custom attributes as part of the MailingList object would require modifying the model in mailman/model/mailinglist.py and probably creating an alembic migration https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/datab…. This would add significant complication to upgrading Mailman core. I think a better approach would be to store custom attributes in a separate database table. Also, you might look at plugins as a way to access your custom attributes via REST without having to modify Mailman core itself. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

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

by Kimmo L

Hey Mark! Diagram chart thing works fine. I had to give the new server time to get him running :) Also about held message - it seems to working now. At least i have run couple of new tests and no issues so far. Everything seems to work smoothly after migration from one server to another. The only concern I've observed and I'm trying to solve right now is with memory. Not sure whats consumes the memory gradually, so that it will start consume also swap memory and eventually you can find"OSError: write error" entries in uwsgi-error.log or "django.request Internal Server Error: /hyperkitty/" in mailmanweb.log Do i need to modify my uwsgi.ini configuration maybe ? Server has 2CPU and 5GB RAM.

2 years, 11 months

[MM3-users] Re: Getting information to connect mailman to new web host

by Mark Sapiro

On 8/11/22 07:24, tg337--- via Mailman-users wrote: > We moved over to a new platform and now our lists.(domain).org address is not working. I'm trying to find the records I would need to update on the new site to connect them, and not sure how. I'm sorry. I can't give a more definitive response without more information. How was Mailman installed on the prior server? New server? Have you moved the Mailman database(s)? When you say your lists.(domain).org address is not working, do you mean a web address or an email address? What's in logs for this failed address? -- 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 core

by Ralf Wiegand

https://docs.mailman3.org/en/latest/install/install.html I was following this "official" page. There is no word on "pip install mailman" as an alternate choise? There is also a reference in regards to "Virtualenv Installation <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…>, recommended for Production" ... why is this recommended? Does the "pip install mailmail" install a production environment I can trust? On 5/29/20 10:41 AM, Ralf Wiegand wrote: > Mark - What is the difference between to two install methods? What are > my pros and cons? > > > I have been using this: > > >>>> > > |# Note: if we are using a dedicated postgresql database server, all > postgresql changes need to be done on the actual postgresql server.| > |>>>| > |sudo yum install postgresql-server postgresql-contrib| > |sudo postgresql-setup initdb| > |sudo systemctl start postgresql| > |sudo systemctl enable postgresql| > |sudo -u postgres psql -c ||"SELECT version();"| > |sudo useradd -c ||"Mailman User"| |-s /bin/bash -m mailman| > |sudo -u postgres create role mailman;| > |sudo -u postgres createdb -O $USER mailman| > |sudo -u postgres psql -c ||"grant all privileges on database mailman > to mailman;"| > |sudo -u postgres psql -c ||"ALTER ROLE mailman WITH PASSWORD > 'secret123';"| > |sudo -u postgres psql -c ||"ALTER ROLE "||mailman||" WITH LOGIN;"| > |sudo echo ||"listen_addresses = '*' "| |>> > /var/lib/pgsql/10/data/postgresql.conf| > |sudo echo ||"# The user mailman will be able to access all databases > from a trusted location (any) without a password"| |>> > /var/lib/pgsql/data/pg_hba.conf| > |sudo echo ||"host all mailman 0.0.0.0/0 trust"| |>> > /var/lib/pgsql/data/pg_hba.conf| > |sudo systemctl restart postgresql| > |sudo ss -nlt | grep 5432| > |<<<| > |sudo yum install python36* --skip-broken -y| > |# check make sure you have both versions| > |sudo python --version| > |Python 2.7.5| > |sudo python3 --version| > |Python 3.6.8| > |sudo pip3 install psycopg2-binary| > |sudo chown mailman.mailman /opt/mailman| > |sudo chmod 755 /opt/mailman| > |# NOTE: The first initial mailman3 core setup has to be done manually.| > |# This is a important step to ensure the user "mailman" will run the > actual mailman3 application and not root.| > |# switch to user mailman| > |mailman# cd /opt/mailman| > |mailman# git clone https:||//gitlab.com/mailman/mailman.git| > |mailman# cat <<EOT >> > /opt/mailman/mailman/src/mailman/config/mailman.cfg| > |[devmode]| > |enabled: yes| > |recipient: root@localhost| > |[webservice]| > |hostname: localhost| > |port: 8001| > |show_tracebacks: yes| > |use_https: yes| > |[mta]| > |incoming: mailman.mta.postfix.LMTP| > |outgoing: mailman.mta.deliver.deliver| > |lmtp_host: localhost| > |lmtp_port: 8024| > |smtp_host: localhost| > |smtp_port: 25| > |[database]| > |class||: mailman.database.postgresql.PostgreSQLDatabase| > |url: postgres:||//mailman:secret123@<IP-ADDRESS or FQDN>/mailman| > |EOT| > |mailman# python3.6 -m venv venv-3.6| > |>>| > |mailman# source venv-3.6/bin/activate| > |(venv-3.6) [mailman@empire mailman]$ cd mailman| > |(venv-3.6) [mailman@empire mailman]$ python setup.py develop| > |(venv-3.6) [mailman@empire mailman]$ mailman info| > |<<| > | > | > | > | > |So I was told I don't have to do this, I can just simple do (rhel7) > | > |yum install pyhton3| > |pip install mailman| > | > | > | > | > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 2 months

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

by paul.sparks＠us.idemia.com

Thanks to Mark Sapiro and others who have answered questions on this list. It has made my job easier. I'm hoping someone can help with another issue I'm seeing. I'm setting up a new mailman 3 server and doing some test posts to a list. This server is intended only as an announcement list with limited members allowed to post. The resulting emails coming from the list do not include the List-Unsubscribe header although other "List-XXX" headers are included. I'm trying to figure out why the header is missing. It seems clear from the code that the header should be included. Here is partial text of the email source as received from the list. I've tried viewing in Outlook.com, Thunderbird, and even captured the email text at postfix prior to sending to look for the missing header. My domain has been replaced with "example.com" throughout. This is from the postfix capture ________ ... To: "test1(a)example.com" <test1(a)example.com> Thread-Topic: Post 8 test Thread-Index: AQHb8oBBzPBOYgrDxUOIiAxhvUzthA== Date: Fri, 11 Jul 2025 16:24:38 +0000 Accept-Language: en-US Content-Language: en-US msip_labels: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=example.com; MIME-Version: 1.0 Message-ID-Hash: FWHZCRE4EA6IFP4BZTPIF23DKAKVRMDT X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Content-Filtered-By: Mailman/MimeDel 3.3.10 From: "Somewhere1, SW" <test1(a)example.com> X-Mailman-Version: 3.3.10 Precedence: list Reply-To: no-reply(a)example.com Subject: [Test1] Post 8 test List-Id: "Somewhere1, SW" <test1.example.com> List-Help: <mailto:test1-request@example.com?subject=help> List-Owner: <mailto:test1-owner@example.com> List-Post: NO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20250711163343.017C31DBB79(a)example.com> Body text ... __________ Details on my test setup: # Mailman version. __version__ = '3.3.10' OS: Amazon Linux 2023 (RHEL 9 compatible) MTA: postfix-3.7.2 I am using the following code with mailman shell to configure the list. include_rfc2369_headers is left at the default value of True (verified via mailman shell) ____________ # Description value must be passed as a parameter def configure_list(ml, description): #ml.accept_these_nonmembers = allowed_to_post ml.admin_immed_notify = False ml.advertised = False ml.allow_list_posts = False ml.anonymous_list = True ml.archive_policy = ArchivePolicy.never ml.bounce_info_stale_after = datetime.timedelta(days=90) ml.bounce_notify_owner_on_disable = False ml.bounce_notify_owner_on_removal = False ml.bounce_score_threshold = 3 ml.bounce_you_are_disabled_warnings = 0 ml.default_member_action = Action.discard ml.default_nonmember_action = Action.discard ml.description = description ml.digests_enabled = False ml.filter_content = True ml.first_strip_reply_to = True ml.forward_auto_discards = False ml.max_days_to_hold = 1 ml.max_message_size = 0 ml.nntp_prefix_subject_too = False ml.pass_extensions = [] ml.pass_types = ['text/plain','multipart/alternative'] ml.reply_goes_to_list = ReplyToMunging.explicit_header ml.reply_to_address = "no-reply(a)example.com" ml.require_explicit_destination = False ml.respond_to_post_requests = False # Allow select members to post to list for mbr in ml.members.members: if str(mbr.address) in allowed_to_post: mbr.moderation_action = Action.defer print('end',mbr.address,mbr.moderation_action) _______________ /etc/mailman3/mailman.cfg file: # /etc/mailman3/mailman.cfg # These settings override the defaults in the following 2 config files # /opt/mailman/lib/python3.9/site-packages/mailman/config/schema.cfg # /opt/mailman/lib/python3.9/site-packages/mailman/config/mailman.cfg [paths.custom] var_dir: /data/lib/mailman pid_file: /data/lib/mailman/pid/master.pid lock_file: /data/lib/mailman/pid/master.lock [mailman] layout: custom # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: ml-owner(a)example.com [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgresql:///mailman # No archiving enabled [archiver.prototype] enable: no [archiver.hyperkitty] enable: no [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 [passwords] # When Mailman generates them, this is the default length of passwords. password_length: 15 [logging.debug] path: debug.log level: debug ______________ With debug enabled I see the rfc-2369 pipeline being run when processing the post to the list. Jul 11 17:51:32 2025 (444088) [IncomingRunner] starting oneloop Jul 11 17:51:32 2025 (444088) [IncomingRunner] processing filebase: 1752256291.9136803+bfd305a28151ce750dde5114b413b351fa4d1284 Jul 11 17:51:32 2025 (444088) [IncomingRunner] processing onefile Jul 11 17:51:32 2025 (444090) [OutgoingRunner] starting oneloop Jul 11 17:51:32 2025 (444090) [OutgoingRunner] ending oneloop: 0 Jul 11 17:51:32 2025 (444097) [DigestRunner] starting oneloop Jul 11 17:51:32 2025 (444097) [DigestRunner] ending oneloop: 0 Jul 11 17:51:32 2025 (444088) [IncomingRunner] finishing filebase: 1752256291.9136803+bfd305a28151ce750dde5114b413b351fa4d1284 Jul 11 17:51:32 2025 (444088) [IncomingRunner] doing periodic Jul 11 17:51:32 2025 (444088) [IncomingRunner] committing transaction Jul 11 17:51:32 2025 (444088) [IncomingRunner] checking short circuit Jul 11 17:51:32 2025 (444088) [IncomingRunner] ending oneloop: 1 Jul 11 17:51:32 2025 (444088) [IncomingRunner] starting oneloop Jul 11 17:51:32 2025 (444088) [IncomingRunner] ending oneloop: 0 Jul 11 17:51:32 2025 (444087) [CommandRunner] starting oneloop Jul 11 17:51:32 2025 (444087) [CommandRunner] ending oneloop: 0 Jul 11 17:51:32 2025 (444091) [PipelineRunner] starting oneloop Jul 11 17:51:32 2025 (444091) [PipelineRunner] processing filebase: 1752256292.373131+a372784a3ff7a76a662ed1c62c224a53a8008b8b Jul 11 17:51:32 2025 (444091) [PipelineRunner] processing onefile Jul 11 17:51:32 2025 (444096) [VirginRunner] starting oneloop Jul 11 17:51:32 2025 (444096) [VirginRunner] ending oneloop: 0 Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: validate-authenticity Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: mime-delete Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: tagger Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: member-recipients Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: avoid-duplicates Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: cleanse Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: cleanse-dkim Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: cook-headers Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: subject-prefix Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: rfc-2369 Jul 11 17:51:32 2025 (444091) RFC 2369 process Jul 11 17:51:32 2025 (444091) RFC 2369 process continue 1 Jul 11 17:51:32 2025 (444091) RFC 2369 process headers extend Jul 11 17:51:32 2025 (444091) RFC 2369 process header for loop Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: to-archive Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: to-digest Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: to-usenet Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: after-delivery Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: acknowledge Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: dmarc Jul 11 17:51:32 2025 (444091) <20250711175131.B8CEC1DA51B(a)example.com> pipeline default-posting-pipeline processing: to-outgoing Jul 11 17:51:32 2025 (444091) [PipelineRunner] finishing filebase: 1752256292.373131+a372784a3ff7a76a662ed1c62c224a53a8008b8b Jul 11 17:51:32 2025 (444091) [PipelineRunner] doing periodic Jul 11 17:51:32 2025 (444091) [PipelineRunner] committing transaction Jul 11 17:51:32 2025 (444091) [PipelineRunner] checking short circuit Jul 11 17:51:32 2025 (444091) [PipelineRunner] ending oneloop: 1 Jul 11 17:51:32 2025 (444091) [PipelineRunner] starting oneloop Jul 11 17:51:32 2025 (444091) [PipelineRunner] ending oneloop: 0 Jul 11 17:51:32 2025 (444085) [ArchiveRunner] starting oneloop Jul 11 17:51:32 2025 (444085) [ArchiveRunner] ending oneloop: 0 Jul 11 17:51:33 2025 (444090) [OutgoingRunner] starting oneloop Jul 11 17:51:33 2025 (444090) [OutgoingRunner] processing filebase: 1752256292.8885148+5e5c4a68eacfead13561df616fe7ca19e1d1d182 Jul 11 17:51:33 2025 (444090) [OutgoingRunner] processing onefile Jul 11 17:51:33 2025 (444097) [DigestRunner] starting oneloop Jul 11 17:51:33 2025 (444097) [DigestRunner] ending oneloop: 0 Jul 11 17:51:33 2025 (444090) [outgoing] <function deliver at 0x7f21ed7b1310>: <175225629286.444091.14942604217243398224(a)ip-10-0-0-168.us-gov-west-1.compute.internal> Jul 11 17:51:33 2025 (444088) [IncomingRunner] starting oneloop _____________ I tried inserting some log.debug calls into lib/python3.9/site-packages/mailman/handlers/rfc_2369.py to see where headers were being removed and added. I modified: log = logging.getLogger('mailman.debug') and inserted log.debug throughout the process function and one in the top level. ___________ ... @public @implementer(IHandler) class RFC2369: """Add the RFC 2369 List-* headers.""" name = 'rfc-2369' description = _('Add the RFC 2369 List-* headers.') log.debug('RFC 2369 processing') def process(self, mlist, msg, msgdata): """See `IHandler`.""" process(mlist, msg, msgdata) __________ When running with debug enabled, I see this top level message many times at the top of the debug.log file during mailman startup, but not after that. I don't see any of my other debug messages. _____________ Jul 11 16:03:36 2025 (409226) RFC 2369 processing Jul 11 16:03:40 2025 (409244) RFC 2369 processing Jul 11 16:03:41 2025 (409250) RFC 2369 processing Jul 11 16:03:49 2025 (409271) RFC 2369 processing Jul 11 16:03:50 2025 (409271) [DigestRunner] starting oneloop Jul 11 16:03:50 2025 (409271) [DigestRunner] ending oneloop: 0 Jul 11 16:03:50 2025 (409261) RFC 2369 processing Jul 11 16:03:50 2025 (409261) [BounceRunner] starting oneloop Jul 11 16:03:50 2025 (409261) [BounceRunner] ending oneloop: 0 Jul 11 16:03:50 2025 (409264) RFC 2369 processing Jul 11 16:03:50 2025 (409267) RFC 2369 processing Jul 11 16:03:51 2025 (409262) RFC 2369 processing Jul 11 16:03:51 2025 (409262) [CommandRunner] starting oneloop Jul 11 16:03:51 2025 (409262) [CommandRunner] ending oneloop: 0 Jul 11 16:03:51 2025 (409266) RFC 2369 processing Jul 11 16:03:51 2025 (409266) [PipelineRunner] starting oneloop Jul 11 16:03:51 2025 (409266) [PipelineRunner] ending oneloop: 0 ... __________ Any suggestions on where else I can look? Any thoughts on why my debug calls are not showing in the logs?

3 weeks

[MM3-users] Re: Hyperkitty: remove discussions

by Mark Sapiro

On 5/21/20 7:25 PM, Peter Adebahr via Mailman-users wrote: > > Hi *, > > is it possible to remove discussions from the archives? As it were tests > only, removing the complete archive would be ok, too. For the customer, > we would like to start this list with a clean archive :) Current HyperKitty can delete the current thread or message and even the entire list archive if you are logged in as a superuser. Also see <https://gitlab.com/mailman/hyperkitty/-/issues/261>. And also see <https://gitlab.com/mailman/hyperkitty/-/issues/3> for a way tyo do this in a django-admin shell, but that doesn't work with MySQL or MariaDB as the database manager because of foreign key constraints. -- 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] Mailman3 upgrades

by dancab＠caltech.edu

I've encountered an issue where Mailman3 is looking for an older jquery package after updating HyperKitty to 1.3.5. I found the error below via Firefox developer tools. "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. ls -l static/hyperkitty/libs/jquery/ total 692 -rw-r--r-- 1 gunicorn root 288580 Oct 19 14:55 jquery-3.6.0.js -rw-r--r-- 1 gunicorn root 89501 Oct 19 14:55 jquery-3.6.0.min.js -rw-r--r-- 1 gunicorn root 137972 Oct 19 14:55 jquery-3.6.0.min.map -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 -rw-r--r-- 1 gunicorn root 68 Oct 19 14:55 jquery-ui-selection.txt drwxr-xr-x 1 gunicorn root 4096 Oct 19 14:55 smoothness Any ideas? Thanks again for all your help. -- Dan Caltech

3 years, 9 months

[MM3-users] Re: User suspended after too much spam

by Mark Sapiro

On 3/6/22 05:55, Eggert Ehmke wrote: > I have set up spamassassin as spamfilter, and it works reasonable so far. Some > spam passes the filter and I try to use it for training. However, one of my > users has a very restrictive spam filter and rejects all spam. This causes > mailman to suspend that user. I have to enable the user each time. > > How can I change that behaviour? I do not want my users to be suspended. Set verp_probes: yes in the [mta] section of mailman.cfg. This situation is exactly what verp probes are designed for. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Database deadlock when trying to delete a member.

by Abhilash Raj

Hi Simon, > On Mar 17, 2021, at 10:16 PM, Simon Coggins <s.coggins(a)cqu.edu.au> wrote: > > Hi, > > I’ve got a strange error. I migrated from mailman 2.1 to 3 using the migration guide on the website and things have been working fine. But I’m in the process of testing the new syncmembers command to replace some inhouse mailman API code we wrote. I’ve tracked my problem down to what appears to be a deadlock in the postgresql database. When trying to delete certain users the SQL query hangs and never returns. > > After doing some tracing and tracking it down to the database, I enabled DB logging of all queries and saw that the following query was never returning: > > DELETE FROM member WHERE member.id = 166814 > > If I try to run it manually I get the same issue, in psql it never returns. > mailman=# explain analyze DELETE FROM member WHERE member.id = 166814; > [… 60 seconds passes…] > ^CCancel request sent > ERROR: canceling statement due to user request > CONTEXT: while deleting tuple (2998,72) in relation "member" > I’m just wondering if there are any commands or scripts I can run to verify the database and it’s constraints to see if there is some error in the database data? Or where you’d recommend I go from here? It only impacts the user on this specific list. If I add this user to another list and remove them, everything works fine. Are you able to retrieve that Member object using API? This[1] the Python code which would try to delete a Member object and I am assuming is being called from syncmembers command. I am not entire sure about what would cause the database to hang, if there was some database constraint that failed, I would imagine some error to be returned. [1]: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p… One thing you can try is see if you can unsubscribe the user using the API or `mailman shell` command. You can unsubscribe from API by calling a `DELETE` method at http://localhost:9001/3.1/members/<member_id> This would give us some indication about whether there is some bug in the implementation of syncmembers command or if there is something else going on. > > This is on a test system so I can do various testing. I’m trying to find the root cause so that I can verify my production system isn’t impacted by the same thing. > > > Setup Details: > OS: Oracle Linux 7 (Redhat) > Installed using pip via virtualenv talking to a local pgsql database on the same box. > Data was migrated from a mailman 2.1 install into mailman3 using migration instructions on the website. > > PIP Modules versions: > django-mailman3 1.3.5 > mailman 3.3.3 > mailman-hyperkitty 1.1.0 > mailmanclient 3.3.2 > postorius 1.3.4 > psycopg2-binary 2.8.5 What is the version of sqlalchemy package? There is a new 1.4.0 version that came out recently and is incompatible with Core right now. There are backwards incompatible changes which might need some changes in Core to add support. > > RPM packages: > postgresql12-12.6-1PGDG.rhel7.x86_64 > postgresql12-server-12.6-1PGDG.rhel7.x86_64 > postgresql12-libs-12.6-1PGDG.rhel7.x86_64 > postgresql12-devel-12.6-1PGDG.rhel7.x86_64 > > > -Simon > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: Introducing Mailman Web project

by Abhilash Raj

On Tue, Mar 26, 2019, at 2:03 PM, Ralph Seichter wrote: > * Abhilash Raj: > > > I have updated it, so example config should also work now :) > > I can confirm that "django-admin migrate" now works with PostgreSQL. > > By the way, how about adding wsgi.py and whatever else might be required > to allow running with uWSGI? It is already there (mailman_web.wsgi.application[1]), I do need to work on docs for that. It can be updated to set default settings to mailman_web.settings as default settings module in wsgi.py. [1]: https://gitlab.com/mailman/mailman-web/blob/master/mailman_web/wsgi.py > > -Ralph > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 4 months

[MM3-users] Re: List invisible to moderator

by Mark Sapiro

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

5 years, 1 month

[MM3-users] Re: troubleshooting hyperkitty

by Morris Jones

On 12/9/2020 9:11 PM, Mark Sapiro wrote: >> path: /opt/mailman/var/logs/archiver.log api_key <--- ?? Ugh ... I must have garbled my email. The files look fine. I don't know where that stray "api_key" came from. > The key in settings_local.py is MAILMAN_ARCHIVER_KEY, not > MAILMAN_ARCHIVER_FROM, a typo in your mail or ?? Yes, typo ... MAILMAN_ARCHIVER_KEY is 'properly_quoted' and unquoted in mailman-hyperkitty.cfg I'm guessing the next thing I need to do is find a way to crank up the logging in mailman and look for occasions where it calls the hyperkitty endpoint and delivers the message. I tried this but it may not be the right syntax: [logging.archiver] level: debug path: /opt/mailman/var/logs/archiver.log Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 7 months

[MM3-users] Re: mass subscribers disablement!?

by Mark Sapiro

On 11/26/21 9:39 AM, Christian Stalberg via Mailman-users wrote: > After the first time where users were unsubscribed automatically, I added > back one at a time all the subscribers who were unsubscribed. Now they have > all been unsubscribed again automatically. They are valid working email > addresses. How can I stop this behavior from occurring please? Do you have the bounce processing notifications `Notify owner on disable` and `Notify owner on removal` set to `Yes`. If not, set them. Then, what's in the notices you receive? You might also consider setting `verp_probes: yes` in the `[mta]` section of mailman.cfg. This will avoid some issues with users being disabled/unsubscribed due to list posts being rejected as spam. -- 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: Displaying addresses in emails from a Mailman 3 installation

by Stephen J. Turnbull

Hi Steve, Somebody (maybe me) forgot to send this to the list. Since you mention Mark, I'm sure "to list" was your intention, and I'm going to quote in full as well. Steve Brown writes: > Thanks, other Steve. I know so little about Alter Messages and > DMARC mitigations that I basically left all those settings at their > defaults unless I was advised otherwise by the MM3 hosting service > (Mailmanlists.net out of Australia). Internet mail is very complicated. I am somewhat familiar with at least 50 documents describing how it's supposed to work (sometimes multiple editions of the same one!), and I discover new ones that I really ought to learn about several times a year. > First strip Reply-To: nothing; neither Yes nor No is checked Pretty sure this defaults to "No". To my mind, this should never be done (it means that there may be no way for an MUA to automatically identify and reply to author, and our "anonymous list" style does this anyway so it's not necessary for that purpose), but it is often done by discussion lists that want to keep traffic on-list. I recommend you set it to "No" so you don't have to remember the default. > Reply goes to list: No munging This is preferred by people who discuss sensitive matters (it reduces accidental distribution of mail intended for specific recipients). Strictly speaking, the Internet standard for the corresponding header's use says that it is to be *set* by the author *only*, but many mailing lists set it to the list to "encourage discussion". > Explicit reply-to address: nothing; box is empty This only affects anything if "Reply goes to list" is set to explicit. > DMARC mitigation action: Replace From: with list address This is the recommended setting. "None" is impractical because many recipients will reject a lot of mail, which will be recorded as bounces for those recipients (who are doing nothing wrong). "Wrap" is impractical because there are a number of popular mail clients (Apple Mail, for one) which make it almost impossible to read the mail. And reject and discard mean that those authors can't post to your list at all, but they usually can't affect their email providers' DMARC policies. > DMARC Mitigate unconditionally: Yes This one you should talk to your subscribers and maybe your provider. "Yes" means that *all* posts will have From changed to the "Steve Brown via a-list(a)example.net" form. An alternative is to set it to "No", which means that the mailing list checks the policy of the author's domain, and changes From only if the domain has a policy of "reject" or "quarantine". Advantage: - Some fraction of the posts would have "From" displayed as the author intended it. Depends on policies of your posters' providers. Could be very large if most are academics posting from departmental addresses, could be very small if most are posting from personal Gmail addresses. There are three possible downsides: - People from "strict" domains complain about discrimination. - Subscribers are confused by multiple formats. - The list's administrative burden increases because Gmail in its infinite disdain for the rest of the world has decided that it does not apply DMARC to mail received by the rest of the world (its published policy is "none"), but it *does* apply it to mail Gmail -> list -> Gmail. I think the most recent versions of Mailman 3 apply the mitigation action to Gmail implicitly, and if not it's simple to add "^.*(a)gmail\.com" to the "DMARC addresses" setting. The issue is that other providers may think "that's a great idea", and there's no way to find out they're doing it except that you get a lot of bouncers from subscribers using that provider. So you have to monitor bounces. > If you think it might help to change any of those, I'll try it and > then roll back if it causes other problems. That's your call. I do recommend setting "First strip Reply-To" to "No" to make it explicit. All the others except "DMARC Mitigate unconditionally" are the recommended settings for your purposes. For "DMARC Mitigate unconditionally", I remember a lot of complaints from AOL and Yahoo! users back in the day about "discrimination", but I imagine people are used to DMARC mitigation by now (and of course popular MUAs try to hide it using associations). I've never seen much confusion from the multiple formats, but some people just value consistency in the user interfaces they use. And the administrative burden is likely to be nil unless you're really compulsive about such things -- you just wait for bounces from a random domain to spike and check for "From a(a)ran.dom" getting bounced by "subscriber(a)ran.dom", and add "^.+(a)ran\.dom" to the "DMARC addresses" list if and when it happens. Really only Gmail and Yahoo! are big enough to do this, and most yahoo.* domains already have a "reject" policy. > I also think that a tweak to the T-bird MUA is a strong suspect. The > affected subscriber is an old guy like me and in my experience it is also a > PITA for him to deal with Mozilla, his email provider (Breezeline), or any > other tech intermediary. > > Mark: Thanks for the suggestions on searching T-bird emails. I'm going to > refrain from passing them on to my subscriber right now as they would > probably seem like another PITA. I agree on that one, although in the long run he'd probably be a lot happier. Another possibility would be to keep a browser tab open on HyperKitty's RADG page, and search authors there. This should work because DMARC processing takes place after archiving in the builtin pipeline, so HyperKitty should know the author accurately. Of course this is suboptimal, but it may be more straightforward than messing with MUA settings (and it works for all MUAs!) Regards, Yet another Steve > On Thu, Jul 3, 2025 at 12:06?AM Stephen J. Turnbull <steve(a)turnbull.jp> > wrote: > > > Steve Brown via Mailman-users writes: > > > > > "For a while now, my e-mail for this list (but not other lists) > > > just shows "To RADG" from "RADG" with a "CC" showing the actual > > > sender's address. > > > > It's very difficult to figure out what's going on with such an > > abbreviated description of what he's seeing. > > > > It may be possible to get better results with alterative settings on > > the list. > > > > In the settings for RADG, under "Alter Messages", what are the > > settings for "First strip Reply-To", "Reply goes to list", and > > "Explicit reply-to address"? > > > > Under "DMARC mitigations", what are the settings for "DMARC mitigation > > action" and "DMARC mitigate unconditionally"? > > > > > Because some other members, including me, have had problems with > > > unexpected entries in both From and To lines, I suspect that > > > Mailman 3 does the DMARC enough differently > > > > The only thing I can think of that might allow other lists to have > > author names for other lists but not for a Mailman list is that the > > MUAs are parsing email addresses out of the display name (which is a > > horrible risk, given the flexibility that users have in setting email > > headers, and especially display names). If there is no email address, > > then they completely ignore the content of the display name in favor > > of their preferred display name for the list. > > > > > My understanding is that all of the recent posts are missing the > > > poster's name, after behaving as expected for some time. Something > > > must have changed, but what is baffling me. If you have any > > > further ideas, fine, but don't waste a lot of time on this. > > > > MUA "upgrade" seems like as likely an explanation as any. I think if > > you want to know details what's going on for a particular user, their > > MUA's support channels are the best bet. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 weeks, 1 day

[MM3-users] Re: Can "Pre Verified" set to yes by default?

by Mark Sapiro

On 12/19/22 00:21, Stephen J. Turnbull wrote: > > I don't know if there's a way to do this in settings.py, but I > suspect not. Maybe Mark knows a way. Well, I haven't tried this and I don't recommend it, but while the intent of settings.py is to assign values to various known attributes, it is a Python module which is imported and could contain any valid Python code including code to read, modify and rewrite .../site-packages/postorius/forms/list_forms.py. However, my recommendation is to maintain your local patches in a script that you can run following an update to apply them. -- 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: "this held message has been lost"

by Mark Sapiro

On 6/9/25 13:34, My Self via Mailman-users wrote: > Hi > > I've upgraded mailman to the latest packages, and suddenly I'm experiencing the same. > It's running on python 3.12 because an issue with nntplib > > There is no race condition, because I'm the only moderator. And I'm not seeing how it can be cross-posted. > It's not immediately, it happens after a while. What `latest` packages? Prior to Mailman 3.3.10 there was a bug in the task runner that could do this. See https://gitlab.com/mailman/mailman/-/issues/1162 (tl;dr skip to https://gitlab.com/mailman/mailman/-/issues/1162#note_2113461048) and https://gitlab.com/mailman/mailman/-/merge_requests/1212. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

> > Please confirm that setting up a rule for cc's in Header Filter to "hold for moderation," it should block the member from sending a cc? It will hold for moderation any message containing a Cc: header. It won't prevent the moderator from accepting the message. > And, for the pattern, are you suggesting I use ".*" with cc: as the regexprs? Or, what exactly do I use under as a regular expression? Use cc as the header and the two characters .* as the pattern (or whatever affinity calls it). See https://docs.python.org/3/library/re.html for information about Python regular expressions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: moving list from mm3 -> mm3

by Jens Günther

Hey Stephen, thank you for your answer. Am 31.12.23 um 08:45 schrieb Stephen J. Turnbull: > My guess is that the REST API is expecting a single JSON object, and > you sent it multiple parameters. > > Have you played with the REST API interactively? The documentation at > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > is really quite good as a tutorial. It's not a full API reference, > and not organized that way, although the table of contents is very > useful for what it does mention. But I think what you need (if you > want to explore it that deeply) is a tutorial to get a "feel" for how > the REST API "likes to talk". Thanks for this advice. I did read the doc and figured out, that PUT and PATCH for my concerns should be the right way to do it: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… (PUT for all writable attributes, with PATCH, one can change one attribute at a time) When playing around, I figured out that there are also Read-only attributes, that can't be set (just got that when Playing with PATCH-command), which are exactly the ones in the PUT-error. So my main question is now: does anybody know of a possibility with this command to extract only writable attributes!? The ones that are too much are: "Unexpected parameters: bounces_address, created_at, digest_last_sent_at, fqdn_listname, http_etag, join_address, last_post_at, leave_address, list_name, mail_host, next_digest_number, no_reply_address, owner_address, post_id, posting_address, request_address, usenet_watermark, volume" > You should post the exact command or interactive conversation you're > using. Getting the config: curl -u restadmin:restpass localhost:8001/3.1/lists/listname.domain/config | jq > listname.domain curl -u restadmin:restpass -d @listname.domain -H "Content-Type: application/json" -X PATCH localhost:8001/3.1/lists/listname.domain/config -> one has to be careful when deleting attributes, at the end of an array, there must not be a "," (!) :-) > > Is there another way to preserve these information about the > > members? > > You can query the REST API (you might need to fetch the subscriber > roster, then iterate over that to get the details), or you can dump > the database table (or the whole database) using SQL-based utilities > like psql (Postgres, I forget the MySQL equivalent). The first point sounds reasonable and I get now with the doc, how it could work ... but maybe a little too much for now, dommage. Just tried getting all the members: curl -u restadmin:restpass localhost:8001/3.1/lists/listname.domain/roster/member | jq > listname.domain.members But putting them back seems to be a different thing: curl -u restadmin:restpass -d @listname.domain.members -H "Content-Type: application/json" -X PUT localhost:8001/3.1/lists/listname.domain/roster/members > > (in general I don't think a lot of people put in effort to > > customize there memeberships ... and furthermore they would need to > > register, right?) > > Not sure what you mean by "register", but every address that writes to > Mailman gets a temporary user until a "real" user claims it via the > mailbox ownership dance. If they receive mail in a mailbox, they've > done the ownership dance for that mailbox. If you don't preserve that > record, they'll have to do it again. Yes. I was talking about "real" users that claim ownership by registering via their mailaddress. Thanks for your answers again, regards.

1 year, 6 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 9:04, Stephen J. Turnbull wrote: > Victoriano Giralt writes: > > > Thanks Stephen for reminding me that sometimes I write what looks like > > proper English on the surface, but the meaning of it comes from the > > deep corners of my mind in some long forgotten dialect :-) > > Your English is fine, it was just my lack of imagination: on February > 12, I couldn't conceive of February 3 being even a little "old"! But... here is a thing that I can not understand: If the source (the .po file) is from november 7th, it doesn't matter how many times you recompile it: the result will be the same. I did what Mark recommended. Before that: /usr/local/lib/python3.7/site-packages/mailman/messages/es/LC_MESSAGES # ls -la total 192 drwxr-xr-x 2 root wheel 512 Feb 8 12:00 . drwxr-xr-x 3 root wheel 512 Feb 8 12:00 .. -rw-r--r-- 1 root wheel 80700 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root wheel 102963 Nov 7 01:50 mailman.po Then... /usr/local/lib/python3.7/site-packages/mailman/messages/es/LC_MESSAGES # msgfmt -o mailman.mo mailman.po And that is: the same .mo file just with different date /usr/local/lib/python3.7/site-packages/mailman/messages/es/LC_MESSAGES # ls -la total 192 drwxr-xr-x 2 root wheel 512 Feb 13 11:09 . drwxr-xr-x 3 root wheel 512 Feb 13 11:09 .. -rw-r--r-- 1 root wheel 80700 Feb 13 11:09 mailman.mo -rw-r--r-- 1 root wheel 102963 Nov 7 01:50 mailman.po I'm not trying to diminish the effort and the excelent work that are indeed making all of you. I appreciate that so much. But is evident to me that something fails in the translation path chain of upgrades. If you access the postorius web to manage subscriptions you can see a full mixed language words. It's not a life or death item... but it has not to be that way as the terms, as far as I know, are 100% translated (at least in spanish). And the subscriptors complain. If that is not a thing that the release manager can do, well... We are stucked, isn't it? I don think it has to be a matter of "automate production of pip'able packages containing only new translations": a new version has just released and the localization languages, at least spanish, were not merged into it for the last Weblate updates. I will wait untill the next update, this thread is closed to me. Thanks, again, for all your good work. > > More important, as long as the .mo file is more recent than the .po > file, that's the best the release manager can do. I haven't been > involved in the release process, so I can't swear to it personally, > but if Mark says that new translations generate a merge request > automatically, and we make sure that the translations are merged > before release, I believe him. That's optimal as far I am concerned. > > Perhaps some enterprising soul would be willing to automate production > of pip'able packages containing only new translations, but without > that, I don't see how to beat our current procedures. (I wouldn't > want to use such a thing, though, I'd be too afraid that one day all > the translations would be replaced with Dril tweets!) > _______________________________________________ > 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, 5 months

[MM3-users] Re: Python is updated

by Mark Sapiro

On 4/27/23 11:42 AM, Lars Bjørndal wrote: > After I've installed the venv and packages again, I get the following error when running the mailman command from within the venv: > > SystemError: initialization of _psycopg raised unreported exception > > How do I fix that? The first issue arises because the venv/bin/ directory contains only symlinks to a system python3, and either they broke upon the upgrade or they pointed to what is now Python 3.11 and there was some incompatibility between that python and modules in the venv. Did you install psycopg2-binary as discussed at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… Is the error logged in var/logs/mailman.log? If so, what's the traceback? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Edit archived email? Is it possible?

by Mark Sapiro

On 10/7/21 6:31 AM, Prasanth Nair wrote: > Hi Mark, > > As you know, we can edit the individual messages using the message_id_hash. > Is there any possibility that we can edit the original message > which then updates all of the threads it has (for example, if someone > already replied to the original message)? Or do we need to edit each > message manually? You need to edit each message. A reply which quotes some or all of another message contains that quoted text as opposed to some reference to the text in the original message. Thus, editing the text in the original message has no effect on quoted text in the reply. -- 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: Removing Moderators

by Mark Sapiro

On 7/20/24 1:27 PM, steve.bachinsky(a)tena-sda.org wrote: > > If I know the moderator's email address, is there a way to do this in a python function? Something like ``` import os import sys from mailman.core import initialize from mailman.database.transaction import transaction from mailman.interfaces.listmanager import IListManager from zope.component import getUtility os.environ['MAILMAN_CONFIG_FILE'] = '/path/to/mailman.cfg' initialize.initialize() def delete_moderator(list_id, email): mlist = getUtility(IListManager).get_by_list_id(list_id) if not mlist: print(f'No such list {list_id}', file = sys.stderr) sys.exit(1) with transaction(): moderator = mlist.moderators.get_member(email) if moderator: moderator.unsubscribe() else: print(f'No such moderator {email}', file = sys.stderr) sys.exit(1) if __name__ == '__main__': delete_moderator('list.example.comg', 'user(a)example.com') ``` -- 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: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

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…> <#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

4 years, 9 months

[MM3-users] Re: Mailman3 command line issue: NameError: name 'cli' is not defined when executing command=cli

by Mark Sapiro

On 5/13/20 7:10 AM, John W wrote: > Hi, I am following the guide here: https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/create.h… > and am falling at the first hurdle. > > command = cli('mailman.commands.cli_lists.create') > NameError: name 'cli' is not defined. In order to run the doctest snippets, you need to import the helpers. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…>. However, If all you want to do is create a list just run the `mailman create` command directly instead of trying to run the snippets in `mailman shell`. -- 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: New releases

by Danil Smirnov

The issue has confirmed by other users: https://github.com/maxking/docker-mailman/issues/382 вт, 9 июн. 2020 г., 20:49 Mark Sapiro <mark(a)msapiro.net>: > On 6/9/20 10:31 AM, Danil Smirnov wrote: > > On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >>> COMPRESS_OFFLINE = True > >>> COMPRESS_ENABLED = True > >> > > > > These two are commented out. > > > Then compress shouldn't be trying to do anything. I can't explain what's > going on. > > -- > 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/ >

5 years, 1 month

[MM3-users] Re: Moderated Signup with "info" box?

by Brian Carpenter

On 12/7/20 10:13 PM, Mark Sapiro wrote: > On 12/7/20 8:01 AM, Brian Carpenter wrote: >> Keep in mind that Mailman 3's REST API is only accessible locally. So to >> access Mailman 3's REST API from another server is not remotely >> possible. (see what I did there?) > > The REST API is only accessible locally by default. It is certainly > possible to configure the webservice section of mailman.cfg to be able > to access it remotely - if you do this, be sure not to use the default > admin_pass. There is also an authenticating REST proxy project called > lemme (possibly abandoned) at <https://gitlab.com/mailman/lemme>. Thank you for the clarification. I did not know that. Is that made clear in the documentation? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Re: Sanity check of upgrade procedure

by David Newman

On 10/26/22 6:14 PM, Mark Sapiro wrote: > >> Attempting uninstall: mailman-web >> Found existing installation: mailman-web 0.0.6.dev9+gc606169 >> Uninstalling mailman-web-0.0.6.dev9+gc606169: >> Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 >> ERROR: Could not install packages due to an OSError: [Errno 13] >> Permission denied: 'WHEEL' >> Check the permissions. >> >> The command also said I needed to upgrade pip. Doing that produced a >> similar error. >> >> How to resolve this error? Thanks again. > > Was the venv initially created as the `mailman` user? Maybe > > sudo chown mailman:mailman /path/to/venv > > will fix it. Yup, that was it. Some Django directories were owned by root. The installation ran clean after running 'chown -R mailman:mailman' on those directories. Thanks! dn

2 years, 9 months

[MM3-users] Re: Problems after Upgrade

by Mark Sapiro

On 10/30/22 17:37, Jeff Steele wrote: > Thanks Mark, > > I was able to fix this problem easily by modifying: > > mailman3/lib/python3.8/site-packages/compressor/management/commands/compress.py > > to change the line: > > Command.requires_system_checks = None > > to > > Command.requires_system_checks = [] > > Now, bin/mailman-web compress runs but outputs: > > CommandError: Compressor is disabled. Set the COMPRESS_ENABLED setting or use --force to override. > > which I guess is fine. If you want to do off line compression which is a good thing, you need to set ``` COMPRESS_ENABLED = True ``` in your Django settings. I recently added this and also a note about CSRF_TRUSTED_ORIGINS to https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… -- 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: mailman3 not working for mailman21 lists

by Odhiambo Washington

On Mon, Aug 22, 2022 at 7:04 AM <blup(a)fortytwo.ch> wrote: > I installed mailman3 on a server where mailman21 was installed before. > Newly created mailinglists work fine. But if I create mailinglists with a > name that was previously used on mailman21 nothing works (same behaviour > with and without import of old configs and archives; no logs). I purged all > old mailman21 config and data and also old postfix aliases (or at least I > do think so). > I recently installed (and got it working! Yayi!) MM3 on a server that had MM21. A few things are still fresh in my mind. But I use Exim as the MTA, not Postfix. If I send a mail to old list list1(a)a.b and new list list2(a)a.b I get the > following logs > > /var/log/mail.log > Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list2(a)c.a.b>, > orig_to=<list2(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, > delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) > Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list1(a)c.a.b>, > orig_to=<list1(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, > delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) > > /var/log/mailman3/smtp.log > ug 21 22:17:40 2022 (934) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Aug 21 22:17:40 2022 (934) Peer: ('127.0.0.1', 44746) > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) handling connection > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'LHLO c.a.b' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'MAIL FROM:<....>' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) sender: .... > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT > TO:<list2(a)c.a.b>' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list2(a)c.a.b > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT > TO:<list1(a)c.a.b>' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list1(a)c.a.b > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'DATA' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'QUIT' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) connection lost > Aug 21 22:17:40 2022 (934) Connection lost during _handle_client() > Aug 21 22:17:46 2022 (936) <166111306097.933.1775779871266718007@...> > smtp to list2(a)a.b for 1 recips, completed in 3.1437485218048096 seconds > > How can I get more info on why the mail for list1 isn't processed? > Where could old mailman21 or postfix info on list1 be stored that causes > mailman3 to not handle the list properly? > How can I diff the config between list1 and list2 from the command line? > In Exim parlance, we usually talk about "routers" and "transports". Routers decide who the mail belongs to and hands the mail to a transport for delivery. In a server where you are running MM3 and MM21, you really need to let ML mails to be processed _first_ by a "router" handling MM3. I don't know so well how you do that on Postfix. It might be possible that rules for MM21 are still being applied in your Postfix config. I used the following HOWTO - https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 - for my setup. There is a section that talks about Postfix which you can refer to. However, the whole shebang is here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: Auth question

by Mark Sapiro

On 1/3/19 11:00 AM, kelly.close(a)lrewater.com wrote: > Hi David, > > Did you ever find a resolution to these Authorization errors? I'm experiencing the same problem in a new setup. Would love to know if you figured it out! The code that produces that error is: if request.GET.get("key") != settings.MAILMAN_ARCHIVER_KEY: return HttpResponse( """<html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html>""", content_type="text/html", status=401) I.e., the key in the request which comes from the [general] api_key: setting doesn't match the key set as MAILMAN_ARCHIVER_KEY. Do you have quotes around the api_key setting? That would be a mistake. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] digest summary heavily cluttered with hrml code

by Mohsen Masoudfar

Hi, I am running Mailman 3.1.1 on Ubuntu 18.04. The user complains that the digest summary is cluttered with HTML code. I thought, I may fix it by: Members > {user} > Member options > Delivery mode set to [Plain Text Digest]. After setting the value and clicking [save changes], I tried to check the value by getting back to Members setting for the user, it shows the value as "Regular", which was the value before I tried to update it. Question 1: How may I be sure that the value is set, if it is set? Question 2: How may set it for all members of the list? Question 3: Is there a CLI way to do this? I tried "mailman members " command. But it seems not supporting this option. Any help is much appreciated. Thanks Mohsen

4 years, 9 months

[MM3-users] Recently active discussions - Hyperkitty

by Sam Darwin

Hi, Sometimes not sure if it's preferable to open a gitlab issue, or chat on the mailing list. I have run a large archive import into mailman3/hyperkitty. After that's done, waited a day, for scheduled cron jobs to complete. In "All Threads", all the email archives are present. The import worked. In "RECENTLY ACTIVE DISCUSSIONS" on the main page, it says: RECENTLY ACTIVE DISCUSSIONS No discussions this month (yet). Nothing there. That means if I direct users to visit the site, the page, it appears empty. That's too bad. :-) It should display recent emails. What would affect this feature during an archive import? Is it a problem with the import script itself, or with a scheduled cron job, or something else? Would you expect "Recently active discussions" be empty when very recent archives do exist? Thanks, Sam

1 year, 2 months

[MM3-users] Re: Mailman appears to send an email to a closed list, from a member who was removed from that list

by Jeremy Stanley

On 2025-07-18 20:52:07 -0000 (-0000), Andy Matthews wrote: > I determined that while there's still an "extra" email being > landing in my text inbox, it is NOT going to the mailing list > because it does not have the list name prefixed to the subject. If your mail client is capable of being set to show you the recipient addresses for the message, check those. I'll wager the person did a reply-to-all and ended up sending separate copies to the list address (which was rejected) and directly to your own address as well (which you received). Not much mailman can do about that. -- Jeremy Stanley

2 weeks

[MM3-users]Re: Installation issues

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

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

9 years, 3 months

Search results for query "dO"