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

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Look: [root@localhost mailman]# find / -name mailman.cfg /etc/mailman.cfg /root/var/etc/mailman.cfg /root/mailman/src/mailman/config/mailman.cfg /root/dev/mailman/mailman/src/mailman/config/mailman.cfg /var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/postorius/var/etc/mailman.cfg /mailman/mailman/src/mailman/config/mailman.cfg /mailman/mailman/build/lib/mailman/config/mailman.cfg /mailman/mailman/var/etc/mailman.cfg El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > There must be another config file being picked up. Have a look at the > mailman.cfg search order explained here [1]. > > My guess is that /etc/mailman.cfg exists. Do a 'find / -name mailman.cfg' > to be sure. You'll want to delete any in the search path and then rerun > 'mailman info'. > > [1] > http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > -Kyle > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

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

by Mark Sapiro

On 12/19/18 7:03 AM, brian(a)emwd.com wrote: > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. ... > 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; > } > } Since you can curl http://172.19.199.3:8000/postorius/lists/ and get the correct output, uwsgi or whatever your wsgi process is is working at that level, and I don't think you should be invoking uwsgi in nginx. I think you should be using proxy_pass. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> for the nginx config used on 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

6 years, 7 months

[MM3-users] Re: Verification Failed Error

by Abhilash Raj

On Thu, Dec 20, 2018, at 2:28 PM, brian(a)emwd.com wrote: > Abhilash Raj wrote: > > Yes, you do need to restart mailman-web container. > > > > $ docker-compose restart mailman-web > > When I added the following to /opt/mailman/web/settings_local.py > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > > I got network not found error message in the log file when I tried to > reset my password. Should EMAIL_HOST be something else besides > localhost? Yes, I am sorry, I should have mentioned this before. Created another issue to add that as well[1]. It should be pointing to Exim running on host, so EMAIL_HOST = 172.19.199.1 [1]: https://github.com/maxking/docker-mailman/issues/277#issuecomment-449156976 > _______________________________________________ > 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, 7 months

[MM3-users] Re: need help to migrate from Mailman2 to Mailman3 (french if possible)

by Pascal Léval

what you have written below worked fine, thanks ! but now, I still have the error sending an email : Erreur : 550 5.1.1 <formule(a)listes.leval.info>: Recipient address rejected: User unknown in relay recipient table I think it's a problem with Postfix, what do you think ? Cordialement Pascal Léval Le 22/03/2024 à 15:13, Odhiambo Washington a écrit : > First, you must create the list in MM3 because the list MUST exist > before any operations can be done on it. > > 1. mailman create formule(a)listes.leval.info > # Create the list in MM3 > 2. mailman import21 > formule(a)listes.leval.info /var/lib/mailman/lists/formule/config.pck > # Import the list config > and members > 3. mailman-web hyperkitty_import -l formule(a)listes.leval.info > /path/to/archives/private/formule.mbox/formule.mbox # import archives > 4. mailman-web update_index_one_list formule(a)listes.leval.info > #update list index

1 year, 4 months

[MM3-users] Re: MM3 Docker

by brian＠emwd.com

Odhiambo Washington wrote: > So you just added: > - stop_grace_period: 30s > > to the block?? I actually did not add it. It was already there from the docker files that I pulled from: https://github.com/maxking/docker-mailman > > I don't know if that setting makes any difference. I am also > > using the > > included postgres database instead of mysql. > > > > For the mailman-web section, you need to add the following: > > > > - SERVE_FROM_DOMAIN=yourdomain > > - MAILMAN_ADMIN_USER=youruser > > - MAILMAN_ADMIN_EMAIL=youradminemailaddress > > > The mailman-web section has sub-sections. Under which one do I add > these? environment?? Or networks below the IP address? Under the environment sub-section. > I have apache2 and nginx on the server. Apache listens on 80 and 443 while > nginx listens on 8080 and 8443. I won't be of much help here I am afraid. My server is just using nginx. Brian

6 years, 6 months

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

by Nick Wynja

On 02/10/19 at 08:57, brian(a)emwd.com <brian(a)emwd.com> wrote: > "In your `settings_local.py` copy the whole INSTALLED_APPS section from [default settings](https://github.com/maxking/docker-mailman/blob/master/web/mailman… and add/remove the auth providers you want/don't want. Notice the `allauth.socialaccount.providers.<provider>` in the list below." Another option, which seems more future-proof, is to strictly remove the account providers you don't want from INSTALLED_APPS rather than defining INSTALLED_APPS locally. First, you have to access INSTALLED_APPS by importing settings into settings_local.py: ``` from settings import * ``` Then, you can set INSTALLED_APPS to everything it already is minus the social providers: ``` INSTALLED_APPS = [a for a in INSTALLED_APPS if not a.startswith('allauth.socialaccount.providers') and not a.startswith('django_mailman3.lib.auth.fedora')] ``` This way if Postorius ever adds any apps you won't need to update your local settings. Anyone see any downsides to doing it this way? -- Nick Wynja https://nickwynja.com

6 years, 5 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Thank you for your prompt response Mark, Στις 2019-09-18 19:12, Mark Sapiro έγραψε: > Is only one list affected, and is it all messages from this list or > only > some? Just two messages from this certain list. Subsequent messages and other activity seems to work properly > Do some deliveries of the problem message succeed? > I think not, the IndividualDelivery lines list all all recipients (list is small so I was able to check) > Postfix can return a 421 status > and drop the connection if there are too many invalid local recipients, > although I don't know if this would apply in the VERP case. Well there is no connection to postfix at all when the runner starts and the "Cannot connect to SMTP server" log shows up. Otherwise I'd have seen something in the postfix logs or tcpdumps in localhost.

5 years, 10 months

[MM3-users] Re: Negative number for digest size

by Mark Sapiro

On 2/4/20 3:12 AM, Gila Halpern wrote: > If I set the digest size threshold to -1, will that make the digest size unlimited, and it will send once per period specified in the digest frequency setting? No. Setting digest_size_threshold to anything <=0 will send a digest on every post. You have to just set it to a very large number (or a reasonable value for the largest you want the digest to grow before it is sent). However, when periodic digests are sent has nothing to do with Digest Frequency. That setting which is misnamed and improperly described (see <https://gitlab.com/mailman/postorius/issues/395>) controls only how often the digest volume number is incremented and issue number reset. The frequency of periodic digests is controlled by when cron runs the `mailman digests --periodic` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Correcting name spellings in a list

by Mark Sapiro

On 2/24/21 10:13 AM, Peter Adebahr via Mailman-users wrote: > On 2/24/21 6:40 AM, Morris Jones wrote: >> I typo'd some full names in a mailing list. Is there a way to fix it >> without writing SQL? >> > > I understand it is just the name itself, which has been typo'd, not the > mail address: Couldn't you just edit the field "display_name" of table > "address" in the MM3 database? Easy with phpmyadmin or adminer... Of course you can do that if that's where the typo is. The actual display name you see may be the one in the `address` table, or it may be the one in the `user` table depending on whether the subscription is by address or by user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] is there a mailman command/setting to periodically clean archives?

by William Oliver

Thanks to everyone's help, mailman3 is up and running for me on two servers with three lists, and they all work as far as I can see. I'm sending out invitations to users tomorrow. Yayy. Up until today, I had been stuck using a plugin in Joomla, which was not the best solution. I'm tickled pink, and my users will be, too. Now I'm just playing and tinkering a bit. I'd like to delete all my archives that are more than a certain age, e.g. more than a week old. I can easily do that with a cron job, deleting old files in /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* which is, as far as I can see the only place archive emails live. However... I was wondering if there was some mailman command or config variable that would accomplish this without using cron. billo

3 years, 7 months

[MM3-users] Re: best pratice - set default MM settings and make them update-save

by Mark Sapiro

On 5/16/22 07:16, Stefan Bauer wrote: > > Is there also a way to have this box checked by default or do not request a > verifcation at all? > Could not find any flag in base.py. To have the box checked by default would require a patch to Postorius like this. ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form): pre_verified = forms.BooleanField( label=_('Pre Verified'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, users will not have to verify that their ' ``` Not requiring verification at all would require patching Mailman core but would be a bad idea as it could allow someone to subscribe anyone without that person's consent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: SOLVED was --- Re: Re: Debian 11 mailman3 installation question

by Stephen J. Turnbull

William Oliver writes: > There were a couple of gotchas, but not too bad. Happily, the > README.debian and a few web pages fleshed it out. I didn't really expect turnkey.... Too many independently configured packages (webserver, Django, wsgi provider, MTA, on top of probably about 5 Mailman packages and dependencies). > The only thing is that the packages put a lot of stuff in places different than the > manual installation tells you to do, so I had to keep poking around to > find stuff. There's a dpkg command that lists what's installed by a package. Probably it's accessible from apt. That plus grep -E '.cfg|settings.py|template|log|queue should get a list of most of what you need to deal with. Someday I should collect a few of those for the popular distros and/or package managers. Steve

2 years, 9 months

[MM3-users] Re: export/import list?

by Dave McGuire

On 8/22/23 17:59, Mark Sapiro wrote: >> I'm moving from sqlite3 to postgres; I can handle that migration. >> But I'm also moving from Mailman 3.1.1 to 3.3.8; do you (or anyone >> else) know of any schema changes? I spot-checked the first few and >> they looked the same, but before going through all of them I figured >> I'd just ask here. > > Schema changes are handled automatically by alembic. The migrations are > defined in /mailman/database/alembic/versions/. Your current version is > is stored in the database in the alembic_version table. When Mailman > core is started, all migrations from your current version to the latest > version will be applied to bring your database up to date. I.e., you > don't need to be concerned about schema changes upon upgrade. They are > handled automatically. Brilliant! Thank you Mark. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

1 year, 11 months

[Test] Re: Down time.

by Mark Sapiro

On 03/18/2016 05:47 PM, Mark Sapiro wrote: > Later this evening (maybe March 19 02:00 UTC) I will be attempting to > reconfigure things to use the gitlab master branches of MailmanClient, > Postorius, HyperKitty and the HyperKitty-Mailman plugin in addition to > using gitlab master branch of Mailman itself which is already the case. > > This will probably involve down time and/or anomalous behavior. I got distracted with things like dinner and all, and I'm doing a lot of it outside the working (to the extent that it is) install, but I'm getting close. The good news is I should be able to stop services, switch over and start and it will live or die, so total down time should be maybe 15 minutes or less, but i won't be ready until more like 04:30 or 05:00 UTC. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 4 months

[MM3-users] Re: Redundant and load balanced Mailman3

by Pawel Grzywaczewski

Thanks Abhilash, I'm a bit confused about dependency on local files? You mean files that are created when an e-mail is processed? So where is the problem with redundancy? If this host is gone there will be another Mailman deployment able to deal with the load. What about having 3 VM where all components of Mailman are installed. Those VMs connect to 1 database on a remote host. We deploy HAProxy in front of 3VMs. So as the result all requests (HTTP/SMTP) are distributed to 1 VM (out of 3). A given VM handles a request HTTP or SMTP, and if there is a problem (or very high load of SMTP) there are still 2 other VM that can do the job. So perhaps the question is: can we plug 3 Mailman instances into 1 DB? Is Mailman software developed taking into account that several Mailman instance writes to the same database at the same time? Cheers, Paweł

4 years, 10 months

[MM3-users] Re: Something wrong in Django admin interfaces

by Mark Sapiro

On 7/21/23 01:39, Franklin Weng wrote: > > When I clicked any features like users, Mail domains, Failed tasks... > anyone, no matter New or Change, the web page was covered by the first > page. All the configuration fields/labels are covered by the first page. > > Please see the screenshot: > > https://nextcloud.slat.org/index.php/s/e5KKEEbqDK6DpiN > > https://nextcloud.slat.org/index.php/s/nLgMRQ9ACyxCwoc > > It was not able to do the administration tasks. I can't see your screen shots; the connection times out. However, this is not a Mailman issue. The Django web admin interface is part of Django. See <https://docs.djangoproject.com/en/4.2/ref/contrib/admin/> This issue should probably be reported to Debian if it is a Debian package issue, or possibly to Django. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 09/28/2017 01:56 PM, David Krantz wrote: > This is clearly a bug and should be fixed. If you report this issue at > <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. I'll do that. >> Of course this very nice functionality is a bit buried. I activated it >> using the interactive python shell, seems less risky than changing the >> database directly. > > > There are many core settings not (yet) exposed in Postorius. This is > something we need to fix, but it takes time and resources. In the mean > time, 'mailman shell' is probably the best way to set them. It is okay and it works just fine. In the current version "mailman withlist" does not set a variable to a list, but it is easy enough to set it yourself if a bit poweruser-ish. br // David

7 years, 10 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/23/20 9:37 AM, Brian Carpenter wrote: > > How would a person already be a core user outside of a registration with > Affinity? Via a list subscription or the import21 script? Yes, or even just by sending a post to a list as a nonmember. Everyone who is or has been a member, non-member, owner or moderator of a list has a user and one or more address records in Mailman core. > I do want to apologize for my tone Mark. I was wrong in the way I communicated. Apology accepted. I understand that it can be frustrating to be dependent on something you don't control and that this can sometimes lead to "anomalous" behavior. Here's a take on this that is intended to be humorous, but is actually quite frightening. https://xkcd.com/2347/ -- 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: Member Issue Discovered

by Brian Carpenter

On 10/28/20 4:29 PM, Mark Sapiro wrote: > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. This is a bug with Affinity which I have scheduled to be fixed. However I am confused. Data is completely removed from Mailman 3 core when you delete the account via Postorius but not when you unsubscribe from a list? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: E-mail every minute: "Cron <www-data@sharky5> ..."

by Mark Sapiro

On 7/7/24 6:11 AM, Robert Heller wrote: > What am I missing? I *think* I have mailman3 *mostly* setup, but there are > still some configuration things that are missing, but I am not sure how to fix > them (the docs are NOT clear). I am getting an e-mail *every* minute that > looks like: ... > /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, > failure to do so will cause the tasks to be retriggered before completion. > See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. Set something like ``` # Set retry > timeout. Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } ``` in your settings_local.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: mailman3-web and the django middleware problem

by Odhiambo Washington

On Fri, Apr 26, 2024 at 8:30 AM Thomas Stein <himbeere(a)meine-oma.de> wrote: > Am 2024-04-26 00:52, schrieb Mark Sapiro: > > On 4/25/24 14:01, Thomas Stein wrote: > >> Am 2024-04-25 22:03, schrieb Mark Sapiro: > >>> > >>> I don't know how things are arranged in the Debian/Ubuntu package, > >>> but you may have a settings.py which at the end does something like > >>> ``` > >>> try: > >>> from settings_local import * > >>> except ImportError: > >>> pass > >>> ``` > >>> If that is the case, adding the above snippet to the end of > >>> settings_local.py should work. > >> > >> Yes, that's the case. I added the snippet in question to > >> settings_local.py but this leads to another error: > >> > >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> > >> from settings_local import * > >> File "/usr/share/mailman3-web/settings_local.py", line 194, in > >> <module> > >> x = list(MIDDLEWARE) > >> ^^^^^^^^^^ > >> NameError: name 'MIDDLEWARE' is not defined > >> dpkg: error processing package mailman3-web (--configure): > > > > Yes. I understand. In your case, MIDDLEWARE is only defined in > > settings.py and not in settings_local.py. As I understand it originally > > you added > > ``` > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to settings.py and you say it didn't help. I don't know why that > > wouldn't work as long as there is no setting for MIDDLEWARE in > > settings_local.py and you added that after the MIDDLEWARE setting in > > settings.py. > > When you say it didn't help, do you mean you still get the > > > > django.core.exceptions.ImproperlyConfigured: > > allauth.account.middleware.AccountMiddleware must be added to > > settings.MIDDLEWARE > > > > message or something else? I note that the original post in this thread > > refers to /etc/mailman3/mailman-web.py which is presumably where the > > package ultimately puts the Django settings, and I don't know what > > `dpkg --configure` is doing. > > > > One thing you could try is in settings_local.py, put > > ``` > > from settings import MIDDLEWARE > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to work around the NameError. > > After that I get: > > File "/usr/share/mailman3-web/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' > (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > > I guess I'll wait for the new package for now. > How about adding: MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) in settings_local.py And how about you use the virtualenv method <https://docs.mailman3.org/en/latest/install/virtualenv.html> for more peace of mind in the future? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 3 months

[MM3-users] Howto: Mass import of nonmembers in several lists?

by Paul Paulchen

Hi MM3 community, got a, perhaps easy question. Following situation, got 8 lists and up to 20 nonmember users missing to the list. The massimport with postorius is only for members, as far as I can use it (Postorius Version 1.3.4). So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. I thought so, because the import21 command did this as well when we migrated to mailman3. I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! Hope I explained my case properly. I appreciate your responds! Thanks in advance. - Paul

3 years, 6 months

[MM3-users] Re: Hyperkitty shows "<" as <

by Mark Sapiro

On 4/5/23 07:39, Andreas Schamanek wrote: > > The function that handles it is escapeemaillinks() in > templatetags/hk_generic.py (at line 111 in my version). > > Adding `.replace("&","&")` to the return value fixes the rendering > of email addresses (at least for me). escapeemaillinks(text) searches text for strings like <a href="mailto:user@example.com>xxx</a> and replaces them with user(a)example.com thus replacing everything from `<a href=` through `</a>` with just the email address with `@` replaced by `(a)` However, text is the whole message body, so what you are doing is just replacing `&` with `&` in the message body, but only when escapeemaillinks(text) is invoked. Also, this is all changed in HyperKitty 1.3.5 with the addition of optional markdown rendering. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: export/import list?

by Mark Sapiro

On 8/22/23 2:38 PM, Dave McGuire wrote: > > I'm moving from sqlite3 to postgres; I can handle that migration. But > I'm also moving from Mailman 3.1.1 to 3.3.8; do you (or anyone else) > know of any schema changes? I spot-checked the first few and they > looked the same, but before going through all of them I figured I'd just > ask here. Schema changes are handled automatically by alembic. The migrations are defined in /mailman/database/alembic/versions/. Your current version is is stored in the database in the alembic_version table. When Mailman core is started, all migrations from your current version to the latest version will be applied to bring your database up to date. I.e., you don't need to be concerned about schema changes upon upgrade. They are handled automatically. -- 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] docker setup

by epi＠epinux.com

Hi, attempting to install mailman3 on a remote ubuntu server - my docker-compose file looks like: https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a /opt/mailman/core/mailman-extra.cfg ``` [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.1.1 lmtp_port: 8024 smtp_host: 127.0.1.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg ``` opt/mailman/web/settings_local.py ``` EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '127.0.1.1' EMAIL_PORT = 25 USE_SSL = False DEFAULT_FROM_EMAIL = "mailman(a)lists.libkml.org" SERVER_EMAIL = "mailman(a)lists.libkml.org" DEBUG = True ALLOWED_HOSTS='libkml.org' ``` I know I am still missing the NGNIX/APACHE settings, but trying to access the service at: libkml.org:8000 I get a django error Invalid HTTP_HOST header: 'libkml.org:8000'. You may need to add 'libkml.org' to ALLOWED_HOSTS. but I have the 'libkml.org' to ALLOWED_HOSTS in both `opt/mailman/web/settings_local.py` and in the dockerfile: https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a#file-mail… https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a#file-mail… Can you help me please to understand what I am doing wrong? Thanks!

3 years, 1 month

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

by Mark Sapiro

On 10/26/22 17:30, David Newman wrote: > > 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. Was the venv initially created as the `mailman` user? Maybe sudo chown mailman:mailman /path/to/venv 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

2 years, 9 months

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

by Arte Chambers

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. Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Mon, Nov 4, 2024 at 4:51 AM Odhiambo Washington via Mailman-users < mailman-users(a)mailman3.org> wrote: > On Mon, Nov 4, 2024 at 12:36 PM Gerald Vogt <vogt(a)spamcop.net> wrote: > > > On 04.11.24 09:13, Odhiambo Washington via Mailman-users wrote: > > > On Mon, Nov 4, 2024 at 10:34 AM Gerald Vogt <vogt(a)spamcop.net> wrote: > > >> On your server it looks like this: > > >> > > >> # ls -la /etc/mailman3 > > >> total 28 > > >> drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . > > >> drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. > > >> -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf > > >> -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg > > >> -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg > > >> -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py > > >> > > >> and it works just fine. > > >> > > > > > > True, but making the mailman user own the files makes life easier when > > you > > > operate from the virtualenv - > > > you do not have to exit the virtualenv to edit the files in > > /etc/mailman3, > > > and then re-enter the virtualenv. > > > > The virtualenv doesn't change the current uid. That doesn't make a > > difference. > > > > > You do not have to give the mailman user sudoer rights. That's the > whole > > > point about the below: > > > > > > ``` > > > sudo mkdir /etc/mailman3 > > > sudo chown mailman:mailman /etc/mailman3 > > > sudo chmod 755 /etc/mailman3 > > > ``` > > > > Well, that essentially was my question: why does the mailman user > > require sudo rights? > > > Mark did not say that the mailman user required sudo access. Please re-read > what he said. > > > > Why does it need to be able to write or change > > those files/directories? Except for the convenience which isn't a reason > > to weaken security. > > > > Make me understand how the security is weakened. The Mailman user account > has no password so cannot login from outside. > Even if it was able to login, it will still end up only accessing $home and > /etc/mailman3, no? > > > > In respect to security, i.e. separation of the service user from write > > access to it's core configuration files, it should not be done unless > > absolutely necessary. > > > Sorry, I didn't understand that. > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > In an Internet failure case, the #1 suspect is a constant: DNS. > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] > _______________________________________________ > 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 paul.m.robey(a)gmail.com >

8 months, 2 weeks

[MM3-users] Re: Moderating posts via email

by Mark Sapiro

On 10/26/2017 02:21 PM, Dmitry Makovey wrote: > > after which we've used above password trying to approve messages > following the steps outlined above. > > What are we doing wrong, or where to look for further information? Are you replying to the outer message or to the message in the attached message/rfc822 part that contains the If you reply to this message, keeping the Subject: header intact, ... text? You don't actually have to 'reply' to anything, but your message with the 'Approved: password' actual header or first body line must be sent To: the list-request address with Subject: confirm <token> (possibly preceded by 'Re: ' or similar. If you reply to the attached message/rfc822 message, it should work. If you reply to the outer message it won't work. -- 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: Broken web UI after upgrade

by Mark Sapiro

On 12/14/22 08:15, Odhiambo Washington wrote: > After upgrading MM3 and running all the post-update tasks and even > re-indexing all the posts, I have ended up with a somehow "broken" > hyperkitty. > The archives display on a browser six, to say the least. > The site is public, so I can share the link: https://list.rc.org/archives/ > > What should I do in order to fix this? > Are you asking about the lack of style or the "No archived list yet."? The former indicates an issue in your web browser with accessing the `static` directory or an issue with the django admin collectstatic or compress commands. I don't know about the latter - could it be because all the archives are private and I'm, not logged in? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Mark Sapiro

On 6/26/23 12:35 PM, Ken Alker wrote: > I'm brand new to this, so take this with a grain of sale, but, I had a similar problem a few days ago, however, mine was "flufl.i18n>=3.2". Perhaps the same thing is happening with flufl.lock (but that didn't bite me). > > I solved my problem by following this: <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately modifying "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires.txt" per that thread (see <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by Thomas Ward section called "The WORKAROUND"). Maybe you need to do the same thing, but for flufl.lock. Yes, the same issue now affects flufl.lock as well as flufl.i18n. You will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. -- 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: Any possible way to reduce robot spam accounts?

by Mark Sapiro

On 7/20/23 20:42, Franklin Weng wrote: > > Thank you. When I set it in my settings_local.py, I clicked register > and got an error: > > ModuleNotFoundError at/accounts/signup/ > No module named 'django_mailman3.views.user_adapter' > > (In the document the path is /etc/mailman3/settings.py but I installed > it with Debian packages so I guess the path is somewhat different, and I > thought setting in setting_local.py should work too. It seems work > since it gave me the error above.) > > Do I have to install something else? Or disable some other options? What is the version of django_mailman3 in your Debian package? As it says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for these settings to work." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Sibling lists in Mailman3

by Markus Grandpre

Is there an equivalent approach to implement sibling lists in Mailman3? Best regards, Markus Grandpré Am 3/28/24 um 16:06 schrieb Markus Grandpré: > Thank you. > > Am 27.03.24 um 17:26 schrieb Mark Sapiro: >> On 3/27/24 08:05, Markus Grandpre wrote: >>> >>> after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or >>> something similar) in Mailman3. How are sibling lists treated in Mailman3? >> >> The sibling list features do not exist in Mailman 3. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 3 months

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

