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

[MM3-users] Re: CPU usage when idle

by roughnecks

Il 28/05/2025 23:42, Mark Sapiro ha scritto: > On 5/28/25 08:27, roughnecks via Mailman-users wrote: >> >> It's the manage.py qcluster whatever is called. I have shut down MM >> for the time being, because I'm not fully motivated to have it >> running, so I can't be more accurate right now. > > I don't know how qcluster is configured in the Debian packages (which > are out of date and possibly buggy anyway). You may be using django-q > <https://django-q.readthedocs.io/en/latest/> and if so, you should > migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both > typically use memcached as a backend. I wouldn't know how to migrate and if that means doing anything not in the debian-way (haven't opened any link so far). About qcluster configs, yes, all correct but there is no configuration for caches, so probably it's the default one you specified. I can look into this. > You can get info about what qcluster is doing with `manage.py qinfo` and > monitor things with `manage.py qmemory` and `manage.py qmonitor`. Thanks, helpful.

11 months

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

The REST API documentation is a bit informal. As someone who is not familiar with mailman, and who doesn't know python, they are a bit of a slog. One day it would be nice to augment the documentation with a formal and complete reference document. Something like this one <https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_REST_API_R…>. A formal reference manual needs a complete listing of every type of object, all possible operations on each object, and all required and optional parameters. Since creating a formal document like that is probably out of scope, at a minimum it would be good to specify that boolean values are passed as JSON strings, not JSON booleans. It might be worth seeing if the code can be enhanced to allow the boolean values to be sent in using JSON booleans as well as JSON strings. Thanks again for the prompt response! -- Stephen On Tue, Jan 18, 2022 at 4:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/22 10:53 AM, Stephen Daniel wrote: > > 2nd follow-up. Apologies for spamming this list. > > > > I went wandering through the code as suggested by the traceback. I > > discovered that thee "as_boolean" routine is expecting a string argument > > but getting a boolean argument. > > > > So, If I send the booleans as strings, with values "true" or "false", all > > is well. > > This is not what the API documentation suggests I should do. Can someone > > either fix the documentation or the code? > > > Those snippets in the documentation are doctests. That code is actually > executed by unit testing and passes. In all those snippets, dump_json is > passing the second argument as `data` to > mailman.testing.documentation.dump_json() which in turn calls > mailman.testing.documentation.call_http() which calls > mailman.testing.helpers.call_api() which ultimately calls > requests.request() with the same `data` argument. > > So basically, the issue is the difference between how requests.request() > handles that `data` dictionary in creating the POST data and whatever > you are doing. > > Possibly we could add some caveat to > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…> > > or possibly elsewhere. Do you have a suggestion as to what? > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 3 months

[MM3-users] Re: Trying basic install of mailman3 in docker, but how do you set allowed hosts?

by Abhilash Raj

On Thu, Jul 8, 2021, at 12:23 PM, bob B wrote: > I am starting small, My goal is just to get mailman3 running in docker > and test the website access via curl from the host, then I will move > on from there > > In the docker instructions it says > > SERVE_FROM_DOMAIN: The domain name from which Django will be served. To > be added to ALLOWED_HOSTS in django settings. Default value is not set. > This also replaces Django's default example.com SITE and becomes the > default SITE (with SITE_ID=1). Perhaps that is my English there, but what it really meant to say was you should set "SERVE_FROM_DOMAIN" in your "environment" section of the docker-compose.yaml file and it will add the value of that variable to Django's ALLOWED_HOSTS settings for you [1]. If you think it could be re-worded for clarity, please feel free to let me know or open a PR in the Github repo. [1]: https://github.com/maxking/docker-mailman/blob/main/web/mailman-web/setting… Also, "localhost" is already added to the list of ALLOWED_HOSTS, so if you are able to point to the container using that, it should work without setting the SERVE_FROM_DOMAIN. Abhilash > But where do I set the ALLOWED_HOSTS I added this to the yaml file > - ALLOWED_HOSTS=127.0.0.1 under environments > > > mailman-web: > image: maxking/mailman-web:0.3 > container_name: mailman-web > hostname: mailman-web > depends_on: > - database > links: > - mailman-core:mailman-core > - database:database > volumes: > - /opt/mailman/web:/opt/mailman-web-data > environment: > - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static > - ALLOWED_HOSTS=127.0.0.1 > - DATABASE_TYPE=postgres > - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb > - SECRET_KEY=333blah-blah-secret > - HYPERKITTY_API_KEY=333someapikey > ports: > - "127.0.0.1:8000:8000" # HTTP > - "127.0.0.1:8080:8080" # uwsgi > networks: > mailman: > > > > But when I try: > [docker-mailman]# curl 127.0.0.1:8000 > <h1>Bad Request (400)</h1>[root@bmimailmandr1 docker-mailman]# > [root@bmimailmandr1 docker-mailman]# > > > > I see this in the logs > > [docker-mailman]# cat /opt/mailman/web/logs/mailmanweb.log > WARNING 2021-07-08 17:40:46,979 1642 django.request Bad Request: / > ERROR 2021-07-08 19:20:58,416 1641 django.security.DisallowedHost > Invalid HTTP_HOST header: '127.0.0.1:8000'. You may need to add > '127.0.0.1' to ALLOWED_HOSTS. > WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: / > WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: / > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 9 months

[MM3-users] Re: Error 500 on held_messages page

by Mark Sapiro

On 2/3/22 08:01, Stephan Krinetzki wrote: > Hello all, > > we now have at least one mailing list (there may be more affected) that generates a 500 error when calling the held_messages page. After looking at the held messages via the mailman shell, we have identified three mails that have neither a subject nor a message body. How can we remove these three mails from the database? This shouldn't be an issue, at least with Mailman core 3.3.5, unless I don't understand. Note that there are 3 tables involved. The request (IListRequests), the pendings (IPended and IPendedKeyValue), and the held message (IMessageStore). > This is the mailman shell command we used: > > mailman shell -l listname(a)lists.example.com > <removed> > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > Die Variable 'm' ist die listname(a)lists.example.com Mailingliste > >>> msg_db = getUtility(IMessageStore) > >>> req_db = IListRequests(m) > >>> reqs = list(req_db.held_requests) > >>> for req in reqs: > ... print('{}: {}'.format(req.id, req.request_type)) > ... > 32598: 1 > [...] > 107656: 1 > 107737: 1 > 107758: 1 OK, you have requests. > >>> from mailman.app.moderator import handle_message > >>> handle_message(m, 107758, Action.discard) > >>> reqs = list(req_db.held_requests) > >>> for req in reqs: > ... print('{}: {}'.format(req.id, req.request_type)) > ... > 32598: 1 > [...] > 107656: 1 > 107737: 1 OK, you discarded the message held with request id 107758. > >>> handle_message(m, 92927, Action.discard) > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/app/moderator.py", line 112, in handle_message > key, msgdata = requestdb.get_request(id) > TypeError: 'NoneType' object is not iterable > >>> There is no request with id 92927. Why do you think there should be? If by remove them from the database, you mean just from the messagestore, you can do (using your above) msg_db.delete_message('the_message_id') To delete a pending request for which there is no request id, e.g. the id 92927 above, you could do ``` pendings = getUtility(IPendings) for token, data in pendings.find(pend_type='held message'): if data and data['id'] == 92927: pendings.confirm(token, expunge=True) ``` Mailman core 3.3.5 has a lot of changes to address this issue. Also see https://gitlab.com/mailman/mailman/-/issues/946 -- 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: Speed/progress of update_index_one_list?

by Stephen J. Turnbull

Philip Colmer writes: > I have now switched to Xapian but, in a way, my original questions still > stand. Is there a way of monitoring the progress of > "update_index_one_list"? What can I do to the specification of the server > to make that process go (much) faster? I see you've already gone to the Xapian lists, which I think is the right place to ask. We appreciate that! But I hope everyone will feel free to ask such questions here (just don't get too upset if we suggest going to the upstream channels in lieu of providing answers ourselves :-). If you do get an answer, feel free to bring it back and ask for Mailman automation for it (as a tracker issue, please, so it doesn't get lost). As I've mentioned before, it's That Time of Year when we start to prepare for GSoC. No guarantees and eventually the students choose their own projects, but suggestions are welcome. > By the way, just in case anyone else is looking to use Xapian, > installing and setting up Xapian for HyperKitty can be boiled down > to: Thanks for the hints! Steve

4 years, 3 months

[MM3-users] Re: GDPR - save subscriptions confirmation emails

by contact＠maadix.net

Thanks Selva for you answer. In my Mailman 3 installation there is no /var/log/mailman/subscribe I have logs about confirmations emails in mailman/var/logs/smtp.log the format is the following: Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) handling connection Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'LHLO mails.example.com' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'MAIL FROM:<contact(a)maadix.net>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) sender: contact(a)example.net Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'RCPT TO:<prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) recip: prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'DATA' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'QUIT' So, one solution that comes to my mind is to grep this log file. This is not a perfect solution and the full confirmation email is still missing. I am not sure if this would be GDPR compliant. Maddish El 03/06/18 a las 18:17, Selva Nair escribió: > Hi, > > On Sun, Jun 3, 2018 at 10:12 AM, contact(a)maadix.net <contact(a)maadix.net> wrote: >> >> Hi, >> >> I am new in the list. I have been looking for this topic in the archives >> in order to avoid duplicate, but I could not find any thread. >> >> According to the new GDPR rules, lists owners need to have a >> confirmation from subscribers, and this is easy to do with Mailman 3. >> >> What I can't figure out is how to save all the confirmation emails >> received from users. >> >> I only see the confirmations commands emails in the logs, >> >> Is there another place/way to store them? > > We have been doing this with mailman2 since Canadian Anti-Spam Law (CASL) > got enacted (2014) by independently archiving the confirmation messages. > With postfix we use recipient_bcc_maps and a script to do some extra filtering > but its clunky, and does not check that the confirmation succeeded or not. > > A feature within mailman to archive successful confirmations would be > useful. Keeping unsubscribe requests and evidence of subsequent > actions also seems necessary at least as per CASL. > > That said, we also keep the /var/log/mailman/subscribe logs (not sure > what that would be in mailman 3). Although the log has a single line > for each action, it may be enough to show (?) that a double opt-in process > was properly followed or unsub request was acted up on. > > Thanks, > > Selva > -- Maadix *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

7 years, 10 months

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

by Allan Hansen

Dear Mailman 3 wizards, Our subscription process requires that the applicant answers a few questions and sends them to the list moderator. Not having a template that gets sent on all subscribe requests, I'm using the 'list:admin:action:subscribe' template. This gets sent to the list moderator, who then sends it forward to the applicant. This is rather tedious. I would like the template to be sent directly to the applicant. There is a template, 'list:user:action:subscribe' that almost does this, but it gets sent only if the email address of the applicant is unverified. A good number of our applicants are already on our lists, so they would not get this template if we set the Subscription Policy to 'Confirm, then moderate'. Our Subscription Policy is currently: 'Moderate' for all lists. I figure that three modifications can be used to fix this: a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. c. That the current 'list:user:action:subscribe' be changed in published Mailman 3 source to 'list:user:action:confirm' and a new template ''list:user:action:subscribe' be set up to be sent when any subscribe request is made. This is more work, of course, so not likely a good thing to hack locally. It could be useful to other users. Any suggestions on how to best and most quickly do the above would be appreciated, starting with (a.) or (b.). Clearly, (a.) and (b.), if we do one of those, are hacks that will need to be applied upon Mailman updates. That's fine by me, as I'm in rush to get this done. I'd welcome pointers as to which file to change and how. Of these two options, which would be the least work? (c.) could be entered as a longer-term enhancement request. I can submit that request if you like. Yours, Allan Hansen P.S.: Thank you for the enhancement that lets moderators see the member lists. It has been a big help for us. GNU Mailman 3.3.8 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /opt/mailman/mm/mailman.cfg db url: postgresql://mailman:VWy26K4pUfU4jw@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass

3 years, 1 month

[MM3-users] Re: Anyone using Rspamd with Mailman 3?

by Philip Colmer

On Wed, 22 Sept 2021 at 10:14, Bjoern Franke via Mailman-users <mailman-users(a)mailman3.org> wrote: > > Hi, > > > > > I'm having a lot of trouble getting DKIM headers rewritten by Rspamd > > after Mailman 3 has altered the subject line and added the signature > > to the body and that, in turn, seems to then be causing Rspamd to not > > add the ARC headers. > > why don't you let Mailman3 do the DMARC mitigation? That is certainly an option. My main concern with this approach is that it needs to be configured on a per-list basis, as far as I can tell. My preference is to try and find an approach that works without modifying the settings per-list. I'll do some more testing with DMARC mitigation enabled to review the Rspamd logs under that scenario and see what breaks then. I'm starting to think that there might be a bug in Rspamd so my other next step is to revert to OpenDKIM for the DKIM headers and use Rspamd for the ARC headers (since I couldn't get OpenARC to work). Regards Philip

4 years, 7 months

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

by Mark Sapiro

On 6/16/22 15:46, Dan Caballero wrote: > Which database table contains these pending subscriptions? I checked the "members" and "address" tables but no luck yet. > > I'm trying to help someone clear a few hundred of these. I can try writing a Python script to use the "hex_token" values in the Python dict. But maybe doing something via MySQL would be easier. The tables are `pended`, `pendedkeyvalue` and `workflowstate`, but don't do it via MySQL. A `mailman shell` interaction like this is better. ``` $ ./mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> util = getUtility(IPendings) >>> for token, data in util.find(mlist=m, pend_type='subscription'): ... if data.token_owner == 'subscriber': ... util.confirm(token, expunge=True) ... >>> 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, 10 months

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

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. No. the mailman-web migrate command will apply relevant migrations for various django projects. You do need to rin it after upgrading things like hyperkitty, postorius and django-mailman3 and other dependencies which may have defined migrations for various database schema changes, but this will do nothing for your data. For that, you need to dump the mailman and mailmanweb databases on the old server and import them on the new server. > but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? With the dump and other utilities from your database manager. Almost everything is in the database. There are some things in Mailman's var/ directory, but those can simply be moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Changing default language for lists

by Stephen J. Turnbull

Wessel Kraaij writes: > How can I change the default language for lists (and other > defaults)? I changed it in mailman-core but Postorius overrides > these core defaults with a patch. You need to be more specific about what you did, what you expect to happen in various cases, and what you mean by "patch". Specifically, what language do you want as default, how did you spell it in mailman.cfg, have you checked that there are no list-specific settings (that override the default), is the problem in distributed posts, in Mailman-generated notifications, or in web pages? Specifically which part of posts, notifications, or web pages have unexpected languages? What language are they supposed to be, and what language(s) do you see? For context, here is how language setting works: In mailman.cfg (usually located at /etc/mailman3/mailman.cfg), there is a `default_language` variable in the [mailman] section (hardcoded to "en" if not overridden). This can be overridden on a per-list basis, usually configured using Postorius. Postorius has read-only access to the default_language setting, I believe, but I am not aware of any way for Postorius to set it. The settings in Mailman core directly control which language's templates and gettext substitutions are used in emails generated by Mailman and in footers and the like added to posts distributed by Mailman. In any given context, for each substitution, the list's language is checked for a translation, then the site's default language, then English is the fallback. You can end up with mixed languages if some contexts have not been translated. Postorius and HyperKitty both use their own templates which are separately provided in those packages. As far as I know they do not have a default language setting of their own (although the Django framework probably does, we don't use that). Instead, through the `mailmanclient` library they read the current list's preferences (and Postorius can change the list preference but not the site default), and fetch templates and variable substitutions in the same way. It is quite possible that the language you specified is missing the translations you're looking for, or that the language code you specified is not one that Mailman recognizes. > I am using the docker version of maxking I don't think that matters, but Abhilash (maxking) is the only real expert on docker-mailman, and he's not following this list closely at this time. Check the docker-mailman documentation for the preferred method of communicating with him if it seems to be relevant. Regards, Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 5 days

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

by Barry Warsaw

On Dec 09, 2016, at 09:37 AM, Mark Sapiro wrote: >I understand you need to feel comfortable about everything going into >the core and this takes time and energy to review all the MRs, but I >think it is pretty important to get the DMARC mitigations into the core. >If there's anything I can do to help with this, let me know. > >I will rebase my branch again and possibly make one minor tweak, but I >think it should be OK. Thanks for pushing back on this Mark. Obviously, I have a high degree of trust in your work, but yeah, my compulsive behavior is showing through. ;) Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. >I can also work on Postorius. Also in this vein I have a question. >Should the DMARC settings be added to the Alter Messages tab in the List >Settings view or would it be better to have a separate DMARC Mitigations >tab. My gut reaction is to add a separate DMARC Mitigations tab, but Florian and Terri have final say I think. Cheers, -Barry

9 years, 4 months

[MM3-users] Re: Mailman 3 Privacy Policies, GDPR, etc and social logins

by Jered Floyd

This was what I was using as well, but it failed to meet their requirements for some ineffable reason. I had a few back-and-forths with someone for whom English was not their first language, and got them to accept a slightly modified version that I posted at https://www.convivian.com/mailman-privacy.html Now, the latest is that I have a new message noting that apps requesting user data (e.g. email address) must be linked to Business Profiles (text below). Django-allauth is cool, but I think it's not going to be long for this world and we'll just have to do internal auth. Disappointing from a workflow perspective, but I'm happy to dissuade subscribers to not use Facebook. Regards, --Jered P.S. The fresh hell from Facebook: You are receiving this message because Mailman List Manager is not connected to a verified Meta Business Account. On Feb 1, 2023 Meta began requiring business verification for apps that request access to data from users (for some apps this is called advanced access). Learn more about this requirement. [https://developers.facebook.com/blog/post/2023/02/01/developer-platform-req…] Here’s what a person with full control of your Business Account needs to do by Feb 2, 2024 to maintain access: Connect the app to a Business Account, if you haven't already. Complete business verification for the Business Account. Business Accounts connect your Facebook Pages, Instagram accounts and the people who work on them, so you can manage them all in one place. ----- On Sep 19, 2023, at 5:00 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 9/19/23 6:22 AM, Jered Floyd wrote: >> >> This is a bit of a headache. Do we have a draft of a community Privacy Policy >> for a vanilla Mailman 3 install that meets Facebook's requirements? Is this >> going to be a constantly unraveling thread of future GDPR and Right to Be >> Forgotten troubles, since there doesn't seem to be an easy way to scrub a >> subscriber from Hyperkitty archives if they request so? How have others >> addressed this situation? > > > I use https://www.list.org/privacy.html which appears to satisfy Facebook. > > -- > 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 jered(a)convivian.com

2 years, 6 months

[MM3-users] Re: Can't remove footer(s)

by Mark Sapiro

On 10/11/2018 02:04 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> The templates named list_member_digest_footer.txt and >> list_member_regular_footer.txt (with underscores) were created by >> import21 and set as the URIs for those templates. Had you just copied >> /dev/null (or otherwise made empty) those files and done nothing else, >> that would have done what you wanted, but since you deleted the template >> URIs for the list, the template names are now the default > > How do I make these not default? You can set them via ITemplateManager. > Or when I upgrade to V3.2.2 will I be able to just empty the templates in /postorius/lists/LISTNAME/templates? You could except Postorius won't let you set an empty value for a template and deleting a template in Postorius just reverts to using the default - e.g., 'list:member:regular:footer'. What you need to do is copy /dev/null to files in (in your case) /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/ named list:member:digest:footer.txt and list:member:regular:footer.txt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 12/8/21 6:05 PM, Philippe B wrote: > Update: After disabling the footer on a few lists (as described here a week ago), we started seeing "Cache content lost" in most (but not all) messages from those lists. > > In some cases, that phrase is an attachment to the "real" body of the message. In others, it's the opposite (which is more problematic for responding). That seems to depend on whether the poster sent in plain text. The difference between inline and attachment has to do with how footers are added. They are only added inline if the message after content filtering is a simple text/plain message. > One puzzling aspect is that it doesn't happen consistently. One hourly automated message will have it; but exactly the same message one hour later won't have it; but will have it again 3 hours later for example. > > Is that a known problem, or would it be possible to troubleshoot? Thanks. The issue may be a bug or a race condition. What is going on is the 'empty' footer you created in Postorius is retrieved from Postorius by a URL. In order to reduce the number of http transfers to retrieve such templates, they are cached in the local file system. Now, when we want a template that is accessed via a non-mailman: URI, we call the cache managers get() method at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/cache.py… to get it. This should return either None if there's no cached file or the contents of the file, but if there is an entry but no corresponding file, it returns 'Cache content lost'. This could occur if some asynchronous process expunged the entry between getting the entry and getting the file. A process that could do that is the task runner that evicts expired cache entries. Look in your mailman.log. There will be `ACCEPT: <message_id>` entries for each accepted message and there will be hourly `Task runner evicted expired cache entries` entries. Do the ACCEPTs for the affected messages occur at the same time as the evictions? One way to avoid this is to not use Postorius to set the template but rather, create an empty `templates/lists/<list_id>/en/list:member:regular:footer.txt` in mailman's var/ directory for each such list and delete the Postorius templates. Of course, this is just a work around and not a solution to the issue. A proper fix is probably to implement a lock on the get(), evict(), evict_expired() and clear() methods so they can't execute concurrently. -- 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: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Odhiambo Washington

PS: I beg you to put your responses below the last one. Makes the hierarchy look better. Now, have you edited your /etc/mailman3/mailman-hyperkitty.cfg and restarted MM3? On Tue, Jul 29, 2025 at 3:18 PM Willie Castillo < Willie.Castillo(a)caemilusa.com> wrote: > Odhiambo, long time no hear from you. Hope you are doing well. > > The last archived post for that specific list is July 3rd. 2025. We do not > see the one for July 25th. Also, I just noticed something else in the logs, > apparently the server is still having "SSLCertVerificationError" issues > even after updating the DigiCert, CA-Certificate,etc. I must be missing > something else. > > Based on that, looks like the archiving is failing still due to the > "SSLCertVerificationError". > > The spool directory now has 8 *.pck files in it. However, I do not see the > original ones from 7/25 > > ~# ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 14725 Jul 29 08:07 > 1753790859.2498085+320096cb9852779b55a4cbb1e4f9603736ebd78d.pck > -rw-rw---- 1 mailman mailman 15122 Jul 29 08:07 > 1753790859.2437658+7fddf881d592f27be60e32aa5b3c34c7077b9988.pck > -rw-rw---- 1 mailman mailman 6399 Jul 29 08:07 > 1753790859.2370558+ee410eb31691bf2854cca46c64e80e3bf61c3523.pck > -rw-rw---- 1 mailman mailman 26619 Jul 29 08:07 > 1753790859.230345+b2e70f5b65900731895bbee5a3d83401f1500567.pck > -rw-rw---- 1 mailman mailman 15676 Jul 29 08:07 > 1753790859.2225533+82371c8a0202d62eaa046dd3633a23d6837d7a80.pck > -rw-rw---- 1 mailman mailman 98273 Jul 29 08:07 > 1753790859.2136636+8ee9273fbbaf4352d482e69d177e2eb2824078a5.pck > -rw-rw---- 1 mailman mailman 98109 Jul 29 08:07 > 1753790859.2026713+49d82ecd57eda7eaa582ba925449e2343bea5c56.pck > -rw-rw---- 1 mailman mailman 88479 Jul 29 08:07 > 1753790859.191489+162aa89dcac50ca6f5463ce1098c828728af12d1.pck > > > > > ------------------------------ > *From:* Odhiambo Washington <odhiambo(a)gmail.com> > *Sent:* Tuesday, July 29, 2025 7:59 AM > *To:* mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>; Mark > Sapiro <mark(a)msapiro.net> > *Cc:* Willie Castillo <Willie.Castillo(a)caemilusa.com> > *Subject:* Re: [MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails > - Hyperkitty - CERT Issue > > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > > > On Tue, Jul 29, 2025 at 2:25 PM Willie Castillo < > Willie.Castillo(a)caemilusa.com> wrote: > > The issue started right after the site's CERT expired. The CERT expired on > 7/8/25. This is what's in the log... > > Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: > HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with > url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by > SSLError(SSLCertVerificatio > nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: > certificate has expired (_ssl.c:1000)'))) > > The CERT has been updated but the 7/25 message is not archived still. > > > While at it, also edit your /etc/mailman3/mailman-hyperkitty.cfg to what > is documented so that the issue doesn't recur: > ``` > [general] > base_url: http://127.0.0.1:8000/archives/ > <https://urldefense.us/v3/__http://127.0.0.1:8000/archives/__;!!E8b8mVbrrfWV…> > api_key: Secret_Hyperkitty_API_Key > ``` > > PS: I haven't seen your responses to @Mark Sapiro <mark(a)msapiro.net>'s > questions quoted below: > ``` > Did the new post get archived? If so, why is last post at still July 25, > 2025? If no, why not. The post must go to the archiver to cause the > queue to be processed. > > If the post was archived and the July 25 messages are still queued, > what's in Mailman's mailman.log. There should be error messages and > tracebacks indicating the issue. > ``` > > -- > 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 > <https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht…> > ] > -- 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]

9 months

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

by Quanah Gibson-Mount

--On Tuesday, March 15, 2022 10:29 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/22 11:16, Quanah Gibson-Mount wrote: >> Hello, >> >> We have a constant issue with confirmation emails for subscribers >> getting lost and then the subscriber contacting us because their posts >> to the list never show up. Is there a way I can, as an administrator, >> do the confirmation on their behalf or in some other way promote them to >> being a member from non-member? > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/MJOOH23W6EKZO7GI5HRDKB4S733JEEVG/ > > If they don't have an outstanding subscription waiting user confirmation, > you can just mass subscribe them. > > If they do and your Postorius and Mailman core is reasonably up to date, > you can find the pending request at Subscription requests -> Pending > Confirmation, delete it and then mass subscribe them. Hi Mark, Thanks for the response. Unfortunately I'm currently stuck with the junk shipped by Debian. Yet another reason to move to a standalone install and avoid their broken packages. Regards, Quanah

4 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Nice! Up and running! How do I start using mailman? what are the steps?? REALLY thank you all for your patience and help! Really appreciated ! El vie., 21 jul. 2017 a las 18:48, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 04:43 PM, Rafael Mora wrote: > > YEEEES! At last!!! I can see the web UI. > > > > Now I´m getting this message in the web UI: > > > > Something went wrong > > Mailman REST API not available. Please start Mailman core. > > > > > > > > Where do I configure the REST API ????? > > > So I guess you figured out that ALLOWED_HOSTS is a Django setting in > settings.py or wherever your Django settings are. > > Now you have to start Mailman Core. In your Python 3 'env' where you > installed Mailman Core, run 'bin/mailman start'. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/23/21 9:18 AM, Mark Sapiro wrote: > However, that's not the issue. You originally reported and I didn't look > closely enough: > >> Update: The above worked fine until MM3 informed a list owner of >> pending subscription requests, with a URL like this: >> >> https://lists.example.com/mailman/admindb/listname >> >> and that URL returned a 404 error. > > > That URL is from a Mailman 2.1 installation. Are you still running > Mailman 2.1? I'm not, but that, and me not looking closely, was the problem. The system doesn't run MM2.1 any more, and no longer has it installed. But I failed to notice the dates on those 'admindb' messages: They were from the day of the upgrade, about 30 minutes before decommissioning MM2.1. And the docs do say explicitly to deal with any pending tasks before doing a cutover. The task-pending message that MM3 sends to list owners and moderators just says generically to check the dashboard, without providing a URL. Can that be modified to provide an explicit URL, something like this? https://lists.example.com/mailman3/lists/listname Thanks again for spotting this. dn

4 years, 4 months

[MM3-users] Re: Can't Start Mailman3 Core on Fresh Install

by Mark Sapiro

On 7/21/22 10:09, Jonathan Green wrote: > I've triple checked the password in mailman.cfg and used the same > username/password directly in MySQL and was able to get to the mailman3 > database. I did run a test script in python3 using the PyMySQL connector > and got the same error. Is there some permissions issue I need to look for? > I ran the install as user root - perhaps the user running the python script > doesn't have access somehow? First, your primary support resource for the Debian/Ubuntu packages should be Debian. That said, the database access credentials are also configured in the DATABASES setting in your Django settings, although your OP indicates this error is in core. I'm not sure what running the install as `root` will do in the Debian/Ubuntu package, but with that package, the user that needs to access things is `list` and all the Mailman processes should run as `list`. Did your test script do pymysql.connect(user='list', ...)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Mark Sapiro

On 05/29/2017 02:16 PM, Simon Liebold via Mailman-users wrote: > > Now, I get to see the confirmation view and upon confirming I see these > (luckily different) errors like below (same with Django 1.10): > > Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > > True, this table doesn't exist in the database. It isn't created by > python manage.py migrate. > > The error is served with HTTP-200. No stack trace in mailmansuite.log. Do you have django_q in INSTALLED_APPLICATIONS in your Django config and do you have # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } in your Django config and are you running django-admin qcluster at startup? See <https://mail.python.org/pipermail/mailman-developers/2017-May/026064.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] Re: Moderating posts via email

by Abhilash Raj

On Thu, Oct 26, 2017, at 03:01 PM, Dmitry Makovey wrote: > On 10/26/2017 02:59 PM, Abhilash Raj wrote: > > Given how emails are not so good at being secret, I'd not advise using > > it despite it's current state. Although, if it is a feature, it should > > work regardless! > > agreed. but how do I strip that from the message sent to user since > instructions are hardcoded into chains/hold.py ? I am not sure of any easy way to do without patching the source itself. You can however modify the 'list:admin:action:post' template for the list with instructions to advise against using the "Approved" feature (regarless of what the text below/above says). I understand that it probably is going to confuse a lot of people, but I am just throwing out ideas to add a band-aid for the bug. Again, I am not sure this feature if broken, I haven't tested it. It might be worth opening issue in Core though. > > > -- > Sr System and DevOps Engineer SoM IRT > > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

8 years, 6 months

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

On 10/26/21 8:18 AM, Seth Seeger wrote: > > I have just upgraded to 3.3.4 from 3.3.2 (via docker). > > Do we need to do anything more than reset the delivery status? I am getting (seemingly) continual emails about bounces. I keep running the recipe in the link which resets everyone's delivery status. I've grep'd one member's address out of bounce.log (see below my signature). > > Is it just catching up on old bounces? There is no significant change in bounce processing from 3.3.2 to 3.3.4 If you really upgraded from 3.3.2, I don't know what would be responsible. On the other hand, it looks like you may in fact have upgraded from Mailman < 3.3.1 in which case, those are old, previously unprocessed bounces, and your log certainly looks like that. If you think some or all users shouldn't have had delivery disabled, you can run the mailman shell seccion in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… to re-enable them and let current bounce processing handle the truly undeliverable ones. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Debian bug report

by Paul Tomblin

On Tue, Mar 3, 2026, at 4:42 PM, Thomas Ward wrote: > I would like to make a note. Firstly, the Debian bug reports *do not* always trickle upstream as they are not necessarily Mailman-upstream bugs or issues. Additionally, the Debian packaging is *NOT* done by Mailman's team necessarily, either, which introduces the "You need to deal with this in $DISTRO specifically, not with us" issue. > Yeah, i know, it's a packaging error, which is why I reported it to Debian, not to Mailman. > ... if we read the Installation Instructions on the Mailman Suite documentation [1], we see that the "Recommended for Production" suggestion is to use the `pip` / `virtualenv` installation method. > If you've got a fresh Debian install, and you see Debian packages for Mailman, that's what you're going to try first. Especially after having Mailman 2 installed from Debian packages from Debian 6 to Debian 11. It's only after encountering numerous problems that I uninstalled them and went to look at Mailman's documentation and do it the Mailman way. It was a lot easier that way - for one thing the documentation is more up to date and complete. -- Paul Tomblin

1 month, 3 weeks

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

by Mark Sapiro

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

3 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This my settings.py email config: #DEFAULT_FROM_EMAIL = 'postorius(a)localhost.local' # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root(a)localhost.local' # Change this when you have a real email backend # EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = '' EMAIL_HOST_PASSWORD = '' EMAIL_USE_TLS = False DEFAULT_FROM_EMAIL = 'Mailing <mailing(a)labbrands.com>' El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 8 months

[MM3-users] Re: Mailman not able to process "big" requests

by Mark Sapiro

On 04/24/2018 12:36 AM, Abhilash Raj wrote: > On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: >> We also have a problem with sending out emails to "large" (>50) groups, >> as they seem to not getting sent out at all. Do you have any idea what >> the problem here could be? > > Which MTA are you using? What do you see in mailman's logs and MTA's logs? > > I haven't seen this kind of problem before with Mailman 3. This very list is hosted using Mailman 3 and I believe has more than 50 subscribers. Nor have I seen this issue. This list currently has 158 non-digest members. There are several @python.org Mailman 3 lists with over 100 non-digest members including the active yt-users(a)python.org list with 301 members, and I have gotten no reports of an issue like this. Also, there are over 600 lists at <https://lists.fedoraproject.org/>, and I don't think this is an issue there either. -- 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] Re: Mailman - delete or backup old archived messages

by Mark Sapiro

On 6/17/21 1:00 AM, olenkoigetublim(a)gmail.com wrote: > > I have been using Mailman-Suite (Hyperkitty + Postorius) quite a long time now and now i was wondering if there is any way to erase or export old archived messages and back them up elsewhere (for example messages, that are older then 1 year). Didnt find any suitable option under "python3 manage.py" command and also didnt find any up to date post which related to mailman3 and python3. There isn't currently anything to do this but is shouldn't be difficult to create a script. You'd need to import the Email class from hyperkitty.models.email, set CUTOFF to a datetime.datetime instance with the cutoff date instantiate a mbox to receive the deleted messages and then do something like for email in Email.objects.filter(date<CUTOFF): msg = email.as_message() mbox.add(msg) email.delete() A lot of required housekeeping such as importing django and calling django.setup(), exception handling and reporting would need to be added to the above, but the basic loop should work. -- 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] at the finish line of mailman3 docker, but can't sign in.

by bob B

I am trying to setup mailman3 in docker and have some questions, I can see the finish line :) i hope. I start my images and I can access the web,http://Servername.domain.com/postorius/lists/ and no list are there of course, but How do i sign in? I click the forget link and I have to enter in a email address. I put in the email address I added to the docker-compose.yaml but that does not wrok. I have these setup in the .yaml file. MAILMAN_ADMIN_USER: The username for the admin user to be created by default. MAILMAN_ADMIN_EMAIL: The email for the admin user to be created by default. I found this url http://Servername.domain.com/admin/login However I never set a password and here is no forget button, Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. How can I make sure my containers can send and receive mail?

4 years, 9 months

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

by gordon＠dickens.com

I agree that this is a Debian packaging issue and I agree with Mark that the underlying issue is the "sed:" error message. I have only had one reply to my Debian bug report. That reply told me what I had to do make apt-get usable again (since it was stuck on the mailman3 error) but that post did not address the "sed:" bug itself and nobody else has responded to the bug report. So, it looks like I am on my own as far as my Debian mailman3 installation is concerned. So, here is what I plan to do: 1) apt-get remove mailman3 mailman3-web mailman3-full. This should not remove any configuration data or database files but I will run "apt-get --dry-run remove" first just to make sure. 2) Install mailman3 using the venv and web instructions as suggested in this thread. I plan to use mysql (mariadb) since my database was originally implemented with mysql. 3) I will poach as much of the configuration data as I can find from my original Debian mailman3 installation. Thanks to everyone for your support and replys! Gordon

4 years, 3 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Steve Brown

Mark Sapiro wrote: > The senders are defined as addresses in the headers listed in > the configuration setting sender_headers, default = from, from_ > meaning envelope sender, reply-to and sender. See > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> This was very useful in explaining why MM3 (3.3.9) accepted the problem post and attributed it to my address, even when seeing the bounce+ address as a different sender. Thank you for taking the time to reply. > Are you saying that the bounce+... address ends up as a nonmember of > the list you are sending to. I don't think that should happen. Yes, that is what is happening, but only for messages from the steve@stevebrown address. I can send a screenshot and a .txt of the headers (of the message after sent back to me from MM3 and long!) but didn't see a way to do that on the archive page. Do I need to post from my gmail address? One clue I hadn't spotted before was a bodyhash_mismatch warning in the headers. No idea where that came from. Doesn't appear in emails from me to other addresses. Steve

1 year, 7 months

[MM3-users] Using as a forum

by tokyoprogressive＠mailbox.org

Our group of 30 plus people have the perennial problem in MM II of not checking previous messages before replying. A second problem is starting a new topic rather than responding to a message in the same topic, which makes searching even harder. I previously suggested a forum or something like Stack or Flock. People had no interest in a Word Press forum yet moan about the inefficiency of a list, also it is something new and involves leaving email. Stack and Flock make it hard to require all to be a member of all topics in their free versions. Then it occurred to me, the threaded view in Mailman III looks good and could help us nudge people back on topic. Am I being too optimistic. It is a closed group only open to people we approve. I would like to migrate to MM III but lack the technical skills to fo this? Anyone who could do this for a fee? We probably do not need to bring in the old topics. (I guess there us no way like a forum to limit the topics but at least we could keep things on track). Thanks Paul Arenson Japan Association for Language Teaching Sent from my iPhone

