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

[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

5 months, 3 weeks

[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

2 months, 3 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, 2 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, 1 month

[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, 2 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

[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

4 years, 8 months

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

by Stephen J. Turnbull

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

3 years, 10 months

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

1 week, 3 days

[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, 3 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

3 years, 9 months

[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, 5 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, 2 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

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

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

by bob B

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

3 years, 7 months

[MM3-users] Re: 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, 6 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)

5 years, 9 months

[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

2 years, 9 months

[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, 1 month

[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, 5 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

[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

6 months, 4 weeks

[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

1 week

[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, 1 month

[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, 2 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, 1 month

[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

2 years, 9 months

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

1 year, 10 months

[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

5 years, 10 months

[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

5 years, 10 months

[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

4 years, 8 months

[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, 3 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, 4 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

[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, 3 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

[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

3 months, 1 week

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

[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, 7 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, 5 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

2 years, 9 months

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

[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, 7 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.

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

1 month, 2 weeks

[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, 2 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, 5 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, 3 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, 3 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, 4 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

2 years, 9 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, 4 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, 5 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???

3 years, 8 months

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

[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, 1 month

[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, 5 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

7 years, 10 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, 5 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, 6 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, 5 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

4 years, 8 months

[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, 6 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, 5 months

[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, 2 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)

6 years, 9 months

[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

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

5 months, 2 weeks

[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

1 year, 11 months

[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, 3 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, 5 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, 2 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, 2 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

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

8 years, 10 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

7 years, 8 months

[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, 7 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, 7 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, 4 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, 3 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, 7 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, 3 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, 6 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

2 years, 11 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, 2 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]

5 months, 1 week

[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/

4 years, 10 months

[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

3 years, 11 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, 8 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, 8 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, 1 month

[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

4 years, 11 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, 6 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, 1 month

[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

[MM3-users] Re: List invisible to moderator

by Mark Sapiro

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

4 years, 10 months

[MM3-users] Re: 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, 4 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, 4 months

[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, 3 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, 2 months

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

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

1 year, 11 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, 6 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

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

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

4 years, 9 months

[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, 4 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, 5 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, 5 months

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

by Abhilash Raj

Apologies for the top-post in advance. So, I am still catching up to this and I don’t very well understand apache2 config, so I’ll try to briefly describe what the setup should be and perhaps it can be translated into apache2 config. Since this thread is mostly about Web stuff, I am not going to talk about mail setup, but replacing `web server` with `mta` and appropriate port changes are the only major differences in mail setup. Postorius (using Django library/web framework) speaks WSGI and can be run using a WSGI Server. There are multiple options for choosing a WSGI server like uwsgi, gunicorn etc. There are also some common web server plugins like mod_wsgi, which are essentially WSGI servers implemented as Apache2 plugin. Web server reverse proxies the WSGI server which runs Postorius/Hyperkitty. You want WSGI Server to be configured to listen on either a socket or a port and then also configure web server to reverse proxy the socket or port. *Ideally* you want to terminate TLS/SSL at the web server level and proxy the HTTP request to the local WSGI server. You don’t need to do anything special for Mailman for SSL if you do this, just follow the regular Web server documentation for SSL for any domains you are supporting in Mailman. If you don’t want to terminate TLS at web server and instead want it down to the last step, WSGI server itself, then the setup is something we don’t have any docs for at the moment but if you go to the respective WSGI server’s docs, I think you’ll find some. uwsgi is a WSGI server implementation, but it is a lot more than that, resulting in a bit more complicated configuration and issues, even though it is stable. The documentation for it exists, but it can be hard to parse if you don’t know a lot about WSGI stuff. A few notable things about uWSGI that Mailman documentation uses are, (1) Ability to manage a daemon process like systemd and (2) ability to speak a new custom protocol called uWSGI with Web Server instead of HTTP that most other WSGI servers use to talk to Web Servers. (1): This is specified as a part of the the “attach-daemon” configuration in the uwsgi.ini file. For Mailman, we use # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster Which will essentially start `mailman-web qcluster` command which starts and a daemon and manage that daemon. Putting it in the uWSGI makes it easy to manage the lifecycle of this and the WSGI server together. If you were using something else like gunicorn, this would be a separate systemd service which you’d start/stop along with mailman-web. (2): This is *probably* what is causing the issue for you from what I can gather in this thread, but I am not sure. Web Server <—> uWSGI communication can be either HTTP or (named exactly same as the package name itself, which causes confusion I suppose) uWSGI protocol. Depending on how you configure uWSGI, you want to update your web server configuration to talk the same protocol. ``` uwsgi-socket = /run/mailman3-web/uwsgi.sock or uwsgi-socket = 0.0.0.0:8000 ``` is the config to talk uwsgi protocol and you want to configure Web server to Proxy using the same protocol. You can find that in the uwsgi docs here: https://uwsgi-docs.readthedocs.io/en/latest/Apache.html You probably need an apache module to speak uwsgi, the docs should have the details. Notice the URL is uwsgi:// instead of http://. Other way is to configure uWSGI to speak HTTP, which can be done by replacing "uwsgi-socket" by "http-socket” in the uwsgi.ini configuration. This might be the easiest for you to try, do make sure to restart the mailman-web service after making the change in uwsgi.ini. Abhilash > On Aug 16, 2021, at 9:34 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Richard, > > Thanks for the details and the pointer to the full configs. That > makes it possible to take a look, but I can't spend much time on it > until next week. > > I'll see if I can prod Abhilash who is more expert than I on all this > stuff (I just use mod_wsgi), but there's some more urgent (sorry, but > it's security) stuff going on, and his absence speaks for his $DAYJOB, > I guess. > > Richard Rosner writes: >> That is entirely possible @Stephen. You can see the entire apache config a few posts back plus the additions from @Mark and mine from the last post. As I interpret it, apache is reverse proxying to the uwsgi app, now through http instead of the socket. But I have no idea if that's the right way round. I'm not sure is the config file templates for apache, nginx and uwsgi that you get with the Debian packages are added by the Debian team or if they are there any way and just have been modified to the Debian file layout, but I'd guess either way it's not that likely that they wrote it the wrong way around. But I'm not too experienced to be able to translate the nginx config to apache to see if that would result in something different. >> >> Also, while the nginx config is written as a standalone website, the apache config seems to have been written to just create a /mailman3 site under an existing website, while I use it as a standalone site. So it's entirely possible that I missed something when I modified the website from mailman2 to serve mailman3, but then it shouldn't have been able to show the website at the beginning. >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

3 years, 8 months

[MM3-users]Re: Installation issues

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

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

8 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, 3 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, 6 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

10 months, 3 weeks

[MM3-users] Re: Message Sent to A Re-Created List Results In Error

by matthew＠alberti.us

I checked all over the mailman core logs and couldn't find a problem. But then I noticed that the 550 error was coming from dovecot-lmtp. I should rename this thread because the actual problem seems to be unrelated to re-created lists. It seems like the actual problem seems to occur in the following situation: * Using Postfix * Using Dovecot * /etc/postfix/virtual includes addresses with same domain as mailman lists. * An e-mail address subscribed to a mailman list is in the /etc/postfix/virtual file as an alias (possibly also if destination address for an alias). * (Possibly related) E-mail address is also one of the list owners. In that environment, Postfix seems to check only 'virtual_transport' list, which in my case is dovecot-lmtp, and when it doesn't find the mailman listname@domain entry in there, it sends a 550 user unknown. It seems to be that it isn't getting passed to 'transport_maps', which is mailman-lmtp. When I remove that one address (that is in /etc/postfix/virtual) from the list of subscribers, I'm able to post again. Interestingly enough, when I put it back in as a subscriber. I'm still able to post. So it seems unsubscribing and re-subscribing that address fixed it, or adding an additional list owner and deleting it fixed it, or some combination of those. I know this might be shaping up to be a very unlikely scenario. But basically the account is mine, an admin, doing testing before/after a deployment.. I'll try to create a few test procedures to document the method to reproduce the problem, and also hopefully fix it. If I can do that, I'll open another thread. This could also be a postfix config error of some kind, which is definitely possible if not likely. Thanks for reading. - Matt Alberti -----Original Message----- From: Abhilash Raj <maxking(a)asynchronous.in> Sent: Monday, December 14, 2020 11:42 PM To: matthew(a)alberti.us; Mailman users <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us <mailto:matthew@alberti.us> wrote: > I created a list in the Postorius interface, used it, and then deleted > it. A week or so later, I re-created the list, and things were fine > thru the creation and subscription process. But when I sent a message > to the list, a > "550 user unknown" error was sent back. Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs. > > > I tried to determine if this is a known issue by searching the issues > in Gitlab; but didn't find anything. But wanted to ask if this was a > known issue or not? I personally don't remember seeing such an issue, but Mark or others might know. > > > > Thanks. > > > > - Matt Alberti > > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking) _______________________________________________ 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, 4 months

[MM3-users] Re: Confirm on mass subscription

by Mark Sapiro

On 7/5/17 1:48 PM, David Krantz wrote: > > Is there a way of requiring all mass subscribed users to confirm their > email adress? I have an use case where we have a current mail list but > when moving it to mailman I for different reasons would like to > confirm all subscribers. Some very shallow testing suggests that if I > just add them using mass subscribe, they will not have to confirm at > all. > > I have yet to upgrade to 3.1 but I will do so in due time. In MM 2.1, you just send the users invitations rather than subscribing them. In MM3/Postorius, this does not seem to be an option at present. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Apache Conf

by Mark Sapiro

On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > Hi, > Currently, I use a nginx configuration for mailman. It's work perfectly. > > I tried to do the same with Apache, but the statics files are not > delivered (404). ... > <VirtualHost *:80> > ServerName mailing.ddd.fr > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > <Location /static/> > Alias "/opt/mailman/static/" > </Location> > > <Location /> > ProxyPass http://localhost:8000/ > ProxyPassReverse http://localhost:8000/ > ProxyPreserveHost On > </Location> > </VirtualHost>/ In Apache, location <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not appropriate for resources in the file system. Try Alias /static/ /opt/mailman/static/ not within a location block. -- 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] Gmail emails bouncing - anybody seen this problem?

by worik

Friends On a fresh install (docker) on a fresh VPS I am getting all Mailman messages to Gmail addresses bouncing telling me I am sending too many messages. Has anybody else have this problem? I am getting the following error in mail.log: "Our system has detected an unusual rate of 550-5.7.1 unsolicited mail originating from your IP address. To protect our 550-5.7.1 users from spam, mail sent from your IP address has been blocked. 550-5.7.1 Please visit 550-5.7.1 https://support.google.com/mail/?p=UnsolicitedIPError to review our 550 5.7.1 Bulk Email Senders Guidelines. l26si395949wme.8 - gsmtp" I have been to the URL mentioned and exhausted my options there. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 2 months

[MM3-users] Re: Trouble in Debian11 after import mailman2 archive

by Mark Sapiro

On 5/25/22 03:21, qro(a)xs4all.nl wrote: > > Question: > Where do I have to look/make changes so I can import the old archive and > can send email to it? You are not looking at the relevant logs. In the first case, mail is delivered to Mailman, but then something happens to it before it is archived and delivered. Look in /var/log/mailman3/mailman.log and wherever Mailman's qfiles are in the Debian install. Assuming the message is not held for moderation, rejected or discarded due to list settings, it is probably queued in Mailman's `shunt` queue, and if so, there will be an exception and traceback logged in mailman.log. -- 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: Retrieve users from a list

by Jered Floyd

Yow! Do you happen to have a recent database backup? (See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…) Every time I look at the UI and see "Remove ALL members" next to "Remove Selected", a chill runs down my spine. I should probably go hide that button with some custom CSS right now. You have my sympathy. --Jered ----- On Feb 6, 2024, at 9:40 AM, pau baiges pau.baiges(a)csuc.cat wrote: > A moderator has deleted all the users from a list, is there a way to recover > them? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

1 year, 2 months

[MM3-users] Where to find disabled members?

by Bill Oliver

Now that I have mailman running smoothly, I'm having to deal with a few other issues. When I changed vendors for my vps, my vendor gave me a static IP address that was apparently run by Satan himself. The ip address is -- or was -- on a number of blacklists. I have spent the past couple of weeks going through various appeals processes to get whitelisted, and I think I'm in good shape. In the meantime, a fair number of subscribers have been disabled. When I look at Postorius -> Settings -> Bounce processing, I see all of the policies I can play with, but I don't see how to a) See who is disabled, and b) un-disable them by hand or... do I just have to wait seven days for them to automatically get un-disabled? Thanks! billo

5 months, 2 weeks

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

by Fabian A. Santiago

On October 25, 2017 9:17:33 PM EDT, "Fabian A. Santiago" <fsantiago(a)garbage-juice.com> wrote: >On October 25, 2017 9:13:20 PM EDT, Mark Sapiro <mark(a)msapiro.net> >wrote: >>On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: >>> >>> No to the domains part and I think virtual alias maps is needed: >>> >>> mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx >>in BOTH virtual_mailbox_domains and relay_domains >>> Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not >>list domain xxx in BOTH virtual_mailbox_domains and relay_domains >>> Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: >>reject: RCPT from >>pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 >><test123@xxx>: Recipient address rejected: User unknown in virtual >>mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP >>helo=<[10.0.0.29]> >> >>(above slightly sanitized for return to the list) >> >>The issue here is your list domain cannot be a virtual_mailbox_domain >>or >>a virtual_alias_domain. >> >>I have the same issue on mail.python.org where we have both Mailman 2 >>and Mailman 3 lists @python.org. and python.org is a >>virtual_alias_domain. >> >>I have a group of MRs for a branch that implements "alias_domains" to >>deal with this. >> >>Basically it works by creating another (virtual_alias_maps) >>postfix_vmap >>mapping to map list addresses @python.org to addresses @x.python.org. >>Then the postfix_domains and postfix_lmtp maps have the x.python.org >>domain and there is a patch to mailman/runners/lmtp.py to map the >>x.python.org domain back to python.org. >> >>The various MRs are >><https://gitlab.com/mailman/mailman/merge_requests/202> for the core, >><https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the >>REST bindings used by Postorius and >><https://gitlab.com/mailman/postorius/merge_requests/186> to be able >to >>set an alias_domain via Postorius. >> >>That's not all implemented at mail.python.org. What's there is the >>basic >>Postfix config, a bash script the generate the new mappings from the >>old >>and a simple patch to mailman/runners/lmtp.py. >> >>So, the bottom line is it can be done and it's in process, but it >won't >>really be supported until Mailman 3.2. In the mean time, you just need >>to have a separate domain for your lists that isn't a >virtual_*_domain. > >Ok thanks. At least I have a clear answer now. Any ETA on 3.2 in mind >yet? >-- > >Thanks, > >Fabian S. > >OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC >_______________________________________________ >Mailman-users mailing list >mailman-users(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Mark, Ok I have it almost perfectly working now having taken your direction and configuring a unique domain not in my email system already. 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. 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 Thanks. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

7 years, 5 months

[MM3-users] Mailman List Lost on URL transfer

by heartsandbones＠zoho.com

Hello Mailman Forum! I hope you all can help me. I have been banging my head against this issue for weeks. Here’s the scoop: I did a web site redesign for a non-profit. They didn’t mention to me that they had a mailman list associated with the site. When we transferred the url to Squarespace their list quakers(a)sbfriends.org stopped functioning and the administration login link: http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org results in a “server not found” error. I don’t know how to set up the site so that their mailman list works again. Please tell me exactly what to do to make this work. Let me know if I can provide any additional information to help you help me. This is my first post to this forum, so I hope I’ve done so correctly. Thanks so much! Licity

7 years, 7 months

[MM3-users] Re: clone a list?

by Dave McGuire

On 1/17/22 4:16 PM, Mark Sapiro wrote: >> Hi folks. Is there a way to clone or duplicate a list in MM3, i.e. >> create a list with a different name but other settings etc being >> identical? > > The short answer is not yet. > > Would you also want to clone the list membership? If not, you could > possibly do something directly with the database mailinglist table by > adding a new row with all the column values other than id, list_name and > list_id equal to those of the existing list. No, different membership. No problem, I'm just being lazy about it; I'll just duplicate it and copy the settings over manually. I only have two clones to make so it's really not a big deal. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

3 years, 3 months

[MM3-users] Re: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/23/24 13:23, Gerald Vogt wrote: > > I don't quite understand the relevance of the user accessing the > localhost tcp port. Any local user can do that. I am trying to duplicate what Mailman does in an attempt to find the issue. > I can access the template content with > > curl > http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… > > as well as > > curl > http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… > > as any user on the mailman server. How about ``` curl -A 'python-requests/2.32.3' http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… ``` as the Mailman user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Mailman 3.2.0 Hyperkitty fulltext index error

by Marvin Gülker

Hi, Am 12. Juli 2018 um 08:14 Uhr -0700 schrieb Mark Sapiro: > This is due the the change from Python 2.7 to Python 3. The existing > search index is not compatible with Python 3 whoosh. Ah, I see. > I fixed this by deleting all the files in the index directory which is > defined as PATH in HAYSTACK_CONNECTIONS in your settings and running > 'django_admin update_index', but just running 'django_admin > rebuild_index' should do it. I simply followed your first suggestion, and it worked. I deleted all files in the index directory (which was "fulltext_index" in the "mailman-suite_project" directory, as we use https://gitlab.com/mailman/mailman-suite/tree/master/mailman-suite_project) and then ran update_index. That took a while, but succeeded. Since then the errors are gone. Thank you! Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

6 years, 9 months

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 14/02/19 1:08 PM, Mark Sapiro wrote: > Presumably this is list mail so your list copy should be the same except > for the few headers related to delivery from Mailman to you. Nope. I cannot send *any* emails to a gmail address. So it is the first "Welcome to the list" email. As far as I can tell there is no solution to the problem, which is why I ask is any one else having this problem? Am I incredibly unlucky or is this a known problem? I have a SPF record. I have tried a new VPS on a different IP address. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 2 months

[MM3-users] Re: mailman3 OWNERS_CAN_ENABLE_PERSONALIZATION option

by Henry S

Thanks Mark. That's exactly what I am looking for. On 3/12/2020 1:09 pm, Mark Sapiro wrote: > 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. > >

4 years, 4 months

[MM3-users] Delete user

by Rainer Herbst

Hi *! Recently, I have updated my docker images to 0.4.2 and it worked great. In the Postorius GUI, I see a new topic "Users" and found it quite comfortable. But one problem remais open - how can I delete a user alltogether, i.e. including his subscription and account data from the database? The reason for this question are the GDPR regulations - we do subscribe new staff members to some lists automatically, and should unsubscribe them and delete the entries after they left our organization. Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years, 1 month

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

by Stephen J. Turnbull

Brian Carpenter writes: Thank you for going to the trouble of making your guide easily available to and usable by the community. > On 2/25/21 8:28 PM, Abhilash Raj wrote: > > 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 Yes, and we try to document them all, written by different people at different times. I don't think that's an unreasonable approach given the wide variety of situations of our site admins, but I'm sure a lot of "greenfield" installations will appreciate your thorough, "from parts manifest to assembled working system", approach. > My guide represents a very stable and easily maintained environment > for me and hopefully others. I'm pretty sure that there are quite a few folks with very similar installations. > Is there an official guide? See that is the problem. Yes, it has been a problem. At this point I'm pretty sure :^þ that mailman.readthedocs.io is the official guide, but that hasn't been well-known in the past and there are a lot of mirrors and unofficial guides like yours (but not as thorough). And there's a lot of stuff on the Wiki that requires effort to integrate because it was originally written in reply to a particular user's questions. > 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. > > Is it something about the contribution process to the official > > documentation that makes it hard > > Well I don't know much about any of the above approach to > > documentation. So I would say that is a hindrance. Sphinx is pretty much the gold standard for Python documentation. It looks nice. The markup is reStructuredText, which is a powerful, Markup-like language with a few features that Markup didn't have last I looked, and it's extensible by Python programmers. It's also used in marking up Python docstrings. So you can see why we'd choose it. But if you're *not* an experienced Python programmer, none of those are advantages. > > 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. @Abhilash: For non-Python programmers, it's not *that* hard, but there is a hurdle at the beginning. I think the best thing to do is to advertise that we're always looking for doc contributions, and that if somebody's not familiar with reST, they shouldn't let that stop them. Of course we'll help them with markup, and if necessary we'll do it. > The Dart Sass section came from Mark's comments on this list. Now, automatic conversion of Mark's posts to reST documentation is a problem I wish we could get those Red Army AI programmers to work on! Steve

4 years, 1 month

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

by Andrew Hodgson

Abhilash Raj wrote: >Mailman core's entire state is in the var/ directory above. I was working round my own backup strategy a few weeks ago as I discussed earlier on this list. One thing I found when the directory structure that Mailman Core uses is that the lists directories do not get re-created when Mailman Core starts if they don't already exist. Is this something that should happen, and when would those directories get created? Every other directory did get re-created. In my case I was moving from a Dockerised installation to one using venvs, and as the directories from the Docker installation were empty as there hadn't been any postings for a few days, I didn't transfer those over. I created the list directories myself and everything carried on. Thanks. Andrew.

5 years

[MM3-users] Re: Error after upgrading mailman3

by Gelpi Andrea

Il 04/05/20 17:44, Abhilash Raj ha scritto: > This is a known and fixed issue in the newer releases of Mailman, I am unable to find the original issue though. The issue is that you need to upgrade dependency on falcon to be >=1.4.0. > > Since this is a Debian package, you may want to contact Debian packaging team for this issue. Thank You. The debian package is python3-falcon. To upgrade to V 1.4.1 I also need to move to pyton 3.8. I read here some problems exists with that version. For now I revert to mailman 3.2.1 By the way do you know which mailman version introduce the command mailman notify? Thank You -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

4 years, 11 months

[MM3-users] Re: Imported Digest Settings

by Brian Carpenter

On 2/16/21 5:21 PM, Mark Sapiro wrote: > Depends what the issue is. The two most obvious approaches are upgrade > to Mailman 3.3.3 if you aren't already there and switch from plain to > MIME digests, but I would really like to see the full raw source of this > digest messages to try to see if there is some other issue. > > >> What I did: I had the client change the list member's digest setting >> from plain-text to mime. Was that the right instruction to do? > It will probably help, but if this is Mailman 3.3.3, there's still a bug > somewhere that needs to be diagnosed and fixed. Hi Mark, The beginning of my OP stated I was using Mailman 3.3.3. Remember to use your reading glasses old man! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] what process creates webui tables (mailmanweb db)?

by tflatley＠gmail.com

hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate - this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file python3 manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? Thanks

2 years, 6 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 16:54, mark(a)suburbia.org.au wrote: > Once again, thanks for taking time to reply. > > Mark Sapiro wrote: >> On 11/18/24 04:12, mark(a)suburbia.org.au wrote: >> This should not happen. In the message as delivered to the list what do >> you see in the X-Mailman-Rule-Misses: header and the >> X-Mailman-Rule-Hits: header if any? > > ``` > X-Mailman-Version: 3.3.8 > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address > X-Mailman-Rule-Hits: member-moderation This says it was held for moderation. Is there an X-Mailman-Approved-At: header which would say it was approved by a moderator? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by nate

On 2022-01-25 6:56, Stephen J. Turnbull wrote: > nate writes: > > > It's "just worked" over the years, no issues. I have been using > > Linux since 1996, not a newbie here. > > If so, and you're familiar with Docker (obviously not the same thing, > but maybe? ;-), you might find the containerized version provided by > Abhilash (which is usually quite up to date) closer to a turnkey > installation. I use the venv approach myself (more because developer > than out of principle), so I'm not really familiar with the container > distribution, but from traffic on the list I get the impression that > most of the troubles have to do with networking in containers, rather > than configuring Django and WSGI hosts. That is an interesting idea. I'm not much into docker but I certainly could do a LXC container or just another VM to run the older mailman and just not update it? My mailing lists are probably less than 1 message a month on average so real low usage. > I appreciate the detailed description of what you did and didn't find > in the docs. The docs are weak on administration, we admit, and we we > get some of those round tuits .... Sure thing, I tried hard to be as polite as I could don't want to offend anyone with their hard work. > It's been years since we had an answer to that question. Mark might > have more to say, but the last time we were challenged on this, the > rival was Sympa, and the conclusion I came to was that the use cases > are different. I'll take a look at that thanks. I'd like to stick to mailman if I can though bypassing the distribution as was suggested to me to get a better version does worry me a bit from a maintainability standpoint, I try to keep things as clean as I can, and holy crap I was shocked at the number of dependencies the mailman3-full package pulled in(165 total packages that were not already installed, most were python3 related). So bypassing that entirely does worry me a little, not that I run anything mission critical on my home server but my home server(that runs in a colo, so not really at home, I have 30 systems on my home network/colo network) historically is super low maintenance. An extreme case I came across last year I discovered I was still using 2 RBLs in postfix that were shut down between 7 and 12 years ago! That just generated warnings in the postfix logs over the years but I wasn't paying attention(never hurt anything). Till I looked up the RBLs to see..wow, gone for that long, so I updated my postfix config! My postfix configs date back to ~2003 and have had minimal changes over the years, same goes for the rest of my mail system whether it was mailman, or Cyrus IMAP (barring a one time painful migration from Cyrus 1.x to 2.x). > Depending on your Linux distro, and your attitude to risk, Python 2 > plus Mailman 2 in a container, VM, or even a dedicated host in the DMZ > or outside the firewall might be a reasonable solution. I will certainly consider that as an option, thanks!! Devuan 3.x still has mailman 2.1.29, in theory I could hack together a 2.1.39 Debian package to get it up to date in that respect. nate

3 years, 2 months

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

by Henrik Rasmussen

Henrik Rasmussen wrote: > Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. > When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. It seems that I was right, however, I need to re-enable all members on a single list who have been disabled due to bounces. Using the `mailman members` command it is possible to list such members, however how do I enable them using either the `mailman shell` command (available) og the mailmanclient (needs first to be installed in the docker container)? Regards, Henrik Rasmussen

3 years, 3 months

[MM3-users] Mailman3 is wrongly display name a list member

by Allan Hansen

All, I got an issue with one subscriber (multiple lists). When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' <a(a)foo.com>. I went into Django and added the name 'B' to the subscriber's account (the name was empty). I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' <a(a)foo.com>. The subscription again lists as 'B' <a(a)foo.com>. This brings up a previous discussion of display names on this list, but I have not been able to find any solution to the need to change Mailman3's display names for a subscriber. It is beyond weird that unsubscribing, setting the account display name and resubscribing the member fishes back up the old and wrong display name. What can I do to help this member? Yours, Allan

3 years, 3 months

[MM3-users] Dealing with email bounces from web signups

by Andrew Hodgson

Hi. Back on the topic of bogus web signups again. I am dealing with several hundreds of these per month and we're talking a very low traffic system here. I have a cronjob to remove the users from the database. Right now a concern for me is handling the bounces for the confirmation emails that don't get delivered. These are coming from postorius(a)lists.hodgsonfamily.org<mailto:postorius@lists.hodgsonfamily.org> which I have redirected to a mailbox so as not to clutter up the mail queue. What I would ideally like is if we get a bounce from one of these confirmation mails we delete the user from the database but that is probably a future request. We don't get too many of these, around 20-30 a week. What are other people doing with these messages? Thanks. Andrew.

3 years, 1 month

[MM3-users] Re: Intermittent: pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77

by Danil Smirnov

Hi, This is most probably to be fixed in the next core release via https://gitlab.com/mailman/mailman/-/merge_requests/864 It seems the same issue I've filed for PostgreSQL: https://gitlab.com/mailman/mailman/-/issues/854 You can apply the patch for now and help with its testing. BR, Danil пн, 24 мая 2021 г., 11:25 Torge Riedel <torgeriedel(a)gmx.de>: > |Hi list, sometimes I get the following error in mailman core's log: > "pymysql.err.InternalError: Packet sequence number wrong - got 102 expected > 77". I attached the full log after this mail. I check the provided link in > the log (|||http://sqlalche.me/e/2j85|) and also searched for it on the > internet and found the following possible reasons: 1. DB user does not have > permissions at all -> I doubt that, because in general mailman is working > ok 2. DB user is not allowed to connect from remote -> I doubt that too, > because everything is on one host and DB user is allowed to connect from > localhost 3. Multi-Threading -> pymysql is mentioned to be not thread-safe > and each thread needs its own connection May this be caused by > multi-threading? What do I have to do (is there anything I can do?) to > solve this on my own?||||| > > Kind regards > Torge > > || > > |Full log follows: [2021-05-23 07:31:45 +0200] [8244] [ERROR] Error > handling request /3.1/lists?advertised=true&count=10&page=1 Traceback (most > recent call last): File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1284, in _execute_context cursor, statement, parameters, context File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", > line 590, in do_execute cursor.execute(statement, parameters) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", > line 170, in execute result = self._query(query) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", > line 328, in _query conn.query(q) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 517, in query self._affected_rows = > self._read_query_result(unbuffered=unbuffered) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 732, in _read_query_result > result.read() File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1082, in read self._read_result_packet(first_packet) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1151, in _read_result_packet self._get_descriptions() File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1222, in _get_descriptions field = > self.connection._read_packet(FieldDescriptorPacket) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 671, in _read_packet % (packet_number, self._next_seq_id)) > pymysql.err.InternalError: Packet sequence number wrong - got 102 expected > 77 The above exception was the direct cause of the following exception: > Traceback (most recent call last): File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/database/transaction.py", > line 50, in wrapper rtn = function(*args, **kws) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", > line 193, in __call__ return super().__call__(environ, start_response) File > "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", > line 269, in falcon.api.API.__call__ File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/lists.py", > line 322, in on_get resource = self._make_collection(request) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 172, in _make_collection request, self._get_collection(request)) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 167, in _paginate return list_start, total_size, > collection[list_start:list_end] File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/utilities/queries.py", > line 42, in __getitem__ return self._query[index] File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", > line 3149, in __getitem__ return > list(res) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", > line 3481, in __iter__ return self._execute_and_instances(context) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", > line 3506, in _execute_and_instances result = > conn.execute(querycontext.statement, self._params) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1020, in execute return meth(self, multiparams, params) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", > line 298, in _execute_on_connection return > connection._execute_clauseelement(self, multiparams, params) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1139, in _execute_clauseelement distilled_params, File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1324, in _execute_context e, statement, parameters, cursor, context > File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1518, in _handle_dbapi_exception sqlalchemy_exception, > with_traceback=exc_info[2], from_=e File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", > line 178, in raise_ raise exception File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1284, in _execute_context cursor, statement, parameters, context File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", > line 590, in do_execute cursor.execute(statement, parameters) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", > line 170, in execute result = self._query(query) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", > line 328, in _query conn.query(q) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 517, in query self._affected_rows = > self._read_query_result(unbuffered=unbuffered) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 732, in _read_query_result result.read() File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1082, in read self._read_result_packet(first_packet) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1151, in _read_result_packet self._get_descriptions() File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1222, in _get_descriptions field = > self.connection._read_packet(FieldDescriptorPacket) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 671, in _read_packet % (packet_number, self._next_seq_id)) > sqlalchemy.exc.InternalError: (pymysql.err.InternalError) Packet sequence > number wrong - got 102 expected 77 [SQL: SELECT mailinglist.list_id AS > mailinglist_list_id, mailinglist.preferred_language AS > mailinglist_preferred_language, mailingli$ FROM mailinglist WHERE > mailinglist.advertised = true ORDER BY mailinglist.list_id LIMIT > %(param_1)s] [parameters: {'param_1': 10}] (Background on this error at: > http://sqlalche.me/e/2j85) | > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 10 months

[MM3-users] Mailman3 via Docker and NGINX

by brian＠emwd.com

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

6 years, 4 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/26/20 10:13 PM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > But I am having a final query over this issue. Out of the two hyperkitty > records I observed in the database, I am confused which record do I need > to remove directly from the database? Because I doubt still there is one > more list with the same style i.e. with two hyperkitty records. If there are multiple rows in the listarchiver for the same `mailing_list_id` and archiver `name`, you can safely delete all but one of them. It doesn't matter which ones you delete. They should be identical except for the `id`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: moderator cannot login to the list

by Brian Carpenter

On 12/16/20 7:36 AM, Gregory Edigarov via Mailman-users wrote: > GNU Mailman 3.2.1 (La Villa Strangiato) > Python 3.7.3 (default, Jul 25 2020, 13:03:44) > > I've imported some lists from mailman-2.1 > using 'mailman import21' command. > > the import went fine, I am able to login into postorius as admin, and > see all imported mail list data. > but login as a moderator member of a list. I tried to reset moderator > password via rest api. > That doesn't help. > > how is that supposed to be done? > > thank you. Hi Gregory, Are we talking about the same user as the one that is logging in as admin? Or do you have additional moderators that need to be able to login and moderate your lists? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

[MM3-users] Re: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Wikinaut

I could not fix the problem, apparently there is a mismatch somewhere now. sudo pip uninstall django-q Found existing installation: django-q 1.3.9 Uninstalling django-q-1.3.9: Would remove: /usr/local/lib/python3.9/dist-packages/CHANGELOG.md /usr/local/lib/python3.9/dist-packages/django_q-1.3.9.dist-info/* /usr/local/lib/python3.9/dist-packages/django_q/* Proceed (y/n)? n whereas dpkg -l | grep django-q: ii python3-django-q 1.2.1-1 /usr/lib/python3/dist-info: 4 drwxr-xr-x 8 root root 4096 21. Jun 2022 django_q 4 drwxr-xr-x 2 root root 4096 21. Jun 2022 django_q-1.2.1.egg-info sudo apt remove python3-django-q the following packet will be REMOVED: mailman3-full mailman3-web python3-django-hyperkitty python3-django-q Continue [Y/n] n What to do? I don't want to remove mailman3, I just want to bring the 1.2.1-1 to 1.3.9...

1 year, 6 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/26/20 9:12 AM, Odhiambo Washington wrote: > On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 7/26/20 3:15 AM, Odhiambo Washington wrote: >> >>> There is still some confusion on my part about the directives in the file >>> so allow me to seek some clarifications. >>> >>> The following are the contents of a file I have created and placed in my >>> Apache Includes/ directory. >>> I was hoping that with it, I can now access http://lists.my.server/mm3 >> and >>> get the UI. >>> >>> <CUT> >>> >>> # Global section >>> WSGIDaemonProcess mailman-web display-name=mailman-web >>> maximum-requests=1000 umask=0002 user=mailman3 \ >>> group=mailman3 >>> >> python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 >>> \ >>> python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var >>> WSGIRestrictSignal Off >>> >>> <VirtualHost *:80> >>> ServerName lists.my.server >>> ServerAdmin odhiambo(a)gmail.com >>> >>> # (I'm not sure that WSGIRestrictSignal Off is required, but it was in >> the >>> # provided example so I kept it. I also made changes to WSGIDaemonProcess >>> # based on my own mod_wsgi experience elsewhere.) >>> >>> ErrorLog /var/log/myserver-error.log >>> LogLevel debug >>> >>> # This goes in the VirtualHost block for the domain. >>> >>> # Mailman 3 stuff >>> Alias /static "/var/spool/mailman-web/static" *<----- Where is this >>> directory supposed to be and what/who creates it and with what >> permissions?* >> >> >> It is created/updated by the mailman-post-update script based on CONFDIR >> and STATIC_DIR. >> > > The fact that I have run the mailman-post-update script and these > directories aren't created means there is a problem in my setup, yes? If your mailman-post-update script is essentially the same as <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> and it ran successfully, it would have created opt/mailman/mm/static and populated it. What was the output when you ran it? > Yes, I have these files: > (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* > -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 > /opt/mailman/mm/settings.py > -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 > /opt/mailman/mm/settings_local.py Is there an empty /opt/mailman/mm/__init__.py file? > PS: I made my /opt/mailman to be owned by mailman3:wheel because of a > confusion with the instructions at some point in the reading > of some documentation previously (in my previous attempt last year!) and > had noted that in my NOTES. I'll change this once things get clear for me. > Also, the fact that one of the init scripts > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > in your "reflection" page was calling sudo :) It does `sudo -u $USER ...` so that it runs Mailman as the Mailman user as it should. Have you set USER=mailman3 in yours? -- 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] REST API notes

by tlhackque＠yahoo.com

As a beginner with the REST API, I found it necessary to read code and experiment to figure out how to get things done. There are a number of implementation choices that are unusual. There is some documentation in src/mailman/rest/docs. It's oriented toward Python and intermixes the mailman client & REST API, apparently trying to show equivalence. Here are some notes that may help others to avoid repeating my research. They reflect Mailman 3.1. Some reflect issues that I've opened, but I think it's worth knowing how things work today. I attempted to tie together some of pieces that are in the documentation - and note some things that aren't. I may have some things wrong, but this reflects my current understanding. (And client code.) The REST API has a hybrid interface: Requests are made with application/x-www-form-urlencoded POST, PUT, PATCH and delete http requests. Requests are also accepted as parameter strings. The responses are JSON. (This is rather surprising - one would expect JSON requests - and I hope someday they'll be accepted, as the split complicates clients. I suspect this evolved to simplify the initial Web GUI client (Postorious), but it precludes using standard JSON-in/JSON-out client libraries.) Error responses are often misidentified as content-type: application/json, but actually contain a text/plain error message. This isn't universally true; for example the 401 response actually IS JSON. A client has to guess and handle decoding exceptions. The API presents resources hierarchically, rooted at '/'. The top level resources include /users, /lists. /addresses, /domains, /system The next level is a resource id. There is a an id which is stable for the lifetime of an object, and a current name (which can be changed). For example, a list has a name like mylist(a)example.com, and a list_id of mylist.example.com. But if you change the list name, it becomes mynewname(a)example.net, while the list_id remains mylist.example.com. Lists are associated with "domains", which are the "domain part" of the list's address. That is, the part after the @. This is sometimes referred to as the "mail host", but there need not be a real host. Just something on the left side of a DNS MX record. Also, don't confuse the use of "mail host" with that of "SMTP Server", which is how Mailman sends mail. The domain is where Mailman expects to receive it. A fully qualified list name is the list name + domain - e.g. its posting address. One domain can (and usually does) support more than one list. If you delete the domain, all its lists go away too. A domain has to be created before you can create a list with an address in that domain. Resources are created with a POST to their top-level resource. To create a domain, post to /domains with mail_host => the domain, and (optionally) description => a description for the GUI. The response isn't JSON as one would expect. In fact, it's an empty application/json response with a 201 status. To create a list, one POSTs to /lists. This post takes a restricted set of parameters; in the case of a list, just its fqdn_listname, (and an optional style - which isn't well defined). The response isn't JSON as one would expect. The Location header of the response contains a URL of the new list. To configure the list, you have to follow up with a PUT or PATCH to that URL + /config This is where you can set the description, posting policy, etc. It's unrealistic to do a PUT; even if you're cloning another list, there's no programatic way to determine which attributes are writable. PATCH what you know... Members are associated with e-mail addresses - which belong to Users. You create a user by posting to /users with email => the email address, and optionally display_name => the name string. (A user can also be implicitly created by subscribing an e-mail address, but that gets confusing.) The e-mail address is the primary email address for the user. More later. Again, you get a Location header in the response, which you can use to PATCH /preferences to set delivery_status, etc. .These preferences are part of a hierarchy - many have a system default, a list default, the user default, and a subscription to that list value. You can find the User associated with a list by a GET of /addresses/address(a)example.net. This GET returns two URLs: user => the user owning this address, and self_link => the address object. Note also that there are both an email and original_email attribute. The latter preserves case. The former is used internally by Mailman as a resource key, etc. (Though exactly what happens if John(a)example.net and john(a)example.net both subscribe is unclear.) Once a list is configured, you can add members. This requires the list_id - which you don't (officially) have. So you do a GET on the list resource, to get the list_id. Then you can subscribe a member with list_id => (the list id), subscriber => email address. Optionally you can pre_verify/confirm/approve the member and/or add a display_name.. POST to /members. Again, you get a Location header back. You can't specify everything you might like. as a creation attribute. So you may have to PATCH the member to, for example, set the moderation_status. You may also need to PATCH the member /preferences if you want to set list-level delivery status, etc. Consider adding at least an owner when creating a list. One challenge is that almost everything requires multiple REST operations to set up. But REST (by definition) is stateless. So the best you can do is order operations & hope. The mailman client examples refer to transactions (e.g in users.rst, there is 'transaction.commit(); - but REST can't hold state. It does appear that the server uses DB transactions to ensure that any given REST operation is ACID, but the composite operations (e.g. create a list and set it's config) can not be Atomic. This is an architectural flaw in the API. Symbolic names (which are required) for attributes are in the src/mailman/interfaces/(class).py. What you can get/set comes from src/mailman/rest/(class).py.

7 years, 9 months

[MM3-users] Re: Another interesting error...

by Simon Hanna

On 04/23/2018 11:29 PM, Darren Smith wrote: > "It's in Mailman's database in the 'message' table." > > I can see the message table - is there a way to see where it is marked as > "held"? All I'm seeing in that table is id, message_id, message_id_hash, > and path. > > I'm wanting to be able to query for held messages for a given mailing list, > as there are currently over 98,000 entries in the message table. This should be possible using the mailman shell http://mailman.readthedocs.io/en/latest/src/mailman/model/docs/requests.htm… I haven't used the shell extensively and didn't read the whole docs, but it looks like it's the right place to look. If you can't do that using the shell, I'd say it's worth a bug report :-)

7 years

[MM3-users] Re: Python error, debian package, again

by Lars Schimmer

On 11/5/19 6:48 PM, Mark Sapiro wrote: > On 11/5/19 7:04 AM, Lars Schimmer wrote: >> >> Abhilash Raj (maxking) mentionend, it maybe a issue with mailman core >> trying to deliver the message to hyperkitty. >> But how can I remove those broken messages, or twitch hyperkitty to >> accept and discard them? > > > Look in Mailman's var/archives/hyperkitty/spool/ directory. This is > where messages that mailman-hyperkitty can't deliver to hyperkitty are > kept for retry. Yeah, there are some in this folder. Can I simply remove those entries from the spool directory? Or do I need to fiddle with any cmdline tool? 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

5 years, 5 months

[MM3-users] Invalid confirm text

by w.schoener＠alp.dillingen.de

Hi there, I am new to mailman 3, python and django. I try to configure a mailman 3 list. To establish german text, I used the web-admin interface of mm3 in the "templates"-section. I inserted a text for "The message sent to subscribers when a subscription confirmation is required" Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: return the message unchange. When I return the message, I get an answer: Invalid confirm text. My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown. Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. Thank you Wolfgang

4 years, 8 months

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

by Richard Rosner

Abhilash Raj wrote: > is the config to talk uwsgi protocol and you want to configure Web server to Proxy using the same protocol. You can find that in the uwsgi docs here: https://uwsgi-docs.readthedocs.io/en/latest/Apache.html You probably need an apache module to speak uwsgi, the docs should have the details. > Notice the URL is uwsgi:// instead of http://. > Other way is to configure uWSGI to speak HTTP, which can be done by replacing "uwsgi-socket" by "http-socket” in the uwsgi.ini configuration. This might be the easiest for you to try, do make sure to restart the mailman-web service after making the change in uwsgi.ini. Thanks, that already helped quite a bit. The website is now loading again, but unfortunately not much else. The site still shows no Connection to REST API.

3 years, 8 months

[MM3-users] Re: Strange password problem

by Stephen J. Turnbull

Eggert Ehmke via Mailman-users writes: > So for now I use the same password for all logins, and that > works. But is that a good solution? The other option would be to > assign multiple superusers for each domain, but they would still > allow to log in via some other domain. If you own the domains, you can probably set up some sort of trivial website on each that does nothing but admin stuff, with the same database backend. Then you can have different passwords for "admin" and the browser will remember them. Probably more tricky than it's worth. What are you doing that requires admin privileges, but you want to authenticate separately for each domain? I ask because we've always envisioned creating a domain-level administrator role, but until now we've had no demand for it. Steve

1 year, 7 months

[MM3-users] Programmatically modify Thread-Topic *before* message is sent out the door?

by Thomas Ward

We use a custom plugin to do numeric thread stamping, which has been working well in the code system. However, it was discovered by Microsoft that Microsoft Outlook and OWA prioritize the Thread-Topic header over the Subject header, which results in the oddness we've experienced in MS365 clients in testing. During our tasks though a custom handler goes through during the pipeline and modifies the Subject field accordingly, adding a thread tag to it. While this is 'fragile' it does work; the only problem is that Thread-Topic doesn't get altered. Programmatically, how would we alter the Thread-Topic during the handler's processing to prepend the corresponding prefix/tag so that when the message actually goes out the door it is properly sending with the modified Thread-Topic? Thomas

1 year, 4 months

[MM3-users] Re: Unsubscribe from a list

by Odhiambo Washington

On Mon, Mar 24, 2025 at 11:38 AM <pau.baiges(a)csuc.cat> wrote: > Hello, > When a list member sends an email to list-leave@... to unsubscribe from a > list, neither the moderators nor the list owners receive it. Only the > person who sent the email receives a confirmation email. > It depends on the settings you have for the particular list. In the list Settings -> Member Policy -> Un-Subscription Policy, you can choose one of the options: 1. Open 2. Confirm 3. Moderate 4. Confirm then Moderate What those options do is documented below that dropdown box. HTH -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 weeks, 2 days

[MM3-users] Re: restrict sending to owner/moderator

by David Krantz

Hi, I have just tested a variant of this as I got curious: You find the member you want to be able to send emails without moderation, then set Administrative Options to "Accept Immediately (bypass other rules)". That works. I have found no other ways, though. // David On Mon, Sep 18, 2017 at 11:28 AM, <m.dohmen(a)xconnect.de> wrote: > Hello, > > I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. > > Is there a way to do this? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 7 months

[MM3-users] MM3 occasionally chokes (?)

by Dmitry Makovey

In the last couple of month we've observed some odd behavior from MM3 (namely the core) where it seems like email that is about to be sent to a large-ish mailing list (10K users) has been processed yet never gets sent out until we restart the core. I would appreciate any pointers on where to look for the source of the problem. At the moment, since I can't reliably reproduce it I can't really test it nor do I know where to look next time things get stuck. Mailing list in question is high profile thus when event like this happens I have only limited time amount to spend on troubleshooting/digging before I just restart the core (which by the way takes about 45min to fully start... which is another puzzle to solve at later time) -- Sr System and DevOps Engineer SoM IRT

6 years, 1 month

[MM3-users] Re: Strange password problem

by Stephen J. Turnbull

OK, I'm convinced. No promises yet since I'm not sure of the scope of the work, but here's the issue. Once I understand the scope and have some idea of the design I will add GSoC and other tags as appropriate. https://gitlab.com/mailman/mailman/-/issues/1103 Jens Günther writes: > I do have the exact same situation. I would love to have domain owners > be able to create/manage their own lists for their respected Domain. > > One problem I see with giving them site ownership: when creating a new > list, not only that they could pick the wrong domain by accident, they > also see all the other domains present in the installation. That would > be a nogo, tehrefore we have to create the lists for all associations on > our side. > > Kind regards, Jens.

1 year, 6 months

[MM3-users] Re: 500 error on one list

by Mark Sapiro

On 7/13/24 8:35 AM, Seth Seeger wrote: > > Did this one list get corrupted somehow? This is https://gitlab.com/mailman/mailman/-/issues/657 We still don't know the underlying cause. Note that the first script in that issue assumes that the multiple entries are for the mhonarc archiver, but this isn't always true. If you run this database query SELECT * FROM listarchiver WHERE mailing_list_id = (SELECT id from mailinglist WHERE list_id = 'list.example.com'); replacing list.example.com with the list_id of your problem list, you will see there are two entries with the same name. Then do DELETE FROM listarchiver WHERE id = nn; where nn is the id of one of the duplicates, it doesn't matter which. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: Help request, almost got it going, but ....

by Mark Sapiro

On 09/01/2017 04:20 PM, Claus-Justus Heine via Mailman-users wrote: > > The issue seems not to be overly active. I thought -- coming from > Mailman v2 -- that the configuration of acceptable submitters to an > email list (e.g. keep everyone moderated?) would be a central and > prominent and important configuration issue. Seems not to be a central > point. Mmmh. Acceptable aliases corresponds directly to MM 2.1 Privacy options... -> Recipient filters -> acceptable_aliases. It has nothing to do with submitters. It is a list of other addresses that can be in the To: or Cc: of a post to avoid and "implicit destination" hold if the list posting address is not there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: MM3 Docker

by Mark Sapiro

On 1/8/19 10:50 PM, Odhiambo Washington wrote: > Now that has clarified the matter for me. That even when I am logged out, > the scripts do the neccessary > to activate the venv to run things. As mentioned before, a virtualenv is not like a container. It is only a directory that contains among other things a bin/ directory with activate scripts and easy_install, python, pip and wheel commands. When you activate a virtualenv in your shell, all it really does is add a deactivate command, modify the command prompt and insert its bin/ directory at the beginning of its PATH. What this means is whether or not a virtualenv is "active", running a command from the bin/ directory in the virtualenv is using the virtualenv. -- 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: Sanity check of upgrade procedure

by David Newman

On 10/26/22 3:10 PM, Mark Sapiro wrote: > On 10/26/22 11:08, David Newman wrote: >> >> For these new releases, is that mistune step still needed? > > > No. That is one of the issues fixed in HyperKitty 1.3.6 which now > requires mistune>=2.0.0,<3.0 and will work with those versions. OK, thanks. Before getting to mistune, this command, run as mailman in a venv: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi Mailmanclient produced this error: .. 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. dn

2 years, 5 months

[MM3-users] Re: New Installation of MM3 is not archiving

by Mark Sapiro

On 1/30/23 02:57, Onyeibo Oku wrote: > > My new MM3 instance does not seem to be archiving. List subscribers > are currently sending and receiving mails on their subscribed lists. > However, none of the correspondence is showing up at > https://mailing-list-site.tld/archives/. That page shows a listing of > the active mailing-lists with '0 participants' and '0 discussions'. > Whereas, those lists contain mails. > > How do I troubleshoot this? The messages as pickled message objects are probably queued in /opt/mailman/mm/var/archives/hyperkitty/spool/. The first place to look for the reason is in /opt/mailman/mm/var/logs/mailman.log. There might also be info in /opt/mailman/web/logs/mailmanweb.log -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

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

by Odhiambo Washington

On Thu, Nov 14, 2024 at 4:05 AM Arte Chambers <paul.m.robey(a)gmail.com> wrote: > I'm also running into permission errors with Postgres - user does not > have permissions on public schema. I didn't see anything in the docs about > how to grant proper access to these tables. > Off the top of my head, this is what I used to do, but the same issue has been discussed several times on the list. # su -u postgres psql #\c mailman postgres # GRANT ALL ON SCHEMA public to mailman; #\c mailmanweb postgres # GRANT ALL ON SCHEMA public to mailman; -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

5 months, 1 week

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mark Sapiro

On 10/1/20 6:12 PM, Mark Sapiro wrote: > >>>>> m.filter_types = ['application/pdf'] >>>>> commit() >>>>> print(list(m.filter_types)) >> ['application/pdf'] > > > This should allow ONLY the PDF and nothing else, not even the text/* > message body parts. Sorry, my statement above is wrong. That should also remove the pdf, but it's redundant given that 'application/pdf' is not in pass_types. > Actually, what's m.filter_content? I suspect it's False which means > don't do any content filtering. I think this is the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Required permissions for mass operations

by mailman3＠werner.by

Hi, I've Mailman 3.3.3 running with some mailing lists and it works great. Now I'm looking for a configuration option. I'd like to have some users with permission to - moderate lists AND - perform mass operations (add members, delete members) AND - change settings for single members (execute actions in menu point "Users", "Members") It should be impossible to change other list or mailman settings for this users. To give them the moderation permission is quite easy: I add the users to the moderators of the lists. But for the user management I've to add the users to the list owners and then is there no restriction anymore to change the full list configuration. What can I do? I link to a documentation for this would help as well, but I found nothing. Thanks a lot for an answer Torsten

7 months, 1 week

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

by Kareem Zidane

Apologies for that!! Yes, this strace was on the out runner process (pid 17171) and yes, the out runner is running: ``` # ps aux | grep [r]unner=out 82 mailman 1:10 /usr/bin/python3 /usr/bin/runner -C /etc/mailman.cfg --runner=out:0:1 ``` Other lists seem to work fine. Here's what I see in mailman.log, after sending two separate emails to the list: ``` Jun 09 17:36:28 2020 (85) ACCEPT: <CAAQM=w13wB6zM-gkjmUWmL26zFSF2DgNKsX3eFetzjtCVPKmCA(a)mail.gmail.com> Jun 09 17:36:30 2020 (84) HyperKitty archived message <CAAQM=w13wB6zM-gkjmUWmL26zFSF2DgNKsX3eFetzjtCVPKmCA(a)mail.gmail.com> to https://lists.cs50.harvard.edu/hyperkitty/list/ap@lists.cs50.harvard.edu/me… [09/Jun/2020:17:36:30 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu HTTP/1.1" 200 373 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:36:30 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu/config HTTP/1.1" 200 3099 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:36:30 +0000] "GET /3.0/users/kzidane(a)cs50.harvard.edu HTTP/1.1" 200 401 "-" "GNU Mailman REST client v3.3.0" Jun 09 17:36:31 2020 (82) Cannot connect to SMTP server postfix on port 25 [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers.lists.cs50.harvard.edu HTTP/1.1" 200 571 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:58 +0000] "GET /3.1/domains HTTP/1.1" 200 537 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:58 +0000] "GET /3.1/domains/lists.cs50.harvard.edu HTTP/1.1" 200 223 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:58 +0000] "GET /3.1/domains/lists.cs50.yale.edu HTTP/1.1" 200 207 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:58 +0000] "POST /3.0/lists/find HTTP/1.1" 200 478 "-" "GNU Mailman REST client v3.3.0" Jun 09 17:42:05 2020 (85) ACCEPT: <CAC-4VT7LRb7REc39i=a8wRc50hOuB_5mSEN37ozatqp9RGNfVA(a)mail.gmail.com> [09/Jun/2020:17:42:06 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu HTTP/1.1" 200 373 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:42:06 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu/config HTTP/1.1" 200 3099 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:42:06 +0000] "GET /3.0/users/kareemzidane2(a)gmail.com HTTP/1.1" 200 293 "-" "GNU Mailman REST client v3.3.0" Jun 09 17:42:06 2020 (84) HyperKitty archived message <CAC-4VT7LRb7REc39i=a8wRc50hOuB_5mSEN37ozatqp9RGNfVA(a)mail.gmail.com> to https://lists.cs50.harvard.edu/hyperkitty/list/ap@lists.cs50.harvard.edu/me… ``` Doesn't seem there are any errors? I grep'd for errors in mailman.log and this is what I got: ``` FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf' FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf' FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf' FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf' ``` No mention of the /hyperkitty/api/mailman/urls API call in mailman.log but I could confirm with tcpdump that mailman is hitting that and I was able to add some logs to the _get_url function in mailman_hyperkitty plugin and it was being called infinitely. /opt/mailman/var/archives/hyperkitty/spool appears to be empty. And lastly, even though emails to this particular list do not go out, they do get archived. Thank you so much! I appreciate all the help!

4 years, 10 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Mark Sapiro

On 2/27/19 12:38 PM, Danil Smirnov wrote: > Hi Abhilash, > > ср, 27 февр. 2019 г. в 22:21, Abhilash Raj <maxking(a)asynchronous.in>: > >> So, what errors are you looking at in uwsgi*.log? >> > > There are tons of errors like this: > > Unknown command: 'qcluster' > Type 'manage.py help' for usage. > [uwsgi-daemons] respawning "./manage.py qcluster" (uid: 100 gid: 101) > Unknown command: 'qcluster' > Type 'manage.py help' for usage. > [uwsgi-daemons] throttling "./manage.py qcluster" for 26 seconds do you have django-q in INSTALLED_APPS in your Django settings and what is set for Q_CLUSTER? Does the manage.py that's being run here point to the right settings.py? -- 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] Google Summer of Docs

by Terri Oda

On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >Ralph Seichter writes: > > * Mark Sapiro: > > >> > If you post an issue at ><https://gitlab.com/mailman/mailman/issues>, > > > one of our GSOC aspirants may pick it up. > > > > Done, although I wonder if any GSOC participant would want to write > > documentation instead of code... ;-) > >For their actual, Google-supported, project, Google explicitly >excludes documentation. > They do for Google Summer of **Code** but they've just announced Google Summer of **Docs** which sounds really neat and we might want to participate. (It's my personal opinion that our docs have really suffered since I finished my PhD and stopped using them as a warmup exercise when I was procrastinating on writing my thesis. *grin*)

6 years

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

by Mark Dadgar

On Nov 23, 2020, at 7:05 PM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Apollinaris Schöll writes: > >> My suspicion is that some users like to use the “report spam” >> buttons way too much and then end up with a extremely sensitive >> individual spam scoring. > > Interesting hypothesis, though I see no easy way to confirm it except > surveying the users, which probably isn't something one wants to do. Anecdotally, I believe this to be true as well. I also believe that it’s common for unsophisticated users to just start marking list emails as spam stop seeing them instead of figuring out how to unsubscribe. Which really sucks for everyone else. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 5 months

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

by Brian Carpenter

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

4 years, 3 months

[MM3-users] Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/2/20 8:10 AM, Mohsen Masoudfar wrote: > > This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? You can't upgrade Postorius alone in any configuration because the latest Postorius requires recent Mailman core, mailmanclient and django-mailman3. Depending on how the Debian/Ubuntu package installs these things, it may be possible to upgrade them with pip3, but as I don't know the details of how they are installed in this package, I can't say how to do this. -- 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: ERROR sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name xxxx to address

by Mark Sapiro

On 3/2/23 14:03, o.mankewitz(a)gmail.com wrote: > > This is the part of mailman.cfg: > [database] > class: mailman.database.postgresql.PostgreSQLDatabase > url: postgresql://mailman:<mypassword>@localhost/mailman > Full error: > sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name "assword>@localhost" to address: Name or service not known Do you have literally `<mypassword>` in `url: postgresql://mailman:<mypassword>@localhost/mailman` `<mypassword>` needs to be replaced with the actual password for the postgress `mailman` user. I.e. the password you provided when you did `CREATE USER mailman WITH PASSWORD 'secure-password';` in postgres (and hopefully didn't set it to literally `secure-password`). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/9/23 08:51, Christian via Mailman-users wrote: > I created a new list using via the form. I sent a test message to the new > list and it appears in the list archive. However I am not receiving the > distribution. > > What should I check for please? Does the list have members, i.e. actual members, not just owners and moderators, and do the members have Delivery status Enabled and Delivery mode Regular. If those show as '-----' in list based preferences, then the address based preferences if any or the global preferences apply. Also check Mailman's var/logs/mailman.log for errors resulting in shunted messages or other messages about the disposition of this message.. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

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

by Stephen J. Turnbull

Mark Sapiro writes: > Not if we're collapsing alternatives. If we're collapsing a > multipart/alternative part with text/plain and text/html > alternatives to just the first alternative we don't keep the > text/html part. I understand that's what we currently do. But I think that when the MUA provides an empty plain text part and a non-null HTML part, that's a mark of lazy MUA developers, not author intent. I think that it's very likely that the author would prefer the reader get converted HTML rather than a blank. Of course if the list owner wants to inhibit conversion, that's fine. But I would expect that list owners who enable conversion would also want to present a converted alternate rather than the blank plain text. Steve

2 months, 3 weeks

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Torge Riedel

Am 07.11.20 um 02:38 schrieb Abhilash Raj: > You can install it using: > > $ pip install --upgrade mailman Hi, I like to ask what to do with other packages when upgrading mailman. I noted, that after upgrading mailman, all requirements are fulfilled, but a lot updates are available: (venv) mailman@basis2:~/core$ pip3 list --outdated Package Version Latest Type ------------------- ------- ------ ----- aiosmtpd 1.2 1.2.2 sdist alembic 1.4.2 1.4.3 wheel atpublic 1.0 2.1.1 sdist dkimpy 1.0.4 1.0.5 sdist dnspython 1.16.0 2.0.0 wheel flufl.i18n 2.0.2 3.1.3 sdist flufl.lock 3.2 5.0.3 sdist idna 2.9 2.10 wheel importlib-metadata 1.6.1 2.0.0 wheel importlib-resources 2.0.1 3.3.0 wheel passlib 1.7.2 1.7.4 wheel PyMySQL 0.9.3 0.10.1 wheel requests 2.23.0 2.25.0 wheel SQLAlchemy 1.3.17 1.3.20 wheel urllib3 1.25.9 1.26.2 wheel zipp 3.1.0 3.4.0 wheel zope.component 4.6.1 4.6.2 wheel zope.event 4.4 4.5.0 wheel zope.interface 5.1.0 5.2.0 wheel Should I update them (regularly) or may I break something in mailman? Kind regards Torge

4 years, 5 months

[MM3-users] mm3mod: command line moderation tool

by David Bremner

Because we're not running postorius, and the moderate-by-mail change is not available in the older version of mailman3 we're running, I needed a tool to moderate lists from the command line. I found mailman-tools, but wasn't able to get them working with python3, so I started from scratch. Maybe someone else will find it useful https://git.tethera.net/mm3mod.git/about/ It's a work in progress, but I am running the version from that repo in production. Like any program using the REST interface, in principle this has complete administrator access to your mailman site, so you need to to trust both this code and the users you let run it. I do run it in "kiosk mode" via ssh command="/home/listmod/.local/bin/mm3mod" ssh-rsa blahblah in .ssh/authorized_keys. This is more of a keeping-honest-people-honest kind of thing.

3 years, 8 months

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

by Mark Sapiro

On 11/24/21 10:17 PM, David Newman wrote: > On 11/24/21 2:36 PM, Mark Sapiro wrote: >> >> To import archives run the Django admin command with arguments >> >> hyperkitty_import -l alist(a)example.com >> /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox > > Good up to here, but ... hyperkitty_import not found. > > This wasn't covered in the venv docs: It is covered at https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy Your issue is probably that the Django admin command you ran is not accessing your `settings.py`. You may need to do ``` export DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/path/to/directory/containing/settings.py ``` before running the Django admin command. These can also be given as --settings and --pythonpath options to the Django admin command. -- 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] Mailman 3 database restore unexpected behavior

by Tibor Molnar

Mailman3 built from source using virtual environment. Version: GNU Mailman 3.3.8 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /etc/mailman3/mailman.cfg Issue: I have restored the database number of times recently and experienced that every time after restoration (an hour after) all members getting an email that they are unsubscribed due to bounces, however non of the users are actually unsubscribed from any lists. It looks like there are duplicates in database and all the duplicates are getting unsubscribed? Bounces message: name(a)email.com unsubscribed from [listname] mailing list due to bounces Only restoring two files: mailman3 and mailman3web Did anyone come acroos this behavior ? It is not right that after restoring a database all 1000 user get an email that they are unsubscribed, but they are actually not. I may do something wrong during the restoring process. Please advise me.

2 years

[MM3-users] Re: 404 on fresh install (Debian11)

by David Newman

On 3/28/23 5:00 PM, comprepair_jimberg--- via Mailman-users wrote: > Can you setup Mailman3 for me? I can't. But I previously provided a pointer to setup instructions using virtualenv, which is MUCH preferable to the older, buggier version packaged with Debian 11. Mark Sapiro also provided a link to a list of providers who help with setup for a fee. If it's any consolation, I practiced with test VMs about 4 or 5 times before attempting a production migration from Mailman 2. Much of my misery was caused by the initial Debian install setting the wrong ownership on some files. For that reason, things got much better when I snapshotted a brand-new Debian 11 VM and rolled back to there each time. I still made mistakes, multiple times, but at least I was no longer fighting with two installations that do things differently. dn

2 years

[MM3-users] Re: Importing mbox file into MM3

by Mark Sapiro

On 6/22/23 7:00 PM, Mark wrote: > Hi All > > I'm trying to import a large mbox file from a MM2 list into a new list > on MM3. > > The new MM3 list has 3 test emails in its archive. > ... > The import or rebuild has failed as it's just rebuilding the existing > archive of the 3 test messages. > > What am I doing wrong? Presumably, the 3 test emails are newer than the messages in the archive .mbox. The default for hyperkitty_import is to not import messages older than the newest message in the existing archive. You need to specify something like `--since='1970-01-01'` on the hyperkitty_import command to import these older messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

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

by Mark Sapiro

On February 7, 2024 1:34:32 PM PST, Odhiambo Washington <odhiambo(a)gmail.com> wrote: >What should I do then? Edit some file? Apply some patch? >It's pretty easy for me to create a DNS record for the same server (IP) for >use with the web host that I'd like to hide. In the Domains view in postorius, you need separate mail hosts. Then you need to change the domain of one of the lists to the 'new' mail host. This implies changing its address which may not be acceptable. Or, you can just live with it as is. Note, I have been without power at my house for almost 3 days now, so I don't have access to all my usual resources. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 year, 2 months

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Danil Smirnov

Hi Mark, On Fri, May 24, 2024 at 11:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > We could default mailman.cfg to contain `start: no` in the runner.nntp > section so people would need to enable it if they wanted it. What do > others think? > I'd vote for disabling it by default and also for moving the Postorius NNTP-related settings from the "Settings - List Identity" page (the last five settings) to a separate page. Users who are born later than my generation are sometimes confused and misinterpret those settings. Once a user set "Newsgroup moderation" to "Moderated" by mistake which implicitly made the mailing list moderated too. Sincerely, Danil Smirnov

10 months, 4 weeks

[MM3-users] Re: "Private archives" aren't private

by Barry Warsaw

On Jul 29, 2017, at 01:33, Simon HANNA <simon.hanna(a)serve-me.info> wrote: > @abompard what's the policy on bug fix releases? > If mailman 3 should get adopted, I guess pushing such fixes quickly shows people that even if they encounter bugs, they get fixed right away... Otherwise they would just wait for it to "mature" Project-wise, the policy is that we coordinate major releases, which in this case means the second digit, much like with Python. So 3.0 and 3.1 were coordinated across all the relevant subproject. Micro/patch releases can happen at any time for subprojects. So if we need to release a Core 3.1.1, we can do that at any time. Of course it means we have to be extremely diligent not to break compatibility. We unfortunately don’t have any good integration tests to enforce this though. -Barry

7 years, 8 months

[MM3-users] Flushing/syncing hyperkitty with mailman

by Eric Abrahamsen

I've got mailman running on Ubuntu 14.04, with systemd service files to govern the mailman and hyperkitty qcluster processes. I notice in the systemctl status call for the qcluster command that there are a bunch of errors like: [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. Is there something more I should be doing to sync hyperkitty's database with mailman? I've got the crontab file in place, and that appears to be running without error. Anything else? Thanks, Eric

6 years, 11 months

[MM3-users] bouncing mail commands

by Liebeskind Uri (luri)

Hi all, when a subscribtion confirmation is sent to MM it replies a bounce mail about unknown commands in the mail. This is very confusing for the users / subscribers and I'd like to disable this function. Actually our users do not need to send commands in the subject and in the body. So responding to words that are unknown commands is not helpful. Currently I have Postfix header and body checks in place that discard this messages from MM to avoid bothering our users. But how can MM3 be configured not to respond to unknown commands or not to parse the mail for commands at all? Thank you for your help and kind regards, Uri Liebeskind -- ------------------------------------ Zurich University of Applied Sciences Information and Communication Technology Uri Liebeskind System Administrator Gertrudstrasse 15 Postfach 805 CH-8401 Winterthur Tel. +41 58 934 72 63 Fax. +41 58 935 72 63 http://www.zhaw.ch/en/ -------------------------------------

5 years, 6 months

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

by Odhiambo Washington

On Sat, May 15, 2021 at 1:04 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:52 PM, Odhiambo Washington wrote: > > > > Do I need to install sassc in the base OS or in the virtualenv? > > Have you checked `which sassc` to see if you don't already have it. It > doesn't matter whether it's in the base OS or the virtualenv. Things > running in the virtualenv can still access the base OS, just not vice > versa. > I install sassc, because sass installation always failed - after some upgrade. <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> I remember posting about it in 2020 or 2019 :) root@gw:/usr/home/wash # which sassc /usr/local/bin/sassc -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

3 years, 11 months

[MM3-users] Error on timeout vs retry values

by Robert Moody

Hi everyone, I have recently setup a new mailman3 service using the venv method. Everything is functionally working however I keep getting an error sent to the mailman email every min which I can not seem to figure out why. /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details.""" I have edited the timeout and retry values in the /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file and restarted both mailman and mailman-web however this still keeps repeating. Any ideas? Regards, Robert -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

3 years, 9 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Tue, 25 Oct 2022 15:56:08 +0900 "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: > Onyeibo Oku writes: > > > This is tiring. At this moment I am left with the possibility that > > SELinux may be in the way. I cannot think of a way to prove this > > hypothesis. > > How about the obvious, disable SELinux temporarily? > To dynamically disable it before the reboot, run the following > command: # setenforce 0 > Thank you. Sure enough Systemd succeeded when SELinux was in permissive mode (ignoring series of AVCs, of course). With SELinux in Enforcing mode, we are back to our previous mileage. Conclusion: SELinux is in the way! I must be missing necessary policy modules for mailman or I am missing relevant parts of the tutorial that deals with SELinux. Where do I go from here?

2 years, 5 months

[MM3-users] Rejecting held emails

by Darren Smith

Hello, We recently had a phishing message make it through our spam filters and arrive at a mailing list. The good news is that since it was not from a list member it was in the held message queue. I was able to find the message in the var/messages directory by searching for a keyword in the subject. However, after rejecting the message from Postorius, the message doesn't seem to be removed from the var/messages directory. Is this expected behavior? I know that infosec people won't be too happy about a phishing email sitting around on our disk. (Infosec guys are notoriously paranoid. :) ) Is there some sort of cleanup process that would remove these messages? If not, does this pose an issue where over time disk usage will creep up? This could be a pretty significant problem if that is the case. What do you think, sirs? -Darren

6 years, 11 months

Search results for query "dO"