by bob B

Question1 We use help users with list settings, so we would log into mailman2 with the master password. So what is the best way to duplicate this for mailman3. I assume I can just use the admin account and share that password with my other admins. But I see the domain owners, but is that working? I added someone as a domain owner, and they do not see private email lists and it looks like that can not edit any list settings? There was a post that this had not yet been implemented? Any other options? Question2 Where are all the emails/archives stored? are they in /opt/mailman/...., or are they in the database? For mailman2 we had mailman located on a large volume to handle archives, just trying to see if that is the same for mailman3 or if all the data is now in the database (which will be external for our installation)?

3 years, 8 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/27/22 05:22, Stephan Krinetzki wrote: > > I think there is a communication problem in the chain: > > apache -> uwsgi -> mailmancore/API ->database > > but i can't dig deeper there. Let me know if i should provide more details or logs It seems that this part of the chain apache -> uwsgi -> mailmancore/API is not experiencing delay. It is involved with every Postorius request, most of which seem to have no issues. It is only this one piece mailmancore/API ->database that seems to have an issue and only with this one DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX query. However, like you, I have no idea as to what you could do further to debug this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

What happened to the maintainer? This is an increasing problem these days. On Sat, 13 Mar 2021 05:00:50 -0500, Bernd Wurst wrote: > > > Hi. > > Am 13.03.21 um 04:36 schrieb John Covici: > > Hi. I am having a great deal of difficulty installing mailman3 using > > gentoo and sendmail. > > Mailman in gentoo is kind of maintainerless (will be in a few > days, I suppose) and so this method can not be recommended. > > We installed using pip in a regular useraccount. > > regards, > Bernd > _______________________________________________ > 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/ > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 4 months

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/18/22 01:55, Élodie BOSSIER via Mailman-users wrote: > Thank you for your response Mark, > > With Mailman 2.1, the lists were split on their webpage respectively. > How could I do same with Mailman 3.3.3 (Tom Sawyer) please ? > > My domain table SQL have this result : > id, mail_host, description, alias_domain > 1, ml.franceserv.fr, NULL, local.ml.franceserv.fr > 2, ml.viticreation.fr, NULL, local.ml.viticreation.fr If you go to https://example.com/mailman3/domains/ (the Domains view in Postorius) you will see at least two entries, one with Mail Host ml.franceserv.fr and one with Mail Host ml.viticreation.fr. What are the Web Host entries for these? You should have two separate site entries in the django_site table (https://example.com/admin/sites/site/) for these domains. -- 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: Disabled by bounce

by denise.mcgeachy＠gov.bc.ca

Hi all - new to this forum but am trying to work out a similar issue raised by a list member's IT department. I'm a bit out of my depth here and hoping you all can help. They have recommended: - When the mailing list relay an email from a member of the list to other members, the email from address should be the mailing list and not the user sending the original email. For example: list-name(a)mydomain.ca (on behalf of Sally Brown) - The mailing list should not modify the original email and thus breaking the DKIM signature I have clicked the DMARC mitigation unconditionally option which seems to solve the second point but haven't managed to have it sent by the list name but not as suggested in the first point. I either get "my email via list(a)mylist.ca" or list(a)mylist.ca" Is anyone aware of a setting to do this? Many thanks d

2 years, 5 months

[MM3-users] Problems with mailman core translation and other details

by Stephen J. Turnbull

celi--- via Mailman-users writes: > Everything almost OK, except from the fact that none of mailman's > core email messages are being translated, even though mailman.po > shows the right messages. Did you restart mailman? Have you changed the default language in mailman.cfg? I don't know how Debian may have altered the configuration mechanism, but they usually do. It's possible they've changed file locations or added "conf.d" capabilities or something like that to make their automated management tools work. > Also, strange things happen to these .po files. The web interface > is almost perfect, but some messages (just some) are not correct - > although the corresponding django.po appears to be OK. It´s the > case below: the pair msgid/msgstr seems to be OK, but this > particular sentence is not being translated. Since this is Django, have you run "mailmanweb compilemessages"?

1 year, 5 months

[MM3-users] Re: Hyperkitty import from mailman2

by Sten Aus

Hi Thank you Mark and Simon for your input! I can see imported list from Hyperkitty GUI, but it's inactive. I can confirm that I can see those emails from command line (python shell shows Email Objects). Import shows everything is OK: # python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox Only emails after 2010-01-01 00:00:00+02:00 will be imported Importing from mbox file /tmp/test.mbox to test(a)list.domain.com /--some 22 emails being imported here --/ 22 emails read 22 email added to the database 22 emails are stored into the database Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now. # python2 manage.py update_index --settings settings Indexing 50 emails NB! Only 6 of them are archived from new list (which has been created from Apache). I have imported 2 times 22 emails from /tmp/test.mbox file (to different lists). I am using Apache2.4 with mod wsgi and Postorius and Hyperkitty are in the same django application. Also tested with running server directly and then connecting to a port 8000, but I guess it does not matter, because both of them are using Python script. I have not yet managed to set up cron tasks, as this is relatively new installation, but I have ran them manually. Also, I have done update_index (runjob update_index and manage.py update_index, both ways). SQLite database shows emails, for example there's a thread FMXQVFDRQVRMINVXI4DJB4SHYTJ3EPWP, but If I insert it to web URL I get Django error: No Thread matches the given query. As Postorius and Hyperkitty are in the same Django, they share sqlite database (mailman/web/database.db). Mailman has it's own database in mailman/var/data/mailman.db. Happy holidays Sten On 22/12/2017 21:09, Simon Hanna wrote: > On 12/22/2017 03:39 PM, Sten Aus wrote: >> Hi >> >> I have installed mailman3 - it looks very great! >> >> Now I wanted to try import from mailman2 mbox, so i did: >> >> python2 manage.py hyperkitty_import --settings settings >> --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com >> /tmp/test.mbox >> >> It shows that it have sucessfully imported all emails and I can see >> them from database (sqlite3), but I cannot see them from GUI >> (hyperkitty). Only thing I can see is this inactive "test" list. >> > How did you try to access them using Hyperkitty? Can you try doing > that while logged in as a django superuser? Could you try using a > permalink for a message? If you can access the files from the database > you should be able to construct the urls using the list name and the > message_id_hash of a message. You should try this using DEBUG=True in > the settings.py. The URL would be similar to > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… > > > Another option would be to check if you can access the data using a > python shell. > > `python manage.py shell` to open a python shell preconfigured for > Hyperkitty and then input the following two lines: > > from hyperkitty.models.email import Email > Email.objects.all() > > > This should print out all the messages that are stored in the > database. (You can limit them by appending "[10:]", or any other > python slice) > > What do you see in the UI? Is it somewhat similar to > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ? > _______________________________________________ > 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] Re: MM3 gateway errors and frequent reboot needs

by Mark Sapiro

On 4/19/20 1:21 PM, hansen(a)rc.org wrote: > We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? We are not seeing an issue like this on either lists.mailman3.org (this list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) What are you seeing in web server logs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

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

by Andreas Barth

* Johannes Rohr (johannes(a)rohr.org) [210314 18:30]: > Please excuse me, if this has been discussed before and I missed it, but > what is the added value of going through the trouble of manually > installing mailman3, rather than doing a simple apt install > mailman3-full? I would assume that in most cases, a well maintained > package is preferable, because it makes life easier. Are the Debian > packages for Mailman3 in some way deficient? As always, packages in Debian stable are not as new as the latest git checkout. So, if the stable version work for you: great. If you want to have something newer, either try the packages from testing / unstable, or some checkout from git. If you want to improve the code, git checkouts are of course also preferred. Of course, this is true not only for mailman3, but also for exim, kde, gimp, whatever. Andi

4 years, 4 months

[MM3-users] Re: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 09:18, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > this is with "Postorius Version 1.2.4" (as installed by the mailman3 > Debian package). The Debian packages are OK for people who want to install things via a package manager, but they are quite out of date. Something like the following in `mailman shell` can do it. ``` >>> # Cutoff date delete pended subscriptions older than this >>> cutoff = '2022-03-01' >>> pendings = getUtility(IPendings) >>> # Prior to Mailman core 3.3.5 need to explicitly delete workflow >>> wfm = getUtility(IWorkflowStateManager) >>>for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['when'] >= cutoff: ... continue ... pendings.confirm(token, expunge=True) ... # for MM < 3.3.5 ... wfm.discard(token) ... >>> commit() ``` -- 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: Problems with New MM3 Installation

by Abhilash Raj