7 years, 8 months

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

by Stephen J. Turnbull

Wikinaut writes: > 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" :-) One piece of generic Python advice: don't mix OS packages and pip (except for Python itself). Always use a venv if you need to use pip for packages that aren't in your OS distro. (Of course it's possible to do so in many cases if you *really* know what you're doing, but it's almost never worth the pain.) All of the site configuration data should be in /etc/mailman3 (except for a few template files in $var_dir/templates), and all of the domain, list configuration, and archive data is in the RDBMS (usually PostgreSQL or MySQL). The RDMBS should be backed up regularly according to its procedures, but that's completely out of scope for Mailman.[1] The RDBMS should "just work" with exactly the same Mailman-side configuration as Debian.[2] As I think Odhiambo mentioned, the Mailman side of the site configuration also does not change (for example, the RDBMS URL and authentication). What you do want to change is the file system configuration. Except for /etc/mailman3, it should be completely different -- as with pip'ing packages, you don't want to share files across a local venv and the OS version of the same package. It just leads to pain. I think among the developers the preferred root = /opt/mailman (or /opt/mailman3) for Mailman's directory hierarchy. This will be populated with subdirectories when you run `mailman info` (or start Mailman) the first time. The directories relevant to configuration are all under $root/var, and you inform Mailman about this by setting `var_dir` in mailman.cfg. If there are other file and directory configurations in mailman.cfg, they need to changed from the Debian values (probably /var/lib/mailman3/...). You may do fine by simply deleting all other directory configurations and let Mailman decide where to put them relative to the `var_dir`, You will need to fix the setting for STATIC_ROOT (I think that's the name, if not search for "static") in settings.py, and maybe in mailman-web.cfg. While it's not necessary (and may be a little inconvenient), I recommend changing the root for Mailman's log files from the Debian value (probably /var/log/mailman3) to the Mailman default of $root/var/logs, and similarly for the Django logs in settings.py. Non-Mailman settings I think you will need to change the settings for your MTA (usually Postfix or Exim4) so that it will recognize Mailman lists and route them to Mailman correctly. There will probably be mailman-related files in /etc/$MTA/conf.d (or something like that). You can edit them directly, but I recommend changing the name (paranoia so that dpkg doesn't overwrite them). The only thing I can think of for the webserver (Apache?) is the location of the static directory. I think Debian uses uwsgi by default so you may need to adjust its configuration too. I think you need to fix logrotate's configuration in /etc/logrotate.d. Not sure how many mailman-related config files are in there. I think you mentioned systemd .service files. If so that doesn't make sense to me -- Debian should provide those. You need to make sure those are disabled or deleted so that Debian Mailman services don't start on reboot. This is automatic if you delete the Debian packages, of course, but not for any files you created yourself. Probably the Debian .service files will work, but you need to make sure they refer to the venv Mailman (using the full path to the `mailman` utility in the venv's bin directory will work, and similarly for `mailman-web`). systemd does not configure the /opt hierarchy in it search path by default. I put the mailman, qcluster, and gunicorn (if you use that instead of uwsgi) .service files in /usr/local/lib/systemd/system, and that works for me. Flotsam and jetsam If you have run Mailman with any success at all, you may find some stuff in Debian's $var_dir/queue/* directories or in its $var_dir/lists/* directories. The queue/* directories contain incoming messages at various stages of processing, and the lists/* directories contain files containing multiple messages that are scheduled to be sent out as digests. You can read the queue files with `mailman qfile /path/to/queue/file.pck`, and the digests are just text files. That way you can check if there's anything important in them. If not, you can just delete them. If there is, you can just copy them to the same place in the venv $var_dir as they were in Debian's $var_dir, but you may want to ask here first before doing that. It's best to let Mailman run until all the queues are cleared (except maybe bad and shunt, but if those have any files in them you need to intervene anyway). Afterword I'm sure this sounds complicated, but in fact it's a pretty short list. When you get there we'll help you. Footnotes: [1] But not for this list. You may as well ask here, somebody probably will tell you the basics quickly. But for troubleshooting, go the the RDBMS's own channels. [2] In fact, it is possible to keep the Debian installation, copy the the mailman.cfg somewhere, edit it, stop Debian Mailman, and start up the venv Mailman. I don't recommend this -- the point is that the venv and the databases are that isolated from the rest of the system.

2 years, 6 months

[MM3-users] Basic settings for a discussion list

by paul＠arenson.org

Over the last 20 hours I have been trying to figure out setup for list members to sign up. One person has kindly helped out, though I am still unsure of the difference between the several signups. That thread is here and I welcome more advice. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… But it occurs to me that my problem is that I have not actually configured my list. So this thread is for help on that. I have found a guide for general users here: http://docs.mailman3.org/en/latest/userguide.html But I have only found a highly technical guide for administrators here: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… It is written for coders and I am looking for a guide similar to the one for users. It seems not to exist yet. WHAT I WANT Discussion only list. Ideally anyone who signs up via the various ways should be able to get the archives and post via email and the interface if they want. The list should be closed to others. In the absence of any guide, all I can do is cross check with you guys and hope I am on the right track. I am non technical, although I managed a Mailman 2 list without difficulty. 1) FIRST ANOMALY Under https://list.tokyoprogressive.org/postorius/accounts/subscriptions/ I see myself twice: List Name Subscription Address Delivery Mode Role discuss.list.tokyoprogressive.org paul(a)tokyoprogressive.org None member discuss.list.tokyoprogressive.org paul(a)tokyoprogressive.org regular owner Is this correct? I added My name in one field somewhere and this is the result. I even got a welcome message. I think it is because I subscribed to my own list.If this was not necessary, what should I do? Global based preferences are listed. Address and email based ones are not showing either enabled or disabled. 2) MANAGE LISTS For myself I have done the following in my MAILING LIST SETTINGS Subscribe to this list My email and name (Maybe that is why i am listed twice) Now I see 3) Users For now only me- I am listed as member and owner. There will be no other moderators or owners I have no idea what a non member is (if they register aren't they a member?) 4) Templates This is showing nothing at this point. Before it was. I am not sure what i did to stop it from showing. Perhaps because I made it a private list? 5) Settings a) List identity I have it set for NOT SHOWING on the Index page because I will link to it from my news magazine website as a way to comment on articles. Is this ok? Other data will be filled in later. I think I am confusing this with private list. I also will have no other list. b) AUTO RESPOND LIST OWNER-- I added a short note thanking people. Respond and Continue Processing c) AUTO RESPOND POSTER--Your message has been been received. If you are a member, it should be posted soon. Respond and Continue Processing d) AUTO RESPOND REQUESTS--No auto response OTHER THINGS DEFAULT e) URL WELCOME MESSAGE--NOT SURE. I want people to subscribe themselves but I also have 500 people from another list from DADA I will import. I want them automatically be able to post. Is it possible? If so, I hope to add them manually. DO I compose a text on my website and welcome them by adding the URL, or enter it in my list? f) NOTIFY OF MEMBERSHIP CHANGES--Yes g) ALTER MESSAGES ---I have left most things as they are. However, as this is a discussion list, I want replies ONLY to go to the list. I chose that. h) DMARC --I have left as is i) DIGEST--I have left as is 6) MASS OPERATIONS--I have left as is 7) BAN--left as is 8) MESSAGE ACCEPTANCE--I have left as is 9) HEADER FILTERS--left as is 10) ARCHIVES--Private Archives (Maybe this is why templates do not show???) 11) SUBSCRIPTION POLICY--MODERATE-- I intend to send them an email to confirm their reasons for subscribing to avoid spammers. LAST THING. My Gravity does not work. I edited it online as per instructions but it does not appear. That is all I can think of. Thanks in advance. paul

6 years, 7 months

[MM3-users] Re: Changing subscription address

by Allan Hansen

Hi Steve, My comments below: On 3/15/21, 21:28 , "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >I don't have the Postorius knowledge to do this in a reasonable amount >of time to help your user immediately, but how about this design: < >In the 'Mailman Settings' screen, List-based Preferences' tab, You may mean the 'Subscriptions' tab. >currently each list has an active link at the list's posting address >(which links to a page with the same options carefully documented), a >plain text display of the subscribed address, and a row of options. >Suppose we > >1. Add a popup menu of addresses and attach it to the > displayed address for each subscription, >2. Add a 'select subscription' checkbox to each subscription. >3. Add an 'act on all selected subscriptions' fake subscription, > whose checkbox has the effect of select or deselect all. I guess > this should be at the top.[1] > >Does that seem like what you have in mind? Any other needs you want >to mention? (Suggestions for feature design are welcome, but "I do >this often and there's got to be a better way" is good too.) The above will work fine, Steve, as it will cover the special needs of people who have several addresses that they use for different lists. It's very flexible. For the other 99% of my users, something much simpler is needed: Under 'User profile for <name>', under the 'E-mail Addresses', add button to ensure that 'Primary E-mail' is used for all lists. Then they can 'Create account' if needed. 'Add E-mail'. 'Make Primary' the new e-mail. 'Use Primary For All Lists'. 'Remove' the old e-mail. This requires them to set up an account, but I'm OK with asking them to do that. And, indeed, new subscriptions should default to 'Use Primary.' That would be fine, but it can be even simpler, which I would much prefer: Instead of the 'Use Primary For All Lists', may I suggest a tool that lets me set all subscriptions to 'Use Primarry' where there either is no account or where the primary e-mail is already chosen as the subscription address (which together form the 99% I mentioned). In that case, the procedure becomes much easier for me to explain to them, and no new functionality needs to be added (although what you suggested is fine). 'Create account' If needed. 'Add E-mail'. 'Make Primary'. "Remove' old email. Is that possible now? Does a member have to have an account for me to set it up thus for them? Thank you for considering this, Steven. Yours, Allan

5 years, 1 month

[MM3-users] Re: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

Rob's reply in this thread was garbled due to <https://gitlab.com/mailman/mailman/issues/616>. The text of the reply is quoted below. On 7/27/19 12:54 AM, Rob Lister wrote: > > One thing that does occur to me is that my exim header fudge will > probably cause the Message-ID header to move around from its original > position, and if someone is doing hashing or actually validating (gpg > signing?) the headers haven't been tampered with, then it might > complain, since although the message-id hasn't changed, it might be in a > different place in the headers. > > Then again, mailman can make plenty of other modifications and additions > to the headers anyway, so I'm not sure it matters. > > Probably the more correct way to do it is only add a new header if it's > missing, and if it's there, leave it alone. > > This is probably possible in exim with some more variables and a lot of > nested curly braces... -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Change delivery_status in bulk

by Hitashi mancho

Thanks, Mark, for the reply. The mailman shell interaction worked for me. Thanks again for your help. On Fri, Apr 4, 2025 at 8:25 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/3/25 19:36, Hitashi mancho via Mailman-users wrote: > > > > Now, I am unable to locate any command or an API call through which I can > > change the delivery_status back to enabled for 1000+ users. > > > > Can you please guide me on how I can do this programmatically using cli > (I > > will write a bash script) or using an API call? > > > See the post at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for a mailman shell interaction to do this. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > 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 huhamails(a)gmail.com >

1 year

[MM3-users] Re: how to administrate mailman3 in CLI ?

by testeur

Hi, I try to find documentation and examples to manage mailman3 with "mailman shell". By example, when i tryied just to define global configuration for all users, like in this example ( https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ), but it changes nothing : |# mailman shell -l testlist(a)domain.tld | ||>>> from mailman.interfaces.action import Action >>> for mbr in m.members.members: mbr.moderation_action = Action.defer |||commit()| |||>>> from mailman.interfaces.action import Action |||||||>>> english = getUtility(ILanguageManager).get('en')| >>> for mbr in m.members.members: || 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|commit()|| Before the shell command, the web interface was with an other language (i tested with italian one) and other options preferences, but after the shell command, after a web interface refresh, it doesn't change. am i wrong somewhere ? Regards, On 16/09/2023 23:05, Stephen J. Turnbull wrote: > Hi > > testeur via Mailman-users writes: > > > I have installed mailman3 and i want to administrate it with rest > > api, > > Do you really mean REST API, or do you mean CLI? > > > i tryied with curl to manage it, i can see if there is a pending > > message with : > > > > curl --user restadmin:restpass > >http://localhost:8001/3.1/lists/ml@domain.tld/held/count|| python3 -m > > json.tool| > > This is a lot easier using "mailman shell" if you want to use CLI, or > a Python program using mailmanclient if you really want to use the > REST API for some reason. > > This is explained here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… > but it's likely to be pretty rough going for you because it's really > oriented to programmers studying to be Mailman developers, not for > admins. > > > but how to delete all held messages ? is it possible in one time ? > > No, you need to fetch the list and then loop over the messages. > > > And how to select a specific message to discard /accept / defer ? > > > > do i have to use a POST ? > > This is all explained here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > Steve > > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-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/mess… > > This message sent totesteur(a)starinux.org

2 years, 7 months

[MM3-users] Re: # comment allowed in a template file?

by Mark Sapiro

On 7/24/20 3:19 AM, skenny(a)scss.tcd.ie wrote: > > I'm running Mailman 3 in maxking's Docker container. I'm also using Puppet to do as much configuration as possible, so I'd like to add a comment to the file that reads something like: > # This file is managed by Puppet. > > Is it ok to do this? I may not have searched the docs enough, but I couldn't find anything relating to comments. If you mean can you add a '#' line that won't be part of the actual rendered template, the answer is No. > One other observation in case it's any use: Initially, I created the template files with owner set to "root". This resulted in postings to lists getting stuck in mailman-core. It's vital that these files are owned by user "mailman". Once I changed the owner of the file to the latter, everything worked. I don't think they need to be owned by 'mailman' as long as they are readable by 'mailman' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Virtual alias + shell

by Mark Sapiro

On 5/26/23 4:36 AM, alopez(a)ac.upc.edu wrote: > Hello, > I want to have a mailman configured together with virtual alias. To do that I need to use alias_domain. > I have tried to do it with mailman shell. The domain seams to be created but when I leave the shell and enter again, the domain is not longer there. Because you are leaving mailman shell with exit() which doesn't commit changes. You deed to either explicitly commit with `commit()` or exit with control-D. Recent mailman shell will report in its banner Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. > On the other hand, If I create a domain in administrator interface, it is not listed in the shell. If I create in the web interface, which field correspond to the alias_domain : Domain Name, Display Name , Mail domain? Your Postorius is too old to support alias_domain, and your Mailman core may be too - requires core >= 3.2.0. -- 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: Extracting mailing list users

by Eggert Ehmke