On Tue, May 11, 2021, at 8:43 PM, Mark Sapiro wrote: > On 5/11/21 7:46 PM, Jeff wrote: > > > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > > > 1) some emails that arrived before I got the archive working are still sitting in: > > > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a > collection of messages in maildir format. This is how the prototype > archiver stores messages. This has nothing to do with HyperKitty. It is > a separate archiver. If you don't want messages to be stored there, you > can disable the prototype archiver for the list by unchecking prototype > in Postorius -> Settings -> Archiving -> Active archivers or disable it > entirely for the installation by setting > ``` > [archiver.prototype] > enable: no > ``` > in mailman.cfg > > > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > > > /usr/local/mailman3/mm/var/queue/shunt > > > > What should I do to get these messages processed? > > > Assuming the issues that caused them to be shunted have been fixed, just > run the command > ``` > mailman unshunt > ``` > > > 3) Similar to above, some messages are in: > > > > /usr/local/mailman3/mm/var/queue/bad > > > > How can I get these messages processed? > > > First examine the messages with > ``` > mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> > ``` > To be sure you want them. Also examine mailman.log for the times they > were stored in the `bad` queue. You are looking for 'Skipping and > preserving unparseable message: <file>' and/or 'SHUNTING FAILED, > preserving original entry: <file> messages and you want to determine > which runner preserved the message. There may be a 'whichq' entry in the > message's metadata in which case, that's the answer. > > Once you have determined the queue, you can just move the .psv file from > the bad queue to the appropriate queue, renaming it from .psv to .pck in > the process. > > > > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? > > > I know little about uwsgi. setting it to `uwsgi://localhost:8000` might > work. You could also set it to the base URL that a user would use to > access the web UI, e.g. `https://example.com` and that would presumably > be proxied to uwsgi. For example, on the server for this list we have > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` > which gets proxied to gunicorn, but the idea is the same. Using the full external URL should work. Core doesn’t speak uwsgi protocol so the uwsgi:// URL won’t actually work. I am starting to think it was a very bad idea to use uwsgi in the official docs :( -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: File in /var/lib/mailman3/queue/bounces/

by Mark Sapiro

On 12/11/21 6:29 PM, Andreas Barth wrote: > > in my local installation there is a file in > /var/lib/mailman3/queue/bounces/ since a couple of days. Any hint how > to get rid of it? 'mailman unshunt' doesn't do it, but also, it's in > queue/bounces and now queue/shunt. I suspect the issue is that bounce runner is not running. If you grep Mailman's mailman.log for `bounces` I suspect you will see that it has died and not restarted. You may or may not find additional information in the log as to why it died, but in any case restarting Mailman should start everything again. The master should restart it when it dies, but this is https://gitlab.com/mailman/mailman/-/issues/898 for which we don't have a satisfactory fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Importing users and mas settings "Moderation Action"

by bob B

I imported email lists and users to version 3 from version 2. One of my lists all the users are set to 'Hold for moderation" for "Moderation Action". I assume this is because they were set to moderation on mailman 2? But if I mass subscribe users via the Gui in mailman 3 then their default "Moderation Action" is set to "none" so I assume it follows list default, is that a correct assumption? I believe there is no way to import mass users and set their "Moderation Action" at the same time is this correct? Wasn't that possible in mailman 2? is there a way to change all their user's "Moderation Action" for a list in bulk? So it looks like for any users I mass subscribe, "Moderation Action" will be set to "none" and if I want to change that I have to do it manually for each user?

3 years, 2 months

[MM3-users] Re: Postorius -owner messages

by Mark Sapiro

On 6/15/23 13:47, ssehi--- via Mailman-users wrote: > > They'd like to disable owner delivery for themselves, and I'd like to not make the change for them using the shell every time I get one of their requests. We have a Postorius front end set up and working, but it doesn't appear that disabling delivery using the List-based preferences in the Postorius interface stops those Owner communications. Is there a way to allow users to disable that natively in Postorius? No. In Postorius you can set the delivery status for members and non-members, but you can't set it for owners or moderators. Owners and moderators do have a delivery_status which will control whether they receive notices sent via the listname-owner address, but it is not exposed or settable in Postorius. -- 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: mail loops back to myself

by Florian Sukup

I have now elimiated reverse.rrr.com. But there isn't much change: vvvvvvvvvvvvvvvvvvvvvvvvv Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: initializing the client-side TLS engine Jun 11 22:19:57 arvak postfix/smtpd[1015581]: initializing the server-side TLS engine Jun 11 22:19:57 arvak postfix/smtpd[1015581]: connect from host.xxx.com[m.y.i.p] Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: warning: host host.xxx.com[m.y.i.p]:25 greeted me with my own hostname host.xxx.com Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: warning: host host.xxx.com[m.y.i.p]:25 replied to HELO/EHLO with my own hostname host.xxx.com Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: 29FCF5F867: to=<mylists(a)lists.yyy.com>, relay=host.xxx.com[m.y.i.p]:25, delay=0.2, delays=0.06/0.01/0.13/0, dsn=5.4.6, status=bounced (mail for lists.yyy.com loops back to myself) Jun 11 22:19:57 arvak postfix/smtpd[1015581]: disconnect from host.xxx.com[m.y.i.p] ehlo=1 quit=1 commands=2 ^^^^^^^^^^^^^^^^^^^^^^^^^^ Is there anything else I can do to find the error? Thank you. Florian.

1 month, 3 weeks

[MM3-users] Re: two signatures on sent mail?

by Mark Sapiro

On 6/19/25 08:33, STR via Mailman-users wrote: > Hi, I am a very non-savvy mailman list user. I am trying to set up a list via cPanel but when I send emails there are two signatures. One is my usual signature and the other, below, is appended by Mailman and includes an http link to a non-existent page on my website. How do I strip the auto signature, just leaving my own? > > I use Mailman via cPanel on two separate hosting accounts. One works fine and this new one attaches the list address. I can't see what I did differently with the first! Please see https://wiki.list.org/DOC/Mailman%20and%20CPanel That said, if you can go to the standard Mailman web admin UI, go to Non-digest options and ensure msg_footer is completely empty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

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

by Brian Carpenter

On 2/26/21 10:00 PM, Stephen J. Turnbull wrote: > Thank you for going to the trouble of making your guide easily > available to and usable by the community. You're welcome Steve. > 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. I agree. I just know there are probably a lot of folks who just want a working and current Mailman 3 server and are not picky over the actual server environment. Mailman 3 is really dependent upon being connected to a number of services: web server, database server and MTA for instance. Then you add in all of the required Python modules, and you have a really complicated system that has a lot of moving parts. I intend to explore other OS for installing MM3 and to document that process as well. I will not document the process of using package managers (apt/yum) etc to install Mailman 3 itself because I think it is very problematic having older versions of Mailman 3 set up. Mark Sapiro put it very well when he said: > Mailman 3 is still relatively young and there are many important > features and fixes in the current releases that aren't in the > Debian/Ubuntu packages. I hoping a guide such as mine will move folks away from using a Debian repo for Mailman installations. > 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. See that is something I am very interested in fixing and cleaning up but I need help in knowing how to work with something like Readthedocs.io. > 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. Exactly! > > > 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. So lift me up and throw me over that hurdle. > 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. "Raises hand here" -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: Unknown attribute: max_message_size

by Abhilash Raj

Hi Thor, On Wed, Dec 6, 2017, at 02:40 AM, Thor Atle Rustad wrote: > If I make changes here: > https://example.com/postorius/lists/test2.example.com/settings/message_acce…, > I get a warning that the Maximum Message Size field at the bottom is > mandatory. However, if I put a number in that field and save, I get > "Unknown attribute: max_message_size". That makes sense, since Mark > states > in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > that max_messages_size is not exposed in REST. I have opened a new issue for this, turns out this was fixed but isn't a part of the 3.1.1 bugfix release of COre. https://gitlab.com/mailman/postorius/issues/246 > What to do? > > I have Maxking mailman-docker but can easily copy files into the image if > necessary. > > Thor > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 7 months

[MM3-users] Re: Mailman3 on Debian 10

by Mark Sapiro

On 1/30/20 8:24 AM, Bala Mutyam wrote: > Hi Mark, > > Thanks for the update and I managed to resolve the errors on the UI. > > I have 2 more questions about the mailman3. > > 1) how to create Mailing Lists? You can create lists with the `mailman create` command lint tool or via Postorius as a superuser. > 2) super user login is not working even with correct login credentials and giving me - The username and/or password you specified are not correct. How did you create the super user? You should do it with the django admin createsuperuser command. > 3) Password Reset Email urls and email confirmation web pages giving me - This site can't be reached error. If this is an error from your browser, there is something wrong with the host portion of the URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Problem with redirection when entering alias without a / at the end

by Jens Günther

Hey there, I'm using Apache2 as the webserver, configured https://mailman.xyz.de as Web host. When I want to get to Mailman Starting Page now I need to Enter the following URL: https://mailman.xyz.de/mailman3/ to be directly redirected as expected to https://mailman.xyz.de/mailman3/postorius/lists/ -> works. Problem: When leave out the slash at the end and I ONLY enter the following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly redirected to a page, taht does not exist: https://mailman.xyz.de/mailman/postorius/lists/ -> 404 Where can I change this misbehaviour? In Apache-conf everything seems as it'S in the docs, for the vHost I do not have any other custom settings. Thank you in advance. By the way: Is there an easy way to redirect directly from https://mailman.xyz.de to https://mailman.xyz.de/mailman3/postorius/lists/ -> what would be a possibility for that?

4 years, 4 months

[MM3-users] Re: outgoing.py mailman@example.com issue

by dancab＠caltech.edu

Mark Sapiro wrote: > On 11/7/21 1:22 AM, Stephen J. Turnbull wrote: > > dancab(a)caltech.edu writes: > > I deployed Mailman3 last night and today we've had some "bounced" > > messages with headers referencing mailman(a)example.com. This has > > only happened with a few lists. Any ideas what causes this? > > ... > > Mark may have a better idea. > > This is a fake DSN that is generated when Mailman's attempt to send a > bounce probe results in a failure from the MTA to which Mailman > delivers. See code at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin... > and around > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin... We do have mailman(a)caltech.edu configured with valid members/owners. We're using Postfix for the MTA. Is it possible there's a misconfiguration there? We've been testing the system with a handful of lists for months. -- Dan

3 years, 8 months

[MM3-users] Warning on EL8: django-mailman 1.3.12 prefers Django 4.2 which requires Maria DB>10.4

by Jered Floyd

A heads-up for anyone else on RHEL 8, because the error is mystifying. django-mailman 1.3.12 bumps the preferred django version from 4.1 to 4.2. Django 4.2 requires MariaDB 10.4 or later. RHEL 8 has full lifecycle support for MariaDB 10.3. For some reason I haven't yet been able to identify, this causes pyMySQL integrations to fail with the mysterious error: django.core.exceptions.ImproperlyConfigured: mysqlclient 1.4.3 or newer is required; you have 1.4.6. (Yes, Database.version_info contains "(1, 4, 2, 'final', 0)" while Database.version contains "1.4.6" and I am totally stumped where that 1.4.2 is coming from as it appears... nowhere.) Bypassing that error check gives the more informative: django.db.utils.NotSupportedError: MariaDB 10.4 or later is required (found 10.3.39). Doing a pip install with django\<4.2 works. This is not ideal since 4.1 is past LTS, so I would recommend that Mailman systems be migrated to RHEL 9. --Jered

1 year, 3 months

[MM3-users] Re: Default values for lists in Mailman 3

by Markus Grandpré

Dear Mark, dear list, in Menu "Mass Operations / Mass Subscription" I have set the default value for checkbox "Invitation" in file </usr/lib/python3/dist-packages/postorius/forms/list_forms.py> (on Debian 12) as you had suggested: invitation = forms.BooleanField( label=_('Invitation'), initial=True, required=False, help_text=_( 'If checked, the other checkboxes are ignored and the users will ' 'be sent an invitation to join the list and will be subscribed ' 'upon acceptance thereof.' ), widget=forms.CheckboxInput(), ) However, administrators of mailing lists on our Mailman3 demo system report that the invitation is still sent, even if they have deactivated the sending of the invitation via the “Invitation” checkbox. What have I done wrong? Best regards, Markus Am 20.09.24 um 09:05 schrieb Markus Grandpré: > Thank you very much for your answer. > > Best regards, > Markus > > Am 19.09.24 um 22:03 schrieb Mark Sapiro: >> On 9/19/24 05:46, Markus Grandpré wrote: >>> Dear list, >>> >>> I would like to activate the invitation setting for all lists as >>> default. In Mailman 2.1 I have done this in the file </etc/mailman/ >>> mm_cfg.py>: >>> >>> >>> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >>> >>> >>> How can I do this in Mailman 3? >> >> There is a draft merge request at https://gitlab.com/mailman/ >> postorius/-/merge_requests/930 which implements a framework for >> setting Postorius defaults and creates a setting to set the default >> for pre- verified on the mass subscription page. Once merged, this can >> easily be extended to provide a default for Invitation. >> >> In the mean time, you can only do this by patching src/postorius/ >> forms/ list_forms.py like >> ``` >> --- a/src/postorius/forms/list_forms.py >> +++ b/src/postorius/forms/list_forms.py >> @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): >> >> invitation = forms.BooleanField( >> label=_('Invitation'), >> - initial=False, >> + initial=True, >> required=False, >> help_text=_( >> 'If checked, the other checkboxes are ignored and the >> users will ' >> ``` >>> Can I also transfer other default values like: >>> >>> ... >>> DEFAULT_SERVER_LANGUAGE = 'en' >>> DEFAULT_SEND_REMINDERS = 1 >>> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >>> DEFAULT_PRIVATE_ROSTER = 2 >>> DEFAULT_ARCHIVE = Off >>> DEFAULT_ARCHIVE_PRIVATE = 1 >>> ... >>> >>> from the very same configuration file to Mailman 3? Is there a >>> documentation of the default values for lists in Mailman 3? >> >> This is done by creating a list style with the desired defaults. See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/ >> styles/ docs/styles.html for documentation of styles and see https:// >> gitlab.com/ mailman/example-mailman-plugin for an example of creating >> a plugin in Mailman core to make a persistent style. >> >> There is no specific doc for the list settings. You need to look at >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/ >> base.py for the various settings and https://gitlab.com/mailman/ >> mailman/-/blob/master/src/mailman/styles/default.py to see which >> default classes are applied for various styles. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

10 months

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

by Ruth Ivimey-Cook

Stephen, On 6/22/20 6:23 PM, Stephen J. Turnbull wrote: > By design, Mailman core doesn't need to talk to the Internet or to the > secure internal network -- Internet functions are delegated to the MTA > and the webapps, and local configuration is via shell access which in > principle could be console. Sorry, I missed this earlier. Ironically I am doing exactly what you are suggesting -- splitting the django frontend web app from the mailman core. In my current case I have put the mailman core on the same host as my mailserver, but that was for the sake of simplicity while I got that split sorted -- I am using exim and there is a big benefit when exim can see the list directory names. I may eventually move mailman-core elsewhere. However, I find the mailman shell program not very intuitive, and so would prefer to have the web app for admin purposes. Regards, Ruth

5 years, 1 month

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

by Mark Sapiro

On 11/2/21 11:50 AM, bob B wrote: > So I am teaching myself to fish, and see that it is actually django-admin, so that is in > mailman-web? (in docker) > > But i get this: > > $ docker exec -it mailman-web /bin/bash > bash-5.0# django-admin shell > Python 3.8.10 (default, May 6 2021, 06:30:44) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import MailingList > Traceback (most recent call last): ... > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. Do what it says. I.e. run DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Odhiambo Washington

On Thu, Aug 8, 2024 at 11:19 AM IEM Network Operation Center (IOhannes m zmölnig) <noc(a)iem.at> wrote: > On 8/7/24 12:27, Odhiambo Washington via Mailman-users wrote: > > On Wed, Aug 7, 2024 at 11:52 AM IEM Network Operation Center (IOhannes m > > zmölnig) <noc(a)iem.at> wrote: > > > >> is a feature-request warranted, or am i worrying too much? > >> > > > > A feature to automate your migrations? Have you consulted ChatGPT yet? > :-) > > > > should i ?-P > > anyhow, i'm happy to say that my migrations have completed by now, and > my new instance is now running with mailinglists previously hosted on > either an MM2 instance or an older MM3 instance. > so far i have not discovered any problems (well, apart from xapian > eating all my (rather small, as this is only a VM) partition; but that > is of course not related to anything we discussed here). > > what i did was in a nutshell: > - create a dump of the database of the old mm3 instance (e.g. 'pg_dump > -Fc mailman3web') > - drop any existing databases from the new mm3 instance > - import the dump into the new instance > - run db migrations > - import pck files from the old mm2 instance > - import archives from the old mm2 instance > > > thanks again, Odhiambo and Mark for your hints! > > > > however, i can report that my fears about migrating between mm3 > instances by means of DB dumps have (at least partially) become true. > 0. i'm using mailman3 as packaged in Debian, and PostgreSQL as the > backend. before running the actual migrations, i've experimented a bit > on the new instance (creating and deleting test lists), to see if the > core configuration is working as expected. so i already had the > databases up and running, filled with a bit of data, before attempting > the migrations. > > 1. for whatever reasons, the db-names have changed between 3.2.1 > ("mailman3", "mailman3web") and 3.3.8 ("mailman3.db", "mailman3web.db"). > i strongly suspect that this is a problem of the Debian packaging of > mailman3 (i'm pretty sure that i only ever accepted the defaults when > installing the mailman3 Debian packages). > As you've rightly discovered, that issue can only be addressed by the Debian package maintainers. > 2. since the db names changed, i tried to be clever (but i'm not a > knowledgeable postgreSQL admin) and tried to only import the data-part > of the dump ("pg_restore --data"), re-using the existing tables. > this of course miserably failed. > I suspect failed because of the schema differences from 3.2.1 to 3.3.8. Well, I am also NOT experienced with PgSQL administration, but I think that for data to be imported from one table to another, the column definitions MUST match. 3. my next attempt to import the data into an existing DB, was to rename > the new db to the old name, import and rename back. > this also failed miserably, most notably because the import insisted on > assigning key IDs that were already in use. (that is: because i had > already created and tested test-lists, the new instance already > contained an email with hyperkitty_email.id=1; the dump from the old > instance also contained an email with hyperkitty_email.id=1; so the > import failed. this example is made up from memory, as i have not kept > all the error logs). > so this also failed. > That is expected. Maybe you could have vacuumed the tables completely. 4. i ended up, deleting the entire database, and import it from scratch. > after that, ran 'mailman-web migrate' to update the DB schema to the > current one. > this again failed with one hyperkitty-related migration that would > create new tables. > it turned out, that the new hosts uses postgreSQL-15.7.0 (the old one > uses postgresql-11), and afaik since psql15 only a database *owner* can > create new tables. after i made my mailman3-db-user the owner, all > migrations succeeded. > That's a known issue here already. Something to do with access privileges to the SCHEMA public. > 5. finally i imported my mm2 mailinglists and archives, which went > rather smoothly. > Sure. The only issue people have had with that was to do with some small inconsistencies in the archives. There is a tool that can be used to check the archives and fix such. some of my problems obviously come from me not being a DB-manager by > profession (e.g. new constraints in psql15,...) > but others, like "3.", seem to hint at a core problem in the suggested > migration strategy: if the to-be-imported db contains unique-keys that > are already taken, the import simply fails (or at best, you get a > partial import). i do not see how such a migration can ever work if you > try to merge to mm3 instances where the dbs have a considerable amount > of entries in the same tables (as you will always get constraint > conflicts). > And that is the point that I did not reach/go beyond when I talked about having consistency in the DBs. But if the destination server had no lists, then it would probably not have been too difficult. Again, that's stuff for DB deep-dive. > to summarize, migrations must: > - *first* import old mm3 data into an *empty* database > (so you cannot import multiple mm3 instances into a single new one) > - import mm2 data afterwards > I believe there is a way around that because I recently did import an ML from one site to a live site. hence my idea for a special export/import format (and command), that > would only contain the actual structured data, but without all the extra > db-specific things (like unique ids for referencing between tables). > Oh, yes! I am sure the Developers will be happy to get such a tool as a contribution from the community. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months, 3 weeks

[MM3-users] Re: Your Dashboard

by Mark Sapiro

On 2/11/20 1:27 PM, Allan Hansen wrote: > > Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. > > Time to visit gitlab? GitLab is the one place for feature requests for Mailman 3/Htperkitty/Postorius. Things requested in list posts get lost and forgotten. That said, the more specific you can be in a request, the better. I.e., if you want a dashboard, what do you want on it for, e.g., the site admin, a user who may or may not be an owner of a couple of lists, a moderator of a couple more and a member of still others. -- 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: unknown encoding: windows-874

by Stephen J. Turnbull

Mark Sapiro writes: > Python doesn't recognize windows-874 as known charset. iso-8859-11 is a known character set for Thai, with a few missing punctuation marks. If the message turns out to be not Thai, but mostly ASCII with a few broken characters that are probably punctuation (including directed quotes, ellipsis, and the EURO SIGN), any Windows-12xx character set (IIRC, Windows-1252 is closest to Latin-1) should have those in the same positions. > You can move it aside, and if it looks like something you actually want > to archive, you might be able to fix it, but that's tricky. The file in > var/archives/hyperkitty/spool/ is I think a pickled email message > object. You can view it with `mailman qfile`, but editing is tricky. If any of the above codecs seem to work, just editing the charset parameter in Content-Type header(s) should do the trick. Sorry, can't help with the editing process itself, though. Steve

5 years, 2 months

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 3:53 PM, maszap(a)tin.it wrote: > Hi, > > I added the line to the main.cf file > > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains > > In my log MTA mail.warn I get: > Jul 13 00:44:56 gamelia postfix/trivial-rewrite[8317]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains What's in your mail.log for a message to and from the list? > I check > my /var/log/mailman3/smtp.log > but is empty If Mailman is sending any mail at all, there should be entries in smtp.log unless the log level is higher than info. What does mailman conf -s logging.smtp show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: per domain SITE_ID views?

by David Newman

On 12/28/21 1:30 PM, Mark Sapiro wrote: > On 12/28/21 1:14 PM, David Newman wrote: >> Using FILTER_VHOST, I have two domains set up and working with MM3, >> Postorius and Hyperkitty. However, because SITE_ID in settings.py >> points to one of the domains, that domain name always appears on >> Postorius and Hyperkitty pages. > ... >> How to get the correct domain to appear on that domain's Postorius and >> Hyperkitty pages? > > > I don't think the domain is actually displayed on Postorius pages. You are almost certainly correct. I saw dom1.tld on a login page, but hadn't realized that login page comes from Hyperkitty and not Postorious. > If > I'm wrong, on what Postorius view do you see it? As far as HyperKitty is > concerned, please file an issue for this at > https://gitlab.com/mailman/hyperkitty/-/issues/new Opened an issue here: https://gitlab.com/mailman/hyperkitty/-/issues/404 dn

3 years, 7 months

[MM3-users] Re: Detectors and Bounces

by Mark Sapiro

On 8/5/22 11:12, summersan(a)nclack.k12.or.us wrote: > > Thank you for refocusing the issue in terms of the "large numbers of bounces", too. > > Here is what I have in `mailman.cfg` for the `[mta]` section: > > `[mta]` > `verp_confirmations: yes` > `verp_personalized_deliveries: yes` > `verp_delivery_interval: 1` > > Does this help narrow down the problem any further? Not really. You need to see why you are getting these bounces. What's in Mailman's bounce.log? Are bouncing users getting their delivery disabled? What are your list(s) `Bounce Processing` settings. In particular, if you set all the `Notify owner ...` settings to `Yes` and `Forward unrecognized bounces` to either `List Admins` or `Site Admin`, what do you see? Also, if there are queued bounces in `/opt/mailman/mm/var/queue/bounces`, you can examine them with `/opt/mailman/mm/bin/mailman qfile` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: IndexError in archiving queue

by Mark Sapiro

On 3/16/23 04:13, Jacob Sievert via Mailman-users wrote: > Hello, > > it seems I have forgotten where I can kick an email out of the archiving > queue as it produces this error in a loop. > Might one of you know where I can do that? > Thanks in advance. The underlying error is a bogus Message-ID header in the message. We have observed cases of Message-IDs like Message-ID: <[d1e99408882e4aed93b0df4c1c28dfa3-JFBVALKQOJXWILKNK4YVA7COOVDWK5D4IVWWC2LMKB2WE3DJONUGK4T4IV4G6U3NORYA====(a)microsoft.com]> where the `[` and `]` are the problem. See the report at https://gitlab.com/mailman/mailman/-/issues/732 and fix for that at https://gitlab.com/mailman/mailman/-/merge_requests/1099 I would like to see the headers of the message in your case. To answer your question, the offending message is queued in Mailman's var/archives/hyperkitty/spool/ directory and can be examined with Mailman's `mailman qfile` command. -- 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: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Thanks for your advice, Stephen. As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. I've confirmed the error is not cached in the browser. If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? Cheers, Simon. ________________________________ From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Monday, 31 August 2020 23:51 To: Simon Handfield <simon.handfield(a)sl.nsw.gov.au> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius Simon Handfield via Mailman-users writes: > I have been able to identify a file in the shunt queue that threw a > matching error when I performed mailman qfile on it. > I have run a loop over all remaining files in the shunt queue and > all the remaining files can be accessed by mailman qfile without > error. Good. But there are still a bunch of problems with those files since they got shunted. > I moved this file out of the queue in the hope that I would then be > able to load the held_messages page successfully. Unfortunately I > am still seeing a 500 error on loading the page. If this is a Mailman problem, I don't understand it. The shunt queue is not the moderation queue. The shunt queue is for messages that Mailman cannot handle without throwing an exception. Once a message is sent to the shunt queue, Mailman ignores it, so it shouldn't cause problems for the moderation page. Have you tried restarting Mailman since moving the qfile? If that doesn't work, and if it's the same error message and traceback, the easy suspect is browser caching (although we should be disabling that, I hope). Try a manual refresh (usually Ctrl-R or in the menu). If that doesn't work, try a private browsing window or another browser if you don't want to clear the cache or restart the browser. > I temporarily reenabled debug logging to confirm that the same > error was being thrown. > > Assuming that file was the cause are there other steps I need to > perform in addition to removing the file from the shunt queue > directory? The only one I can think of is the check for browser-side caching. Unfortunately, Mark's out of town (like, on top of a mountain with no bars on his phone), and I am not going to be able to do much with this until Thursday at the earliest. If you do get a new traceback, post it here (somebody else may have an idea). If you like you may send me the qfile at the address in From. I'll see if I can reproduce the bug, and I'm pretty sure I can tell you what's in the file so at least you'll know whether it's important to somebody who isn't a scammer/spammer. Steve _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

4 years, 10 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, you > can set max_message_size in your list configuration. It defaults to 40; > units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- 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] duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

Hi I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: client.create_domain(name) Is this a bug? Or did I mess something up? What significance do those SITE_IDs have? What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Thanks! Stanisław

3 years, 4 months

[MM3-users] Re: Postfix-Fehler mit mailman-web

by Stephen J. Turnbull

Jens Günther writes: > 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: > reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host > rejected: cannot find your hostname, [192.168.176.6]; > from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP helo=<mailman-web> There are a bunch of $myxxxx variables in Postfix, I think $myhosts might be the right one. If you add the IP 192.168.176.6 to that variable, it will be whitelisted and this problem should go away. There may be better ways to handle this, but don't mess with hostnames. Find the "right" way to permit that IP should do the job. > I mean the hostname for the core-container must be there, since > mail is accepted :-D That's not the way this works. Postfix accepts the mail because it's arrives at the physical host, then looks up routing for the mailbox and discovers it should be delivered via LMTP to the core container's IP. No hostname needed. Steve

1 year, 11 months

[MM3-users] Re: Mysterious Bounces Being Logged

by Mark Sapiro

On 3/26/21 8:51 PM, Brian Carpenter wrote: > On 3/26/21 6:13 PM, Mark Sapiro wrote: >> Absolutely. At first MM3 wasn't processing bounces at all. A GSOC >> student did the bulk of the current implementation and we were happy >> to get that even though this piece was missing. We know we need it. If >> you don't think we're working fast enough, you can submit a merge >> request or dock our pay. > > I don't understand the sarcasm here at all. I am just trying to figure > out what the PRIORITIES are from the Mailman 3 developers. That's all. > BTW, I still haven't figured it out. OK, the "dock our pay" remark was uncalled for, but I was only trying to point out that for the most part, all of this work is being done by or in some cases mentored by Abhilash and me, and we are both volunteers with other responsibilities. This is a known issue <https://gitlab.com/mailman/mailman/-/issues/737> posted by me 8 months ago. There are no offers to help work on it, nor are there any comments to the effect that this should be higher priority than any of the 307 other open Mailman core issues in the tracker. I can't speak for Abhilash, but my priorities are fix things that are trivial to fix as they arise and work on the harder stuff as time and interest allow. I realize that doesn't help you much, but I'm a volunteer. This is (one of) my hobbies. If it's not fun or at least satisfying, I won't do it. > It still doesn't explain why Postfix is not recording the delivery > issues which I assume has nothing to do with Mailman 3. I see successful > deliveries with Postfix and bounces with Mailman 3 core. I never seen > that with Mailman 2 and Exim. They always matched. If you can help me to > understand that with out the petty sarcasms then that would be great. If > not, then ok. I don't know why you never saw this with MM 2.1 and Exim. Possibly because MM 2.1 sent you the DSN with the admin notification, you never looked. I told you in my initial reply in this thread "They are being bounced by a downstream MTA." To elaborate on that, Mailman's MTA be it Postfix, Exim or whatever, attempts to deliver the mail to the MX of the recipient domain. Sometimes this results in a 5xx status which is logged and reported as a bounce to the sender, i.e. the LIST-bounces address. Sometimes it results in a 4xx status which will cause the delivery to be retried at intervals until it is either accepted or exceeds a configured lifetime and is reported as a permanent failure. The rest of the time, the delivery succeeds, but that is only delivery to the MX for the domain. It may be that for that recipient, that MX is a relay to another MX in the delivery chain, and sometimes, either quickly or after some delay due to retries downstream eventually timing out, the ultimate delivery fails and a DSN is returned to the original envelope sender which is the LIST-bounces address. If you look in the Postfix logs around the time that Mailman recorded the bounce, you should see an incoming message from=<> (DSNs always have a null envelope sender) and to=<LIST-bounces(a)list.domain> or if you are VERPing to=<LIST-bounces+recip=recip.domain(a)list.domain> which is the DSN being returned by the downstream MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: pending subscriptions lost?

by IEM Network Operation Center (IOhannes m zmölnig)

On 3/14/22 17:03, Mark Sapiro wrote: > On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman > 3.3.5. thanks for comfirming. > > >> - i (as administrator) do not see any "pending subscriptions" (the >> list is setup with a simple "Confirm" subscription policy > > The count badge only counts subscriptions waiting moderator approval. If > you pull down the Subscription requests tab and click Pending > Confirmation you should see them and be able to discard them. hmm. i'm not sure i can follow. my "Subscription requests" tab seems to not have any "Pending Confirmation" section (see attached screenshot). this is with "Postorius Version 1.2.4" (as installed by the mailman3 Debian package). fdsm< IOhannes ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Subscription requests.png

3 years, 4 months

[MM3-users] Editing the "example.org" site

by Stephen J. Turnbull

Hi all, I don't know how many people will need this, but I just realized that you can edit Django's SITE 1 and (probably, 100% untested but I'm going on the clock so want to get this done quick :-) use that. When you add your first domain, there's a link in that page (not a button, a link!) to edit the domain list. Then you can click on the link to "example.org" in the list, and edit both display name (which I assumed) and the domain name. Maybe I'm just slow, but I've been adding SITE 2 = "Whatever site <whatever.tld>" the whole time. :-) But then you have to edit the SITE = 1 statement in settings.py (which I often forget and hilarity ensues). Of course adding a web site and editing settings.py (which you have to do anyway for other variables) works too, but this seems cleaner to me. Steve

1 year, 7 months

[MM3-users] Re: Ann: Mailman Core 3.3.5 is out

by Eggert Ehmke

Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would have to bypass the Debian installer. Or will there be Debian packages available? Same question for Postorius 1.3.6 Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb Abhilash Raj: > Hey Everyone, > > I just tagged and uploaded Mailman Core 3.3.5 release. > > This release includes both bug fixes and some new features. A full list of > changes is available here: > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS. > html#news-3-3-5 > > You can install this version using pip: > > $ pip install mailman==3.3.5 > > The release tarball is available on PyPI as well: > > https://pypi.org/project/mailman/3.3.5/#files > > Thanks to everyone who made this release possible! > > Abhilash > > > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > > > > Hey Everyone, > > > > I just tagged and released Mailman Core 3.3.5rc1 release. > > > > This is identical to 3.3.5b1 in code, the only changes that have been made > > are in utility scripts and testing configuration.> > > You can install this version using: > > $ pip install --pre mailman==3.3.5rc1 > > > > If you want to download a release tarball, you can do so from here: > > https://pypi.org/project/mailman/3.3.5rc1/#files > > > > This is the first (and only) planned release candidate for 3.3.5 release. > > The stable release is planned for next week. > > > > thanks, > > Abhilash > > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: > >> Hello Everyone, > >> I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a > >> pre-release for 3.3.5, which is slated to come out in 3 weeks from now. > >> I am planning for a 2 week beta period, after which I'll release the > >> first RC and then stable a week after. Right now I am not planning to > >> release a second beta version, but if there are several changes in Core > >> in the next week or so, then I might. This release includes a lot of bug > >> fixes and some new features. It also includes a security enhancement > >> that improves the authentication of REST API by adding resistance to > >> some timing channel attacks. A full list of changes in this version can > >> be found here[1]. > >> [1]: > >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NE > >> WS.html#news-3-3-5 We have also made improvements in the i18n workflow > >> and now the email templates are updated from the translated messages in > >> the .po files that we get from Weblate. Documentation for translators is > >> available here[2] if you want to help translate Mailman into your native > >> language. [2]: https://docs.mailman3.org/en/latest/translation.html > >> > >> This is a pre-release version, if you want to test it with your setup, you can install it using: > >> $ pip install --pre mailman==3.3.5b1 > >> > >> If you want to download a release tarball, you can do so from here: > >> https://pypi.org/project/mailman/3.3.5b1/#files > >> > >> This release received a lot of contributions from community, which I am > >> really happy about! I'd like to thank everyone who made this release > >> possible!> > > -- > > thanks, > > Abhilash Raj (maxking) > > -- > thanks, > Abhilash Raj (maxking)

3 years, 10 months

[MM3-users] Re: OperationalError: database is locked

by Cyprian Laskowski

Thanks for your feedback again. It turned out that upgrading our components to the listed 3.1 suite versions *and* fixing permissions on /var/www/.cache helped significantly. We still get database locked errors, but much more sporadically, and the application is more responsive in general. However, we haven't been able to switch to postgresql. We did do a django "migrate" for sqlite due to the new version, but when we then backed up the sqlite and tried to load it into the new postgresql database, we get: hyperkitty.models.email.DoesNotExist: Problem installing fixture '/opt/mailman/mailman-suite/mailman-suite_project/dump_sqlite_updated.json': Email matching query does not exist. Interestingly, this seems to be the same error as perhaps the most common one in our uwsgi-error.log (see my previous message), which is still seeing constant activity. Any suggestion of how to overcome this? I have tried to compare our settings to the example ones, and haven't found obvious culprits, but I will take a closer look.

7 years, 6 months

[MM3-users] Upgrade Mailmam Core from

by sascha.rissel＠gmail.com

Hello, I have newly set up Mailman 3 on Ubuntu 20.04. Sending and receiving mails between list members does work, but I am currently experiencing two issues: 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. 2) Archiving is activated within list settings, but there isn't any archive created. I found this thread, where the first of these issues is also described: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. I am running Mailman 3.2.2 on Python 3 .8.10. So I need to either upgrade Mailman Core or downgrade Python. I already did > apt-get upgrade > apt-get update Unfortunately this didn't upgrade Mailman Core's version. Which steps do I have to undertake to upgrade Mailman Core? Regards, Sascha.

2 years, 10 months

[MM3-users] Re: Default setting for Delivery status

by Mark Dale

>> Where and how do I set the default setting of "Delivery status" to be "Enabled". > > It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… >> At the moment, a new subscriber is neither "Enabled" or "Disabled". > > That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. > > Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. > > New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. > Ahhhh. Thanks very much Mark. I did some experimenting to get my head around what you've explained and I can see how it works now.

2 years, 9 months

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

by Mark Sapiro

On 1/9/23 05:31, Johannes Rohr wrote: > > Thanks! I assume, there is a reason why this cannot be easily > implemented, else it would have been. Asking because I know a number of > people would make extensive use of this in MM2. The actual implementation is probably not difficult, but it's more than just handling things like `@list_id` in *_these_nonmembers. It also requires developing appropriate unit tests, updating REST and `mailman import21` to accept the syntax and documentation updates at least for Postorius Settings -> Message Acceptance -> * these non-members. That adds up to a significant amount of work. I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

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

by Mark Sapiro

On 11/18/24 23:13, mark(a)suburbia.org.au wrote: > - Modified second test user to "Hold for moderation" in Members list. Noted the Moderation was set to "List default" before changing it to "Hold for moderation" The actual value is None, but Postorius displays/sets that as List default. >> If that is true, I can only think that at the time of that post, >> settings weren't as they are now. > > I think for now I will have to assume that's the case, until the next email can be readied against the proper list. If you hear nothing further, assume that this was all based on some random quirk (by humans or machines). I'll update if it happens again. Thank you for doing the test. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

[MM3-users] Re: cannot bind to lmtp host address through lmtp port(OSError: [Errno 99] error while attempting to bind on address: cannot assign requested address)

by Mark Sapiro

On 10/18/22 11:28, Paul Ssekamatte via Mailman-users wrote: > i have successfully set up mailman3 instance by following the guide at https://gitlab.com/mailman/mailman-suite-doc/blob/master/source/install/vir… and from this mailing list. > my setup uses an alias domain i.e the mail server is different from the lists server. That is not what alias domains are for. You do not want an alias domain. > I have successfully created an alias domain and mailing list through Postorius but I keep getting this error in syslog. > OSError: [Errno 99] error while attempting to bind on address ('xxx.xx.xx.xx', 8024): cannot assign requested address. > Even when I change the port number, I still get the same error > Kindly assist. First, remove the Alias Domain from your domains. > here is my mailman.cfg config > [paths.here] > var_dir: /opt/mailman/mm/var > > [mailman] > layout: here > site_owner: postmaster(a)mail.example.com > > [database] > class: mailman.database.postgresql.PostgreSQLDatabase > url: postgres://mailman:#passwd@localhost/mailman > > [archiver.prototype] > enable: yes > > # For the HyperKitty archiver. > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > > [shell] > history_file: $var_dir/history.py > > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com The above is wrong. You want the default lmtp_host: 127.0.0.1 > lmtp_port: 8024 > smtp_host: mail.example.com smtp_host should be the mail server, not the list host. Is it? > smtp_port: 25 > configuration: python:mailman.config.postfix These next 3 do not belong in mailman.cfg. They are Postfix main.cf settings: > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no and this next one is a Mailman 2.1 mm_cfg.py directive and is not for Mailman 3. > POSTFIX_STYLE_VIRTUAL_DOMAINS= ['example.com'] > > /etc/mailman3/settings.py file is as follows not relevant for this issue. > /etc/postfix/main.cf is as follows > smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) > biff = no > append_dot_mydomain = no > readme_directory = no > compatibility_level = 2 > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > mydomain = example.com > myhostname = lists.example.com > mydestination = $myhostname, localhost.$mydomain, localhost > relayhost = mail.example.com > myorigin = $mydomain > mynetworks = 127.0.0.0/8, 10.0.0.0, 192.0.0.1, [::ffff:127.0.0.0]/104 [::1]/128 > mynetworks_style = subnet > mailbox_size_limit = 4096000000 > #message_size_limit = 2048000000 > recipient_delimiter = + > inet_interfaces = all > #inet_protocols = all > inet_protocols = ipv4 > unknown_local_recipient_reject_code = 550 > owner_request_special = no > virtual_mailbox_domains = example.com You probably don't want this, at least not if the mailman server is example.com > virtual_mailbox_base = /var/vmail > virtual_uid_maps = static:20000 > virtual_gid_maps = static:20000 > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap and you don't want this virtual_alias_maps. > postfix domains as follows: > lists.example.com example.com > > postfix lmtp as follows: > testlist(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-bounces(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-confirm(a)lists.example.com lmtp:[mail.example.com]:8024 The host in lmtp: is the Mailman server. > postfix vmap as follows: > testlist(a)example.com nmutest(a)lists.example.com > testlist-bounces(a)example.com nmutest-bounces(a)lists.example.com > testlist-confirm(a)example.com nmutest-confirm(a)lists.example.com You don't want that at all. -- 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] Where to put static files referred to from list Info page?

by Greg Newby

Hi friends. Some of my version 2.1 lists had some static files that were referenced from the list's HTML pages. I'd like to do the same for the lists now that they're ported to MM3. My question: Is there a place I can put these files within the Mailman directory hierarchy so they can be linked from the list Info page? I.e., under "Settings / List info / Long description" I'd like to include a <a href=...> to a file that's somewhere in a persistent location in the same directory tree as the Mailman web. I tried putting it under mm/var/lists/listname/ (where 'listname' exists, and is where templates go. This yielded a '404.' I confirmed I can add an href to the Long description, but don't know where in the Mailman3 directory hierarchy I can put the files. Thanks! Greg Newby

11 months, 3 weeks

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

by Stephen J. Turnbull

via Mailman-users writes: > Now I have: > > -rwxr--r-- 1 list list 0 Oct 10 2018 list:member:generic:footer.txt* > -rwxr--r-- 1 list list 0 Mar 30 2021 list:member:regular:footer* > -rwxr--r-- 1 list list 507 Jan 9 01:35 list:user:notice:welcome* > -rwxr--r-- 1 list list 506 Jan 15 04:45 list:user:notice:welcome.txt* LGTM, not sure why the issue persists. Have you checked that group and world have 'x' (directory search) permissions on every directory in the path to these files? (This is unlikely to be the problem but it's easy to check.) And it shouldn't matter but those files themselves don't need 'x' (execute) permission. Pretty sure the existence of the .bk file has nothing to do with this problem. Evidently you don't need it this time, but in the future you needn't hesitate to keep backups around if they would be useful. Steve

6 months, 2 weeks

[MM3-users] Re: ARC issues

by Mark Sapiro

On 3/2/20 7:45 AM, Stephen J. Turnbull wrote: > David Krantz writes: > > > Is there any known issues with ARC that I should be aware of? > > Doesn't Postfix do ARC yet? :-( rspamd seems to be recommended by a > couple of Linux distros, supports the milter interface that Postfix > uses to call out to 3rd party processes, and the website looks good. > See rspamd.com. That said, if you want to use Mailman's support... I've been trying openarc <https://github.com/trusteddomainproject/OpenARC> with Postfix as well as Mailman's ARC. I still haven't got it all worked out - I have a fairly convoluted mail flow with the possibility of messages being altered before they ever get to Mailman. There is an issue with Mailman's ARC signing in a supporting library. See <https://github.com/ValiMail/authentication-headers/issues/5>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] non-members issue with held email

by Lars Schimmer

Hi I want to check a issue with a few mailing lists of us. We do run mailman3 on debian with debian package 3.2.1-1 (not yet updated for backup reasons). We created a new mailinglist, added 3 owner and several members. Now we want some email addresses to post to that list but not receive mails from the list. So I added those to the "non-member" area of the mailinglist and checked every non-member to "acceppt at once". But on a test, a email address, which is owner AND non-member, cannot send to mailinglist, always get a "HOLD: ...... The message is not from a list member" The Email address in that HOLD log entry is the same as in the owner/non-member list. Any idea howto check the mailman3 logs for this case? Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years

[MM3-users] Suggeested change to the venv installation instructions

by Bill Oliver

Well, I'm now on my third installation of mailman3. I ran into a problem I had forgotten about but once I figured it out, *then* I remembered running into it last time. Configuration: Ubuntu 24.04 ib a vos, It's this. I'm a mysql person, not a postgres person, but I installed postgres for this installation just so I could follow the instructions directly. Whenever I tried to start the mailman service, I got the error that mailman didn't have permission to do whatever needed to be done. The error was: psycopg2.errors.InsufficientPrivilege: permission denied for schema public After a little searching, I found out that mailman needs to be made the OWNER of the database, not just granted all privileges. After adding the commands: ALTER DATABASE mailman OWNER TO mailman; ALTER DATABASE mailmanweb OWNER TO mailman; I suggest adding those two lines to the instructions for "Setup Database" at https://docs.mailman3.org/en/latest/install/virtualenv.html billo

8 months

[MM3-users] Re: Shunt Error Mail?

by Mark Sapiro

On 3/2/21 2:52 PM, Pete Ashdown wrote: > I have a number of list managers with subscribers who are confused as to > why their messages are silently disappearing. I've read the archives on > how to decipher why a message was shunted, but this is not workable at > scale. Is sending an error email back to the sender a consideration? Why are messages being shunted? Each shunted message has thrown some kind of uncaught exception which is logged with a traceback in Mailman's mailman.log. These should be due to bugs that should get fixed or possibly malformed messages which are almost always spam. In short, under normal circumstances messages should not be shunted at all and when they are it is something the site admins need to address. It is normally not something the sender of the message can do anything about. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] changing the main template for subscriptions and more

by Jens Günther

Hey there, in Mailman2 there was a simple link in the moderation-emails, with which I was able to open directly the "held-messages". I know how to manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) But: How can I change the template for all the lists (respectively maildomains/webdomains) so that I don't have to do this manually for all lists? I searched a bit for the corresponding template, but didn't find it. At the end it only says the following: "At your convenience, visit your dashboard to approve or deny the request." -> here I would like to add the following: "At your convenience, visit your dashboard to approve or deny the request: https://$domain/postorius/lists/$short_listname.$domain/held_messages" Or if someone sees another possibility to get us on the right track, it would be more than welcome, thank you! Kind regards, Jens.

4 years, 1 month

[MM3-users] Re: External Mail-Server?

by Jörg Michael Schulz

Hi, yes, this should be possible. See the parameters in your mailman.cfg: [mta] # The class defining the interface to the incoming mail transport agent. incoming: mailman.mta.exim4.LMTP #incoming: mailman.mta.postfix.LMTP # The callable implementing delivery to the outgoing mail transport agent. # This must accept three arguments, the mailing list, the message, and the # message metadata dictionary. outgoing: mailman.mta.deliver.deliver smtp_host: mail.yourfavoritedomain.de smtp_port: 25 smtp_user: smtp_pass: Am 11.09.21 um 19:53 schrieb Florian Schulze: > Hi! > > Is it possible to use an external Mail-Server? Does mailman3 support > that directly, or would I have to setup a local MTA which somehow > fetches incoming mails from the external inbox and uses the external > Mail-Server for delivery? > > Does anyone do that and have example configurations? > > Regards, > Florian Schulze > _______________________________________________ > 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] How to delete user completely?

by Stephen J. Turnbull

William Oliver writes: > I have installed mailman3 and it's up and running great. However, I > noticed that, during a mass subscribe, I mis-typed an address, e.g. > name(a)domain.ned rather than name(a)domain.net. I found how to unsubscribe > the bad address, but I haven't found a "delete" option under Users or > anywhere else. How to I purge a user from the users list? For the record and the general audience (I assume you've already replaced the bad address with the correct one, and then deleting the User with the bad address is a perfectly good way to do it), especially in the case where you've done other configuration of that User (this would be rare as far as I can tell, but I can imagine somebody flipping all the metoo bit with a withlist script or similar), you might want to add the correct address and delete the bad one to the User. Steve

3 years, 6 months

[MM3-users] Re: LDAP/Krb5/SAML auth for Mailman

by Simon Hanna

On November 7, 2017 6:20:16 PM GMT+01:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: > >Can anyone share some information on LDAP/Krb5 or better yet SAML auth >implementation for Mailman. Is it just adding appropriate auth module >to >DJango project or is there more involved things? This depends on what you want to do. If you just want to allow people to login to postorius and hyperkitty (the web UI) then you need to just add them to django. The cleanest approach would be to implement a socialaccount provider if that is possible. It should probably also work if you just add whatever you want to authentication providers in django itself. I'm not entirely sure if we assume that email addresses in django are verified by default or not.... Since there were a couple of requests for ldap, this might even be a candidate for a merge request.... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

7 years, 8 months

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

by bob B

So doing some more digging it looks like the mailman-core is not listing on 8024 docker logs mailman-core shows *********************** srv: AsyncServer = self.loop.run_until_complete(srv_coro) File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete return future.result() File "/usr/lib/python3.8/asyncio/base_events.py", line 1463, in create_server raise OSError(err.errno, 'error while attempting ' OSError: [Errno 99] error while attempting to bind on address ('::1', 8024, 0, 0): address not available [root@bmimailmandr1 docker-mailman]# netstat | grep 1024 *********************** I also see nothing on port 8024 on the docker host (just incase that causes a conflict) if I get into the mailman-core image I so not see anything listing on port 8024 ************************** bash-5.0# netstat -l Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 mailman-core:8001 0.0.0.0:* LISTEN tcp 0 0 127.0.0.11:34093 0.0.0.0:* LISTEN udp 0 0 127.0.0.11:59940 0.0.0.0:* Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node Path bash-5.0# *****************************

3 years, 11 months

[MM3-users] Re: set a new default for max_message_size

by Abhilash Raj

> On Apr 22, 2022, at 13:09, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 4/22/22 12:28, Paul Paulchen wrote: >> According to the answer of Mark you can change the "/usr/lib/python3/dist-packages/mailman/styles/base.py" - mlist.max_message_size. >> Now time went by, is there a possibility to use the mailman.cfg to set a new default? > > > No. It still is not configurable except by patching or creating a new style, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… It is however possible to create new Styles using Mailman plugins, without having to patch Mailman. We have an example style that demonstrates how to do that: https://gitlab.com/mailman/example-mailman-plugin/-/blob/master/example_mai… The repo’s README has more details on how to create and install the plugin. There is more documentation about plugins in Mailman Core’s docs: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… -- thanks, Abhilash Raj (maxking)

3 years, 3 months

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

by bob B

Today was the 2nd time mailman stopped sending out mail, it receives mail but sends nothing out. To resolve the issue I restarted the mailman services and then all the incoming/queued mail was sent out... last time this happened was 21 days ago.... Before that, it has been rock solid for years. We are running in a docker environment with no recent changes. On the host in /var/log/maillog, I see the mail coming in and going to mailman in docker. for docker, the mailman logs are in /opt/mailman/core/var/logs in /opt/mailman/core/var/logs/smtp.log ---------- I see the messages coming in /opt/mailman/core/var/logs/debug.log ------------ is empty /opt/mailman/core/var/logs/mailman.log -------------- I do not see anything that looks like it had an issue So where can I look to try to determine a cause? If it happens again, what and where can I cook to troubleshoot before restarting the service? Thanks

1 year, 4 months

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

by Stephen J. Turnbull

Daniel Armengod writes: > I'm not comfortable with posting specific names on a public mailing > list (that's tantamount to self-advertising), Your comfort level is up to you, and being reticent until you've established a strong record as a good Mailman citizen is the way I'd do it. :-) However, we've long been comfortable with minimalist self- advertising (ie, a one-liner of "I provide hosting services including Mailman at X Co." or "I recommend X Co, who I consult for") on list when somebody asks (especially in combination with a long helpful post ;-) And we also have pages on the wiki explicitly for Mailman service providers and consultants. I don't think it's a good idea for third parties to list others there, but feel free to tell anyone you would recommend to potential clients to come to us to get listed (you need an account on the wiki to post there). Steve

5 years, 5 months

[MM3-users] Re: Announce Only List

by Stephen J. Turnbull

Mark Sapiro writes: > On 8/13/20 9:49 AM, joseverde(a)gmail.com wrote: > > So if we want to make a list announce only (e.g. only specific > > folks) can post, I've found I can set the list settings to > > automatically discard messages from members and non-members. Then > > I go into the individual permissions on each user to be allowed > > to post without moderation. This works fine, however it seems > > cumbersome. Don't we have a list style for announce lists? If we don't, we should.... I don't see what's "cumbersome" about the individual permissions. You need to do *something* per allowed user, if only sending email to their individual addresses to tell them the password in the anternate method: > There is an alternative. Set a moderator_password for the list. Then > anyone can successfully post with an `Approved: <password>` header or > pseudo header if they know the password. Steve

4 years, 11 months

[MM3-users] Recently redeployed mailman3 and then received huge amount of subscription disabled notification emails

by francesd919＠gmail.com

Hi everyone, I recently redeployed our mailman3 server. As the owner for one of our mailing lists, I received a huge amount of subscription disabled notification emails. These emails mentioned that the subscription was disabled due to bounce score. Furthermore, we received a few emails from our subscribers saying that they have functioning email addresses and not sure why there were bounces and that their subsctiptions had been disabed. I have some questions: 1. Why do mailman mass send out subscription disabled notification emails to admins after it's been redeployed? 2. I have "Bounce disable warnings" set to 3 and "Bounce disabled warnings interval" set to 7d. How come there are still so many emails seem to be disabled but not unsubscribed? Hence we receiving so many subscription disabled notification emails. 3. What could have cuased functioning emails to bounce and therefore being disabled? Thank you in advance! Frances 3.

9 months, 3 weeks

[MM3-users]Re: Installation issues

by Mark Sapiro

On 04/20/2016 01:11 AM, Andrew Hodgson wrote: > > My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. You should be aware that mailman-bundler uses two venvs, one for Python 2 and one for Python 3. The idea is you create the Python 2 venv and activate it when running mailman-bundler's buildout, but that process will also create a venv-3.x venv in the bundler directory. I think what may make sense is to clone mailman-bundler directly into /opt/mailman rather than /opt/mailman/mailman-bundler. Then follow the docs from there. This should give you paths like /opt/mailman/venv/, /opt/mailman/venv3.x/, /opt/mailman/deployment/, /opt/mailman/mailman-web/, /opt/mailman/bin/, /opt/mailman/var/ and so on without the extra mailman-bundler/ level. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

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

by Mark Sapiro

On 4/20/19 10:13 AM, brian(a)emwd.com wrote: > Hi Mark, > > I followed your instructions to confirm the user. When I ran ">> util.confirm('hex_token')" nothing happened which I take it to mean it worked. I then ran ">> list(util.find(mlist=m,pend_type='subscription'))" and the pending member did not show up which I thought was a good thing. But . . . > > I tried to mass subscribe the user and got back: > > "HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}'" Did you do commit() or exit shell (which does an implicit commit) before trying the mass subscribe? I'm not going to be able to look at this further for some time as I am traveling today, but I will. -- 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: makemigrations --merge error after Debian upgrade

by Chupin Maxime

Tried to add these lines before the test in the `conf.py`and nothing changes. Should I remove the test on TIMEOUT ? ``` # Number of seconds to wait for a worker to finish. TIMEOUT = conf.get("timeout", 58) # Whether to acknowledge unsuccessful tasks. # This causes failed tasks to be considered delivered, thereby removing them from # the task queue. Defaults to False. ACK_FAILURES = conf.get("ack_failures", False) # Number of seconds to wait for acknowledgement before retrying a task # Only works with brokers that guarantee delivery. Defaults to 60 seconds. RETRY = conf.get("retry", 60) Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } # Verify if retry and timeout settings are correct if not TIMEOUT or (TIMEOUT > RETRY): warn( """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.""" ) ```

10 months

[MM3-users] Re: Error on timeout vs retry values

by Abhilash Raj

> On Aug 24, 2021, at 1:00 PM, Andrew Hodgson <andrew(a)hodgson.io> wrote: > > Hi. > > I just received the same error this evening when rebuilding Mailman3 on a new Debian 11 instal. There is a later version of Django on the new install. > > I got the original settings from the Mailman-Suite Gitlab project. I have made the modification but does this need to be made in that Gitlab project as well as that is where a lot of folks are getting their base Settings.py from? I have just updated the mailman-suite gitlab project with this change. https://gitlab.com/mailman/mailman-suite/-/commit/7f5dfd4992d4c454327233453… > > Thanks. > Andrew. > > -----Original Message----- > From: Robert Moody <robert(a)kneedrag.org> > Sent: 18 July 2021 22:35 > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Error on timeout vs retry values > > Thank you, that's fixed it. > > On 19/07/21 7:28 am, Abhilash Raj wrote: >> >> On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: >>> 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. >> You shouldn't edit files in `site-packages` directory as they are part >> of the package itself and could cause issues. >> >> What you want to do is override it in your settings.py (or >> settings_local.py) file for Django. I am not sure which guide you >> followed to install Mailman, but it should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). >> >> It should look something like this >> >> >> https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web >> .settings.mailman.Q_CLUSTER >> >> Just the value of retry should be just > than timeout as the error >> says, so not necessarily same values, but so far 300 and 360 has been >> working good for us and I haven't seen any report to increase them. >> >> >>> Any ideas? >>> >>> Regards, >>> >>> Robert >>> >>> >>> -- >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> _______________________________________________ >>> 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/ > _______________________________________________ > 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, 11 months

[MM3-users] Installation - creating the mailman.cfg permissions

by Mark Dale

https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… Following the instructions (at the above URL) to create the mailman.cfg, I'm getting a permissions problem when trying to do so as user "mailman" . Although the instructions say to create the file as user "mailman", should it be created by root (with/without virtualenv?) and then chown to "mailman"? ***** Make sure that you are running commands as mailman user from here forth. root@mx:/# su mailman Create the virtualenv for Mailman: mailman@mx:/$ cd /opt/mailman mailman@mx:~$ python3 -m venv venv Activate the created virtualenv: mailman@mx:~$ source /opt/mailman/venv/bin/activate The rest of this documentation assumes that virtualenv is activated. Installing Mailman Core (venv) mailman@mx:~$ pip install wheel mailman psycopg2-binary ...Successfully installed... After this, create a configuration file at /etc/mailman3/mailman.cfg for Mailman Core: (venv) mailman@mx:~$ nano /etc/mailman3/mailman.cfg [ Directory '/etc/mailman3' does not exist ] (venv) mailman@mx:~$ mkdir /etc/mailman3 mkdir: cannot create directory ‘/etc/mailman3’: Permission denied *****

3 years, 10 months

[MM3-users] Re: File in /var/lib/mailman3/queue/bounces/

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [211212 05:41]: > On 12/11/21 6:29 PM, Andreas Barth wrote: > > > >in my local installation there is a file in > >/var/lib/mailman3/queue/bounces/ since a couple of days. Any hint how > >to get rid of it? 'mailman unshunt' doesn't do it, but also, it's in > >queue/bounces and now queue/shunt. > > > I suspect the issue is that bounce runner is not running. If you > grep Mailman's mailman.log for `bounces` I suspect you will see that > it has died and not restarted. You may or may not find additional > information in the log as to why it died, but in any case restarting > Mailman should start everything again. Thanks for your answer. Actually I didn't find anything in the log, but according to ps the bounce runner is actually not running. A restart of mailman fixed the issue for me. Andi

3 years, 7 months

[MM3-users] Re: Error -- postorius Un-handled exception

by Ron / BCLUG

Mark Sapiro wrote on 2024-04-10 14:09: > I suspect you are not starting the services with your venv active. > What's in your mailman3.service and mailman3-web.service files? Thanks for the pointer! I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` somehow. I changed that to match the docs, did the `systemctl daemon-reload`, etc. but still had similar problems. I went through all my config files carefully, I wiped the static folder completely and rebuilt it, and I finally have the last piece of the puzzle in place and my web interface is working! I'm not sure which change actually fixed the issue though. (When looking at "Available lists" my header has "example.com" in the top-left corner?!?) Thank you! I think I need to backup what I have and do a clean re-install so I have a better grasp of what's going on with all these components. Mailman3 looks quite nice, gotta say! rb

1 year, 3 months

[MM3-users] Re: Must issue a STARTTLS command first when forwarding from old server to new server

by Mark Sapiro

On 11/14/24 15:53, jkoral(a)luc.edu wrote: > I have a fully functioning Mailman3 server now and have setup and alias on the old server to forward mail to the new server. We have TLS enabled on the new server, but not the old server, so the new server is rejecting the mail coming through. Our IT security will not allow me to disable TLS on the new server. > > Is there a way to make an exception in mailman3 to allow a specific host to send mail through without using TLS? This is all the MTA, not Mailman. As you suggest in a follow up, you should enable TLS on the old server. In Postfix main.cf, I think ``` smtp_tls_security_level = may ``` should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Help with fresh debian install

by Jonas Meurer

Mark Sapiro: > On 10/3/19 5:17 PM, Mark Dadgar wrote: >> I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: >> >> — >> mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck >> Traceback (most recent call last): >> [...] >> PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' > > > This is the issue. I don't know how the Debian packages do this, but I > recommend having a 'mailman' user that owns everything and running > commands as that user. The Debian package uses user `list` for this. It also provides a command `mailman-wrapper` which takes care of running mailman commands as this user. It would be awesome if the upstream /usr/bin/mailman command could take care of this automatically, making the wrapper command obsolete. Cheers jonas

5 years, 9 months

[MM3-users] Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Mark Sapiro

On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > I am currently automating a few things using the CURL commands but only > postorius related as of now. Now I have a requirement. > > I need to create a lot many users and their mapping email ids through > Site Administration almost daily. But it is becoming to do the same through > Graphical Interface. > > So, I just want to know the CURL commands that can be used to create the > user accounts and email ids mapped to user accounts. The accounts you are talking about are Django accounts. You cannot create these via CURL to the Mailman core REST API. You might find <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. -- 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] warning: database postfix_domains.db is older than source file postfix_domains

by Torge Riedel

Hi, I frequently get this warning mail.log. stat'ing the files give: # stat /opt/mailman/var/data/postfix_domains File: /opt/mailman/var/data/postfix_domains Size: 361 Blocks: 8 IO Block: 4096 regular file Device: 801h/2049d Inode: 1573095 Links: 1 Access: (0660/-rw-rw----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) Access: 2020-10-24 19:52:16.887258326 +0200 Modify: 2020-10-20 07:09:48.792000000 +0200 Change: 2020-10-20 07:09:48.792000000 +0200 Birth: - # stat /opt/mailman/var/data/postfix_domains.db File: /opt/mailman/var/data/postfix_domains.db Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: 801h/2049d Inode: 1583965 Links: 1 Access: (0640/-rw-r-----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) Access: 2020-10-26 07:46:54.569935782 +0100 Modify: 2020-10-20 07:09:47.575889000 +0200 Change: 2020-10-20 07:09:47.575889000 +0200 Birth: - I do not have the feeling that this is really a problem, cause everything works well. But it is confusing and misleading and might makes me missing a problem in the future, when the database is really outdated. Could this be easily fixed in mailman? It's mailman core 3.3.1. Kind regards Torge

4 years, 9 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Am 16.06.23 um 01:10 schrieb Mark Sapiro: > On 6/15/23 14:03, Jens Günther wrote: >> >> >> Am 15.06.23 um 00:34 schrieb Mark Sapiro: >>>> - Then I tried settings_local.py with: >>>> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' > > > Sorry, this is actually a different setting. There are actually two more > that control this. These are DEFAULT_FROM_EMAIL > <https://docs.djangoproject.com/en/4.2/ref/settings/#default-from-email> > and SERVER_EMAIL > <https://docs.djangoproject.com/en/4.2/ref/settings/#server-email>. Note > that the defaults mentioned in the Django docs are probably overridden > in your settings.py, but you should set them in settings_local.py Thank you Mark. I changed now DEFAULT_FROM_EMAIL to my address, restartet container and it works. Also it works if I delete the EMAIL_CONFIRMATION_FROM-line again and do not put the SERVER_EMAIL, at least for the password-reset. Can you tell the diffenrence between the 3? Would you recommend to set all 3 to my admin-mailaddress?

2 years, 1 month

[MM3-users] Re: Clean-up of non-members

by Mark Sapiro

On 12/24/24 08:13, Odhiambo Washington via Mailman-users wrote: > On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> I saw that too. Reported >> https://gitlab.com/mailman/mailman/-/issues/1187 and fixed >> https://gitlab.com/mailman/mailman/-/merge_requests/1297 > > > It isn't clear to me what I should do to mitigate the error. Apply this patch: ``` --- a/src/mailman/commands/cli_members.py +++ b/src/mailman/commands/cli_members.py @@ -103,7 +103,12 @@ def display_members(ctx, mlist, role, regular, digest, if nomail is not None: if member.delivery_status not in status_types: continue - dn = address.display_name or member.user.display_name + # Non-members may have empty address.display_name and member.user can + # be None resulting in AttributeError on member.user.display_name. + try: + dn = address.display_name or member.user.display_name + except AttributeError: + dn = '' if email_only or not dn: print(address.original_email, file=outfp) else: ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

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

by Terri Oda

On 2016-12-03 12:22 PM, Florian Fuchs wrote: > I did some manual integration testing today > (core+mailmanclient+postorius) which looked fine so far. I didn't get > to test HyperKitty and the bundler though, so any help testing those > would be very much appreciated. I will have some more time tomorrow. I tried to do some testing based on these wiki instructions last weekend https://wiki.list.org/HyperKitty/DevelopmentSetupGuide and hit a "[Errno 61] Connection refused" issue when attempting to log in to Postorius. I suspect it might be an issue with the mac, since googling for the error (it's a django one) seems to find a lot of people on macs with problems, but I didn't manage to narrow it down more than that to make a useful bug report. I did set up a new linux install on another machine to work on next, though, so I may have something else to say on that front tomorrow. Terri

8 years, 7 months

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

by Johannes Winter

Thank you very much maxking and everyone involved for this new release!! maxking/mailman-core:latest is only 6 days old. Probably the tag to choose? https://hub.docker.com/r/maxking/mailman-core/tags/ Am Wed, 11 Jul 2018 11:20:31 +0200 schrieb Alexander Klotz <alexk(a)kulturserver.de>: > 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. > > Or are we just a bit too impatient? ;) > > Thanks & Regards, > Alex Klotz > > (CultureBase editorial staff) > _______________________________________________ > 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/

7 years

[MM3-users] Mailman Core 3.2.2 is now out

by Abhilash Raj

Hello Everyone, Mailman Core 3.2.2 is released and available on PyPI[1]. This is a regular bugfix release and I had to do that to fix a version constraint which pulled in a pre-release of a dependency (falcon) when installed via pip and caused the default install to break. There are few other changes included in this release, including a big refactor of error reporting in Core's REST API. All the error responses are now correctly formatted as JSON with more information about the error. For example, invalid inputs for Enum data types return the valid options. Other error message are now generated from the input validtor and will be more informative. REST API also accepts input as JSON formatted body, alongside the x-www-form-urlencoded. A full list of changes are available here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 This release supports Python 3.5-3.7. Thanks very much to all the contributors involved in this release. [1]: https://pypi.org/project/mailman/ -- thanks, Abhilash Raj (maxking)