Am Montag, 2. Januar 2023, 02:40:58 CET schrieb Mark Sapiro: > Understood, but there are a couple of things at work here. One is that > this particular task is a one-off the correct the result of a bug, but > perhaps more significantly, mailman developers (at least me) are > comfortable with `withlist` (it's been around since MM 2.1) and if I can > do it that way, it reduces the motivation to make something more > friendly for the normal admin. Unfortunately doing things easily that > way requires a lot of specialized knowledge of Mailman internals, so > most admins need help with it. Mark, I completely understand your situation as a core developer with limited time and lots of requests from all directions. Being a Python programmer myself, I would be happy with a consistent documentation of the relevant Python classes to be able to develop own applications. The isolated code snippets in the mm3 documentation are not too helpful. Such a documentation would possibly remove some of the workload you feel by constantly answering admin questions.´ When you look at the documentation of the Qt library you know what I mean. Thank you again for this great project! Cheers, Eggert

3 years, 3 months

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

by Guillermo Hernandez (Oldno7)

On 5/1/22 21:50, Mark Sapiro wrote: First, thanks a lot Mark for your guidance. >> >> HINT: Configure the DEFAULT_AUTO_FIELD setting or the >> SocialAccountConfig.default_auto_field attribute to point to a >> subclass of AutoField, e.g. 'django.db.models.BigAutoField'. > > This is from Django >=3.2 can be fixed by adding > > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > > to your settings. This has been done in HyperKitty's > example_project/settings.py for the not yet released 1.3.6 version. > > These warnings are only warnings, they aren't fatal. I thought so. I've added it in the settings.py file. In the last part of your suggestions you wrote: "I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0" But this is exactly what made me fall in this mess: I realized that the versions of hiperkitty and mailman-hiperkitty in that server were outdated.. and I tried update them separately, forgetting the saying "if it works, don't touch it" (si funciona, no lo toques). In my first message I listed the versions of all the items, but to refresh it, as they are now: (from pip list) ... gunicorn 20.1.0 HyperKitty 1.3.5 ... mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 ... mistune 2.0.1 ... mod-wsgi 4.7.1 ... postorius 1.3.6 (end of pip list) I did the upgrade of all of it. The "migration" process output the same warning as before about to doing a "makemigration" (I did not this time) Thinking that the problem in the "migrate" and "makemigration" process could be that I touched the mistune/scanner.py to add escape and escape_html imports, I deleted that two lines. Then all went bad: the postorius list page didn't show anymore. The error.log form the apache server shows django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' from 'mistune.scanner' (/usr/local/lib/python3.7/site-packages/mistune/scanner.py) So I tried to put them back (but I had problems with, I believe, the __pychache__). I had to reinstall mistune and write back this lines that I found in a previous thread from William Oliver last 12/28/21 I've finally came back to administering the lists via postorius. I created a new list to do the tests without disturbing the rest. And now I am at the exact same point: No message is archived and the log shows: ERROR 2022-01-06 12:38:45,574 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,586 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,801 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,832 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,847 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,867 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:46,075 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. As this server has very low traffic, the emails are distributing well, and the only thing that fails is the archiving of new messages, I will wait until a more complete upgrading process is needed for mailman, postorius or hiperkitty. Thanks, again, for your support. P.S.: One thing that make me curious is the "mistune" package... I don't see it installed in the other servers that are working flawlessly with mailman3. > > ... >> Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows >> the same warning listed before and some new errors: >> >> *-*-*-*-*-*-* >> >> Migrations for 'postorius': >> /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py >> >> - Alter field name on emailtemplate >> Traceback (most recent call last): >> File "manage.py", line 10, in <module> >> execute_from_command_line(sys.argv) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", >> line 419, in execute_from_command_line >> utility.execute() >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", >> line 413, in execute >> self.fetch_command(subcommand).run_from_argv(self.argv) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 354, in run_from_argv >> self.execute(*args, **cmd_options) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 398, in execute >> output = self.handle(*args, **options) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 89, in wrapped >> res = handle_func(*args, **kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", >> line 190, in handle >> self.write_migration_files(changes) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", >> line 228, in write_migration_files >> with open(writer.path, "w", encoding='utf-8') as fh: >> PermissionError: [Errno 13] Permission denied: >> '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' >> >> >> *-*-*-*-*-*-* >> >> The file >> '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' >> does not exist at all > > > makemigrations is trying to create that migration and you don't have > permission to create the file. I don't know why it's trying to do > that. Postorius 1.3.6 has migrations through > 0016_auto_20210810_2157.py and shouldn't need more. To you have > modificationd to Postorius? > > >> Despite the error, I did a 'su -m mailman3 -c "python3 manage.py >> compress"' and the subsequent "django-admin compilemessages" in >> >> /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and >> ../django_mailman3 >> >> And the log continues showing the same error when trying archive a >> new message. >> >> ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > > > These messages come from some HyperKitty version between commit > b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 > -0700 and > commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 > 2021 +0000 > > They do not come from HyperKitty 1.3.5 but from something later than > 1.3.4 which makes be think your mailman-hyperkitty version is not > 1.2.0 either. > > I suggest you do > > pip install --upgrade hyperkitty mailman-hyperkitty > > and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 > > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

4 years, 3 months

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

by Mark Sapiro

On 2/23/21 9:40 PM, Morris Jones wrote: > I typo'd some full names in a mailing list. I want to correct them ... > > I can't see a way to do that in the Member Options, so I thought I'd try > "remove" and re-add, either from the command line or the UI. > > But the name gets readded with the typo intact. :( > > Is there a way to fix it without writing SQL? You can do it with mailman shell. The basic issue is the display name is a property of the user or the user's address, which ever is subscribed to the list. When you add a previously unknown user to a list, Mailman creates these user and address records, but they belong to the user, not the list. There are some threads around this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and a somewhat protracted one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

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

by Gerald Vogt

Hi, On 04.11.24 02:06, Mark Sapiro wrote: > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > We should probably cover this in the docs, but for /etc/mailman3, you > should do > ``` > sudo mkdir /etc/mailman3 > sudo chown mailman:mailman /etc/mailman3 > sudo chmod 755 /etc/mailman3 > ``` > Then you can create all the subordinate files as the mailman user. For > other things like the systemd service and the postfix and web server > configs, you need to do them as root (via sudo). is it really necessary that the mailman user can write that directory? For most services, directories and files in /etc/ may be readable for the service but usually not writable as you don't want the service itself change it's core configuration. 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. Regards, Gerald

1 year, 5 months

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

by Mark Sapiro

On 12/6/21 2:51 AM, Stefan Bauer wrote: > Need to bring this up again. Django now sends with STARTTLS, but mailman > itself, does still only drop mails in cleartext. > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] > ehlo=1 mail=2 rcpt=2 data=2 commands=7 > > No starttls=1 at all :( > > Does the above settings work for anyone? > > etc/mailman3/mailman.cfg > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: > smtp_verify_hostname: false > smtp_verify_cert: false > smtp_secure_mode: starttls This should work. What do you see in Mailman's smtp.log if you add ``` [logging.smtp] level: debug ``` to mailman.cfg. However, do you really need this. It will only affect delivery from Mailman to Postfix via the loopback interface on the localhost. -- 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] moving lists to another server

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > I have both my mailman lists and django config in postgres > databases. These are Mailman 3 lists? What Django config? Do you mean Postorius and HyperKitty? Do you intend to use Postorius and HyperKitty on the new server? > If I want to move my lists to another server that is running > mailman 3, aside from copying the databases to the other server, Do you mean the other server is already actively distributing Mailman list traffic, managing users and archives? Or is it fresh instance? > what other things (perhaps all files under /var/lib/mailman3?, etc) > would I need to bring over to the other server? That's going to vary depending on the way your existing server is set up. A Mailman 3 instance is a complex system of cooperating applications. Assuming you have not patched or added any Python code, typical configuration and customizations include 1. Your webserver (Apache, nginx are most common) needs configuration to handle WSGI applications and may need modules enabled or installed for the WSGI server. This is usually installed as an OS distro package, and the configurations will live in /etc/apache2 or similar for another webserver. Depending on other content served by the two hosts you may have to edit the configuration on the new host rather than copy it from the old one. 2. The WSGI server is typically a separate application, although there is an Apache module for this. Gunicorn is a Python application usually installed via pip. I like to keep its Django configuration, which I call gunicorn.conf.py, in /etc/mailman3. (Mailman core also uses gunicorn, but that is transparent to you, it should not need custom configuration.) uwsgi is a C or C++ application normally supplied as a distro package. Don't know where it keeps its config files but since it's a distro package my first guess is /etc/uwsgi. 3. Your MTA, usually Postfix or Exim4, maybe Sendmail or qmail needs to be configured to route mail to Mailman, and apply any milters, signatures, and perhaps anti-yahoo configurations such as ARC. 4. Your database server, usually PostgreSQL or MySQL. 5. Mailman core has a single configuration file mailman.cfg, which I keep in /etc/mailman3. It also has a crontab, which in Debian- derived systems typically lives in the file /etc/cron.d/mailman3. Note that this could be implmented as a systemd timer, but I don't know if any distros do that. 6. Django, Postorius, and HyperKitty together constitute the mailman-web subsystem. I strongly recommend you use the mailmanweb Python package to manage Django and its applications. In any case I am not familiar with other organizations of those packages, so I'm going to assume it. If you are not using mailmanweb, you will need to be careful because most subpackages in the Django subsystem name their configuration files settings.py, urls.py, and views.py just like top-level, and distinguish them by using Python's attribute notation (eg, postorius.urls). a. Django application configuration for Postorius and HyperKitty goes in settings.py, which I put in /etc/mailman3. b. Django site configuration for Postorius and HyperKitty goes in urls.py (the routing configuration mapping URLs to views) and views.py (mapping views to Python code). I put these in /etc/mailmn3. c. Full-text indexing for HyperKitty. Default is Whoosh (a Python application) whose configuration goes in Django's settings.py. I prefer Xapian, which requires a separate application (Debian and Ubuntu have packages), but the needed configuration can be done in the top-level settings.py. 7. Template customization. If you have any customized templates for Mailman's email or Django's views, you'll need to copy and move them too. I haven't customized email, but Django's page templates can be kept separately with a path variable set in settings.py. I put them in a hierarchy under /etc/mailman3/templates. Maybe Mailman core has a similar setting? 8. Transient files. Aside from code and configuration, everything in Django is in the RDBMS, there are be no random files strewn around as far as I know. Mailman core is another matter. You can hope that all Mailman transient files are in its "var" hierarchy. $var_dir (the setting in mailman.cfg or inherited from schema.cfg) is the root of this hierarchy. I set var_dir=/opt/mailman/var, I think Mark may use var_dir=/opt/mailman/mm/var. I would guess that FHS-conformant distros would likely use var_dir=/var/lib/mailman3. a. The queue directories $var_dir/queue/* should be empty. Shut down the incoming mail and let mailman run until it's clear. (Normally takes < 5 seconds.) The exceptions are the shunt and bad queues, which are messages that Mailman doesn't know what to do with. With the venv active, run "mailman unshunt" to attempt to clear the shunt queue. Move anything that's left in shunt as well as any .bak or .tmp files into the bad queue for later treatment. These can be copied to the bad queue in the new instance. Use "mailman qfile <file>" to examine them to see if they can be deleted. b. I think the only stuff that ends up in the $var_dir/lists/* directories are digests being built for later distribution. Use the usual tools to send them off or copy them over to the new instance. c. There should be nothing in $var_dir/archives/hyperkitty/spool, which is temporary storage for messages to be archived. That is, it should get cleared up by the few seconds while incoming mail is stopped and outgoing messages are being processed. If there's anything still there, stash it away for later examination using "mailman qfile". (Don't put it in queue/bad or queue/archive though, this is a different process from the normal pipeline.) I think that's about it. Steve

2 years, 5 months

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/12/21 3:21 AM, Victoriano Giralt wrote: > > I just wanted to make visible that the .mo files were a "bit old". For > example, Guillermo, in this thread, pointed that the Spanish > translation was quite compelte. Actualy, I spent some hours bringing > them to 100% around Christmas. But, the .mo file for es from the pip > install --update i did recently is dated November 7th. I have > definitely added a lot of translated material from then until the end > of the year. Why do you say the .mo files are old. The timestamps are all Feb 3 02:47 which is when the package was built for PyPI. > I know the translation happens outside the development community. I > tried to point that there might be some synchronisation problem, so to > say, between the translation site and the packaging of the latest > mailman release. When things are changed on weblate, we get automatically generated merge requests to update our source. We don't always merge them immediately, but we certainly do merge all the outstanding ones before making a release. -- 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] Issues with international characters (replaced by ?) when mail is send as text/html

by Michal Soltys

Hi, I have noticed that any mail send with text/html, e.g. with following headers: Content-Language: en-US-large Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit is slightly transformed by mailman3 - the body is put into its own part, but all the international letters are replaced by question marks. Having searched the list I tried: 1) adding following to mailman.cfg: [language.master] description: English (USA) charset: utf-8 enabled: yes [language.en] description: English (USA) utf8 charset: utf-8 enabled: yes 2) changing preferred language of a mailing list to something else via shell, e.g.: m.preferred_language = 'pl' 3) changed default_language to 'pl' in mailman.cfg 4) Ensured all relevant glibc locales are generated (not sure if that matters though in this case) None of this seems to have any positive result - all mails, whether under 'pl' or 'en' setting still get all non-ascii chars replaced with question marks (in html case, probably(?) in any case where it becomes multipart). Any ideas what to do so html mails are passed without filtering out their characters ? Do I have to recreate all mailing lists under new [language.en/master] settings ?

4 years, 3 months

[MM3-users] Re: MM3 not processing some mails from specific user

by Stephen J. Turnbull

Stefan Bauer writes: > thank you. Funny. All problematic mails are in the shunt-queue from one > specific user. That's good news (given that things aren't working), something in there will show us why. > the mailman-logs did not log anything helpful. I thought they should ... not your problem, I'll check and let you know if there's someplace else you should look. > What do you recommend to find the needle in the haystack? I mean, what can > cause mailman to fail processing? Most frequently the issue is a non-ASCII character in the header. A frequent cause is spam filters and virus checkers quoting non-ASCII text in their reports in the header. Nonconforming dates can cause problems for some applications (specifically those that work with list archives), but I don't think they should cause non-delivery, and the date in the sample message is conformant. You could try running "mailman unshunt", which may produce a helpful error message if for some reason it can't do so. Also check for logs that were updated at that time, which might identify a log with some useful information. Steve

3 years, 8 months

[MM3-users] Re: MIME Digests with posts and index inline likewise Plain Text Digests

by Mark Sapiro

On 1/18/19 5:11 AM, Henrik Rasmussen wrote: > Please correct me if I'm wrong, but as I understand, Mailman attaches posts in a MIME Digest mail intead of inline in the digest mail itself, like Plain Text Digests does. Some mail readers like Gmail eventually displays attachments inline anyway, but readers like Outlook do not. Also the digest index seems to be posted as an attachment in MIME Digests. > > Would it be possible for Mailman to send both posts and index inline in the MIME digest? The format of the MIME digest is specified by RFC 2046 which defines the multipart/digest format in section 5.1.5. This defines the MIME digest as a multipart/digest message part containing the individual messages as message/rfc822 sub-parts. It also says (after spelling corrections - ErrataID: 510): Note: Though it is possible to specify a Content-Type value for a body part in a digest which is other than "message/rfc822", such as a "text/plain" part containing a description of the material in the digest, actually doing so is undesirable. The "multipart/digest" Content-Type is intended to be used to send collections of messages. If a "text/plain" part is needed, it should be included as a separate part of a "multipart/mixed" message. The MIME format digest Mailman produces has the structure multipart/mixed text/plain the "masthead" text/plain (only if a digest header) the digest header text/plain the table of contents multipart/digest message/rfc822 the first message message/rfc822 the next message ... message/rfc822 the last message text/plain (only if a digest footer) the digest footer The only change that could be made while keeping the digest compliant would be to combine the masthead, digest header if any and table of contents in a single text/plain part. While this might solve the the issue of the table of contents being an "attachment" in some MUA's rendering, it won't address the larger issue of the messages being rendered as attachments. As you note, Gmail's web mail does an OK job of rendering the MIME digest as do other mainstream MUAs such as Thunderbird. The real solution is for those people who insist on using non-compliant MUAs to subscribe to the plain format digest. The whole point here is if you want a digest which has everything in line, that's what the plain text digest is. If you want a digest which maintains the original structure of the messages without flattening them to plain text, the messages have to be separate message/rfc822 parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

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

by Mark Sapiro

On 1/29/21 3:52 PM, Jack Lenox via Mailman-users wrote: > > Good news everyone! I've got it working. It turns out my issue was with > the mynetwork IP settings in my Postfix config. Things do now appear to > be working. Good. Thanks for the update. > My only remaining issue is that the posts aren't appearing > in the archive. Hmm. If you want our help with that, tell us if you have any non-default [archiver.*] settings in mailman.cfg and what the list's Settings -> Archiving settings are. If you are expecting HyperKitty archiving, are messages remaining queued in Mailman's var/archives/hyperkitty/spool/ directory and if so, what kind of errors do you see in Django's log? Does the value for MAILMAN_ARCHIVER_KEY in your Django settings match the api_key in the [general] section of the mailman-hyperkitty.cfg (or whatever you call it), quoted in MAILMAN_ARCHIVER_KEY but not in api_key, and is the base_url setting in the [general] section of the mailman-hyperkitty.cfg a URL that can actually access hyperkitty? -- 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: Disabled by bounce

by Stephen J. Turnbull

Jan Eden via Mailman-users writes: > To distribute messages with valid DKIM signatures, I set > > remove_dkim_headers: yes > > in /etc/mailman3/mailman.cf That should be "mailman.cfg" for a standard installation, and it may not be in "/etc/mailman3" in a shared hosting situation. Do you have evidence that removing DKIM headers helps you get mail delivered? (Not adding your own, IMO you should do that regardless of whether you strip existing ones, but removing originals.) The DKIM spec says that you shouldn't, and that consumers should treat invalid signatures no differently from missing signatures. I haven't run into a "public" host that treats an invalid signature as a problem in quite a while. On the other hand, I know of at least one postmaster who is experimenting with simple "repairs" (namely, stripping list tags and serial numbers from Subject and unwrapping simple MIME structure for Mailman lists at least -- the case where Mailman wraps the original message in multipart/mixed and adds a text/plain part to the message with the footer in it) and checking the original DKIM signature and from alignment on the "repaired" message. I don't know if they're still working on that. Steve

3 years, 2 months

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

by Brian Carpenter

On 2/25/21 10:35 PM, Abhilash Raj wrote: > I think it is okay to be pick up a specific configuration and provide a > guide to installation keeping that as the target technology. As it happens > to be, the official doc uses the same set, Nginx, Postfix and PostgSQL. > > https://docs.mailman3.org/en/latest/install/virtualenv.html Thank you for pointing the above out. I will keep track of the URLs you provided in this thread and I am willing to also assist to try to make sure such links are propagated via search engine results. > I don't see anything very specific to Debian in the doc except the package > names and I think they are similar enough in Debian derivative distros that > we can write up that assumption up front in the top. > > Given that most of the installation is based off on pip, I don't think there is > going to be a *lot* of deviation for even RHEL/Fedora based distros when it > comes to Mailman itself. Some minute deviations could occur with the > behavior of certain commands, like `nano` doesn't exist, but I still expect > 95% of the doc to be the same, except obviously the package names. I agree. One of my goals was to make it easy for Mailman 3 adopters to use a different installation method other than a repo since distro packages tend to install older versions of Mailman 3 core, Postorius, and Hyperkitty. At this stage of Mailman 3 development, these new versions bring a LOT of improvements to the Mailman 3 user. I am also willing to start testing out my installation method on other distros and document the differences. If you are willing to help me, I have no problem posting installation instructions and tips to Mailman 3's official documentation. I am also more than willing to keep such documentation up to date. I am always being called upon to install Mailman 3 for someone, so I seem to be on the front-line when it comes to "surprises" such as the issue with the cryptography module. That puts me in a good position to update documentation simply because I need to know such things for the next install. > I am not that well versed in SEO, but the official website https://list.org > does point to it. Maybe not prominently enough for new users to discover? > I'll see if we can make the discovery of docs.mailman3.org better. I think the issue I found was running into outdated documentation for older versions of Mailman 3. Even doing a search for an up to date changelog or release notes are problematic. Again, I am also willing to help out with trying to get such vital pieces of information showing up prominently in search results. > I guess it is fine to be opinionated about choosing the technologies but > yet provide pointers to help people using other technologies. > > Right now, I do that using "Hints" and "Notes" and "See also" banners > through out the documentation to point to different pages where they > can lookup setup for other technologies. For example, how to setup > MySQL if official doc recommends Postgres. Are there still any outstanding issues with using MySQL? I know I ran into some when I tried to use MySQL and chose to go with PostgreSQL (which I am so glad I did). I still recall even seeing some recent issues brought to this list for someone using MySQL. I know MySQL is very popular for websites so I do believe the momentum for someone to set up a Mailman 3 server is to go with MySQL. Perhaps just putting up some heads up warnings (here there be dragons!) IF there are still issues out in the wild for those wanting to use MySQL with Mailman 3. Personally I will always steer clients to PostgreSQL when I get a chance. My own documentation reflects that bias. > Gitlab has a fairly good experience editing REsT files and you don't > necessarily > have to do much outside of a Web Browser actually. It lets you preview before > saving like wiki.list.org and you can submit it for review and merging into > main repo. > > Would you be more willing to contribute to official documentation if we > documented the Gitlab contribution process better? Absolutely. My current installation documentation was the result of a certain beautiful Mailman developer who I won't name (just protecting your privacy Mark!) providing me assistance when I decided to go with the certain installation direction. So if you scratch my back (i.e. teach me Master for I am your student!) then I will scratch yours. > Because we haven't yet gotten to updating those in the official docs, > unfortunately. And there are more things missing like Fulltext search (Xapian > recommended) and more of the Email setup like SPF and DKIM. Very much > aligned with your plans, which is why I suggested contributing updates > to docs.mailman3.org instead :) Well show me how to update the documentation and I will certainly take care of those things. I am also now comfortable in getting OpenDKIM working with Mailman 3 so I can also provide documentation there as well. I have done Xapian installations for clients but unfortunately did not document my methods so I will need to work on that. How do you feel about documentation for the use of Elasticsearch and Solr? Remember, I was a Mailman 2 host for years using cPanel. cPanel took the thinking of out a lot of things when it came to Mailman 2 hosting and I don't have that crutch anymore with Mailman 3. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 00:16, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:03 AM, Odhiambo Washington wrote: > > > > Thank you for clarifying. > > So once I have a venv created, the services will just run as long as the > > startup scripts are running even when I'm logged out of the system? > > > As long as the startup scripts actually reference things in the venv. > > If you look at the samples in the Recommended Configuration section at > <https://wiki.list.org/x/17891998> for > > /opt/mailman/mm/bin/django-admin (sample) Script to run Django > management commands. > > /opt/mailman/mm/bin/mailman (sample) Script to run mailman commands. > > and > > /opt/mailman/mm/bin/gunicorn (sample) Script to start Gunicorn. > > You will see they all do things like activate the venv or run a command > from venv/bin. > > > Now that has clarified the matter for me. That even when I am logged out, the scripts do the neccessary to activate the venv to run things. I hadn't looked at the scripts at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 3 months

[MM3-users] Re: LTMP to Postfix problem

by Brian Carpenter

On 6/18/20 4:09 PM, Mark Sapiro wrote: > Do you have > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > in the [mta] section of mailman.cfg? (these are the defaults) > > $ /opt/mailman/mm/bin/mailman conf|grep lmtp > [mta] lmtp_host: 127.0.0.1 > [mta] lmtp_port: 8024 I do > Is Mailman's lmtp runner listening on port 8024? > > $ sudo netstat -lntp|grep python > tcp 0 0 127.0.0.1:8024 0.0.0.0:* > LISTEN 1867/python > tcp 0 0 127.0.0.1:8000 0.0.0.0:* > LISTEN 1199/python > tcp 0 0 127.0.0.1:8001 0.0.0.0:* > LISTEN 1871/python It is. > > Is there some firewall issue blocking access to the port even from > localhost? Let me describe the problem a little better. Mail delivery from postfix to mailman works most of the time. However in the past week or so, lmtp starts refusing connections via postfix about once a day. I have port 8024 open in the firewall (UFW). There are no errors in the smtp.log file. I think restarting Mailman core seems to get things running again. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 10 months

[MM3-users] Re: hooking up mailman and sendmail

by John Covici

That post does not answer my question, it applies only to mailman2 and is a big mess. I was hoping to use lmtp, which sendmail will use and mailman seems to have some facilities to use it as well. Thanks. On Sun, 14 Mar 2021 10:29:20 -0400, Stephen J. Turnbull wrote: > > John Covici writes: > > > Hi. So, I have sendmail as my mta and I want mailman to use it. So > > far, I have a local delivery agent able to send on port 8024. So, > > what do I have to tell mailman to use sendmail and listen on port 8024 > > and to send on port 25? > > As Mark wrote in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, > > > For sendmail, see > > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> > > Regards, > > _______________________________________________ > 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

5 years, 1 month

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

by Brian Carpenter

On 2/17/21 6:52 AM, Andreas Barth wrote: > Just from the top of my head, for example I want to differentiate > between private, member and public lists. So if a member logs in, they > see more lists than a non-member. This is currently not possible, not > too big a deal (all member lists are currently configured as private) > but of course would be nice. Also archiv access should be aligned with > these permissions. What I have done with Affinity is design everything around roles. Roles are List Owner, Moderator, and List Member. So when a registered user logs in they will see: All their lists that they have a role in and an icon assigned to each role that they play. Those lists are shown at top. Below their lists associations, public lists are shown. These they do not have a associations with for the logged in user. Here is an image in what I am referring to: https://www.mailmanhost.com/wp-content/uploads/2021/02/Screenshot_2021-02-1… Is the above image what you are thinking about? If it is then I do think that is possible with Postorius with some customization. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

[MM3-users] Re: MM3 not processing some mails from specific user

by Stefan Bauer

Hi Stephen, thank you. Funny. All problematic mails are in the shunt-queue from one specific user. the mailman-logs did not log anything helpful. What do you recommend to find the needle in the haystack? I mean, what can cause mailman to fail processing? Stefan Am Do., 11. Aug. 2022 um 14:30 Uhr schrieb Stephen J. Turnbull < stephenjturnbull(a)gmail.com>: > Stefan Bauer writes: > > > Any idea what that could be? Here are some logs: > > I don't see anything in either the MTA log or the sample message. > However the sample message is incomplete, I assume the rest is an HTML > version of the plain text MIME part. It's unlikely but possible that > there is a defect in the rest of the message. > > Have you checked the Mailman logs? Typically they end up either in > /var/log/mailman or /var/lib/mailman/log (or variations on those > appropriate for your installation) > > Also, check the shunt queue, typically in > /var/lib/mailman/queue/shunt. This is where Mailman puts messages > that contain errors that didn't prevent delivery but make processing > impossible. > > Steve > >

3 years, 8 months

[MM3-users] Re: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Jan Eden

On 2025-06-16 17:29, Mark Sapiro wrote: > On 6/16/25 15:26, Eggert Ehmke via Mailman-users wrote: > > I have django-allauth 65.9.0 and still the same problem. mailman-web runjobs minutely throws it each minute, which is annoying. > > Do you have > ``` > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] > ``` > in your django settings? > > What releases of HyperKitty, Postorius and Django-Mailman3 are you running? > Current releases do not have any minutely jobs. I did have the same issue about a month ago[1] with the current versions of the above components, and these are the cronjobs I installed according to the docs[2]: @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…

10 months, 1 week

[MM3-users] Re: Implementing threading [was: hyperkitty failed to create a thread]

by tlhackque

Notes inline. On 12-Feb-19 11:09, Stephen J. Turnbull wrote: > tlhackque writes: > > > I believe that for threading to work more or less reliably, the > > thing to do is to look at the 'References' header. > > > > That should give you the thread in order, and allow any message > > received out of sequence to be put in the proper location in your > > display. > > This is more difficult than it seems, since References is not defined > for mail as far as I know (it's a netnews concept originally, and RFC > 5337 is a netnews-specific RFC). Not sure why you believe this. RFC2822 3.6.4 defines References for e-mail. See https://tools.ietf.org/html/rfc2822#page-25 As I wrote in later post, the message-ID syntactically requires the <>. (just one set). msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS] Look at that for the full syntax and reference. > Although it is adopted by most mail > clients, there's no guarantee of strict conformance. I agree that conformance has traditionally been hit-or-miss with almost everything about e-mail. Sigh. I also agree that life is hard. There have been clients that use the same message-id for all messages, and it's a long-standing problem. E.g. See https://cr.yp.to/immhf/thread.html Not only do you not have a guarantee of ever getting all links, you don't have a guarantee of the order in which they arrive. So one can have gaps ( parent, reply2-delayed, reply 3 references reply 2 and parent, reply 2 might arrive - or note.) You also can have a reply that references 2 or more branches. E.g. /--R0 p/--r1 \ \ --r2 / And a reply (r3) comes that references r1 AND r2 (and the parent) - which you probably want to show as a descendant of both r1 AND r2. R4 replies to r2 - but that's also an implicit response to r1. Once you's sorted that out, r5 comes along that references R0, r4, and P. 2822 does say: Therefore, trying to form a "References:" field for a reply that has multiple parents is discouraged and how to do so is not defined in this document. But programmers are rarely discouraged - with GUIs, it's pretty easy to intuit that one might like to check the boxes on several branches of a thread and respond "Of course, you're all right - see my cat photo". :-) 5537 tries to make life easier - until you get to: If the resulting References header field would, after unfolding, exceed 998 characters in length (including its field name but not the final CRLF), it MUST be trimmed (and otherwise MAY be trimmed). Trimming means removing any number of message identifiers from its content, except that the first message identifier and the last two MUST NOT be removed. So, even if you get all the messages, you don't necessarily get all the references that you need. I'm sure glad that I'm not working on Hyperkitty! But I'm not holding my breath for when MM3 is complete enough to adopt in my environment. Yes, "In-Reply-To" is more often present (likely because it's modestly simpler for RFC-readers to understand - it's one thing, not a list.) It's less expressive (hence, informative.) One can try to use it as a fallback when no References is present (and that's what 2822 implies). The whole undertaking in the real world is an example of the halting problem. Or Parkinson's Law. The best one can do is to come up with a "good enough" approximation in the available time, and tinker with/improve it until bored. It's likely to be a bunch of heuristics. And if you're not careful, throw in the Peter principle :-( > In mail, > In-Reply-To is more reliably present, but of course asynchronicity > means you have no guarantee of a complete set of all links. Even if > all clients conform to the netnews RFC, you still need to create the > full tree (full conformance to RFC 5537 means it will be a tree), and > break ties between branches in some arbitrary way to create a total > order. It's worse if you *don't* have conformance from all clients: > you can get a DAG or even something that isn't even a DAG. So, even > today, you can't assume a well-behaved ancestry graph. > > > 'References' should be a superset of Reply-To (which is at most 1 > > Message-ID), so you only need Reply-To if there is no References - or to > > handle a client that doesn't obey the RFCs. > > I suppose HyperKitty uses References (it works for messages that have > proper Message-IDs ;-), but I don't know what algorithm it uses. > Might be worth looking into, as well as considering a more Postelian > parsing of Message-IDs. Specifically, take the field body, unfold it, > strip leading and trailing whitespace and leading "<" and trailing > ">", and whatever's left is the message ID. > > Alternatively, strip everything that's not atext or "@" (including > inside the purported Message-ID). See my other post. The left and right halves can, besides being atoms, be non-folding quotes or literals. So you have to handle that. Although I have recently seen e-mail clients that are confused when you do it. (Ran into that generating content-id for multipart/related. Yes, MIME makes plain e-mail look straightforward.) Although it has a defined syntax, the semantics are that message-id is an opaque globally-unique identifier. Attempting to parse it as anything but '<[^>]+>' is likely to be a mistake. (On receipt; generating is the other side of Postel-correctness... I commend RFC 2468 to anyone who hasn't read it.) I doubt 'striping' is worth doing - when an message-id is present, I've almost always seen it include the required <>. Until yesterday's hyperkitty bug, I've never seen <<>>. I've rarely seen the <> missing - but I'd consider that a warning that the message format is suspect. As in this case. My suggestion is that if you can't find a message-ID, keep the message in an "unthreaded" bucket. If you sort that by subject (omitting "[listtag]" and "Re:*" (case insensitive, and in multiple languages) then by date, you probably have a useful presentation. And a list of MUAs that need bug reports :-) Yes, althought 2822 says that "Re:" is the proper introducer in the subject of a reply, RE: is common, and I've seen it (incorrectly) translated in the headers.) As I said, "life is hard". > This won't break any RFC 5537-valid > Message-IDs, but might identify two different, nonconforming > Message-IDs as the same (too bad if they can't take a joke!), or > identify a nonconforming message with a conforming one (<sad_emoji />. > > Thoughts? > > Steve > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 2 months

[MM3-users] Docker, Mailman 3, templates and list user accounts

by Henrik Rasmussen

I used Docker to installed Mailman 3. The top header of the web interface says "Example.Com" while linking to the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a post[1], Mark Sapiro referred to the template system in Mailman 3 by pointing out that "a custom template can be put in var/templates/site/en/welcome.txt or var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> or var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> where var is Mailman's configured var_dir". I believe this refers to the mail templates. 1) Where do I change the similar template system, for the web interface, without breaking a laver upgrade? 2) How do I change the site name in the top of the web interface on Mailman 3 to my subside and ? [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… The Mailman command in Mailman Core doesn't seem to have a command for listing the accounts users have created by using Sign up in the web interface, so I believe that accounts may be created in the webinterface. Is there similar commands for the web interface like the mailman commands for the Mailman core? Regards, Henrik Rasmussen

8 years, 8 months

[MM3-users] Re: Question about adding addresses using the REST API

by Mark Sapiro

On 1/15/22 10:03 AM, Stephen Daniel wrote: > > The only way I've found to create a standalone address (not linked to any > user) is to create a user with that address, unlink the address, then > delete the user. > > Is there a more straightforward way to just create an address with no user? The more straightforward way is via the IUserManager create_address method. This method is not exposed directly in REST, so you can't do it via REST. My question is why do you want to? Granted when an unknown nonmember address posts to a list we create a standalone address record, but maybe we should be creating a user too. We don't because it's tricky. Suppose User A with address A posts to a list from nonmember address B. We create the standalone address B record as a nonmember, but now user A can add address B as another address. If we also created User B, this would not be possible. But again, what is your use case for creating standalone addresses? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Archives with encoding characters

by Seth Seeger

I should add that they are both on Plain Text Digests. (People seemed to be unhappy with MIME digests, because they had to double click on each email to open it up. You couldn't just scroll through a long email.) Seth On Wed, Mar 4, 2020, at 4:55 PM, Seth Seeger wrote: > Hello everyone, > > I have a few (but not all) members complaining that their digests are > full of coded characters. Two examples below were forwarded to me: > > > What I ended up doing was creating 2 "practice lines" in the centre of=20 > > our big teaching circle (I always teach new figures in a big circle) -=20 > > which each had 3 people set up in a line with generous space between,=20 > > and first=C2=A0 I walked through one of those lines myself starting first= > > =20 > > and > > > Robins pass Right=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Larks Loop L= > > eft > > What is the cause? Is there anything I can do about it? > > Thanks, > Seth

6 years, 1 month

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

by Mark Sapiro

On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > Is nntp common enough these days to be a useful default runner? > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > resources (yet another Python interpreter running) for a fairly edge > case of mailing list <--> nntp transits. You raise an interesting point. By default, the runner runs, but if there are no lists gating to usenet, its queue is always empty and it mostly sleeps between waking, finding its queue empty and going back to sleep. A more significant use of resources is every (default) 5 minutes spawning `mailman gatenews` which goes through a startup process and then looks at every list figuring out there's nothing to do. We could default mailman.cfg to contain `start: no` in the runner.nntp section so people would need to enable it if they wanted it. What do others think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: My email address appears in quoted test in my list. Hoot change that.

by Abhilash Raj

On Wed, Sep 4, 2019, at 5:56 PM, paul(a)arenson.org wrote: > Thank you. When you say OPTIONAL, do you mean it is up to me (in the > web interface or email client) to remove them as I have done below? Right, it totally depends on how one is replying. In the web interface, since you already seem to be using it, there is a button which adds the quoted text if needed. For email clients, the behavior varies from one client to other and there are tons of them. Some will quote by default, some won't. Then, it also depends on the users, since even if it is not the default, they can optionally add quotes. > > Abhilash Raj wrote: > > On Wed, Sep 4, 2019, at 5:41 PM, paul@-------- wrote: > > > Hi. I thought I had the settings right, but I do not > > > see one to get > > Thanks. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Mark Sapiro

On 6/22/20 7:58 AM, Waqas Ahmed Khan wrote: > Hi, > > I have installed mailman3 with postfix. The server is working fine. To > protect the IPs from blacklisting, I want to relay all emails from > postfix/mailman to external SMTP servers like O365, Gmail, or our exchange > server. I would not recommend using O365 or Gmail as outgoing MTAs. I don't really know about )365, but I don't think Gmail likes you to send mail via a gmail server if it is not From: (or maybe envelope from or both) a gmail or googlemail address. > Could you please confirm is this possible. And how to do its configuration. It is possible and there are two ways to do it. You can configure this in Postfix to relay all outgoing mail via some other server. You can configure it in Mailman by setting in the [mta] section of mailman.cfg smtp_host: smtp_port: and presumably for authentication smtp_user: smtp_pass: Also see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… and following for other relevant settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: If you delete a list but not the HyperKitty archive

by Philip Colmer

On Tue, 4 Jan 2022 at 18:34, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/4/22 6:45 AM, Philip Colmer wrote: > > > > So ... should the archive be deleted when the list is deleted and it is a > > bug that it isn't? Or is it expected that access to the archive is > "frozen" > > once a list is deleted? > > > It is often desired to have a public archive available after the > corresponding list has been deleted. Even for a private archive, it may > be desirable for site admins to have access. Furthermore, a list might > not even have a HyperKitty archive in the first place. Thus, what to do > about a HyperKitty archive (or prototype archive or ...) when a list is > deleted is an administrative decision and is best left up to the site > admins to do it or not. > > As you note with a private archive, former members no longer have access > when the list is gone, but unless an attempt throws some uncaught > exception, that is not a bug. > Thanks, Mark, for the clarification. Regards Philip

4 years, 3 months

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

by worik

This has been a very interesting discussion. We should be mindful that it is occurring all over society. It is arguable, and I hope true, that the worm has turned regarding privacy. People are starting to realise that you always (in the general case) are paying for a service. If not with money then with something else. In some cases both (hello square space!) tl;dr The choice for or against using the big bad corporation services needs to be clear and usable. Privacy is a minority interest today but IMO the writing is on the wall and for web services it will become the wolf in the kitchen. On 14/02/19 3:42 PM, Stephen J. Turnbull wrote: > Jonas Meurer writes: > > > But still, adding so-called "social" authenticators to the mailman3 > > django application will expose users to the risk of clicking on > > those ID provider buttons. > > I can see this point for Debian users. I suspect Ubuntu users are > somewhat less paranoid. :-) > > Since that risk holds even for sites that enable explicitly (assuming > we adopt the same policy) I will take a look at making that risk hard > to realize (more distance from anything else clickable, smaller > buttons with visible and accurate boundaries. Better that it is off, or it is on for a selected group of providers. The issue is not the prominence of social login options but the presence. I disagree that accidental clicking on social login widgets is a major issue, but I have no data, so it is a opinion. > > > Personally, I consider it a major privacy issue if one central > > instance (e.g. Facebook) is able to track on which platforms and > > services you authenticate. > > Sure, but that ship has pretty well sailed AFAICT. Most users use > unconfigured versions of IE (or Edge) and Safari, which means they're > subject to all manner of webbugs. My employer just asked me to stop > using Firefox because it's too pedantic for their website development > vendors. :-( GDPR enforcement seems to primarily be an arm of the EU > trade offensive against large American services (that's the > Economist's recent opinion, not mine), while Europe-based globals are > undoubtedly doing the same crap. The ship has not sailed. We can get back what we have lost. The new generation of web developers are, in my experience, too enamoured with the cool stuff they can do, and ignore old grey beards (like myself) talk of "attack surfaces" and "chains of trust" and blithely install google fonts, load javascript from CDNs, etcetera that gives their user's data away without a thought or regret. Ten milliseconds and 20kb is considered too high a price to pay for enabling some body else's privacy. But they are starting to face push back from consumer groups who understand the value of what is being handed over. > > And to be honstes, I'm a bit irritated that those tracking features > > from big corporates like Facebook and Google, whose main business > > model is to aggregate as as much private data points as possible > > about as much users as possible are enabled by default in Mailman3 > > upstream. > > Your irritation is not our problem, though, since you can use Debian's > version, and as I mentioned earlier, as far as I know most of our > sites are happy to have social auth. I will be paying attention to > the list to see what others think. That irritation is exactly the problem. It is a problem we need much more of. > > > Besides the privacy concerns raised above, on problem with central > > authentication services is that they also create new single points > > of entry/failure. If your Facebook account gets hacked, you now > > loose control over all other services/platforms, that you used the > > Facebook authenticator service for. > > Same thing if you use a weak password. Effective and secure > authentication is not something we're good at, and we can't really > afford the effort to be good at it. These things are tradeoffs, and > the default should be something that most of our users (ie, site and > list admins, NOT subscribers) want. Hopefully their preferences in > this respect reflect those of *their* users (== subscribers). Attack surfaces. "Whataboutism" is not a valid argument against the argument that you should decrease your attack surface. But social authentication is enabled are the trackers are not loaded too. As far as I can see. If so that is a good thing. The big bad corporates only get data when some one actually uses their services. > > > I agree with Torge that those social auth providers should be > > disabled per default. IMHO, A sane default would be to list them in > > the settings.py but have them commented out. > > "Those" social auth providers? Are there social auth providers who > provide what you consider acceptable privacy guarantees (a la > Duck-Duck-Go in search engines)? If so, we could make those higher in > the list/easier to use. I disagree that they should be disabled by default. I agree they should be disabled, but it should be by choice. What is required is a configuration option in the interface not in the text configuration files. The former is for list administrators the latter is for site administrators. Currently list administrators do not have that choice. (I am new here, do I have that correct?) Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

7 years, 2 months

[MM3-users] Re: modify subscription page by mailinglist?

by Stephen J. Turnbull

Lars Schimmer writes: > And I think I could fiddle out how it works. But in general, e.g. a > custom page per mailinglist for the "list information page" is a bit > more work than expected and I will not follow this idea. > (e.g. adding a logo per list, ...) Just adding a list-specific logo is not hard. Choose a naming convention (probably something like f"logo-{list_id}.png"), put the logo PNG in one of the static directories and add <IMG SRC="logo-{{list_id}}.png" ALT="Logo for {{list_id}} list." /> in the right place in each template (maybe even "base.html", but more likely an intermediate template specifically to allow putting such customizations in one place for list-specific pages). Adding the ability for a list admin to easily upload a file and set the logo to it would require surgery to Postorius's Python code, though. I will admit that though I think this is a cool idea, I am not interested in doing it myself. But if your interest is at the "I'd rather wait a few months than do myself", GSoC is coming up again, and you could lobby for it when the students start applying. ;-) Steve

4 years, 3 months

[MM3-users] Mailman3 not able to deliver emails sent through list, but moderation notifications

by Daniel Böhmer

Hello Mailman users, I've been using Mailman2 for 10+ years and have recently upgraded to Debian Buster with Mailman3. I've tried to setup Mailman3 similarly but it fails to deliver emails sent through a list. I do receive all moderation notifications at the same time. During startup /var/log/mailman3/mailman.log receives: > Cannot connect to SMTP server localhost on port 25 but I've made sure postfix is listening on *:25 for both IPv4 and IPv6. When sending a message to a list the same file receives: > Nov 25 11:38:14 2022 (70371) ACCEPT: <MESSAGEID@HOST> (message ID and host redacted) and nothing else happens: no more log messages, Postfix logs the email sent TO Mailman but doesn't log anything about emails sent BY Mailman. If Mailman fails to send emails via Postfix I'd expect it to log error messages but it doesn't seem to do so. I found this article stating the the SMTP error message might be misleading: https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… How to further debug this? What could be wrong with my Mailman3 instance and how to fix it? Kind regards Daniel Böhmer

3 years, 5 months

[MM3-users] Re: Installing Mailman3 under a Python Virtual environment running on RHEL9

by Odhiambo Washington

On Tue, May 21, 2024 at 2:44 PM Andy Macheta <andy.macheta(a)gmail.com> wrote: > Hi, > So tried, without much success, to get Postorius working on my Mailman3 > server and every internet trick& tip I tried did not work so decided to > take a new approach as recommended at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Used this reference: > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… > which I know is more for Debian/Ubuntu systems but I was hoping that 90%+ > would also work with Red Hat. > Fell at the first hurdle with no packages available called "python3-dev" > or "python3-venv" > The virtualenv method should work for all OSes, not just Debian/Ubuntu. I use it on FreeBSD too. I have never touched RHEL, but Google-foo tells me that you need to do: yum install -y python3-devel Alternatively, search for the package in yum , use the following command: yum search python3 | grep devel You could also search for the venv one by: yum search python3 | grep env Whatever else you'd need to install on the base OS, just use the above search method and install it. Feel free to post questions here if you aren't sure on what to install. The documentation - https://docs.mailman3.org/en/latest/install/virtualenv.html - requires you to install the following in the base OS: 1. python3-dev python3-venv sassc lynx 2. A database server - could be PostgreSQL or MySQL. You can search for them too :) 3. An MTA - could be Postfix or Exim. Your choice. 4. A webserver - could be Apache or Nginx The challenge you're likely to face is probably to do with how to start the MM3 core and MM3 web services, but you can figure that out, no? Alternatively, just dump RHEL and use any Debian-based OS :) Is there anyone that has managed to install a running version of Mailman3 > that has a working GUI whether it is on bare metal or Python virtual > environment and if so, could they kindly let me know how they did it?? > The closest I've come is a running command line version of Mailman3 which > is fine for me of course but not for anyone else as they like access via > web browser. > Let's see if you can get this running in the next 3hrs. Do you use WhatsApp? Let's chat on +254732000004 -- 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, 11 months

[MM3-users] Re: Enable delivery

by Mark Sapiro

On 12/9/24 17:35, Hirayama, Pat wrote: > Greetings, > > I'm finding something a bit odd with our listserv. Please see https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv > Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled). If you look in the MTA logs is mail being sent to them. As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p… Also see the various tabs at https://www.example.com/mailman3/accounts/subscriptions/ > If I select Enabled and Save, then delivery starts working for that user. This should only happen if the users address or user based preference or the global preference is Disabled. > There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run: > > mailman members --nomail any listname@listserv > > Nothing is returned. Because all members ultimately have delivery enabled. > If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great. It shouldn't be necessary to do that. For one of these members, e.g. user(a)example.com, that isn't getting mail, do this in mailman shell ``` mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)example.com') >>> print(mbr.delivery_status) (this will print the ultimate delivery_status, for the components do) >>> print(mbr.preferences.delivery_status) (output) >>> print(mbr.address.preferences.delivery_status) (output) >>> print(mbr.address.user.preferences.delivery_status) (output) >>> print(system_preferences.delivery_status) (output) >>> ``` The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status). -- 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: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Stephen J. Turnbull

Kimmo L writes: > This is simple test email with content like "Test test test" to > test out this specific mailing list, which somehow does not sent > emails to the list of members. Wierd that other lists works fine, > but this one is bugged. Maybe i should try to delete it and > recreate it ? That might work. > 2) This second error seems indeed not related with that first one. > "AttributeError: 'NoneType' object has no attribute 'strip'" occurs > quite many times in mailman.log file. Should i check some specific > list settings? I don't think so. That usually indicates mal-formed mail, missing a required header field. In the case you posted earlier, the mail had no Message-ID that Mailman could find. I suspect you have a configuration where your MUA doesn't add the Message-ID header (this is common, because all internet-facing MTAs do add one if there isn't one already in the message, so many MUAs let the MTA do it), and for some reason local mail doesn't go through a proper MTA and never does get one.

3 years, 7 months

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 9/11/24 15:21, Dan Caballero wrote: > Mark, > > Do you have any tips for scripting the setting changes via mailman shell -l somelist(a)caltech.edu or a python script to run. eg. mailman shell -r dmarcsettings.py? > > We have a number of lists that email Gmail addresses either directly or via aliases and virtual email domains using Google Workspace. If your Mailman version is >=3.3.9 you can add `^.*(a)gmail\.com` to each list's `dmarc_addresses` to apply `dmarc_mitigate_action` to any mail From: a `(a)gmail.com` address. A `mailman shell` interaction to do that and set `dmarc_mitigate_action` to munge_from for all lists is like ``` $ /opt/mailman/mm/bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager): ... mlist.dmarc_addresses.append(r'^.*(a)gmail\.com') ... mlist.dmarc_mitigate_action = DMARCMitigateAction.munge_from ... >>> commit() ``` If your Mailman is older than 3.3.9 or you don't want to use dmarc_addresses, replace the line ``` ... m mlist.dmarc_addresses.append(r'^.*(a)gmail\.com') with ... mlist.dmarc_mitigate_unconditionally = True ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by John Hein

Mark Sapiro wrote at 12:18 -0700 on May 12, 2016: > On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote: > > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. > > > This format vs. plain text digests was a user option in Mailman 2. > > > > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. > > > The core still supports the same plain text and MIME format digests and > the same individual subscriber and per-list default formats as did > Mailman 2. The issue is none of these things are exposed in Postorius. > > If you subscribe to digests on this list, you will receive the > 'encapsulated' MIME format because the lists mime_is_default_digest > setting is True, but currently that has to be set through the > bin/mailman shell tool. > > > > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? Thanks for the info - and Barry's reply as well. I understand that MIME digests are supported in Mailman 3 - that's what I'm using (and thanks, Barry, for the info that Summary Digests is the same right now). My quibble is that the multipart/digest encapsulation level is gone. Barry Warsaw wrote at 15:16 -0400 on May 12, 2016: > The MIME format of MIME digests should roughly be: > > multipart/mixed > text/plain (the digest heading) > text/plain (the TOC) > message/rfc822 > message-1 > message/rfc822 > message-2 > ... > text/plain (footer) But mm 2 had: multipart/mixed text/plain (the digest heading) text/plain (the TOC) multipart/digest <--- this is the part that's gone in mm3 message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer) So was that removal intentional, a bug or ?? Maybe you're saying there is definitely an unexposed (in Postorius) knob for that in mm3. > > It is the intent that Postorius will eventually expose all these > settings. We're not there yet. At present you could possibly do this by > interacting with mailmanclient, although I'm not certain the settings > are exposed there. You can do it via bin/mailman shell if you have > access and know what you're doing (see > <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>) > > If you file an issue at > <https://gitlab.com/mailman/postorius/issues/new>, it might help > expedite this. Okay.

9 years, 11 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

Hi, On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > It's ok now, but still I can't make it send the confirmation email > > This is from mailman.log: > > > [mailman@localhost logs]$ tail -f mailman.log > Aug 01 15:59:18 2017 (2327) lmtp runner started. > Aug 01 15:59:18 2017 (2333) virgin runner started. > Aug 01 15:59:18 2017 (2332) retry runner started. > Aug 01 15:59:18 2017 (2330) pipeline runner started. > Aug 01 15:59:18 2017 (2325) command runner started. > Aug 01 15:59:19 2017 (2328) nntp runner started. > Aug 01 15:59:19 2017 (2326) in runner started. > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > 90 > > > > > What should I do? If you are talking about Account confirmation emails, they usually are sent out from Django and not Mailman Core itself. To configure Django you need to edit the `settings.py` file, wherever that is one your installation. If you are following the guide mentioned at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at `mailman-suite/mailman-suite_project/settings.py`. To configure your Django to send emails, have a look at http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required. That documentation page has pretty much everything you need in order to have a running Web Frontend, please go through it and make sure you have everything configured. Finally, the actual emails from Mailing lists are supposed to be handled by Core. You need to configure Postorius & Mailman both to communicate. The settings are mentioned http://docs.mailman3.org/en/latest/config-core.html#configuring-mta here. Hope that helps! > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > Why does it say Address already in use? > > > > > > Because you are starting lm tp runner and it's already running. > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > any if necessary. Then do 'mailman start'. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years, 8 months

[MM3-users] Immediate notification to the administrator

by Stephen J. Turnbull

pau.baiges(a)csuc.cat writes: > When there's a message being held because it needs approval, it > automatically sends an email to the list owners. However, it also > states that it sends a daily reminder if the email remains > unapproved, but it's not doing that. Did it send the daily reminder before, and then stop? Or did it never send the daily reminder? The immediate notification is triggered by the receipt of the moderated mail. However, once that happens, the Mailman daemon no longer pays attention to it. Instead, there is a cron job that runs once a day that checks the held queue and sends daily reminders. The most likely reason is that the cron job is not running. > I'll show you how I have /etc/postfix/transport configured. I > receive the first "owner" email, but not the daily one. This is irrelevant. The same Mailman function is used to send both the immediate notification and the daily reminder, and it does not use the list-owner alias to do so. The difference is only whether it is run from the Mailman runner daemon or from a one-shot process started by cron. It consults the list configuration directly when composing the email. Steve

2 years, 5 months

[MM3-users] Re: Unknown attribute: max_message_size

by Abhilash Raj

On Wed, Dec 6, 2017, at 08:25 AM, Simon Hanna wrote: > On 12/06/2017 11: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. > It is. https://gitlab.com/mailman/mailman/merge_requests/329 I have added a backport-candidate tag to the MR and will get it out in 3.1.2 release, if that happens. > > > > > What to do? I understand that it might not be the best answer, but `rolling` tags for images do have this problem fixed, they are based on Git-heads. > > > > I have Maxking mailman-docker but can easily copy files into the image if > > necessary. > Are you sure you have up to date images? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 4 months

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

by Guillermo Hernandez (Oldno7)

On 6/8/21 18:37, Mark Sapiro wrote: > On 8/6/21 9:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> Hi all: >> >> I need to remove all non members from a list. I know I can do it via >> Postorius, but it has to be done one at a time. (you can delete ALL >> suscribers but not all non members...) >> >> Anyone has a python recipe to do this? > > $ /opt/mailman/mm/bin/mailman shell -l list.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> for nonmember in m.members.nonmembers: > ... nonmember.unsubscribe() > ... > >>> commit() > Thanks a lot for the promt response, Mark. It's not functioning. It says: "AttributeError: 'MemberRoster' object has no attribute 'nonmembers'" My system info is: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Postorius 1.3.4

4 years, 8 months

[MM3-users] Re: Create a mailman-web admin user

by Odhiambo Washington

On Tue, Jul 30, 2024 at 4:55 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2024/07/30 15:48, Roland Giesler via Mailman-users wrote: > > However, which user in the mailman user mentioned? > > > > I tried to do this as root, but login in as an admin doesn't give me > > any option to create new lists in postorius. What am I missing / > > doing wrong? > > > I seem to have solved the riddle. The "mailman-web createsuperuser" > command suggest the the mailman user is www-data, which I accepted. That > worked and I can now create a new list from Postorius. > Actually, it wasn't a riddle. You looked at documentation meant for the virtualenv <https://docs.mailman3.org/en/latest/install/virtualenv.html>installation method while your installation seems to be done from your OS package distribution. The OS package installation is fraught with pain. The virtualenv method is the officially recommended. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

[MM3-users] Re: manage.py runjobs hourly

by Mark Sapiro

On 6/11/20 11:04 AM, Mark Dadgar wrote: > I have started getting this emailed to root each hour from the cron job. > >> From: root(a)pdc-racing.net (Cron Daemon) >> Subject: Cron <www-data@mail> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly >> Date: June 11, 2020 at 11:00:06 AM PDT >> To: www-data(a)pdc-racing.net >> >> 18:00:03 [Q] INFO Enqueued 1350 >> 18:00:03 [Q] INFO Enqueued 1351 > > The Enqueued numbers do increment. > > Anyone know what this is? The short answer is you fixed your HyperKitty indexing issue so the hyperkitty update_index job has work to do and some of those tasks get queued by Django Q. See <https://gitlab.com/mailman/hyperkitty/-/issues/295> for another discussion around this. Those messages depend on system load. Sometimes you'll see bunches of them and sometimes (at least on mail.python.org which is the most busy server I am involved with) you won't see any for up to a week or longer. Run django-admin qifno to get the current django q stats. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 12/1/22 01:43, Jan Eden via Mailman-users wrote: > > There are currently 5 (test) threads in the archive. After changing the > PATH in the HAYSTACK_CONNECTIONS dict to /opt/mailman/fulltext_index, > and fixing the issue with MAILMAN_ARCHIVER_FROM above, > /opt/mailman/web/logs/mailmanweb.log does not display new error > messages, but I do not get any suggestions for reattaching threads, and > a search for a specific thread subject ("Third test") does not return > any results. By "search for a specific thread subject", do you mean searching via the search box at the top of HyperKitty pages? This relies on the search index for Haystack (Whoosh in your case). This index is updated by the HyperKitty update_index job. Assuming you have set up the cron jobs for Django <https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…>, this will be run hourly and posts added to the archive in the last hour won't be indexed. > So reattachment works in principle, but the suggest/search function does > not. Reattachment suggest doesn't depend on the search index, but it does depend on loosely matching thread subjects. -- 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: Guidance Request: Migrating Existing Mailman 3 Installation to Docker-Based Deployment

by Prasanth Nair

Hi Odhiambo and Stephen, Thank you both for your helpful responses and guidance. Given that this is a critical production system, I am now considering migrating to a new server using a host-based Mailman installation first, before evaluating a Docker-based setup at a later stage. In that case, could you please advise on the recommended approach for migrating from my current host-based Mailman 3 installation to a new host-based server? In particular, I would appreciate any guidance on: - Safely migrating the PostgreSQL databases (e.g., dump and restore approach) - Preserving mailing lists, memberships, and configurations - Migrating HyperKitty archives and Postorius data - Any best practices to ensure a smooth cutover with minimal downtime Any documentation or pointers you can share would be greatly appreciated. Thank you again for your time and support. Kind regards, Prasanth Nair On Sat, 11 Apr 2026 at 17:52, Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Prasanth Nair writes: > > > I am currently running a Mailman 3 setup on a standalone server and > > planning to migrate it to a Docker-based deployment using the official > > Docker Mailman images. I would appreciate your guidance on the > recommended > > approach for this migration. > > docker-mailman is basically a hobby of the maintainer's. It's not > even maintained in the GitLab project. As far as I know it's there > because it's frequently requested and folks who run docker usually > know what they're doing so it doesn't impose a particular burden on > us. But really the only expert on docker-mailman is Abhilash himself. > > All three of the major Mailman suite applications (core, Postorius, > and HyperKitty) use object-relation managers with automated schema > updates. So contrary to Odhiambo's advice, I would try to replicate > the versions of the Mailman components and PostgreSQL, then do > upgrades in-place in Docker. Doing a database dump (in the current > host) and restore (in the containerized PostgreSQL) is safe if you > have the same schema on both hosts. (Upgrading the PostgreSQL version > is much less risky but why tempt the software gremlins?) > > An alternative if you know PostgreSQL well would be to setup a > "failover and failback" system, where you start with your current > PostgreSQL as the primary and the container's as a replica, then when > you're ready to go live you swap primary and replica for the database > and point the DNS to the containerized Mailman. This probably > involves less downtime (although in my experience PostgreSQL dump and > restore is quite fast, and the Mailman databases for core and > Postorius are small), but the big advantage is if you have a problem > with the containers you can switch back right away. I know this works > because I worked on a project where high availability was required, > but another guy did the PostgreSQL work so I can't provide details. > > Networking is a FAQ for mailman-docker. I've only run it out of the > box with all its defaults, and that worked fine. But somehow people > have problems with it. My guess is that they're trying to fit the > Mailman containers into some predetermined scheme, either a Docker > host that hosts other containers and there are IP conflicts, or some > organizational constraints. If you know what you're doing, no problem > I think, but if you're newish to containers, you might want to set up > docker on a host dedicated to Mailman. > > Other than that, I think Abhilash provided a preferred channel for > discussing docker-mailman in the docs in his repo, that would be where > to get your best (and more detailed) information. > > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan > _______________________________________________ > 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 prasanth.nair(a)linaro.org >

2 weeks, 2 days

[MM3-users] Re: mailman3 not working for mailman21 lists

by blup＠fortytwo.ch

Stephen J. Turnbull wrote: > blup(a)fortytwo.ch writes: > > I installed mailman3 on a server where mailman21 was installed > > before. Newly created mailinglists work fine. But if I create > > mailinglists with a name that was previously used on mailman21 > > nothing works >> If I send a mail to old list list1(a)a.b and new list list2(a)a.b [..] > Your logs below show that *something* is working because Mailman 3 is > logging the incoming message. I didn't mean nothing literally, what I meant is that the mail to list1 is neither being sent out nor shown in the list archives nor ... I.e. all general stuff is working, but things specific for list1 aren't (whereas they do for list2). > > (same behaviour with and without import of old configs and > > archives; no logs). > I don't understand what you mean by "without import of old configs". > Do you mean you just create the list with the old name? Did you do > any further configuration and set up of that list? First I did create the list with the old name and imported the old configs with mailman import21. As the list did not work then, I deleted it and created it again (with the same manual configuration as for the new list that's working). If you think the problem is neither mailman3 nor postfix, the only issue could be that the first import set some wrong setting for the old list which was not removed when deleting the list. > > How can I get more info on why the mail for list1 isn't processed? > First check the queues (normally /var/lib/mailman/qfiles/*/* where the > first * is a wildcard for list names and the second is a wildcard for > message objects, the '/var/lib' part may be different in your > installation) for a "stuck" message. I don't have a qfiles directory. In /var/lib/mailman3/ there are archives cache data lists locks messages queue templates web > Second, have you checked the other Mailman logs for information? Sure -- nothing there... > Third, are both lists visible in the message header as addressees? You mean in the header of the received message via list2? Yes it is. > Is the 'outgoing' qrunner still running? (ps ax | grep outgoing) no > Are there any subscribers with delivery enabled on 'list1'? yes > Is list1 configured to accept only member posts? If so, is the sender > a member whose posts are accepted? Yes. Anyway: there should be a reaction if there is a post from a non-member (i.e. mail shown in held messages, sender and admin being informed of it). > Is there a sibling list setting that would prevent the message from > being sent to the same address if it is on both lists? I don't think so. But also if it would be that couldn't be the problem, as my previous tests all only included list1. > Are the spam filter settings the same? No clue -- where do you set them? But once more: list1 was working fine as long as mailman21 was used and stopped working when switching to mailman3. I don't expect spam filters that worked with mailman21 to stop working with mailman3. > > How can I diff the config between list1 and list2 from the command > > line? > This doesn't seem to be implemented. I need to prep for some > meetings, but here's the basic strategy I'd follow: > > Use "mailman withlist -i -l list1". This puts you in a Python > interpreter command line. > Next "attrs = dir(m)" to get the list attributes as a list. Should this give an output? I get none... > Check "attrs" for things like the roster of subscribers that > you're not interested in printing out, and delete them. How? > Open a file as 'f', then loop over attr in attrs using > "print(f'{attr}: {getattr(m, attr)}', file=f)". I have more or less no Python knowledge (i.e. I can read and understand Python but can't write it). Could you please give me detailed command by command instructions. Thanks. Regards Diana

3 years, 8 months

[MM3-users] Re: Rebuilding a list index fails

by Mark Dadgar

On Feb 17, 2021, at 11:06 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: > On Feb 17, 2021, at 9:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On 2/16/21 9:59 PM, Mark Dadgar wrote: >>> Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. >>> >>> Error messages below. >>> >>> rebuild_index fails with the same error. >>> >>> This is with django version 3.0.12. >> >> >> django.utils.six was removed in Django 3.0. See >> <https://pypi.org/project/django-utils-six/> for a work around >> replacement. I.e. in your venv do >> >> pip install django-utils-six > > > OK, that got me a step further. Then I needed to do a “pip install xapian-bindings” and now I am up and running. One last note on this for the next person who searches the list archives: I also ran into the “Key too long” error while re-indexing. Applying the patch linked here fixed it: https://gitlab.com/mailman/hyperkitty/-/issues/322 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: Moderating posts via email

by Abhilash Raj

On Thu, Oct 26, 2017, at 02:21 PM, Dmitry Makovey wrote: > Hi, > > we are trying to figure out what is that we're doing wrong as we can't > use instructions that mailman sends with information on held messages as > referenced in: > https://gitlab.com/mailman/mailman/blob/master/src/mailman/chains/hold.py#L… > > In particular - replying to the message with "Approved: listpassword" we > were not able to approve any message. Did you add it to the body/subject of the email? AFAIK, Mailman looks for "Approed" header to approve the held messages. > Since there's no place we could find in interface to change ML password > I did it through the mailmanclient: > > ml=client.get_list('mylists(a)lists.some.com') > ml.settings['moderator_password']='password123' > ml.settings.save() > > 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? > > -- > Sr System and DevOps Engineer SoM IRT > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

8 years, 6 months

[MM3-users] REST Runner (and other runners) taking long time to boot up

by Dmitry Makovey

splitting this discussion into it's own thread from "MM3 occasionally chokes (?)". Re-iterating background info for posterity: we have been experiencing increasingly long boot ups from mailman-core over the past year to the point where it's at about 45min for the sequence to complete. We run couple of mailing lists (20+) that are anywhere between 100 and 10K+ members and most of them are low traffic. From what I can tell all that time is spent doing some sort of indexing operations, I'm writing from memory since I can't restart the system to confirm that. sizes of directories that containers use: 3.6G core 352M database 285M web state of my queues (as far as I understand how to evaluate them: $ for q in core/var/queue/*; do echo ${q}; ls ${q}/ | wc -l ; done core/var/queue/archive 1 core/var/queue/bad 3845 core/var/queue/bounces 0 core/var/queue/command 0 core/var/queue/digest 0 core/var/queue/in 0 core/var/queue/nntp 0 core/var/queue/out 7 core/var/queue/pipeline 0 core/var/queue/retry 1 core/var/queue/shunt 958 core/var/queue/virgin 0 what kind of tuning should we be looking into to speed up our boot-ups? -- Sr System and DevOps Engineer SoM IRT

7 years, 1 month

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 11/20/20 8:24 AM, Gordon Dickens wrote: > My mailman3 installation has now been up and running successfully for > several weeks without any issues and then the following error message > was emailed to me by my server. > What's up with this error message and what do I need to do? > Thanks, > Gordon > > -------- Forwarded Message -------- > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: > /mailman3/hyperkitty/api/mailman/archive > Date: Fri, 20 Nov 2020 01:25:41 -0000 > From: [1]root(a)host2.mailhub4u.com > To: [2]gordon(a)mailhub4u.com > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\xA4\\xA3\\xF0\\x9F...' for > column `mailman3web`.`hyperkitty_email`.`content` at row 1") '\xF0\x9F\xA4\xA3' is a utf-8 encoding for the emoji '🤣'. For MySQL and MariaDB, 4-byte encodings require the database allow utf8mb4. If your Django database settings use the mysql database engine as in ``` DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', ``` You need to add ``` 'OPTIONS': {'charset': 'utf8mb4'} ``` -- 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: Log rotation

by Abhilash Raj

On Tue, Apr 10, 2018, at 3:04 PM, Darren Smith wrote: > Hey everyone, > > So I have a question about log rotation... > > Our mailman.log has grown to over 5 gigs. It's time to add this to log > rotation. We added what we thought might work to the > /etc/logrotate.d/mailman script, but when we ran it with a -f, we learned > that the -f flag doesn't keep old logs. > > That in itself is fine - a normal scheduled log rotation won't have that > problem. > > My problem is that doing the rotation caused the mailman not to be able to > write to the log anymore. It appears that it no longer has a handle to the > file. You can send a SIGHUP to mailman's master process and it will reload all the log files. The PID of the master process is stored in "var/data/master.pid". > To overcome this with, say, nginx, there is a command in logrotate that you > can add that restarts the service. > > I have found, however, that restarting the mailman service can be VERY > problematic. There is so much going on that it takes a very long time to > stop, and I have seen several instances where the service never shuts down > cleanly - even after 3-4 minutes. The service thinks it is shut down, but > there are several threads that haven't yet completed. If they are killed, > then you have to go clean up the master.lck files etc. It seems like a bad > way of doing things and a good way to somehow corrupt data. Yes, this is a known thing and the reason for it is that the SIGTERM isn't delivered till the process wakes up next time. We can have the process sleep for a smaller amount of time to fix this, but then it would mean that it will be running much more often. It is the Retry runner, which has sleep_time set to 15m. I don't know if you want to retry very often, like 2min or 5min, but you can change it by adding the following snippet to your mailman.cfg [runner.retry] class: mailman.runners.retry.RetryRunner sleep_time: 5m > > Anyway - after rambling... > > 1) Has anyone come up with a good log rotation strategy that doesn't > necessitate a restart of the service? Manually SIGHUP the master runner is what I can think of the top of my head. A better solution would be to implement a "mailman logrotate" (or similar) command to do it, please free free to open an issue for it. > 2) Has anyone seen problems stopping and restarting the service? Is there a > way to help with this problem? Hope this is answered above. -- Abhilash Raj maxking(a)asynchronous.in

8 years

[MM3-users] Re: How to delete an archive

by Abhilash Raj

On Wed, Sep 4, 2019, at 6:06 PM, Andrew Bernard wrote: > I deleted a list but I want to delete the archive as well. > > How do you do that? I know this is a big pain point for many people, but this doesn't work right now on MySQL, which is why I haven't been able to commit my fix for this yet :( > > Also, I had a list called Test. I deleted it. I made a new list called > Testing, with a different email address, bu the archive points to the > test list. This seems to be messed up. Why? I am sorry to say I have > had continuous trouble with many aspects of Hyperkitty from the > beginning several months ago. I know that is not helpful, but I am > starting to wonder about all this. Deleting a list doesn't delete the archives. This the default behavior and perhaps the user interface can be improved by optionally allowing deletion of archives. I created: https://gitlab.com/mailman/postorius/issues/382 > > Andrew > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Turned on archiving and it is not working

by bob B

I normally have archives not enabled on all my lists and I do not even have hyperkitty enabled for them. but I need to turn on archiving for one list and it is not working. I made sure hyper kitty is enabled for the list, and I have private archives enabled. I even restarted my environment (more on that in a moment) and still the list works but nothing gets archived. my mail log shows Jun 09 18:49:10 2022 (28) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>The archiver key is now File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message <h1>Authorization Required</h1><p>The archiver key is now <h1>Authorization Required</h1><p>The archiver key is now I am running in docker: my HYPERKITTY_API_KEY is the same in my docker yaml file for mailman-core & mailman-web (I am using an external database) mailman info GNU Mailman 3.3.5 (Tom Sawyer) Python 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] Hyperkitty web interface is working and I can log in so it is up HyperKitty version 1.3.5. This used to work when I initially installed, so not sure why it is broken now. Any thoughts on what to do next?

3 years, 10 months

[MM3-users] Re: message duplication and an NNTP related error

by Mark Sapiro

On 2/27/26 07:17, Laurens Kils-Hütten wrote: > > So thanks a lot for clarifying. There's only one issue left I'm seeing > right now. Mailman does not rewrite the Newsgroups: header. Thus mua's > like Thunderbird which also talk NNTP offer to reply to the newsgroup > instead of to the list. Arguably this might be called a bug in > thunderbird, but I think it would be reasonable if mailman would change > "Newsgroups:" to "X-Newsgroups:" to avoid these kinds of pitfalls. Mailman has a couple of settings in the [nntp] section that control this. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…>. You can't use rewrite_duplicate_headers to do this because it onle rewrites the duplicates and not the original, but you can use remove_headers to remove the Newsgroups header. If you want to do this you could add ``` [nntp] remove_headers: nntp-posting-host nntp-posting-date x-trace x-complaints-to xref date-received posted posting-version relay-version received newsgroups ``` to your mailman.cfg to continue to remove the defaults and also remove the Newsgroups header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

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

by 朱超

At 2023-01-17 15:56:35, "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: >Mark Sapiro writes: > > > On 1/16/23 18:55, 朱超 wrote: > > > Hi, When I subscribe the email list in Subscription Policy is > > > confirm, Some problems happen in here： > > > 1.Some mail mua reject send the confirm the message, because the > > > length of recipient is too long. for exmaple: > > > requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, > > > and the mail mua reject to modify about this. > > > > The default English template says in part: > > > > Before you can start using GNU Mailman at this site, you must first > > confirm that this is your email address. You can do this by replying to > > this message. > > > > Or you should include the following line -- and only the following > > line -- in a message to $request_email: > > > > confirm $token > > > > I.e. It gives an alternative method if `reply` doesn't work. You can > > provide a custom version of this template with different wording if you > > think you can improve it. > >The problem is the reply address, though. Changing the template to >suggest only the "confirm $token" in body method doesn't help people >who hit R expecting that should work, especially since many "user >fiendly" (misspelling intentional) MUAs don't display the address. >Avoiding that requires code changes, I guess? Yes, You got it. It is too cumbersome to ask the user to write a reply email for email confirmation. > > > > 2.It is inconvenient for users to use. Many people will > > > mistakenly think that after clicking the subscribe button, it > > > will be successful, and they will not process the email. > > > step, you can set Subscription Policy to Open, but then anyone can > > maliciously subscribe third parties to the list. > >*Please* do not do this if your server is exposed to the Internet. >There are bots that search for such servers, and sell lists of them to >people who want to DOS mailboxes. You may find yourself banned across >the Internet. > Yes.For service security, we will not set the Subscription Policy to open >The only real alternative to confirmation is approval by moderators. >I believe Mailman 3 offers that alternative as Mailman 2 did, can't >check at the moment. > > > > Regarding the discussion on the subscription method of the > > > mailing list, should we consider optimizing the subscription > > > method of the mailing list, for example: > > > 1. use the method of sending a verification code to subscribe by > > > email，When you receive the verification code sent by the > > > mailing list and fill it in again, you can subscribe > > > successfully。 > > > > How is this different from the present method. > >Just wording. I think they are thinking of the "invite" option that >was provided in Mailman 2 mass subscribe (again, I think Mailman 3 >retains it but I never ever used it so I don't recall for sure). But >it doesn't make sense for a user-initiated interaction. > > > If you want, you can make > > a custom template and include something like: > > > > Alternatively, you can confirm by going to the URL > > > > https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token > >If I understand the OP's PoV correctly, I think I would change the >list information page to say "Send a personal invitation to join the >list to [email address here]. If you aren't a subscriber, you can >invite yourself." And change the word "confirm" in the confirmation >template to "subscribe". Why do you need to modify the mailman-core service， I suggest we should modify the code of the postorius, We can refer to postorius to reset the user password process， Detail, through the postorius to send email to user, and user click the url in email to confirm subscribe the email，Currently I have achieved it this way。 > > We don't include that in the default template because Mailman core > > doesn't know if you even have a web UI or how to access it if you > > do. > >We should fix that, at least if the web interface is Postorius >(wishlist, assigned to me): >https://gitlab.com/mailman/mailman/-/issues/1055 > >@mark >https://gitlab.com/mailman/mailman/-/issues/901 >Maybe we can close this? I'm not sure why it was left open since >there's no action proposed for Mailman improvement. > > > > 2. use the email to send a connection to confirm the > > > subscription，People click the link to be redirected to a > > > confirmation page to subscribe to the email。 > > > > See above. > >Indeed, AFAICS almost everything the OP is suggesting amounts to an >identical procedure as far as the Mailman server is concerned, it's >just described to the subscriber differently. The one exception is >the suggestion to eliminate the confirmation step, and while that is >supported, it's quite likely to cause problems for third parties and >eventually for the Mailman site unless you have an alternative ground >source of truth such as an employee database. > >Steve >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >This message sent to tom_toworld(a)163.com

3 years, 3 months

[MM3-users] Mailman 3 Installation

by bruce.dubbs＠gmail.com

I am trying to set up Mailman 3 on a new server. So far I have run: pip3 install Django==3.1.5 pip3 install postorius pip3 install Hyperkitty pip3 install mailman pip3 install uwsgi All that went well. I've been struggling with the configuration though. I am using /etc/mailman.cfg and that seems to be explained in the documentation OK. From there I am confused. I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? I think I can follow the instructions to set up postfix. In the section 'Configure Web Frontend', it discusses setting up the administrator. As I want to put Mailman on /srv/mailman I can create that, but what should the owner/permissions be? Later the docs discuss editing Django's settings.py. Where do I find that file? I'll note here that my experience with python is quite limited and my knowledge of Django is nil. Later in the section 'Set up HyperKitty', it sends me to a page that discusses installing it. I did that with pip3. Then it says to 'Setup your django project'. What django project is that. I would appreciate advice or a pointer to where I can figure this out. Thanks. -- Bruce

5 years, 3 months

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

by Mark Sapiro

On 9/16/21 2:39 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Hi all: > > I need to provide the list moderators a way to change the moderation > flag for users from whichever it is (normally "list default processing") > to "hold for moderation" and viceversa (to "list default" or to "accept") > > I understand that it could be done via console script (That's the way I > did on mailman2: I made two commands using "withlist", one to hold, > moderar.py, and other one to accept, desmoderar.py. I show you below) Are you asking what the equivalent MM 3 scripts would be? > But I think I'm not the only one that could use as an improvement a way > to do this on postorius/web. Postorius allows a list owner or site admin to set Moderation for list members and non members at e.g. https://www.example.com/mailman3/lists/list.example.com/members/(non)member/. Currently, a list moderator who is not an owner cannot do this, but a moderator can set Moderation for the sender of a held post when handling the post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Configuring ARC with multiple domains in Mailman3

by Stephen J. Turnbull

Lance A. Brown writes: > I found a ... a dedicated service which handles the ARC sealing. > It's working nicely! Great! That's a perfectly acceptable solution, and you have access to the ARC-Authentication-Results which can be checked in Mailman's "Header Filter" configuration section with Header | Pattern | Action ARC-Authentication-Results | authserv-id=$SERVICE.*(arc|dkim)=fail | Hold where $SERVICE is a token provided by your service, I definitely recommend holding and checking the message if ARC failed. There's no safe reason for that to happen that I know of. DKIM and especially DMARC do fail for various reasons, so you have to judge if there are too many false positives. You can remove the "|dkim" part or add additional protocols with "|spf" (for example) inside the parentheses. > I was even able to turn off the DMARC munging on my test list > without problems. Be careful about this in production. Monitor your bounces and the RBLs, this is the kind of change that warrants a period of heightened attention. There are free "pull" services for multiple RBLs that you have to check, and of course you can pay for "push" services that do the monitoring and notify you of events. Steve

1 year, 2 months

[MM3-users] Re: clearing pending db

by Morris Jones

On 8/8/25 11:48 AM, Mark Sapiro wrote: > On 8/8/25 09:59, Morris Jones wrote: >> >> But pendingdb.evict() doesn't seem to clear the list. For example, on >> one of my lists: >> >> >>> from mailman.interfaces.pending import IPendings >> >>> >> >>> from zope.component import getUtility >> >>> >> >>> pendingdb = getUtility(IPendings) >> >>> pendingdb.count() >> 5040 >> >>> pendingdb.evict() >> >>> pendingdb.count() >> 5040 >> >>> > > > pendingdb.evict() only deletes expired pendings, but by default > subscriptions pending confirmation expire after 3 days, but this is set > by pending_request_life in the [mailman] section of mailman.cfg. Have > you set that to a long time? > > On the other hand in Mailman 3.3.2, subscriptions pending approval were > pended with a 10 year lifetime. This was changed in 3.3.5 to a new > moderator_request_life setting (default 180 days). > > If you just want to delete all pendings you could do > ``` > pendingdb = getUtility(IPendings) > for pending in pendingdb: > pendingdb.confirm(pending[0], expunge=True) > # and if doing this in mailman shell > commit() > Perfect, thank you Mark. :) Mojo -- Morris Jones, Monrovia, CA

8 months, 3 weeks

[MM3-users] Re: Python 3.13 compatibility

by Mark Sapiro

On 3/29/26 7:57 PM, Thomas Krichel wrote: > Thomas Krichel writes > >> What now? > > Actually it looks I could do > > pip install -U mailman==3.3.9 postorius django-mailman3 hyperkitty mailman-web > > To get back to a working system > > But that still leaves me without 3.3.11 which I apparently need for my > import21. If you do that and it results in a working system, you can then patch mailman/utilities/i18n.py as follows --- a/src/mailman/utilities/i18n.py +++ b/src/mailman/utilities/i18n.py @@ -114,8 +114,7 @@ def search(resources, template_file, mlist=None, language=None): languages.append(language) languages.reverse() # The non-language qualified $template_dir paths in search order. - templates_dir = str(resources.enter_context( - files('mailman').joinpath('templates'))) + templates_dir = str(files('mailman').joinpath('templates')) paths = [templates_dir, os.path.join(config.TEMPLATE_DIR, 'site')] if mlist is not None: # Don't forget these are in REVERSE search order! However there are other incompatibilities between the released Mailman versions and Python 3.13. At the moment, until updated packages are released, in a Python 3.13 environment it is best to install all of mailman, django-mailman3, postorius, hyperkitty and mailman-web from the heads of the gitlab branches. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

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

by Barry Warsaw

On Sep 21, 2017, at 18:35, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote: >> On 09/21/2017 01:29 PM, Andrew Hodder wrote: >>> >>> I keep getting around this by creating symlinks to the pid file and then >>> the stop works, but it's getting silly. It seems like mailman just assumes >>> CWD + /var/ + master.pid must be the location. Once I realized this, I >>> found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since >>> it'd then add /var/master.pid). But that seems a little nonsensical. >> >> That is the normal expected behavior if devmode is enabled. Check your >> configs for this. > > I don't think `devmode` has anything to do with this, it only disables > sending out emails by accident and routes all emails to a pre-defined > address. Haven't looked at the relevant portion of the source so I might > be wrong. That’s correct. The [paths.*] sections are what control the file system layout, and [mailman]layout is what defines which of the [paths.*] sections to use. Cheers, -Barry

8 years, 7 months

[MM3-users] Re: Setting archive_policy "private" using REST changes web UI setting Archive policy, but does not hide archive until UI Save

by Mark Sapiro

On 8/14/24 01:15, Henrik Rasmussen wrote: > I am working on disabling a list removing all members using REST and then setting archive_policy to "private" also using REST. This changes the UI Archive policy setting to Private archives as I would expect, but I just discovered that the (now previous) member, still logged in, and alså public (not logged in), still have access to the archive. It is not browser cache. > > At the moment I click Save in the UI settings/archiving, both logged in user and not logged in user (other browser) changed to "This mailing list is private. You must be subscribed to view the archives." on page reload. > > It seems that i need to click Save on every list having been changed, before the archive is hidden. Is that a bug? The daily Django hyperkitty sync_mailman job will probably do it. Or, you can figure out what REST calls saving the settings in Postorius does and do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 4/28/22 13:09, bob B via Mailman-users wrote: > Mark, > Thanks for the Assistance but a little lost in the interpreter, and no luck googling. How do Iget back to the >>> prompt? > > I enter > > bash-5.0$ mailman shell -l maillistappha(a)XXXXX.org > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the maillistappha(a)XXXXX.org mailing list >>>> from mailman.app.moderator import handle_message >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... handle_message(m, req.id, Action.discard) > ... > ********* This is where I am stuck ********** I hit return it takes me to a new line with no characters? how do i get back up a level to the >>> prompt to enter commit() You wait until it finishes processing the 30K messages and then you'll get the >>> prompt. -- 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: list footer web customization procedure

by Mark Sapiro

On 12/10/21 3:45 PM, dancab(a)caltech.edu wrote: > Thanks Mark. We're using https:// for the URLs. Mailman 3.3.5 is what we're running. > > (mailmanve) mailman@14ea21f6d4b1:/var/www/mailman-www$ mailman conf |grep tasks > [mailman] run_tasks_every: 1h > > We're using two containers behind a load balancer for Mailman so I suspect this is where the lost cache comes into play. Yes. The cache entry is stored in the database which presumably is shared, but the actual cached data may only be stored in the file system of the server that cached it so the other server will think it's lost. Are you sharing Mailman's var/ directory between the two servers? I think you need to do that. > Would it be safe to increase the task frequency to every 15 minutes via the setting below? > > run_tasks_every: 15m I don't think that will do what you hope. It won't hurt, but the task runner only evicts expired entries, and they have a life set by cache_life in the [mailman] section of mailman.cfg (not to be confused with cache_lifetime set in the [dmarc] section) with a default of 7 days. -- 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: Managing mailman3 via curl (using bash-scripts or perl-scripts)

by Jeremy Stanley

On 2025-09-29 13:05:27 -0000 (-0000), Christian Schneider wrote: [...] >- list creation via command-line script with two/three parameters like: > ./create-list --listname myfirst.list(a)lists.example.org --admin-email admin-user(a)example.org [--admin-name "Peter Rabbit"] > >The create-list script itself should be a bash- or perl-script (I am not very familiar with python - SORRY ;-) ) >I would like the scripts to trigger some curl-calls on the mailman server >(from outside the mailman shell and even from outside the virtual environment) [...] We're creating lists using Ansible to make calls to Mailman's REST API, but it should be trivial to translate this example to any scripting language of your choice: https://opendev.org/opendev/system-config/src/commit/79fc523/playbooks/role… Hopefully that gets you on the right track, but if you do decide to delve into Python you'll have a lot more flexibility since the existing Mailman CLI is essentially a Python module. Note that "activating" a venv is typically not necessary (I never do it), you just have to make sure to type the full path to executables in the bin directory of the venv when running them, or add that directory to PATH in your shell environment. -- Jeremy Stanley

7 months

[MM3-users] Re: Dump/restore users (with passwords) via API Update

by Simon Hanna

Please note that for authentication the frontend keeps it's own database. So the used usernames/passwords are not available in core and need to be restored from the frontend's database. So to migrate a mailman3 instance you need to migrate the data stored in core _and_ the data stored in the frontend/django. It looks like you are doing fine with the core stuff. I would recommend using django's builtin methods to do the rest. You are looking for dumpdata/loaddata. https://docs.djangoproject.com/en/2.1/ref/django-admin/#dumpdata Note the warning about the permissions and content-type tables. https://docs.djangoproject.com/en/2.1/ref/django-admin/#cmdoption-dumpdata-… If you haven't changed anything in these tables (You probably haven't) You can safely ignore these tables using the --exclude option during dumping. A manual method to restore Users can be found inline in this reply. On 9/26/18 12:20 AM, Conrad Holmberg wrote: > Hello: > Just an update and review on a previous thread and some progress. > > I'm trying to write a Python script to do the following: > > - Dump all the members from a email list within mailman instance > A. This includes the display name, email, password hash, and all the > preferences. The output is a json file. > > - Then we read this json file and create the user, membership to > the email list, and the preferences into mailman instance B. > > The problem is that we are trying to insert the members with the > password hash and NOT a new plain text password. > > A simple json dump example: > > { > "password":"$6$rounds=656000$QhEAT7XCQ9tyUmJV$cj2xv3GKd8UXdSSasMZdqe0NjUL4T751nBEkdubog55jzIY1iZ5AQ4aRVeJIi1jnS1CKHHJn6nVnW.Hz91Xvk.", > > "list_fqdn": "helpme(a)confused.com", > "display_name": "Bob Nobody", > "email": "nobody(a)nowhere.com", > "preferences": { > "receive_list_copy": false, > "hide_address": false, > "preferred_language": "en", > "delivery_mode": "regular", > "receive_own_postings": true, > "acknowledge_posts": false, > "delivery_status": "enabled" > } > } > > > The code for this within the mailman client API is pretty straight > forward. However, the method for create_member will not work for our > situation because the argument requires the password to be in plain > text to be encrypted later. The rest of the tasks (subscribing, > preferences) can be done with the mailman client with this single > exception. > > Now my question is irf someone can send a single piece of code example > or where to look to accomplish this. > > I see two options: > > Using the mainman core. I believe the modified code would be > something like this: > > user_manager = getUtility(IUserManager) > #with transaction(): > new_user = user_manager.create_user( > 'nobody(a)where.com', 'Bob Nobody') > new_user.password = config.password_context.encrypt('abc123') > #replace with hash > new_user.password = '$6$rounds=656000$tS8sTX' > > > So the password is set with the hash instead of the encryption method. > > Original code: new_user.password = > config.password_context.encrypt('abc123') As mentioned in a previous thread, the password that is stored in core, isn't being used anywhere. So saving/restoring it is of no use. > > > The other possible method is through django. However, I'm not really > sure where to being on this on as I've been looking over the > django-mailman3 and this is the only example I can find in > test_delete_account.py: That is the correct password to save/restore. the create_user method takes a plaintext password and hashes it. So you would need to do something like this: user = User() user.username = 'username' user.email = 'email(a)example.com' user.password = 'password-hash' user.save() Setting the password like this bypasses the hashing, which is what you want. > > def setUp(self): > self.mm_user = Mock() > self.mm_user.user_id = "dummy" > self.mailman_client.get_user.side_effect = lambda e: self.mm_user > self.user = User.objects.create_user( > 'testuser', 'test(a)example.com', 'testPass', > first_name="firstname", last_name="lastname", > ) > > self.client.login(username='testuser', password='testPass') > > Again, it appears that the password is encrypted somewhere else before > encrypted. > > Any help on this is greatly appreciated. > > > Thanks > > Conrad > > > > _______________________________________________ > 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, 7 months

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

by Frank Richter

Hello, occasionally we face the problem "The content of this message was lost." when handling a message on hold. We use the mailman3 packages on Debian 12: 3.3.8-2~deb12u2 GNU Mailman 3.3.8 (Tom Sawyer) Python 3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0] with postgresql, exim and Apache httpd on the same machine. To get closer to this problem we made 2 changes: /usr/lib/python3/dist-packages/mailman/app/moderator.py def _lost_message(mlist, subject, sender, message_id): # Create a substitute for a message not found in the message store. text = _("""\ The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. """) + # Don’t send an empty message to all members in case this event occurs. + # raise an exception instead: + raise Exception("_lost_message",subject, sender, message_id) /usr/lib/python3/dist-packages/mailman/runners/task.py def _evict_pendings(self): … messages = getUtility(IMessageStore) for msg in messages.messages: # msg can be None if file is already removed. if msg is not None: mid = msg.get('message-id') if mid not in mids: messages.delete_message(mid) # 2024-12-11 fri: Debug inserted + tlog.debug('Task runner deleted message %s', mid) count += 1 tlog.info('Task runner deleted %d orphaned messages', count) So let’s see what happens: A message sent to one list is set on hold: exim mainlog: 2025-01-28 14:10:23 1tclMF-00H6cW-1s <= user(a)s2024.tu-chemnitz.de H=vittal.hrz.tu-chemnitz.de (mail.tu-chemnitz.de) [2001:638:911:b01:134:109:133:32] P=esmtps X=TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=no K S=9058 id=2f972b-6798d700-9f-5b841500@14907502 2025-01-28 14:10:23 1tclMF-00H6cW-1s => fsr-hsw(a)lists.tu-chemnitz.de R=lists_mailman T=mailman3_transport H=localhost [::1] C="250 Ok" 2025-01-28 14:10:23 1tclMF-00H6cW-1s Completed vette.log Jan 28 14:10:24 2025 (2602) HOLD: fsr-hsw(a)lists.tu-chemnitz.de post from user(a)s2024.tu-chemnitz.de held, message-id=<2f972b-6798d700-9f-5b841500@14907502>: The message is not from a list member A task runner deleted the message 5 seconds later: task.log Jan 28 14:10:29 2025 (2609) Task runner deleted message <2f972b-6798d700-9f-5b841500@14907502> Jan 28 14:10:29 2025 (2609) Task runner deleted 1 orphaned messages Later an owner/moderator want to do a moderation action: mailman.log: 2025-01-28 17:40:54 [FALCON] [ERROR] POST /3.1/lists/fsr-hsw(a)lists.tu-chemnitz.de/held/7544 => Traceback (most recent call last): File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 155, in on_post handle_message(self._mlist, request_id, **arguments) File "/usr/lib/python3/dist-packages/mailman/app/moderator.py", line 144, in handle_message msg = _lost_message(mlist, subject, sender, message_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/app/moderator.py", line 104, in _lost_message raise Exception("_lost_message",subject, sender, message_id) Exception: ('_lost_message', 'Re: [Fsr-hsw] ...', 'user(a)s2024.tu-chemnitz.de', '<2f972b-6798d700-9f-5b841500@14907502>') Do you have any suggestions what we can do to find the reason, why the task runner deletes the message? Or any other hints … Thanks and kind regards Frank -- Frank Richter, Chemnitz University of Technology, Germany

1 year, 3 months

[MM3-users] Re: Running customized version of Mailman 3

by tlhackque

On 28-Feb-20 16:46, Alan Kelm wrote: > Since 2005, our organization has been running a customized version of > Mailman 2 with extensions that meet our particular needs. The main > novelty is support for /fixed subscription lists/, in which the list > members are predetermined (corresponding to a "committee"). Fixed list > subscribers are not offered the opportunity to unsubscribe, nor can > others add themselves to the list. A further enhancement is /hybrid > lists/ which, for example, have both a fixed and opt-in part. (This is > implemented as a fixed list residing within an opt-in one in a way which > is transparent to users). Our customizations consist of code > adjustments (patches) to 23 files. > > We are considering moving to Mailman 3 and would like to do this in a > way which makes it possible to periodically upgrade our installation to > the newest Mailman version, without clobbering our customizations. > Thus, I do not think that installing via "pip" is the right approach for > us. While I'm relatively new to git and GitLab, they seem to be ideally > suited to this situation. If I understand the developer documentation > correctly, I start out by creating a "fork" and can later "fetch" > changes from the master branch and "rebase" to bring them into our branch. > > I would welcome comments on what we are doing. I also wonder whether > others might be interested in support for "fixed lists", if they are > done in a way which can be "contributed" back into Mailman. > > I extend our "thank you" to the developers of Mailman who have provided > the robust system which has served us well for 15 years and provides the > possibility to extend this into the future. > > -Alan > FWIW: When I had similar requirements (MM2), I found it most convenient to populate the "fixed" list with a distribution list name. The distribution list was sourced from an LDAP group. That allowed the distribution to be populated based on job title, reporting relationship, committee membership - whatever. On the Mailman side, it's only one member (the distribution list) that had special treatment. Opt-in would be moderator approval, as was unsubscribe. But the moderator only had to remember the one "can't unsubscribe" name. That, or a variant might work for you - and probably can be done modifying fewer files... In minimal form, if you don't want to rely on a human, it seems like the minimal implementation is a "can't unsubscribe" bit for users and an admin interface to set it. You could also cause that user to have a different "language" - e.g. en-ZZ; then adjust the templates for that "language" to remove references to "unsubscribe". That's not functionally necessary - but prettier.

6 years, 2 months

[MM3-users] Re: message duplication and an NNTP related error

by Stephen J. Turnbull

Laurens Kils-Hütten writes: > I understand mailman will send messages via NNTP. But how about the > other way round? Mailman will function as an NNTP client on behalf of a list in both directions. > What I'm trying is setting up INN so it sends messages for the list > to the respective list address. I would not do that. Asymmetric paths are usually headaches to deal with. For example, I seem to recall that there were news clients that had a "post and mail" operation. Mailman does not deduplicate across messages (the subscriber "no dups" setting is used to keep an explicitly addressed subscriber in To or CC from receiving both a direct mail copy and the list copy, not keeping Mailman from receiving and distributing the same message twice), so in that case without a custom rule to discard duplicate messages, Mailman might receive and distribute the exact same message twice, once received via NNTP and once via LMTP. > But could mailman also pull news from nntp? And is that what the > "News to Mail" flag is supposed to do? Yes and yes, Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months

[MM3-users] Re: How to get rid of footer (Mailman3)

by Mark Sapiro

On 2/11/20 11:31 PM, tarmokumar(a)gmail.com wrote: > Hi, I have read multiple posts in this forum that you should be able to get rid of the footer completely but I am unable to. > I have tried: > - adding the footer template to a list and not adding any "Data" to it. Result was a attachment with some "dfgdfgdfgdfg" text in it. Did you add this via Postorius. If so, it would seem to be a Postorius issue. > - adding/creating a blank "list:member:generic:footer" document to /var/templates/site/en, var/templates/lists/LIST.ID/en/ and var/templates/domains/DOMAIN/en/. Result is that the sent e-mail still has the original unsubscribe text in the footer (as an attachment) Did you name the file list:member:generic:footer.txt (with the .txt extension)? Putting a zero-length file of that name in any of those places should work. > - removing all the files from /mailman/src/mailman/templates/en, still no change If you restarted Mailman after doing this, this indicates something (Postorius?) may have set a URI for this template. What do you get from curl -urestadmin:restpass \ http://localhost:8001/3.1/lists/LIST.ID/uris -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Timeouts

by tlhackque

On 25-Apr-21 18:08, Mark Sapiro wrote: > On 4/25/21 2:20 PM, Andrew Hodgson wrote: >> Hi, >> >> Hyperkitty 1.3.4. >> >> I am trying to download a complete list mbox by going to all threads view >> and using the download option. I have tried a couple of tools (Gunzip and >> Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. >> >> Here is the list URL I am using: https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil… > Depending in the web server configuration, timeouts can occur when > downloading large archive mboxes. instead of downloading the entire mbox > with > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, > do it in pieces by adjusting start and end. e.g. > > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> > > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> > > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> > > > Although, I don't think timing out is the issue, and I'm not sure what > is, but I think it has something to do with messages in the archive. If > I try to get the 3 pieces as above, the first piece with > start=2008-02-19&end=2012-12-31 works but the others don't and even the > smaller > > <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> > > fails the same way. > > If I try to get 2013 month by month, all work except December which > gives me an internal server error. What's the traceback from that error. > The described timeouts are something that hyperkitty ought to be able to avoid. For apache, the timeout is idle time between blocks of output. Hyperkitty can avoid this by generating the archive in segments (based on size, or elapsed time), flushing its output buffer, generating a multi-file archive, and/or using Transfer-Encoding: chunked (chunked doesn't work for http/2). It ought to be able to break the work into blocks of "n" messages & do something to generate output. Besides avoiding timeouts, working in segments allows the GUI to display meaningful progress (e.g. if you're loading with XMLHttpRequest, "onprogress") It really oughtn't be up to the user to break up the request. Until then: the apache directive is "TimeOut" (or "ProxyTimeout"), with a default value of 60 (seconds). It's a server config/virtual host parameter, so if you're running in an environment where you only have .htaccess, you need admin help or you're out of luck. Other webservers (especially those with accelerators) may have more granular timeouts.

5 years

[MM3-users] Add domain to Mailman, can't create list with that new domain

by Andy Matthews

I'm testing locally to try and support additional domains. I can add new mailing lists with a domain: announce-123(a)mydomain.com I can't add a new mailing list with an alternate domain: announce-123(a)testing.com Following the documentation for domains I'm able to successfully add the new domain (locally) with the following steps: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… 1. Shell into the mailman server 2. Shell into the mailman Python environment: mailman shell 3. Add a new mailing list. from mailman.interfaces.domain import IDomainManager from zope.component import getUtility manager = getUtility(IDomainManager) manager.add('testing.com') show_domains() # with method from the above documentation URL <Domain testing.com> <Domain mydomain.com> But then when I run a cURL command (from the mailman server) to add a list with that new domain I get an error: $ curl -k -u restadmin:restpass -X POST -H "Content-Type: application/json" --data '{"fqdn_listname": "new-list(a)testing.com"}' https://0.0.0.0:8001/3.1/lists {"title": "400 Bad Request", "description": "Domain does not exist: testing.com"} Am I doing something wrong, or missing a step? If not, how do I add support for additional domains such that I can provide mailing list support for that domain?

1 year, 6 months

[MM3-users] Auto discard after max_days_to_hold not working.

by Stephen J. Turnbull

Hitashi mancho via Mailman-users writes: > I have migrated around 300 mailing lists from Mailman 2 to Mailman > 3. In most of the mailing lists we have configured > "max_days_to_hold" to 2. It was working fine in Mailman 2. However, > it is not working in Mailman 3. This doesn't seem to be exposed in Postorius. It's not all that old in Mailman 3 (April 2020) so it's possible that it is not moved from Mailman 2 to Mailman 3 by the migration scripts. You can use "mailman withlist" to access that variable: Use "mailman withlist -l LIST(a)DOMAIN.TLD", then at the prompt: >>> m.max_days_to_hold to examine the value for LIST(a)DOMAIN.TLD. To do a mass change, something like for ml in `mailman lists`; do mailman withlist -l $ml -r fix_mdth done where you put in Mailman's bin directory the file 'fix_mdth.py' containing def fix_mdth(ml): ml.max_days_to_hold = 2 commit() Of course if there are list where you want a longer or indefinite hold you'll need to change those back, since this approach changes all of them. You can get more information with "mailman withlist --detail". -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year

[MM3-users] Re: Finding all held messages

by Gerald Vogt

Hi, if you have access to the database you could check like this: SELECT _request.*,mailinglist.list_name,mailinglist.mail_host FROM _request LEFT JOIN mailinglist ON _request.mailing_list_id = mailinglist.id; -Gerald On 29.11.25 02:43, Peter Chubb via Mailman-users wrote: > > Hi Folks, > Is there a way from the Web UI to find all lists with held > messages? > > I'm site owner and admin for a domain; I'd like to see all the held > messages for all the lists in that domain, so I can gently > encourage moderators to do their jobs .. and to stand in when > they're away or otherwise cannot release held messages in a timely > manner. > > To do this I want to see all held messages, and the lists they are > meant for. Right now, to see which lists have held messages means > clicking on each list name n turn. which can take a long time, even > for the couple of dozen lists we have. > > Peter C > _______________________________________________ > 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 vogt(a)spamcop.net

5 months

[MM3-users] Re: Implementing threading [was: hyperkitty failed to create a thread]

by Stephen J. Turnbull

tlhackque writes: > No. It's not an address. "local part" has to do with an address. in a > Message-ID, It's syntactically a local-part or other stuff. RFC 5322: 4.5.4. Obsolete Identification Fields The obsolete "In-Reply-To:" and "References:" fields differ from the current syntax in that they allow phrase (words or quoted strings) to appear. The obsolete forms of the left and right sides of msg-id allow interspersed CFWS, making them syntactically identical to local-part and domain, respectively. > It's in "id-left", which is a supposed to be something generated by the > host that makes the message unique within the namespace defined by > "id-right". Right, those are the *semantics recommended to implementers*, for the reasons which you summarize accurately. But a validating parser doesn't care about that. > Treat the whole thing as an opaque string. Nothing else is safe. s/else// and I'll agree with you. But safety is not an issue in threading (except for DoS if the procedure might be non-terminating; I suppose you could argue DoS if a user misses an out-of-order mail from their boss and gets fired :-). > Yes, but did you fix the References header to match? Of course I did. :-) That was long before I was a Mailman developer and started reading the RFCs, also of course. > Yes, but you brought up the news RFCs, IIRC in saying that they defined > threading. Actually you brought up the news RFCs. I was wondering why. I guess it was to argue (implicitly) that there's a bug in the 2822 (and 5322) spec, and that 5537's solution tends to muck things up? > My quote was verbatim. 5537 does say you must trim. The point is that > the news rfcs may have introduced References, but they have different > obstacles to reconstructing threading. I don't think that's right, because mail suffers from the same line length restriction, with no exception for References. Mail just has strictly more specification bugs. :-( > I haven't looked at that. Given the trimming in 3.4.4 of 5337, I don't > see how this can be produce the whole thread, unless you are guaranteed > to have the complete thread to fill the gaps. It can't because you aren't. But it seems unlikely that anybody is producing msg-ids longer than 74 characters, so 998/(74+1) - 1 = 12 is a long enough gap that you probably don't care that they're the same thread. At least not in any forum I participate in! It's true that an MUA that doesn't produce either References or In-Reply-To will necessarily break threading, and that "enough" missing messages can do so. But both are pretty uncommon in my experience. Even AppleMail gets those right AFAICT. ;-) > Plus, you can lose messages for strange reasons: The moderator > deleted one for inappropriate content. A message was copied to the > list and the poster. The response to the list is lost. But a > reply from the poster happens later. So the response in question > is never seen by the server, though the reference is. Life is hard > :-) > Sure, but Jamie's algorithm *will get that right*. What remains is a UI question: missing message placeholder, to display or not to display? > Heuristics are fine. Guaranteeing that the resulting algorithm > terminates is important. But real life doesn't get you to "enough > messages" 100% of the time. 100% isn't necessary. If the thread is sufficiently broken that Jamie's msd-id-based procedure doesn't work, his full algorithm falls back to your idea of collecting the singletons by subject and sorting. (He doesn't specify the ordering criteria, rather what objects (= subthreads of the same parent) are to be compared. Your suggestion of date seems most appropriate for the leftovers.) > > > See my other post. The left and right halves can, besides being atoms, > > > be non-folding quotes or literals. So you have to handle that. > > > > Of course, but that's just a SMOP. The harder problem is figuring out > > what to do about non-conforming input. > And, as I've noted: lost input. Lost input does not prevent thread reconstruction as long as (1) all messages have a Message-ID, (2) "enough" messages have a non-empty References containing "enough" msg-ids, (3) those References do not misorder the msg-ids or introduce msg-ids corresponding to messages not in the thread. It should be obvious why I don't want to define "enough" (except in terms like "enough means Jamie's algorithm can reconstruct the thread" ;-), but in particular losing *one* message will certainly not prevent reconstruction. > When they don't, trying to guess at the semantics of an opaque ID will > seem to work for a while. But it amounts to the halting problem. There > are lots of variants of "generate a globally unique ID with an '@' in > the middle". I may have created a new one today :-) The problem I'm trying to address with the "stripping" is incorrect copying of msg-ids by MUAs that try to parse them, as we saw here. Apparently the bug was in Mailman itself, so it's not required, I guess. > Yes. But if they're well-formed, the <> are there, so stripping them > only saves a couple of bytes. > > If they're not, all bets are off. <two<three(a)example.net> - stripping > the outer <>s doesn't help. > > <"two<three"@example.net> is a valid message-Id, > and distinct from <"twothree"@example.net. Sure. Is it likely? > <twothree(a)example.net> distinct from <"twothree"@example.net>? > (unnecessary quoting, or a distinct message-ID) If you treat it as > opaque, you don't care. Take the whole thing, <@> included, as given > and look for it in the other fields. The most you might do is remove > quotes (and escapes) and use the left and right parts as your key. Which is basically what my stripping and cleaning procedure would do. The question is "does it help or hurt, on net?" If there was a widely distributed MUA out there that doubled the delimiters, it would help. Since it was Mailman doing that, it's a bad idea. > You could also fingerprint the user agent (e.g. by the order of headers, > format of message-ID), and correct for its bugs. But I'm inclined to > report client bugs and get them fixed. Meantime, their messages are > unthreaded (but not lost). It's just not worth working around other > people's bugs - there are better uses for your time. That's not my experience. See Reply-To munging. Depends on the bug, of course, but all too often people think it's our job to help them deal with bad MUA design. > Yes. A message ID should exist. These days I think all MTAs will assign > one if the client doesn't. > What I tried to say was that there will be times where you can't figure > out where to put a message into the thread graph (or forest). Because it > references message that you can't find, or it doesn't have a references > or reply-to, or those fields are corrupt. None of those prevent you from threading that message. The only reasons you won't be able to thread a message at all are when no other available message references it (eg, if several MUAs in a row supply In-Reply-To but not References, and the middle messages are missing or their identification fields are corrupt), and when there are References that have conflicting opinions on where that message belongs. Of course if a message lacks References and In-Reply-To it will be identified as a thread root (unless some descendent manually corrects References ;-). Even then it could be grafted into the tree more or less correctly using your sort on subject and date procedure. > These are heuristics - you might come up with better ones. Yours are already implemented in Pipermail, I believe, I'm not sure about HyperKitty. I don't think Jamie's algorithm messed with [name] and [serial number] because they weren't common at that time, but he stripped Re: and its nonconforming variants, as well as "Fwd:". > At least with an orphans bucket, you don't end up with "invisible" > messages. Nothing I suggested produces invisible messages, just a different set of orphans or occasionally a misthreaded message that seems to be a duplicate if different msg-ids are munged to the same string. At least not in Jamie's algorithm. I don't know exactly what algorithms are used in Pipermail and HyperKitty. Interesting discussion, but I've reached the point of diminishing returns. I will be checking to see if any of your suggestions are improvements over what HyperKitty currently does.

7 years, 2 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/7/21 11:27 PM, Marcus Granath wrote: > It seems like the version used is: Postorius Version 1.1.2 Current Postorius is 1.3.4. If you can't upgrade, someone with shell access to the server can do this with `mailman shell` > What I basically want to achieve is that my "sendmail" script (executed from linux) will send announce-mails to this mailing list - and will set an "pseudo-address" (not my own name and address) as sender of this e-mail, i.e "ABC Announcement <no-reply(a)abc.com>" - and to get this "pseudo-mail" to be one of the accepted users (together with me and some team mates with real addresses) to send on the list - one option I understood was to use the "non-member" user for this "ABC Announcement <no-reply(a)abc.com>". > > But in my web-interface (as described above), I cannot find where to add and manage such user (non-member). > Or can I use some other API (then the web-page) to do that kind of operation? ;-) Just add the no-reply(a)abc.com address as a member and set its delivery status to disabled. -- 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: Updating from Ubuntu-20.04 LTE installation

by Abhilash Raj

On Sat, May 23, 2020, at 8:28 PM, Mark Sapiro wrote: > On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > > > Our installation was done by "apt-get install" in Ubuntu 20, thus still > > running MM 3.2.2 (and python 3.8.2). > > > > Do you have any advise, how to upgrade from there to your current > > version? I know this might be a bit dangerous, but with today's VMs the > > risk is much less than it used to be: > > > It shouldn't be difficult, but I can't give you details because I don't > know exactly how the Debian/Ubuntu package installs things. Also I don't > know whether "current version" refers to the 3.3.1 release or the head > of the https://gitlab.com/mailman/mailman master branch. > > > > Do you think it would be possible, just to replace the code and library > > parts, keeping the database and config files as is? > > > Yes. It should be fairly straightforward. You first need to find where > the Mailman Core package is. You should be able to just replace the > contents of the `mailman` package directory with ours. You may be able > to do this via pip > > pip install --upgrade mailman > > globally or within Mailman's virtualenv if it is installed in a virtualenv. This is probably not a good idea, global install quite often breaks a lot of stuff (Like I broke Yum on my work computer since I wanted something newer than 10yo python packages). A better idea would be to install Mailman from scratch inside a virtualenv somewhere in /opt/mailman and then letting it consume the same configurations. I think Ubuntu/Debian have their configurations in `/etc/mailman3/` and Mailman Core installed anywhere should just pick that up without any special work. Same goes for Postorius/Django stuff. You can switch to a different Django project and just point to Debian/Ubuntu's settings.py (location of which should be in README.debian of the Debian package I presume). > However, there are caveats. There are Debian patches at > <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` > patch replaces importlib_resources with importlib.resources because > importlib_resources is not available in Debian. Most of the patches > apply to tests, and for the actual working code, we fixed this > differently as of Mailman 3.3.1, so I don't think you need the Debian > patches. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 11 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

That explains a lot. Is there any documentation you can provide to show me where I can set a static config/db? On Tue, Jul 31, 2018, 4:22 PM Mark Sapiro, <mark(a)msapiro.net> wrote: > On 07/31/2018 12:39 PM, Ryan McClung wrote: > > I do see the output of the script and it shows the mailing lists being > > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > > > Also, to that end, the output of lists changes depending on which > directory > > I am in which makes 0 sense. > > > That is the problem. Either your mailman.cfg does not specify a fixed > directory for var_dir or the mailman command(s) you run do not specify a > fixed mailman.cfg. > > If you look, you will probably see a var/ directory is every directory > in which you ran a 'mailman' command and they will all have different > databases, etc. > > -- > 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/ >

7 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hi Abhilash, I started to setup Postfix (I don't know if that is the suggested and easy to use mail server) doing the steps on the website http://docs.mailman3.org/en/latest/config-core.html which tells: Postfix <http://www.postfix.org/>: To setup Postfix, add the following configuration to master.cf: # Support the default VERP delimiter.recipient_delimiter = +unknown_local_recipient_reject_code = 550owner_request_special = notransport_maps = hash:/path-to-mailman/var/data/postfix_lmtplocal_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtprelay_domains = hash:/path-to-mailman/var/data/postfix_domains I added that config at the bottom of the master.cf file and did a 'postfix reload' and I got this error message: [root@localhost ~]# postfix reload /usr/sbin/postconf: fatal: file /etc/postfix/master.cf: line 129: bad field count postfix/postfix-script: fatal: cannot execute /usr/sbin/postconf! What do you suggest??? Thank you El jue., 20 jul. 2017 a las 14:09, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > Hi Rafael, > > On Wed, Jul 19, 2017, at 01:49 PM, Rafael Mora wrote: > > Hello, > > > > What are the suggested steps in order to install the web UI ?? > > I haven't read through this entire thread but I understand that you are > having problems with multiple configuration files for Core and setting > up the Web UI. > > The installation guide at docs.mailman3.org should now have a > "Pre-Installation Guide" and another new section called "Configuring > Mailman 3". Please make sure than you read both of them along with the > "Installation Guide" They have more information about how to setup > Mailman 3 after you have installed them so that it becomes function. > > Also, your original question's answer can be found there. It has > instructions about how to setup your Django project, which is the what > the Web frontend for Mailman 3 is based on. > > > > > Thanks > > > > 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 > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: I don't get my posts with Gmail

by Stephen J. Turnbull

Allan Hansen writes: > I was pleased to see the advice below on how to get your own list > messages sent from a Google client, as my subscribers complain > about their messages going AWOL all the time. > Do those messages really show up in the spam folder without this > filter? (I don’t use Gmail). No. They don't show up *at all*. GMail puts a copy of the sent mail in the sent folder, not in the INBOX. Because it has not left the MUA, it has no trace header fields at all, only the fields required by RFC 822 plus any fields the user has populated. This makes it completely useless for debugging mail problems. It then discards the post returned from the mailing list. > If so, then the server is, indeed, sending the message to the mail > client, I'm not sure what you mean by the server. If you mean the Mailman list, yes, it is sending the message in the case in point. > and the mail client is doing the message ID linking locally, > discarding the incoming duplicate. "Mail client" is ambiguous here. There are a large number of roles involved, any of which may be implemented as a separate program (and the user is always a separate program ;-). 1. User == you. 2. Message user agent (MUA), which fetches messages from a message store (file, maildir, POP server, IMAP server), displays it to the user, and provides commands for the user to manipulate the message in various ways. 3. Message store, which keeps a database of messages received from the message delivery agent. 4. Message delivery agent (MDA), which accepts messages from the message transfer agent, and delivers them to applications such as message stores. 5. Message transfer agent (MTA), which accepts messages from the Internet, and delivers them to the MDA. Duplicate handling (which is a special case of filtering) can be implemented in any of those roles, but we can assume the user is not doing it. If she were, we'd just tell her to stop. > Would a change in mail client solve that? No, the issue is that users want to use a particular client, Gmail. Even if they're willing to change: > If so, then problem solved by a work-around. > If not, then how can the filter above work? If user-defined filters are implemented in the same program as deduplication, then they're just alternative targets for delivery, where deduplication uses the target /dev/null. If the user says "send those messages to a particular folder," that should override the program's defaults. What seems possible here is that Google implements message filters in the message store, and deduplication in the MDA. In that case the filter can't work. But you'd have to ask Google to be sure. Steve

5 years, 6 months

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 9:29 AM, Simon Hanna <simon.hanna(a)serve-me.info> wrote: > On 03/31/2017 08:10 AM, David Krantz wrote: >> I think that would correspond to this line in urls.py >> >> url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), > Yes, that's the culprit. Replace it with the following: > > url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), > You can also update whatever guide you were using... Great, will try that! I don't know whether I can update the guide. It's the one referenced earlier in this thread named something like setup experience of mailman 3 in production. >> Then I of course have things to do on getting social logins to work. I >> currently get "DoesNotExist: SocialApp matching query does not exist." >> if trying to connect an account to google (which I started with). Not >> a showstopper as passwords do work. > Did you follow django-allauth's guide on setting them up? No, I haven't found that yet, I just followed the config examples as those seemed reasonable (although my knowledge of Django is quite limited so I am not a good judge of that of course). Will try that as well. Any particular known to work nice with the django setup used for mailman applications? // David

9 years

[MM3-users] Re: clicking on a username when viewing a thread results in "Page not found"

by Mark Sapiro

On 6/26/23 9:26 PM, Ken Alker wrote: > Mark Sapiro wrote: >> This is a problem. That link goes to, e.g., >> https://example.com/archives/users/<user_id>/. What do you get if you >> strip the user_id and just go to what >> https://example.com/archives/users/ translates to on your system? >> You should get a page saying >> Not implemented >> >> This feature has not been implemented yet, sorry. >> >> If you get a 404, there is an issue with your web server configuration >> or maybe your top level urls.py. > > I get "Not implemented". I do not get a 404 error. That indicates there is some corruption somewhere. I need to research it to figure out where, but the issue is the <user_id> in https://example.com/archives/users/<user_id>/ doesn't exist. Are the crons - https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m… running? If they are, the hyperkitty sync_mailman job should run daily and might fix this. You can also run `mailman_web mailman_sync` manually. -- 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: configuring postfix local recipient table

by Mark Sapiro

On 4/23/25 9:25 AM, Stephen J. Turnbull wrote: > Alexander Inzinger-Zrock via Mailman-users writes: > > and then i just found out that my postfix_lmpt file was empty > > 1. What database are you using?[1] Is it running? If not, yes, that > file is going to be empty. > 2. Do you have any lists configured for your Mailman 3 instance? If > not, that file will be empty. > 3. Is Mailman running? (This probably isn't necessary, just > checking.) > 4. Is there a postfix_lmtp.db file in the same place? (Postfix will > not read the plaintext version, it must be a .db file.) If you haven't set `incoming` in the `mta` section of mailman.cfg to other than the default `mailman.mta.postfix.LMTP`, the `mailman aliases` command will at least write ``` # AUTOMATICALLY GENERATED BY MAILMAN ON {} # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. ``` to the postfix_lmtp file. -- 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: Join a Mailman 3 list?

by Mark Sapiro

On 6/8/25 20:18, Cathryn McGuire wrote: > Hi Mark, Stephen & Thomas, > > We've successfully merged our Mailman 2 list into Mailman 3. EMWD worked over the weekend to get it done for our members. We're pretty grateful. > > There are a few things we're trying to get our heads around, specifically to do with the Affinity Web UI. Most of it is pretty self explanatory, and I can see where it will be more aesthetically pleasing to manage, but a few things that aren't so intuitive. Affinity is a proprietary product of EMWD. At one point during the development of Affinity, when Brian C was still alive, I had access to a demo version, but no more. I don't know if there are any EMWD Mailman 3 users on this list, but I suspect your best resource for Affinity questions is EMWD. > Is anyone working with Mailman 3 and Affinity that could help us through the set up? For instance, when I log in as owner and go to change my password, it won't take a new one and asks me (with a pull down menu box) which account I want to change the password for, and it gives me a list of my emails, and also the other owner's email address. When I choose the email I'm logged in under, it says it's not the correct "credentials." > > Has anyone had this issue? Have you actually created an Affinity login? I believe initially, you have to sign up before you can sign in, even if you are the listowner. > Another thing is, and Stephen J. Turnbull prepared us for this, that the transferred membership are all "enabled" but not "registered." I understand we have to send a membership wide notification with a link to the Affinity log in page, and instructions going to the top right hand and clicking on the login icon, putting in their email address (the one in the system) and adding a password OR do they have to "create" a new sign in? If it works like our web UI, they have to create a new sign in. You do too. The process that imports a Mailman 2.1 list to a Mailman 3 list does not create web UI logins. > Thanks for any info you can give us about Affinity. (I see Brian Carpenter was beta testing it 4 years ago.) Cheers, Cathryn I was one of the people working with Brian back then to try out and give feedback on Affinity, but I've probably forgotten all I knew at that time. There may be current EMWD/Affinity users on this list, but as I said, your best support resource is probably EMWD. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

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

by jonathan.mailing.lists＠gmail.com

Andreas Barth wrote: > I need to add custom attributes to the mailing lists: > "responsible department": Free text field who is responsible from an > organisational pov (not a person but an entity) > ... > Any hints how to do that best? Is it possible to store custom > attributes, or should that be stored elsewhere? It's possible to do something similar with Mailman 2 - see "Bob's Unofficial Mailman Tricks & Tips" at http://nleaudio.com/bnotes/mailman.htm - I've been using it for years. In my case it's like the Systers subscription page that Steve mentioned - something to help me decide whether to accept the subscription request, rather than something that I need to store in a database. When I looked at Mailman 3 last year I made a short custom subscription form which included a custom field, and a script to email it to me then send an email to the listname-subscribe email address. (I think I must have edited the MM3 confirmation link too because I've found a script that takes URL parameters, and sends a confirmation email to an address created from listname-confirm+ and the relevant token. I can't remember whether that was linked to having the custom field script.) Best wishes Jonathan

4 years, 11 months

[MM3-users] Re: Docker or virtualenv?

by Andrew Hodgson

Tim Cutts <tim(a)thecutts.org> wrote: >I’ve used docker on my setup. I have been wondering about this though, it causes me to need to run an AWS VM continuously to run my mailing lists, and that probably isn’t really necessary. I do sometimes wonder whether docker might be a better approach and run it under ECS, so I no longer have to >look after a VM. >Even better, MM3 is just a bunch of python functions at the end of the day, and it doesn’t *need* to be running continuously. Mailing lists are, more or less by definition, event driven. Has anyone considered whether it’s feasible to turn it into a bunch of Lambda functions with a serverless database behind >it? I actually moved from Docker to Virtualenv on my machine as I wanted to use the same larger VM to run a Cloudron instance which takes over Docker. Overall I have been more happier with the virtualenv approach as it allows me to customise the install more easier. I did look at running Mailman using Azure Container instances. The main thing here is we need to get the MTA integrated, and the MTA needs to send out emails from a static IP address with reverse DNS etc setup. This isn't easy to do on anything other than a VM. Thanks. Andrew.

3 years, 3 months

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by justfixit＠marilynstrother.com

Very interestng! Upon restarting the system (down momentarily for taking a snapshot) and starting Mailman again, all of these missing [List] messages emerged from their timewarp and were delivered to the members / subscribers. Just before shutting down the system I discovered that the apache2 webserver had been off the air due to a module not being enabled yet. As of yet, I was unaware of any requirement for a web server to be online (beyond possibly gunicorn) in order for Mailman to run its lists. Does that speculation have a factual basis? Or do I risk starting a vicious rumor amongst the impatient readers who are not still here once we deduce this pair of observations were merely correlated in time, with no cause-and-effect relationship? Before this situation healed itself, the thought had crossed my mind to peek and see if anything was stuck in the queues: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… While that could have provided peace of mind that email messages were merely delayed instead of vanished, even in hindsight I do not see how that would have led to repairing the situation. In the absence of a hypothetical command: mailman status --verbose about which diagnostic tools or clues should I learn?

2 years, 10 months

[MM3-users] Re: Loops back to myself

by Stephen J. Turnbull

simonjwiles(a)gmail.com writes: > Grateful for any insight you can offer! Thanks! Have you asked Postfix channels? I don't think this is a Mailman problem, and they would recognize the issue faster than we do. The first thing I would do is grep /path/to/mailman/var/data/postfix_lmtp for the looping address. If it's not in there, then Mailman is not involved in the loop. I'm pretty sure that what's happening is the domain is recognized because it's in relay_domains, the transport maps are consulted, the address lookup fails, the transport defaults to relay_transport, which defaults to relay, which is in fact smptd, which recognizes a loop because the source and next-hop are both self. Voila! From the ADDRESS_CLASS_README: Valid recipient addresses for [relay_domains] are listed with the relay_recipient_maps parameter. The Postfix SMTP server rejects invalid recipients with "User unknown in relay recipient table". If this parameter value is empty, the Postfix SMTP server accepts all recipients for domains listed with the relay_domains parameter. [Ie, you're an MX for those domains.] I guess relay_recipient_maps = hash:/path/to/mailman/var/data/postfix_lmtp will fix this problem assuming the error message above is acceptable. I can't guarantee it won't cause other problems, though, depending on whether your host provides other services to those domains. Steve

2 years, 3 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.***/settings/message_acceptance MultipleObjectsReturned .. get() returned more than one EmailAddress -- it returned 2!

by Marco Emilio Poleggi

Thanks, Mark. On 2025-09-01 19:40, Mark Sapiro wrote: > On 9/1/25 08:17, ^m'e via Mailman-users wrote: >> >> The same problem appeared today with my mariadb-based installation. @Mark, >> do you have a mysql version of your scripts? > > I'm not certain as I don't offhand have a way to test, but I think > > g/psycopg2/s//pymysql/ > > (i.e. just replace both occurrences of `psycopg2` with `pymysql`) will do it. > Yeah, it works! In my case, no uppercase addresses were found by the UC_fix script, whereas the Mult_primary did spot two accounts, both with 'staff status' in Django admin UI and with the same set of extra addresses. Most probably my fault, as I intended to use both accounts for administrative tasks and played to far with assigning the same sets of addresses, one of which was primary for one account. I guess that was causing the failure, right? -- ^m'e ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pgp-keys Name: OpenPGP_0xC366FCF67CDBD9F9.asc

7 months, 4 weeks

[MM3-users] Re: how do I bulk-remove users from ML in MM3?

by tlhackque

On 25-Oct-17 12:05, Simon Hanna wrote: > Postorius is currently using this to mass unsubscribe. > AFAIK there is an open issue in core to add such functionality Yes, see https://gitlab.com/mailman/mailman/issues/419 Yes, the current API has a number of scaling issues. Delete is bad, but other operations can require multiple API calls... (e.g. get state to conditionally create; create+patch; create user+create subscription, ...) https://gitlab.com/mailman/mailman/issues/367 (and others) Mass modify is also missing - https://gitlab.com/mailman/mailman/issues/241 notes one such case. > On October 25, 2017 5:59:46 PM GMT+02:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >> On 10/25/2017 07:35 AM, Barry Warsaw wrote: >>> On Oct 25, 2017, at 03:08, Dmitry Makovey <dmakovey(a)stanford.edu> >> wrote: >>>> I just realized that "mailman members" only offers to "add members" >> via >>>> "-a filename" but I see no remove option. >>> It’s true, `mailman members` doesn’t currently have a —remove option. >> I found Rest API call for single user removal but I am questioning it's >> effectiveness given that I need to use this operation to potentially >> remove 1500 members >> >> -- >> Sr System and DevOps Engineer SoM IRT

8 years, 6 months

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Mark Sapiro

On 6/16/23 22:14, Stephen J. Turnbull wrote: > > @Mark > I've been seeing an unusual number of disabled subscriptions on > python.org and mailman3.org lists recently. Maybe we should look into > this. If you haven't seen this O365 breakage, I can send you some > samples. I haven't noticed this. I do receive notices when delivery is disabled, and I generally look at the attached DSN, and I don't recall any that have this issue. We do have an issue with mailman-users(a)mailman3.org messages for five users in the outlook.com, msn.com and hotmail.es domains. These are all since the server was moved last month and are all for the reason 550 5.7.1 Unfortunately, messages from [165.227.190.41] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3140). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [VI1EUR05FT020.eop-eur05.prod.protection.outlook.com 2023-06-17T05:14:54.401Z 08DB6E025E06C828] with differences only in the bracketed part at the end. The same five addresses keep getting disabled because I keep re-enabling them, and I have contacted Microsoft about this, so far with no results. -- 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: How to identify the exact reason behind the shunting of the mails ?

by Mark Sapiro

On 6/18/21 6:48 AM, Shashikanth Komandoor wrote: > Dear Mark, > > FYI, I observed this issue with the postfix that receives the > mails from the previous MTA and hands it over to the mailman. But I fixed > at postfix by upgrading it to the version postfix 3. > > But still Mailman is not able to understand Hindi (Indian local > language) in which language the display names of the email ids are there. > > So, now what to do at Mailman so that it can also understand > local languages or any work around or other alternate solutions for these > sort of cases. As noted in my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… the issue is a Mailman bug which is fixed in the next release. It has to do with the fact that the display names are RFC 2047 encoded and not the particular encoding. Actually, the fix at https://gitlab.com/mailman/mailman/-/merge_requests/841 depends on https://gitlab.com/mailman/mailman/-/merge_requests/652 which was released in Mailman 3.3.2. A complete patch for versions < 3.3.2 is attached. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: One-click unsubscribe?

by Stephen J. Turnbull

Jered Floyd writes: > Ugh, I had not considered that RFC 8058 breaks the separation of > concerns here. Not your job, but it is ours. :-) > we can at least make this work for Postorius users. Definitely, that's a reasonable first step. We just need to make sure to do that while allowing others to opt out until they've implemented it themselves. I think I have a suggestion how it could just work for everybody, though. > Are there many who use just Mailman-Core and not the full suite? I don't know about absolute numbers, but yeah, it's a FAQ. There's the EMWD Affinity application which replaces Postorius for many of the sites they host, and enterprises often ask how to use bespoke scripts to control lists (although they may be using Postorius as well). > The URI path/query is defined as opaque. It probably should be > something like list-name/subscribed-address plus a signed hash to > avoid unsub-attacks. That means this likely will be a new web > application endpoint (although it may be possible to overload the > existing "unsubscribe" endpoint -- I haven't looked at the code > yet). RFC 8058 says The URI SHOULD include an opaque identifier or another hard-to-forge component in addition to, or instead of, the plaintext names of the list and the subscriber. The server handling the unsubscription SHOULD verify that the opaque or hard-to-forge component is valid. We don't need to have an explicit reference to the subscription in the URI. As I discovered (to my chagrin) Mailman's current simple RFC 2369 List-Unsubscribe field doesn't, even for personalized lists where there might be a personalized link in the footer. So I think we should go with "instead of". Maybe while experimenting it would be useful to have the plain text subscription information in the URI, though. So ... the existing REST endpoint in core won't change, because the whole REST API assumes that it's talking to the superuser. The "obvious" way to do this is through Postorius, which provides a proxy object backed by a map in Mailman core from tokens in the URL to subscriptions, and use the existing REST endpoint. This is "obvious" because Django already provides an authorization framework for subscription management -- we wouldn't be exposing anything else protected by that framework to mischief. The token would be the encrypted (list, address) pair, possibly dated in clear (to allow expiration of tokens and rotation of encryption keys). Unfortunately RFC 8058 doesn't discuss that, I guess John assumed that people would usually be unsubscribing from the most recent post. On the assumption that unsubscribes would be "rare", you wouldn't have to store the token in the database. (Have to think about that, you might be able to DOS attack by sending lots of fake unsubscribes and attack the encryption with known plaintext attacks. Safety would suggest adding a random nonce and that would need to be saved in the database.) Alternatively, you could reverse proxy this directly through the front-end webserver to Mailman core with a new REST endpoint. That gives me bad vibes because I can just see naive admins messing up the configuration of the single endpoint, and "fixing" the problem by reverse proxying port 8001 to the Internet. We'd have to be careful that the urlconf not slop over to anything else, maybe something like "listen" on the Internet at (nginx notation): location /mailman3/rfc8058/ { proxy_pass http://localhost:8001/3.2/PROXIED/rfc8058; } The "PROXIED" part is just to provide a REST namespace that is obviously separate from the domains, addresses, users, lists, etc. Maybe "SELF_AUTHORIZING" would be more accurate. I think that reverse proxy sepcification would be safe enough. And you could combine the two strategies which would allow sites that don't use Postorius to configure the reverse proxy, while sites that do would get it for "free" since we'd configure Postorius to do it. Aside: RFC 8058 says But anti-spam software often fetches all resources in mail header fields automatically, without any action by the user, and there is no mechanical way for a sender to tell whether a request was made automatically by anti-spam software or manually requested by a user. Weirdly, the RFC doesn't address this problem at all. :-( -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 3 weeks

[MM3-users] Re: Hacking attempts?

by Stephen J. Turnbull

Lists via Mailman-users writes: > No, we’re nothing to do with Fedora, we just run a few low volume > mailing lists for our members. I would disable the fedora auth application as described in my previous mail, then. I wouldn't worry too much about the possibility that there are users of the feature, if there are people with Fedora accounts, they are sophisticated users who know how to request it be reenabled. > Happy to send you example error emails, I received 1,987 in the > past 24 hours. They seem to come in waves, it’s particularly bad > right now, but it will die off to a lower level for a while, then > hit a peak again in a week or so. This is how it would behave if web crawlers are the problem. Do you have a robots.txt file? If so, is your Django site protected? https://developers.google.com/search/docs/advanced/robots/intro https://robotstxt.org/ Note that if you decide to adopt Tim's suggestion of fail2ban, you probably need a robots.txt file, if there's *anything* on your site that you want indexed, you don't want the crawlers banned. > Let me know how many examples you want and I will send them direct > to your email. OK, but first let's try the low hanging fruit. Steve

3 years, 9 months

[MM3-users] Re: Deleting A List

by Odhiambo Washington

On Fri, May 3, 2024 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > Mark Sapiro wrote: > > > update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; > > update hyperkitty_mailinglist_owners set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = > 13; > > delete from hyperkitty_mailinglist where id = 13; > > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > > 'list.lists.nog.ke' where id = 2; > > Or instead of that you could just go to the new list(a)lists.nog.ke > archive in HyperKitty and delete it and then just do the > ``` > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > 'list.lists.nog.ke' where id = 2; > ``` > I went with this approach and worked super! Thank you. So, seeing as deleting a list retains its archives, if I want to delete a list together with its archives, do I first delete the archives, then follow with the list? -- 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, 11 months

[MM3-users] Re: bulk deletion of messages from Hyperkitty

by Ron

On 2024-07-10 12:05, Danil Smirnov via Mailman-users wrote: > After importing from Mailman 2, thousands of badly compiled messages > from the past appeared with empty content on the same date (date of > import). > > Is there a safe way to delete them all? If we delete them from the > database - hyperkitty_email table - do we need to do some clean-up > of hyperkitty_thread table as well? Per https://docs.mailman3.org/en/latest/migration.html, there's a tool with mailman2 that can clean messages *prior* to import: > all mailboxes should be checked for defects before importing. Certain > defects such as missing Message-ID: headers or missing or unparseable > Date: headers will be corrected or ignored by the import process. The > one defect that will definitely cause problems is lines beginning > with From in message bodies. These will be seen as the start of a new > message. There is a Mailman 2 script at $prefix/bin/cleanarch. I'd try deleting the corrupt list, running `cleanarch` on the old list, and re-importing. If the new list has messages that are not in the old list (i.e. it's in live production), then I'm not sure of how to proceed. Note the linked page also mentions a tool called check_hk_import script in hyperkitty/contrib folder.

1 year, 9 months

[MM3-users] Digest Formatting

by Stephen J. Turnbull

mailman(a)manygoodideas.com writes: > I'm wondering how other admins have customized their digests to > make them more useful. It sounds like you have the digest format set to "plain". If you set it to "MIME", many email clients will format the display in such a way that you can click on individual messages. This is also possible with the plain format, but in my experience fewer clients implement that, because it's more fragile and painstaking to do. That might help. In general, this problem is really hard to address because the capabilities of clients vary so greatly. Perhaps your subscribers would be better off with single-message mode rather than digest mode. I'm not really clear on why anybody subscribes in digest mode any more. Digests still make sense for individual collections of messages, eg, "Your Honor, here are all the emails in which the defendent libeled my client." But for an ongoing stream such as a mailing list, I would think you would be much better off to receive the individual messages and let your modern client do its own thing with grouping threads and folders, and threading and ordering posts. Obviously, people like their own ways of doing things, but that suggestion might be useful for some of your subscribers. I hate to ask you to ask your subscribers to learn how to use their clients, as that frequently doesn't go over well, and they'll probably ask you to teach them with a client you've never used yourself :-/. However, if that's an option, most email clients provide a way to "burst" the digest into individual messages, which will then be threaded in the normal way for that client. This provides the user with the "download all the recent messages periodically" benefits of the digest, as well as the threading capability of the client. Also, a *good* email client will provide a way to view a digest "as a folder", without bursting it into individual messages. The latter is closest to what your users want, I think. (I still think that for most of them switching to regular mode is best.) > Yahoo! Groups used to send out HTML digests that had the thread > titles nicely distinguished, live links to the thread, and links to > Reply to sender, Reply to All, etc. Dealing with HTML email requires the resources of a billion-dollar company, unfortunately. It's a real mess. (For us old-timers, our favorite Mailman options are "strip HTML parts" and "convert HTML to plain text." ;-) For a small organization like Mailman, it's a "throw up your hands in distress" size problem. On the other hand, if you use a MIME-format digest, it's quite easy (but unfortunately not universal) for the client to implement that formatting itself. So that's the route we had to take. Hope this helps. If it inspires more questions, please ask! Steve

5 years, 5 months

[MM3-users] eccentric setup question

by Jeff Berry

Good morning all, we've got a somewhat eccentric setup for our mailman installation, and we're having difficulty getting some of the settings to work properly, so I'm hoping some one has some insight. Our server machine is hidden behind our firewall, with the actual machine name not availble via external DNS) and all the mail is being routed through an Exchange server. So mail to list(a)domain.com hits our exchange server, which sends it on to lists(a)listserver.domain.com The problem we're having is that if the mailman domain of the list is listserver.domain.com then spamfilters start to flag the mail since it looks like spoofing/malformed headers and so on. If the mailman domain is just domain.com then postfix rejects it with an unknown local recipient error. I though I might be able to just tweak the incoming mail headers in postfix via header_checks but that's not working, either because I've got the wrong check or it's the wrong approach, or both. postfix relay_domains might do it, I think, but if it maps listserver.domain.com to domain.com that would break the listserver domain mailing lists (I think). Is there a canonical way to do this and/or have I missed some obvious configuration option in either mailman or postfix? Kind regards, Jeff Berry jeff.berry(a)mrc-cbu.cam.ac.uk

3 years, 1 month

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

by Odhiambo Washington

On Mon, Nov 20, 2023 at 8:53 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/20/23 00:58, Odhiambo Washington wrote: > > > > What is the command to export the archive as a mbox from the DB? > > I can't figure out which option it is by looking at 'mailman-web -h'. > > Normally you do this on the old server via the HyperKitty web UI which > has download buttons which do things like > > > https://example.com/archives/list/list@example.com/export/list@example.com.… > > or for a partial archive > > > https://example.com/archives/list/list@example.com/export/list@example.com-… > > However, in your case I don't think you have the old installation working > any more so the above won't help. > I had a dump of the old installation actually - both databases. The above has actually helped and I obtained the archive. > > BTW, how will ' mailman addmembers' treat a file containing: > > ``` > > Firstname Lastname <email@address> > > Onlyname <email2@address> > > ``` > > Correctly. It will import email@address with display name = 'Firstname > Lastname' and email2@address with display name = 'Onlyname'. > Super! > > I have opted for the simple way to do this: > > 1. Create the site in Django Admin and create/configure the list in > > Postorius > > 2. Add the members from the file dump, with delivery set to regular. > > 3. Send the members an email informing them that they need to set their > > delivery preferences. > > > > I am stuck on the issue of exporting the archives to mbox file as already > > stated above. > > Perhaps you can export the mbox via the web UI on the old server or > maybe temporarily create a second mailman-web on your server with the > old mailman-web database and use that web UI. That's exactly how I did it and got the archives. > Otherwise, if you have a working mailman-web that can access this > database, you could try > something like > ``` > $ mailman-web shell > > >>> from hyperkitty.lib.compat import get_list_by_name > >>> mlist = get_list_by_name('list_name_only', 'list_domain') > >>> with open('output.mbox', 'wb') as fp: > ... for email in mlist.emails.order_by("archived_date").all(): > ... fp.write(email.as_bytes() + b'\n') > ... > >>> > ``` > I tested the above out of curiosity. It failed. There are 9 lists in the setup, but I am only interested in 1. ``` (venv) mailman@debian12:~$ mailman-web shell Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] Type 'copyright', 'credits' or 'license' for more information IPython 8.17.2 -- An enhanced Interactive Python. Type '?' for help. In [1]: from hyperkitty.lib.compat import get_list_by_name In [2]: mlist = get_list_by_name('list_name_only', 'list_domain') --------------------------------------------------------------------------- Http404 Traceback (most recent call last) Cell In[2], line 1 ----> 1 mlist = get_list_by_name('list_name_only', 'list_domain') File ~/venv/lib/python3.11/site-packages/hyperkitty/lib/compat.py:37, in get_list_by_name(list_name, domain) 35 matching = list(MailingList.objects.filter(name__startswith=list_name+"@")) 36 if len(matching) == 0: # no candidate found ---> 37 raise Http404("No archived mailinglist by that name") 38 if len(matching) == 1: # only one candidate 39 return matching[0] Http404: No archived mailinglist by that name ``` Was I supposed to substitute something for the real listname of the list I wanted? Another thing - totally unrelated - that surprised me: While using the commented-out block below, I could not click and get anything beyond http://http://list.name/mailman3 as anything to do with /postorius/xxxxx gave "Page not found" error. However, with the second config block that uses the UNIX socket, I am able to access everything ``` #<IfModule mod_proxy.c> # ProxyPreserveHost On # ProxyPass "/mailman3" "http://127.0.0.1:8010/mailman3" # ProxyPass "/archives" "http://127.0.0.1:8010/archives" # ProxyPass "/accounts" "http://127.0.0.1:8010/accounts" # ProxyPass "/admin" "http://127.0.0.1:8010/admin" # ProxyPass "/user-profile" "http://127.0.0.1:8010/user-profile" # </IfModule> ProxyPassMatch ^/static/ ! ProxyPassMatch ^/favicon.ico ! ProxyPass / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ ProxyPassReverse / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ ``` Why is it that the UNIX socket option worked flawlessly while the other option failed??? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 5 months

[MM3-users] Re: Mail configuration

by Mark Sapiro

On 03/27/2018 03:43 PM, Stephen J. Turnbull wrote: > > My feeling is that you want to ask on Postfix channels, since I don't > see a good reason to involve Mailman itself in what is really a task > for the MTA. Mailman was deliberately designed to not know anything > about outgoing mail except a host and port to send to. Which brings up the point I've been meaning to post for days but it keeps slipping off the back burner and falling on the floor. I can think of a couple of ways to hack the code in Mailman 2.1 to select a different outgoing MTA by list. It can also be done in Mailman 3 by having separate MTA configs per list, but I can't give you a recipe off hand. But, the way I would do this is what you are presumably doing anyway. That is have separate Mailman installations on the old and new server. Then you can move the lists incrementally and gradually. Then all you need is a transport map in Postfix on the old server to route mail to the new server for the already moved lists, and then finally update DNS after all the lists are moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 5:48, Mark Sapiro escribió: > On 10/26/22 04:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I did it via pip and all seems to be working, but when I try to >> discard or accept any message via postorius it shows a Forbidden 403 >> error CSRF verification failed. >> >> In my settings.py I have commented out these variables: >> >> # Other security settings >> # SECURE_SSL_REDIRECT = True >> # If you set SECURE_SSL_REDIRECT to True, make sure the >> SECURE_REDIRECT_EXEMPT >> # contains at least this line: >> # SECURE_REDIRECT_EXEMPT = [ >> # "archives/api/mailman/.*", # Request from Mailman. >> # ] >> # SESSION_COOKIE_SECURE = True >> # SECURE_CONTENT_TYPE_NOSNIFF = True >> # SECURE_BROWSER_XSS_FILTER = True >> # CSRF_COOKIE_SECURE = True >> # CSRF_COOKIE_HTTPONLY = True >> # X_FRAME_OPTIONS = 'DENY' >> >> I've been messing with them whith no results. It's like it lacked >> some value in some template... > > > It's not an issue with the code per se or the templates. These updates > are all installed on mail.python.org and lists.mailman3.org and are > working fine. > > After upgrading did you run > > django-admin collectstatic --clear > django-admin compress > django admin migrate Since I made all the mailman3 enviroment wide server open (not using venv) I already executed the migration doing a su -m mailman3 -c "python3 manage.py collectstatic" su -m mailman3 -c "python3 manage.py migrate" Being mailman3 the user who runs all of mailman3 related stuff I had problems doing the migrate part, showing an error of lacking perms. I solved it running the migration under root (I know it could be trouble after, but...) After that the compress part showed errors... but the postorius web maintenance was working well except for the CSRF error verification. I will trace the compress errors and will try to find the problem later. With your point to the CSRF_TRUSTED_ORIGINS parameter, I can now do the accept or discard part of a receiving message to the lists (I put below the config that is working for me). All seems to be working now flawlessly. Thanks once again for your guidance. ############ SESSION_COOKIE_SECURE = True SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_BROWSER_XSS_FILTER = True CSRF_COOKIE_SECURE = True CSRF_COOKIE_HTTPONLY = True X_FRAME_OPTIONS = 'DENY' # CSRF_TRUSTED_ORIGINS = [ "https://*.mydomain-example.xxx", "https://mydomain-example", "https://mydomain", ] ############ > > If you have and it doesn't help, you probably need to add > CSRF_TRUSTED_ORIGINS to your settings.py. > > See > https://docs.djangoproject.com/en/4.1/ref/settings/#csrf-trusted-origins > and note the differences between Django <4.0 and >=4.0. > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 6 months

[MM3-users] Re: Using MySQL via unix socket

by Mark Sapiro

On 2/2/19 5:31 AM, Torge Riedel wrote: > > A call to > > mysql -umailman -p > > successfully uses the socket on the machine and logs in. Yet you haven't specified -S or --socket > I tried > > mysql+pymysql://mailman:mailmanpass@127.0.0.1/mailman3?charset=utf8&use_unicode=1&unix_socket=/var/run/mysqld/mysqld.sock > > > as the connection string but it says that mysql server is not available. > Which is the same if remove the "unix_socket" parameter. I have found > this parameter when searching the net, but I'm not sure if it is supported. I think it should be, but the actual connection is via the the sqlalchemy create_engine() function. It appears this should be passed to the pymysql Connection() function per <https://docs.sqlalchemy.org/en/rel_1_2/core/engines.html#custom-dbapi-args> What happens if in a Python 3 session, you do from pymysql import connect conn = connect('127.0.0.1', user='mailman', password='mailmanpass', database='mailman3', charset='utf8', use_unicode=1, unix_socket='/var/run/mysqld/mysqld.sock') As I understand it, that's what sqlalchemy should be doing with your database url. In my testing, the above works with or without the unix_socket= argument, so I suspect something else is wrong in your case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Held message notifications ending up in junk

by Tibor Molnar

Hi Steve, I will look in to DKIM, thanks for your suggestion. Tibor On 09/09/2022 03:01, Stephen J. Turnbull wrote: Tibor Molnar writes: > I wonder if anyone else if having this trouble that all the held > message notifications are landing in junk folder. It's reported occasionally. This is automated pattern recognition doing its thing: these notifications *do* present very similar content *repeatedly* and *are* sent by a bot, and the algorithms figure that out quickly. Make sure the site DKIM signs its outgoing mail and whitelist the site, or whitelist the bot's address. Steve -- [Walton icon] Tibor Molnar [website icon] <https://waltoninstitute.ie/> [linkedin icon] <https://www.linkedin.com/in/tibor-molnar-564293106> [twitter icon] <https://twitter.com/username> [facebook icon] <https://www.facebook.com/username> System Administrator tibor.molnar(a)waltoninstitute.ie<mailto:name.name@waltoninstitute.ie> | +353 (0)51 30 6145 Walton Institute, South East Technological University, West Campus, Carriganore, Waterford, Ireland, X91 P20H [walton logo]<https://waltoninstitute.ie/> [setu logo] <https://www.setu.ie/> [DORA logo] <https://sfdora.org/read/> ________________________________ This email is subject to the following disclaimer(s) available at SETU Disclaimer.<https://www.wit.ie/about_wit/documents_and_policies/email-disclaimer> T? an r?omhphost seo faoi r?ir an ts?anta/na s?anta seo leanas at? le f?il ag SETU S?anad<https://www.wit.ie/about_wit/documents_and_policies/email-disclaimer> [SETU]<https://www.setu.ie>

3 years, 7 months

[MM3-users] Re: Mailman 3 Installation Assistance

by brian＠emwd.com

Hi Simon, Thank you for your reply. I did not realize that docker created everything for you so I prefer that. So let me get back to my original problems. I ran into the following after doing the normal docker installation: 1. curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; Connection refused 2. I was told to run docker ps. Here is the output from that: ONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 073ecf209106 maxking/mailman-web:0.1 "docker-entrypoint..." 3 days ago Up 3 days 8000/tcp, 8080/tcp mailman-web aef8f44a7136 maxking/mailman-core:0.1 "docker-entrypoint..." 3 days ago Up 3 days 8001/tcp, 8024/tcp mailman-core 398e3fc05e2c postgres:9.6-alpine "docker-entrypoint..." 3 days ago Restarting (1) 36 hours ago dockermailman_database_1 3. I was asked to look at the logs which I don't have any: cd /opt/mailman/web/logs -bash: cd: /opt/mailman/web/logs: No such file or directory 4. I was asked to do docker logs mailman-web. It is filled with the following entries: psql: could not translate host name "database" to address: Try again Postgres is unavailable - sleeping It is after the above when I got confused. So now I understand that the Docker installation creates the database and runs it. That is important to know. So if you can help me get through the above 4 issues, it would be very appreciated. Thanks! Brian

8 years

[MM3-users] Re: Help understanding why some users don't receive emails

by Mark Sapiro

On 9/21/22 14:06, Stephen Daniel wrote: > > Looking at one user in particular, I see in /var/log/syslog that postfix is > sending the email. There is nothing in bounce.log. And does the postfix log indicate the mail is accepted by the users MX? I.e. a log message with `status=sent`. > They are the only user who uses that particular email domain (embarqmail.com > ). > > Is there anything I can do to debug why they do not get the emails? Or is > this up to them and their email provider? Assuming the message is accepted by the user's MX, the user can check a spam/bulk/junk folder and if the messages aren't there, complain to their ISP about messages being silently discarded. Your log entries showing the message successfully delivered to the MX can provide evidence. Other than that, you need to ensure that your outgoing messages are DKIM signed, and that your outgoing MTA server has full circle DNS <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. It can also possibly help for the server's domain to publish a DMARC policy even if that is `p=none` -- 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] My Server is unable to connect to Mailman REST API few times

by Shashikanth Komandoor

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values in production environment from the past 4 months almost. As of now, we are having around 1327 lists created on this. When I am trying to do some operations like creating the lists, deleting the lists or accessing the lists through the GUI, I am getting the below error. If I am trying to do the operations through API or through mailman shell, still I am not able to connect to the API. Something went wrong Mailman REST API not available. Please start Mailman core. But my mailman core was working fine in the background. At the same time I was able to do other operations on a few other lists. By the time I am getting the above error, the mailman.log recorded the below messages. *[2020-09-16 12:49:08 +0530] [2600] [CRITICAL] WORKER TIMEOUT (pid:20234)* *[2020-09-16 12:49:08 +0530] [20234] [INFO] Worker exiting (pid: 20234)* *[2020-09-16 12:49:09 +0530] [21042] [INFO] Booting worker with pid: 21042* My mailman.cfg configuration is as below. The timeout value is the default value. I did not set any customized value. *(venv3) [root@lsmgr mailman]# grep -v ^# /var/lib/mailman/mailman/var/etc/mailman.cfg* *[archiver.hyperkitty]* *class: mailman_hyperkitty.Archiver* *enable: yes* *configuration: /var/lib/mailman/mailman-hyperkitty/mailman-hyperkitty.cfg* *[mta]* *incoming: mailman.mta.postfix.LMTP* *outgoing: mailman.mta.deliver.deliver* *lmtp_host: 0.0.0.0* *lmtp_port: 8024* *smtp_host: localhost* *smtp_port: 25* *[webservice]* *workers: 10* *[database]* *class: mailman.database.postgresql.PostgreSQLDatabase* *url: postgres://<postgresdbuser>:<postgresdbpassword>@127.0.0.1/mailman <http://127.0.0.1/mailman>* Then as per the suggestion I got earlier I configured the [webservice] section in the above file as below. *[webservice]* *configuration: /var/lib/mailman/mailman/var/etc/gunicorn.cfg* * [root@lsmgr logs]# cat /var/lib/mailman/mailman/var/etc/gunicorn.cfg* *[gunicorn]* *workers = 10* *timeout = 90 * After the above configuration, I found many errors like below in mailman.log file: *sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'pended.id <http://pended.id>'"* *sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically.* *sqlalchemy.exc.DatabaseError: (psycopg2.DatabaseError) error with status PGRES_TUPLES_OK and no message from the libpq* The above might be few of the errors. FYI, for the creation of each list, it is taking almost around 15 to 20 minutes. After multiple times of the above error messages, at some time, I am fortunately getting the list created or some other operation getting done. I found the same scenario when the workers are from default 2 to 10. I don't understand where exactly I need to focus to solve the issue. Please let me know if I have to share any other details for you to suggest to me. -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

5 years, 7 months

[MM3-users] Re: Question after upgrade to mm 3.2.3 and latest postorius

by David Krantz

Thank you for your quick reply! Comments below. On Sun, Aug 11, 2019 at 10:03 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > I would recommend that you bump up to 3.7 for the web part too, mostly because 3.5 is now has been in security maintenance state for a while. We will drop support for 3.5 after this next release (so you do have some time :), but I fear there *could* potentially be other dependent libraries who might have dropped 3.5 support. > > Even though we do run CI and we'd (hopefully) know when there is a dependent library seriously breaking, but since we don't pin down versions, newer releases can cause problems. > > The web-server plugin I assume is mod_wsgi? Good information. Of course it is mod_wsgi. > If you use a separate wsgi server than the one embedded in web-server, you can bump versions a bit more easily. gunicorn or uwsgi are recommended options. Do note that the new version of Mailman Core also uses gunicorn now. That might be simpler although I probably still will have to use apache as passthrough as there are other things on that server using port 443 (80) and yet another server running is not what I'd like even if wsgi is a server process anyway as I understand it. I'll consider that and change it. > 1. The index page with all lists is not sorted in any useful way > > although it is based on something as the order seems to be stable. > > Prior to the upgrade the lists were sorted in alphabetical order after > > list name which is a lot more usable for me as admin. If I click the > > link at the bottom with "click to view all lists" I get the old > > behaviour. > > This change was made so that you will see only the lists you are a member of either as a subscriber, moderator or owner. This is default when you are logged-in, but when logged-out, you will see the old view with all lists alphabetically sorted. That is very good. It still is strange that this view is not sorted. > Are you sure the migrations are there? I can see the following list on the latest git master of Postorius (all the ones after 0004_ are related to emailtemplate): I thought so, but it seems as if they are not. That said I have not used django for anything else. After setting up the django-admin-script and modifying a few paths I got it to work correctly. The run I had made did not work although it also failed silently. Had I been used to django I'd known that it should print "OK" and ticked boxes for performed migrations, but I just use django for mailman-things. So now it works. Great. Thanks! // David

6 years, 8 months

[MM3-users] Re: Single-Sign-out for List member

by Ángel

On 2020-08-13 at 16:55 -0700, Abhilash Raj wrote: > > I understand you may have a legal requirement do do this, but these > > "one-click - no user confirmation" links are a bad idea because usera > > will reply to a list post or forward it and not remove the link and > > userb will receive usera's reply and click usera's unsubscribe link > > either maliciously or thinking it will unsubscribe userb. > > There is also the issue that these days some Mail clients will try to > create a preview of all the URLs if they can and it would inadvertently > GET the URL resulting in the un-subscription. It's not just mail clients, but also anti-spam solutions. So for some customers, when the email passes through the antivirus/anti-spam solution, it would automatically unsubscribe the user. Check also this piece: https://inboxplacement.com/2020/05/machine-clicks-in-email/ If you end up with such system, the very least, I would make such system to also email the user one last time saying "Per your instruction as requested by machine IP V.X.Y.Z, we have unsubscribed from foobar-list, you can subscribe again by XYZ, etc." (maybe bcc the responsible internal team) And you don't want to start trying to tell apart real vs synthetic clicks. Regards

5 years, 8 months

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

by Danil Smirnov

Hi Stephen, My example assumes that there are folders (inside of /basedir) on a Docker host machine which are mounted to mailman containers. So we run logrotate on the host machine against those mapped folders. Hence, /etc/logrotate.d/mailman file is for the host machine as well. Danil On Fri, Sep 4, 2020 at 12:36 PM <skenny(a)scss.tcd.ie> wrote: > Hi Danil, > > Firstly, thank you so much for your reply, and I do apologize for taking > so long to respond to your message. > > I understand your approach, and it sounds reliable and sensible. I'm > still a bit confused by something though. In your example, you create the > file /etc/logrotate.d/mailman - I presume that it must live in, or be > available in the container - but which one? You've created a single file, > with entries for both the mailman-core and mailman-web logs. But the logs > of -core are not available in -web and vice-versa. Did you mean to do > separate > "cat <<EOF > /etc/logrotate.d/mailman" operations for each container? > > Thanks again > Stephen > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

5 years, 7 months

[MM3-users] Re: Archiver Hyperkitty Not Found

by Mark Sapiro

On 3/3/23 15:16, pat(a)suwalski.net wrote: > Hello, > > I upgraded from Debian 10 to 11 today, and hyperkitty archiver stopped working. > >>From the mailman.log: > > AssertionError: Archiver not found: hyperkitty > > I followed along on a related thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > I don't see any resolution to that thread. The only thing that worked for me was removing the hyperkitty rows from the listarchiver table in the database. But of course, now I don't have working archiving. There is a resolution of sorts there: It was setting ``` [archiver.hyperkitty] enable: no ``` in mailman.cfg, restarting Mailman core and then setting it back to `enable: yes`. > Any ideas? How would I make the archiver available? This django stuff is infuriatingly difficult compared to other frameworks. Do you have ``` [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg ``` in your mailman.cfg where `/opt/mailman/mm/mailman-hyperkitty.cfg` is the actual path to mailman-hyperkitty.cfg and do you have in that file ``` [general] base_url: http://example.com/hyperkitty/ api_key: key matching the MAILMAN_ARCHIVER_KEY set in Django's settings. ``` Actually, even if these latter settings were wrong, the error would be different. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Apache shows No Lists

by Mark Sapiro

On 5/22/23 12:57, ceo(a)sartrack.nz wrote: > Postorius is running. > I just removed all mailing lists, and created new empty ones. > These now show in the Apache2 website, via the link to Postorius I assume. > Then I imported members from the old mailing list "Templist" into the new one. > Now the "templist" is no longer visible on the website! Did you do this import with `mailman import21`? If so, did you run it as the Mailman user and not as root? > It is here: > https://sartrack.nz/mailman3/ > Note that the existing list "Templist" is missing. https://sartrack.nz/mailman3/ is missing CSS. Apache doesn't know how to access /static/ or you never built it with the django admin collectstatic command. > Now I need to login as 'superuser' or whatever it is called, so I can manage all the lists. > Where do I set up my login and password for access via the web browser? You create a superuser with the django admin createsuperuser command. How you invoke the django admin command depends on how you installed Mailman. Please tell us how you installed Mailman so we don't have to guess about this and other things. -- 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: Message is received but is not sent out. Another, similar message, is processed fine.

by Stephen J. Turnbull

Allan Hansen writes: > LookupError: unknown encoding: iso-8859-8-i > Finally, in the captured message source (the last which was Cc'd to me) I do see this: > > Content-Type: text/plain; charset="iso-8859-8-i" Yes, that's the problem. Python doesn't define a codec for that encoding. It's generally preferable that mail senders use UTF-8, as that is likely to be implemented correctly in almost all modern mail clients, while the ISO-8859/8 series are likely to be implemented only in mail clients that specifically support Hebrew. That said, if the users are unable or unwilling to use UTF-8, it would be possible to create a codec for "iso-8859-8-i", I don't know how to do that, and I doubt Mark does. You could ask on python-list(a)python.org, or file an RFE on Python's GitHub tracker. For Mailman's purpose, there's no need to handle bidi, just codepoint for codepoint translation from "iso-8859-8-i" to Python internal encoding. So I guess the encoder and decoder from "iso-8859-8" (which does exist) can be used. If it's just code-for-code, then we can figure out how to have it used only for Mailman. Steve

2 years, 10 months

[MM3-users] Re: Domain defaults for new lists

by Mark Sapiro

On 1/29/26 14:04, Peter Chubb via Mailman-users wrote: > > Hi Folks, > Is there a simple way to set up the defaults for any newly created > lists? > We've had a few cases recently where in the time between creating a mass-populated > list and making it private it's been inundated with spam. > > I'd like to change the defaults so newly-created lists are private and have > private archives, new members are moderated, etc., to give time for > the list to be set up completely before announcing it to the world. Actually, I think the 'private-default' list style does almost all you want except for new members moderated. https://gitlab.com/mailman/mailman/-/issues/871 asks for that to be changed, however the 'private-default' list style sets the subscription policy to confirm then moderate so spammers can't subscribe and post without their subscriptions being approved by a moderator. You can implement a new list style to do exactly what you want. See https://gitlab.com/mailman/example-mailman-plugin for information about implementing a plugin to do that. Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… for general information on list styles. -- 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: Issues with Mail delivery after Mailman 3 installation

by Chihurumnaya Ibiam

On Fri, Feb 6, 2026 at 7:57 AM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Chihurumnaya Ibiam via Mailman-users writes: > > About disabling dovecot: > > > I don't plan on shutting down the host anytime soon, so hopefully, > > I remember to the next time it restarts. > > systemctl stop dovecot > systemctl disable dovecot > systemctl daemon-reload > > should do the trick without rebooting the host. > That did, showed it was removed from /etc/systemd/system/multi-user.target.wants/. > > > Yes, postfix_lmtp table is set in transport_maps, virtual_mailbox_maps, > > relay_domains, local_recipient_maps. > > Do you have lists.sugarlabs.org in $virtual_mailbox_domains? As Mark > points out, virtual mailboxes make life more complicated. Also, I > don't think postfix_lmtp should be in $relay_domains (that table > contains addresses which won't match domains being looked up). If > anything it should be postfix_domains. > No, I don't have virtual_mailbox_domains set, I didn't need to. Yes, postfix_lmtp isn't in relay_domains, that was my fault, it's postfix_domains. > > > > It's problematic for Mailman because that means that *all* local mail > > > will be delivered to Mailman, which will reject it if it's not > > > list-related. > > > I'm totally fine with this because that's why we setup the host, > > I'm sorry, that was unclear. By "list-related", I meant that "the key > Postfix is trying to match is an exact match for a key in the > postfix_lmtp table". Because these are hash tables, it is Postfix's > responsibility to strip "+extension" from the recipient address before > presenting the stripped address to the table for matching -- the table > can't do it. > > Specifically, this applies to the confirmation and VERP cookies that > may be attached to addresses for various reasons. > Now I understand why it's a problem. Going by your earlier assumption that perhaps the same thing doesn't happen for mailbox_transport, how would I use that as a fallback in such cases? > > > a mailing list, which should work just fine but then it seems > > they need to connect to this host. > > > 165968 Feb 5 04:48:46 lists postfix/smtp[1941010]: connect to > > weblate.sugarlabs.org[2001:5a8:601:f::214]:25: Connection refused > > 165969 Feb 5 04:48:46 lists postfix/smtp[1941010]: B785D1A897F: to= > > <root(a)weblate.sugarlabs.org>, relay=none, delay=17323, > > delays=17323/0.02/0.33/0, dsn=4.4.1, status=deferred (connect to > > weblate.sugarlabs.org[2001:5a8:601:f::214]:25: Connection refused) > > This is a problem at weblate.sugarlabs.org. Is it supposed to be > receiving mail? I don't think that this is an authentication problem > (SASL authentication takes place after connection), although if > "weblate" expects authenticated TLS that might be the problem. So > "lists" needs to be whitelisted (eg in $mynetworks) at weblate (I > suppose Postfix is also the MTA at "weblate"?) If you have only the > toplevel domain sugarlabs.org whitelisted, you may need to set another > parameter to automatically include subdomains such as lists.sugarlabs.org. > > No, weblate isn't supposed to receive email. It runs a service that sends emails just like MM3. Yes, postfix is also the MTA at weblate. I can include subdomains, but I don't see a reason for doing so at the moment. One thing I had done to remediate the error - which didn't do anything from the logs - is add check_client_access hash:/etc/postfix/client_access in smtpd_client_restrictions. > > No, I'm not running mailman as root, it's run as mailman. > > Seeing as that's the case, would I still need to change lmtp_port? > > Yes, as far as I know. That's because by convention ports < 1024 can > only bound to programs running as root (enforced by the kernel). I > don't understand how Mailman is receiving mail configured to listen on > port 24. This may have something to do with dovecot running. > > However I really don't understand the lsof output, because you present > logs that indicate that Mailman is processing mail for lists, but > nothing was listening or connected on port 24. You also say Postorius > and HyperKitty are running, but nothing showed up on port 8000, which > is where they would be listening. Maybe I got the lsof options wrong, > but it did find Postgres and Mailman's REST API. > Me configuring lmtp_port to 24 earlier did interfere with Mailman because I had dovecot running on the same port at the time, after disabling dovecot and commenting out lmtp_port, I noticed Mailman listening on 8024, postfix_lmtp also showed this. I don't know why Postorious and Hyperkitty didn't show up at the time, but I just ran lsof and this is the output; $ lsof -i TCP(a)127.0.0.1 -i 'TCP@[::1]' | grep 24 python3 1983955 mailman 26u IPv4 181237054 0t0 TCP localhost:8024 (LISTEN) uwsgi 1985531 mailman 9u IPv4 181247623 0t0 TCP localhost:8000 (LISTEN) uwsgi 1985547 mailman 9u IPv4 181247623 0t0 TCP localhost:8000 (LISTEN) uwsgi 1985548 mailman 9u IPv4 181247623 0t0 TCP localhost:8000 (LISTEN) mailman-w 1985554 mailman 44u IPv6 185803776 0t0 TCP localhost:60244->localhost:postgresql (ESTABLISHED) postgres 2458591 postgres 9u IPv6 185580185 0t0 TCP localhost:postgresql->localhost:43102 (ESTABLISHED) postgres 2458595 postgres 9u IPv6 185581026 0t0 TCP localhost:postgresql->localhost:43140 (ESTABLISHED) postgres 2458607 postgres 9u IPv6 185579124 0t0 TCP localhost:postgresql->localhost:43234 (ESTABLISHED) postgres 2482767 postgres 9u IPv6 185805780 0t0 TCP localhost:postgresql->localhost:60244 (ESTABLISHED) postgres 2482831 postgres 9u IPv6 185807057 0t0 TCP localhost:postgresql->localhost:56188 (ESTABLISHED) postgres 3568035 postgres 5u IPv6 160224851 0t0 TCP localhost:postgresql (LISTEN) postgres 3568035 postgres 6u IPv4 160224852 0t0 TCP localhost:postgresql (LISTEN) Which shows the expected ports being listened on, I'll assume the issue with Postorious was probably because the mailmanweb service stopped at some point as I tried to restart it and that was basically running uwsgi, it didn't run and when I looked further I noticed uwsgi was running so there was no need to do this, as that's what it was trying to do. > > It did get it working, I can see mail being sent in the logs. > > I sent a ping to the systems list just to get delivery confirmation > > and I'm yet to get a response. > > I don't have an idea what's going on yet. The mail you see being sent > in the logs, is that to a gmail address? Or is it a sugarlabs.org > address? (Both of these seem to be problematic at the moment.) > It was to a sugarlabs.org address, I've been able to receive mail owner messages to my inbox, I configured a gmail address as the admin for Mailman suite, which indicates that mail delivery works as expected. > > > > > What does "lsof -i @127.0.0.1 -i '@[::1]' | grep 24" output? > > > > > > > python3 1592922 mailman 27u IPv4 177685024 0t0 TCP > > > localhost:8001 (LISTEN) > > > > python3 1592949 mailman 27u IPv4 177685024 0t0 TCP > > > localhost:8001 (LISTEN) > > > > python3 1592950 mailman 27u IPv4 177685024 0t0 TCP > > > localhost:8001 (LISTEN) > > > > > > The above are Mailman (actually, a gunicorn application) listening for > > > connections to its REST API. These are HTTP listeners used by > > > Postorius and HyperKitty (I guess those aren't running?), not for > email. > > > > > > > Postorius and HyperKitty are running. > > But they should show up as several Python applications running as > mailman, listening or connected on port 8000. But they're not here. > Try "lsof -i :8000 -i :24". > I agree, I've explained a probable cause above. They now show up in the lsof output. > > This is one that's consistent with Dovecot in the logs; > > This is Postfix sending a non-delivery notification about A26F71A8977: > > 157323 Feb 4 12:27:02 lists postfix/bounce[1587396]: A26F71A8977: > sender non-delivery notification: AC7381A8978 > > The <> tells us that this is the nondelivery notification referred to > as AC7381A8978 so there's no return address to send to: > > 157324 Feb 4 12:27:02 lists postfix/qmgr[1593314]: AC7381A8978: > from=<>, size=3129, nrcpt=1 (queue active) > > postfix/local looks at mailbox_transport and sends it to lmtp, where > dovecot is listening; > mailbox_transport currently doesn't have a value. > > 157325 Feb 4 12:27:02 lists postfix/local[1593315]: AC7381A8978: > passing <mailman(a)lists.sugarlabs.org> to transport=lmtp > > 157326 Feb 4 12:27:02 lists dovecot: lmtp(1600482): Connect from > 127.0.0.1 > > Postfix is done with A26F71A8977, and pops it off the queue: > > 157327 Feb 4 12:27:02 lists postfix/qmgr[1593314]: A26F71A8977: > removed > > dovecot denies knowing about a local user named "mailman", rejecting it: > Yes, this probably because I haven't properly configured user lookup on dovecot. > > 157328 Feb 4 12:27:02 lists postfix/lmtp[1593316]: AC7381A8978: > > to=<mailman(a)lists.sugarlabs.org>, relay=localhost[127.0.0.1]:24, > delay=0.04, > > delays=0.02/0/0/0.01, dsn=5.1.1, status=bounced (host > localhost[127.0.0.1] > > said: 550 5.1.1 <mailman(a)lists.sugarlabs.org> User doesn't exist: > > mailman(a)lists.sugarlabs.org (in reply to RCPT TO command)) > > dovecot says "I'm done here": > > 157329 Feb 4 12:27:02 lists dovecot: lmtp(1600482): Disconnect from > 127.0.0.1: Logged out (state=READY) > > > Which we've established that mailman doesn't know how to deliver to > local > > users. > > So that's a bounce from dovecot. I don't know enough about dovecot or > your configuration of dovecot to guess what happened. > > At the moment, I've disabled the service and have no configurations for it. I commented out my earlier configs before disabling it. > > Could be, doesn't seem to be an issue at the moment so I won't worry > about > > it. > > The Message-ID is syntactically well-formed. I'm worried about side > effects from the hostname not being the FQDN in mail protocols. As > long as all the configurations for Postfix use the FQDN (Postfix is > smart enough to abbreviate when that's useful), there shouldn't be any > problems like that. > All the configurations that are supposed to contain the FQDN does; mydestination, mydomain, myhostname. Am I missing any? > > Yes, earlier when I set it up I had set the port for Mailman to use as > 465. > > OK. > > > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan > -- Ibiam Chihurumnaya ibiamchihurumnaya(a)gmail.com

2 months, 3 weeks

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Nelson Strother

Yes, Postfix is also running, but this system currently has a trivially small configuration (single domain, single digit number of lists). When the CPU is kept ~100% busy for (maybe once as few as a) dozen minutes to (usually 20 minutes, but rarely) an hour [1] during `mailman start`, essentially all of the CPU time is being consumed by the dozen or so mailman runner processes, so I do not think Postfix alias processing has much if anything to do with these delays. [1] wall clock time; as an arbitrary indicator of how many cycles VMWare is giving to this server, here is what 7-zip observes: x@localhost:~$ 7za b 7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,1 CPU Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz (406F0),ASM,AES-NI) Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz (406F0) CPU Freq: - - - - - - - - - RAM size: 425 MB, # CPU hardware threads: 1 RAM usage: 219 MB, # Benchmark threads: 1 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 2909 99 2861 2831 | 29117 99 2502 2486 23: 2370 88 2741 2415 | 28833 99 2512 2496 24: 1937 79 2622 2083 | 27937 98 2501 2453 ---------------------------------- | ------------------------------ Avr: 89 2741 2443 | 99 2505 2478 Tot: 94 2623 2461 x@localhost:~$ On 6/8/23 10:14, Stephen J. Turnbull wrote: > Nelson Strother writes: > > > I did not intend to imply that `mailman start` (predictably) > > consumes more time than `mailman restart`. Both are lengthy and > > variable; > > You did say something about "30min" I believe. I don't understand why > it would take anywhere near that long. For example, I'm working with > a site with ~20,000 lists, and it only takes a few seconds. > > Oh ... wait ... are you using Postfix as the MTA? The supplied > Postfix MTA interface rebuilds the list aliases database on every > (re)start, and that's an O(#lists^2) process the way Mailman does it. > Postfix doesn't actually use the file to route mail, it always goes to > lmtp:127.0.01 or something like that. So I configured Postfix to > probe for existence of the list in Mailman's database. > > I think Postfix has plugins for all Mailman-supported databases > (PostgreSQL, MySQL/MariaDB, SQLite3). I can provide the changes > needed for this for PostgreSQL right away, if you're a MySQL site I > can give you the PostgreSQL config to give you the idea, but I may be > sslow if you want advice about the MySQL config. It's pretty > straightforward, though. > > > I do not yet understand how to make use of these clues, but at > > least one can see an epitaph from each deceased process. > > I don't understand them either. The only thing I can think of is that > a runner may try to access Mailman core, timeout, and crash during the > long startup. > > At least the MTA reconfig would make the restart cycle a lot less > painful. Note: this is NOT a Mailman-supported config (or even > contrib quality) yet, but I'm pretty confident of the theory and it is > working well in QA testing. > > Regarding the "alpha" status of the config, one Mailman 3 instance can > support multiple domains, but the Postfix docs say not to hit the > database for the "domain exists" check. If you aren't going to add > additional Mailman domains, then this doesn't matter (the domain list > file produced by the stock Mailman postfix config will work), but if > you do add or remove domains, you either need to configure Postfix to > hit the database for the "domain exists" check too contrary to > Postfix's advice, or you'd need to manage the domain list file by > hand. > > In any case, you could use this config for debugging, and go back to > the tried and true aliases file approach for production. And as I > indicated I'm somewhat available on a best-effort basis for > trouble-shooting. > > > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-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/mess… > > This message sent tojustfixit(a)marilynstrother.com

2 years, 10 months

[MM3-users] Re: Rerun emails in the queue/bad

by Mark Sapiro

On 11/20/18 8:20 AM, Kaleb White wrote: > How do I run the emails in the queue/bad again? I need to see why the failed and get them to work. Thanks. There should be error messages in the 'mailman' log for each preserved file. These would be like 'Skipping and preserving unparseable message: ....psv' 'Unpickling .bak exception: <error msg> Preserving file: ....psv' '.bak file max count, preserving file: ....psv' The first of these indicates an error in retrieving the message from it's original queue. The others have to do with how message loss is avoided. When a .pck file in a queue is processed, it is read and renamed to a .bak. Then if processing is interrupted by a crash, upon restart the .bak file will be processed. The second error above indicates a problem in unpickling the .bak and the third says the same .bak has already been tried too many times. You may be able to examine the files by pointing 'mailman qfile' at them. If that fails, either 'cat' or 'strings' may produce something useful. If they appear to be good, you can reprocess them by renaming to .pck, moving to queue/shunt and running 'mailman unshunt'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Request for ideas and mentors for Summer of Code 2026

by Stephen J. Turnbull

alain williams writes: > Do add what was discussed here a month or so ago: the ability for a > list owner to change a user's email address. Sorry, but this is a design problem that is way out of scope for GSoC. For example From: alain(a)hacks.r.us To: somelist-owner(a)example.net Subject: Please change my address I can't access my addw address because I'm not working at phcomp any more. -- Alain Oops. In general, addresses are *owned* by users. So you need to authenticate the *user* in order to be sure you're changing the address for the right person. List owners are often not even power users. At least site owners can be expected to have some experience with how nasty the raw Internet is and a certain amount of paranoia, but that's not generally true of list administrators. I want the people designing privilege hierarchies to be MUCH more paranoid than typical site owners. > ? should a list owner be able to do so ? Ie rogue/malicious list > owners. I'm not really worried about a rogue list owner. I'm worried about naive list owners. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months, 3 weeks

[MM3-users] Re: Things I miss about mailman2

by Mark Sapiro

On 3/17/20 8:58 AM, Quanah Gibson-Mount wrote: > Now that we are on mailman3, I'm finding things that were really useful > in mailman2 are completely missing in mailman3, which seems odd, since > they in particular affect the ability of list moderators to do their job > well. > > a) When a post was made to a moderated list in mailman2, I would get an > email that included a LINK to the held email. Now I just get a canned > email saying I need to go to the dashboard, blah blah. Why was this > link removed? It was extremely useful and now I have to jump through > extra hoops. The message comes from Mailman core. Mailman core does not know what web management UI you are using or the URI to access it. You need to change the template for the message to include the URL. E.g. on this iist, in var/templates/sitr/en/list\:admin\:action\:post.txt we have As list administrator, your authorization is requested for the following mailing list posting: List: $listname From: $sender_email Subject: $subject The message is being held because: $reasons At your convenience, visit https://lists.mailman3.org/mailman3/lists/$list_id/held_messages to approve or deny the request. > b) When a post is made to a moderated list in mailman2, when I went to > the page to approve/deny/discard, there was additionally an option to > remove the moderated flag from the user for all future emails. This > option no longer exists. This was EXTREMELY useful, as we force all new > members of the list to be moderated for a time while we evaluate the > quality of their postings. Now I have to go manually track down the > user and their settings. Unnecessary extra hoops to jump through Click on the subject in the held messages list. At the bottom of the dialog that opens, there is a drop down to set the user's moderation. Normally, you would set it to 'default processing'. > c) When a post is made to a moderated list, one of the options when > selecting REJECT was it allowed me to set a custom message when > rejecting the email. This was extremely useful. For example today, > someone emailed our bug tracking list directly instead of filing a bug. > In the past, I would have added a note to them about what they should do > (in this case, I would have told them to send their email to our > community technical discussion list). Now I can no longer do that, I > can only reject it or discard it. Why was this removed? This was not "removed". It just hasn't been implemented in MM 3 yet. See, e.g., <https://gitlab.com/mailman/postorius/-/issues/368> and <https://gitlab.com/mailman/postorius/-/issues/368>. -- 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: Migrating Mailman 3 lists

by Mark Dadgar

On Apr 27, 2020, at 8:58 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> I know how to migrate mailman 2 lists to a new mailman 3 server. However >> I do not know how to migrate a mailman 3 list from one mailman 3 server >> to another one. Are there any instructions or protocol on how to >> accomplish this? The Mailman 3 server I want to migrate *from* was setup >> using Docker. The Mailman 3 server I want to migrate these lists *to* >> was setup using a python virtual environment via pip. > > If you can backup and migrate the database, that should do all of the Web stuff (except search index & logs) and most of the Core data. You'd need to additionally move the `var/` directory if you want to digests/logs/pending emails. At some point I would like to redo my MM3 instance to correct 2 bad decisions I made when I installed it: 1) using sqlite3 in production, and 2) using the Ubuntu packages, which are way behind current stable (~1 year). I’ve seen mentioned that it’s not as simple as dumping the sqlite3 database and restoring it to, say, Postgres because some of the data types are different between them (which seems like an odd design choice). Anyone sorted this kind of migration out yet? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years

[MM3-users] Renaming a server after building

by Philip Colmer

We're getting closer to migrating from Mailman 2 to Mailman 3. In preparation, I want to get new servers built ready to accept the migrated data from our old MM2 servers before we shut them down. So, the new servers will be something like "new-lists.example.com" to complement the existing "lists.example.com" servers. When we are ready to do the migration, we'll rename the MM2 servers to "old-lists" and rename the MM3 servers to "lists" and then migrate the data. Looking at the settings in the Django admin interface, I *thought* I had figure out how best to do this: - Under /admin/sites/site/, click on the existing domain name and change it to match the correct FQDN. - Under /admin/django_mailman3/maildomain/, click on the exist mail domain and change the mail domain to match the correct FQDN. However, although the above works, if I then go back to the *Mailman* interface and go to /mailman3/domains/, the web interface recreates a domain for the original domain name that was in place when the server was created, i.e. we end up with "lists" and "new-lists". We've tried deleting that "new-lists" domain, rebooting and trying again but "new-lists" keeps on being created again. What am I overlooking here? Is there a better/approved way to achieve what we want to achieve? Thanks. Philip

4 years, 5 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Steve Brown

Genius. Yes, the bodyhash_mismatch is in the DKIM stuff, and the message returned from MM3 has a footer attachment. Although I had modified the default to contain no content, it is still 129 bytes. Second, the reason why I saw different behavior from my posts and my wife's was that she wasn't a member. When I made her a member and sent another post from her address, the bounce+ address showed up in the nonmember list identically. So all of this has something to do with how our email host handles the outgoing mail. TMD uses Mailgun as a mail handler that provides deliverability services. I have a ticket in to them, but haven't heard back. Mailgun appears to modify the return path to a bounce+ address that MM3 sees as a nonmember sender, and then the recipient's email handler sees it as equivalent to another address that might be in the envelope. The header of a message sent from steve(a)stevebrown.us to my radg.us address shows: spf=pass (fr-int-smtpin1.hostinger.io: domain of "bounce+906d23.99dcd9c-administrator=radg.us(a)stevebrown.us" designates 143.55.232.17 as permitted sender) smtp.mailfrom="bounce+906d23.99dcd9c-administrator=radg.us(a)stevebrown.us"; I think I have bothered you enough for something that does not seem to create any real problems or threaten to do so. So reply only if something here stimulates another thought.

1 year, 7 months

[MM3-users] Re: How to remove a nonmember from a list

by Abhilash Raj

On Thu, Apr 9, 2020, at 3:25 AM, skenny(a)scss.tcd.ie wrote: > Thanks for that Abhilash. I've since figured out how to add and remove > nonmembers using the REST API. > > Regarding the web interface, I wonder could you comment on the > following: I've created a test list and I have added a large number - > 1,800 - of nonmembers to it. I find that if I try to delete a > nonmember via the web interface, it seems to hang, and then the > following message appears: > > Something went wrong > Mailman REST API not available. Please start Mailman core. > > The same operation succeeds on other lists, where the number of > nonmembers is not large. Do you think this could be an issue of scale? Could be, I am not sure which operation is it stuck at. Can you check logs to see where is it breaking? Can you try doing the same with the REST API, just to verify if it is the Core which has the issue or it is the web frontend. Abhilash > > Thanks > Stephen > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years

[MM3-users] Re: Replace "visit your dashboard" with URL link, like in Mailman 2.

by Mark Sapiro

On 5/8/23 09:52, Mark London via Mailman-users wrote: > Has anybody attempted to change the format of the emails that are sent > to the owner of a mailing list, to include a URL, instead of stating > "visit your dashboard"? The former is the behavior of Mailman 2. Many users, e.g. Jens Günther whose replied to this thread, have made custom templates to do this. > Is there any reason why this can't be done? If nobody has tried to do > so yet, I'll give it a try myself, as I'm familiar with django. Thanks. See https://gitlab.com/mailman/mailman/-/issues/901 and https://gitlab.com/mailman/mailman/-/issues/1055 Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for some documentation of templates, but note that you don't need to set URI's via REST, You can place list specific templates in Mailman's var/templates/lists/<list-id>/<lc>/ directory, domain specific templates in var/templates/domains/<domain-name>/<lc>/ and sitewide templates in var/templates/domain/site/<lc>/ or you can create list and/or domain specific templates via Postorius but see https://gitlab.com/mailman/postorius/-/issues/366 -- 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: Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Thomas Möhle

Hey Mark, thanks for your reply!> In what way? Do list posts get delivered? What works and what doesn't? > What are the observable symptoms for things that don't work? Yes, mails are not delivered. You can send a mail to the mailinglist without getting a bounce, but you will not receive the mail back through mailman. In addition to that, I'm unable to edit mailing lists in the web interface. After clicking on a list, I'll get a 404. Plus, I noticed that mailman is constantly writing files to /var/lib/mailman3/queue/out/ but they seem to get deleted right away again. I'm getting alot of IO there though. > What do you get for example if you go in a web browser with hyperkitty > running to > > https://mail.bitkomplex.de/mailman3/hyperkitty/api/mailman/urls?mlist=landw… I get a small gziped json file back. Key is "url", value is a link to a message. > And please don't post secret keys and change the value of api_key: in > mailman-hyperkitty.cfg and the corresponding value in > MAILMAN_ARCHIVER_KEY in your Django settings. I actually tried to redact the logs and config files, but I must have failed to save my edits on that one file. I'll change it right away.

4 years, 8 months

[MM3-users] Re: [Mailman-Developers] How to know the URLs for CURL while getting or modifying the data of mailman 3

by Shashikanth Komandoor

Stephen, Thank you for your response. I am sorry for getting confused between two lists mailman-users and mailman-developers. Developers may be busy and my question may be basic but still there is a space for more politeness at your end to advice me. Apart from that, you have given a lot much of useful information which is really and honestly helpful for me to the maximum extent. Now I shall take the help of members of mailman-users only. @mailman-users@mailman3.org <mailman-users(a)mailman3.org>, Team, I have installed Mailman Version 3.3 and running in production. Our development team developed another application which requires the access of the REST API and do changes over the MM3 DB automatically without manual intervention. That application would be connecting to REST API over http or https protocol To achieve this I have enabled the REST API to run at all the IP addresses of my MM3 Server by editing the mailman/src/mailman/config/schema.cfg file. I was able to run few commands like creation of domains, lists, list configuration changes for testing using the CURL (GET, POST, PATCH, DELTE) and got succeeded. But for every operation I need to write a different URL for CURL command to work. Out of many operations I require, addition of members to a list and removal of members from a list are most important tasks. So, I request herewith, from the URL https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html, I could see many URLs but they are executed at python prompt (>>>) only. I require URLs usable at the CURL command. Is there any way I could generate the URLs or any where documented regarding the URLs usable with CURL for the addition and removal of subscribers ? On Sat, Apr 25, 2020 at 8:04 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Shashi, > > This whole thread is off-topic for the developers list. This list is > for development of Mailman, not for teaching people to use it. Read > the whole recommended documentation before you ask busy developers to > tutor you in very basic things. There's a mailman-users(a)mailman3.org > list for users to help each other. All of the Mailman developers who > might be willing to answer your questions are there as well, but there > are also many experienced users, some of whom have experimented with > the REST API who will also help. Please reply there for further > help. (Reply-To is set.) > > That said, there are plenty of URLs in the API documentation. Here's > a hint: search for "dump_json". That function takes an URL. You may > want https: instead of http: in your URLs, and you may need to change > the port from 9001, depending on the configuration of your REST > server. Try it with simple GET requests for information first, such > as for domains or lists. You can also do these requests with an > ordinary web browser, though I don't know what it will do with the > JSON-formatted reply. > > If you don't have domains and lists configured, I suppose the > informational requests will come back as empty JSON objects. It > should be safe to make them. You can either use Postorius to > bootstrap a few example domains, lists, and users, or (the hard way) > figure out how to POST appropriate requests. I don't recommend trying > to update the backend DBMS by hand; the schema is quite complicated. > I don't know how to use curl to update Mailman's databases. That > requires a POST request which I have never done with curl. The POST > request needs to be valid JSON. > > The more I think about this, the less I think your idea of using curl > is worthwhile, because formatting JSON requests by hand is going to be > a real annoyance and a great way to mess up your database with > spurious information. You're really going to want programmatic > support for this. But that's already all available in Python in the > Mailman system. > > It's up to you, but I feel a responsibility to warn you that using > curl is not going to be simpler than learning enough Python to do > these things. > > Regards, > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/16/23 18:55, 朱超 wrote: > > Hi, When I subscribe the email list in Subscription Policy is > > confirm, Some problems happen in here： > > 1.Some mail mua reject send the confirm the message, because the > > length of recipient is too long. for exmaple: > > requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, > > and the mail mua reject to modify about this. > > The default English template says in part: > > Before you can start using GNU Mailman at this site, you must first > confirm that this is your email address. You can do this by replying to > this message. > > Or you should include the following line -- and only the following > line -- in a message to $request_email: > > confirm $token > > I.e. It gives an alternative method if `reply` doesn't work. You can > provide a custom version of this template with different wording if you > think you can improve it. The problem is the reply address, though. Changing the template to suggest only the "confirm $token" in body method doesn't help people who hit R expecting that should work, especially since many "user fiendly" (misspelling intentional) MUAs don't display the address. Avoiding that requires code changes, I guess? > > 2.It is inconvenient for users to use. Many people will > > mistakenly think that after clicking the subscribe button, it > > will be successful, and they will not process the email. > step, you can set Subscription Policy to Open, but then anyone can > maliciously subscribe third parties to the list. *Please* do not do this if your server is exposed to the Internet. There are bots that search for such servers, and sell lists of them to people who want to DOS mailboxes. You may find yourself banned across the Internet. The only real alternative to confirmation is approval by moderators. I believe Mailman 3 offers that alternative as Mailman 2 did, can't check at the moment. > > Regarding the discussion on the subscription method of the > > mailing list, should we consider optimizing the subscription > > method of the mailing list, for example: > > 1. use the method of sending a verification code to subscribe by > > email，When you receive the verification code sent by the > > mailing list and fill it in again, you can subscribe > > successfully。 > > How is this different from the present method. Just wording. I think they are thinking of the "invite" option that was provided in Mailman 2 mass subscribe (again, I think Mailman 3 retains it but I never ever used it so I don't recall for sure). But it doesn't make sense for a user-initiated interaction. > If you want, you can make > a custom template and include something like: > > Alternatively, you can confirm by going to the URL > > https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token If I understand the OP's PoV correctly, I think I would change the list information page to say "Send a personal invitation to join the list to [email address here]. If you aren't a subscriber, you can invite yourself." And change the word "confirm" in the confirmation template to "subscribe". > We don't include that in the default template because Mailman core > doesn't know if you even have a web UI or how to access it if you > do. We should fix that, at least if the web interface is Postorius (wishlist, assigned to me): https://gitlab.com/mailman/mailman/-/issues/1055 @mark https://gitlab.com/mailman/mailman/-/issues/901 Maybe we can close this? I'm not sure why it was left open since there's no action proposed for Mailman improvement. > > 2. use the email to send a connection to confirm the > > subscription，People click the link to be redirected to a > > confirmation page to subscribe to the email。 > > See above. Indeed, AFAICS almost everything the OP is suggesting amounts to an identical procedure as far as the Mailman server is concerned, it's just described to the subscriber differently. The one exception is the suggestion to eliminate the confirmation step, and while that is supported, it's quite likely to cause problems for third parties and eventually for the Mailman site unless you have an alternative ground source of truth such as an employee database. Steve

3 years, 3 months

[MM3-users] Re: Anyone integrated Single Sign On like Azure SSO with Mailman3?

by Ryan Morash

Since mailman-suite is already using allauth, I was able to easily enable the Microsoft Graph provider: https://django-allauth.readthedocs.io/en/latest/providers.html#microsoft-gr… From: Gilles Filippini <gilles.filippini(a)free.fr> Date: Wednesday, July 29, 2020 at 1:11 PM To: Jacob Bargery <jbargery(a)smccme.edu>, mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Anyone integrated Single Sign On like Azure SSO with Mailman3? Hi, Jacob Bargery a écrit le 28/07/2020 à 22:28 : > We are looking at whether it is possible to integrate Azure Single Sign On with Mailman3 to streamline use for our users, has anyone had any luck with doing this? If so, how did you go about doing so? I did such a thing with LemonLDAP-ng and the OpenID Connect protocol. I just had to add the django module mozilla-django-oidc and a custom logout method. The mozilla-django-oidc documentation [1] was quite helpful. [1] https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fmozilla-django-oidc.rea… Best, _g. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.mailman3.org%2fma… Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

5 years, 9 months

[MM3-users] Re: mailman-suite scheduled tasks

by Eric Broens

Thanks Morris!Since I included it in the crontab of the mailman user I could leave out the user: @hourly /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings Clear skies!Eric On Saturday, December 5, 2020, 11:39:41 PM GMT+1, Morris Jones <mojo(a)whiteoaks.com> wrote: On 12/5/2020 2:12 PM, Eric Broens via Mailman-users wrote: > Hi, > The documentation https://docs.mailman3.org/en/latest/config-web.html includes a section on scheduled tasks that need to be included in cron. > "runjobs" seems to be available only from "manage.py". > Do these scheduled tasks need to be executed from the python virtual environment?If so, is there a way to do that directly from cron, or should I create a script for these tasks which can be called from by cron? Eric, here's an example from my mailman crontab. By calling the django-admin instance from the virtual env, it gets picked up automatically: @hourly mailman /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings (Hopefully the line wrap won't munge the line too badly.) Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com> _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 4 months

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Wed, Dec 14, 2022 at 8:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > 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 lack of style is the main issue. > 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. > So I have tested this with Brave, Google Chrome, Firefox - all on MS Windows and I do clear the browser cache. > I don't know about the latter - could it be because all the archives are > private and I'm, not logged in? > Even when logged in, the situation is the same, unfortunately. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 4 months

[MM3-users] Re: Social signup?

by Duane Raymond

HI Mark, On Sun, 12 Mar 2023 at 22:06, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/12/23 13:56, Duane Raymond wrote: > > Is there a way to enable social signup (vs just login for existing > users)? > > It isn't at all clear or documented, but a user without an account can > go to the login page and login via a social account button and this will > create an account connected to that social account and log the user in. > Thanks for clarifying. Once I implemented social login, the buttons for social login did appear fine on the login page, but not on the signup page. I noticed for this list as well, there are no social signup buttons. So if it works, how does this happen? 1. Is there something I am missing adding to my settings.py and settings_local.py files to make it appear on the Posterius/Hyperkitty signup (vs login) page? (I searched but couldn't find anything) 2. Do I manually add this code to the Posterius/Hyperkitty signup template? 3. If a user tries to login via the login page and isn't registered will it be counted as a signup? 4. something else :-) I'm trying to get my head around where this is working from / what I need to do to get social signup obvious on the signup page (or other route) Cheers, Duane

3 years, 1 month

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

by Florian Fuchs

On Fri, Dec 02, 2016 at 11:07:24AM -0500, Barry Warsaw wrote: >Hello Mailman 3 users and developers! > >It's been a long slog but I think we are finally ready to begin the release >process for Mailman 3.1. I am pretty happy about the state of the Core, and >Florian is going to do some more integration testing with HyperKitty and >Postorius. We still have a few issues and a merge proposal or two to address, 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 did all of my testing locally, which has some limitations. So I started setting up a more realistic environment on one of my dev machines. But I'm not done yet. Will report back when I'm done... ;-) >but I am planning to spin a beta of Core this weekend to facilitate testing. I think it's OK to put out a separate beta of the core, because the version pulled from pypi will still be 3.0 if I'm not terribly mistaken. For the real 3.1 we should probably do a coordinated release of all components, once everything's tested a little more thoroughly. Cheers Florian

9 years, 4 months

[MM3-users] Re: Can creating too many Django accounts crash Mailman3 server?

by Abhilash Raj

On Tue, Sep 15, 2020, at 12:09 AM, Stephen J. Turnbull wrote: > Mohsen Masoudfar writes: > > > It seems anybody can go to the site: > > https://LISTSERVNAME/mailman3/postorius/lists/ > > and click on the [Sign up] on the top-right corner and create an > > account. > > Yes. > > > This can easily be automated, even though the next step, confirming > > the email address, being ignored. I believe it can be used as a > > target for a DOS attack by creating so many accounts, that > > eventually causes an 'out of space' error. > > > > Is this a justified concern? > > "Justified" depends on who you think the attacker is. Theoretically > it's a real possibility, but the space used by an unverified account > is not large. I suspect there are always much more painful DoS > attacks to worry about. > > > Is there a way to manage this feature in a secure way? > > In some sense, I don't think there is. The point of the feature is to > allow anybody to sign up without authentication beyond having a usable > email address. Either you allow the DoS attack or anything you do is > likely to deny service to legitimate users. > > Brian's approach (cron job purging unverified users) is generally good > hygiene, but I don't think it would do much against an deliberate > attack. And it shouldn't be hard to automate the confirmation > process. I guess you could handle that by purging accounts with no > subscriptions or other roles on any lists, but that might annoy a few > legitimate users. > > Probably the best you could do for an open server would be to throttle > user creation to say 1 per minute (adjustable to the scale of your > site). > > I don't know if there is currently a way to require admin approval for > account creation (as opposed to list subscription). Perhaps we should > add that if we don't have it. I checked django-allauth, it doesn't have a feature like that. We could implement something on-top of that to optionally allow for admin approval but some other details would need to be figured out and would be a sizeable task involving a new view for account approvals. We potentially also would have to modify the models used in django-allauth to add the flag for "approved", which I am not sure would be an easy task to figure out. Perhaps, it might be easier to make a feature request and implement it in django-allauth though. > > Steve > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 7 months

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Mark Sapiro

On 5/17/18 3:35 AM, Henrik Rasmussen wrote: > > I am also concerned that new lists are created with a subscription policy "Confirm" as default, rather than at least "Moderate", which can cause people to be subscribed by others against there will. I'm confused. Confirm sends a confirmation request to the subscribed address which must be acted upon by the user before she is added to the list. Moderate just means approval by an owner/moderator which, it seems to me is more susceptible to a 3rd party subscribe succeeding - i.e., subscription requires membership in some organization. A subscribes B who is a member of the organization but doesn't want to be on the list. The moderator verifies that B is an organization member and approves the subscription. Granted, it may be possible for some brain-dead vacation responder to confirm a subscription request, but that's a separate issue. > Also, regardless of this setting, administrators can subscribe people without their knowledge. Granted that this can be abused, but not allowing admins to directly add members will probably create more problems than it solves. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: Mailserver Log entries following through mailman?

by Mark Sapiro

On 11/10/23 12:39, Andreas Barth wrote: > > is there some way to find an ID to follow an email through mailman? In > the exim logfile there is only something like C="250 Ok" (whereas in > mails sent to another exim there is something like C="250 OK id=…"). > (What I sometimes need to do is to follow an mail whether it is sent > through mailman and to where.) Every message should have a unique Message-ID: header. According to my reading of https://www.exim.org/exim-html-current/doc/html/spec_html/ch-log_files.html Exim should create a => log entry with an id= field containing the Message-ID when the message is received for delivery to Mailman and another similar entry when the message is received from Mailman for delivery to one or more list members. Mailman itself logs ACCEPT:, HOLD:, DISCARD:, REJECT: and OWNER: entries in mailman.log for those events (OWNER: indicates a message to list owners). All these entries contain the Message-ID. Mailman's smtp.log contains 'post to' and 'smtp to' entries with Message-IDs for all outgoing messages. > Or should I raise an issue as whishlist request? What exactly would you wish for that Mailman can 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, 5 months

[MM3-users] Re: Display the last post time for a list or all lists.

by Mark Sapiro

Mark Sapiro wrote: > It wouldn't be difficult to do, but at the moment, it wouldn't provide anything useful because of <https://gitlab.com/mailman/mailman/issues/453>. The issue is now fixed in the branch head at least. The script corresponding to https://www.msapiro.net/scripts/last_post.py would be almost identical except for changing real_name to display_name, last_post_time to last_post_at and fixing the print for Python 3. Also changing the string interpolation to format(), it becomes: --------------------------------------------------- import time def last_post(mlist): print('{}: Last post at {}'.format( mlist.display_name, time.ctime(mlist.last_post_at) )) --------------------------------------------------- The only issue with the script is for a list which has had no posts since #453 was fixed, mlist.last_post_at is None and time.ctime(None) is the current date and time. That too could easily be fixed like: --------------------------------------------------- import time def last_post(mlist): if mlist.last_post_at: print('{}: Last post at {}'.format( mlist.display_name, time.ctime(mlist.last_post_at) )) else: print('{}: No posts'.format(mlist.display_name)) --------------------------------------------------- The trickier part is the Mailman 3 mailman withlist command has no option to run for all lists, so you'd need to run it something like #!/bin/sh for list in `mailman lists -q`; do mailman withlist -r last_post -l $list done -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: Running mailman shell commands in a script

by Eggert Ehmke

Thanks, that works for me. Am Dienstag, 14. September 2021, 20:31:59 CEST schrieb Abhilash Raj: > On Tue, Sep 14, 2021, at 4:57 AM, Eggert Ehmke via Mailman-users wrote: > > Hello, I understand that the mailman shell is basically interactive. I > > need to run some actions as adding and deleting users in a Linux shell > > script, or even from another python program. How does that work? > > Check out mailman members, addmembers, delmembers, syncmembers > commands[1] and see if they do what you are expecting the Mailman2 commands > to do or you need something more. > > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d > ocs/commands.html > > If you are using another Python program, then you can rely on > mailmanclient[2] python package for operations on lists and memberships > using Mailman's REST API. > > [1]: https://pypi.org/project/mailmanclient/ > > > In fact, I miss the commands that were in the bin directory of the old > > mailman2 installation. Wouldn't it be nice to add them again to mailman3? > > > > Cheers, Eggert > > > > > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 7 months

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Stephen J. Turnbull

Ibiam Chihurumnaya via Mailman-users writes: > I had done the members part in the past, but the issue with it was > I wanted certain members to not receive messages from the list, but > only send to the list. As Mark explained, you can set those members to 'Default Processing' in the moderation option, and to 'No Mail' in the mail options. In that case they or list owners could reset them to receive mail. The alternative is to add the addresses one by one as non-members and set their moderation. In that case they cannot receive mail, although they may be able to subscribe themselves depending on list settings, or an administrator could subscribe them. In both cases the nonmember would remain unless removed by an administrator. In both cases, although you can add members with mass subscription, there are no "mass" operations to update the subscription option or to create non-members in Postorius, you need to do it one by one. You can automate that by using a loop over a list of addresses in Mailman shell, or if you expect to do it more than once, you could create a withlist script to use with the -r option. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months

[MM3-users] Re: Mailman runners missing - nothing in logs

by Mark Sapiro

On 1/18/20 6:13 AM, Torge Riedel wrote: > > So now back to good. I checked all the logs prior to restarting the > service in directory /opt/mailman/var/log, but I do not see any errors. > And the master was still running, I would expect that the master will > start / restart a runner in case it died? What's in /opt/mailman/var/log/mailman.log? There should be entries like Jan 18 13:51:11 2020 (11700) xxxx runner started. for each runner every time it starts and like Jan 18 13:47:31 2020 (10096) xxxx runner caught SIGTERM. Stopping. Jan 18 13:47:31 2020 (10096) xxxx runner exiting. for each runner every time it stops, but with perhaps a reason other than `caught SIGTERM` That should at least tell you when they stopped. Also, if they stopped for some reason. The master will only restart runners that exit if they exit because of SIGUSR1 or some internal error and even then, only the configured max_restarts number of times. Do you have a logrotate script for the logs in /opt/mailman/var/log, and if so, does it have a postrotate script that signals Mailman to reopen logs other than by a `mailman reopen` command, perhaps by signaling the master with other than SIGHUP? -- 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: Question about whitlisting a domain for specific mailing list

by Zaheer Abbas

Thanks, Mark & Odhiambo for providing options for the solution. I will try the 'postorius header filters' hacky way as it's more suitable to my requirement, however, if it didn't work as expected, then filtration through exim filter is also an acceptable option. Thanks again for the quick response. On Thu, Mar 30, 2023 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/30/23 11:07, Odhiambo Washington wrote: > > So the MTA option that doesn't involve any regex is better than no? > > Partly it's a matter of taste and possibly a matter of necessity. I.e. a > list admin can do this with header filters and may not have access to > the MTA config. > > Also, it's not clear to me that doing this in Postfix is less > complicated than understanding a regex. > > -- > 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 zaheer.psg(a)gmail.com >

3 years

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

by Mark Sapiro

On 12/02/2016 08:07 AM, Barry Warsaw wrote: > Hello Mailman 3 users and developers! > > It's been a long slog but I think we are finally ready to begin the release > process for Mailman 3.1. I am pretty happy about the state of the Core, and > Florian is going to do some more integration testing with HyperKitty and > Postorius. We still have a few issues and a merge proposal or two to address, > but I am planning to spin a beta of Core this weekend to facilitate testing. Barry, I understand you need to feel comfortable about everything going into the core and this takes time and energy to review all the MRs, but I think it is pretty important to get the DMARC mitigations into the core. If there's anything I can do to help with this, let me know. I will rebase my branch again and possibly make one minor tweak, but I think it should be OK. I can also work on Postorius. Also in this vein I have a question. Should the DMARC settings be added to the Alter Messages tab in the List Settings view or would it be better to have a separate DMARC Mitigations tab. -- 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: New messages not being archived

by Mark Sapiro

On 7/8/21 1:03 PM, Mark Sapiro wrote: > On 7/8/21 8:35 AM, Sarah H wrote: >> >> When trying to add a new thread via the hyperkitty interface I can see >> the email go through the maillog, I get the email with the entered >> content and everything else works, it just doesn't add a new thread to >> the archive. > > What if anything is in Mailman's var/archives/hyperkitty/spool/ directory? > > Do you have something like > ``` > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > ``` > in your mailman.cfg? Do you then have > ``` > [general] > base_url: ... > api_key: ... > ``` > in the mailman-hyperkitty.cfg file and is base_url set to a url tha > accesses hyperkitty and is api_key set to the same value as the > MAILMAN_ARCHIVER_KEY is your Django settings - quoted in settings but > not in mailman-hyperkitty.cfg, i.e., > ``` > api_key: xxx > MAILMAN_ARCHIVER_KEY = 'xxx' > ``` > I see that these settings are not covered in the virtualenv installation guide at https://docs.mailman3.org/en/latest/install/virtualenv.html. This is now https://gitlab.com/mailman/mailman-suite-doc/-/issues/32 and we'll fix that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Mailman not able to process "big" requests

by Abhilash Raj

On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: > Hi, > > We migrated from mailman2 to mailman3 a week ago. Since then we are > unable to send messages the our students through the mailing list. > Here are some symptoms: > > 1. I go to mass subscribe and subscribe 400 emails > 2. I click subscribe, the browser (in my case safari) tries to load the > page for a few seconds > 3. The request times out > 4. Once the service becomes responsible again, I see that only part of > my emails got subscribed (~50 in this case). > > For me this really looks like the emails are sent on the "web-thread" > that gets killed once the request times out. > Looking at this > https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p… > <https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p…> > seems to confirm my suspicions. Yes, you are correct. Mass Subscription current just subscribes each address one-by-one and thus times-out. I have created an issue for this https://gitlab.com/mailman/postorius/issues/264. > > Some quick overview of our infrastructure: The TCP endpoints are: > browser -> haproxy in kubernetes-entry-router -> nginx in kubernetes- > ingress -> nginx in mailman -> mailman I would very much appreciate if you'd share you configuration and/or a blog post on your setup. I have been trying to set Mailman use Kubernetes for a time, but haven't had time to do it. > We mitigated the issue by giving it more CPU power and increasing the > timeouts in one of the nginx endpoints. > We also have a problem with sending out emails to "large" (>50) groups, > as they seem to not getting sent out at all. Do you have any idea what > the problem here could be? Which MTA are you using? What do you see in mailman's logs and MTA's logs? I haven't seen this kind of problem before with Mailman 3. This very list is hosted using Mailman 3 and I believe has more than 50 subscribers. > > We would be really glad if you can help us getting our mailman up and > running, as I currently have to send emails out by "hand". > I will happily provide you with more details about our configuration, > just let me know what you need. > > Kind regards, > > Jonas > > Jonas Felber <jonas.felber(a)vis.ethz.ch <mailto:jonas.felber@vis.ethz.ch>> > Aktuar & CTF Präsident > > VIS - Verein der Informatik Studierenden an der ETH Zürich > CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich > https://www.vis.ethz.ch <https://www.vis.ethz.ch/> > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

8 years

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

by Christian Stalberg

mailman.log is showing this: ERROR 2021-10-18 22:19:12,385 616 django.security.DisallowedHost Invalid HTTP_HOST header: 'subdomain.domain.tld'. You may need to add 'subdomain.domain.tld' to ALLOWED_HOSTS. ERROR 2021-10-18 23:01:15,318 616 django.security.DisallowedHost Invalid HTTP_HOST header: '192.168.0.1'. You may need to add '192.168.0.1' to ALLOWED_HOSTS. Where do those entries go? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 11:44 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: installing a new instance of mm3 On 10/22/21 6:37 AM, Christian Stalberg via Mailman-users wrote: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 As Steve said, it should be. > Brian installed my instance. Now its broken. My lists are down. I'm > getting nowhere with diagnostics and troubleshooting (which was easier > with mailman 2). What's broken? Postorius, Hyperkitty, mail delivery, all of them? Do you find any clues in the logs at /opt/mailman/mm/var/logs/? Particularly mailman.log for core and mailmansuite.log for Postorius and Hyperkitty. We will try to help if we have information to help identify the problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 6 months

[MM3-users] Re: Mailman3 equivalent of list_owners binary

by Odhiambo Washington

On Thu, Oct 2, 2025 at 6:39 PM <l.reilly(a)ucl.ac.uk> wrote: > Hi, > > In our Mailman 2 environment we have a script that uses the binaries > 'mailman/bin/list_owners' and 'mailman/bin/sync_members' to keep a list of > owners up to date. This is handy for sending out service notifications to > all list owners. Unfortunately, there doesn't seem to be an exact > equivalent in Mailman 3 for list_owners. > > I've tried using the command 'mailman members --role administrator > LISTSPEC' whilst looping through each list from the output of 'mailman > lists'. It almost does the job, but in cases where an owner has a display > name set the sync fails as it cannot parse these lines. > > e.g. Cannot parse as valid email address (skipping): Smith, John < > john.smith(a)example.com> > > I can probably try to clean the output of "mailman members" before doing > 'mailman syncmembers'. I just wondered if anybody is doing something > similar and has a better approach I'm missing? > Chatgpt :) -- 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]

6 months, 4 weeks

[MM3-users] Re: List of "site admin" commands in Mailman 3.1 docker-mailman

by Abhilash Raj

Hi Henrik, On Mon, Jul 17, 2017, at 07:55 AM, Henrik Rasmussen wrote: > I am new to all of Python, Django, Docker, Docker-compose and everything > else used by docker-mailman. I have managed to get a webinterface of > Mailman 3.1, I installed using Docker and Docker-Compose from > github.com/maxking/docker-mailman, but my config is still bogues > (probably just my Apache-config). > > I'm quite confused about Mailman 3 documentation regarding those commands > the site admin would do in Mailman 2 like list_members, config_list -o > etc.)., and I have been trying to figure out what documentation regards > the development of Mailman 3, what regards the final version 3.1 and what > I am supposed to do regarding Docker. > > > 1) Should I enter the container using "docker exec -it mailman-web > bash" and run "python" in order to get a python prompt, and from there > run commands like those documented at > mailman.readthedocs.io/en/latest/src/mailman/commands/docs/control.html > ?. Just to add to what Barry mentioned, the in docker command above, you should enter the `mailman-core` container instead of the `mailman-web` container if you are looking for the command line options of Mailman Core. so it should be something like: $ docker exec -it mailman-core bash -- thanks, Abhilash Raj

8 years, 9 months

[MM3-users] Re: Mailman3 Docker question and importing lists from MM2

by Andrew Hodgson

bin/mailman import21 I saw this in the image, do you have any idea about what may be missing from this? I may shelve this project again for the time being if we can't do the migration, but good to know I can get a production like Docker instance running relatively painlessly. Andrew. -----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: 01 September 2017 16:43 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman3 Docker question and importing lists from MM2 On 09/01/2017 07:09 AM, Andrew Hodgson wrote: > > I had a question regarding the parameter: SERVE_FROM_DOMAIN. > > I want to use multiple domains, what is the best way to specify multiple domains in this environment variable? I don't know the answer to this. > Furthermore, is there a recommended way to get data from MM2 (list configs and archives) into MM3? There are two things. For importing list configs there is bin/mailman import21 but it is not up to date and probably doesn't work. For importing archives there is django-admin hyperkitty_import [--settings=if.needed] which works well using the MM 2.1 LISTNAME.mbox/LISTNAME.mbox file as input. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list mailman-users(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 7 months

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

by Allan Hansen

Hi Stephen, Thank you for your response. I have let my users/moderators know how few resources are available for developing Mailman - that it’s not a system supported by hundreds of highly paid developers, testers, security experts, product managers, etc., and that the software is public-domain code. My own involvement in this is similar to yours. A note to flush bounces to people upgrading may be a good idea. And yes, the disabled accounts were mostly on busy lists, but not all. I should also mention that a heck of a lot of them were sbcglobal.net users, which was interesting. AT&T apparently is not doing a good job for their clients (and they do have armies of staff who could). Maybe your users have better service providers than mine. As for looking at subscription options, I have an authenticated (verified) Django account that I use for testing (non-owner but moderator). When I log in to that account (or as list owner with my usual account), the only field that is filled out in the ‘Subscription options’ dialog is the ‘Select Email’ pulldown menu. So yes, I think that there is an issue here. I agree with you that to provide access to this information for people who don’t have verified Django accounts does not make sense. But those who have set up accounts should, and the moderators and owners definitely should. If not being able to see these settings is specific to my installation, I would appreciate getting it fixed. If needed I can provide screen shots to prove authentication and issue. Once a setting is modified, it becomes visible then and afterwards! I thought about contacting you all at the time, but figured that I needed to get this done promptly (based on the reactions from my users/moderators, which were very prompt). :-) Finally, about the ‘Change Address’ feature: It’s really not complicated, Stephen, or rather, it should not be. People all the time move from one provider (like sbcglobal, hopefully) to another (like gmail). When they do, they generally want all instances of their old address strings everywhere necessary in Mailman/Postorius to be replaced with the new address, so they can use that instead. This is how the ‘Apply Globally’ address change worked in MM2 and that was more than good enough. If there are other use cases where they need to retain the old address for whatever reason, they would not use this feature, but add the new address to their account and then manage the old in some other way. Of the thousands of subscribers I have, maybe a handful are interested in maintaining more than one subscription address. All the rest simply use one address and when they get a new email address they want to use that instead for all their subscriptions everywhere and never see the old one again (other than in the archives, of course). Period. It’s really that simple in 99.9 % of the cases. Please don’t hold this up for the 0.1%. Yours, Allan

5 years, 2 months

[MM3-users] Long-shot cry for help

by David Partain

Hi, I'm having severe operational issues with my mailman3 site. My site is built on standard Ubuntu packages (18.04), and they're ancient. I'm having two big issues... 1. I have the old smiley problem that I've had from the very beginning and never solved. I have added 'charset': 'utf8mb4' to the relevant config file (/etc/mailman3/mailman-web.py), but that hasn't "taken", in the sense that the calls to mysql do not include the charset stuff. /usr/share/mailman3-web/settings_local.py links to /etc/mailman3/mailman-web.py and there is no file /usr/share/mailman3-web/settings_local.pyc. I moved it out of the way hoping it'd get re-built, but it has not been in the months since. The result of this that I get hundreds of mail messages to root (thousands, really), rapidly filling / with mail in /var/mail/root and logging in /var/log/mail.log. The mail has something like "Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive" and "DataError at /hyperkitty/api/mailman/archive (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0D\\x0A...' for column 'content' at row 1")" I have tried to trace to figure out what file is _actually_ controlling the calls to mysql. There's a file called /var/lib/ucf/cache/:etc:mailman3:mailman-web.py as well, but I have no idea what that is or if it might be used. Is there something like 'mailman info' for mailman-web so I can see what files are being used? I'd love to fix this... 2. There's this one curious cron job... * * * * * www-data [ -f /usr/bin/django-admin ] && python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings (yes, I know python2.7 is a problem... see the last paragraph below). These jobs start piling up. They run & run & run, and eventually the machine screeches to halt when it runs out of memory and goes belly up. This is a relatively recent development. After a while, I'll have 5 or 6 or more of these all running, looking something like this: www-data 6366 6364 99 15:00 ? 00:12:27 python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings What this means in practice right now is that I'm forced to go in and kill these on a regular basis or the machine _will_ die and people _will_ shout at me. Does anyone have any idea why these might not be finishing? Can I comment this out completely & live happier? Any help whatsoever? ----------------------------------- Finally, I should add that I know my current installation is fundamentally flawed because I chose to go with distro packages. I simply cannot fix it. My strong recommendation to others who follow me is that they do NOT do this. Bite the bullet and install via pip... I'm now in the process of setting up a new server that is completely based on the latest via pip installation. I have to get away from what I have or lose my sanity. Cheers, David