6 years, 4 months

[MM3-users] Re: How to delete user completely?

by Mark Sapiro

On 1/21/22 4:32 PM, William Oliver wrote: > I have installed mailman3 and it's up and running great. However, I > noticed that, during a mass subscribe, I mis-typed an address, e.g. > name(a)domain.ned rather than name(a)domain.net. I found how to unsubscribe > the bad address, but I haven't found a "delete" option under Users or > anywhere else. How to I purge a user from the users list? You need to do it via REST or `mailman shell`. In mailman shell, ``` >>> um = getUtility(IUserManager) >>> usr = um.get_user('user(a)example.com') >>> um.delete_user(usr) >>> commit() ``` > As a related question, in docs.mailman.org, I can find a list member's > manual, but I can't seem to find an admin manual. Is there one? No, not per se. -- 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: Issues encountered while upgrading to 3.3.7

by Mark Sapiro

On 12/5/22 02:37, Odhiambo Washington wrote: > > Here again, Google-fu came to the rescue. I added the following line to > settings_local.py and the warnings were suppressed. > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > I need to understand how this affects everything and how this is likely to > impact the functionality of MM3. What is the proper solution for this? > And should it be django.db.models.BigAutoField or > django.db.models.AutoField? Which is which? Prior to Django 3.2 Django set default primary keys to 32 bit integers. In 3.2 Django introduced the possibility to set default primary keys to 64 bit integers by setting the type to django.db.models.BigAutoField. Thus, putting ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in your settings will maintain compatibility with pre 3.2 versions and existing tables and this is the correct thing to do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

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

by Thomas Ward

When people are communicating on Mailman3 lists, some set up automatic responders for out-of-office, etc. and get let through the system to list recipients. Unfortunately, this is bad behavior and appears to not be caught by default. I'd like to set up some kind of rule globally rather than per-list that would check if a message is an automatic reply (based on a set of criteria we've come up with programmatically on our previous custom implementation of lists) and then default-discard those messages. Is there a way with custom rules to implement this? We're looking for certain strings on the subject line or other headers to determine "Discard" cases in our custom list implementations, but we are hoping we can implement this with customized rules in Mailman3 to achieve this goal. How would we structure that type of rule, and do we check the message object or the msgdata instead? Thomas

1 year, 8 months

[MM3-users] API errors making member changes to one list but not others

by Stephen J. Turnbull

Stephen Willey Mats Mats writes: > mailman3 should do a better job of reporting errors and recovering > when accidents happen. It appears that the side which is logging the errors is working fine. It expects to receive data which is not arriving, so there's a timeout. So probably it's on the Postorius side, which is not in these logs. I don't recall offhand if Django keeps its own logs, if it does and you have them, it would help to understand the problem and design a mitigation. But since it's a network connection, it could be any number of things in the middle, too -- even a kernel problem. If you have ideas about how better to report, fine, but it seems to me that in case of a major system incident, it's better to leave the diagnosis of faults in the interactions such complex systems to the humans. Steve

4 years, 6 months

[MM3-users] Mailman and Exim 4.94.2 (Debian Bullseye)

by Stephen J. Turnbull

Andrew Hodgson writes: > The issue I ran into was that Exim wasn't able to resolve localhost > in order to connect to the LMTP listener. That's odd. > I changed VPS provider at the same time (moved from Bytemark to > Gandi) so not sure if they were doing anything different with DNS, Sure looks like it. My home router resolves localhost to 127.0.0.1 as expected. So does my employer's. > I solved the issue by using the following configuration on the > Mailman router: Using the gethostbyname option is one way to solve the problem. Since you should only be able to reach the Mailman 3 transport via the Mailman 3 router (in Exim), this shouldn't cause whatever problem made Exim decide to use only DNS and not gethostbyname. An alternative would be to specify the LMTP host as 127.0.0.1 in the hosts list. This is more precise, but I doubt it has other advantages over "gethostbyname / hosts = localhost". Steve

3 years, 9 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/14/22 21:33, Stephen J. Turnbull wrote: > > Whether we *want* to do that depends on how much trouble that causes > for our main constituency (list and site admins), and whether we can > provide discoverable documentation of the problem. My take is that > this seems to be an extremely rare problem, and at least some MUAs are > able to read the message, so we should let it through. First, we are not silently dropping this message. We are rejecting it at LMTP time so the sender should be notified. Then the broader question is should we accept all messages with defects, almost all of which are spam, or only certain defects and which ones. I note that Apple has now released Mail 16 so maybe they've fixed this. My macs are still on Big Sur, so I can't test this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Correct way to filter auto-replies to list?

by Gary Holman

I have seen a few messages on this list regarding handling 'out of office' auto-replies. However I do not see a final resolution. What is the best practice to filter auto-replies to list: header filter or postfix milter-reject or something else? We are running dockerized Mailman 3 version 1.3.4. A list user auto-replied their vacation message to list and then the listserv created a chain-reaction of continuously replying to auto-replies by that user. There isn't really a good header option to filter from, as the subject seems to be randomized. For example: From <SENDER ADDRESS> Tue May 4 19:02:29 2021 From: Sender Name <SENDER ADDRESS> To: <LIST ADDRESS> Subject: [electronics-daq] Re: 25ad Date: Tue, 04 May 2021 20:59:57 +0200 Message-ID: <A2FB195E-5261-4F26-AF19-7AFE0B0632A5> In-Reply-To: =?utf-8?q?=3C0101017937874647-cf4b59ca-737e-4db0-9a01-85d9d43c8?= =?utf-8?q?d68-000000=40us-west-2=2Eamazonses=2Ecom=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7283775935526227777==" --===============7283775935526227777== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thank you, Gary

4 years, 2 months

[MM3-users] Re: Can't deliver mails in queue

by Mark Sapiro

On 5/19/21 2:45 PM, Nathanael Schneider wrote: > > They were in fact not identical, as I changed some stuff in hopes to get > it up and running again quickly. I now changed the completely new List > to be identical with the cleanly created one (as far as postorius shows > me) and it still works just fine. Do I understand correctly that you deleted the MM 2.1 imported list and created a new list in Postorius with just two members and it doesn't work. If that understanding is not correct, please outline all the steps you took to arrive at the current list that doesn't work. Also, please capture one of the .pck or .bak files from the out queue and send it to me off list. I will treat it confidentially, but there might be clues in it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Bug in 2.1.36?

by Mark Sapiro

On 11/12/21 3:47 PM, Joel Lord wrote: > On 11/12/2021 5:25 PM, Mark Sapiro wrote: >> Thanks for the report. I think the issue is caused by the fix for >> https://bugs.launchpad.net/mailman/+bug/1949403 and can occur when a >> list admin is trying to handle moderator requests on a list that has >> no moderator password. I'll investigate and try to put out another fix >> later today. >> > > Just realized I misread your statement. No, these lists don't have any > "moderators", so they don't have a moderator password set. Just admins, > doing both roles. > Yes, the issue occurs when logging in to the admindb with the admin or site password on a list with moderator requests and no moderator password set. It is fixed in Mailman 2.1.37 which I just released (announcement to follow). -- 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] Members (and moderators) can't view the list of members.

by mrl＠psfc.mit.edu

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 Any ideas? I did make a few "minor" changes to the code, but hopefully it didn't cause this problem. What file(s) contains the code that checks for permissions? Or maybe there is a config file? I also notice by default, for all users, in their "Global Mailman Preferences", the default setting for "Hide Address" is "Yes". How can I change that to be "No". And can I reset that setting for all my present users? Thanks. - Mark

8 months, 3 weeks

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/21/2017 06:46 PM, Rafael Mora wrote: > Can I use it for mailing lists? like MailChimp? Yes, if all you want is a simple one way announcement type list, Mailman can do that quite well, with appropriate list configuration[1], but as I tried to say, MailChimp has many more features that are oriented towards that kind of mailing. [1]There are many horror stories of people setting up a mailing list and subscribing a bunch of people to it without ensuring that members can't post back to the list. Then with the first post, people start posting back to be removed and then others reply that they didn't send that mail and it snowballs and within an hower, the poor list server is so backlogged that the clueful replies take hours to be delivered. I personally have been added to more that one list to which this happened. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Filtering signed mails

by Rainer Herbst

Dear all, today I recived a user complain that his messages were rejected with error "The message's content type was not explicitly allowed" I checked the list and indeed, it was configured to filter content and to allow only a very limited number of content types, namely application/pdf and image/jpeg. After some experiments, the problems seems to be the s/mime signature. The messages contain a signature: <snip> Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" <snap> I added this type to the allowed MIME content type, but signed messages are still rejected. What do I miss? 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, 8 months

[MM3-users] Re: MTA authentication and smtpd_sender_login_maps

by Jan Eden

On 2022-11-25 11:44, Mark Sapiro wrote: > 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 Thanks! I feel rather stupid, but the obvious and really simple solution is a wildcard entry for the SASL user in controlled_envelope_senders: @lists.domain.org mailman_sender(a)domain.org Sorry for realizing this *after* bothering you. - Jan

2 years, 8 months

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

by smith.ja1ck＠gmail.com

Hello All Community Member, I am in the process of setting up Mailman 3 on an Ubuntu 22.04 server & have faced some challenges during the configuration phase. Also I have followed the installation guide & while Mailman Core and Postorius seem to be working I am struggling to configure the Mailman web interface correctly with NGINX. Also I have tried a few different configurations for the reverse proxy but I m running into 502 Bad Gateway errors. Does anyone have experience setting up Mailman 3 with NGINX who might be able to offer some guidance? ?I am interested in seeing a working configuration file for NGINX and any tips on troubleshooting Mailman 3 issues during this phase. As well, I found these resources when doing research on this; https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://redacted If anyone have any resources, tutorials or personal experiences please share with me, It would be greatly appreciated!!

10 months, 1 week

[MM3-users] Re: Mailman3 on Debian 10

by Mark Sapiro

> On Wed, Jan 29, 2020, at 9:22 AM, Bala Mutyam wrote: > >> but the mailman service is not able to start it’s giving below error. Could you help me how to resolve it please? And also instructions for to install Mailman3 using Debian packages mailman3-full. I would like to use MySQl as backend and Exim4 as mail server. I couldn’t find new mailing list using the command line utility (/usr/sbin/newlist? Questions about the installation of Debian packages should be directed to Debian. >> Please see the attached Traceback. Which said in part: > urllib.error.HTTPError: HTTP Error 401: b'{\n "title": "401 Unauthorized",\n "description": "REST API authorization failed"\n}' The most likely cause of this is your Django settings in settings(_local).py for MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS do not match the mailman.cfg [webservice] settings for admin_user and admin_pass (defaults restadmin and restpass). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Mark Sapiro

On 4/14/22 06:32, Torsten R. wrote: > Aah, one last question that came just up. > Due to the removal of the list and the recreation there are now some message files with the extension psv in the bad queue. > Is it safe to just delete them manually or how should they be treated? These are messages that were queued in some queue, but now can't be dequeued after a few retries. In your case, this is probably due to permissions because of incorrect ownership. Examine the files with `mailman qfile`. If you don't want to continue processing the message, just remove the file. If you do, rename it, changing the extension from .psv to .pck and change the ownership as needed - probably from root to mailman, and move the file to the original queue indicated in the metadata - the second object shown by `mailman qfile`. -- 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: Postorius claims 2 messages held when there are none - out of sync

by Odhiambo Washington

Check your log file for mailmanweb for clues. On Mon, 26 Jun 2023, 10:01 Ken Alker, <mailman3.org(a)alker.net> wrote: > When I view a list via Postorius the "Held Messages" menu item has an > inverse-red-"2" next to it, as if there are two held messages. There are, > in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held > messages should be in "pipeline" subdirectory). When I click on "Held > Messages" I get "Something went wrong" followed by "HTTP Error 500: > {"title": "500 Internal Server Error"}". How do I fix this? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 1 month

[MM3-users] Re: HyperKitty Question

by Mark Sapiro

On 5/4/20 6:11 PM, Samir Faci wrote: > > I have nginx running with multiple website being serviced from the same > server. > > I updated the config where port 80 gets redirected to SSL. > > I tried setting mailman3-hyperkitty.conf to both: > > base_url: http://localhost/hyperkitty> base_url: https://lists.domain.com/hyperkitty/ > Either should be OK, possibly dependent of your nginx config. > But neither seem to be working. Does hyperkitty require traffic to be > going over port 80? No. https should work. Can you go to https://lists.domain.com/hyperkitty/ in a browser? Do you have api_key: set in mailman3-hyperkitty.conf and is it set to the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django settings. Note the value needs to be quoted in MAILMAN_ARCHIVER_KEY = 'the_value' and not in api_key: the_value because the former is a Python string and the latter is a config value. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Footer from templates not working - DB issue?

by Mark Sapiro

On 9/25/22 05:26, mailman--- via Mailman-users wrote: > Dear All, > I have a similar issue. Also on Debian 11. Also installed as Debian PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) > I am using sqlite3. When I do the SQL-query I get an URI which is in multiple reasons wrong > http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… The initial part of that URL is set from the Django setting `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to `http://localhost/mailman3/`, it should probably be just `http://localhost/`. > OK - the hostname could be changed but the path is not existing at all. > There is no file "list:member:regular:footer" on the complete filesystem. It's not a file. It refers to an entry in the postorius_emailtemplate table in the database which is retrieved via the Postorius API. -- 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: Held messages page not rendering the message

by Odhiambo Washington

On Sun, Mar 19, 2023 at 1:12 PM <mike-mailman(a)earth.li> wrote: > Thanks - may be on to something. > > The sources tab shows everything ok except for > /mailman3/static/postorius/js/script.js for which it says "Unable to fetch > script source" > However the network tab shows it successfully retrieving it. > > /var/lib/mailman3/web/static/postorius/js/script.js exists and contains > only comments > Is anything showing up in your webserver logs that is related to this? Just maybe. I have tested on my setup (although I use a virtualenv setup) and I see as a click on a held message corresponds to a log entry in my webserver log. I do get a pop-up like this: ``` https://imgur.com/a/esxmDsK ``` And that is the same across all my browsers. My Desktop is running Winblows11 though. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 12:01 AM, Ken Alker wrote: > When I view a list via Postorius the "Held Messages" menu item has an inverse-red-"2" next to it, as if there are two held messages. There are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held messages should be in "pipeline" subdirectory). When I click on "Held Messages" I get "Something went wrong" followed by "HTTP Error 500: {"title": "500 Internal Server Error"}". How do I fix this? The held messages are not in any queue. They are stored in Mailman's var/messages/ hierarchy. They can be examined with `mailman qfile` Also, there is a long thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and maybe others that might be relevant. -- 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] Import old mails into list

by franklin＠slat.org

Hi, I just built a new mailman3 instance. I installed directly on Debian using mailman3-full and follow /usr/share/doc/mailman3/README.Debian to set up database/web. Then I'd like to import some old mail (in a mbox file) into this list. I searched for any documentation but all I got is Import list data (from 2.1): https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/comma… How do I import an archive into a new mailing list: https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%2… The first is import list data, not list contents (mails). The second is very old, written in 2007, and now I even can't find bin/arch commands. Also, this post in this mailing list: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Which nobody replied yet. And when I tried `django-admin hyperkitty_import` it even told me "Unknown command: 'hyperkitty_import'". Could anyone please tell me how to import old mails from mbox file into a new mailing list? Thanks, Franklin

2 years

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

by Odhiambo Washington

On Wed, 29 Jul 2020 at 02:58, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/28/20 2:34 AM, Odhiambo Washington wrote: > > > > So, now I remember why I had to chown -R mailman3 /opt/mailman > > Then now it seems like I have been doing things incorrectly, because I > have > > been doing > > a lot of operations as root by simply: > > cd /opt/mailman/mm > > virtualenv venv > > source venv/bin/activate > > Looks like the correct way is to start with su - mailman3 > > > Yes. All those things should be done as the Mailman user. > > > >>> PS: There is the issue with qcluster, which doesn't seem to have been > ... > > I have run it from supervisord. It has forked 30 processes and refuses to > > kill them when I stop supervisord. > > I will look for options around it. > > > I know nothing about supervisord, but there should be a parent process. > E.g., here > > > msapiro@mail:~$ ps -fwwu mailman|grep qcluster > > mailman 2885 1 0 Jul18 ? 00:00:00 /bin/bash > /opt/mailman/mm/bin/mailman-web-django-admin qcluster > > mailman 2889 2885 0 Jul18 ? 00:01:57 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 2930 2889 0 Jul18 ? 01:21:03 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 2944 2930 0 Jul18 ? 00:04:17 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 2945 2930 3 Jul18 ? 07:11:14 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 6467 2930 0 15:39 ? 00:00:03 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 12337 2930 0 15:00 ? 00:00:07 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 12639 2930 0 11:08 ? 00:00:11 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 14658 2930 0 Jul27 ? 00:00:22 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 15860 2930 0 01:41 ? 00:00:21 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 19205 2930 0 Jul27 ? 00:00:29 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > msapiro@mail:~$ > > pid 2885 is the parent which forked 2889 which in turn forked 2930 which > forked all the others. stopping (sigterm) 2885 in this case will stop > them all. > > I have seen an issue on one server where some of the qcluster workers > become orphaned and their parent pid is 1. These are left when I stop > the upstart service so I have this script. > > #! /bin/bash > if echo `status qcluster` | grep -q 'running' ; then > echo qcluster is running > exit > fi > ps -fwwu mailman|grep '[a]dmin qcluster'|awk '{print $2}'|xargs kill > > to kill them. > I found some obscure option for supervisord that enabled the killing of the process(es). Obscure because it's not documented in the sample configuration for supervisord, but it's out there in the wild. > > PS: Did you by any chance find time to look into the issue about wsgi.py > > that you had mentioned - the one that has me > > stuck using it?? > > If you're referring to the issue at the end of > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > I think that was caused by your not having the __init__.py file in > /opt/mailman/mm/. > > If not, I probably need more information. > Yes, the same problem. I created the file __init__.py in /opt/mailman/mm However, when I run using the wsgi.py I ended up (still do!) with the error: [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', application='mm3-lists.server.name|/mm3'): Loading Python script file '/opt/mailman/mm/wsgi.py'. [Wed Jul 29 10:08:51.872461 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] mod_wsgi (pid=79132): Failed to exec Python script file '/opt/mailman/mm/wsgi.py'. [Wed Jul 29 10:08:51.872507 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] mod_wsgi (pid=79132): Exception occurred processing WSGI script '/opt/mailman/mm/wsgi.py'. [Wed Jul 29 10:08:51.872754 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] Traceback (most recent call last): [Wed Jul 29 10:08:51.872827 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/wsgi.py", line 38, in <module> [Wed Jul 29 10:08:51.872835 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] application = get_wsgi_application() [Wed Jul 29 10:08:51.872847 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/wsgi.py", line 12, in get_wsgi_application [Wed Jul 29 10:08:51.872852 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] django.setup(set_prefix=False) [Wed Jul 29 10:08:51.872862 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/__init__.py", line 19, in setup [Wed Jul 29 10:08:51.872868 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Wed Jul 29 10:08:51.872878 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 76, in __getattr__ [Wed Jul 29 10:08:51.872884 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] self._setup(name) [Wed Jul 29 10:08:51.872893 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 63, in _setup [Wed Jul 29 10:08:51.872899 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] self._wrapped = Settings(settings_module) [Wed Jul 29 10:08:51.872909 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 142, in __init__ [Wed Jul 29 10:08:51.872914 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] mod = importlib.import_module(self.SETTINGS_MODULE) [Wed Jul 29 10:08:51.872923 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/usr/local/lib/python3.6/importlib/__init__.py", line 126, in import_module [Wed Jul 29 10:08:51.872929 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] return _bootstrap._gcd_import(name[level:], package, level) [Wed Jul 29 10:08:51.872938 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "<frozen importlib._bootstrap>", line 994, in _gcd_import [Wed Jul 29 10:08:51.872949 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "<frozen importlib._bootstrap>", line 971, in _find_and_load [Wed Jul 29 10:08:51.872960 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked [Wed Jul 29 10:08:51.872984 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] ModuleNotFoundError: No module named 'settings' -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years

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

by Stephen J. Turnbull

Thomas Stein writes: > Thanks for your answer. So the the file in queue/shunt contains > information too? I will have a look. The file in queue/shunt is the message plus some Mailman metadata, as a Python pickle. You can find out what is in it using "bin/mailman.py qfile", but probably the log and traceback will tell you (or us) everything needed to fix the problem. If it's a Mailman bug (somewhat unlikely), we send you a patch and you use "bin/mailman.py unshunt" to reinject the message into the mail system via Mailman. If it's a nonconforming mail message (somewhat more likely -- typically this happens when you have raw UTF-8 or other 8-bit characters in the message header), then the easiest thing to do is to edit a saved copy of the message and resend from your mail client. (It's theoretically possible to edit the pickle and use "unshunt", but Mailman currently does not provide that feature.)

6 years, 6 months

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

by Stephen J. Turnbull

Duane Raymond writes: > Regarding emails not reaching some users, the logs seem to indicate > the emails are being sent fine and in communication with users it > isn't in spam or bulk emaIL folders. Some emails arrive hours after > despite being sent on time. This may be greylisting, the practice of sending an artificial temporary SMTP failure in hopes that spammers won't come back but a legit MTA will automatically retry. IIRC the traditional first retry comes after 4 hours, although most greylisters will allow the transaction after 15 minutes. I think modernized sites do retry a lot quicker, but I don't know what MTA defaults are nowadays. If the mail is not being delivered direct from Mailman's MTA to the recipient's MTA, you wouldn't be able to tell from the sender and recipient times alone, you'd need the whole Received trace from the recipient's copy to find the point where the delay is happening. Steve

4 years, 3 months

[MM3-users] Re: changing the main template for subscriptions and more

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210622 14:22]: > It isn't necessary to patch the source in this way. If you put the > modified templates in Mailman's var/templates/site/de/ directory, > ensuring that the Mailman user can read them, they will be used and > you won't have to patch the source every time you upgrade. Thanks Mark for pointing that out. I also should have mentioned that this would be the recommendation for operations, especially if mailman is install by some normal means (pip, distribution packages, etc). I perhaps took it for granted too much to never touch files coming out of automated systems by hand (except where the automated system caters for, e.g. debian conffiles), because that is a sure way to get into trouble with the next upgrade. (My mailman installation is the exception and not the rule, so unless you know what you're doing and have done similar before, just follow Marks advice) Andi

4 years, 1 month

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/15/21 2:11 PM, Sarah H wrote: > I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get: > > curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number A 301 from http will be an issue always. I'm not sure where the `wrong version number` comes from. This could be the issue. If I do for example, curl -X POST https://lists.mailman3.org/archives/api/mailman/archive I get the response <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> This is the expected response. You need to figure out what base_url will give you a similar response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [220315 23:31]: > I understand that, but even Debian sid has mailman3 3.3.3-1 and > mailman3-web 0+20200530-2 which are quite old for a package like > Mailman 3 which is still in active development. If we speak about unstable, that's something else. However, Debians next stable release won't release with mailman 3.3.3, as this package is removed from testing at the moment. I'd be happy if someone would update this package, however, I don't think I should get myself also involved there. ('Removed from testing' means: the current unstable package is considered not to be in shape to be released with the next stable release). So, if someone wants to get involved into Debian package maintainership with mailman3 (and related packages), that would be great, and I'm happy to support. As said, the most easiest way to get things fixed in Debian is by doing it. Andi

3 years, 4 months

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

by Jens Günther

This here would be best if I could list them by Domain!? But seems to me a little nonsense ... but maybe it's registered, through which VHOST the user registered. Am 08.12.23 um 17:01 schrieb Jens Günther: > > ## registered users > > This part is somehow tricky, since I have no clue how to do it. Some of > the mailinglist-admins don't want to bother their list-owners again with > registering newly on the other system. Is there a way to export all > users (I think I found them in the DB in the table auth_users, somehow > in combination with account_emailaddress) and get them over to the new > instance (actually I just need part of them, but that's another question > that I might solve lateron on my own). > > Maybe the answer is already here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but can somebody help to get this working (import/export)?

1 year, 7 months

[MM3-users] Re: Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by skenny＠scss.tcd.ie

Hi Stephen, Yes, everything *does* work if I delete and create the database afresh prior to importing - I see all my lists, with the correct memberships, settings etc. I was afraid that by removing the default database that comes with the database container, I'd be losing some vital information that may have been added or changed in the database config since I first got my production server working 2 years ago - changed field values, extra table columns ... ? Does that make any sense? I've a hazy understanding at best of the minutiae of databases, being honest. I had actually started to mull over creating all my lists afresh on the new server, and populating them using scripting/mailmanclient, but I'm now encouraged by your answer :-) - so maybe I'll just wipe and recreate mailmandb, and then do the import. Thanks a lot for your reply Stephen

3 years

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

by Odhiambo Washington

On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 04:26, Odhiambo Washington wrote: > > > > Okay. This is a bit off from my understanding. > > > > What is the cause and how do I mitigate it? > > The cause is the monthly hyperkitty update_and_clean_index job runs for > a long time, i.e. hours, because it is rebuilding the entire search > index so during the time it's running multiple hourly hyperkitty > update_index jobs are started and they are competing for the same lock. > > See > > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > for mitigation. What is the danger of replacing my settings.py with this one, seeing as it differs in a number of ways with mine? -- 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] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Mark Sapiro

On 1/24/24 02:38, amg hsn wrote: working packages with exact version. > for me each time i build venv i have different warning or erro. I understand your frustration and I'm sorry. The problem is that the current release of django-mailman3, 1.3.11, just requires django-allauth>=0.56, so a new install will get the latest django-allauth==0.60.1, but django-mailman3==1.3.11 is not compatible with django_allauth>=0.59. This will be fixed in the next release, but in the mean time, you can apply https://gitlab.com/mailman/django-mailman3/-/merge_requests/237/diffs and https://gitlab.com/mailman/django-mailman3/-/merge_requests/243/diffs to update django-mailman3 for compatibility with the latest django-allauth. This can be an issue when any of our third party dependencies is upgraded in an incompatible way. Short of pinning all the dependencies to a specific version, there's not much we can do about it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by David Newman

On 1/7/22 12:06 PM, Mark Sapiro wrote: > On 1/7/22 11:06 AM, David Newman wrote: >> >> 1. In Users/Members, moderation action for the newly resubscribed >> users shows as "None". Is there a method, either in the UI or the >> command line, to change this to "Default processing" for all users? > > > I assume you don't want to set `Default action to take when a member > posts to the list` to Default Processing because you want new member > posts to be held. This is a good practice. To set all members to default > processing in mailman shell .. OK, thanks >> 2. Although Delivery Mode shows as "Regular" for all users in >> Users/Members list, clicking on a member's name shows all options such >> as delivery status, delivery mode, etc., as undefined. > > > They show as undefined, but if you look at your own settings by > selecting `Mailman settings` from the dropdown under your username at > the upper right in Postorius, you will see you have Global Mailman > preferences, Address-based preferences and List-based preferences. If a > list based preference is unset for a list, it falls back to the address > based preference for the address and if that's unset, to the global > preference. > > When you as an admin look at a user, you only see the user's list based > preferences. Thanks. This makes sense, but something's wrong with this particular list. I was able to change preferences using the shell commands you kindly provided. All list member now have regular delivery and default moderation. However, there's no evidence test messages to the list are going out. (Nondelivery was the reason I was mucking around in the admin panel in the first place.) The Postfix log shows delivery to the list address. MM3's smtp.log shows the usual handshake. However, I do not then see messages going out to subscribers in the Postfix log, and as one of those subscribers I do not receive a copy even though my preferences are set to receive my own posts. The admin panel shows 0 messages held for moderation. Another mailing list in the same domain on the same server delivers mail to all subscribers OK. This is surely config problem on my end, but which log(s) and/or admin panel setting(s) to check? Thanks again. dn > >> Similar question: How to set subscriber options for all members in one >> go? > > > Per the above, you only need to set the user's preferences if they don't > have address based preferences and the preference differs from the > global (default) preferences. > > However, if you want to set the member's list preferences, you could add > to the beginning of the above: > ``` > >>> from mailman.interfaces.member import DeliveryMode, DeliveryStatus > >>> english = getUtility(ILanguageManager).get('en') > ``` > and to the `for` loop in the above: > ``` > ... mbr.preferences.acknowledge_posts = False > ... mbr.preferences.delivery_mode = DeliveryMode.regular > ... mbr.preferences.delivery_status = DeliveryStatus.enabled > ... mbr.preferences.hide_address = False > ... mbr.preferences.preferred_language = english > ... mbr.preferences.receive_list_copy = False > ... mbr.preferences.receive_own_postings = True > ``` > Or whatever you think these settings should be. > >> 3. As a subscriber to this list, I received email notification that >> I'd been unsubscribed. Where is the control for enabling/disabling >> subscription notifications? > > > Settings -> Automatic Responses > > >> Settings/Member Policy/Un-subscription Policy is set to Confirm, but I >> don't think that's relevant here since I unsubscribed users as the >> Django superuser. > > > Correct. >

3 years, 6 months

[MM3-users] Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)

by Odhiambo Washington

On Thu, Apr 17, 2025 at 3:14 PM Christian Schneider < christian.schneider(a)tu-dortmund.de> wrote: > Thank you for your instant reply! > > Mihai Moldovan wrote: > > > But I could find no information about the location where hyperkitty > stores the archives on an Ubuntu-/Linux-system. > > > I assume the archives are stored underneath "/var/..." this is only a > guess. > > > But is this guess right? > > > Not quite. > > To the best of my knowledge, by default, a venv installation is fully > contained > > under /opt/mailman, with archives and stuff stored at > /opt/mailman/var/lib/... > > This information is very helpful! > Actually I have about 45GB of archives and these archives only hold > messages of the last year... > I run a clean-up script every first day of a month which deletes posts > older than 365 days... > So there is lot of disk space needed... ;-) > (and even more if I plan to keep posts around for a longer time) > > > > Another question is: > > > How much space do I have to plan (roughly) for the "/opt"-partition > for the mailman install if the archives are stored under "/var/..."? > > > Depends on your archives, the way things are archived (you can choose > different > > database backends, and these might make a difference in how efficiently > or > > inefficiently data is stored) and whether you want to use the full-text > search > > index, which adds another big chunk of data. > > I can give you a few pointers regarding my setup: my mailman 2.1 data > directory > > takes up about 8.2 GB of disk space, most of which are archives, > naturally (8.1 > > GB). I've imported most of the big archives to mailman 3 already, with a > > full-text search index, and that uses 5.2 GB disk space currently, but > I'm still > > missing a few archives, so that'll still grow a bit. It will probably > end up at > > about the same size, but I can come back to that once my import is fully > done > > (which sadly will take a few days). > > Now, the 8.1 GB of mailman 2.1 archives are stored pretty inefficiently, > because > > they are essentially duplicated (as a private mbox archive and public > text > > archives). Mailman 3 doesn't do that - at least not directly - but > instead > > stores archives once into the database, and queries the database > whenever the > > archives are accessed via hyperkitty, so I would *assume* the size you > need for > > the mailman 3 data after a successful migration is just a bit shy of > what you > > needed for the mailman 2.1 data, maybe even a bit less. > > Perfect! :-) > If I mount an extra partition of 250Gigs at /opt this should carry me for > a longer time... > And - if I setup a logical volume with LVM - there is an option to stack > up the space with ease... ;-) > Does your DB backend also store the data files in /opt? I doubt it. The archives will be stored in the DB backend. So unless you use SQLite backend, the data will go where you configure your DB to store data- whether it's MariaDB or PostgreSQL. -- 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]

3 months, 2 weeks

[MM3-users] Re: Query on how to change moderator message to non-members

by Simon Hanna

Yes you can. But you can't do it thought the web ui yet. https://gitlab.com/mailman/mailman/issues/426#note_43861203 has pointers to what needs to be done On 07/01/2018 12:19 PM, robert.kydd(a)gmail.com wrote: > Hi > My users are upset that when their mail is waiting moderation release they receive this message: > > 'Your mail to 'Members' with the subject > > AW: [Members] Hamburg 2019 > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list' > > Is their a way to change the text "post by a non-member to a members-only list" as they are registered members of the Joomla site > _______________________________________________ > 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/

7 years, 1 month

[MM3-users] Re: Mailman Suite installation on CentOS 7

by Mark Sapiro