4 years, 10 months

[MM3-users] Re: One-click unsubscribe?

by Jered Floyd

> > If we add a timestamp to the encrypted token I suggest there should > > be a pretty broad window allowed (i.e. several months). > > I guess it would be a matter of keeping 2 tokens in the database. In the case we sign/encrypt a tuple of (list, subscriber, timestamp) we don't need to store anything in the database. We just check timestamp against our validity period and remove the subscriber for the list. This is simple, but I agree as discussed later that just having a random opaque UUID that corresponds per subscription-instance in the database provides a lot more flexibility/safety overall. Option 1: signed/encrypted tuple (list, subscriber, timestamp) Option 2: UUID referencing a unique subscription in the database Sounds like you are favoring the 2nd option? > > I agree with your analysis, but this would be a very specialized > > attack, especially if we don't provide direct feedback on if the > > request was successful (which we are not required to do). > > I think we do need to provide feedback, at least when the request > fails due to an expired token. RFC 8058 doesn't specify response codes or really any behavior in response to the POST request. The user never sees this interaction. On the other hand, in Postorius we probably want to support a GET interaction against the same URI which provides a page with a button that generates the equivalent POST. That means that the same URI can be used in a personalized footer as a (two-click) unsubscribe link. In that case, we will want the POST to generate a response that indicates success or failure. Incidentally, I imagine 8058 defines this as a POST interaction to avoid the mail-scanner issue we talked about last message. Mail scanners may follow links with GET requests, but are unlikely to generate POSTs. > > The real risk without a per-subscription random unique identifier > > would be a replay attack -- the user is unsubscribed multiple > > times? That feels outside of the threat model. > > The identifier has to be unique to the subscription. If there are > multiple valid unsubscriptions, the later ones won't have an existing > subscription to unsubscribe. That does argue for the nonce -- that > would stop the attack in the case where the user resubscribes. Yes, exactly -- I didn't mean multiple valid subscriptions at the same time, but rather serial subscriptions by the same subscriber (if they are maliciously unsubscribed). > > Regardless, not something we can do much about. > > There's hope. When Yahoo! and AOL broke the Internet in 2014 by setting > p=reject DMARC policies, the Ministry of Education issued "administrative > guidance" that *yahoo.* addresses should not be used for school business, > and my university sent them all to spam. ;-) Including yahoo.jp which did > not have a p=reject policy. Ah, to be outside the US, where the concept of consumer protections still exists... --Jered

4 months, 3 weeks

[MM3-users] Re: Mailman3 on virtual domains

by Mark Sapiro

On 10/7/23 09:25, Lars Bjørndal wrote: > [Mark] > > [...] > >> See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > Ok, so I have to create an alias_domain in Mailman. Is it possible to do that from the web interace? It has been in postorius since 1.2.0. > I find an Edit button for each domain, and then I may change name and description. But I can't find an option to add an alias_domain. As I'm blind, and using a text only browser, some information may have been missing. Or can I do it from the command line? If your Postorius is >=1.2.0, there should be 3 fields on the Edit domain page - Description, Alias Domain and Web Host. The whole page looks something like: Edit domain example.com Description Alias Domain Normally empty. Used only for unusual Postfix configs. Web Host The domain from which you want the web UI to be served from. This can be same or different from the Mail Host. You can edit the list of available web hosts here. You can also set an alias_domain in `mailman shell`. E.g., ``` >>> domain = getUtility(IDomainManager).get('example.com') >>> domain.alias_domain = 'x.example.com' >>> commit() ``` -- 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: Subscription Request asking for Confirmation instead of Moderation

by Henry Hartley

> -----Original Message----- > From: Stephen J. Turnbull <steve(a)turnbull.jp> > Sent: Thursday, August 28, 2025 12:27 > > Henry Hartley via Mailman-users writes: > > >>> 1. Are there particular headers that are causing the email > >>> to go to the Confirmation page instead of the Approval page? Or >>> are > there particular headers we can add that will help with this? > > No. That's entirely determined by the list's configuration. You cannot change > that behavior via a user's subscription request whether by email or web. IIRC, > the only overrides are either through the REST API, "mailman shell", or the > "mass subscribe" page on the web. (I guess it's possible that the moderator can > "pre confirm" at approval time, do you see such an option when you approve? > I've never managed a "moderate" list so I don't know without groveling through > the code.) > > Do you really only have one list? Is it possible that the misbehaving list is not > configured as you expect (ie, the list subscription policy is "confirm" or "confirm > then moderate")? Unlikely, but if you haven't checked since the problem > started, please confirm. I have 50 lists and they all have the "Subscription Policy" set to Moderate. If I send an email (e.g. from my gmail account) to the LIST-join address, it goes into the Subscriptions Pending Approval list, as it should. But, when sent from Drupal it goes to the Subscriptions Pending User Confirmation list. That's the weirdness that I'm trying to untangle. Nevertheless, I will have one of our testers subscribe through Drupal to a list and confirm that the issue happens every time. > Are you sure that the members have not been approved by some moderator? I > forget exactly how this works, but unless you use mass subscribe with the "pre > confirm" option set, the user will have to confirm before they can receive mail. The issue was reported by the moderator, who saw the email address in the wrong place. If the Subscription Policy is set to 'Confirm then Moderate' then ;First subscribers have to confirm, then a moderator needs to authorize.' Since it's set to 'Moderate' (only), then 'Moderators will have to authorize each subscription manually.' > > > > 2. Is there any way for us to move an address from the > > > > Confirmation Pending page to confirmed on the backend > > > > (preferably through the web interface, but on the server > > > itself, if > necessary)? > > Not that I know of, but what you can do is mass subscribe those addresses. I > think that you'll still end up with them waiting for confirmation as described > above. You can confirm them by accessing the database directly, but that's > more fraught than I want to deal with at bedtime :-). Until we figure this out, I've instructed the moderator to copy the address from the User Confirmation list and Mass Subscribe them and then remove them from the Confirmation List. It works but the moderators don't like it. > > Authentication-Results: spf=fail (sender IP is 192.168.0.0) > > smtp.mailfrom=SCHOOL.edu; dkim=none (message not signed) > > header.d=none;dmarc=fail action=oreject > > header.from=SCHOOL.edu;compauth=fail reason=000 > > This requires some care. DMARC is failing, and necessarily will fail. > If SCHOOL.edu has a p=reject policy, this mail should not get to Mailman at all. I'm pretty sure the outgoing mail from mailman is getting the right headers for DMARC but it definitely bears testing. > If the Drupal host is the Mailman host, then you could use the PHP script to talk > to the REST API instead of using email. Cutting out the long list of middlemen, so > to speak. (It would also be possible if they're different hosts, but the security > precautions I would recommend are quite a bit more severe.) Yes, Drupal and Mailman are on the same host. We definitely could rewrite our code to use the REST API, and in the long run, that would be good. But we brought this code over from government servers that were using Mailman2 and since it basically worked (except for this odd issue) we put that at a lower priority. But maybe we need to do that sooner rather than later. -- Henry Hartley

8 months

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

by Cathryn McGuire

"I think the header rule you have will hold any post with a Cc: to anywhere. If you want to not hold posts with a Cc: <neighbours(a)mailist.dunbar-vancouver.org> regardless of To:, you can do that by adjusting your header rules, but I don't think you want that." Our members are suddenly sending To: member or non-member and Cc: to our list (neighbours): From:Caroline Astell <astell(a)shaw.ca> MIME-Version:1.0 Subject:Re: [Neighbours] Re: Telus Landline Question Date:Fri, 14 Nov 2025 17:47:10 -0700 (MST) Message-Id:<2DD7F314-971B-41AB-9A62-CB14D575C11A(a)shaw.ca> References:<CAAGK_erkMQx=R+ita4KU-M2msvXaQFWjiM5=ssjDMpb-4WrVpw(a)mail.gmail.com> Cc:neighbours Mailist Dunbar <neighbours(a)mailist.dunbar-vancouver.org> In-Reply-To:<CAAGK_erkMQx=R+ita4KU-M2msvXaQFWjiM5=ssjDMpb-4WrVpw(a)mail.gmail.com> To:Beverly Dunne <dunontime(a)gmail.com> X-Originating-IP:[72.143.235.33, 72.143.235.33] X-Mailer:Zimbra 10.1.10_GA_4785 (MobileSync - Apple-iPhone12C1/2207.100) Thread-Topic:Telus Landline Question X-MailFrom:astell@shaw.ca X-Mailman-Rule-Hits:header-match-neighbours.mailist.dunbar-vancouver.org-0 X-Mailman-Rule-Misses:dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation So, I think it's like you said: "the header rule will hold any post with a Cc: to anywhere." You hinted there's a way to not hold posts with a Cc: to <neighbours(a)mailist.dunbar-vancouver.org> by adjusting our header rules, but I think yes, now we do want that. What would that header rule look like? Thanks Mark, Cathryn

5 months, 2 weeks

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

by Ken Alker

--On Monday, June 26, 2023 8:24 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > 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` Is the var/messages hierarchy also where all the archived emails are stored for future viewing via the web interface? > Also, there is a long thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/UWCUQYU7Q5X5LWNII57ZZ4DDXE4DEFX7/ and maybe others that might be > relevant. I have never used the mailman shell before, but based on the referenced thread I learned to do this (note that the thread also taught me how to rewrite it to narrow down to just the list with issues so I didn't delete held messages in other lists, if my case): for verification: venv) mailman@speedy:~/web/logs$ mailman shell -l sbarc-list(a)lists.netlojix.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the sbarc-list(a)lists.netlojix.com mailing list >>> requests = IListRequests(m) >>> first = True >>> for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if first: ... first = False ... print(m.list_id) ... print (f"""\ ... Sender: {data['_mod_sender']} ... Subject: {data['_mod_subject']} ... Date: {data['_mod_hold_date']} ... Reason: {data['_mod_reason']} ... """) ... and then to delete the two messages: (venv) mailman@speedy:~/web/logs$ mailman shell -l sbarc-list(a)lists.netlojix.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the sbarc-list(a)lists.netlojix.com mailing list >>> requests = IListRequests(m) >>> first = True >>> for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if first: ... first = False ... print(m.list_id) ... print(f'request id: {request.id}, deleting') ... requests.delete_request(request.id) ... sbarc-list.lists.netlojix.com request id: 27, deleting request id: 28, deleting >>> The result of this, however, was that the web interface still claimed I had two held messages. I wasn't sure if there was some cron-type "sweeper" process I had to wait to auto-run or if I had to manually do something to create an update. I then realized that the sample script had a ' >>> commit ()" ' at the end, which I'd missed. So, I re-entered the script (but it didn't spit out that it deleted anything this time) and got an error when I did the commit. So, I figured the messages HAD been delete and the commit wasn't really necessary. When I went back to the web interface, the number of held messages was at 0 and I no longer get the original error when clicking on "Held messages", so my issue is solved. But this does leave me with some educational questions: 1) Did I affect something somehow with my "commit", or was there a job that cleaned things up (if so, what job)? 2) Is the "commit" even necessary (I saw it in someone else's script in the thread)? 3) Is there a way to save a script and then execute it via shell rather than typing it in every time (it appears from the examples that people are typing them in every time, which is super tedious; I didn't paste for fear of doing something damaging, but maybe that would work)? 4) Are the request.id's of the messages dynamic/changing, or are they fixed for life? I thought I'd delete based on exact request.id without looping but I was afraid maybe they were changing over time and that this wouldn't be a good idea. Might be nice to know for the future. Thanks for the guidance! Ken

2 years, 10 months

[MM3-users] Re: Guidance Request: Migrating Existing Mailman 3 Installation to Docker-Based Deployment

by Washington Odhiambo

On Fri, Apr 10, 2026 at 6:04 PM Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi all, > > I am currently running a Mailman 3 setup on a standalone server and > planning to migrate it to a Docker-based deployment using the official > Docker Mailman images. I would appreciate your guidance on the recommended > approach for this migration. > > *Current (existing) setup:* > > - Mailman Core: 3.3.5 > - Postorius: 1.3.6 > - HyperKitty: 1.3.5 > - PostgreSQL: 12.22 (Ubuntu) > - Host-based installation (non-Docker) > - Postfix used as the MTA > - Active mailing lists with members and archives > - Apache reverse proxy in front > > *Target (new) setup:* > > - Docker-based Mailman 3 (mailman-core, mailman-web, PostgreSQL > containers) > - Based on the official Docker Mailman repository > - Postfix as the MTA > - Apache reverse proxy in front > > I would like to migrate the following components safely: > > - Mailing lists and their configurations > - Subscribers and roles > - HyperKitty archives > - Postorius/web data (users, preferences, etc.) > > I have a few specific questions: > > 1. What is the recommended migration approach from a host-based Mailman > 3 installation to the Docker-based setup? > 2. Is it safe to directly restore the PostgreSQL databases into the > Docker environment, or is there a preferred migration method? > 3. Are there any version compatibility considerations when migrating > from Mailman Core 3.3.5 / Postorius 1.3.6 / HyperKitty 1.3.5 to the > versions used in the current Docker images? > 4. How to migrate archives? > 5. The official Docker Compose file references `postgres:12-alpine`. Is > it recommended to stay on PostgreSQL 12 for compatibility, or is it > supported to use a newer PostgreSQL version (for example, PostgreSQL 18) > with the Docker Mailman setup? > 6. Are there any common pitfalls or best practices you would recommend > for ensuring a smooth migration? > > > Any guidance or documentation you can provide would be greatly appreciated. > > Thank you for your time and support. > Hello Prasanth, How about you just test the installation on Docker and migration and see the results. You could even use a higher version of postgres in your container since MM3 supports it. My test machine has PostgreSQL 17 and MM3 running. Since the test migration is non-destructive, you could do it, fail, drop the volumes, do it again until you have it working. And you take notes in the process. I asked Uncle Google for "migrate mailman3 from bare metal to docker" and the AI response at the top seemed quite close to what it should be. Scare the fear away and just do the testing on some VM. -- 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]

2 weeks, 6 days

[MM3-users] Re: Mailman 3 localization

by Simon Hanna

On 07/03/2018 10:21 AM, Stephen J. Turnbull wrote: > Simon Hanna writes: > > > > We would like to contribute further german translations, since there > > > are still some parts missing, e.g. in the postorious interface. Would > > > https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate > > > be the right place to do so, so that everybody could use our > > > translations? > > I don't think that is the right place to do it, because I'm sure > Ubuntu lags our releases by quite a bit. Obviously on Launchpad you > should translate for their releases. > > > I wanted to set it up, but the requirement is to use a free hosted > > solution. > > If by "free" you mean we can't afford to pay for a service, that's > probably not true. If by "free" you mean the services you mention > operate on non-free software, yes, RMS would indeed give us bat-guano > about that, but it's not a 100% requirement. We did use Jira for some > services for several years. So the main issue would be how long > Abhilash is willing to put up with rms-guano. Yeah I meant the second definition :-) When I brought it up Barry said it had to be this way and that we don't want to self host it.

7 years, 9 months

[MM3-users] Re: Hyperkitty CPU usage

by Alain Kohli

I see loads of "A string literal cannot contain NUL (0x00) characters." messages, but I haven't found missing messages in the archives yet. Not sure how that could be related, though. Apart from that I don't see anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to run and finish normally. On 4/26/19 6:32 PM, Abhilash Raj wrote: > On Fri, Apr 26, 2019, at 8:14 AM, Alain Kohli wrote: >> Hi >> >> I have hyperkitty running and noticed that the process 'python manage.py >> runjobs minutely' is running for over 70h now and is constantly using >> 100% of a CPU core. That can hardly be intended, but I don't know why >> it's doing that. As far as I could see, this job mainly updates the >> search index. Running 'python manage.py rebuild_index' only takes about >> an hour, though, so I don't see why this would take so much longer. The >> text search is not working in the first place, so that might be >> connected as well. I'm currently running the v1.2.2. > Do you see any errors in the logs? > >> Regards, >> Alain >> _______________________________________________ >> 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] Re: hyperkitty_import Unicode Errors

by kdhall＠binghamton.edu

Stephen J Turnbull wrote: > On 2023-05-07 07:39 Mark Sapiro writes: > > On 5/6/23 11:27, Dave Hall via Mailman-users wrote: > > > django.db.utils.OperationalError: (1366, "Incorrect string value: > > '\xE1\x90\xA7\x0A\x0AO...' for column > > mailman3web.hyperkitty_email.content at row 1") > > Is there a known cause for this? > > Almost always nonconforming user clients. You write "frequently", but > I'm > guessing it's maybe 1% or 2% of all the messages, right? I suspect it's > a > particular author or institution using such a client. > > Is it fixed in some release more recent than 0+20180916? > > This is almost surely not something we can fix. Based on the error, > it's in third > party code (Django) that we import. It's possible we could provide a > more explanatory message, but the only thing we can sensibly do is hold > the > message for an admin to edit it by hand. As long as the text in > question and the > Content-Type header aren't too sensitive, we can help with identifying > charset > (often UTF-8 as Mark suggests but why someone would be encoding FINAL > MIDDLE DOT is a mystery to me). > > I'm not sure what's going on here. My first thought is the database is > > MySQL or MariaDB and this is a 4-byte UTF-8 encoding and the database > > column charset definition is utf8 and not utf8mb4, but > > '\xE1\x90\xA7\x0A\x0A' is the 3-byte UTF-8 encoding for CANADIAN > > SYLLABICS FINAL MIDDLE DOT ('\xE1\x90\xA7') followed by two > > newlines. so I'm not sure what the issue is. > > I'm guessing home-made client, possibly Asian or a spammer, which > provides no > content-type header. Even today I see raw 8-bit encoded text without an > encoding > spec from legitimate Japanese and Chinese sources, and of course with > spammers > all bets are off -- they might even do it deliberately to crash filters. I have located an email with a similar error in a V2.1 .mbox file. The post was by a faculty member in my organization using Thunderbird 60.2.1 on a Mac - OSX 10.13. The list was used to correspond with students taking a programming course. The message body is multi-part MIME with two sections: This is a multi-part message in MIME format. --------------4BAB6CD38F4927471D366565 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit and --------------4BAB6CD38F4927471D366565 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit The hexadecimal sting \\xEF\\xBB\\xBF\\xEF\\xBB\\xBF appears one place in each section. I'm not sure exactly what this means. I did check my MariaDB (as Mark hinted) and found that it set for utf8 rather than utf8mb4. I'd be willing to change this, but would I also have to do something to update the Mailman databases since those tables are already created? Thanks. -Dave

2 years, 11 months

[MM3-users] Re: converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Lucio Chiappetti

Dear Mark, thanks for your interest. On Fri, 11 Feb 2022, Mark Sapiro wrote: > This may actually be a bug. I'll have to think about that. I've filed > https://gitlab.com/mailman/mailman/-/issues/978 on this. > This is https://gitlab.com/mailman/mailman/-/issues/794 (still open) Given the time needed to solve the issues (I will anyhow notify the site administrators, hopting they would update mailman when/if resolved), this means we have to find a workaround. > And those non-members all have there moderation action set to Defer > which means their posts will be accepted but the additional checks such > as too big, etc. will still be applied. not sure what you mean by "defer". The non-member options I see are called List default -- follow the list's default member action. Hold -- This holds the message for approval by the list moderators. Reject -- this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. Discard -- this simply discards the message, with no notice sent to the post's author. Accept -- accepts any postings without any further checks. Default Processing -- run additional checks and accept the message. > If they are nonmembers, you can accept the post and set moderation > action in one operation in Postorius, but the regexps in > hold_these_nonmembers will still take precedence. OK, I've found where to do it, it requires to select the held message and scroll to the bottom then set Moderation from a menu. But if hold_these_nonmembers takes priority this will be uselesws in the current setting. > I'm not sure what you are looking at here. Imported nonmembers should > all have moderation action set according to which *_these_nonmembers > they came from. Imported members should have their moderation action set > to Defer if they were unmoderated and if they were moderated, it should > be set based on the 2.1 list's member_moderation_action. I go to the non-member list, select non-member options and at the bottom see an item Administration options Moderation. The possible values are those I pasted above. The actual value for most of the imported non-members is "Default processing" while it is "List default" for thoase automatically added afresh, It is "Discard" for a number of imported non-members with spam-looking addresses (I guess they were in some other *_not_members part of the standard 2.1 antispam ... I can't recall me doing something on those) Side question: is there a way to operate IN BULK on non-members ? Like it is for members (I exported them to CSV). >> - if so, how can we do it automatically for all 189 entries ? >> - or move back the 189 addresses to accept_these_nonmembers ? > Yes, move them back. I am not so concerned of these 189 (or better of the 189 minus the discard ones which should stay) ... anyhow moving them back will be uncomfortable if there is not a bulk operation tool. I am more concerned of the new cases automatically added. Our member list includes 1043 addresses. Of these less than 20 use an external address (say gmail), so they post "from home" and will pass. 194 addresses are of the form name.surname(a)inaf.it (these are likely to be recently hired staff, who have and use onlyu the organization-wide address). All the rest (so still more than 800, can't really ask all of them to re-register (*)) are of the form username(a)institute.inaf.it (and it won't be easy also to bulk-delete and bulk-resubscribe because of the inhomogeneous mapping of username to name.surname. Of these about 800 some are lurkers and are no problem. Some are frequent posters and remember to post from username(a)institute.inaf.it and are no problem. Other may post from an alternate address (maybe even the old address exists as a receiving-only alias), and in this case with the current arrangement they will bo on hold every time. I guess we should wait for the solution of issue 794 (*) by the way do you confirm that if one is subscribed to a list with an address (be it bulk subscription, import or new fast subscription), this person CANNOT change their settings (or address) unless one does a "sign in" to a (Postorius) account ? > It is because all the legacy *_these_nonmember actions are applied > before nonmember moderation checks, so if an address matches a regex in > hold_these_nonmembers, the post will be held regardless of the > nonmember's moderation action. > Addresses still work, and accept_these_nonmembers takes precedence over > hold_these_nonmembers just as in MM 2.1. This was not my impression when I ran a thorough test of 12 cases. Except the obvious case of the subscriber posting from the subscription address, all messages went on hold. Whatever the non-member moderation would be (even if set to reject ! ... but that makes sense if *_these_nonmembers prevail on non-member options), and even if the address was set explicitly in accept_these_nonmembers (should I delete it from the non-member list ?) What is the actual order (or flow chart) of choices ? *_these_nonmembers in the order listed in the page (within each in the order of occurrence of regexp's) then non-member options ? If I have Name.Surname(a)inaf.it in accept_these_nonmembers, then hold_these_nonmembers set to ^.+@.+\.it ^.+@.+\.tng\.iac\.es what do you foresee ? And for different regexps, will processing terminate at the first non-matching one, will they be ANDed or ORed, or what ? I am reluctant to accept inconditionally ^.+\..+(a)inaf\.it (they may be falsified, only the check on their presence in the other list (issue 794) I guess I should remove the ^.+@.+\.it regexp AND AT THE SAME TIME change the Default action to take when a non-member posts to the list to Hold instead of Discard. This way we'll have to check spam (instead of having it auto-discarded), but if people with alternate addresses post, once they are entered in the Non-member list they can be authorized to pass for the future ... .. would it work ? -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html

4 years, 2 months

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

by Cathryn McGuire

Hi Mark, You: What is the content of this? Probably should be empty. Me: It is empty. You: No, it doesn't interfere with header checks. Me: Okay. You: What does Blocked mean? If you mean held for moderation, what is the reason they are held? Me: We've changed from Accept Immediately to Default Processing. We'll investigate other settings that might be making all message Held. You: If you have Default action to take when a member posts to the list set to Accept, that bypasses this check and many others. Me: As above--changed from Accept to Default Processing. File sizes should be limited now. You: What do you have in your header filter rules? More importantly, what are you trying to accomplish? I.e. what do you want to happen in the following cases? Message To: the list, no Cc: -- Accepted Message To: the list, Cc: to other address (non-member) -- Hold for moderation. Message To: the list, Cc: to a member's address –– Accepted Message To: somewhere else, Cc: to the list -- Hold for moderation. Message To: elsewhere, Bcc: to the list (require explicit destination will hold this one) -- Hold for moderation. We're no longer concerned about Bcc because you explained it before. It's in the subject line here, but we're not concerned about it. Thanks Mark, Cathryn

6 months, 1 week

[MM3-users] Re: Postfix SMTP REJECT non-subscribers

by Odhiambo Washington

On Wed, Jul 10, 2024 at 3:48 PM Matthew Blissett via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hi, > > > With Mailman 2, I have configuration and scripts to reject non-members > from posting to lists _during the SMTP connection_. This is better than > bouncing (no backscatter), better than discarding messages (the user > finds out) and better than moderation (spammy messages aren't forwarded > to external email systems). > > > The configuration and scripts are described here: > https://code.launchpad.net/~jimpop/mailman/check_subscriber > > > Is anything like this built-in to Mailman 3? I cannot find it in Gitlab. > MM2 stored the subscribers' addresses in the /PATH/TO/mailman/lists/LISTNAME/config.pck. MM3 has the subscribers' addresses stored in your favorite DB backend (PostgreSQL, MySQL.Sqlite). So you'll need to do an SQL lookup for the subscribers. I am wondering why you should waste those CPU cycles instead of just having MM3 do its work: So, when "Default action to take when a non-member posts to the list = Discard", how does the user find out? I suppose it's an MH370 kind situation :( -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

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

by Mark Sapiro

On 5/19/22 06:17, bob B via Mailman-users wrote: > 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? Correct. > 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? Yes. > 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? That's correct, and that was also the case in Mailman 2.1 . > is there a way to change all their user's "Moderation Action" for a list in bulk? You could do it with `mailman shell`, but not in Postorius. > 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? If you are a list owner whose only access is via Postorius, that's correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: MASS mailing list import - 900 ezmlm lists to Mailman

by turnbull

Couple of points: 2023-04-20 07:37 に grant(a)horizonsunlimited.com さんは書きました: > I'm looking to have some time for me. Time to get out and ride my > motorcycles more. :) Mark takes a month off every year to ride his bicycle into the wilds. We definitely encourage our admins to ride more! > 3: Batch script to mass convert - not me! I suspect I COULD - but the > time involved is no way worth it to me. As long as you have access to the (*nix) host, I suspect we'd be happy to write the script. The problem is the ezmlm list config database. > Hosting the lists is a thought, but again, trying to reduce costs, and > since my server already HAS mailman 2, that seems unnecessary. > I did get a couple of DM's re hosting a list, one even suggested they > can do the conversion, so will check out if they will do the conversion > for a reasonable fee. I understand that your users are unlikely to be massive donors, but maybe you could spend the time saved on administration on applying for grants. I wouldn't be surprised if the telephone operators at an organization like the Gates Foundation have authority to grant a $9.98/month hosting service. :-) Good luck on finding a good deal, and let us know if we can help.

3 years

Search results for query "dO"