On 11/8/21 4:18 AM, Kimmo L wrote: > Hello! > > I want to install fresh Mailman, which is combined with hyperkitty+postorius. After checking documentation i found, that Mailman Suite is perfect for me. > But i have some misunderstandings about installation. I only found this part in documentation, which explains how to clone and start using Mailman Suite (https://docs.mailman3.org/en/latest/devsetup.html#run-the-mailman-suite-com…) > > But am i correct, that before doing so, i need to install mailman core, mailman client, django-mailman3 ? > Or what would be the correct steps to build up my first Mailman Suite on CentOS? The docs you want to look at are https://docs.mailman3.org/en/latest/#the-pre-installation-guide and https://docs.mailman3.org/en/latest/install/install.html. There is also information at https://wiki.list.org/x/17891998 and in docs linked from thefirst paragraph thereof. -- 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: Messages not picking up header or footer template

by Mark Sapiro

On 2/26/23 13:04, benjamin(a)tougshire.com wrote: > > I can see the entry in the database with the uri: http://localhost:8000/mailman3/api/templates/list/testing.comms.sdcvirginia… > > I can do a wget on that uri and download a copy of the footer, and it looks right > > But when I send a message to the list and the message is forwarded, the footer isn't on the messages that members receive > > Looking at mailman.log, I cannot see any attempt to access the footer. I can see connections to the REST API (config, roster/owner, roster/moderator) that correspond to the time I sent the message Can you see an attempt to GET /mailman3/api/templates/list/testing.comms.sdcvirginia.org/list:member:regular:footer in your web server's logs? Is there anything in Django's 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, 5 months

[MM3-users] Re: Social signup?

by Mark Sapiro

On 3/15/23 05:08, Duane Raymond wrote: > > I'll jump over to the developers list when I start this (I'm about to > travel for a week to run an annual event in Oxford - so the far removed > from programming)...but which chatGPT suggested so far was > > 1. Extending postorius/signups.html with a loop to get the configured > social login providers PLUS adding a csrf_token field to the form > 2. Modifying postorius/views.py (which doesn't seem to exist but there > is a postorius/views folder) - so perhaps this is views/urls.py This is not what you want to do for this. The changes need to be in django-mailman3, not postorius. I have attached a patch which might work for you. I think it is good, but some of the wording is stuff that may not be appropriate. See what you think. -- 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: unrequested unsubscription

by Mark Sapiro

On 6/14/23 19:40, Mike Wertheim wrote: > I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. > > A few of the list members are reporting that they received Email Address > Unsubscription Confirmation emails, but claim that they never requested to > be unsubscribed. (All are Gmail users. but they might be coincidental, > since most list members are Gmail users.) > > Has anyone seen this behavior before? Any ideas on what might be happening? Yes. This is someone sending an email `leave` or `unsubscribe` command for the user in question. This may be malicious, i.e. someone doesn't like a user's posts and tries to unsubscribe them, or it may be just spam of some sort. the user should just ignore the email. Beyond that, there's not much you can do unless you can identify from mail logs the source of the requests. -- 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: Issues with @gmail.com addresses

by Jeremy Stanley

On 2023-09-09 01:21:32 +0900 (+0900), Stephen J. Turnbull wrote: [...] > We could easily have an option to not attach the messages to the > notifications, just a list of most useful headers, or simply a > statement of how many if you really want to be minimal. A number of our lists would probably make use of that if it were an option, though sadly my dance card is too full to code the feature any time soon. Checking list moderation pages directly isn't a huge deal anyway, I mean I have something like 20 browser tabs perpetually open to the moderation queues for lists I personally handle and just refresh them every morning to see if there's anything that needs attention (I do get the notifications but tend to only skim them in case there's something urgent, though I also run my own MTA for my personal mailboxes so there's no risk of the postmaster getting concerned and banning them). -- Jeremy Stanley

1 year, 10 months

[MM3-users] Bounce processing

by Andrew Hodgson

Hi, Just upgraded to Mailman 3.3.1 at the beginning of the week and its very refreshing to have bounce processing working after all this time, stops the continued delivery to dud email addresses causing problems with junk email scoring. Anyway after a few days of using this I have noted the following feedback: When users are set to disabled after their bounce score reaches a certain threshold, I seem to recall on Mailman 2 they were sent an email with a link to reactivate their subscription. On Mailman 3 they are told to contact the list admin, I have had messages from a few subscribers regarding this asking how they can re-enable delivery. I am also getting bounces that look like they are coming from Qmail (Yahoo addresses) which are being forwarded to the list owner as unrecognised bounces. Should the type of bounces that Mailman 2 was handling be handled in Mailman 3 or is the way that the addresses are extracted different? I have disabled the relevant users but do have the bounces to hand. Thanks. Andrew.

5 years, 3 months

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

by Stephen J. Turnbull

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

3 years, 8 months

[MM3-users] Re: No e-mail distribution after import of archive

by Markus Grandpré

Dear Mr Odhiambo, that is what i see in mail.log 1) when sending an e-mail to list that owns an *imported* archive. This list does *not* distribute a received e-mail to any list member: 2024-11-12T10:42:25.921700+01:00 mailman-app-test postfix/smtpd[736246]: connect from mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962093+01:00 mailman-app-test postfix/smtpd[736246]: EACD47C: client=mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962943+01:00 mailman-app-test postfix/cleanup[736250]: EACD47C: message-id=<523343bc-3789-443e-8404-98a13d1e0adf(a)uni-konstanz.de> 2024-11-12T10:42:25.967472+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: from=<markus.grandpre(a)uni-konstanz.de>, size=9650, nrcpt=1 (queue active) 2024-11-12T10:42:25.967630+01:00 mailman-app-test postfix/smtpd[736246]: disconnect from mailout.uni-konstanz.de[134.34.240.38] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:42:26.059198+01:00 mailman-app-test postfix/lmtp[736251]: EACD47C: to=<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.11, delays=0.02/0.01/0/0.08, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:42:26.059525+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: removed 2) when sending an e-mail to list that does *not* own an (imported) archive. This lists distributes a received e-mail to all list members: 2024-11-12T10:42:25.921700+01:00 mailman-app-test postfix/smtpd[736246]: connect from mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962093+01:00 mailman-app-test postfix/smtpd[736246]: EACD47C: client=mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962943+01:00 mailman-app-test postfix/cleanup[736250]: EACD47C: message-id=<523343bc-3789-443e-8404-98a13d1e0adf(a)uni-konstanz.de> 2024-11-12T10:42:25.967472+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: from=<markus.grandpre(a)uni-konstanz.de>, size=9650, nrcpt=1 (queue active) 2024-11-12T10:42:25.967630+01:00 mailman-app-test postfix/smtpd[736246]: disconnect from mailout.uni-konstanz.de[134.34.240.38] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:42:26.059198+01:00 mailman-app-test postfix/lmtp[736251]: EACD47C: to=<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.11, delays=0.02/0.01/0/0.08, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:42:26.059525+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: removed 2024-11-12T10:44:11.500683+01:00 mailman-app-test postfix/smtpd[736314]: connect from mailout.uni-konstanz.de[134.34.240.59] 2024-11-12T10:44:11.531183+01:00 mailman-app-test postfix/smtpd[736314]: 81A2B7C: client=mailout.uni-konstanz.de[134.34.240.59] 2024-11-12T10:44:11.532139+01:00 mailman-app-test postfix/cleanup[736316]: 81A2B7C: message-id=<802848fd-713b-4318-af7b-f868728edae3(a)uni-konstanz.de> 2024-11-12T10:44:11.535226+01:00 mailman-app-test postfix/smtpd[736314]: disconnect from mailout.uni-konstanz.de[134.34.240.59] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:44:11.535529+01:00 mailman-app-test postfix/qmgr[736016]: 81A2B7C: from=<markus.grandpre(a)uni-konstanz.de>, size=9595, nrcpt=1 (queue active) 2024-11-12T10:44:11.564063+01:00 mailman-app-test postfix/lmtp[736317]: 81A2B7C: to=<nochntest(a)mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.01/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:44:11.564429+01:00 mailman-app-test postfix/qmgr[736016]: 81A2B7C: removed 2024-11-12T10:44:14.144185+01:00 mailman-app-test postfix/smtpd[736314]: connect from localhost[::1] 2024-11-12T10:44:14.149134+01:00 mailman-app-test postfix/smtpd[736314]: 245CC7C: client=localhost[::1] 2024-11-12T10:44:14.150698+01:00 mailman-app-test postfix/cleanup[736316]: 245CC7C: message-id=<802848fd-713b-4318-af7b-f868728edae3(a)uni-konstanz.de> 2024-11-12T10:44:14.155543+01:00 mailman-app-test postfix/qmgr[736016]: 245CC7C: from=<nochntest-bounces(a)mailman-test.uni-konstanz.de>, size=11569, nrcpt=2 (queue active) 2024-11-12T10:44:14.155843+01:00 mailman-app-test postfix/smtpd[736314]: disconnect from localhost[::1] ehlo=1 mail=1 rcpt=2 data=1 quit=1 commands=6 2024-11-12T10:44:15.883334+01:00 mailman-app-test postfix/smtp[736318]: 245CC7C: to=<christian.mack(a)uni-konstanz.de>, relay=thurn.uni-konstanz.de[134.34.240.38]:25, delay=1.7, delays=0.01/0.02/0.04/1.7, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4XnhML1WGSz1q) 2024-11-12T10:44:15.883517+01:00 mailman-app-test postfix/smtp[736318]: 245CC7C: to=<markus.grandpre(a)uni-konstanz.de>, relay=thurn.uni-konstanz.de[134.34.240.38]:25, delay=1.7, delays=0.01/0.02/0.04/1.7, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4XnhML1WGSz1q) 2024-11-12T10:44:15.883730+01:00 mailman-app-test postfix/qmgr[736016]: 245CC7C: removed Postfix and mailman configurations for 1) and 2) are the same. With kind regards, Markus Am 12.11.24 um 10:27 schrieb Odhiambo Washington via Mailman-users: > On Tue, Nov 12, 2024 at 11:52 AM Markus Grandpré < > markus.grandpre(a)uni-konstanz.de> wrote: > >> Dear Mr Odhiambo, >> >> thank you very much for your reply. >> >> In mailman.log I see: >> >> Nov 12 09:46:02 2024 (698086) ACCEPT: >> <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de HTTP/1.1" >> 200 486 "-" "GNU Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de/config >> HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/users/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 285 "-" "GNU >> Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/owner >> HTTP/1.1" 200 789 "-" "GNU Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/addresses/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 436 "-" >> "GNU Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/lists/ >> import_mm3_testliste.mailman-test.uni-konstanz.de/roster/moderator >> HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" >> Nov 12 09:46:03 2024 (698083) HyperKitty archived message >> <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> to >> >> https://mailman-test.uni-konstanz.de/mailman3/hyperkitty/list/import_mm3_te… > > > Is that ALL you have from mailman.log for today,? I was expecting more - > like some task runners being logged. > > > In smtp.log I found: >> >> Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) >> PLAIN(builtin) >> Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO >> mailman-app-test.kim.uni-konstanz.de' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL >> FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: >> markus.grandpre(a)uni-konstanz.de >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT >> TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: >> Import_mm3_testliste(a)mailman-test.uni-konstanz.de >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost >> during _handle_client() >> >> I have no idea why there is a "connection lost". What do you think? > > > That 'connection lost' is normal. > So there seems to be communication from mailman to your MTA. > What do you see in your MTA (Postfix?) logs when you send an email to the > list? > > > >> How can I increase the log level? >> > Actually, you do not need to, but mailman.cfg complete documentation is > here: > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > > > > > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

8 months, 3 weeks

[MM3-users] Re: Pd CRON mailman gatenews

by Pierre Malard

Hi Mark, Thanks for your answer and your lead > Le 16 mars 2023 à 18:34, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On 3/15/23 23:31, Pierre Malard via Mailman-users wrote: > >> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 502, in _read >> with open(self._lockfile) as fp: >> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' >> —————————————————————————————————————————————————— >> CRON content: >> —————————————————————————————————————————————————— > ... >> # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured >> */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi > > Do you have any list's for which Gateway to mail is set to yes or for which there is a Linked Newsgroup?. If not, running gatenews is superfluous. No, we don’t have > >> I thought, given the last line, a problem of rights. It is not the case ! The directory and the files contained in /var/lib/mailman3/locks belong to the user "list". >> When I run "/usr/bin/mailman gatenews" by hand everything is correct. > > Can you do `sudo -u list cat /var/lib/mailman3/locks/dbcreate.lck`. If that succeeds, this may be a SELinux or other security manager issue. Their is no file with this name! listesman:~# ls -ld /var/lib/mailman3/locks/dbcreate.lck ls: impossible d'accéder à '/var/lib/mailman3/locks/dbcreate.lck': Aucun fichier ou dossier de ce type > > >> The questions I have are these: >> We have 8000 files "dbcreate.lck..." in the directory "/var/lib/mailman3/locks". >> What are they for? >> Can we delete them? > > They are probably all orphaned lock files due the the gatenews failure. To be certain that none are current you could stop Mailman core. Then with Mailman core stopped, any files in /var/lib/mailman3/locks are orphaned and should be removed. Ok, is done. We will see today if it continues > >> We have 2 files "master.lck..." dated from the day after tomorrow ! >> What is this date? >> Aren't these files the problem? > > > Those files are normal. They are the master lock that prevents Mailman core from being started when it's already running. The future date is the way flufl.lock handles lock lifetimes. Locks when set have a lifetime, after which they can be broken. This is implemented in flufl.lock by setting the file's date that far into the future. Ok, that’s smart :-) > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to plm(a)teledetection.fr -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Je n'ai jamais séparé la République des idées de justice sociale, sans laquelle elle n'est qu'un mot » Jean Jaures - 1887 |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 4 months

[MM3-users] Re: Where is postorius.wsgi?

by Simon Hanna

On 01/26/2018 11:18 AM, Peter Münster wrote: > On Fri, Jan 26 2018, Peter Münster wrote: > >> ImportError: No module named settings > Ok, I've found the solution: > > In wsgi.py: > > import sys > sys.path.append('/srv/www/htdocs/ckc3r/postorius/example_project') > > > But now, I get another error: > > File "/usr/lib/python2.7/site-packages/postorius-1.1.2-py2.7.egg/postorius/views/rest.py", line 33, in <module> > from django_mailman3.lib.scrub import Scrubber > File "/usr/lib/python2.7/site-packages/django_mailman3-1.2.0a1-py2.7.egg/django_mailman3/lib/scrub.py", line 26, in <module> > from email.message import EmailMessage > ImportError: cannot import name EmailMessage > > What should I do please? You appear to be using a prerelease version of django-mailman3 which is not compatible with the other parts. Install an earlier version and it should work. You also appeared to have used Python3 for the frontend in earlier posts. Currently Python3 is not yet supported. The next stable releases will most likely support Python3 and drop support for Python2

7 years, 6 months

[MM3-users] "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Hello, I've been getting "Cannot connect to SMTP server localhost on port 25" from runner "out" in mailman.log over some mails stuck in shunt queue, postfix logs show nothing when this happens, tcpdump on lo interface port 25 shows nothing. The log shows up when I start mailman, and then it seems not to show up again. This is my mailman.cfg's relevant parts: [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix I can do 'telnet localhost 25' just fine, including as mailman user. I can send and receive mail on my mail server. I tried making a test list and sent/received messages fine. smtp debug logs show "Using agent: <mailman.mta.deliver.Deliver object at 0x7fdd9793c940>" and "IndividualDelivery to: <email(a)address.tld>" on repeat, where the email address is one of the addresses of the shunted mails. version 3.2.2

5 years, 10 months

[MM3-users] Re: Python is updated

by Mark London

Because of my own personal horror stories of waking up to finding high priority linux servers broken, due to nightly automated updates, I now prevent automatic updates on my servers. I only do manual security updates. In addition to implementing modern security techniques for our network. That is just my personal belief system. It's worked for the past 25 years. The only time we ever got hacked, was because of some stupid php scripts that our developers had put online, or because people's passwords had become leaked. And some of those situations were nightmares also. In two case of which, happened while I was away on vacation, and I had to fix everything remotely. But that was never due to updates. I probably shouldn't express my opinion. But I have a lot of empathy for the guy who discovered his mailman broken due to upgraded Python. Which triggered my nightmares. But it's great though to have a very responsive community here, to bring people back from the dead. - Mark

2 years, 3 months

[MM3-users] Re: Ready to try installation: use "normal" install or docker.

by Tom Browder

On Tue, Aug 1, 2017 at 12:28 Abhilash Raj <raj.abhilash1(a)gmail.com> wrote: > Hi Tom, .... > On Tue, Aug 1, 2017, at 07:54 AM, Tom Browder wrote: > > I'm leaning toward installing using the docker method but I would > > appreciate any recent thoughts about which method to choose. > > It really depends on what way you want to go, container images will be > much less hassle to use right now, mostly because all the dependencies > are bundled in and the moving parts are already configured to work with > each other. Abhilash, thanks for the response. My goal is to use the installation in production immediately (production meaning using some interested friends as testers before opening lists to "real" subscribers). If I understand properly, the docker way will be a good path to do that and it should make my volunteer maintenance life easier in the future, too. Does that sound reasonable? -Tom

8 years

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

by Stephen J. Turnbull

Andreas Barth writes: > Not sure if this is the right approach, or if it wouldn't be more > appropriate to "just" replace the dependency on allauth in postorius, > and do all the magic in the frontend only (because that's where people > actually subscribe). If it's purely a matter of managing subscriptions by individual users, that's the path of least resistance, I think. I would not be surprised if there are things you don't actually need, but you'd need to implement so that Postorius doesn't blow up if some IMember feature you haven't implemented gets accessed. If in the future you might have an external personnel database with other stuff in it, and you want Mailman automatically synced to that, then IMember now might make sense to avoid technical debt in the future. But I don't know enough about IMember or your use case at the moment to make a useful recommendation. Steve

4 years, 2 months

[MM3-users] Adding users

by horvath.arpad.szfvar＠gmail.com

Hi, I've tried to add new members to the mailing list, but I failed even if I tried 3 ways: - manage.py shell - invitation letter - sending a letter to subscribe. I try to solve it with the Python shell now. Based on this site: https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode… I tried this one from Debian bash command line, but there is an error message, as you can see at the end. # pwd /usr/share/mailman3-web # ./manage.py shell In [1]: from mailman.interfaces.usermanager import IUserManager In [2]: from zope.component import getUtility In [3]: user_manager = getUtility(IUserManager) --------------------------------------------------------------------------- ComponentLookupError Traceback (most recent call last) <ipython-input-3-9500ce4250f0> in <module> ----> 1 user_manager = getUtility(IUserManager) /usr/lib/python3/dist-packages/zope/component/_api.py in getUtility(interface, name, context) 167 if utility is not None: 168 return utility --> 169 raise ComponentLookupError(interface, name) 170 171 def queryUtility(interface, name='', default=None, context=None): ComponentLookupError: (<InterfaceClass mailman.interfaces.usermanager.IUserManager>, '') What do I wrong. Should I stop all my mailman processes first? Thanks, Arpad

2 years, 9 months

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 12/5/19 1:40 PM, ikemulder(a)hotmail.com wrote: > > In the script I am filtering for 'mhonarc' ListArchivers, since the duplicate ListArchivers always seem to be mhonarc archivers. > > If this is not the appropriate place, please let me know - I would like to get to the bottom of this :). I see you've also filed <https://gitlab.com/mailman/mailman/issues/657>. Thank you for that. We are as puzzled as you are by this. It would help if you could detect this duplication when it happens and try to get more information. The problem is I can't see how to do that. I would start by adding some logging to the patch_put method of the ListArchivers class in mailman/rest/lists.py to log the list and the request. Then when you see the duplicate, you can check this log to see if anything suspicious happened just prior to that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

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

by Brian Carpenter

On 10/29/20 12:21 PM, Mark Sapiro wrote: > On 10/29/20 8:51 AM, Brian Carpenter wrote: >> On 10/29/20 11:33 AM, Mark Sapiro wrote: >>> The real question is if a user has a subscription waiting confirmation >>> and the policy is changed to moderate, is a second request rejected >>> because of the request waiting confirmation. If so, I think this is a >>> bug which should be fixed. >>> >> Do you think this is a bug with Mailman core or my system? > > If the current policy is moderate and the user has a prior request > waiting confirmation and a new request is rejected because of the prior > request waiting confirmation, I think that is a bug in core, but I don't > know if that is the case or not. I think it is a bug in Mailman 3 core. I am seeing the same behavior on my Postorius server. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Mark Sapiro

On 2/8/21 1:22 AM, r.woithe(a)callassoftware.com wrote: > Hello, > > i did try the script and unfortunately there is a problem. The script is deleting django-users are not member,nonmember ... of any lists.But thats not the point. Its ok if a user want to be only a django-user to see the archives and work with them. If a user sign's up for an account at /accounts/signup/ and then confirms her address, she will then be a Mailman user with a user and an address record even though not a member of any lists. > The script should delete django-users who dont confirm your email address. Change one line in the script from ``` if mm_user is None or len(list(mm_user.memberships.members)) == 0: ``` to ``` if mm_user is None: ``` And it will do what you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] DMARC DNS settings for MM3?

by Jay Hamilton-Roth

Emails from our list are currently being blocked by Google & Yahoo because of the "Dmarc policy of the sender domain" (according to Google Postmaster). Our list doesn't do any munging for "Reply goes to list" and our DMARC Mitigations is set for "No DMARC mitigations" and we're not DMARC Mitigating unconditionally. Given this is our MM3 policy, it's not clear what the DMARC DNS policy should be for consistency (note: we currently don't have a DMARC DNS setting). MM3 documentation doesn't have enough info, and reading up on DMARC Records it's not clear if we should be: v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@ourdomain.com -or- v=DMARC1;p=quarantine;pct=100;ruf=mailto:postmaster@ourdomain.com -or something else- Our DNS' SPF record is: v=spf1 ip4:aa.bb.cc.dd +a +mx ~all [Note: aa.bb.cc.dd is a redacted address] I'd rather not experiment on DMARC record settings for fear of making a bad situation worse. Thanks in advance for any assistance.

3 years, 6 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Thanks for the hint. Unfortunately it's not working as expected. I'm using the docker-setup and tried it in 2 different locations, but neither got the expected effect: - I put the variable in the mm-web-container-environment: mm-web: environment: - EMAIL_CONFIRMATION_FROM=myaddress(a)something.org - Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' What am I missing, where do I have to set this value correctly? Thanks for the help! Jens. Am 08.06.23 um 01:57 schrieb Mark Sapiro: > On 6/7/23 14:13, Jens Günther wrote: >> >> The more important question would be, where :-) since I already >> checked if I can set it to something alse, I might need a hint where >> exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not >> stumble upon it. If you don't know it, no problem, let's just wait for >> somebody who does, thanks. > > > It's the EMAIL_CONFIRMATION_FROM setting in your Django settings. >

2 years, 1 month

[MM3-users] Re: Badsignature on uwsgi-error.log

by Mark Sapiro

On 3/20/24 14:25, Helio Loureiro wrote: > Hi, > > I keep receiving a lot of errors like this: > > --- Logging error --- > Traceback (most recent call last): ... > "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", > line 55, in unsign > raise BadSignature('Signature "%s" does not match' % sig) > django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" > does not match ... > > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY > on setting.py are the same. Of those three, the api_key on mailman-hypperkitty.cfg and MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django thing and has nothing to do with the others. See https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key If you changed it, that's the issue. If you know what it was previously, you could set the previous value in SECRET_KEY_FALLBACKS, see https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

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

by Mark Sapiro

On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: > 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? > > Please see this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… The script in that post does all lists. For a single list see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… but note that the command line ``` $ shell -l list(a)example.com ``` should be ``` $ mailman shell -l list(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

8 months, 3 weeks

[MM3-users] Setup Question: Disk-Layout (Migrating from Mailman 2.1)

by christian.schneider＠tu-dortmund.de

Hello, actually I am running the latest available Mailman-2 Version on Ubuntu 20.04! Now it is really time to move on! :-) I want to set up a new server (Ubuntu-24.04) and install Mailman-3 with the Virtualenv setup method: https://docs.mailman3.org/en/latest/install/virtualenv.html As I know from my old Mailman-2.1 the archives could get quite big... ;-) So it seems very important to provide enough (expandable) disk space at the right place. (I plan to use a seperate partition with LVM for the path in question) But I could find no information about the location where hyperkitty stores the archives on an Ubuntu-/Linux-system. I assume the archives are stored underneath "/var/..." this is only a guess. But is this guess right? Another question is: How much space do I have to plan (roughly) for the "/opt"-partition for the mailman install if the archives are stored under "/var/..."? Any guidance ist very much appreciated! Thank you very much Chris

3 months, 2 weeks

[MM3-users] Re: New platform administrators

by Abhilash Raj

On Tue, Sep 18, 2018, at 1:14 PM, Simon Hanna wrote: > On 9/18/18 5:42 PM, Hellen Cubero wrote: > > Hello! > > I would like to know how to add a new site administrator to the mailman 3.2 > > platform. Can you help me please? > > You are probably referring to Postorius the webui? > > If yes, you just add another superuser. If the admin is enabled, you can > just visit https://you-url/admin sign in, and create a new user with > staff and superuser permissions. > > You can also do that on the cli using ./manage.py createsuperuser A better way would be to ask them to sign-up as a regular user and then you can go into the Admin Console (/admin) and add flags for Superuser for the user you want to promote. Create Superuser and Django's create user interfaces don't tie up with all-auth, which creates problems because their EmailAddress records aren't created, like they should be. -- thanks, Abhilash Raj (maxking)

6 years, 10 months

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

by Lars Schimmer

Hi! I did filed #248 in https://gitlab.com/mailman/hyperkitty/issues and tried to resolve this issue. Furst converted the database as noted in the ticket, no solution. Second search all unicode subject lines in DB for the specific mailinglist, and delete them all via hyperkitty web interface, no success, error still appears. As the error happens 10-12 time on strange times (6am 2:20 pm, 4:20pm), it does not look like a fixed cron job. 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? Those 30-60 error messsages/day are really annoying and on the other side do not look fine for mailman3 to break at such a easy task. (could have discarded those messages, also). So, please, howto fix this? 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, 8 months

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

by Mohsen Masoudfar

Hi, I am not sure, if it is designed this way, or I am doing something wrong. I created a list in MM3 as a hidden list, meaning: Show list on index page: NO and assigned the owner. When I login as Postorius web admin, I see the list on the list page which is listed as: (unadvertised*). This is fine. But when the owner or moderator login to Postorius they don't see the list at all. Of course if they add the list name at the end of the URL, they get to the list and as the owner can manage it too. My question is: I am just not sure, if I am missing something or this is how it is supposed to work? You could expect, that the owner or the moderator should see the list as (unadvertised*) too. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

5 years, 1 month

[MM3-users] Re: Default setting for Delivery status

by Mark Sapiro

On 10/10/22 15:31, Mark Dale via Mailman-users wrote: > > Where and how do I set the default setting of "Delivery status" to be > "Enabled". It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… > I'm not seeing any clues in mailman3-web/settings.py > > At the moment, a new subscriber is neither "Enabled" or "Disabled". That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. -- 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: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 19:09:20 CEST schrieb Mark Sapiro: > On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > > > All packages were upgraded fine. I applied the patch to > > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > > It shouldn't have been necessary to apply any patch. The head of the > GitLab hyperkitty master branch is already compatible with mistune 2.0.4 strange, I still had the line with the (not working) from mistune.scanner import escape_html, escape_url maybe because the migration step was not working at that time? > I'm guessing at some point you installed something which required you to > manually make this migration and that produced this conflict. Do you > have both 0017_alter_emailtemplate_language.py and > 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, > probably just removing 0017_auto_20220628_1132 will fix this? That's what I did in the meantime, and it works now! Thank you.

2 years, 9 months

[MM3-users] Re: configuring postfix local recipient table

by Mark Sapiro

On 4/29/25 00:17, Alexander Inzinger-Zrock via Mailman-users wrote: > [Status] > > Suggestion: > > It seems, we are wasting to much time with a probably messed up system. > I suggest, that i do as initially suggested [1] and start over with a > reinstall. > > Last idea before that would be to > > 1. delete the files: > > -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_domains > -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_domains.db > -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_lmtp > -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_lmtp.db > > 2. restart services > > 3. test if programms make new files > > 4. report to mailinglist > > Would that be of interest to someone? Yes. Also, is there anything in Mailman's logs from the time you ran `mailman aliases`? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

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

by Stephen J. Turnbull

Kyriakos Terzopoulos writes: > Firstly, thank you for your kind support. It seems that there is > some misunderstanding there from my side, since I did not use the > github repo to install mailman - I did it through pip install. Right, I understood that. The point is you can create a requirements.txt file by using "python -m pip freeze > requirements.txt", edit that file as suggested in the GitLab issue, and run "python -m pip install -r requirements.txt". I prefer this method because it documents exactly what I had in the venv at any given point in time. I think that should only reinstall the package with the new constraint, but it may refuse to do any installation because everything is already installed. In that case you have to either use "--force-reinstall" in the pip command (which will reinstall *all* packages) or you can use "python -m pip remove importlib_resources" followed by "python -m pip install 'importlib_resources>=1.1.0,<6.0'". Steve

1 year, 9 months

[MM3-users] Re: subscribing to a list from a WordPress site

by Odhiambo Washington

On Mon, Dec 25, 2023 at 1:08 PM Johannes Rohr <johannes(a)rohr.org> wrote: > Dear all, > > is there a wordpress plugin/widget allowing visitors to subscribe to a > mailman3 hosted mailing list? Else, what is the most convenient way? Sure, > I > could just link to the maiman site, but since joining a list is as easy as > sending mail to LISTNAME-join, there should be a simple way to impement > this. > What is the best practice? > Such plugins existed 10 years ago and aren't maintained. I just checked by doing a search in the "Add new plugin" window. However, isn't it just as easy as creating a CTA button on your WP site, which you then link to your MM3 subscription page? -- 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, 7 months

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

by Jonas Meurer

Am 18.09.2018 um 23:25 schrieb 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. I can confirm that these mails are sent in response to messages to -subscribe (not only to -request) with Mailman 3.2. I experienced the same as Hagen and I also wonder how to turn them of. Cheers, jonas

6 years, 10 months

[MM3-users] Re: very few moderation capabilities for moderators

by Mark Sapiro

On 9/18/21 2:52 PM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 18/9/21 22:59, Mark Sapiro wrote: >> On 9/18/21 11:56 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> >>> Just a one more silly question: >>> >>> Where do I can find the diferent values that memb.moderation_action >>> can take? (I want to prepare the "unhold" script too) >> >> >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/act… >> > > Thanks: It's perfect One more thing. It isn't obvious, but generally you want Action.defer rather than Action.accept. Action.defer will pass the moderation check, but still continue to check other rules such as administrivia, implicit-destination, max-recipients, max-size, no-subject and header filters whereas Action.accept will accept the message unconditionally and bypass those subsequent checks. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

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

by Stephen J. Turnbull

Onyeibo Oku writes: (backtrace reformatted for readability) > Oct 22 04:13:55 mail.server.tld mailman[9253]: > File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", > line 1616, in _get > Oct 22 04:13:55 mail.server.tld mailman[9253]: with open(path, 'rb') as stream: > Oct 22 04:13:55 mail.server.tld mailman[9253]: PermissionError: [Errno 13] > Permission denied: > '/opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO' That's just an ordinary attempt to read a file, nothing special about zope. It seems that that package was installed with the wrong ownership or permissions. Most likely you installed the package as root rather than the mailman user. Everything in a venv should be owned by the user:group it is intended for.[1] Assuming that the user that Mailman processes are running under is "mailman" with group "mailman", then chown -R mailman:mailman /opt/mailman/venv should do the trick. Steve Footnotes: [1] Probably there are applications where this is not true. But it is true for Mailman.

2 years, 9 months

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

by Mark Sapiro

On 3/23/23 08:42, Odhiambo Washington wrote: > On Thu, Mar 23, 2023 at 6:13 PM thomas--- via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Thanks both of you. I didn't know Debian11 version is out of date. I will >> try using pip. >> > No. Debian 11 is _not_ out of date. It's just that the preferred and easy > to support installation method is using the virtualenv. The Debian stable mailman packages definitely ARE out of date. bullseye (stable) has Mailman core 3.3.3 and django-mailman3 1.3.5 (current releases are 3.3.8 and 1.3.9 respectively) It is unclear what Postorius and HyperKitty versions are in mailman3-web 0+20200530-2. bookworm (testing) and sid (unstable) do have current versions of Mailman core and django-mailman3 and possibly mailman3-web 0+20200530-2.1 has current Postorius and HyperKitty, but those are generally not the Debian packages that most users would install. -- 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] Managing users in postorius

by Lieuallen, Thomas Otis

In our environment, people have multiple email addresses, any/all of which might be used as members or admin addresses. I try to steer people in the right direction, but inevitably, we end up with people registering the ‘wrong’ address or even both addresses. I don’t seem to have very much control with the site admin account. I’d like the ability to add a secondary address for a user instead of talking them through the process of doing it themselves. Is there a way that I’m not aware of? Additionally, when I look up users and choose ‘manage’, it only lists a person’s member roles. It doesn’t list any other roles (owner/admin, moderator, etc). Any way to fix that? I’m also curious what the process would be for merging two postorius accounts into one? My thought process was that I should remove one and then have the user add that email address to the other account. But, if you delete the account, it will unsubscribe the user. Thank you Tom Lieuallen Oregon State University

10 months, 1 week

[MM3-users] Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Mark Sapiro

On 3/31/25 06:26, Philip Bondi wrote: > My /etc/mailman3/urls.py is empty. > > Should I, like it indicates in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > cp /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py /etc/mailman3/urls.py > chown mailman:mailman /etc/mailman3/urls.py > and add to /etc/mailman3/settings.py > > ROOT_URLCONF = 'urls' You can do all of that, but it's probably unnecessary. What is in /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py? compare it to https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py > After completing above, https://systemdatabase.ca/mailman3 still gives > Service Unavailable It appears that https://systemdatabase.ca/postorius works so the issue is almost certainly that your urls.py is missing path('mailman3/', include('postorius.urls')), -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Relay Access Denied

by Mark Sapiro

On 7/22/25 10:25 AM, jkoral(a)luc.edu wrote: > Here is what I have in postfox_lmtp. Do I need to add another line for joetest(a)lists.luc.edu as well? > > joetest(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-bounces(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-confirm(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-join(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-leave(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-owner(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-request(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-subscribe(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-unsubscribe(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 If you want to address the lists @lists.luc.edu, the list names should be, e.g. joetest(a)lists.luc.edu, not joetest(a)listservnew.luc.edu. If you want to be able to use either domain for list mail, that's more involved. If you want this, say so and as I have time I can make suggestions., but I suspect you really only want to use the lists.luc.edu domain. -- 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: Member Issue Discovered

by Mark Dadgar

On Oct 20, 2020, at 9:13 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > 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? Yeah, that makes sense for very large installations. Good point. IIRC, mm2 had the concept of a site-admin. It would be nice if it had worked for them, though. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 9 months

[MM3-users] Error message from monthly cronjob

by Johannes Rohr

Dear all, Mailman3 on my system is installed in virtualenv. Each month I get the following error message. This error does not seem to have a serious impact on the functioning of mailman, still, what does it mean and how do I get rid of it? Thanks for any hints! Johannes -------- Weitergeleitete Nachricht -------- Betreff: Cron <mailman@*** /opt/mailman/venv/bin/mailman-web runjobs monthly Datum: Fri, 1 Dec 2023 05:56:40 +0100 (CET) Von: Cron Daemon <root(a)mail.rooot.de> An: mailman@*** ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django_extensions/management/commands/runjobs.py", line 40, in runjobs job().execute() File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/jobs/update_and_clean_index.py", line 37, in execute run_with_lock(update_index, remove=True) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", line 177, in run_with_lock with lock: File "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ self.unlock() File "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 420, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked

1 year, 7 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Ken Alker

As an aside, for anyone else who is trying to do the same (and to give some background into my procedures so far), I have been following these references: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-virtualenv> My goal is to create the least change to file locations and configuration files as possible (I may move things into more "source-installed centric" locations once I have things working again), thus, many files are still in the original Debian package-allocated directories. That said, I was forced to move mailman3web.db to /opt/mailman/web as sqlite (and, hence, mailman-web) simply could not open the database as user mailman from my virtual environment (even with mailman3web.db file permissions set to 777 and owner.group set to mailman.mailman). So far I've gotten mailman running properly and handling the mailing lists, however, I have not gotten the web interface working again.

2 years, 1 month

[MM3-users] REST API for list owners/moderators

by Stephen J. Turnbull

mathias(a)koerber.org writes: > Does Mailman 3 have an REST API that allows list-owners/moderators > to perform list-management functions without having access to the > whole server/other lists etc? No. You can provide selective access to a selection of REST API endpoints via a front-end webserver such as Apache or nginx, but it would be rather painful, and possibly also rather insecure.[1] > The documentation seems to only indicate a single one-admin-user > REST API that should not even be accessible from outside? That's right. If the documentation only "indicates" that, we should fix the documentation. The point of separating Postorius from core was to put authentication and authorization in the hands of people who know how to do it (ie, Django). Footnotes: [1] That depends on what threats you're worried about. But the endpoint hierarchy is designed to make sense to application programmers, not to make it easy to disable access to "dangerous" endpoints that allow deleting lists or extracting user information.

1 year, 6 months

[MM3-users] Re: How to get Mailman core to provide more debug info in a running environment

by Henrik Rasmussen

> From: Barry Warsaw [mailto:barry@list.org] > Sent: 28. september 2017 16:38 > >On Sep 28, 2017, at 07:28, Henrik Rasmussen <her(a)adm.ku.dk> wrote: > >> [logging.smtp-failure] >> path: smtp.log > > That’s a typo/leftover in the schema.cfg comments. There is no longer an smtp-failure log so [logging.smtp-failure] can’t be used. Oh okay. I suppose that smtp failures will be logged in the smtp.log by default then? Or otherwise, how do I increase logging if needed. For now I found the problem by consulting the mailman.log. > However you said that “stopped incoming mails”. Can you provide more information on exactly what happened? Bogus logging sections should effectively be ignored. Actually I think my Postfix docker container got confused when restarting the Mailman core container. I just associated it with my change in mailman-extra.cfg. -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

7 years, 10 months

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 6/6/19 6:02 AM, Henrik Rasmussen wrote: > > Still, attachments (PDF) is removed by Mailman. I as the list admin to send a new mail, but hold it back, to see what type it is. You have to add the MIME types for the attachments you want kept the the list's pass_types. You need to do this via mailman shell or REST as it isn't currently exposed in Postorius. Here's an example from a list that wants to accept PDFs as well as word processing and spreadsheet documents. Note that nappdf and x-pdf are uncommon PDF subtypes that I have seen. ['multipart', 'message/rfc822', 'text/plain', 'text/html', 'application/pdf', 'application/nappdf', 'application/x-pdf', 'application/rtf', 'application/vnd.oasis.opendocument.spreadsheet', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', 'application/vnd.ms-excel', 'application/vnd.oasis.opendocument.text', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/msword' ] -- 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] Re: I like your style, but what is it?

by Mark Sapiro

On 1/26/21 9:12 PM, Stephen Willey Mats Mats wrote: > > How do I get a dump of list settings for each style. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py> and <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/default…>. > Thanks, > steve > > p.s. the search on https://mailman.readthedocs.io/en/latest/README.html gives results but every link needs to have ‘projects/mailman/‘ removed from the url to work. Or have its domain changed from `mailman.readthedocs.io` to `docs.mailman3.org`. If you start at <https://docs.mailman3.org/en/latest/> or just go to <https://docs.mailman3.org/projects/mailman/en/latest/README.html>, I think everything works. Granted, search from <https://mailman.readthedocs.io/en/latest/README.html> should work too, but I'm not sure offhand whether its a Sphinx or a Read the Docs issue or how to fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Mailman and Exim 4.94.2 (Debian Bullseye)

by Andrew Hodgson

Hi. I moved Mailman instance to a machine running Debian Bullseye last week. Ran into an issue with the Exim transport from this doc: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… The issue I ran into was that Exim wasn't able to resolve localhost in order to connect to the LMTP listener. I changed VPS provider at the same time (moved from Bytemark to Gandi) so not sure if they were doing anything different with DNS, but by default Exim doesn't use standard libraries to lookup hosts: https://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_dnslookup_… I solved the issue by using the following configuration on the Mailman router: # /etc/exim4/conf.d/transport/55_mm3_transport mailman3_transport: driver = smtp protocol = lmtp allow_localhost gethostbyname hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true I haven't defined the lmtp settings at all in mailman.cfg meaning they are using the default settings of 127.0.0.1:8024. Is this the best modification to make to the Exim config or should I go an alternative route? Thanks. Andrew.

3 years, 9 months

[MM3-users] Re: mailman3 digest sending questions and also adding docker to the mix

by Abhilash Raj

On Wed, Apr 13, 2022, at 3:35 PM, bob B via Mailman-users wrote: > No worries, I hoping Abhilash will respond to the docker, > > But for non docker installs I assume that it sends out digest daily? > when "Send Digest Periodically " is set to yes, is that correct? Docker install currently doesn’t run routine cron jobs in Core like it does in Hyperkitty. Part of the problem is that there is no engine to run the cron jobs in the container. I _should_ figure out a way to do that using supervisord or something similar inside the image, but that is still not there yet. There is https://github.com/maxking/docker-mailman/issues/420 which could use some help with fixes or even simply documentation udpates. > _______________________________________________ > 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, 3 months

[MM3-users] Question to add "alias" address in list by group

by Pierre Malard

Everithing is in the subject. We must add some (a lot) alias address for members and I don’t find any indications on doc to do that with « mailman » command. Is their a way? -- Pierre Malard « Il faut créer en même temps les élites et les débouchés, le syndica- lisme et les usines. Faire l'un sans l'autre, c'est travailler pour le malheur du peuple. » Romain Gary - "Les racines du ciel" |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 3 months

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

by Abhilash Raj

On Sun, 20 Aug 2017 20:50:39 +0200 (CEST) Ruben Ibanez <ribanez(a)sciops.esa.int> wrote: > Hi Abhilash, > > Thanks for your reply. > > The point is, I think I'm missing something. I'm just a sysadmin who wants to deploy Mailman 3.x to be used for an operational environment, like any other software. Is this software actually ready for that? There are production environments running Mailman 3.1 right now if that is your questions, see https://lists.mailman3.org. Although, I guess you already saw that when subscribing to this list ;) > Of course, I'm not asking for .rpm, .deb, etc... because I understand that's > quite complex, but I tried it following all available guides, including the > Contributor's Guide, and it seems impossible to get it running at the first > time (or just to get it running) without getting crazy or fixing lots of > unexpected errors during installation. It would be helpful if you send in those errors here. It will help us debug your problem and also improve the guide for the people using it in future. One small problem about the configuration, off the top of my head, can cause some problems in the "Mailman Suite Installation" Guide[1]. I have that on my todo to fix. But, apart from that everything else should work! [1]: http://docs.mailman3.org/en/latest/prodsetup.html You would have to do some additional configuration for the web frontend to work and for the mail servers to talk to Mailman and Frontend separately, both of which is also mentioned in the documentation under "Configuring Mailman Core" and "Configure Web Frontend". Contributor's guide is not focused on deploying but just setting it up locally to play with and modify the source itself. > Have you tried to deploy Mailman 3.x strictly following the documentation? I think people have used it in past to successfully deploy Mailman 3.x, but without looking at the errors you are facing I don't have any clue as to why it doesn't work for you! > > By the way, many thanks for your hard work! > > Cheers, > RI > > > From: "Abhilash Raj" <maxking(a)asynchronous.in> > To: ribanez(a)sciops.esa.int > Cc: mailman-users(a)mailman3.org > Sent: Saturday, August 19, 2017 8:55:20 AM > Subject: Re: [MM3-users] Which documentation to follow for installation > > On Fri, 18 Aug 2017 09:40:37 -0000 > ribanez(a)sciops.esa.int wrote: > > > Hi everyone, > > > > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to > > look for documentation. I found two different sites: > > > > https://mailman.readthedocs.io/en/latest/ > > http://docs.mailman3.org/en/latest/ > > Both of the above are actually latest documentation, > > docs.mailman3.org should be the one to look for installations guidelines for > the entire Mailman 3.x Suite, > > mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles > the mail. > > http://docs.mailman3.org/en/latest/prodsetup.html > > This should be the best place to start, be sure to look at the Pre-Installation > Guide if you are new to the Python ecosystem. > > > > > Do you know which one should be followed? Both at the same time? I find it > > quite unclear... and this installation will be for an operational environment. > > > > Also, there are some (official?...) docker images, but all images are for > > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. > > It is meant for Mailman 3.X series and is maintained by me. It currently > includes the latest releases for all the Mailman's sub-projects, also Mailman > 3.1. > > > Hope that helps! > > -- thanks, Abhilash Raj

7 years, 11 months

[MM3-users] Re: Mailman 3 api php

by Mark Sapiro

On 03/14/2017 05:24 AM, david.terni(a)gmail.com wrote: > Hi, > I apologize if this is't the right place but I don't understand how connect mailman 3 with api and php/CURL. It's possibile to do it? I tried to use the same url used with mailman2 but doesn't work. Mailman 3 is completely different from Mailman 2 in this respect. While it would be possible to use php/CURL to post to Postorius analagously to posting to the Mailman 2 web UI, this is not how it is done. Mailman 3 core exposes a RESTful api on localhost. Both Postorius and HyperKitty use this UI to communicate with the core and you should too. Start at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/rest/docs/basic.ht…>. The "Previous" link will take you to the section on Addresses and the "Next" links will take you through the rest of the REST api. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Mailman 3 on RHEL 7 help

by Abhilash Raj

On Thu, Oct 25, 2018, at 4:24 PM, A Almeda wrote: > Hi. I am trying to install mailman 3 on RHEL7. Docker install is not a > possibility. I am trying to install it using a bundler by following > https://media.readthedocs.org/pdf/mailman-bundler/stable/mailman-bundler.pdf, > but after logging in as mailman, I can't do virtualenv venv. It works if > I login as root, but still fails during buildout. That document is quite a bit old. You can find the latest instructions here[1], if you face issues with instructions in there, please let us know. [1]: http://docs.mailman3.org/en/latest/prodsetup.html > > In short, I need help. Has anyone of you guys installed mailman 3 on > RHEL 7 or CEntOS 7? If so would you share me detailed instructions? > Thank you in advance. > _______________________________________________ > 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, 9 months

[MM3-users] Re: Welcome Message

by Mark Sapiro

On 4/16/19 9:18 AM, brian(a)emwd.com wrote: > Thanks Mark. I added the POSTORIUS_TEMPLATE_BASE_URL to my settings: > > /opt/mailman/web/settings_local.py > > Now I get the following errors: ... > requests.exceptions.SSLError: HTTPSConnectionPool(host='mailman3.emwd.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/testlist.mailman3.emwd.com/list:user:notice:welcome (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)'),)) > Apr 16 15:38:44 2019 (28) 172.19.199.3 - - "POST /3.1/members HTTP/1.1" 500 59 > > I am confused by the SSL errors. I have a valid SSL certificate installed on mailman3.emwd.com. These errors occur whether the POSTORIUS_TEMPLATE_BASE_URL is using http or https. I'm confused too. What happens if you just do in a python3 interactive session >>> import requests >>> response = requests.get('https://mailman3.emwd.com/postorius/api/templates/list/testlist.mailman3.em…') and if you get this far >>> response.status_code >>> response.text -- 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: Customising hyperkitty and postorius

by Mark Sapiro

On 11/18/20 5:16 PM, peter(a)chubb.wattle.id.au wrote: > > Hi, > I've put up a mailman3 instance, with hyperkitty enabled, and > imported all my mailman2.1 archives -- it all seems to be > working. > > How do I now customise the look and feel of my site? > > In particular, I'd like to render archived emails with a > monospace font, and I'd like to change the colour scheme and > styles of all the pages to match other pages on the same website. HyperKitty will display a message in monospace if you click the 'A' icon at the bottom of the message. I don't know offhand how you would make that the default. For styles, they are mostly SCSS in the directory hyperkitty/static and CSS in the directory postorius/static/postorius. I think you'd have to find the relevant styles and edit them. -- 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: Mysterious Bounces Being Logged

by Brian Carpenter

On 3/26/21 6:13 PM, Mark Sapiro wrote: > Absolutely. At first MM3 wasn't processing bounces at all. A GSOC student did the bulk of the current implementation and we were happy to get that even though this piece was missing. We know we need it. If you don't think we're working fast enough, you can submit a merge request or dock our pay. I don't understand the sarcasm here at all. I am just trying to figure out what the PRIORITIES are from the Mailman 3 developers. That's all. BTW, I still haven't figured it out. It still doesn't explain why Postfix is not recording the delivery issues which I assume has nothing to do with Mailman 3. I see successful deliveries with Postfix and bounces with Mailman 3 core. I never seen that with Mailman 2 and Exim. They always matched. If you can help me to understand that with out the petty sarcasms then that would be great. If not, then ok. -- 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 Odhiambo Washington

On Sun, Oct 1, 2023 at 1:41 PM Wikinaut <mail(a)tgries.de> wrote: > > Maybe you can make your life a little more bearable by abandoning the > use of Debian packages and embracing the virtualenv.... > > I fully understand. Need to look up how to smoothly backup the mailman3 > settings and list databases in order to make that move with losing stuff... > (kinda "mailman3 backup all" and mailman3 restore all" :-) > You do not really need to change much. The /etc/mailman3/* are almost usable as it with a little modification to file paths. The databases are also usable as-is. You may need to move a few files to the virtualenv directory tree and change permissions accordingly. -- 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

Search results for query "dO"