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

[MM3-users] Re: ValueError: ...:EVP_DigestInit_ex:disabled for fips

by Ralf Wiegand

Hello Mark, Can I substitute Django with something that will be FIPS complaint? Can I do without it? Thank You, Ralf On 5/19/20 1:02 PM, Mark Sapiro wrote: > On 5/19/20 5:57 AM, Ralf Wiegand wrote: >> (venv-3.6) [root@maildev mailman-suite_project]# python manage.py migrate >> Operations to perform: >> Apply all migrations: account, admin, auth, contenttypes, >> django_mailman3, django_q, hyperkitty, openid, postorius, sessions, >> sites, socialaccount >> Running migrations: >> Applying contenttypes.0001_initial...Traceback (most recent call last): > ... >> File >> "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/utils.py", >> line 221, in names_digest >> h = hashlib.md5() >> *ValueError: error:060800A3:digital envelope >> routines:EVP_DigestInit_ex:disabled for fips* >> >> >> >> Hello group, I am running into this error. any idea what is going >> wrong here? > This is a Django issue, not Mailman per se. The migration that's failing > is django/contrib/contenttypes/migrations/0001_initial.py. A brief > search seems to indicate that this won't work with NSS FIPS. >

5 years, 9 months

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

by Mark Sapiro

On 3/27/21 2:08 PM, Brian Carpenter wrote: > I was testing out the process of rejecting an incoming subscription > request. Choosing the reject option for a moderated subscription request > does send out a rejection notice but it gives no reason for the > rejection. ... > Is there a place somewhere in Postorius to provide a rejection reasons > for moderated subscription requests? Does Mailman 3 core provide this > via its REST api but it is just not revealed in Postorius yet? It's in Postorius since 1.3.3. If in the held message view, you click the subject of a held message, you get a popup dialog the shows the message with options to also show headers or the raw message. There is also a dropdown t=o set the poster's moderation action and a box for a reject reason if you click the reject button in the dialog. Do you not see this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] logrotate

by Christian

I noticed that my mailman logfiles are not being rotated. I followed the instructions in https://mail.python.org/archives/list/mailman-developers@python.org/message/ FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ Now when I try and run logrotate I get the following error root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file or directory error: stat of /opt/mailman/mm/error.log failed: No such file or directory error: stat of /opt/mailman/mm/mailman.log failed: No such file or directory error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file or directory error: stat of /opt/mailman/mm/smtp.log failed: No such file or directory root@zarathustra: What am I doing wrong please? -----Original Message----- From: bob B via Mailman-users <mailman-users(a)mailman3.org> Sent: Tuesday, May 2, 2023 5:14 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: looking for more detailed traceback for shunted message Ok, thanks for looking. _______________________________________________ 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/ FLCRIRLKXM3VIT3VAN7TQNJLIB3LRXLR/ This message sent to csa(a)web-analysts.net

2 years, 10 months

[MM3-users] Configure new list via REST API - trying to add moderators

by Andy Matthews

I'm stepping into some existing code which creates a new list via the REST API. I know this works because I can shell into the mailman3 box and run `mailman lists` and it shows the newly created list. We're also submitting list config options via the `/lists/<list id>/config` endpoint, but there's a specific key that we have in our config map that doesn't appear in the REST API docs and I'm wondering about it. We have an array of strings called `moderator` that appears to send successfully. But looking at the docs for "Mailing list configuration" (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) I don't see anything named `moderator` The "Managing owners and moderators" docs (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…) indicate that we can perform add owners and moderators via a Python shell, but don't indicate that it's possible to do it via REST. Is this true?

1 year, 5 months

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 7/30/25 07:27, Stephan Krinetzki wrote: > Hi all, > > I'm running into an issue with Mailman 3. Mails sent to a list are being held due to moderation settings — which is expected — but after approving them, they are not delivered to list members. Are there any regular members with delivery enabled? ``` mailman members --regular --nomail enabled LISTSPEC ``` > The message does not end up in the shunt queue, and nothing is delivered. > > Here's what I see in the Mailman log: > > Jul 30 16:12:23 2025 (213300) HOLD: mm(a)lists.example.com post from sender(a)sub.example.com held, message-id=<20250730141221.5VVrn%sender(a)sub.example.com>: The message is not from a list member > Jul 30 16:12:39 2025 (213338) held message approved, message-id: <20250730141221.5VVrn%sender(a)sub.example.com> This is expected. Is there anything relevant in Mailman's smtp.log? Do any posts to this list get delivered, e.g., posts which aren't held. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

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

by Duane Raymond

On Wed, 10 Mar 2021 at 15:52, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > Update: the other person on the test list has indicated they are > receiving the emails now - and that gmail may be the cause of the issue by > filtering out copies of the message I had sent. (my fairsay.com address > is gmail hosted, but another is not and is simply forwarded there). > > > > ...so perhaps the problem is solved (will do a little more testing to > verify!) > > It's Gmail. Just check the mail.log and look for status=sent > Thanks Brian - then I think it is fixed :-) Thank you Mark and Brian for your patience and persistence. I'll keep monitoring the situation as new subscribers (not sure if all) seem to also be missing the user id in the members table and I then need to run an update query to fix it - but at least I know what to look for and how to resolve it! (this last week was painful!) Cheers, Duane

4 years, 11 months

[MM3-users] Strange behaviour when SSL (https) is activated

by fr-mm3＠tourde.org

Hi, I do a fresh install of Mailman3 and Mailman3-web on Debian 11 and all seems working fine using non-ssl access. But if I activate SSL on the web server, I'm unable to login. I go to the /admin, prompted for the user/pass, and got a Firefox error page saying "Échec de la connexion sécurisée". Main django account was created with: mailman-web createsuperuser --username XXXX --email xxxx(a)xxxx.xx extract of /var/log/mailman3/web/mailman-web.log : [pid: 103142|app: 0|req: 40/40] 192.168.200.252 () {48 vars in 1039 bytes} [Mon Jan 3 11:26:32 2022] GET /accounts/login/ => generated 9321 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 429 bytes (1 switches on core 0) Mon Jan 3 11:26:40 2022 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during POST /accounts/login/ (192.168.200.252) OSError: write error [pid: 103142|app: 0|req: 41/41] 192.168.200.252 () {54 vars in 1008 bytes} [Mon Jan 3 11:26:40 2022] POST /accounts/login/ => generated 0 bytes in 704 msecs (HTTP/1.1 302) 9 headers in 0 bytes (1 switches on core 1) All is working fine on non-ssl connection. Any hint appreciated ;)

4 years, 2 months

[MM3-users] CSS Hyperkitty ERROR

by Johan Alsina

Hi, i installed mailman3 with virtualenv, all is working fine, the admin site works fine, the mailman(postorious) site works fine, but when im in hyperkitty the site shows without the css style.. in my web browser dev tool it shows like they loaded ok.. Here you can see what i see when loading hyperkitty https://freeimage.host/i/3n6kXKQ and mailman(postorius) https://freeimage.host/i/mailman.3n6kVix When i run my server with verbosity it shows like all is loading ok: https://freeimage.host/i/3n6SViG Any ideas? :/ My static files are loading from /static/CACHE/css/output.a0f71925131b.css and /static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css It seems like the real error are in the /static/CACHE files, because hyperkitty is the only one who load files from this directory.. postorius uses /static/postorius and all the css files are working fine. I checked permissions for the directory, cleared cache, etc.. i dont know what to do. This is my config for staticfiles: STATIC_URL = 'static/' STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles') STATICFILES_DIRS = [ os.path.join(BASE_DIR, 'static'), '/opt/mailman/projectes/mailman3web/static/CACHE', Thank you so much in advance.

11 months, 2 weeks

[MM3-users] Re: Templates and docker-mailman

by Abhilash Raj

On Tue, Mar 20, 2018, at 2:47 PM, Mark Sapiro wrote: > On 03/20/2018 02:13 PM, jwhathaway(a)locklaw.com wrote: > > > > /opt/mailman/core/var/templates/site/en/list:member:generic:footer > > > > But this is not being honored by the mailman container. I have restarted all of the containers. Is there something else I need to do? > > > That's only one place the template is looked for. The search is first > list, then domain then site. > > So the search will be first in > /opt/mailman/core/var/templates/list/<list-id>/en/ followed by > /opt/mailman/core/var/templates/domains/<domain>/en/ followed by > /opt/mailman/core/var/templates/site/en/ > > and the first list:member:regular:footer or list:member:generic:footer > found is what will be used for regular deliveries and the first > list:member:digest:footer or list:member:generic:footer found is what > will be used for digest deliveries. I'd probably have to look at the code, but aren't they supposed to have either .txt or .html extensions? -- Abhilash Raj maxking(a)asynchronous.in

7 years, 11 months

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

by Mark Sapiro

On 6/29/20 1:38 AM, Florian Schulze wrote: > Hi! > > After upgrading to HyperKitty 1.3.x I get the following error for qcluster: > > File ".../lib/python3.7/site-packages/django_q/cluster.py", line 300, > in pusher > task = SignedPackage.loads(task[1]) > File ".../lib/python3.7/site-packages/django_q/signing.py", line 31, > in loads > serializer=PickleSerializer) > File ".../lib/python3.7/site-packages/django_q/core_signing.py", line > 38, in loads > return serializer().loads(data) > File ".../lib/python3.7/site-packages/django_q/signing.py", line 44, > in loads > return pickle.loads(data) > AttributeError: Can't get attribute 'process_task_result' on <module > 'hyperkitty.tasks' from > '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> > > How do I recover from that? It seems like there are still persisted > tasks in the qcluster queue using the old code from 1.2.x with the old > locking implementation. Have you stopped ans started qcluster since upgrading? Are you running the Django periodic jobs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

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

by Élodie BOSSIER

Le 18/02/2022 à 18:23, Mark Sapiro a écrit : > If you go to https://example.com/mailman3/domains/ (the Domains view > in Postorius) you will see at least two entries, one with Mail Host > ml.franceserv.fr and one with Mail Host ml.viticreation.fr. > > What are the Web Host entries for these? > You should have two separate site entries in the django_site table > (https://example.com/admin/sites/site/) for these domains. Ah alright, now I understand how to proceed and it's working perfectly. I need to add domains through https://ml.franceserv.fr/admin/sites/site/ and define a new site_id for each domain name. Thank you very much for your help. This is my result : https://images.franceserv.fr/images/2022/02/18/06d4eb84a0ded88d55c0296ff0c3… Now, I need to find how to set it automatic when I will add a new list. Perhaps I could do it with an an SQL command if there are no bash command ? I will check with "mailman create" and the --domain argument. Thank you again for your help.

4 years

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I made a change for test purpose on the mailman.cfg file and I got this: (env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running? How do I solve this? El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > 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, 7 months

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 4/8/19 4:44 AM, Henrik Rasmussen wrote: > I finally received the right mail from the user. I am sorry for the delay. > > The mail from the list does actually not contain any X-Mailman-Rule-Misses: nor X-Mailman-Rule-Hits: This is quite strange. There are no 'X-Mailman' headers which might be exchange removing all 'X-' headers other than its own, but while there are some 'List-' headers, there is no 'List-Id:' header which Mailman always adds. Can you try to get an example message from the list that was sent to a non-outlook/exchange user. Perhaps you could subscribe a gmail or other non-microsoft managed address to the list. I note the MX for your email domain is ku-dk.mail.protection.outlook.com, so that probably won't do. However, one thing to check is the list's Header filters settings. Is there a filter there that could match the owner's email with action accept? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 7/8/22 8:28 AM, kisner(a)live.com wrote: > > I tried to follow that guide ( https://docs.mailman3.org/en/latest/install/virtualenv.html ), but I couldn't get it to work. I'd have to try it again to see where it broke. One thing that I got past was I had to change: > > (venv)$ pip install wheel mailman psycopg2-binary<2.9 > > to > > (venv)$ pip install wheel mailman psycopg2-binary==2.8.6 > > and that got me past that part, I don't understand why that would make a difference since the latest psycopg2-binary<2.9 is 2.8.6 > but hyperkitty/mailman-web pip install has components that failed to install. I'm not sure why, someone smarter than me could probably have figured it out, but as written it wasn't working for me. If you do try again, post the specific issues/error messages and we will try to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Converting non-members to members

by Alan So

Postorius is not currently exposing non-members management. Our Mailman 2 users are currently using accept_these_nonmembers, hold_these_nonmembers and reject_these_nonmembers. We know that mailman import21 will change these to nonmembers entries in Mailman 3. Since list owners will still want to manage them, we tend to move all of them to members and turn off delivery status for them. However, we met some difficulties when we try to develop using mailman client. 1) If those non-members addresses already exist as members, we will encounter error when we subscribe for them: urllib.error.HTTPError: HTTP Error 409: b'Member already subscribed' 2) We cannot change the moderation_action: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: moderation_action' 3) We cannot change the preference: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: delivery_status' Are there any better ways to enable the list owners to manage those previously configured nonmembers' addresses through the web? Otherwise, we probably need to have some manual effort to overcome the above three issues. We know that we can always do the above manually but we got a lot of lists to migrate to Mailman 3.

7 years, 2 months

[MM3-users] Re: Not able to start mailman server

by Mark Sapiro

On 8/4/21 2:24 PM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to start the mailman server on a mac according to the instructions given on the website as shown - What web site? A URL to the instructions you followed would help. > $(py3) git clone git@gitlab.com:mailman/mailman.git > $(py3) cd mailman > $(py3) python setup.py develop Rather than 'python setup.py develop', do 'pip install -e ./' > $(py3) mailman start > $(py3) cd .. > > But I run into the following problem - > > Starting Mailman's master runner > Generating MTA alias maps > /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > > Can anyone help me out with this? There should be a `master` in the same bin/ directory as `mailman` which is probably not '/usr/local/opt/python(a)3.9/bin/' What does `mailman info` show? -- 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: Mailman 3 with AWS auto scaling and potentially load balancing

by Abhilash Raj

On Fri, Mar 30, 2018, at 12:00 PM, Chris McMacken wrote: > Thanks for the prompt response. > > Why does the application store messages on the local disk? It is how our queuing system is built, every queue is stored on disk and messages in intermediate states like when being processed or decorated inside Mailman Core as stored on disk. *Most* of these isn't the problem, since the emails are sent out pretty fast, it's the held messages waiting for approval or broken messages in the shunt queue that would be lost and is what I mean by "State" mostly. AFAIK API being served by different instances will affect what and how many held messages are reported. > I'm guessing > it's for performance reasons but wanted to ask. Do you have any plans to > add database storage for these at some point in the future? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 11 months

[MM3-users] Dmarc settings and

by paul＠arenson.org

In a long thread I asked this but have not gotten a clear enough explanation. Presumably, to insure fewer problems with users of Yahoo etc,, there seem to be two settings: 1) Alter messages 2) Dmarc mitigations I don’t understand how my choice in one affect the other, if they do even, Two experts have tried to help, but I think I need a little hand holding. I understand there is no consumer ready manual and all I have found us this: https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/dmarc-mi… My settings; REPLY GOES TO LIST (alter messages)--current settings REPLACE FROM: with list (DMARC mitigations) -> current settings DMARCH Mitigation YES OR NO (DMARC mitigations)--> currently NO I was told that Dmarc mitigations YES might prevent people from not getting mail How about Replace from with list? How about reply goes to list? In other words, what is the relationship between these two different menu items and the effect of the settings in one on the settings of the other? Can anyone help a confused would be happy user? Thanks? If so, what about the Alter Messages settings:

6 years, 6 months

[MM3-users] mailman.log file owned by 'list' user

by Mike Wertheim

I'm on Debian 11, trying to troubleshoot an installation of Mailman 3.3.3 that was done by someone else. Mailman is running as a non-privileged (non-root) user called 'xyz'. On the day that Mailman was installed, that non-privileged 'xyz' user was able to execute mailman commands successfully to create, view and modify lists. A couple of days later, when the 'xyz' user tried running those same mailman commands, they failed with this error: PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' Doing "ls -l" on the file /var/log/mailman3/mailman.log showed this: -rw-r----- 1 list list 0 Jan 6 00:00 /var/log/mailman3/mailman.log When I did a 'ps' command, I saw that all of the mailman processes are running as user 'xyz'. No processes were running as the user 'list'. It seems that some process is rotating the mailman.log file at midnight, and the newly-created mailman.log is being owned by user 'list'. Can anyone explain why this is happening, and how to fix it?

3 years, 1 month

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

by Matthew Alberti

I had a very similar experience. I don't mean to knock the dev team; Mailman3 is an awesome tool that really meets a need. It is really much much more than a 'tool.' A very comprehensive software suite. For me, I ended up using the docker option on Ubuntu 20.04. My advice is to give up on the idea of using OS package managers. They just aren't current enough (certainly for Ubuntu LTS), or updated frequently enough, for the current development of Mailman3. Nothing but problems for me on Ubuntu, and Debian is about the same. Pypi, or installation in a virtualized environment, was equally challenging. I strongly recommend the docker installation method. It is not quite turnkey, but the documentation is close enough where it might 'just work' in your environment. I used MariaDB, and that introduced some challenges. If you are using postgre, postfix, and nginx, you are pretty close to a very easy installation. This list is very supportive, with very frequent responses from the core dev team. And there are guys like me who really struggled to get to a production instance. Please let us all know what isn't working in the docker approach, and we will try to help I'm sure. - Matt Alberti ⁣Get BlueMail for Android On Dec 31, 2020, 8:15 PM, at 8:15 PM, ieso(a)johnwillson.com wrote: >So I've been trying for the last two weeks to get a new mailman3 server >running on a virtualized server (any server), and I'm turning to this >list after having failed many times and running out of holiday time. > >I started trying a non-docker installation on Ubuntu 18.04 >(https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) >, which got me the closest. Except I had a problem with inbound email >only being triggered when it came from certain accounts. But that >clearly wasn't good enough for production, so after many attempts to >figure out where it was failing, I decided to turn to docker as a >solution that should be cleaner. > >A few attempts at doing a docker installation on digitalocean.com >failed, which I realized might be due to it not routing private IP >addresses, so I moved to AWS after checking that their VPC policy would >fit mailman's docker requirements. I found a great but slightly >outdated guide on how to do this >(https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) >By this point I knew enough to correct a number of places where the >environment had changed since the procedure was written, but postorius >still failed at the curl test. > >The challenge for me has been the difficulty to know how to >troubleshoot the different different systems and network infrastructure >that are used to keep mailman3 humming. I've tried about 7 different >installation walkthroughs (there are no recent ones on Youtube by the >way, in case anyone wants to seize that opportunity!), and the good >guides provide ways to check each stage to try to help you a bit on >that front. > >Nonetheless, I feel stuck and thought I'd ask the simple question... >for a completely basic, barebones new installation, what's the easiest >way to get a mailman3 installation up-and running? (e.g. Which server >provider? Which operating system and version? Docker or otherwise?) > >Any pointers highly appreciated. Google Groups is clearly on its way >out, as it no longer allows for people to easily join groups by sending >an email or clicking a link, so that should be a big opportunity for >mailman3 to step up and help give those mailing list migrants a new >home... which is what we're looking for. We're just not quite as smart >as you guys. ;-) >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 2 months

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

by Shashikanth Komandoor

Hi Mark, Thank you very much for your response. I understood myself as quite ignorant even to find out the versions of each of the component. But my "mailman info" output looks like the below: *(venv3) [root@dlist-lsmgr mailman]# mailman info* *GNU Mailman 3.3.2rc2 (Tom Sawyer)* *Python 3.6.8 (default, Aug 10 2019, 06:54:07)* *[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]* *config file: /var/lib/mailman/mailman/var/etc/mailman.cfg* *db url: postgres://<username>:<password>@127.0.0.1/mailman* *devmode: DISABLED* *REST root url: http://localhost:8001/3.1/ <http://localhost:8001/3.1/>* *REST credentials: restadmin:restpass* *(venv3) [root@dlist-lsmgr mailman]# pwd* */var/lib/mailman/mailman* How to find out the versions of the each and every component of the mailman 3 like mailman core, mailmancilent, postorius, hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, after installation? If I am running an old mailmanclient or older version of any other mailman component, please suggest how to upgrade either one or multiple components based on the requirement. Is there any link that would help me to upgrade ? I have used the link https://docs.mailman3.org/en/latest/devsetup.html to install the mailman 3 components. I expected that the procedure followed in this link would install the latest versions of the mailman 3 components. Please correct me if I am wrong. Is there any latest version compatibility table ? Also please suggest me an URL that would install the latest versions of mailman 3 components and allow me to do customizations related to our domain. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Mon, Oct 26, 2020 at 4:16 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/20 8:22 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > I am currently running Mailman 3 with version 3.3.2rc2 and > in > > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.9 version > > with default values. As of now, we don't have any lists and just > installed > > software components only. > > > > After the installation and configuration, I have tried > > creating the domains and lists. I was successful in creating them but > when > > I tried to login and browse the lists using LDAP authentication, I am > > getting the "Mailman REST API not available. Restart Mailman core". > > > > I see the below trace in the mailmansuite.log. > > > > > *Traceback (most recent call last): File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 119, in __getattr__ return self._get(name) File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 86, in _get raise KeyError(key)KeyError: 'get_requests_count > ... > > > > I don't see any error messages in the mailman.log. And I > > also executed a few curl commands in getting the details of the lists > > created and list info which I got their results successfully. > > > > Could you please guide where exactly I am missing or do I > > need to make any changes in my customizations ? > > > I think the issue is your mailmanclient is too old. The version of > Postorius you are running requires mailmanclient >3.3.1 which is only > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > What version of Postorius is this? It appears to be >1.3.3. If you > install Postorius from unreleased code on GitLab, you have to install > all of mailman, mailmanclient and django-mailman3 as well. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 4 months

[MM3-users] Re: From address of subscription notifications

by worik

On 27/02/19 11:54 AM, Mark Sapiro wrote: > On 2/26/19 2:11 PM, worik wrote: >> When I subscribe some body to to a list I on I get a notification that >> says it comes from changeme(a)example.com >> >> As far as I can tell no subscribers are getting mail with that, so this >> is not a crises. But it is untidy and I cannot find where to change it. >> >> SERVE_FROM_DOMAIN is set in the mailman-web/environment section of >> docker-compose.yaml (I am using the docker distribution...) > You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > > There is no `mailman/config/schema.cfg` on my system. Should I raise a issue over at the docker-mailman github? I have: /opt/mailman/core/mailman-extra.cfg /opt/mailman/core/var/etc/mailman.cfg Should I change it in the second one? -- 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

[MM3-users] Re: Uncaught runner exception

by Stephen J. Turnbull

Wolfgang Bock via Mailman-users writes: > I tested port 25 with swaks ->mail to user on server: localhost > port 25 -> everything fine What is "swaks"? > Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server > localhost on port 25 Is it possible that Postfix is configured for TLS connections only? If so, it is probably listening on port 465 (the "submissions" port, AKA ssmtp and smtps) or (less likely) 587 (the "submission" port -- no trailing "s"). Mailman needs to be configured correctly for this. See https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht… It's barely possible that Postfix is listening on port 25 but insists on TLS. But that's very unusual, and I think that would produce a SMTP error such as "Need STARTTLS" or "Need SASL" (which happen *after* the TCP connection is established) instead of "Cannot connect" (which suggests a TCP error before a connection is completed). > I have no idea what to do for solving my problems. That's when we're most of service. At least, I hope so! :-) Steve

5 years, 10 months

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

by Mark Sapiro

On 10/27/20 11:08 PM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > All the mentioned versions of all the components are taken from my > currently running system only in which I am facing the issue. Did you run $ cd mailmanclient $ python setup.py develop as it says at <https://docs.mailman3.org/en/latest/devsetup.html> I do not understand exactly how the various components are installed in your installation, so I can't tell you what is wrong, but the version of mailmanclient that gives you the AttributeError: 'MailingList' object has no attribute 'get_requests_count' is not the one whose latest commit is ### Mailmanclient Version ### commit aaa529808e2d61899f90509da4ea802a70d2c8ff Merge: ff39dd8 8670751 Author: Abhilash Raj <maxking(a)asynchronous.in maxking(a)asynchronous.in> Date: Thu Oct 15 01:09:32 2020 +0000 Merge branch 'fix-ci' into 'master'* Use GHCR for the CI image* See merge request mailman/mailmanclient!130* because that one won't have this error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Stephen J. Turnbull

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

4 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I put this config in mailman.cfg: To configure Core to use Postfix, add the following configuration to your mailman.cfg configuration, be sure to replace mail.example.com with your email domain: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 is this correct?? El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > 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, 7 months

[MM3-users] Re: Selective mailing

by Abhilash Raj

On Wed, Feb 27, 2019, at 8:43 PM, chucka(a)blackforest-co.com wrote: > I like the controls that MM uses. What I have and need: a member > database [name, address, email, date dues paid, etc]. So I can do this > 2 ways: 1) select name, email from members where xyz > file. Login to > MM empty member list - which is kind of painful then load file and send > the email. Then repeat for NOT xyz You could use the API to create mailing lists on-demand with the list of members, which you can get by executing SQL queries in whatever way you want. Then you can send the emails and re-create the mailing lists everytime your list of members change (monthly?). > or > 2) roll my own php script where I select from and if (xyz) Aemail else > Bemail > > Problem with #2 is I lose the discussion part. <sigh> > _______________________________________________ > 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)

7 years

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

by Nicolas Pettiaux

much thanks. I use mailman 2 interface (and will switch soon to 3) i'll look asap. --- Nicolas Pettiaux - PhD - nicolas(a){educode,pettiaux}.be - Président de Educode asbl Informer, former et susciter la réflexion des acteurs du monde de l'enseignement face aux évolutions d'un monde numérique - http://2019.educode.be & http://2018.educode.be Le 2019-06-19 6:33, Mark Sapiro a écrit : > On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: >> >> By mistake a user has been banned to post to mailman list. How can I >> allow him not only to post but also to become a member of a list ? >> >> I have not found any info on the web, or I have been unable to search >> correctly. > > > Do you have the Postorius web UI in your installation? If so go to the > list's Ban List and remove the unwanted entry. > > Or is this perhaps a Mailman 2 question? If so you'll find the ban_list > in the web admin UI at Privacy options... -> Subscription rules.

6 years, 8 months

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

by Abhilash Raj

On Fri, Apr 10, 2020, at 3:45 AM, skenny(a)scss.tcd.ie wrote: > Out put from my python program is not dissimilar - I am seeing the > same WORKER TIMEOUT message: > > [10/Apr/2020:10:42:54 +0000] "GET > /3.0/lists/scss-sysadmins(a)lists.scss.tcd.ie HTTP/1.1" 200 421 "-" "GNU > Mailman REST client v3.3.0" > [10/Apr/2020:10:42:55 +0000] "GET > /3.0/lists/scss-sysadmins(a)lists.scss.tcd.ie/roster/member HTTP/1.1" 200 > 3766 "-" "GNU Mailman REST client v3.3.0" This seems like is timing out getting list of members. Without pagination, I do expect it to time out if the list is large. I think `.members` by default doesn't use pagination. > [2020-04-10 10:43:25 +0000] [30] [CRITICAL] WORKER TIMEOUT (pid:38) > [2020-04-10 10:43:25 +0000] [38] [INFO] Worker exiting (pid: 38) > [2020-04-10 10:43:26 +0000] [45] [INFO] Booting worker with pid: 45 > > 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)

5 years, 10 months

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

by Odhiambo Washington

On Sat, May 15, 2021 at 1:08 AM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > On 14/5/21 23:52, Odhiambo Washington wrote: > >> Which OS are you using? > > FreeBSD. > > > > > As Mark pointed, you probably have installed the textproc/sassc port (or > package). I'ts an equivalent for sass. Do the config as advised. > > I have mailman3 installed and running smoothly in a pair of 12.2 RELEASE > FBSD servers. > > There is a thread about this installations that can help: > https://forums.freebsd.org/threads/mailman-3.61050/post-488128 > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> I will look into this. I know FreeBSD has a mailam3 port, but I have mailman2 in production and the port installs to /usr/local/mailman so I have to be careful - install mailman3 in /opt, then plan on hosing mailan2 and moving mailman3 to it's place after migration. It's not simple. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 9 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Wed, Feb 1, 2023 at 2:03 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > > All the above noted, and well-received. > > I only decided to experiment with this particular documentation because > it > > is the *OFFICIAL* one. > > Yup, and thank you for that! > > But not everyone has the time or the skills for it, so I wanted to say > in a public place that questions really are welcome (and please > don't be deterred if occasionally we seem exasperated by somebody's > questions, that happens but we get over it, it's not your fault :-). > > Steve > > Hello Steve, That is quite well understood. I am all too happy to be asking questions and yes, I know you and Mark do give us a lot of your time and we are grateful. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: Debian Package Install - Ownership and Permissions

by Odhiambo Washington

On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < as2020+github(a)fam.tuwien.ac.at> wrote: > > On Fri, 7 Apr 2023, at 12:43, Dave Hall via Mailman-users wrote: > > > On Fri, Apr 7, 2023 at 12:29 PM Odhiambo Washington <odhiambo(a)gmail.com> > > wrote: > >> On Fri, Apr 7, 2023 at 7:14 PM Dave Hall via Mailman-users < > >> mailman-users(a)mailman3.org> wrote: > > >> It's actually not that difficult to migrate from the Debian > >> packages to the virtualenv setup. > > It's not an option for me today. > > I feel you. > > I am running MM2 und 3 in parallel without problems, I do have a > special MTA setup though (Sendmail). Can't speak for Postfix etc.. > Your setup can handle list1(a)domain1.name via MM2 and MM3, simultaneously, right? :-) -- 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, 10 months

[MM3-users] spam filtering (was: Re: list of subscribers)

by Peter Münster

On Sun, Feb 04 2018, Mark Sapiro wrote: > This would seem to be specific to your use case. I think in general what > we would want to display is the display_name from the list's member record. Ok, I see. Now I know, how to generate such list (email + full name) as site administrator, so it's ok for me. > We tried to send your copy of your post to you, but your MTA called it spam. > > Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: > to=<pmlists(a)free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, > delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host > mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of > DATA command)) IMO, spam filtering should be done at user level, every user should be free to filter what he likes, not the MTA. Perhaps I should do it like you, and manage my own email relay host? I've tried to subscribe with an address at orange.fr but it does not seem to work, probably the same problem as with free.fr... -- Peter

8 years, 1 month

[MM3-users] Is there a "global" max_message_size?

by skenny＠scss.tcd.ie

I'm running Mailman under Docker (maxking). I've a test list with a max_message_size set to 0 (unlimited). I know it's not what anyone should be doing in production, but I still want to test this. I've sent a series of messages with increasingly larger attachments to the list. Going up in 5MB increments, I find that while a message with a 15MB attachement gets through to the list members, a 20MB one doesn't. The interesting thing is the message in the mail logs: Jun 19 11:44:50 venus postfix/lmtp[17630]: C0C7928564: to=<mj(a)lists.scss.tcd.ie>, relay=172.19.199.2[172.19.199.2]:8024, delay=109, delays=2.2/0.04/0.01/107, dsn=5.0.0, status=bounced (host 172.19.199.2[172.19.199.2] said: 552 Error: Too much mail data (in reply to end of DATA command)) So 172.19.199.2 is complaining about "Too much mail data". That's the IP address of the mailman-core container. I'm wondering why this is happening, and where the decision is being made, as it seems at odds with the fact that the mailing list has no limit on message size. Would be grateful for any insights, many thanks. Stephen Kenny

5 years, 8 months

[MM3-users] Re: Set Postorius interface locale

by Mark Sapiro

On 3/2/21 7:55 AM, Duane Raymond wrote: > > The problems I've encountered so far are: > 1) Where do I set the local of the Postorius interface? > 2) Individual lists have a language setting, but it doesn't seem to reflect what the Postorius locales are as the only english option is "English (USA)" and none of the other English speaking locales and on the file system there is no en-us PO files....so I suspect I'm looking in the wrong place. Multiple things are required. In order to be able to set the list's preferred_language via Postorius, the language must be included in the LANGUAGES definition in postorius/utils.py. However, you can set the list's preferred_language in Mailman core via `REST` or `mailman shell` or direct update of the database. Then there must be message catalogs for the language in postorius/locale, django_mailman3/locale and hyperkitty/locale and these must be compiled by the Django management command `compilemessages`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

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

by William Oliver

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

4 years, 1 month

[MM3-users] Re: Docker or virtualenv?

by Johannes Rohr

Am 31.12.22 um 12:29 schrieb Andrew Hodgson: > 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. Sorry, can you elaborate? Are you talking about an MTA that runs inside a VM? Docker actually isn't a VM, so I am a bit confused. Johannes > > Thanks. > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to johannes(a)rohr.org

3 years, 2 months

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

I have now seen a similar instance on one of my servers. I was able to get the raw garbled response from the user. I have asked to get the raw message that was sent, but unfortunately, I haven't gotten it and I suspect I won't. I think it was an attempted post sent by mistake to the LIST-confirm address. I have tried, so far without success, to duplicate this, but I will keep at it. The raw message is attached. This one is worse than the one in the OP in that the Content-Transfer-Encoding is base64, but the content is unreadable in the raw message. It is clearly not a valid base64 encoding. I'm guessing that the original message looked similar to the one in the OP, but Microsoft Exchange garbled it by doing some attempt at base64 decoding the unencoded plain text and placing that result in the message body -- 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: "From address" for list moderation notification

by Mark Sapiro

On 12/29/23 10:58 AM, ronn.ramirez(a)pge.com wrote: > Hi Mailman Group, > > I noticed that the from address for list moderation notifications are coming from a certain user address. > May you please help me figure out where to change this? > > In this example, I would like to change the From address "listadmin(a)domain.com" > > ================================================================ > -----Original Message----- > From: Admin <listadmin(a)domain.com> > Sent: Thursday, December 28, 2023 12:00 AM > To: dummy-list <dummy-list(a)domainx.com> > Subject: The dummy-list(a)domainx.com list has 2 moderation requests waiting. > > The dummy-list(a)domainx.com list has 2 moderation requests waiting. > ... I do not understand "certain user address". I also don't undersatnd the above example. These notices are sent both From: and To: the list owner address. In the above example it would be From: dummy-list-owner(a)domainx.com To: dummy-list-owner(a)domainx.com Is this not what you see? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Bounce processing

by Mark Ziranski

Thank you. when can we expect the release of Mailman 3.2? Gesendet: Freitag, 11. August 2017 um 17:06 Uhr Von: "Barry Warsaw" <barry(a)list.org> An: "Mailman 3 users (mailman-users(a)mailman3.org)" <mailman-users(a)mailman3.org> Betreff: [MM3-users] Re: Bounce processing On Aug 11, 2017, at 06:02, Mark Ziranski <Wal3(a)gmx.net> wrote: > I read that mailman3 supports 'bounce processing' but I do not know how > to configure it. I want to delete members automatically from a mailing > list if the delivery has failed after a certain time of attempts > because his mailbox has been removed or his mail server has been > shutdown etc. There is also the case that an users mailbox is full > (mailbox limit exceeded). Is possible to deal with this case too? Bounce processing is currently incomplete in Mailman 3.1. We will fix that in Mailman 3.2. (I was going to include a link to the issue, but GL is giving me a 500 error right now.) -Barry _______________________________________________ Mailman-users mailing list mailman-users(a)mailman3.org [1]https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org / References 1. https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 6 months

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

by Odhiambo Washington

On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/23/24 02:16, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 1:37 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Isn't this just `mailman members --role nonmember LISTSPEC`? > >> > > > > I didn't know that the option was right in front of me, but it seems > there > > is a problem: > > GNU Mailman 3.3.10 (Tom Sawyer), Mailman Core API Version 3.1 > ... ^^^^^^^^^^^^^^^^^^^^^^^^ > > AttributeError: 'NoneType' object has no attribute 'display_name' > > > I saw that too. Reported > https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > https://gitlab.com/mailman/mailman/-/merge_requests/1297 It isn't clear to me what I should do to mitigate the error. -- 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, 2 months

[MM3-users] migration plan and auto responder

by Mohsen Masoudfar

Hi, I am writing this in the hope to get some good advises for migration lists from Mailman2 to Mailman3. Thanks a lot in advance. Here is the requirements: * During the migration the old system shouldn't process the emails for the list under migration in the normal way. It should send an email, and only one to the member who sent the original email to the list saying the list is under migration. I know I could do this by auto responder, but the original email would be processed and sent to all members, which I want to block . * After migration the old system should send, per auto responder again, an email to the member who sent to the list, mentioning the new address (the domain is a new one, the list name the same), but again not sending the original email to the list members. * No hackers, robots, spammers should get the new list address. The lists are all hidden. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

5 years, 7 months

[MM3-users] Re: Shunt Error Mail?

by Pete Ashdown

On 3/2/21 4:09 PM, Mark Sapiro wrote: > On 3/2/21 2:52 PM, Pete Ashdown wrote: >> I have a number of list managers with subscribers who are confused as to >> why their messages are silently disappearing. I've read the archives on >> how to decipher why a message was shunted, but this is not workable at >> scale. Is sending an error email back to the sender a consideration? > Why are messages being shunted? Each shunted message has thrown some > kind of uncaught exception which is logged with a traceback in Mailman's > mailman.log. > > These should be due to bugs that should get fixed or possibly malformed > messages which are almost always spam. > > In short, under normal circumstances messages should not be shunted at > all and when they are it is something the site admins need to address. > It is normally not something the sender of the message can do anything > about. This is good to know. I was concerned that shunting could happen due to HTML or message content (ie: not size).

5 years

[MM3-users] Delayed password requests & migrating users from mm2

by Duane Raymond

Hi again, With my new mm3 instance, password reset email to members are being received many hours late or not at all. They seem to be sent fine and when I trigger one to one of my addresses, it works instantly. But many users report getting it many hours later or not at all (despite looking in spam and bulk folders). Anyone else experience this password reset mail delay/vanishing and/or have any suggestions for diagnosing it and resolving it? The main reason this is problematic is that in migrating lists from mm2, I've set a 'fake' password for them in the mm3 db and instructed members to reset their password to set a new one so they can access the list and update their subscription and/or subscribe to other lists (which they can also do without an account of course - but then lose the ability to use the web interface and access archives). So if, as an alternative, there is another way to get list members to access their account then I'm open to it. Cheers, Duane

4 years, 11 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Torsten R.

Mark Sapiro wrote: > The issue is not related to message content. > One possibility is that there is an incompatibility between > mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause > this. What are your versions? Understood, just wanted to mention that as I read it in another thread about the 401. Hyperkitty is 1.3.4 and mailman-hyperkitty is 1.2.0 > What is your setting in mailman-hyperkitty.cfg for base_url: base_url is set to https://www.fqdn.tld/mailman/hyperkitty > if you append api/ to that and do something like > curl base_url/api/ > it should return a page of documentation of the API. If that is the > case, the issue is almost certainly communicating the api key between > mailman-hyperkitty and HyperKitty I get some information back when appending /api/ to that URL mentioned above about REST API and some formats and endpoints. So, from your words it looks like there is some issue in the communication between mailman-hyperkitty and HyperKitty. Is there some place I could/should start looking or some log I should be examining (maybe some loglevel to be increased as well)?

3 years, 10 months

[MM3-users] Re: Postorius, Hyperkitty new release candidates

by Abhilash Raj

Hey Everyone, It turned out that we added a lot of bugfixes soon after the rc1 and so I am going to do another rc before the stable release. - Postorius: 1.3.3rc2 Changelog: https://docs.mailman3.org/projects/postorius/en/latest/news.html#rc2 Download: https://pypi.org/project/postorius/1.3.3rc2/ - Hyperkitty: 1.3.3rc2 Changelog: https://hyperkitty.readthedocs.io/en/latest/news.html#rc2 Download: https://pypi.org/project/HyperKitty/1.3.3rc2/ - Django-mailman3: 1.3.3rc2 Changelog: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Download: https://pypi.org/project/django-mailman3/1.3.3rc2/ The major changes between rc1 and rc2 are are mostly bugfixes. One big cosmetic change is Settings page for List owners, which now has a vertical menu on the left instead of horizontal tabs. The major problem with horizontal tabs for settings was that we were running out of horizontal space in our page width, because of which we weren't able to separate out settings in as-many sections as wanted to. Bounce processing for example was a part of the "Member Policy" tab which included subscription/un-subscription policies. Now, we have a new section for "bounce processing" and flexibility to group other settings into a new section for better discovery of so many list settings. Hopefully, this will be the last rc and I'll do a stable release next weekend! Abhilash On Sat, May 9, 2020, at 6:46 PM, Abhilash Raj wrote: > Hi Everyone, > > I am pleased to announce a couple of more releases: > > - Postorius: 1.3.3rc1 > Changelog: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#rc1 > Download: https://pypi.org/project/postorius/1.3.3rc1/ > - Hyperkitty: 1.3.3rc1 > Changelog: https://hyperkitty.readthedocs.io/en/latest/news.html#rc1 > Download: https://pypi.org/project/HyperKitty/1.3.3rc1/ > - Mailmanclient: 3.3.1rc1 > Changelog: > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > Download: https://pypi.org/project/mailmanclient/3.3.1rc1/ > - Django-mailman3: 1.3.3rc1 > Changelog: > https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > Download: https://pypi.org/project/django-mailman3/1.3.3rc1/ > > Python 3.6+ and Django 2.0+ is supported for all of them. Django 3.0 > support for Hyperkitty requires manually upgrading a dependency > (django-haystack>=3.0b2, once a stable version of this has been > released, it shouldn't require manually upgrading). > > There are tons of bug-fixes across the board and some new features. > > Biggest visible change is switch to Bootstrap 4, which has been long > pending for us. Bootstrap 4 completely changes the CSS grid model using > the new Flexbox. There might be some small changes or breakages when > using on mobile. Please report such issues to us via Gitlab! > > Some other notable changes are in Postorius, which includes many more > list settings exposed include content filtering settings, bounce > processing (which was added in the previous release of Mailman Core) > settings and some other ones. You can now also specify a reason when > rejecting held messages. > > There was also a gnarly bug, which caused the name of some members to > be the string "None". For the longest time, I couldn't figure out the > reason for it, but it ended up being a simple fix in mailmanclient's > json serialization of display_name, which would result in Python's None > value being passed as string "None" to Mailman's API for subscription. > > There is also better support for filtering visible lists based on the > current vhost, which I see a few people are already waiting for from > mailman-users list. > > A full changelog has been added to each project in the top. These are > still pre-releases and if you are installing via pip, you would need > the `--pre` flag, for e.g. > > $ pip install --pre --upgrade postorius hyperkitty > > As with all other releases, these have also been running on > mail.python.org and lists.mailman3.org for some time now, so it should > be relatively safe to upgrade to. Stable releases for this is now > scheduled in 1 week, hopefully, next weekend. > > -- > thanks, > Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

5 years, 9 months

[MM3-users] Re: Whitelist non subscriber

by Mark Sapiro

On 08/10/2017 07:12 AM, Mark Ziranski wrote: > > I want to whitelist an email address on all lists to bypass moderation. > The email address is not a subscriber. On google I > found accept_these_nonmembers but I do not know how to use it. > Please show me some examples how to whitelist someone(a)example.org. Since this is a Mailman 3 list, I assume you are asking about MM 3. Mailman 3 defines the list attribute accept_these_nonmembers, but it is not currently implemented to actually have any effect, nor is it exposed in Postorius. At the present, I think you would have to create a user record with the address and add that user to all lists with role nonmember and moderation_action 'defer' to apply subsequent tests or 'accept' to unconditionally accept posts from that address. (In MM 2.1, accept_these_nonmembers is a list of addresses and regexps matching addresses whose posts are to be accepted, subject to subsequent tests, and is exposed in the web admin UI) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Added two tasks for Google Summer of Code

by Stephen J. Turnbull

Based on recent threads, I've added two tasks to our 2021 GSoC ideas page: https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021#List_Configura… https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021#User_Profile_T… Bcc'd to David and Johannes because I referred to threads starting with their posts. If you want me to paraphrase in the task description, let me know, but I preferred to do it this way to encourage applicants to join the community. (Note: we haven't been selected yet, so this isn't any more public than the archived mailing lists.) Suggestions of other GSoC tasks and refinements to existing ones welcome. However, please discuss them on the list (or to a core dev privately) unless you have GSoC experience. Google has specific requirements for Summer of Code projects, so there are a lot of important tasks that should not be on that page. If you have an enhancement that you'd definitely like to put on our agenda, and also suggest for GSoC, feel free to file an issue on the tracker and point me, Mark, or Abhilash to it. Steve

5 years

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

by Abhilash Raj

> On Aug 18, 2021, at 6:44 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: > > Abhilash Raj wrote: >> is the config to talk uwsgi protocol and you want to configure Web server to Proxy using the same protocol. You can find that in the uwsgi docs here: https://uwsgi-docs.readthedocs.io/en/latest/Apache.html You probably need an apache module to speak uwsgi, the docs should have the details. >> Notice the URL is uwsgi:// instead of http://. >> Other way is to configure uWSGI to speak HTTP, which can be done by replacing "uwsgi-socket" by "http-socket” in the uwsgi.ini configuration. This might be the easiest for you to try, do make sure to restart the mailman-web service after making the change in uwsgi.ini. > > Thanks, that already helped quite a bit. The website is now loading again, but unfortunately not much else. The site still shows no Connection to REST API. Is your mailman core systemd service up and running? Have you modified the default host:port for Core in mailman.cfg? -- thanks, Abhilash Raj (maxking)

4 years, 6 months

[MM3-users] Re: Problem with debian uipgrade

by Lars Schimmer

Am 08.03.2022 um 21:08 schrieb Mark Sapiro: > Possibly one way to fix this is to run > ``` > django-abmin migrate socialaccount > ``` > where django-admin is the name of your django management command. > > Then running `django-abmin migrate` should succeed. The issue appears to > be due to the face that `django-admin migrate` runs the migrations in > alphabetical order by app. This is fine if migrations were run during > the period after socialaccount.0003_extra_data_default_dict was created > and before hyperkitty.0007_allauth_20160808_1604 was created, but it's > an issue in an installation that wants to migrate > hyperkitty.0007_allauth_20160808_1604 without having previously migrated > socialaccount.0003_extra_data_default_dict. Thx for your always competent answers. In this case I just needed to uncomment the not needed socialaccount lines in mailman3.cfg. As we do not use them. And now I hope for a debian package upgradem or I need to replace them with virtuelenv install as soon as I need to upgrade. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

3 years, 11 months

[MM3-users] Re: Upgrade-path from Ubuntu18LTS to recent mailman release

by Stephen J. Turnbull

Stefan Bauer writes: > As i only use sqlite, i will give it a try to just copy the database files. OK, if sqlite works for you, I think there's no hurry (I don't know of any severe performance issues for small sites, nor security issues). However, I still recommend considering a migration to one of the more powerful RDMBSes like PostgreSQL or MySQL for the long run, because Mailman installations can easily scale to sizes where sqlite becomes a performance bottleneck. It's not that hard to do, because Mailman (mostly via the Django and SQLAlchemy ORMs, but I think there's some "raw" SQL in Mailman) sticks to the common core for SQL, so you can dump the database as SQL commands and then restore it in another SQL database without too much fiddling. You may need some fiddling, such as the database-specific initializations such as setting the encoding for text items and ensuring that sized columns are wide enough, but mostly that will be taken care of by the ORMs. Regards, Steve

3 years, 9 months

[MM3-users] Re: mass remove pending confirmation

by Odhiambo Washington

It's been a while since I saw Abhilash post here. @Abhilash Raj <maxking(a)asynchronous.in> how's it going in Bengaluru? Please come back. On Mon, May 22, 2023, 23:48 Jens Günther <jens.guenther(a)posteo.de> wrote: > Running Mailman 3.3.8 with docker. > > ----- > > Since we migrate some lists from mailman2 to 3, there are a lot of new > users/subscribers and an admin made the mistake to not checkbox the 3. > option that the users don't need to verify their address. > > Now we have a long list of pending confirmations in different lists. Is > there an easy way in the shell to mass remove these pending > mailaddresses so that we don't have to do that one by one? That would be > awsome. > > Regards, Jens. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 9 months

[MM3-users] Re: Post installation issues (recipients refused) with Exim4 in a virtual host environment

by Kyriakos Terzopoulos

I get this in mainlog of Exim: 2023-10-12 10:48:33 H=static.16.91.201.138.clients.your-server.de ([127.0.0.1]) [138.201.91.16] sender verify fail for <shinylist-bounces+kterzopoulos=myproject.eu(a)myproject.eu>: Unrouteable address 2023-10-12 10:48:33 H=static.16.91.201.138.clients.your-server.de ([127.0.0.1]) [138.201.91.16] F=<shinylist-bounces+kterzopoulos= myproject.eu(a)myproject.eu> rejected RCPT <kterzopoulos(a)myproject.eu>: Sender verify failed *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d> On Wed, 11 Oct 2023 at 18:44, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > >> his message sent to kyriakos.terzopoulos(a)gmail.com >>>> >>> > [snip] > > What do you have in the Exim's mainlog? > > -- > 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, 4 months

[MM3-users] Re: Cannot Create New List

by Stephen J. Turnbull

dap1--- via Mailman-users writes: > [2025-11-10 15:35:21 +0000] [5297] [DEBUG] GET /mailman3/ > [2025-11-10 15:35:25 +0000] [5297] [DEBUG] GET /accounts/login/ > [2025-11-10 15:35:28 +0000] [5295] [DEBUG] POST /accounts/login/ I assume the preceding "POST /accounts/login/" was you entering username and password? > Forbidden (403) > > CSRF verification failed. Request aborted. CSRF (cross-site request forgery) is an attack where an attacker tries to spoof your authenticated session. This is prevented by adding a one-time authentication token to the page to ensure that the login procedure all comes from the same host, and then the resulting session cookie is provided only to the authorized user. See https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_P… Somehow your browser or site is doing this incorrectly, and your attempt to log in is being refused. One way this can happen is if you use the "back page" browser button (or otherwise the browser history). Otherwise I don't know how this can happen offhand. Maybe Mark knows. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 3 weeks

[MM3-users] Re: Cannot Run Web Frontend

by Stephen J. Turnbull

Sam Darwin via Mailman-users writes: > Googling: cheapest dns registrar, the results say "Register cheap > domain names from $0.99" and "Starting at $0.99!" If you're not careful, you may be signing up for a $50/year renewal or a very painful extraction of the domain from that registrar to somebody reasonable. Also, I'm like ... do I want to give my credit card data for $1 to somebody who probably keeps it in public AWS S3 bucket? (I did, but it was like 3 years before I bit the bullet on that. :-) But yeah. > Ok. It sounds like a difficult and convoluted exercise in mail flow > configuration. :-) :^) This is not the hill you want to defend unless you're really into it. I have seen worse inside of clients, LOL. All that nonsense aside, thanks for your support! We regularly advertise the non-core developers on the list as a resource, and we appreciate you making that real. 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, 1 week

[MM3-users] Re: hyperkitty threads by month question

by Bryan Fields

On 7/26/24 4:01 PM, Mark Sapiro wrote: > Yes, I suspect this bad date is part of the issue. > > I would do a few things. First, > > SELECT message_id FROM hyperkitty_email WHERE thread_id = 35670; mailmanweb=> SELECT message_id FROM hyperkitty_email WHERE thread_id = 35670; message_id ------------------------------------- 200204151506953.SM01412(a)sunchar.com Yep, that matches the bad date message ID. > If this returns just the one message_id, I would then > > DELETE FROM hyperkitty_thread WHERE id = 35670; > DELETE FROM hyperkitty_email WHERE id = 150555; It's giving an error due to a fk constraint on another table. I'm not familiar with the db structure enough to be certain how to clean/fix it. mailmanweb=> DELETE FROM hyperkitty_thread WHERE id = 35670; ERROR: update or delete on table "hyperkitty_thread" violates foreign key constraint "hyperkitty_lastview_thread_id_5bd4f0ad_fk_hyperkitty_thread_id" on table "hyperkitty_lastview" DETAIL: Key (id)=(35670) is still referenced from table "hyperkitty_lastview". mailmanweb=> DELETE FROM hyperkitty_email WHERE id = 150555; ERROR: update or delete on table "hyperkitty_email" violates foreign key constraint "hyperkitty_thread_starting_email_id_fa7c55f5_fk_hyperkitt" on table "hyperkitty_thread" DETAIL: Key (id)=(150555) is still referenced from table "hyperkitty_thread". > and see if that fixes the internal server error when accessing the > archive. I would also > > SELECT * FROM hyperkitty_email WHERE id = 136872; mailmanweb=> SELECT * FROM hyperkitty_email WHERE id = 136872; id | message_id | message_id_hash | subject | content | date | timezone | in_reply_to | archived_date | thread_depth | thread_order | mailinglist_id | parent_id | sender_id | thread_id | sender_name --------+------------------------------------------+----------------------------------+------------------+-------------------------------------------------------------------+------------------------+----------+-------------+------------------------+--------------+--------------+----------------+-----------+-------------------------+-----------+--------------- 136872 | 200001010102.BAA05112(a)genesis.domino.org | SGZJVBCSRYSHGHR4BB2632INFGYWOJYH | UK GMT roll over | +| 0100-01-01 01:02:34+00 | 0 | | 1999-12-31 20:20:13+00 | 0 | 0 | 3 | | neil(a)genesis.domino.org | 31067 | Neil J. McRae | | | | GMT and CET rolled over without any major incidents. The cellular+| | | | | | | | | | | | | | | networks were busy but thats to be expected. +| | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | Regards, +| | | | | | | | | | | | | | | Neil. +| | | | | | | | | | | | | | | -- +| | | | | | | | | | | | | | | Neil J. McRae - Alive and Kicking. +| | | | | | | | | | | | | | | neil(a)DOMINO.ORG +| | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | That message had "Date: Sat, 1 Jan 100 01:02:34 +0000 (GMT)" in the mbox. It looks like it should be year 2000 from the rest of the headers This message was found by your script too: Date: changed at line 13785764 Date: Sat, 1 Jan 100 01:02:34 +0000 (GMT) Date: Fri, 31 Dec 1999 20:20:13 -0000 > and maybe update the `date` in that entry. I'm actually thinking I need to fix the archive mbox, then delete them and re-import them once they are cleaned. > Also, FYI, assuming those messages with very old Date: headers had > reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script > would fix them, except you have to get the script from > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… > or https://www.msapiro.net/scripts/cleanarch3 because the script in the > latest release has a bug. I tried the dry run option on your script and it gave a bunch of output for bad dates. This was absent on the one shipping with the source. What's interesting is that pipermail seems to have no issue with this, detecting the date correctly. https://mailman.nanog.org/pipermail/nanog/2000-January/137630.html One other thing, I did notice a number of archives not showing up in sequence due to missing "In-Reply-To:" headers from the source. The first message in this is one like this, and pipermail in mmm2 seems to handle this by referencing the subject, https://mailman.nanog.org/pipermail/nanog/2002-April/151325.html, where as in hyperkitty it's an orphaned thread. Is the archive tool in pipermail's import more robust in this manner? I'd argue it's common to have missing In-Reply-To: headers where the subject and time would need to be used to infer the likely thread. I'll agree this is a major violation of the relevant RFC's to be missing this, but many MUA's (M$) are famous for doing just this. Thank you, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 year, 7 months

[MM3-users] Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Mark Sapiro

On 8/25/25 12:42, Flo via Mailman-users wrote: > Hi, > > I have setup in Debian Trixie mailman3-full and came that far, that I > have created a mailing list. I can sent emails to the members. Your primary support resource for the Debian package is Debian. See https://wiki.list.org/x/12812344 > However when I send from an email which is non-member the message is > held. If I want to accept this message as list admin, I get: > > `An error occurred while processing your request.` > > And I get an email: > > `Internal Server Error: /mailman3/postorius/.../held_messages > > TemplateSyntaxError at /postorius/lists/.../held_messages > 'humanize' is not a registered tag library. Must be one of: You need to add 'django.contrib.humanize' to the INSTALLED_APPS list in settings.py. If you Debian packages don't do this, it should definitely be reported to Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Finding a user to delete them

by Quanah Gibson-Mount

Due to a bug in mailman3, I have an incorrect user that's been created via github auth that has no confirmed email address yet. I've been poking around the user manager documentation (why is there no UI for user management???), and after adding in bits that are missing from the official documentation (<https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/usermanager…> is missing "from mailman.testing.documentation import dump_list" despite using dump_list repeatedly in its examples) I can't find the user. I have the confirmation email mailman3 sent out, that tells me the username mailman3 created for the incorrect account is "quanah98", but the user manager documentation doesn't detail how to find a user by their username, only their email. And apparently if the email hasn't been confirmed (and I *do not* want it confirmed), you can't find them by email. Suggestions on how to track down this user so I can delete them would be much appreciated. Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 11 months

[MM3-users] Re: Migrating Mailman 3 lists

by Stephen J. Turnbull

Andrew Hodgson writes: > Mark Sapiro wrote: > >On 5/19/20 7:25 PM, Mark Dadgar wrote: > >> For reference my pgloader script looks like: > >> > >> load database > >> from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db > >> into postgresql://mailman3:XXREDACTEDXX@localhost/mailman > >> > >> with include drop, create tables, create indexes, reset sequences, no truncate > Have you tried this without indexes and then run the migrate > script? It may re-create them as part of the schema upgrade > check. That was my immediate guess. I'm not an SQL expert, but I believe that sequences and indexes are different entities, they're both optimizations that you don't need (ie, ignoring performance), and implementations differ on how they're implemented. Eg, if sqlite implements them as tables, while PostgreSQL has a special data structure, you could run into this kind of behavior. I'm pretty sure that these will be recreated appropriate to the new database when the schema validator is done. But don't trust me, and *do* keep a backup. ;-) Steve

5 years, 9 months

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

by Mark Sapiro

On 9/10/22 22:22, Stephen J. Turnbull wrote: > > Will let you know if I find anything. Mark will be back soon, too. Yes, I'm back and am looking at this. I'm looking at the traceback at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and I would like to get a copy of the shunted 1662376669.3194733+25b74de3b7cd8a28d0c3cf5b6cc6fc582726efec.pck file. If that is not available, any of the shunted files from the same `Uncaught runner exception: 'list' object has no attribute 'encode'` will do. Also, the same post contains a traceback from mailman_hyperkitty indicating the message has no Message-ID header. This is possibly related to the fact this is an anonymous list. For anonymous lists, the original Message-ID is removed because it can reveal the sender's domain, but it should always be replaced by a generated one. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/clean… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Hyperkitty

by Odhiambo Washington

On Mon, Jan 30, 2023 at 3:41 PM Onyeibo Oku <onyeibo(a)schemefusion.com> wrote: > I am having a similar issue as described below. I don't have > /etc/mailman3/mailman3-web.py > > I added MAILMAN_ARCHIVER_FROM variable in /etc/mailman3/settings.py > instead. It did *not* solve the issue. Hyperkitty is blank. > More questions below > > On January 27, 2023 7:30:22 PM GMT+01:00, Massimiliano Paragnani < > max.paragnani(a)gmail.com> wrote: > >SOLVED! > >I edited /etc/mailman3/mailman3-web.py adding in MAILMAN_ARCHIVER_FROM = > >the ip of the server and finally starts to work > > Is this a string value or a list? MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') So an array?? > Perhaps I did something wrong here. Any documentation on this? > https://mailman-web.readthedocs.io/en/latest/settings.html > > My instance is not archiving. > Things to check: 1. Is your MAILMAN_ARCHIVER_KEY value in settings.py (quoted here!) the same as api_key in mailman-hyperkitty.cf (unquoted here!)? 2. Your MM3 log files - do they say anything? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: ValueError: The ADMINS setting must be a list of 2-tuples.

by David Partain

Hi Mark, Helpful, as always. Thank you. And do I feel silly. That was pretty darned obvious. In any case, it's fixed. Cheers, David ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 21, 2024 01:46 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: ValueError: The ADMINS setting must be a list of 2-tuples. On 3/20/24 13:23, David Partain via Mailman-users wrote: > raise ValueError("The ADMINS setting must be a list of 2-tuples.") > ValueError: The ADMINS setting must be a list of 2-tuples. > > Our ADMINS setting in /etc/mailman3/settings.py has > > ADMINS = ( > ('Mailman Suite Admin', 'someone(a)our.domain', 'someoneelse(a)our.domain'), > ) > > Can someone point me in a direction to correct this? 2-tuples, not triples. E.g. ADMINS = ( ('Mailman Suite Admin1', 'someone(a)our.domain'), ('Mailman Suite Admin2', 'someoneelse(a)our.domain'), ) -- 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: Cannot Create New List

by Mark Sapiro

On 11/9/25 10:04, dap1--- via Mailman-users wrote: > > I can now see the list. I can't find the URL for members so I'm not sure if this really worked. Have you created a Django superuser for yourself? mailman-web createsuperuser You need to do that and then go to https://your.host/accounts/login/ and log in as that user. Then if you go to https://your.host/mailman3/lists/lllllllllll@ddddddddd.net/ you will see a Users dropdown in the secondary nav bar and can view members, nonmembers, moderators and owners. You can also go directly to https://your.host/mailman3/lists/lllllllllll@ddddddddd.net/members/x/ where x is one of member, nonmember, moderator or owner. > It seems the archives were imported but when I go to that page there are no entries: To what URL are you going? Are you logged in? depending on the list's archiving settings you may need to be logged in as a superuser or list member to see the archives. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Customizing Look and Feel?

by Mark Sapiro

On 12/27/18 7:42 PM, Joel Lord wrote: > Is it possible to customize the look at feel of the web interface at > all? I have some lists that really require that subscription requests > include full name, to make the workload on the moderators, well, > workable in keeping a closed list tight. I've found where the "Your > name (optional)" text is in list_forms.py, but modifying that strikes me > as a poor plan. > > Changing that text would be lovely. Actually making that field required > would be seriously awesome. > > Is this possible in the current code base (3.2.0) without doing > ill-advised things modifying source code? None of this is really possible in Postorius without modifying source code. However, Postorius is just an example of a web list management UI. While it is non-trivial, it is possible to build your own web UI that either communicates directly with Mailman core's REST API or communicates via MailmanClient. -- 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: Unsubscribe Notifications Clarification

by Abhilash Raj

On Wed, Sep 2, 2020, at 7:32 AM, Brian Carpenter wrote: > I am trying to understand how Mailman 3 handles unsubscribe > notifications. From my testing I see the following behavior: > > 1. If list member sends email to listname-leave@listname, an > unsubscribe notification is sent to both list owner and list member if > list settings have them enabled. > > 2. If list list member is a registered user of Postorius and he uses > Postorius to unsubscribe, then no notification is sent out to either > list owner or list member, even if list settings has unsubscribe > notifications enabled. > > Is this correct? This is a bug in Core, for which I have opened https://gitlab.com/mailman/mailman/-/issues/759 It seems like the Unsubscriptions via the API do not follow the right codepath and just unsubscribe the user. It also does not seem to take the unsubscription policy into account. > Brian > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 6 months

[MM3-users] Re: Problems with New MM3 Installation

by Jeff

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

4 years, 9 months

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Stephen J. Turnbull

Chihurumnaya Ibiam via Mailman-users writes: > On Wed, Feb 4, 2026 at 9:06 PM Stephen J. Turnbull <steve(a)turnbull.jp> > wrote: > > > Chihurumnaya Ibiam via Mailman-users writes: > > > systemctl shows the service is still active, > > The fact that there is a systemd service implies that dovecot > > will be running by default unless it is disabled. > There's no service file for dovecot, I didn't create one. As far as I know, if systemd knows about a service, there's a control file somewhere. systemd will create a unit from an rc file in /etc/rcN.d if there is one. (I was perfectly happy with SysV init, but I guess systemd makes hyperscalars happy.) I don't know if "systemctl disable" works on those. > I configured mailbox transport because that was how I was able to get lmtp > to run on port 24, Something like that would be necessary for Dovecot, which I believe can be configured to automatically create a mailbox for any address. It is not necessary for Mailman, which tells Postfix how to deliver to Mailman lists in the postfix_lmtp table. You can find that in /opt/mailman/mm/var/data, if you followed the virtualenv installation to the letter. 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 not sure this is why the confirmation mails are getting rejected, but at a guess, for some classes of mail Postfix will first try the whole address, and if that fails to route, it will remove the extension (starting with "+"), and try again. Perhaps it does NOT do that for the mailbox_transport. > there wasn't any service before that and the documentation > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> > for setting up a mail server mentions postfix delivering > by default over port 24. What it says is this: Postfix will deliver via LMTP over port 24 by default, however if you are not running Mailman as root, you’ll need to change this to a higher port number, as shown above. Are you running Mailman as root? If so, stop it, change lmtp_port back to 8024 in mailman.cfg, and stop and start Mailman to regenerate the postfix_lmtp.db. There's no need for running as root unless you have an MTA that is hard-coded to think that 24 is the one and only lmtp port handed down from Mount Olympus. Postfix knows better. Furthermore, you should NOT run mailman as root if there's any alternative. Mailman occasionally crashes for various reasons (I've never seen it take Python down, but then, if there were an exploit, I wouldn't), and is not securely authenticated (I mean, it's reasonably secure, but it is just a password, and once you get in to Mailman core, you're the superuser for Mailman) and if there *is* an exploit and Mailman is running as root, you've got system root, too. Don't run Mailman as root. Please. > Disabling this means there's no lmtp to be used by postfix, except I'm > missing something. Yes, you're missing something. Postfix is always able to speak LMTP, and is very flexible about when to do so. If you followed the virtualenv installation to the letter, you have transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp in main.cf (perhaps there's other maps there), and in that file you have lines that end in "lmtp:[127.0.0.1]:24", which tell Postfix "connect to IP address 127.0.0.1, port 24, and speak LMTP to that connection." If you change lmtp_port to 8024 and restart Mailman as suggested, all those lines will change to "lmtp:[127.0.0.1]:8024" and Postfix will be happy to deliver to Mailman that way without being root. > I set the port number for lmtp to be 24, and that's what I used, I'm not > sure if Mailman sets up lmtp itself, > if it does then I'll have to remove the config for that. > > I've stopped dovecot after our conversation so it's no longer running, the > only way the port is open is through the > config I set in postfix for mailbox_transport. That should get it working, except that with mailbox_transport set there's a good chance that Mailman functions that use "+" extensions will mess up as described above. Those functions are confirmations and I think VERP probes. > There's just one active user, which is me, and I also have root access. > I setup authentication for postfix because I'm used to setting it up that > way, this was a force of habit. > I assumed postfix would run just fine if I set postfix up the way I usually > set it up. It might. But "Internet Mail" is another name for Dante's Third Circle of Hell. (You must have committed a horrible felony to be sentenced to administer an Internet mail host. :-D That's just a joke, it sounds to me like your "usual setup" is quite solid and secure.) Anyway, any deviation from the setup described in virtualenv.html is a chance for everything to go wrong. "What I usually do" is just not deep enough knowledge if you're working with a new mail application with complex routing needs. > > 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. > postgres 3568035 postgres 5u IPv6 160224851 0t0 TCP localhost:postgresql (LISTEN) > postgres 3568035 postgres 6u IPv4 160224852 0t0 TCP localhost:postgresql (LISTEN) These are PostgreSQL listening for database connections. > python3 1592924 mailman 22u IPv6 177685051 0t0 TCP localhost:48638->localhost:postgresql (ESTABLISHED) This is Mailman talking to Postfix. > postgres 1592954 postgres 9u IPv6 177686124 0t0 TCP localhost:postgresql->localhost:48498 (ESTABLISHED) > postgres 1592912 postgres 8u IPv6 160224857 0t0 UDP localhost:36787->localhost:36787 + 21 more copies of the above, differing only in the PID. Don't know what's going on with those, not a PostgreSQL wizard. I probably should have specified TCP in the lsof command, UDP applications are either trivial or they are black magic. It appears that *nothing* is listening on or connected to port 24. I'm not sure how that works. I'm guessing that when mail was getting to Mailman, Mailman had opened port 24 and Dovecot was cut out of the loop (maybe check logs for Dovecot complaining it couldn't bind to port 24?) > > > [mta] lmtp_host: *.*.*.* > > > > That should be 127.0.0.1. Mailman should not be listening on network > > interfaces other than the loopback (localhost). > > Yes, it is. OK > > > [mta] lmtp_port: 24 > > > > This can't work if Dovecot is configured to use the same port, as is > > Dovecot's default. > I've stopped the service. OK > > > [mta] outgoing: mailman.mta.deliver.deliver > > > [mta] smtp_host: 127.0.0.1 > > > [mta] smtp_port: 25 > > > > Those are normal. > > > > > [mta] smtp_pass: ************** > > > [mta] smtp_user: mailman > > > > This is going to cause Mailman to try to authenticate to Postfix. > > That's OK if it's what you want and Postfix / saslauthd has been > > properly configured to accept Mailman's credentials. Otherwise, > > they must be left empty to disable authentication. > Okay. > > > The Message-ID being the way it is doesn't seem like a > > > configuration issue, if it is then how do I look into it? > > > > Probably you don't have the full hostname in Postfix's myorigin or > > myhostname parameter. > > I do have the full hostname there, I also have it in /etc/mailname. I don't understand it then. Perhaps the mail composition client is providing the Message-ID. > > If not, I would guess that's a spammer who is somehow spoofing > > the PTR record. > The log entry before that warned of the same, they're definitely a spammer. > Relay access is denied though, so no mails are going through. OK. > No, I mean smtps. Same problem except the port that Mailman is *not* using is 465. > > I don't think permit_auth_destination does what you think it does. > > Here's the Postfix doc: > > > > permit_auth_destination > > Permit the request when one of the following is true: > > > > - Postfix is a mail forwarder: the resolved RCPT TO domain > > matches $relay_domains or a subdomain thereof, and the address > > contains no sender-specified routing (user@elsewhere@domain), > > - Postfix is the final destination: the resolved RCPT TO domain > > matches $mydestination, $inet_interfaces, $proxy_interfaces, > > $virtual_alias_domains, or $virtual_mailbox_domains, and the > > address contains no sender-specified routing > > (user@elsewhere@domain). > > > > I did read the documentation before adding it, I definitely misunderstood > what it meant, and after looking at the old > documentation, it makes sense not to add it. > > Could you help me understand what the above means? I gotta run now, I'll come back to it later. You're probably asleep, anyway. :-) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month

[MM3-users] Re: Installation Wooes

by Mark Sapiro

On 5/2/20 12:51 AM, Samir Faci wrote: > A few questions about an Ubuntu install. > > I managed to add my domain to hyperkitty, created a new list and now i'm > getting this behavior: > AttributeError: module 'time' has no attribute 'clock' > I'm on python 3.8.2 It time.clock() went away in Python 3.8. Mailman versions older than 3.3.0 are not compatible with Python 3.8. You need to upgrade Mailman core. > Question #2. I'm setting up mailman 3 on sqlite for simplicity's sake. Do > people find the performance of mysql / postgres worth the upgrade? It depends on the size of your installation - how many lists, how many list members, frequency of posts and so on. You may find <https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgre…> of interest. > 2B. Is there a migration path if I want to switch to mysql at a later date? The migration path mostly consists of migrating the data from the SQLite database. -- 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: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Mark Sapiro

On 6/15/20 12:37 PM, Gilles Filippini wrote: > > There are 4 emails stored into this folder. 3 of them are spam, and the > last one is a legitimate email. This is annoying that such emails could > accumulate and stay into var/archives/hyperkitty/spool/ forever, causing > more and more hyperkitty errors. > > Any idea how to make their processing more error proof? Change the offending .encode() method to add errors='replace'. The traceback from the error should tell you where it is. You could also open an issue at <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If you do that, please include an error traceback if possible. If there is not a traceback in mailman.log associated with the error, there might be one in HyperKitty's log (configured in Django's settings). Also, including enough of a message to duplicate the issue is very helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Hyperkitty

by Stephen J. Turnbull

Mark Labeste writes: > ]$ mailman conf -s archiver.hyperkitty > Usage: mailman conf [OPTIONS] > Try 'mailman conf -h' for help. > > Error: No such section: archiver.hyperkitty `mailman conf` reads the configuration. There is no configuration for HyperKitty in the default configuration (mailman/config/schema.cfg and the active mailman.cfg). You need to have an [archiver.hyperkitty] section in the active mailman.cfg. If you never added one, check the documentation for what needs to go in there and add one. If you already have a HyperKitty section, run `mailman info`, which will tell you what mailman.cfg is being used. If it gives an unexpected answer, you're probably just running `mailman` in a "wrong" place (wrong only because the search algorithm finds the unexpected configuration file). Try running `mailman` from a different current working directory. There is one tricky point. For reasons I don't understand, `mailman` will often create var/etc/mailman.cfg, and it will be empty except for comments. I've found it very easy to trip over that file, so I usually do `ln -s /etc/mailman3/mailman.cfg var/etc/mailman.cfg` to placate the evil spirits.

2 years, 5 months

[MM3-users] Re: default processing

by Gerald Vogt

Hi, just to chime in: the bigger issue I see with our (non english native) list owners is the confusion between "Accept immediately (bypass other rules)" and "Default processing", in particular during moderation of a held message to set the status of a new list member which was hold for moderation as list default. People tend to choose "Accept immediately (bypass other rules)". "Default processing" doesn't include "Accept" which I think is the reason. They want to accept the member. They want to accept it now, i.e. "immediately". They choose Accept. I keep regularly telling them that they don't want "Accept immediately (bypass other rules)" ever. But it's not intuitive for list owners with litte moderation volume. I check the database occasionally for members set to immediate and change it to default processing. I'll keep reminding people. But it still happens. I think something like "Default Accept" or "Standard Accept" would be better. And also changing the "Accept immediately" to something which makes it more clear that it's "dangerous" would be helpful to keep people from choosing it. But I haven't found the best names for them either, yet. I do wonder somehow if there is really a use case where you would actually need "Accept immediately". For our lists I haven't seen it, yet, but to be honest, it's not totally clear to me what the default processing rules do exactly... Cheers, Gerald On 13.08.25 14:59, Sam Darwin via Mailman-users wrote: >> I don't understand why you are confused. > > I understand now, and I'm not confused. However before, when I was learning about this topic, I encountered a problem, and it's worth trying to make it easier. Even now that I 'understand', the issue continues. > > It's about terminology and language, and not about the functioning of mm3. > > There are distinct choices. You'd like to easily remember them, in your mind, and be able to quickly explain to yourself, or to someone else. > > - "list default". I would just think "Ok, clearly that's the default. Look at the name there. List default. The default." > > - "default processing'. I would just think "Ok, clearly that's the default. Look at the name there. Default processing. The default." > > Yes, we know they're different. What is the mnemonic device to remember each one. Couldn't they be named differently? > > 99% of the time, you can remember "a config file", "the executable", "the bin directory", you can remember a thing based on what it's called, and those don't conflict with each other. > > But if you name both of your sons "Michael" even though you understand they are separate people, it causes headaches. > > If you choose a naming scheme such as "the red automobile" versus "the red car", and then ask the person "don't you understand, those are two different things for us. Why are you confused? They are two separate things. You know that. Why are you confused." Answer: the problem is the choice of naming. > > So ask the question is "default processing" the only compelling name for that functionality? The word "default" is already used for "list default". Why use it again? Why not "Standard Processing -- run additional checks and accept the message." Or "Regular Processing". "Typical Processing". Anything besides "default". Invent a new word: quark-spark processing. (well, don't use 'fallback' because it's just a synonym.) > > well, just trying to answer "why you are confused". maybe I am being too repetitive already. > _______________________________________________ > 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

6 months, 3 weeks

[MM3-users] Re: No resend after delivery bouned

by Mark Sapiro

On 1/31/22 06:47, Axel Rau wrote: > My listserver has been blocked with 550 and I received > bounce score on <list_add> has been incremented. > notifications. > After resolving the block issue, I'm now waiting for mailman to resend > the mails. > Now, after 3 hours, nothing has happened so far. And nothing will. Mailman sent the message originally and when it was done sending it, it discarded the outgoing message. The message may have been archived depending on the list's archiving settings, but that's it. No version of Mailman 2.1 or Mailman 3 has ever automatically resent bounced messages. If the failures are temporary, the MTA should keep the message queued and retry up to a limit before reporting a bounce, but that's it. The best you can do is get the messages from the archive (you can export a mbox from Hyperkitty or get the messages from Mailman's var/archives/prototype/LIST_ADDRESS/new/ directory) and manually resend them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected

by Christian Stalberg

Environment: Debian 10; Postfix 3.4.14; GNU Mailman 3.3.5; Mailman Core API Version 3.1; Mailman Core Python Version 3.7.3 Digging a hole after having simply created a new mailing list. This has not happened before. Steps taken: -Created list via web interface -Added subscribers via web interface -Sent email to listname -Received error bounce: This is the mail system at host zarathustra.ccalternatives.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <Deepadaptation(a)lists.ccalternatives.org>: mail for lists.ccalternatives.org loops back to myself -Added lists.ccalternatives.org to the mydestination line in /etc/postfix/main.cf and restarted Postfix -Now a new error message: <Deepadaptation(a)lists.ccalternatives.org>: host lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command)

3 years, 8 months

[MM3-users] Re: serving /static-content within /mailman3-web-Folder - change in recent mm release

by Stefan Bauer

thank you Mark, that did the trick :) Am Do., 29. Sept. 2022 um 18:33 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 9/29/22 06:50, Stefan Bauer wrote: > > Hi Folks, > > > > during our migration to latest MM we noticed, that nowadays, the static > > content is not served from within mailmans base directory, but from > outside. > > > > old MM3: > > > > domain.tld/mailman3/static/django-mailman3/js/main.js > > > > new MM3: > > > > domain.tld/static/django-mailman3/js/main.js > > > > Is there a chance to change it to the old behavior? > > > See the Django settings STATIC_ROOT and STATIC_URL. > > > -- > 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/ >

3 years, 5 months

[MM3-users] Re: Sendgrid experiences

by Andrew Hodgson

Stephen J Turnbull wrote: >2023-05-10 03:49 に Andrew Hodgson wrote: >> Sendgrid is maintaining the Message-Id header which is good for >> archiving. It is re-writing the Return-Path header though which means >> that bounce handling in Mailman won't work, but I think all the >> services do this in some way so I am happy to live with that for the >> moment. >How does it rewrite the Return-Path? Returned mail is not something that such a service would be able to handle properly (although they can help with apparently returned spam). If mail is legitmately sent and returned as undeliverable, only the author or their agent will know how to handle it. So such >services should provide some way to find out about returned mail. An example: Return-Path: bounces+[Sendgrid GUID]-andrew=hodgson.io(a)em6096.lists.hodgsonfamily.org Sendgrid provide information about bounces but crucially that bounce isn't forwarded back to the original return-path sender (i.e, Mailman). A few people have pointed out they can provide list hosting at a cheaper cost than Sendgrid so I'm looking for alternatives again. Andrew.

2 years, 9 months

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

by Odhiambo Washington

On Sat, 25 Jul 2020 at 22:11, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/25/20 11:37 AM, Odhiambo Washington wrote: > > On Sat, 25 Jul 2020 at 19:58, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> This is a packaging glitch with the flufl modules. Remove and reinstall > >> them. > >> > >> pip uninstall flufl.bounce flufl.i18n flufl.lock > >> pip install flufl.bounce flufl.i18n flufl.lock > >> > >> > > It would appear that luck isn't just on my side: > > > > root@gw:/opt/mailman/mm # pip uninstall flufl.bounce flufl.i18n > flufl.lock > ... > > > You need to run these pip commands in your venv. I.e. do this > > > [root@gw /opt/mailman/mm]# source /opt/mailman/mm/venv/bin/activate > > before the pip uninstall and pip install. > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> That has solved the problem. Thank you very much. I have taken note of that. for my NOTES. Finally, I have adapted your init script to get some rudimentary one that I could use on FreeBSD. I have to change /opt/mailman to be owned by mailman3:mailman3 (because I have "live" MLs on this server, using mailman-2.1.34. I am not sure if they can co-exist. I suppose they could, but what might be the security implication, if any?? This is what the init script looks like (rudimentary!!): (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 ### BEGIN INIT INFO # Provides: GNU Mailman # Short-Description: Mailman3 Service # Description: service control for Mailman3 ### END INIT INFO PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: DESC="GNU Mailman service" DAEMON=/opt/mailman/mm/bin/mailman NAME=mailman USER=mailman3 GROUP=mailman3 # Needed by click export LANG=en_US.UTF-8 # Exit if the package is not installed [ -x "$DAEMON" ] || exit 0 # Load the VERBOSE setting and other rcS variables #. /lib/init/vars.sh # Define LSB log_* functions. # Depend on lsb-base (>= 3.2-14) to ensure that this file is present # and status_of_proc is working. #. /lib/lsb/init-functions case "$1" in start) [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" # use --force to remove a stale lock. /usr/local/bin/sudo -u $USER $DAEMON start --force ;; stop) [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" /usr/local/bin/sudo -u $USER $DAEMON stop ;; status) /usr/local/bin/sudo -u $USER $DAEMON status ;; reopen) /usr/local/bin/sudo -u $USER $DAEMON reopen ;; restart) log_daemon_msg "Restarting $DESC" "$NAME" /usr/local/bin/sudo -u $USER $DAEMON restart ;; *) echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 exit 3 ;; esac It does start mailman3 for sure, but also complains after a few seconds with the message: (venv) [root@gw /usr/local/etc/rc.d]# */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: DeprecatedWarning: Call to deprecated function __init__(...). API class may be removed in a future release, use falcon.App instead.* * **kws)* But: (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman 11677 - Is 0:00.01 /usr/local/bin/python /usr/local/mailman/bin/mailmanctl -s -q start (python2.7) 15860 - S 0:07.86 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s (python2.7) 16310 - S 0:07.43 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s (python2.7) 16928 - S 0:07.07 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s (python2.7) 17335 - S 0:07.47 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s (python2.7) 17975 - S 0:07.02 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s (python2.7) 18419 - S 0:20.06 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s (python2.7) 19015 - S 0:07.13 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s (python2.7) 19131 - I 0:00.15 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s (python2.7) 27273 - Is 0:01.64 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/master --force -C /opt/mailman/mm/mailman.cfg (python3.7) 28526 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=archive:0:1 (python3.7) 28627 - I 0:01.77 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=bounces:0:1 (python3.7) 28988 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=command:0:1 (python3.7) 29341 - S 0:01.69 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=in:0:1 (python3.7) 29978 - S 0:01.68 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=lmtp:0:1 (python3.7) 30843 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=nntp:0:1 (python3.7) 31541 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=out:0:1 (python3.7) 31675 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=pipeline:0:1 (python3.7) 32181 - S 0:01.77 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 (python3.7) 33166 - I 0:01.65 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=retry:0:1 (python3.7) 33694 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=virgin:0:1 (python3.7) 34600 - S 0:01.69 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=digest:0:1 (python3.7) 41250 - S 0:00.01 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 (python3.7) 41533 - S 0:00.01 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 (python3.7) 98450 - I 0:00.45 httpd: mailman-web (httpd) 59886 0 S+ 0:00.00 grep mailm Assuming that I am using mod_wsgi with Apache, and that I have configured apache right using https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… .. should I be able to access the MM3 web UI?? At that point, I am feeling somewhat confused as to what to try next. (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log Jul 25 22:53:16 2020 (40670) Master started Jul 25 22:53:18 2020 (42036) bounces runner started. Jul 25 22:53:18 2020 (45205) out runner started. Jul 25 22:53:19 2020 (41191) archive runner started. Jul 25 22:53:19 2020 (46670) retry runner started. Jul 25 22:53:19 2020 (44567) nntp runner started. Jul 25 22:53:19 2020 (43069) in runner started. Jul 25 22:53:19 2020 (46960) virgin runner started. Jul 25 22:53:20 2020 (45720) pipeline runner started. Jul 25 22:53:20 2020 (47326) digest runner started. Jul 25 22:53:20 2020 (43755) lmtp runner started. Jul 25 22:53:20 2020 (45922) rest runner started. [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: http://127.0.0.1:8001 (45922) [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 Jul 25 22:53:21 2020 (42743) command runner started. How do I access the web UI for MM3 now? Thanks in advance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, should I install the SASL authentication daemon saslauthd and start it? El mar., 25 jul. 2017 a las 15:40, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 01:19 PM, Rafael Mora wrote: > > What should I do to tell Postfix to use my domain?? for example send > emails > > using the email account mailing(a)labbrands.com > > > If what you're asking is how to configure Postfix to relay all outbound > mail via some other email server, that is a Postfix configuration question. > > If I thought I could give you a simple answer and that would be the end > of it, I'd try, but in your case every answer leads to another question, > so I suggest you start here to learn about configuring Postfix > <http://www.postfix.org/documentation.html>. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

[MM3-users] Migrating from Listserv 17 to Mailman 3

by Stephen J. Turnbull

Cooper, Robert A via Mailman-users writes: > Howdy! Does anyone have or know of a guide to migrate from Listserv > 17, including list archives, to Mailman 3? I doubt there is one. > I've found documentation on moving to Mailman 2, but those don't > seem to apply to the newer version. There are about seven steps in the process: 1. Get the list configurations out of ListServ. 2. If separate from 1, get the user profiles and subscriptions out of ListServ. 3. Get the archives into mbox form. 4. Create the Mailman 3 lists. 5. Adapt ListServ configurations as much as possible to Mailman list attributes (there's not much you can do automatically unfortunately).. 6. Import the lists into Mailman. 7. Import the archives into HyperKitty. Steps 1--3 are identical to the same steps for Mailman 2. Steps 4 and 7 are well-documented (eg, for importing from Mailman 2), and it doesn't matter what MLM you're importing from. Step 5 is manual labor. Step 6 I can't say much about until I've seen the result of step 5. HTH Steve

2 years, 3 months

[MM3-users] Re: An issue with the postfix_domains directory creation and the mailman start command.

by Ron

On 2024-07-10 08:48, Keith Christian via Mailman-users wrote: > 4 [mailman3@somehost ~]$ sudo ls -l > /opt/mailman3/mm/var/data/postfix_domains > 5 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': > No such file or directory > 6 [mailman3@somehost ~]$ ls -dl/opt/mailman3/mm/var/data/ > 7 drwxr-xr-x. 2 mailman3 mailman3 6 Jul 5 13:38 > /opt/mailman3/mm/var/data/ > > What should I do about lines 4-7? Thought it might be a permissions > issue but it's owned by the correct user. My guess would be that mailman is using a different location for storing these files (aliases, domains, etc.) One could search the system for where (if) the files were created with something like: find / -name "postfix_domains" Another (better?) thought would be to compare the [paths] pointed to by the "layout: ..." in /etc/mailman3/mailman.cfg to ensure it's pointing where you expect (in this case, /opt/mailman3/mm/var/data for data_dir). As user mailman, running: mailman conf to double check the "layout: ..." that's in use.

1 year, 7 months

[MM3-users] Re: update_index

by Mark Sapiro

On 04/03/2018 09:02 AM, Darren Smith wrote: > Hello, > > If I'm reading the docs correctly, when we run manage.py update_index, it > should be an incremental index of new emails that have been added since the > last time update_index was run - can anyone confirm that this is the > expected behavior? Or is there another command line option that I am > missing? There are two ways to run update_index. Hyperkitty's update_index is incremental and is run by manage.py runjob update_index Running manage.py update_index runs haystack's update_index which with no options does a full update. Run manage.py update_index --help to see the options. The incremental 'manage.py runjob update_index' should be run every minute by 'manage.py runjobs minutely' assuming cron is running the periodic Django jobs, so running either update_index job manually shouldn't be necessary ... > So...can anyone help with how to get the update_index to do only emails > added since the last time the update_index was run? manage.py runjob update_index -- 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: How to setup mailman?

by Jacob Bargery

Depends on what you are wanting to install it on. As for the API need, not really sure what you are meaning with that so I for installing Mailman 3 similar to what you see here with Postorious and Hyperkitty, I would recommend some great instructions I could find by Kelly Close who often posts on here. They are at this link: https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… They worked great when I was installing for a ubuntu 18.04 set up. However I needed to install on 20.04 and that required a few deviations and was a complicated install, so if you can do 18.04 I highly recommend the link above. (Kelly, if you read this, thank you for making those instructions, they saved me when beginning my set up) Note: Using instructions and not installing from source means that a lot of people can't help you with problems you come across during install. I found people still try to help but it's much harder. I will link the options from the Mailman website, however I found them difficult to follow when I was trying. https://docs.mailman3.org/en/latest/install/install.html

5 years, 7 months

[MM3-users] Re: Mailman 3 installation from latest Debian packages

by Mark Sapiro

On 2/12/21 4:49 AM, Matthew Blissett wrote: > Hi, > > I've installed mailman3-full 3.3.3-1 from Debian bullseye (Debian testing). > > The dropdown controls on the UI for Postorius (e.g. "Subscription > requests", "Mass operations" and the username button to log out) and the > similar controls on Hyperkitty (e.g. "Threads by month") do not work. > You can see the latter at > http://newlistszm.gbif.org/mailman3/hyperkitty/list/test@newlistszm.gbif.or… Everything works as expected at <https://lists.mailman3.org/mailman3/> and <https://mail.python.org/mailman3> which are installed from source. > Could this be a problem with the Debian packaging, or perhaps my > configuration -- which is very close to the defaults (i.e. Mailman and > Apache configuration generated by dpkg). I can't speak to the Debian package possibility, but it might possibly be related to the way your browser handles the javascript. I don't know anything in configuration that would cause this. -- 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: Configure administrative users via command line?

by Mark Sapiro

On 7/18/23 11:38, kjohnson(a)eclypse.org wrote: > > How can I configure administrative users via command line? I need to process a moderation request. I have root access on the server. A pointer to the appropriate documentation would be more than welcome. Thank you to anyone who can provide help. I'm not sure what you want. If you are an owner or moderator of a list or a superuser, you can handle moderation requests via Postorius. If you are a list owner or a superuser, you can manage owners and moderators via Postorius. You can add superusers via the command line django admin `createsuperuser` command. It might be good if the command line `mailman addmembers` and `mailman delmembers` commands accepted a `role`, but they don't. You can manage owners and moderators via the REST API which you can access via curl. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. You can also do this via `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Regarding this: # To be added to Django's settings.py EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = <username> EMAIL_HOST_PASSWORD = <password> What should I use for username and password? Should I keep the localhost on the host param? Thanks El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > 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, 7 months

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Mark Sapiro

On 5/8/20 10:36 AM, Seth Seeger wrote: > > I believe this is what I’m seeing. I was able to change the displayed name by changing the original entry in Django. That name displays no matter what the URL hostname is. This is strictly a Django thing. The HyperKitty template, hyperkitty/templates/hyperkitty/navbar-brand.html, contains this: <a class="navbar-brand" href="{% url 'hk_root' %}">{{ site_name }}</a> {{ site_name }} is provided by Django when the template is rendered. In my case in my test installation, I have three sites in django.Sites: Domain name Display name example.com example.com msapiro.net msapiro.net msg1.msapiro.net msg1 example.com is a dummy, and it is also referenced in my settings by SITE_ID = 0 which may have something to do with my success, but if I go to HyperKitty via https://msapiro.net/, I see the site name msapiro.net, and if I go via https://msg1.msapiro.net/ I see the site name msg1. -- 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: Moderation for nested mailing lists

by Mark Sapiro

On 11/18/20 8:48 AM, peterbw(a)gmail.com wrote: > Hi Everyone, > > I have a list that has other mailing lists as members. When a non-member posts to this list I receive a moderation message. After approving the moderation message I then receive a lot of other moderation messages for the sub-lists that are members of the "top-most" list (since the non-member is not a member of any of the sub-lists). Is there any way to approve a message for moderation once and have all sub-lists automatically approve the message? That capability doesn't exist. If the poster were a member of the top-most list this issue <https://gitlab.com/mailman/mailman/-/issues/794>, currently not fixed, would apply, but for non-members, even that wouldn't do. If the same nonmembers post repeatedly, you could set the moderation action for their various non-member records to defer to accept their posts without moderator intervention, but for one-offs, this doesn't save any effort. -- 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: Virtual alias + shell

by Mark Sapiro

On 5/26/23 9:51 AM, alopez(a)ac.upc.edu wrote: > Now I have created the mailing list with 'mailman create' but I get this error: > > postmap: warning: /etc/postfix/main.cf, line 65: overriding earlier entry: virtual_alias_maps=hash:/etc/postfix/virtual_alias/example.edu, hash:/etc/postfix/virtual_alias/example.org > > in my postfix file I have the following code: > > virtual_alias_maps = hash:/etc/postfix/virtual_alias/example.edu, > hash:/etc/postfix/virtual_alias/example.org, > hash:/var/lib/mailman3/data/postfix_vmap > > Should I remove hash:/etc/postfix/virtual_alias/example.edu, and hash:/etc/postfix/virtual_alias/example.org, ? In that case how I create alias not related to mailman? Without seeing the contents of those files, I can't say, but something in /var/lib/mailman3/data/postfix_vmap is conflicting with and overriding something in the other two files. Since the only things in /var/lib/mailman3/data/postfix_vmap are specific list addresses, they are probably what you want, and you could just ignore the warning, but you probably do want to examine and remove conflicts from the other two files. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Trying to understand the mailman.cfg from the virtualenv installation guide

by Odhiambo Washington

On Sun, Sep 8, 2024 at 11:26 AM unite42--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hello, > > I'm trying to install Mailman3 following the Virtualenv Installation > guide. I would like to understand why the configurations in the displayed > mailman.cfg are recommended. > > Especially the following two: > > [archiver.prototype] > enable: yes > > "The prototype archiver stores messages individually in > var/archives/prototype/LIST_NAME/." > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Do I need this, when using hyperkitty? Is this a fail-safe recommendation? > > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > > What is the background of these recommendations? > Please take a look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 5 months

[MM3-users] Re: Change 'from' server for outgoing messages

by Benjamin Goldberg

Well, this is interesting. Based on your reply, I stopped trying to figure out any difference between the admin messages and the posts. Instead I removed the settings which routed the outgoing messages through MailerSend. That worked. I received both a welcome message and a post from a list I created just for this test. Then I restored the settings, and it still worked! Without the external routing, my messages ended up in spam but at least they were delivered. Routed through MailerSend they get delivered to my inbox. I'll do some more testing because this all seems strange and I'm not convinced it's fixed. BTW the errors that I had been getting were, at first: response exception: (450, b'The from.email must be verified. The from.email must be verified.') but later changed to: response exception: (450, b'Sorry, please try again. 429 Too many requests.') I had assumed both errors were being generated by MailerSend but now I'm not sure I'm not sure it's fixed but if not, I'm certainly closer. Thank you

2 years, 11 months

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

by Jeremy Stanley

On 2024-07-07 13:43:49 -0400 (-0400), Robert Heller wrote: [...] > what is the point of the Debian 12 packages? Are they just not > meant to be used? Really? Do you mean that I should use a separate > package management system for Mailman3? That really sucks. [...] I'm sure packages from any distribution are fine, but if you're using distro packaged software then your distribution is your first line of support because upstream developers don't know what changes have been made downstream by every distribution's package maintainers. If you need assistance with Debian's packaged software, the debian-user mailing list[*] is generally your first line of support. If you believe you've found a bug in the software, file it in the Debian BTS[**] and the package maintainer can determine if it's specific to Debian's version of the software or not. If the problem is not Debian-specific, the package maintainer should then forward the bug upstream for further action. [*] https://lists.debian.org/debian-user/ [**] https://www.debian.org/Bugs/Reporting -- Jeremy Stanley

1 year, 7 months

[MM3-users] Re: Moderator e-mails only going out once a day

by Stephen J. Turnbull

Joe, It may help to have more information about what your system is like. Specifically: 1. Did you install Mailman from our source distribution, from PyPI, or from some other source? 2. Did you install Mailman in its own virtual environment? 3. When you run 'mailman info', does the output make sense? Especially, is the configuration file (mailman.cfg) in the directory (usually /etc/mailman3) you expect? 4. How do you control the Mailman processes? Using systemd's systemctl utility, SysV init scripts, or the 'mailman' and 'mailman-web' utilities? If you are not using the systemd or init utilities, what is the current directory when you start or restart Mailman? 5. Is the virgin runner running? (ps aux | grep virgin) Are there messages stuck in queue/virgin or elsewhere in queue/*? Especially queue/shunt and queue/bad. As long as I'm asking, may as well check these as well: 6. What versions of Mailman applications (mailman, Postorius, HyperKitty, mailmanclient, django-mailman3) are installed? 7. What version of Python are you running Mailman under? 8. What is the operating system?

11 months, 1 week

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

by Thomas Stein

On 04.01.19 15:55, Abhijith PA via Mailman-users wrote: > > > On Friday 04 January 2019 08:19 PM, Thomas Stein wrote: >> On 04.01.19 09:40, Thomas Stein wrote: >>> >>> Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe >>> i missed something else but after adjusting the permissions of that template everything worked as expected. >> >> While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should >> I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation >> what variables i can put in those templates? > > If you are using 3.2.0, you can do that from webapp itself. [ I haven't > tried though] Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik. https://launchpad.net/ubuntu/+source/mailman3 thanks and cheers t. > > --a > _______________________________________________ > 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] Re: xapian db corruption - xapian.DatabaseCorruptError: Couldn't read enough (EOF) ??

by Odhiambo Washington

On Mon, Jul 29, 2024 at 9:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/29/24 03:27, Odhiambo Washington via Mailman-users wrote: > > Today, my hourly cron job has generated an error and continues to do so > > every hour: > > > > ``` > > Subject: Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs > hourly > > ``` > > > > Not sure what caused this. Perhaps a reboot when the cronjob hadn't > > completed? And a possible manual remedy would be to wipe the indexed db > and > > let the cron run again? > > > Or maybe just run `/opt/mailman/mm/bin/django-admin rebuild_index Nice to know. I just deleted the contents of the xapian_index folder and then ran the cronjob. Solved. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 7 months

[MM3-users] Re: User cannot reset password

by Greg Newby

On Sun, Aug 11, 2024 at 11:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/11/24 10:56, Greg Newby wrote: > > I imported MM2.1 lists to Mailman3 (using import21 - details are in my > > previous messages to mailman-users), and have had a couple of reports of > > people for whom the password reset function via "Forgot password" on the > > list login screen doesn't work as expected. > > > Django (web) accounts (Postorius and HyperKitty) are separate from > Mailman core. Users inported from MM 2.1 do not have web accounts. They > have to sign up, not request a password reset. > 1. Will the new (Django) and imported (Postorius) usernames automatically be matched to the same email address? The goal is for someone to use the web-based front end to manage their migrated subscriptions. 2. How can I customize the email that went to users who selected "Forgot password?" ( You are receiving this email because you, or someone else, tried to access an account with email I didn't find that string in the source code. Thanks as always! ~ Greg

1 year, 6 months

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

by Mihai Moldovan

* On 4/17/25 18:47, German Rodriguez wrote: > I wondered about the difference of the two archivers (prototype/hyperkitty) and whether both should be enabled. > > Mark explains here that the prototype archiver is for storing the raw email message, whereas HyperKitty only stores select information. > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Interesting. I probably want the prototype archiver enabled, even if that means duplicating most of the archives and doubling the amount of data stored. I was not aware that Hyperkitty doesn't store all information. I'd like to have all information archived (in order to be able to restore it again, if need be), even if they aren't published. Now... is there a way to import mbox files into the prototype archiver? Looking around, I haven't found anything mentioning this. Since it's just using the Maildir format, I guess I could find a tool that unpacks messages from an mbox to a Maildir destination and get that done, but if mailman has some command to do that, it would be even better. Mihai

10 months, 2 weeks

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

by Odhiambo Washington

On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 3:15 AM, Odhiambo Washington wrote: > > > There is still some confusion on my part about the directives in the file > > so allow me to seek some clarifications. > > > > The following are the contents of a file I have created and placed in my > > Apache Includes/ directory. > > I was hoping that with it, I can now access http://lists.my.server/mm3 > and > > get the UI. > > > > <CUT> > > > > # Global section > > WSGIDaemonProcess mailman-web display-name=mailman-web > > maximum-requests=1000 umask=0002 user=mailman3 \ > > group=mailman3 > > > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > > \ > > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > > WSGIRestrictSignal Off > > > > <VirtualHost *:80> > > ServerName lists.my.server > > ServerAdmin odhiambo(a)gmail.com > > > > # (I'm not sure that WSGIRestrictSignal Off is required, but it was in > the > > # provided example so I kept it. I also made changes to WSGIDaemonProcess > > # based on my own mod_wsgi experience elsewhere.) > > > > ErrorLog /var/log/myserver-error.log > > LogLevel debug > > > > # This goes in the VirtualHost block for the domain. > > > > # Mailman 3 stuff > > Alias /static "/var/spool/mailman-web/static" *<----- Where is this > > directory supposed to be and what/who creates it and with what > permissions?* > > > It is created/updated by the mailman-post-update script based on CONFDIR > and STATIC_DIR. > The fact that I have run the mailman-post-update script and these directories aren't created means there is a problem in my setup, yes? > > <Directory "/var/spool/mailman-web/static"> > > With the settings in the sample, the above should be > > <Directory "/opt/mailman/mm/static"> > > and the alias > > Alias /static "/opt/mailman/mm/static" > > Clearly > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > doesn't match some other files. I'll review abd update that. > Okay. I am anxiously waiting. > > > Require all granted > > </Directory> > > WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > > <Directory "/opt/mailman/mm/"> > > <Files wsgi.py> > > Order deny,allow > > Allow from all > > Require all granted > > </Files> > > WSGIProcessGroup mailman-web > > </Directory> > > </VirtualHost> > > > > </CUT-HERE> > > > > I end up with an "Internal server error" and from the error log I see: > > > ... > > [Sun Jul 26 12:04:44.093265 2020] [wsgi:error] [pid 6444] [remote > > 197.232.81.246:53383] ModuleNotFoundError: No module named 'settings' > > > Django is trying to import your settings.py file and can't find it. Is > it at /opt/mailman/mm/settings.py and also local settings at > /opt/mailman/mm/settings_local.py? Yes, I have these files: (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 /opt/mailman/mm/settings.py -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 /opt/mailman/mm/settings_local.py PS: I made my /opt/mailman to be owned by mailman3:wheel because of a confusion with the instructions at some point in the reading of some documentation previously (in my previous attempt last year!) and had noted that in my NOTES. I'll change this once things get clear for me. Also, the fact that one of the init scripts <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> in your "reflection" page was calling sudo :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 7 months

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

by Mark Sapiro

On 1/6/22 12:52 PM, Stephen Daniel wrote: > > Sendgrid requires that the "From:" address on any email reference an > authenticated domain. > > In the old mailman2 implementation, emails sent by mailman are listed as > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > Reply-to: <human name> sender(a)senderdomain.com (the original email's sender) > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > validated domain. > > However, in my mailman3 implementation, the From: header lists the original > email's sender. Sendgrid rejects this because the original email's > sender's address is not one of the validated domains. > > How do I configure mailman3 to generate headers in the same style as the > old mailman2 implementation? In the list's Settings -> DMARC mitigations, set DMARC mitigation action to Rrplace From: with list address and DMARC Mitigate unconditionally to Yes. -- 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: Lost posting in archives

by Mark Sapiro

On 1/21/22 3:06 PM, Axel Rau wrote: > I created a list, did migration from 2.1 and run update_index_one_list. > Then I posted a test mail to the list and it got distributed and was seen in the archive. > Now 2 days later it does no longer show up in the archive. > > What is going on here? > May this have to do with > HYPERKITTY_RENDER_INLINE_IMAGE > which I have turned on meanwhile. It may. Is there anything in Django's log about this? If you have the original message from the list, can you go to the URL in the Archived-At: header? is the message in the hyperkitty_email table in the database? E.g., SELECT * FROM hyperkitty_email WHERE message_id_hash ='xxx'; (xxx is the value of the Message-ID-Hash: header from the message) If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list(a)example.com/new directory and that message will have the Archived-At: and Message-ID-Hash: headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: MM2 -> MM3 Migration: listinfo page

by Jeremy Stanley

On 2023-03-09 13:49:09 +0300 (+0300), Odhiambo Washington wrote: [...] > I'd rather not touch the MM2.1 domain because references have been made to > it in publications. > What I am struggling with is the listinfo.html file: > ``` > https://lists.kictanet.or.ke/mailman/listinfo/kictanet > ``` > I am struggling to add reference to the MM3 subscription link user the > " Subscribe to KICTANet by filling out the following form:" > The HTML code to insert there beats me :) Redirecting the listinfo pages to your Postorius interface should be sufficient to keep those URLs which are referred to in publications working. We do basically the same thing Mark mentioned, for the reasons you say you don't want to: https://opendev.org/opendev/system-config/src/commit/ae7884a/playbooks/role… If someone follows a link to the old MM2 https://lists.opendev.org/cgi-bin/mailman/listinfo/service-discuss URL they get redirected to https://lists.opendev.org/mailman3/lists/service-discuss.lists.opendev.org/ so that there's no risk they'll try to use the old MM2 subscription form. -- Jeremy Stanley

2 years, 11 months

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

by Mark Sapiro

On 11/18/24 04:12, mark(a)suburbia.org.au wrote: > > For the list I am talking about: > - Default action to take when a member posts to the list is set to "Hold for moderation" > - Default action to take when a non-member posts to the list is set to "Hold for moderation" > - When I am viewing all users, the migrated ones are set to Moderation Action: "Hold for moderation". The mass-added ones post-migration are set to Moderation Action: "None" > - When a mass-added post-migration user sent an email to the list it passed through without being held. This should not happen. In the message as delivered to the list what do you see in the X-Mailman-Rule-Misses: header and the X-Mailman-Rule-Hits: header if any? > Happy to check any logs if there might be something to hunt for. What if anything is in the lists Accept these non-members setting? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Postfix + MariaDB + Mailman 3 Core

by Peter Knowles

Steve, I'm referring to Postfix specific records, not Mailman records which are not the topic of conversation here. Presently, Mailman creates two files under "/opt/mailman/mm/var/data"... "postfix_lmtp" which is a "transport_maps" table "postfix_domains" which is a "relay_domains" table The instructions in the docs says to set these up as "hash" table entries in Postfix so that when they're updated by MM Postfix references get updated accordingly. What I'm doing is, converting the "hash tables" to MariaDB tables stored in a Postfix specific database. Two primary objectives are intended with this updated architecture design... 1. allow management of Postfix tables through my web UI 2. Offer future scalability whereby the database for MM and Postfix amongst other things may get placed on a separate node, and/or setup in a Master-Master mirror cluster. *** On a segway, but related to the overall goal... I'm adding OpenDKIM management into my admin UI, which also is tied to a MariaDB database for key signing tasks and management. For the same reasons above, this is why I'm moving from files to databases. ***

1 year

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

by Alexander Inzinger-Zrock

Am 28.04.25 um 16:27 schrieb Stephen J. Turnbull: > Alexander Inzinger-Zrock via Mailman-users writes: > > > + also checked that command ''postmap'' (under /usr/sbin) is available > > for user 'mailman' (usr/sbin was not in path; it is now). > > This should not matter since the full path is in postfix.cfg, so > Mailman should find it and run it unless there is some permissions > problem or the executable itself is broken, regardless of PATH. > > You've probably run all these pretty recently, but if you've made any > changes since then: > > What is the output of the "mailman lists" command? (expect the test > list with domain) 2 matching mailing lists found: testliste01@MY_DOMAIN testliste02(a)my-example.com + MY_DOMAIN - replaced my domain by MY_DOMAIN + second was a test domain, created via postorius to check if i mesed up with the first one - no differences > What is the output of the "mailman aliases" command? (expect none) Indeed, none. > After "mailman aliases" do you get aliases in the postfix_lmtp file? > No.

10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Installing mailman-suite for web ui. I did this: (env) [mailman@localhost ~]$ git clone https://gitlab.com/mailman/mailman-suite/ Cloning into 'mailman-suite'... error: RPC failed; result=22, HTTP code = 404 fatal: The remote end hung up unexpectedly but it returned an error, what should I do?? Thanks El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 10:29 AM, Rafael Mora wrote: > > Can we modify the docs? > > > > El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > >> > >> However, that said, the doc is wrong. The lines should be added to > >> main.cf, not master.cf. See > >> <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. > > > That's what the above issue and associated MR are for. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

[MM3-users] Show number of subscribers

by Stephen J. Turnbull

andrew.bernard(a)gmail.com writes: > Would there be a way to show the number of subscribers to a list in > the web UI? Currently the answer evidently is no. I'm not sure why Mark is pessimistic (except that I don't see hordes of list owners breaking down our doors for this feature), because I don't see why it couldn't be added. HyperKitty already imports mailmanclient, so it can query the list. If you want to pursue this, you should file an RFE in the tracker, but I won't promise it will be very high priority, and it does mean closer integration with core than we've had so far, so there might be some unease from the developers. (I don't see why there would be an issue, except for the slight increase in maintenance burden.) On the other hand, we do have a bunch of students and others interested who were attracted by Summer of Code and Season of Docs, and one of them might find this an interesting task. It's not an introductory project, but it looks straightforward to me, with well-defined requirements. Steve

6 years, 8 months

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Yes, and I made all the tests as discribed here: https://workaround.org/ispmail/buster/relaying-through-postfix/ including the swaks test mentioned before output of sudo netstat -lntup | grep ":25" tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20660/master tcp6 0 0 :::25 :::* LISTEN 20660/master output of sudo lsof -i :25 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 20660 root 13u IPv4 1474228 0t0 TCP *:smtp (LISTEN) master 20660 root 14u IPv6 1474229 0t0 TCP *:smtp (LISTEN) Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Dienstag, 7. April 2020 21:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Uncaught runner exception On 4/7/20 3:22 AM, Wolfgang Bock via Mailman-users wrote: > Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost > on port 25 > > I have no idea what to do for solving my problems. Can you successfully telnet localhost 25 from a shell on the server? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 10 months

[MM3-users] Message of the day

by Stephen J. Turnbull

Henrik Rasmussen writes: > Are there any way of displaying a "Mesage of the day" to the users > of Postorius and Hyperkitty? Not built in to those applications. However, you could easily alter a template, possibly the base template, to include a file would contain your message with appropriate formatting. Django has a conditional include feature so you wouldn't get an error and no glitch in the display if the file weren't present. Extensions to the idea would include putting the formatting in CSS (sort of pointless by itself) and adding Django code to check whether the user's previous login was before the MOTD was changed (and then the CSS could be used to hide the message in case they had logged in recently, and presumably already saw it). It wouldn't be hard to add a MOTD table to Django, and then you could display all messages more recent than previous login. I'm not interested in doing this myself but would be willing to help a volunteer write the code and get it committed (subject to Steering Committee consensus, but I don't see why not). Steve

4 years, 4 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/17/19 6:39 PM, paul(a)arenson.org wrote: > > A) Thoughts before summarizing tests. > 1) I had originally thought of making archives only for subscribers to give them the benefit of posting from the archives directly and being able to find stuff more like a forum (email is always hard to follow). Anyone logged in to an account can post from Hyperkitty. Their post is treated the same as if they posted by email. > 2) But in retrospect it seems people can get an idea what the list is about from free access. So that is now what I have. OK > 3) On the other hand, it is a bit confusing that a non member can post from the archives without realizing that they need to register, with my settings I can moderate and decide if I want to add him or her to the list based on whether that is spam or not. So ok. A non-member is a non-member. A post from a non-member is handled according to "Default action to take when a non-member posts to the list" unless that non-member has a Moderation action other than List Default. > B) THE TESTS > I was testing too many variables so, to simplify things, I made my settings as follows > > 1) Subscription—> Confirm > > 2) Message Acceptance—> Default processing (so only members may post) > > 3) Testing Procesure > I added people three ways—> To do that I created 3 unique addresses to see if they can send and receive by email. > > > 3a) subscribe without creating an account—from here (bottom) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > 3b) Subscription / Unsubscription from same page, navigate to Login and again navigate to signup > Comment 1: Confusing because even after creating an account, they are not subscribed to the list. Maybe it makes sense if a person has many lists, but I only have this one. It does not say clearly that one has to subscribe after creating an account. I understand it's not totally explicit, but it says "To subscribe or unsubscribe from this list, please log in first. If you have not previously logged in, you may need to set up an account with the appropriate email address." To me the implication is once you have created an account, you have to come back, log in and subscribe. What do you want it to say? > Comment 2: The other thing is that it does not show my domain but that of mailman3.emwd.com <http://mailman3.emwd.com/>. Talk to Brian (emwd) > 3c) Mass Subscribe by me. Which is what I intend for my 600 users from another list company. > Comment This worked fine. > > > C) Summary > 1) I have been thinking of having an account as a good way to get users used to using the archives as a way to confirm current and past topics (as opposed to keeping track by email. But it seems I need to tell them to BOTH subscribe AND create an account. Am I thinking about it the wrong way? That's correct. They need an account and they need to subscribe that account to the list. > 2) When a person wants to unsubscribe, they go to discuss-request(a)list.tokyoprogressive.org <mailto:discuss-request@list.tokyoprogressive.org> with subject bline help. > > a) Isn’t there a better way to unsubscribe by email? email to discuss-leave(a)list.tokyoprogressive.org (or discuss-unsubscribe(a)list.tokyoprogressive.org) Or you can login, go to https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… and click the big red unsubscribe button. > b) And how about a way to remove their account itself? Log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/ and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/delete -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: required cron entries?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210101 03:49]: > Andreas Barth writes: > > > as I found some mails in queue/shunt, I thought who should be running > > them. > > Mark covered this quite completely, but I do have one remark. In my > experience, most shunted emails are spam (that's *not* how we normally > handle spam, it's just that spam is far more likely to be sufficiently > malformed to cause an uncaught exception than legit mail). You can > just delete the corresponding .pck. Thanks to you both. In my case, this was however Uncaught runner exception: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (sqlite3.OperationalError) database is locked [SQL: 'UPDATE mailinglist SET last_post_at=?, post_id=? WHERE mailinglist.id = ?'] [parameters: ('2020-12-23 10:18:41.030593', 10, 11)] (Background on this error at: http://sqlalche.me/e/e3q8 The 'fix' for that was turning it off and on again (i.e. rebooting the VM), but now I have a few messages around. (Perhaps I should also migrate to a real database, but that's a different problem) Andi

5 years, 2 months

[MM3-users] Re: Login confusion

by Mark Sapiro

On 2/11/25 01:26, Stephen J. Turnbull wrote: > > That will work in the short run, but I'm not sure that's a long-term > solution. It's not clear to me that allauth won't do the same thing > again. Allauth since 0.62.0 and better since 0.63.0 no longer does this. See https://codeberg.org/allauth/django-allauth/src/branch/main/ChangeLog.rst#s… > > Could I have achieved the same deletion using the REST interface? > > I don't know. I would think not. That's correct. The issue is in the account_emailaddress database table which is an allauth table that Mailman core and hence the REST api know nothing about. Our latest recommendation is django-allauth>=65.4, but that requires changes, see https://gitlab.com/mailman/django-mailman3/-/merge_requests/316 and https://gitlab.com/mailman/mailman-web/-/merge_requests/58 although the changes only affect testing and a deprecation warning. Also, installing that django-allauth version may result in upgrading Django to a version which doesn't support django-haystack<3.3.0 and may also require manually upgrading django-haystack. -- 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] Website 404 error

by Stephen J. Turnbull

peter(a)pi4cc.nl writes: > I'm running Debian 12 with the latest version and installed > mailman3 via apt install-mailman3-full. Assuming you have done no configuration "by hand", this is almost certainly a Debian issue. You should report it to them. > When I first access the website domain.nl/mailman3, it's redirected > to domain.nl/mailman/postorius/lists/, resulting in a 404 error The initial redirect is done by your webserver, not by Mailman. I have no good idea why the result changes if you do it twice.[1] In Apache, this is likely in a file in /etc/apache2/sites-available/. In nginx, similarly /etc/nginx/sites-available/. The file's name is likely to be either something like "debian-default.conf" or "mailman3.conf" for either of those popular webservers. Footnotes: [1] The only thing I can think of is that in one case you accessed domain.nl/mailman3, and in the other domain.nl/mailman3/ (difference is the trailing "/"), and there are separate redirects for the two URLs for some reason. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 3 weeks

[MM3-users] Re: Mailman issues after re-boot

by Odhiambo Washington

On Sat, Sep 16, 2023 at 5:49 PM Paul Rubin <paulrubin37(a)gmail.com> wrote: > *<< I sent this to the mailman3 issues on gitlab and Mark replied but asked > me to move to this list, so I copied everything and inserted responses. I > hope this makes sense and someone can help me.>>* > > After a lengthy power failure I had to reboot a machine that has been > running for several years. the WEB-UI does not seem to be able to see > mailman-core. I have looked for log entries that might explain what the > issue is and I am stumped to even find logs that will update when I get an > error on the browser. Mailman is definitely running, postgres is running > and mailman web is running. if I go to the lists page I see lists, if I try > to access a specific list I get Server error: An error occurred while > processing your request. > > I looked in /var/logs/mailman /opt/mailman/web/mailmanweb > > All I can find is: > > django.urls.exceptions.NoReverseMatch: Reverse for > 'list_unsubscription_requests' not found. > 'list_unsubscription_requests' is not a valid view function or pattern > name.16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal > Server Error: /mailman3/lists/goodstein.goodstein.org/ File > "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", > line 8, in <module> from django.utils.translation import > ungettextImportError: cannot import name 'ungettext' from > 'django.utils.translation' > > (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/__init__.py) > > Also I have to run mailman from "mailman start" because the systemctl > returns this: > > ● mailman3.service - GNU Mailing List Manager Loaded: loaded > (/etc/systemd/system/mailman3.service; enabled; vendor preset: > disabled) Active: failed (Result: exit-code) since Tue 2023-09-12 > 10:06:31 EDT; 13s ago Process: 31159 > ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, > status=1/FAILURE) CPU: 806msSep 12 10:06:31 mail > mailman[31159]: Error in atexit._run_exitfuncs:Sep 12 10:06:31 mail > mailman[31159]: Traceback (most recent call last):Sep 12 10:06:31 mail > mailman[31159]: File "/usr/lib64/python3.8/logging/__init__.py", > line 2126, in shutdownSep 12 10:06:31 mail mailman[31159]: > h.flush()Sep 12 10:06:31 mail mailman[31159]: File > "/opt/mailman/venv/lib64/python3.8/site-packages/mailman/core/logging.py", > line 67, in flushSep 12 10:06:31 mail mailman[31159]: if > self._stream:Sep 12 10:06:31 mail mailman[31159]: AttributeError: > 'ReopenableFileHandler' object has no attribute '_stream'Sep 12 > 10:06:31 mail systemd[1]: mailman3.service: Control process exited, > code=exited, status=1/FAILURESep 12 10:06:31 mail systemd[1]: > mailman3.service: Failed with result 'exit-code'.Sep 12 10:06:31 mail > systemd[1]: Failed to start GNU Mailing List Manager. > > Please tell me where to start looking or adjusting. > > > Reply from Mark Sapiro,* Edited to include responses:* > > Mark Sapiro <https://gitlab.com/msapiro>@msapiro > <https://gitlab.com/msapiro>· 1 day ago > <https://gitlab.com/mailman/mailman-web/-/issues/23#note_1557601916> > Owner > Add reaction > More actions > > The mailman-users(a)mailman3.org list is probably a more appropriate place > for issues like this. > > django.urls.exceptions.NoReverseMatch: Reverse for > 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is > not a valid view function or pattern name. 16688 ERROR 2023-09-12 > 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/ > goodstein.goodstein.org/ > > /opt/mailman/venv/lib64/python3.8/site-packages/postorius/urls.py should > contain > > re_path( r'^unsubscription_requests$', > list_views.list_unsubscription_requests, > name='list_unsubscription_requests', ), > > Y > > *Yes this exists* > > and /opt/mailman/venv/lib64/python3.8/site-packages/postorius/views/list.py > should define list_unsubscription_requests. > > *Yes there is a method by this name defined* > > File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", > line 8, in from django.utils.translation import ungettext ImportError: > cannot import name 'ungettext' from 'django.utils.translation' > (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/ > *init*.py) > > See > > https://docs.djangoproject.com/en/4.2/internals/deprecation/#deprecation-re… > - > ungettext() is removed from django>=4.0 > > Sep 12 10:06:31 mail mailman[31159]: AttributeError: > 'ReopenableFileHandler' object has no attribute '_stream' > > I don't understand this one offhand, but what is the content of > /etc/systemd/system/mailman3.service, in particular the settings for User, > Group and ExecStart? > > *The service looks right:* > > 1 [Unit] > 2 Description=GNU Mailing List Manager > 3 After=syslog.target network.target postgresql.service > 4 > 5 [Service] > 6 Type=forking > 7 PIDFile=/opt/mailman/mm/var/master.pid > 8 User=mailman > 9 Group=mailman > 10 ExecStart=/opt/mailman/venv/bin/mailman start > 11 ExecReload=/opt/mailman/venv/bin/mailman restart > 12 ExecStop=/opt/mailman/venv/bin/mailman stop > 13 > 14 [Install] > 15 WantedBy=multi-user.target > > *It seems I may have two versions of the mailman script:* > > mail:/opt/mailman # which mailman > /usr/bin/mailman > mail:/opt/mailman # ls -al /usr/bin/mailman > -rwxr-xr-x 1 root root 382 May 10 2021 /usr/bin/mailman > mail:/opt/mailman # ls -al /opt/mailman/venv/bin/mailman > -rwxr-xr-x 1 mailman mailman 231 Sep 12 10:02 /opt/mailman/venv/bin/mailman > > Somehow, your installation is corrupted. I don't know how > > *I need to know what to remove, how to correctly update, etc., That said > the two scripts appear to be very similar:* > > mail:/opt/mailman # head /usr/bin/mailman > > #!/usr/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' > __requires__ = 'mailman==3.3.4' > import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( > > > mail:/opt/mailman # head /opt/mailman/venv/bin/mailman > #!/opt/mailman/venv/bin/python3 > # -*- coding: utf-8 -*- > import re > import sys > from mailman.bin.mailman import main > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) > sys.exit(main()) > mail:/opt/mailman # > > *Given the two years since the last reboot I also tried following * > https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was > running the latest* > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web > Why don't you try and do a fresh virtualenv install and move your configs into it? 1. cd /opt 2. mv mailman _mailman.BAK 3. Create a backup of the database. Then follow this: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, but do not create the database as it already exists. You also do not need to run any database migrations, so you can actually skip those You just need to ensure that `mailman info` says that its configuration files are in /etc/mailman3/ Create the necessary directories as per the above installation instructions. -- 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: hyperkitty.lib.utils Failed to update the fulltext index

by Abhilash Raj

On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: > April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: > > > > Which version of Hyperkitty are you using? > > > > Did you upgrade the version of Hyperkitty when you migrated to the > > new host? > > I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple > releases), so it's hyperkitty 1.1.4. > > I didn't upgrade anything with the move. I am not sure where does Debian packaged version store it's fulltext index, but I am assuming the move somehow makes Hyperkitty not be able to read the index. Can you try removing and re-building the entire index? I don't know again the right command for Django there, but the hyperkitty command you want to run is called `rebuild_index`. For source package, something like: $ python manage.py rebuild_index Do note that this will take a lot of time if you have a big archive. > > Thanks, > Ben > -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: How to separate bans for sending emails to lists and subscribing to them

by Mark Sapiro

On 5/29/19 9:29 AM, Nathan Dixon wrote: > Hi, > Our requirements for using Mailman are that we can have non-members send an > email to a list from any domain name, but only people who's email addresses > match a list of specific domains should be able to actually subscribe to > those lists. > > I can't seem to find any way of doing this. Any ideas? > > I have tried using the bans (global and on each list) but these appear to > stop all subscriptions and emails being sent to or from a list if the > address matches a ban. Right. The default posting rules chain includes 'banned-address' which discards posts from banned addresses. You can work around this by creating a new chain based on mailman/chains/builtin.py but without the 'banned-address' rule and setting the list's posting_chain to use it. -- 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: Apache+mod_wsgi issue

by Mark Sapiro

On 12/26/22 07:08, Odhiambo Washington wrote: > > So it seems your WSGIDaemonProcess is defined somewhere outside the VHOST, > right? Or it wasn't necessary? > And what does your urls.py look like? Eggert's configuration is for uWSGI. This is completely different from Apache mod_wsgi. Background: Python PEP 333 defines the Python Web Server Gateway Interface (WSGI) which is a protocol for communication between web servers and applications. Django is one such WSGI application. Basic web servers typically do not support WSGI directly but need some kind of intermediary. Apache mod_wsgi is an Apache module that extends Apache to communicate with WSGI applications. Both uWSGI and gunicorn are separate applications that can receive http requests via proxy from a web server and communicate them to a WSGI application and receive responses from the application and return them to the web server. Thus Apache mod_wsgi, uWSGI ang gunicorn are three separate ways of providing the connection between the web server and Django (or other WSGI applications), each with their own separate configuration requirements. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

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

by Mark Sapiro

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

by Stephen J. Turnbull

John Covici writes: > That post does not answer my question, it applies only to mailman2 Look, John, I understand that you're frustrated because Gentoo doesn't maintain their Mailman 3 package to the point where it's turnkey on your system, but that's not something you can blame on us. What you can do is pay us the respect of assuming we know what we're talking about, and genuinely want you to get your system set up to *your* preferences even though we're not familiar with the OS distro you chose. And you can read our posts to the end, as well as the documentation that various people have put hours into writing. The point of citing the post is that, yes, John, that post already answered your question. No, it did not deal only with Mailman 2. Here's the answer to this question for the third time: > > > For sendmail, see > > > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> Please read it, and if you have any questions after that, we'll try to answer them. Regards,

4 years, 11 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by Mark Sapiro

On 7/8/22 6:34 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > Interesting -- that does produce two directories with names starting > > with a tilde: > > > > /opt/mailman/venv/lib/python3.9/site-packages/~jango: > > /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info: > > I would guess that those are the previous versions before the upgrade, > moved out of the way in case a revert-to-previous was needed. Again, > guessing, they should have been removed by the upgrade process once > the new package was fully installed. Was there an interrupted or > partially successful upgrade in the past? When pip is doing an upgrade of the xyz package, it renames the existing package as ~yz and then ultimately deletes the old ~yz package after successfully installing the new xyz. In this case, the upgrade was aborted because of the Django<3.1 constraint in mailman-web and apparently pip then installed Django<3.1 and left the ~jango* directories behind. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

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

by Matt Blissett

Stephen J. Turnbull wrote: > Matt Blissett via Mailman-users writes: > > I get exceptions logged when certain pages in the email archives > ... > This: > > File "/usr/lib/python3.12/site-packages/mistune/markdown.py", line 120, in __call__ > > return self.parse(s)[0] > > suggests it's trying to parse Markdown out of a non-markdown file. > This: > > File "/usr/lib/python3.12/site-packages/mistune/core.py", line 214, in parse_method > > assert lastgroup > > ^^^^^^^^^ > > Exception Type: AssertionError at /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies > > doesn't make sense to me, as core.py has only 207 lines in my > installation, and there is no assert in the parse_method function. > Check what version you have. Thanks — it's version 3.1.3, so it's these lines: https://github.com/lepture/mistune/blob/v3.1.3/src/mistune/core.py#L212-L216 > If you do not need the Markdown rendering, you can disable it (per > list). "Archive Rendering Mode" for this list is already set to "Plain text". -- Matt

10 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< mailman-users(a)mailman3.org>) escribió: > I think you're confused. > > You already have mail.labbrands.com set up as the MX record for > labbrands.com. And it has an A record with the same address as your > webserver. > I'm working with the hostgator mailserver, we are not running a local mailserver. As suggested I added an A record like this: [image: image.png] Is it correct? is it redirecting to my Ip so I can redirect it to my postfix/mm3 server? > > So if you're getting e-mail on that domain, there's another e-mail > server running on that IP address. You can't have 2 servers on port > 25. In that case, as has been noted before, you'll need to setup a > relay in that server, not a firewall redirect. Depending on your MTA, > you would need to relay to your internal server. And make sure your > firewall setup allows your MTA to do this. > > We can see it's EXIM: > > telnet mail.labbrands.com 25 > Trying 192.185.51.89... > Connected to mail.labbrands.com (192.185.51.89). > Escape character is '^]'. > help > 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48 > -0500 > 220-We do not authorize the use of this system to transport unsolicited, > 220 and/or bulk e-mail. > 214-Commands supported: > 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > quit > 221 gator4137.hostgator.com closing connection > Connection closed by foreign host. > > Or, consolidate all your e-mail to one server - which is a lot easier to > manage unless you have a really big operation. Postfix is probably the > right choice, but requires more setup. > > Although Mailman3 configuration is not well documented (as you've > discovered), you may want to get help from someone with more general > network and mail experience. You're now into territory that is, as > Simon indicated, not Mailman-specific. > > On 03-Aug-17 16:28, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > >> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > >> escribió: > >>>> You need to forward port 25 for SMTP mail delivery and if you want the > >>>> web UI (Postorius and HyperKitty) accessible from the outside, port 80 > >>>> for http and/or port 443 for https > >>>> < > >>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>> . > >>> I mean for incoming mail redirected from my hostgator hosting, because > >> when > >>> I suscribe an email address MM3 sends a confirmation email, so I have > to > >>> reply to be suscribed to the list. > >> > >> As I said, for mail delivery you need to forward port 25 to the Mailman > >> server. > >> > > Ok so I'll redirect in my zentyal firewall the port 25 to my local > centos7 > > with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > > > > >> > >> -- > >> 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/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > 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, 7 months

[MM3-users] Re: Ann: Postorius 1.3.6 is now out

by Odhiambo Washington

On Wed, Sep 29, 2021 at 6:28 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hey Everyone, > > I just tagged and released Postorius 1.3.6. This release includes both bug > fixes and > new features. > > Some of the notable features include > - Ability to list and handle un-subscription requests to the list > - Option to choose delivery mode and delivery_status directly when > subscribing to a list > - Addition of a user management interface, which allows updating a users > password, > manually verifying their email addresses, update user’s Display Name > etc. > - Expose a number of Bounce processing related options in List’s settings > > A full list of changes is available here > > > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 > > You can install this release using pip > > $ pip install postorius django-mailman3 mailmanclient —upgrade > root@svr:/usr/local/mailman # pip install postorius django-mailman3 mailmanclient —upgrade ERROR: Invalid requirement: '—upgrade' Why do you think I got this? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 5 months

[MM3-users] Re: Where to configure 'hostname' used in 'From:'-header?

by Mark Sapiro

On 3/10/23 01:55, Dmitri Heerdegen wrote: > > I've recently installed MM3 with Exim4 on, say, subdomain.myhost.tld > and configured MM3 to use lists.someotherdomain.tld as web host and mail > host. > Thus, the mailman.cfg contains: > > [mta] > smtp_host: lists.someotherdomain.tld > > When I send a message to test(a)lists.someotherdomain.tld it gets > delivered, however the 'From:'-header becomes "test(a)subdomain.myhost.tld". The From: should be unchanged from the incoming post unless the list is anonymous or DMARC mitigations are applied. In the case of anonymous lists, the From should be the list's address and in the case of DMARC mitigations it should be something like User Name via listname <list-address>. In either case, the list address should be list-name@list-domain where list-domain is the list's email domain. If the address is being rewritten as test(a)subdomain.myhost.tld it is probably Exim doing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] confirm mail rejected

by Marc Sluiter

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working (with some configuration modifications, see other mail). The only thing which doesn’t work is conformation mails, they are rejected: In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) Thanks and greetings, Marc

8 years, 5 months

[MM3-users] Re: Welcome Message

by Abhilash Raj

On Tue, Apr 16, 2019, at 6:41 PM, brian(a)emwd.com wrote: > With all of this back and forth, I got it working. Using the mass > subscribe feature or the subscribe form on the info page WHILE LOGGED > IN AS ADMIN was causing the error. That shouldn't cause the error. Irrespective of how you subscribe, when you subscribe anyone to a list, Core will try to send the welcome message and try to reach Postorius for template. If the URL for template is wrong, or Postorius is down for whatever reason, the subscription will fail with the error that you saw before. > I logged out of Postorious and subscribed using the subscribe form on > the info page and the change to the welcome template showed up. So it > looks like being logged in as admin while trying to subscribe someone > was what was causing the problem. Is that a bug I discovered? I suspect stopping-restarting and re-creating the template (idk, if you really did that) might have something to do with it. I am not sure if this is a bug unless you can reliably reproduce this. -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: ARC

by Marvin Gülker

Am 13. August 2019 um 05:42 Uhr -0700 schrieb Mark Sapiro: > The question is not whether they support ARC, but whether they will > trust you. Well. That's nothing new, given that GMail and Microsoft liberally reject e-mail from small providers for no reason anyway (I have experienced it myself). If this situation doesn't change with ARC, I can live with this (by paying for an SMTP relay provider that proxies my e-mail). However, I thought the entire point in ARC was fixing automatic rejections caused by DMARC invalidation by mailing lists, which are vital for so many open-source projects (including Mailman iself). If ARC falls short of solving that problem, because the large providers do not automatically trust ARC, then supporting ARC on my mailing list server is kind of void. Why should almighty Microsoft trust my small personal mailing list server? ARC can only achieve its goal with black-listing untrusted relays rather than white-listing known good ones, because it is simply unfeasable to manually maintain a list of all open-source project mailing lists in the entire world. I could set a new one up tomorrow, how should you know? -- Blog: https://mg.guelker.eu

6 years, 6 months

[MM3-users] Re: Hyperkitty stuck files

by Odhiambo Washington

On Wed, Jul 10, 2024 at 1:36 PM <zoltan(a)circle-interactive.co.uk> wrote: > Thank you Mark! > > I think I tracked down the related django error for that message. > mailmanweb.log says > > MySQLdb.OperationalError: (1366, "Incorrect string value: > '\\xF0\\x9F\\x98\\x8A. ...' for column > `mailmanweb`.`hyperkitty_email`.`content` at row 1") > > but collation is utf8mb4_general_ci on the table. > > Do I need to maybe specify it in settings file? > Does your Django settings for the DATABASE look like the below? DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'DBNAME', # Example, change as needed 'USER': 'USER', 'PASSWORD': 'XXXXXXXXX', 'HOST': '127.0.0.1', 'PORT': '', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, } } I think the OPTIONS bit was required to mitigate that error. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 7 months

[MM3-users] Re: Migrating Mailman 3 lists

by Mohsen Masoudfar

Hi Brian, It would be great if you share the information about "How to migrate mailman 2 lists to a new mailman 3 server". It is what I am currently having issues with, maybe I am missing some parts . Thanks Mohsen -----Original Message----- From: Brian Carpenter <brian_carpenter(a)emwd.com> Sent: Monday, April 27, 2020 11:52 AM To: Mailman users <mailman-users(a)mailman3.org> Subject: [MM3-users] Migrating Mailman 3 lists [EXTERNAL EMAIL] Hello Mailman users, 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. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fclientare… EMWD's Community Forums https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdiscourse.… _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 10 months

[MM3-users] Re: REST API authorization failed

by Mark Sapiro

On 1/8/22 10:40 AM, Axel Rau wrote: > Hi all, > > I’m going to do a mailman2->3 migration in a FreeBSD jail. > I installed mailman3 in an venv from pypi, along with nginx, uwsgi and exim. > The above error happens when I try to open the base url of my server with a browser > (is redirected to postorius/lists/) > (no errors on admin/ and hyperkitty urls) > > Same passwords and users in mailman.cfg: > > [webservice] > hostname: localhost > port: 8001 > use_https: no > admin_user: restadmin > admin_pass: ??? > > and in settings.py: > > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = ??? > > Its a long password, created as secret key by manage.py Is the password unquoted in mailman.cfg as admin_pass: ??? and quoted in settings.py as MAILMAN_REST_API_PASS = '???' Does the `mailman info` command report what you think for REST credentials? To you get an appropriate JSON response from wget -O- --user restadmin --password ??? http://localhost:8001/3.1/lists -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Cannot Install Web UI

by Mark Sapiro

On 11/2/25 07:30, dap1--- via Mailman-users wrote: > I may have found the problem but would like confirmation before I mess things up.. The proxy stuff added to apache.conf asks for the modules mod_headers.c and mod_proxy.c. They do not exist in /etc/apache2/mods-available. However, none of the modules in that directory are file type 'c'. In any case if those modules are not loaded would not that explain my problem? I'm not sure it is appropriate to add those modules with a2enmod. If they don't exist in mods-available, they needed to be added with apt or whatever the package manager is in your distro. If they are in mods-available but not mods-enabled, they can be enabled with a2enmod. The docs assume that if you see required modules in IfModule statements in the config you are adding, you would ensure those modules are enabled. Perhaps this assumption is unwarranted, but there is a line somewhere between an installation doc and a tutorial on system administration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Cannot Run Web Frontend

by dap1＠bellsouth.net

How do I tell if mailman-web is running? There is no such service. /etc/mailman3/gunicorn.py (recall I had to use py rather than conf to get it to work under Ubuntu): # /etc/mailman3/gunicorn.conf # # bind = ['127.0.0.1:8000'] proc_name = "mailman-web" # # If you are having response issues you can tune the number of workers. # # The suggested starting point is (2 x $num_cores) + 1 # # See https://docs.gunicorn.org/en/latest/design.html#how-many-workers workers = 3 chdir = "/opt/mailman/mm" pidfile = "/opt/mailman/mm/var/gunicorn.pid" accesslog = "/opt/mailman/mm/var/logs/access.log" errorlog = "/opt/mailman/mm/var/logs/error.log" loglevel = 'debug' I did notice one thing in the access.log that is wrong: 127.0.0.1 - - [24/Nov/2025:16:02:55 +0000] "GET /archives/api/mailman/urls?mlist=lllllllllll%40dddddd.net&msgid=705caa ab-afcc-4249-8d1d-cc48050d02d1%40bellsouth.net HTTP/1.1" 200 113 "-" "python-requests/2.32.5" The mlist name is wrong. It should be lllllllllll%40gmail.com. I don't know where that is coming from but I'm sure it is left over from before I changed the list name. When I include the port in the URL I get an unable to connect page. P.S. Merry Christmas

2 months, 1 week

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

by Stephen J. Turnbull

andrew.bernard(a)gmail.com writes: > My goodness - have just tested with a small Python program. This is > a bug in Python. Parsing a single message mbox with a body line > somewhere starting with 'From' breaks it into two fragmentary > messages. Wow. Almost certainly not a bug in Python. That's the mbox format. If you're into scatological software analysis, here's one of the best flamers in the business doing his thing on mbox: https://www.jwz.org/doc/content-length.html If you've been shocked by the date on that post, no, *nothing* has changed since then. Jamie explains why. You may be dealing with MTA/MDA software using Content-Length, in which case I'm pretty sure the email package has an option for dealing with it. In that case, you should report an RFE to us and we'll try to figure out how to recognize that file format, and automatically deal with it. If not, the software is too unusual for us to worry about, and we'll help you work around the problem. Regards,

6 years, 8 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/23/20 7:02 AM, Brian Carpenter wrote: > On 9/23/20 7:33 AM, r.woithe(a)callassoftware.com wrote: >> Thank u for the hint ! >> The only one is that Ubuntu uses uWSGI and not gunicorn. >> I set the para socket-timeout = XXX. >> I hope thats the right parameter. >> _________________________________________ > > I think Mailman 3 core still has its own gunicorn process that it runs. > Brian is correct. The REST API does not use the web server and uWSGI is not involved. Since Mailman core 3.3.0, the REST API is served by Gunicorn processes that have nothing to do with the web server. The time limit for these processes needs to be set as described at <https://wiki.list.org/x/17892072>. Prior to 3.3.0, the REST API used the standard library wsgiref module which doesn't have timeouts. Since you said you have Mailman core 3.2.2, this may not be a REST timeout at all. -- 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: mailman3-web language preference and translation settings

by Mark Sapiro

On 12/6/23 15:54, Nils wrote: > Thanks for your help, Mark. I've already tried that and it gave me this > message: > > # sudo -u www-data python3 /usr/bin/django-admin compilemessages > --pythonpath /usr/share/mailman3-web --settings settings > CommandError: This script should be run from the Django Git checkout or > your project or app tree, or with the settings module specified. > > I'm working on ubuntu and I don't have (venv)$ The other commands (migrate, collectstatic and compress) worked fine. Kind regards I don't know why this fails like that, particularly since the same thing works for migrate, collectstatic and compress. The only thing I can think of is you may need to cd to the directory containing django/ django_mailman3/ postorius/ and /hyperkitty before doing the above. This may be something like /usr/lib/python3.x/site-packages. If that doesn't work, since I think you are using the Debian/Ubuntu package, I suggest you try Debian for help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: footer template priority

by Sam Darwin

Thanks. That fixed it. Comments: 1. In the docs, the instructions say "POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'. As a reader, you are thinking, I'm running both hyperkitty and postorius. Hyperkitty is at /archives/ and postorius is at /mailman3/ . What about the path '/mailman3/ for postorius? The doc could mention the path even if it's to explain why it's not needed. (The reason perhaps it's not needed is root will redirect to '/mailman3/'.) 2. This all seems very self-referential. The setting goes into settings.py which is the website for postorius itself. It is accessing itself. Given that's the case do you really need to tell Django about it's own URL? Doesn't it know it's own URL already? Could Django just contact itself without being configured? 3. Logging... when it can't find the templates, does it log an error anywhere? 4. The server had been up for a year. After I rebooted, the problem vanished, even after removing the new setting. So either it's caching the setting in Redis, or else the problem is really gone. Very strange. Anyway, that was it. thank you.

8 months, 2 weeks

[MM3-users] Re: hyperkitty threads by month question

by Bryan Fields

On 7/26/24 11:19 PM, Mark Sapiro wrote: > On 7/26/24 18:53, Bryan Fields wrote: >> On 7/26/24 4:01 PM, Mark Sapiro wrote: >> >>> If this returns just the one message_id, I would then >>> >>> DELETE FROM hyperkitty_thread WHERE id = 35670; >>> DELETE FROM hyperkitty_email WHERE id = 150555; >> >> It's giving an error due to a fk constraint on another table. I'm not >> familiar with the db structure enough to be certain how to clean/fix it. > > Yes, you need to do these first. > > DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; > DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; > DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; > DELETE FROM hyperkitty_vote WHERE email_id = 150555; > > Not all those will exist, but then you should be able to > > DELETE FROM hyperkitty_thread WHERE id = 35670; > DELETE FROM hyperkitty_email WHERE id = 150555; Sill no go on it. mailmanweb=> DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_vote WHERE email_id = 150555; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_thread WHERE id = 35670; ERROR: update or delete on table "hyperkitty_thread" violates foreign key constraint "hyperkitty_email_thread_id_038c9aee_fk_hyperkitty_thread_id" on table "hyperkitty_email" DETAIL: Key (id)=(35670) is still referenced from table "hyperkitty_email". mailmanweb=> DELETE FROM hyperkitty_email WHERE id = 150555; ERROR: update or delete on table "hyperkitty_email" violates foreign key constraint "hyperkitty_thread_starting_email_id_fa7c55f5_fk_hyperkitt" on table "hyperkitty_thread" DETAIL: Key (id)=(150555) is still referenced from table "hyperkitty_thread". >> I'm actually thinking I need to fix the archive mbox, then delete them and >> re-import them once they are cleaned. > > > Actually, that would be safest. Fix the mbox, delete the entire archive > and re-run the import. I'll attempt to clean this up tomorrow an clean it up/re-import. Is there a quick/easy way to drop the entire archive from the db or must I delete the entire list? >>> Also, FYI, assuming those messages with very old Date: headers had >>> reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script >>> would fix them, except you have to get the script from >>> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… >>> or https://www.msapiro.net/scripts/cleanarch3 because the script in the >>> latest release has a bug. >> >> I tried the dry run option on your script and it gave a bunch of output >> for bad >> dates. This was absent on the one shipping with the source. What's >> interesting >> is that pipermail seems to have no issue with this, detecting the date >> correctly. > > If I recall correctly, pipermail checks date skew and 'fixes' the dates > in the archive, but they remain off in the mbox. I'll have to check that, but I've got at least some good leads now and tools to find suspected issues. It does seem like a bad design that importing a mailman2 mbox can cause the server to error 500. >> Is the archive tool in pipermail's import more robust in this manner? >> I'd argue >> it's common to have missing In-Reply-To: headers where the subject and time >> would need to be used to infer the likely thread. I'll agree this is a >> major >> violation of the relevant RFC's to be missing this, but many MUA's (M$) are >> famous for doing just this. > > > Yes, it's arguably a defect in HyperKitty to not implement Jamie > Zawinski's threading algorithm <https://www.jwz.org/doc/threading.html>, > but it doesn't. Well that kinda blows :-( I'm not going to take down the old archives, but I'd like at least one to be searchable, which is why we wanted to use mailman3/hyperkitty. Thank you, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 year, 7 months

[MM3-users] Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

On Thu, Mar 24, 2022 at 09:27:06PM -0700, Mark Sapiro wrote: > The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of > the table entry. See `sites` in the Django admin UI. > > So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` Ok thanks, this is good to know. How about mailing list creation using Mailman Client, like this? domains = client.domains domains = list(filter(lambda x: (domain_name == x.mail_host), domains)) # .. check if domains is a singleton list .. domain1 = domains[0] domain1.create_list(list_name, style_name=style_name) Do you know of any quirks/deficiencies related to this kind of code? This code is taken from mailman3-utils: https://github.com/sfindeisen/mailman3-utils , a set of scripts I stitched together to facilitate common Mailman3 operations on the command-line. Most importantly this can apply the (currently hardcoded) set of list settings uniformly across the different lists (and different domains). (I realize part of this overlaps with the mailman command, especially in the local setting.) Thanks Stanisław

3 years, 11 months

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

by Kimmo L

> > Mark may have more suggestions, but this is almost certainly the cause > of the problem. The default for this parameter is > anonymous_list_keep_headers: ^(?!x-) ^x-mailman- ^x-content-filtered-by: > ^x-topics: ^x-ack: ^x-beenthere: ^x-list-administrivia: ^x-spam- > which is a list of strings separated by spaces, and I believe the > leading space on the second line is significant (meaning a > continuation of the list on the first line). > There are a number of possibilities that cause this. > (1) Check whether anonymous_list_keep_headers is set in mailman.cfg. > If it is, it may be all you need to do is remove a spurious > newline after the keyword anonymous_list_keep_headers. Otherwise, > you can restore the default by copying the setting above. Thanks to this i found the cause of concern - my mailman.cfg had "empty anonymous_list_keep_headers:" option defined. I commented out and now test email went through by using anonymous option successfully. One small thing, but so much trouble. My bad that i didint notice it before. Big thanks again Steve and Mark!

3 years, 5 months

[MM3-users] User stories about topics, dynamic sublists, or sibling lists

by Stephen J. Turnbull

Mark Sapiro writes: > On 3/27/24 08:05, Markus Grandpre wrote: > > > > after I migrated a list from Mailman21 to Mailman3 I missed the > > Mailman21 setting "regular_include_lists" (or something similar) > > in Mailman3. How are sibling lists treated in Mailman3? > > The sibling list features do not exist in Mailman 3. Topics, dynamic lists, now sibling lists. All of these address a set of related problems, characterized by a large number of users who are divided into subgroups by interest, where the interests are pretty concrete and don't overlap much, each user may have several of those interests, and each subgroup considers the threads on other topics to be an interruption of their preferred workflow. I would be interested in hearing user stories about their sites' use cases for these features (and any similar features whether or not they were implemented in Mailman 2). Also horror stories, if any. (I can imagine that mixing rosters could leak personal information or result in annoying crosstalk.) Please keep it in this thread, or write me personally if you prefer. Steve

1 year, 11 months

[MM3-users] Re: Hyperkitty performance problem

by Mark Sapiro

On 12/31/24 06:07, monochromec via Mailman-users wrote: > Further RCA reveals the fact that the archiver runner tries to archive the same message over and over again - hence the overhead during pipeline processing. The total # of attempts reaches well into five digits for a single message. This is not directly related to the pipeline runner issues but they may have the same underlying cause. All the pipeline runner does is put the message in the archive queue. It's the archive runner that is doing all these retries. However, the pipeline runner in processing the rfc_2369.py handler is also communicating with hyperkitty to get the values for the List-Archive: and Archived-At: headers. You need to focus on the communication between mailman_hyperkitty and HyperKitty. If there are significant delays there, it could explain your pipeline runner issue. Btw, I see https://gitlab.com/mailman/mailman/-/issues/1189 is also from you. I wondered at the time why you were trying to increase the number of pipeline runners which is not something that would normally be required. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Linking to a forum thread from a (news) website.

by Mark Sapiro

On 9/25/19 2:29 AM, Paul Arenson wrote: > SOLUTION > I figured out that all replies are listed under Re:, so if the first comment does not have the Re:, then it gets cut off. ... > QUESTION > Am I correct that if I want to create a thread and link to it, but make sure the first note is included, I need to make the thread title: Re: Something? Re: has nothing to do with it. Replies are not threaded by subject. Replies are threaded by In-Reply-To: and References: headers in the reply. These headers are generated by the sending MUA (mail client) when replying to a message. If you send a 'new' message without those headers, it will be a new thread regardless of whether or not the Subject: matches with or without the Re:. Also, there are broken MUAs that don't properly generate In-Reply-To: and References: headers and replies from these MUAs will never be properly threaded. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Email verification

by Abhilash Raj

On Sun, Feb 9, 2020, at 8:05 AM, Allan Hansen wrote: > Some members cannot get past the email verification when they create > their accounts. > They insist that they have looked in their spam folders. Their email > addresses they entered are correct - the are able to log into their > accounts with the right email address. But they get the message saying > that a confirmation message was sent and if they don’s see it to > contact us. Is your Django configured to send out emails? https://docs.mailman3.org/en/latest/config-web.html#setting-up-email-requir… > > 1. Who is ‘us’? My members are asking... > 2. How do I help them? > > I tried subscribing them to a bogus list with pre-verified email, but > that did not work, so both they and I are stuck. > Tried finding help in archive, but did not see anything. > > Yours, > > Allan Hansen > hansen(a)rc.org > > > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years

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

by Stephan Krinetzki

Stephen J. Turnbull wrote: > Mark Sapiro writes: > > mailmancore/API ->database > > that seems to have an issue and only with this one > > DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > > query. However, like you, I have no idea as to what you could do further > > to debug this. > > I have an idea, but it seems so obvious that presumably it's already > been tried: log in to the database as mailman with pgsql and try > deleting something. If that works immediately, try with mailmanclient > and the mailman command line utility. > Steve Well, we didn't try this. Since we don't know what the query for deleting a held message in the database needs to look like, we left that out for now. If someone can help me there, it would be great. Over the mailman shell it hangs as long as on the web ui (using mailman shell -l list@host and iterating over the held messages). So it is the communication Mailman API <-> Database.

4 years, 1 month

[MM3-users] Re: Trouble Installing Mailman3

by Mark Sapiro

On 6/3/25 08:22, Henry Hartley via Mailman-users wrote: > > (venv) mailman@wz-prd-tpmd-1:~$ pip -v --trusted-host pypi.org install wheel mailman psycopg2-binary > Using pip 24.0 from /opt/mailman/venv/lib/python3.12/site-packages/pip (python 3.12) > ERROR: Could not find a version that satisfies the requirement wheel (from versions: none) > ERROR: No matching distribution found for wheel > > The same error shows up if I try to install just mailman or psycopg2-binary, except the word "wheel" is replace with whichever package I've requested. I don't understand why this is occurring. All those packages exist in pypi.org https://pypi.org/project/wheel/ https://pypi.org/project/mailman/ https://pypi.org/project/psycopg2-binary/ Also, pypi.org has a valid ssl certificate signed by GlobalSign nv-sa If I create and activate a new virtualenv named zzz, and do ``` (zzz) mark@msapiro:~$ pip -v install wheel mailman psycopg2-binary ``` I get a successful installation. I am guessing that there is something in your local network that's redirecting connects to pypi.org to somewhere else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/9/25 5:02 AM, Flo via Mailman-users wrote: > Hi, > > I added a new site in Django: lists.example.com > > Usually I click on 'view site' and I can add a Domain in Postorios. In > this case I get an error message and I need to add a Domain in Django. > Then I can go to 'view site'. > > I can create a mailing list there. However when I send an email to be > subscribed, I get the following in mailman.log (and nothing else happens): > > > Oct 09 13:46:24 2025 (110452) deque: do_confirm_verify > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailman/model/domain.py", line > 177, in __getitem__ > raise KeyError(mail_host) > KeyError: 'lists.example.com' It appears you don't have a domain in Mailman core with mail_host = 'lists.example.com'. Do you see one in Postorius' domains view? If not, perhaps you need to add it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

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

by Thomas Stein

On 04.01.19 16:02, Thomas Stein wrote: > On 04.01.19 15:55, Abhijith PA via Mailman-users wrote: >> >> >> On Friday 04 January 2019 08:19 PM, Thomas Stein wrote: >>> On 04.01.19 09:40, Thomas Stein wrote: >>>> >>>> Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe >>>> i missed something else but after adjusting the permissions of that template everything worked as expected. >>> >>> While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should >>> I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation >>> what variables i can put in those templates? >> >> If you are using 3.2.0, you can do that from webapp itself. [ I haven't >> tried though] > > Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik. > > https://launchpad.net/ubuntu/+source/mailman3 This ppa seems to have 3.2.0. https://launchpad.net/~efficios/+archive/ubuntu/ci Is it trustworthy? Someone using this? thanks and cheers t.

7 years, 2 months

[MM3-users] Re: Moving from forum to Mailman 3

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/9/20 4:39 PM, jonathan.mailing.lists(a)gmail.com wrote: > > > > Thanks for this. I’m sure I could turn that basic information > > (from, date, subject) into an mbox file somehow. What else does > > Mailman need, eg to work out which messages are in reply to > > which? > > To properly thread messages, each message should have a unique > Message-ID: header and all replies should have an In-Reply-To: header > with the Massage-ID: of the message to which it's a reply. [example thread omitted] > The angle brackets around the strings are required and every Message-ID: > in the entire archive for a list must be unique. This is harder to do well (or even "well enough") than you might think. I recommend using some software targeting RFC 4122: https://tools.ietf.org/html/rfc4122. RFC 4122 is implemented in the Python standard library (the uuid module), so if you have Mailman, you have it. The command line utility uuidgen is also good, and you probably have that too if you prefer CLI scripting to Python. Steve

5 years, 4 months

[MM3-users] Re: installation

by Brian Carpenter

On 11/22/20 6:54 PM, Henry S wrote: > > Now I am trying to figure out how to configure mailman+postfix to pass > the unnecessarily convoluted world of spam-free certification and ip > blockings by those 'security lawmakers'. > > Any suggestions on how to not be blocked by gmail, hotmail, etc? I > have used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an > appropriate question to this mailman list. Mark Sapiro provided some very good suggestions. Is this a new IP address or one that has been used for mail traffic for a white? The only way Gmail and Hotmail will block an IP address is if you have some major outgoing spamming problems or in the case of a new IP address, the IP address has a sordid history which will be reveal if you do a RBL check on it. Gmail likes SPF records and MTA's that utilizes SSL for outbound mail. For Hotmail deliveries, you will want to signed up for Microsoft's Smart Network Data Service (SNDS) program which I find very good. Also sign up for their JMRP program for your IP address. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by Mark Sapiro

On 12/9/20 6:39 PM, matthew(a)alberti.us wrote: > > For core, the connection string seems to accept a tailing > "?charset=utf8&use_unicode=1" per > https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So > for core, maybe just updating the connection string to include > "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the > recommend encoding... maybe that should be updated? I'm in the process of doing that update. > Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is > recommended, and it needs to be explicitly identified in the database > settings for BOTH core and web, and probably somehow at database creation > time? It's not as critical for core because barring things like 4-byte utf-8 unicode graphics in list configurations, core doesn't store anything like that in its tables. The major issue is with HyperKitty where messages have emojis and other 4-byte utf-8 encodings in message subjects and bodies. -- 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: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/21/23 17:30, Thomas Ward wrote: > > MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). > > If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. -- 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: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 09:08, Wikinaut wrote: >>> In the Postorius held messages view, click on the message's subject to >> open a dialog showing the messages content > > Dear Mark, sorry: > How should I know this? Well, the subject of the message in the held messages view looks like a link. Maybe click it once to see what it does. > I'd rather prefer to have these both changes: > > i) relabel the existing one od three buttons from "accept" to "accept once" ; and > ii) add a fourth button "accept all messages from this sender (i.e. add to white list)" That wouldn't include options like "discard further posts from this user", "reject further posts from this user" and perhaps other possibilities. If I were going to do anything, it would probably be adding a line above the list of held messages saying something like "Click the message's subject for more options." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailman web interface / uwsgi

by Mark Sapiro

On 11/26/22 21:29, Jan Eden via Mailman-users wrote: > > Replicating this setup on the server solved the KeyError problem, > everything works now! I just wonder why these uwsgi parameters need to > be passed explicitly when using a file socket, but not with a http > socket. You are doing more than just switching from a tcp socket to a unix socket. You are also switching from communicating with uwsgi via http protocol to uwsgi protocol. > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > files when using the virtualenv installation instructions > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, not mailman-web. If you want, you could put mailman-hyperkitty.cfg in /etc/mailman3/ by putting ``` configuration: /etc/mailman3/mailman-hyperkitty.cfg ``` in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Issues encountered while upgrading to 3.3.7

by Mark Sapiro

On 12/5/22 10:02, Odhiambo Washington wrote: > On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Thus, putting >> ``` >> DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' >> ``` >> in your settings will maintain compatibility with pre 3.2 versions and >> existing tables and this is the correct thing to do. >> > > Thank you very much for the clarification. Also note that for the past year or so, the files postorius/example_project/settings.py:, mailman_web/settings/base.py, hyperkitty/example_project/settings.py and mailman-suite/mailman-suite_project/settings.py have all contained DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' and if you follow https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… you will import mailman_web/settings/base.py and pick this up from mailman-web 0.0.6 and both https://wiki.list.org/x/17892066 and https://wiki.list.org/x/17891998 suggest that your settings.py should be a copy of the mailman-suite settings.py file but with DEBUG = False, the implication being that when that file changes, yours should too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] How to edit default 'Reject (with notification)' message

by Stephen J. Turnbull

Zaheer Abbas writes: > Currently, the default rejection text is as follows: > > "Your message to the $list was rejected for the following reasons: > > The message is not from a list member > > The original message as received by Mailman is attached." [...] > Is there any source file, which I can modify to replace the default > rejection text mentioned above? Is mailman/src/mailman/templates/en/list:user:notice:rejected.txt what you're looking for? But it's not recommended to alter the source, because when you upgrade it will get overwritten, and then you have to remember how to do it again. I haven't done this myself, but IIRC you can select "Domains" from the menubar at the top, then the "Templates" button at the right, then "New Template", and select list:user:notice:rejected from the dropdown menu to set the template domain-wide. Unless you have a *lot* of domains, this is what I would recommend. There's a similar feature for individual lists. I forget how this interacts with localization for different languages, sorry. Steve

2 years, 9 months

[MM3-users] Re: Template for Password Reset Email

by Mark Sapiro

On 11/17/24 16:57, Mark wrote: > > I can see the French text for the "Password Reset Email" in the > django.po file. And running the compilemessages command reports the > "django.po" for French is okay and up to date. Should I be recompiling > the ".mo" file? No, It's fine. The issue is the language context for this message has nothing to do with any Mailman list's preferred language. Again, see https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… If all the lists on your server are French, you could set LANGUAGE_CODE = 'fr' in your Django settings. Otherwise, the user's browser has to include an Accept-Language: header specifying French as the most preferred language in it's request. Also note the ordering of SessionMiddleware, LocaleMiddleware and CommonMiddleware in the above doc. I have recently updated the various places where we suggest or supply MIDDLEWARE settings, but you may find that your settings have LocaleMiddleware after CommonMiddleware and you should fix 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, 3 months

[MM3-users] Re: Migrate from mysql to postgresql

by Mark Sapiro

On 03/17/2018 01:44 PM, Bjoern Franke wrote: > Hi, > > is it possible to migrate a mailman3-mysql-database to a > postgresql-database? > > I tried to convert it with pgloader, but some identifiers had to be cut off: > _address_id); > 2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner > idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e > wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac > gekrzt I suspect the issue is due to the way Mailman supports different databases via SQLAlchemy. The bottom line is the table and column specifications are based on the Mailman database models, but are database specific. If I were doing this, I would dump the data from MySQL, but rather than using the CREATE TABLE queries from the dump, I would let Mailman create a new PostgreSQL database and then just load the existing tables from the MySQL dump. However, that may all be irrelevant. I don't know which table/column that specific item comes from, but it appears just visually that idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e is already truncated so further truncating it to idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac may not be a problem. -- 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: messages with attachments, without text discarded silently

by Mark Sapiro

On 1/27/25 12:35, Schulz via Mailman-users wrote: > Using the current mailman version, I can reproduce the following: > - send a text-formatted email with attachment but without text body to a list. > - the msg will be received by mailman > - the msg shows up in shunt, the log shows: > ile "/usr/lib/python3.12/email/message.py", line 343, in set_payload > payload = payload.encode(charset.output_charset, 'surrogateescape') > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > UnicodeEncodeError: 'ascii' codec can't encode characters in position 10-17: ordinal not in range(128) Please provide the full traceback and the MIME structure of the message. > an attempt to unpickle the file leads to the same error. > I know it's uncommon to send emails without txt but with attachments - but it may happen; at least we would welcome an error message. Without more of the traceback I can't be sure which handler is doing this and without the MIME structure I can't be sure what's going on. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/29/2017 03:46 PM, Barry Warsaw wrote: > On Mar 30, 2017, at 12:34 AM, David Krantz wrote: > >> When starting this as the recipe seems reasonable I find that I have >> no reliable source for git links for the parts. Some of the git links >> I find are marked with "do not use" so it is a bit hard having >> confidence in selecting one of the others. > > All the Mailman 3 suite subprojects are listed here: > > https://gitlab.com/mailman > > Those project links will take you to the active git repositories. The only > one you should not use is mailman-bundler. To be more specific, the projects that are required for a fully functioning Mailman installation with Postorius and Hyperkitty are Mailman (the core) Hyperkitty (the archiver) Postorius (the web list management UI) django-mailman3 (common django things used by Postorius and Hyperkitty) MailmanClient (python bindings for the core REST API used by Postorius and Hyperkitty) HyperKitty - Mailman plugin (plugin for the core to communicate with Hyperkitty) -- 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: MM3 to MM3 migration

by Odhiambo Washington

On Wed, Feb 1, 2023 at 12:35 AM David Newman <dnewman(a)networktest.com> wrote: > I’m looking to migrate several mailing lists from one server running > MM3/Django/Hyperkitty to another. Same operating system and python > environment and venvs for both. Although the canonical hostnames for the > two servers will differ, I can use the same hostnames for lists once > I’ve got everything set up. > > Is this really as simple as building the new server, creating the same > lists on the new server, and rsync’ing the archives from the old server? > If not, how to do the migration? > > I checked the archives and saw many threads on MM2 -> MM3, but did not > see anything on MM3 migration. Thanks in advance. > Seeing as a venv is a self-contained container, I am tempted to say that it's possible to move one from one server to another - AS LONG as you also migrate the DB. I am not an expert on this so I stand corrected. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

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

by Ugnius

I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? > On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini > 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 > 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 > 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini > > This fishy, why do you have both uwsgi and "python manage.py runserver" running? > > You only need one of those, since they both do the exact same thing. Please remove > whatever is running the "python manage.py runserver" part and only use uwsgi. > >> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >> May mailman processes are next: >> >> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >> >> Looks like there are no double. Nothing more is running. >> >> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >> >>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>> >>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>> $ sudo pip3 install mailman >>> $ sudo pip3 install postorius >>> $ sudo pip3 install hyperkitty >>> $ sudo pip3 install mailman-hyperkitty >>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >> >> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >> >>> >>> >>> >>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>> >>> >>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>> > Hi. All the project installation is under the same user / path and >>> > it works. Archiving working as well, (just one remark: no matter what >>> > to set in postorius, hyperkitty shows list as public) >>> > I have found work around - it is possible to change list as private in >>> > "admin" page. >>> > I started to get issues with runjobs after I have created couple of >>> > new lists with "no archive" option. >>> >>> How did you install all these components. It seems there the installation is broken in weird ways. >>> >>> > >>> > If as owner user from project home I run: >>> > >>> > django-admin mailman_sync >>> > >>> > Traceback (most recent call last): >>> > File >>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>> > line 84, in _execute >>> > return self.cursor.execute(sql, params) >>> > File >>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>> > line 383, in execute >>> > return Database.Cursor.execute(self, query, params) >>> > sqlite3.OperationalError: attempt to write a readonly database >>> > >>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>> > "django-admin runjob new_lists_from_mailman" >>> > django.db.utils.OperationalError: attempt to write a readonly database >>> > END TRACEBACK >>> > >>> > I did not find information how to fix this. It was worked without errors >>> > before. >>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>> > to work. >>> > If I start "mailman start", then "django-admin mailman_sync" failing >>> > again. >>> > I did not check other jobs, but I think what is related to database, >>> > will get errors. >>> > Seems mailman locking the database. It is not a file permissions issue. >>> > Mailman db location is: /project_directory/var/data/mailman.db >>> > >>> > if to rename /project_directory/var/data/mailman.db to something, >>> > mailman creates database file size 0, django-admin runjobs start >>> > working, but of course postorius stops working. I did it for testing. >>> > I have returned this database file back, postorius started to work >>> > again, but django-admin runjobs does not work, error: "database read >>> > only". >>> > Please help me how to fix this issue. >>> > _______________________________________________ >>> > 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) >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> > > -- > thanks, > Abhilash Raj (maxking) > >

6 years, 6 months

[MM3-users] Re: Understanding of members, accounts

by Mark Sapiro

On 5/11/20 5:15 PM, Peter Adebahr via Mailman-users wrote: > Is the solution to "sign up", using one's very e-mail address already in > the system? Yes. The address is in the Mailman Core part of the systen, but not in the web UI part. > I would like to understand why there is a difference between being > (only) a subscribed member and a member having an account - or, what > might be the advantage of being a member without an account? Being a mailing list member is a Mailman core concept. It usually says you receive posts from the list based on your delivery status and you can post based on your moderation status. Logging in to the web UI to access HyperKitty and Postorius is a Django concept and requires a Django account. If all you want is to post by email and receive messages from the list, you don't need a Django account, but to manage your user settings via Postorius and to visit private archives, you do. -- 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: spanish localization

by Stephen J. Turnbull

Victoriano Giralt writes: > Thanks Stephen for reminding me that sometimes I write what looks like > proper English on the surface, but the meaning of it comes from the > deep corners of my mind in some long forgotten dialect :-) Your English is fine, it was just my lack of imagination: on February 12, I couldn't conceive of February 3 being even a little "old"! More important, as long as the .mo file is more recent than the .po file, that's the best the release manager can do. I haven't been involved in the release process, so I can't swear to it personally, but if Mark says that new translations generate a merge request automatically, and we make sure that the translations are merged before release, I believe him. That's optimal as far I am concerned. Perhaps some enterprising soul would be willing to automate production of pip'able packages containing only new translations, but without that, I don't see how to beat our current procedures. (I wouldn't want to use such a thing, though, I'd be too afraid that one day all the translations would be replaced with Dril tweets!)

5 years

[MM3-users] Modify approval email

by Stephen J. Turnbull

pau.baiges(a)csuc.cat writes: > Is there a way to modify the email that is sent by default to list > owners when a non-list member sends email to the list? Yes. As list owner (or site admin) in Postorius go to Templates, and click on "New Template". Select list:admin:action:post from the drop-down menu to the right of "Name". Copy the current message (site-packages/mailman/templates/en/list:admin:action:post.txt is the original, but do not edit this -- it will be overwritten on upgrades) to the text box and edit to taste. Unfortunately there is no "web site" variable but typically that is the same for all lists, so adding https://your.host.here/mailman3/lists/$list_id/held_messages in some appropriate place probably does what you want. There is no way to indicate that this is a link because these messages are plain text. However, most mail clients will turn a URL into a link. If your moderators are not so lucky, try wrapping it with <URL:https://your.host.here/mailman3/lists/$list_id/held_messages> or even the usual HTML: <a href="https://your.host.here/mailman3/lists/$list_id/held_messages"> Moderation Page </a> One of those may help. Steve

2 years, 5 months

[MM3-users] dkim failing

by Mark Sapiro

On 10/15/18 8:37 PM, Abhijith PA via Mailman-users wrote: > > I am seeing dkim fail in mail that people send to lists > /dkim=fail reason="signature verification failed"/ > but it is not happening when the list solely sending mail to subscribers > (like digest, or subscribe/unsubscribe messages etc). I recently added a > new domain to the mailman3. After this I started noticing this issue. > Any help ? Are you saying the DKIM signature on the incoming post fails to validate in the post as sent from the list, or are you saying that a DKIM signature added by your MTA to the outgoing post fails to validate. If the former, this is probably expected. If your list does any content filtering, adds a subject prefix or adds a list header or footer, these transformations will break the incoming DKIM signature. This is why we offer DMARC mitigations. If the latter, you may be doing your own DKIM signing before Mailman applies transformations to the message. You need to sign the message on the way out, not before. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

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

by Mark Sapiro

On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is > there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ 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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- 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: How to delete non-users

by Mark Sapiro

On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Domain in welcome message

by Mark Sapiro

On 02/19/2017 02:05 PM, Maadix wrote: > Hi, > I'm having problems with customizing welcome message > > It's working fine for > var/templates/site/en/welcome.txt > > but not for domains or lists , so maybe I'm doing something worng > > I'm using a subdomain as mail_host which is different from the URL Host. > > I've been trying all these combination, with no success: > > var/templates/domains/sub.example.com/en/welcome.txt > var/templates/lists/listname.sub.example.com/en/welcome.txt > var/templates/lists/listname(a)sub.example.com/en/welcome.txt > > I'm running mailman-bundler version 3.0.0 Templating has changed for MM 3.1, and I don't have a 3.0 platform available for testing, but as far as I can recall, the paths var/templates/domains/sub.example.com/en/welcome.txt and var/templates/lists/listname.sub.example.com/en/welcome.txt should be valid for domain and list specific templates and the precedence should be (high to low) list, domain, site, default. I don't know why it isn't working for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Set Postorius interface locale

by Duane Raymond

Hi everyone, Thanks to Brian I'm up and running with my migrated mailman3 lists and am now starting to get into customising the interface (styling and content). I've been trying to figure out how to set/change the Postorius locale - I specifically want to change some text strings on the info page without breaking the i18n mechanisms. I've worked with po and mo files before, so changing and compiling them isn't a problem. The problems I've encountered so far are: 1) Where do I set the local of the Postorius interface? 2) Individual lists have a language setting, but it doesn't seem to reflect what the Postorius locales are as the only english option is "English (USA)" and none of the other English speaking locales and on the file system there is no en-us PO files....so I suspect I'm looking in the wrong place. Am I looking at this all wrong? The documentation doesn't seem to have any info about this and yet the mechanisms seem to be there. Once I learn more I'm quite keen to start working on improving the documentation based on what I learn. Cheers, Duane

5 years

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

by William Oliver

On Sat, 2022-02-19 at 13:11 -0800, Mark Sapiro wrote: > On 2/19/22 12:41 PM, William Oliver wrote: > > > > So, I can just kill the listname user altogether? > > > As far as Mailman is concerned, Yes. > > No joy. I deleted the list as well, and recreated it with the same name -- and the error repeated. I created a list with a different name, and there's no error. I must have really screwed something up in dovecot. Happily, this is a small list, so I'll just migrate everybody to the newly named "listname2". So.. as an aside, it was a bit of a hassle to copy and paste all the usernames from the "Users" list in Postorius to the "Mass subscribe." The only way I could see to do it was copy and paste them one at a time. That worked OK for me, since it's a small list, but that made me wonder if there was a way to select, say, 100 users out of Users and subscribe them all to a list. billo

4 years

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

by Brian Carpenter

On 9/14/20 10:54 AM, Mohsen Masoudfar wrote: > 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. 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? > Is there a way to manage this feature in a secure way? We no longer use Django to manage our mailman 3 user registration, but the same concerns that you have are still valid for us. What we do is run a cronjob that purges all unverified accounts once per day. So problem solved for us. Perhaps something like that can be done for Django. -- 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, 5 months

[MM3-users] Re: SpamAssassin header confusion

by skenny＠scss.tcd.ie

My last post was speculative and wrong (my original one contained mistakes too). The summary question is this: A post to the mailing list passes through Amavis/Spamassassin on the mail server that feeds posts into Mailman. On the - different - mail server that delivers the message to my inbox (I'm a member of the list), it passes through another instance of Amavis/Spamassassin. So why do I only see one set of X-Spam-* headers - those added by the latter mail server? It turns out that there is a setting in Amavis called $remove_existing_spam_headers, and by default it is set to 1. It means: "remove existing spam headers if spam scanning is enabled (default)". That default setting on the latter mail server explains the absence of the previous set X-Spam-* headers. As expected, when I switch this setting to 0, Amavis stops removing Spam headers. If I then send a new post to the list, I can see in the email that drops in my inbox all the Spam headers that were added along the way, and not just those added by the final mail server. Thanks Mark for taking the time to respond. Kind regards Stephen

4 years, 10 months

[MM3-users] Re: anyway to change/set options for a bunch of users?

by Mark Sapiro

On 3/22/22 06:19, bob B via Mailman-users wrote: > We just migrated to mailman 3 and one of my admins asked is there a way to change their digest options, when adding a bunch of users via mas subscription? Not yet at least. You could submit a feature request at https://gitlab.com/mailman/postorius/-/issues/new to be able to set Delivery mode when mass subscribing. > I was looking for an option to say all new users are set to digest, but I can't find it. Also, is there a way to select multiple users in list and change their digest options? I believe could do this in mailman2 but I am trying to figure out if this is possible for the GUI in mailman3? No, it's not, and in MM 2.1 you could check the digest option for multiple users in the Membership Management... -> Membership List, but if the list was paginated, you'd still need to go page by page. -- 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: Legit login attempts yield, "An error occurred while processing your request."

by Mark Sapiro

On 8/14/24 3:18 PM, Greg Newby wrote: > > My primary question is: *How can I find out what's causing this*? > > I've looked in all the MM and web logfiles, by "tail -f" while generating > the error, and nothing is logged there. Apache logs shows something like > this: > > x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ > HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" > "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" This is django-allauth. Errors should be logged in Django's log which, if yoiu followed our virtual env install doc is /opt/mailman/web/logs/mailmanweb.log. > I've come across this error while trying to do authentication-related > activities that worked before the reboot: Did django-allauth get upgraded to >=64.0. There are currently issues with that. It should be >=0.63,<64.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

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

by Ken Alker

--On Monday, June 26, 2023 2:32 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 11:53 AM, Ken Alker wrote: >> >> Is the var/messages hierarchy also where all the archived emails are >> stored for future viewing via the web interface? > > > No. They are stored in the hyperkitty_email and hyperkitty_attachment > tables in the database. What else is stored in /var/messages, if not archives? I see 4711 messages in that directory (which I presume would be as many messages are in the archive database). If there is a write-up on this, feel free to point me to it. I found <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode…> but this isn't really answering my question. >>> Also, there is a long thread at >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thr >>> ea 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. > > Was this in the same `mailman shell` interaction or a new one? What was > the error? I am pretty sure I started over entirely (ie. exited via ctrl-D and restarted). It was a syntax error, but in reviewing, I see now that I'd copied the example exactly, and I included the trailing quote mark. After some experimentation and reading, I see now that that should not have been there. >> 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)? > > > I'm not sure of the sequence of events, but I think you probably looked > in Postorius before you quit `mailman shell` and then you quit `mailman > shell` with ctrl-D which did an implicit commit. I didn't think so, but I'll certainly buy that. So, I'm assuming by this you are implying that there is no helper function that needed to run and the number of held messages should have dropped to zero immediately upon a refresh of the web page? >> 2) Is the "commit" even necessary (I saw it in someone else's script in >> the thread)? > > It is necessary to explicitly commit() or quit with ctrl-D to actually > update the database. Got it. Thanks. That explains why I didn't see any deletions when I re-ran the script the second time (after likely exiting with ctrl-D first). >> 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)? > > > Yes, you can save a script in the bin/ directory in your venv and run it > with `mailman shell -r`. See `mailman shell --details`. > > >> 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. > > The request.id is constant for that request object. The request object is > fixed for a specific held message request. I.e., a specific held > message's request object and its request.id and other attributes are > fixed until that request is handled. So if I run the script, exist the shell, then come back in again, I can't rely on the request.id being the same? I'd need to re-run the script and get a new request.id?

2 years, 8 months

[MM3-users] Re: Hyperkitty reply indent

by Abhilash Raj

On Sun, Jul 21, 2019, at 5:07 PM, Abhilash Raj wrote: > > > On Sun, Jul 21, 2019, at 1:13 AM, Andrew Bernard wrote: > > Hi Abilash, > > > > I took a quick look through the Hyperkitty source code to try to find > > where the indent is computed, to no avail, not being experienced with > > that code base. > > > > But wouldn't there be some simple code that increments an indent value > > somewhere that could easily be modified? > > https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/templates/hype… > > You could remove the "margin-left" on the class to get rid of the indent > if you want to patch your installation. > > I want to basically disable this based on the screen size and set this > value null for smaller screens only since this is helpful in threaded > conversations in larger screens. I recently worked on this and removed the indent on smaller screens. Please check out https://gitlab.com/mailman/hyperkitty/merge_requests/171 if you want to do this on your own server right now. I cut a release soon. -- thanks, Abhilash Raj (maxking)

6 years, 6 months

[MM3-users] mailman web spamming uwsgi error log.

by Sarah H

I'm having an issue with the mailman web logs (/opt/mailman/web/logs/uwsgi-error.log) spamming the below: 20:53:44 [Q] ERROR Failed [rebuild_mailinglist_cache_for_month] - MailingList matching query does not exist. : Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/django_q/cluster.py", line 436, in worker res = f(*task["args"], **task["kwargs"]) File "/opt/mailman/venv/lib64/python3.6/site-packages/hyperkitty/tasks.py", line 79, in _rebuild_mailinglist_cache_for_month mlist = MailingList.objects.get(name=mlist_name) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/db/models/query.py", line 417, in get self.model._meta.object_name hyperkitty.models.mailinglist.MailingList.DoesNotExist: MailingList matching query does not exist. the best match I can find in the archives is https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I have used suggested command there (/opt/mailman/venv/bin/mailman-web runjobs recent_threads_cache) as well as manually running the hourly, daily, weekly, and monthly crons manually and all run successfully but I'm still getting the same entries spamming the logs to the point that when I discovered this the logs were 9.6GB in size. I do not have a list named "MailingList".

4 years, 8 months

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

by Mark Dadgar

On Oct 15, 2021, at 7:46 AM, Shawn Heisey <mailman(a)elyograg.org> wrote: > On 10/14/21 10:09 PM, Mark Dadgar wrote: >> I REALLY encourage you not to install via the Ubuntu packages. A number of us here have done so and it always ends in tears. I ended up paying someone to re-install for me via pip so I had a clean baseline to admin from going forward. > > I had lots of trouble with the pip/venv setup. So I decided to give the docker route a try. Having trouble with that too. Looking over the instructions, I seem to have missed some of the info on my first try. I will give it another whirl after my work shift ends today. That’s actually why I paid someone to do in the initial install. While I have 3+ decades of UNIX-like admin experience, I am not even remotely well-versed in Python and its ecosystem and/or Docker. Unfortunately, the person I hired, who did a great job and has contributed mightily to this community, is no longer with us. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 4 months

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

by Danil Smirnov

Hi Odhiambo, I see that URLs like " https://list.rc.org/static/CACHE/css/output.93545e20bc30.css" are failing, hence you might need to reset the Django cache with something like "mailman-web clear_cache". With my best regards, Danil Smirnov Mailman3.com On Wed, Dec 14, 2022 at 6:16 PM Odhiambo Washington <odhiambo(a)gmail.com> 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? > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > _______________________________________________ > 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 danil(a)smirnov.la >

3 years, 2 months

[MM3-users] Re: mailman-web causing constant 100% cpu load of mysqld

by Odhiambo Washington

On Fri, Jan 13, 2023 at 7:33 PM Johannes Rohr <johannes(a)rohr.org> wrote: > Dear all, > > with mailmanweb running, the CPU load of mysqld constantly hovers around > 100% > > In /var/log/mysql/errors.log I see repeatedly: > > 2023-01-13 17:22:42 27198 [Warning] Aborted connection 27198 to db: > 'mailman_core' user: 'mailman' host: 'localhost' (Got an error reading > communication packets) > 2023-01-13 17:27:43 29621 [Warning] Aborted connection 29621 to db: > 'mailman_core' user: 'mailman' host: 'localhost' (Got an error reading > communication packets) > > This also seems to affect other services such as dovecot which rely on > mysql and at times can't connect to it. > > Does anyone have a suggestion what to do about this? > > Cheers, > > Johannes The issue could be related to the cron run for archiving, given that MM3 stores the archives in the DB. You could start by looking at tuning your MySQL server instance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Settings for prevention of spam obfuscation

by Richard Rosner

Are there any settings that may help with making it easier seeing spam as spam? E.g. some mail programs, including Outlook, allow the user to set a from mail address that most mail clients will show instead of the true sender address, but the senders mail address is still present in the sender header field. While some people and companies carelessly abuse that functionality, hiding their true mail address, those bad practices also are abused my spammers and others. Does mailman have any settings that would remove any such obfuscations, e.g. in this case detect the manipulated from address and replace it with the sender address? While I do run my own spam filter, it's virtually getting harder every day to make sure you detect all spam while not having too many false positives. If it was possible to reverse at least the most obvious manipulations, that would probably already help. Also, it would make it much easier for the users to see at first glance who actually wrote an email. It's always less trustworthy if the senders address is shown as user3168(a)suspiciousdomain.gg instead of it being manipulated to say support(a)yourprovider.com.

2 years

[MM3-users] Re: Import Archives using Docker Image

by Abhilash Raj

On Thu, Jun 6, 2019, at 11:37 AM, brian(a)emwd.com wrote: > I want to test out importing a 2.1 archive into a Mailman 3.2 list. I > am using maxking's docker images for MM3. How would I go about > importing the mbox file? I don't think the following commands would > work on a Docker installation of MM3: > > $ python manage.py hyperkitty_import -l foo-list(a)example.com > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > $ python manage.py update_index_one_list foo-list(a)example.com > > I am not sure how to go about doing this within Docker. You can copy the mbox file inside the container and them import it from there. See docs for "docker cp"[1] on how to copy something inside a container. After that, you can enter the container with usual "docker exec -it mailman-web bash" and use the commands mentioned above. https://docs.docker.com/engine/reference/commandline/cp/ > > Thanks for any assistance, > Brian > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 9 months

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

by Mark Sapiro

On 4/6/21 2:00 AM, marcus.granath(a)gmail.com wrote: > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? My fault. Sorry for the confusion. I wrote: > Now, no one can post. To allow your set of users to post, you have > choices. The easy way but not secure against spoofing is to set the > Maderation Action for the three allowed members to List Default and toi > create a non-member for no-reply(a)abc.com and set it's moderation action > to List Default. That should have said "set the Moderation Action for the three allowed members to Defer or Default Processing (again two names for the same thing) and to create a non-member for no-reply(a)abc.com and set it's moderation action also to Defer or Default Processing." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 2:10 PM, Marco Marinello wrote: > Dear Mark, > > configuration needed much troubleshooting so I'm sure I always restarted mailman core along apache2 but since it's still a testing environment, I took the liberty to test it again for you. > > # pip install https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip > # pip install https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… It appears that https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… is the latest mailman-hyperkitty, but https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip is missing some commits. It has https://gitlab.com/mailman/hyperkitty/-/commit/79b22a23d3390db741a8233fa1ff… but is missing https://gitlab.com/mailman/hyperkitty/-/commit/ec9c8ed18798cf8f7e89dfaba001… which is very strange because it does seem to have https://gitlab.com/mailman/hyperkitty/-/commit/705bdbb2fb27be60d17ada7cba84… I Suggest you do pip install -U HyperKitty pip install -U mailman-hyperkitty which will get the latest packages from PyPI or if you want the heads from gitlab, pip install git+https://gitlab.com/mailman/HyperKitty.git pip install git+https://gitlab.com/mailman/mailman-hyperkitty.git -- 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: search this list searches more then just this list

by Marco van Tol

Op 23 jan 2024, om 19:09 heeft Mark Sapiro <mark(a)msapiro.net> het volgende geschreven: > > On 1/23/24 05:49, Marco van Tol wrote: >> Small unfortunate twist, this leads to: >> --- >> [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... >> --- >> I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? > > This issue is discussed at <https://github.com/notanumber/xapian-haystack/pull/181>. > There are two patches for this issue. They are somewhat different approaches, but either one is OK. One patch is the one in the above PR <https://github.com/notanumber/xapian-haystack/pull/181/files>. The other is at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…>. > > I use the one from the PR, but it requires a substitution `s/force_text/str/`. Hi, thanks! Just to double check, do you mean `str` or `force_str` in the substitution? I found a comment on this topic regarding django-4 where they advice to use force_str. https://stackoverflow.com/questions/70382084/import-error-force-text-from-d… Thanks! Marco van Tol

2 years, 1 month

[MM3-users] Re: Hyperkitty error - not archiving

by Odhiambo Washington

On Sat, Jul 26, 2025 at 8:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/25 1:23 AM, Odhiambo Washington via Mailman-users wrote: > > I am seeing the error below and wondering what's the cause: > > The message has some issue which is causing HyperKitty to not be able to > archive the message. The message will be queued in Mailman's > var/archives/hyperkitty/spool/ directory and can be examined with > `mailman qfile`. If you do that and the cause is not clear, you can post > the message, and we will investigate. If the message is unwanted, you > can just remove the file from Mailman's var/archives/hyperkitty/spool/ > directory. > I had examined the message using 'mailman qfile', but did not see anything obvious. There were 3 files inside the spool/ directory. I have just checked again and they are no longer there. -- 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]

7 months, 1 week

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

by Mark Sapiro

On 10/20/25 23:21, Stephen J. Turnbull wrote: > > I agree with Mark -- I don't see how to do this without changes to the > code. Also, note that even if you could configure this as you desire, > the CC addresses will be delivered. But people who subscribe but > aren't CC'd will receive the post only if and when the post is > released from hold. Only you can decide whether that's desirable, but > it's likely some subscribers will be unhappy about it. This is an important point. If your goal is to prevent exposing those non-member addresses in Cc:, etc. in posts from the list, then all this may help, but if your goal is to prevent list posts from going to non-members, you can't accomplish that. by the time mailman receives and perhaps holds the post, it will already have been sent to all the directly addressed To:, Cc: and Bcc: recipients. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- 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: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 11:01 -0500, William Oliver wrote: > > . > [snip] > However, when I try to sent an email *to* the list from either > account, > I get the following error: > > This is the mail system at host mail.libertyfp.org. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > > The mail system > > <"lmtp:[mail.libertyfp.org]:8024"@libertyfp.org> (expanded from > <fplist(a)libertyfp.org>): unknown user: > "lmtp:[mail.libertyfp.org]:8024@libertyfp.org" > > Apparently, fplist(a)libertyfp.org is getting rewritten to > 8024(a)libertyfp.org. Another data point. When Ichange the port number in mailman.cfg, the error changes to reflect it. When I change the port to 8055, I get: The mail system <"lmtp:[mail.libertyfp.org]:8055"@libertyfp.org> (expanded from <fplist(a)libertyfp.org>): unknown user: "lmtp:[mail.libertyfp.org]:8055@libertyfp.org"

4 years, 2 months

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

by Mark Sapiro

On 5/19/23 09:10, Christian via Mailman-users wrote: > > May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: > to=<billb6951(a)gmail.com>, > relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, > delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host > gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM > domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard > fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: > [192.46.218.224]. To best protect our users from spam and 550-5.7.26 > phishing, the message has been blocked. Please visit 550-5.7.26 > https://support.google.com/mail/answer/81126#authentication for more 550 > 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - > gsmtp (in reply to end of DATA command)) `dig txt lists.ccalternatives.org` reports "v=spf1 a mx ip4=192.46.218.224 -all" It should be "v=spf1 a mx ip4:192.46.218.224 -all" i.e. :, not = > Could the hard fail policy be implicated in the gmail rejection? Yes but only because the ip4 is not effective due to the syntax error. ~all could help, but I suspect replacing the = with : will do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Mark Sapiro

On 07/18/2018 02:07 AM, Sebastian Hagedorn wrote: > > I have only now started playing around with Mailman 3.2, because I never > managed to get the earlier releases to work, and reading through the > documentation I thought that such situations could be handled with > Alembic, as described here under "Database Migrations": > > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> > > Is that not the case, and if not, in what cases can or should it be used? Alembic is used by Mailman core to migrate changes in Mailman's data models (database schema). It interfaces with SQLAlchemy <https://www.sqlalchemy.org/> which is used by Mailman core to interface with the underlying SQL database. Alembic is used by mailman developers to create migrations when table and column definitions are modified for some reason. It is not used by end users unless they are actually modifying Mailman's code and database schema. Alembic does not do migrations based on a change in the underlying database engine, e.g. SQLite -> PostgreSQL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: API privileges question for mailman3

by Stephen J. Turnbull

bob B writes: > Thanks, I thought about a separate instance, but then I have to set > them up a separate mail domain, which may ultimately be the > answer... but I am sure there will be meeting to discuss :) How quickly do you need this, and how secure does it need to be? For example, are the relevant folks all going to be coming from inside the organization's firewall? (I'm thinking "locks are for honest people, the crooks know how to pick them".) @PeanutGallery Anybody else want it? I'm interested in working on it (I'd like to see more layered security in Mailman, among other things) but tbh I wouldn't bet on me getting it done in less than 6 months, even with the head start that "lemme" gives. OTOH, if several people express interest and optionally (I mean optionally but it does help ;-) put some money behind it, you might find somebody with more current skills interested in the work. For the longer term, there's Summer of Code (no guarantees it will even exist, and we might not get a nibble from an appropriate student). Steve

4 years, 4 months

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

by Ron / BCLUG

Steve Brown wrote on 2024-04-16 15:53: > My understanding is that "yes" to Send Digest Periodically is supposed > to send digests daily even if the threshold size is not reached. Hi Steve, As Jered said, it's probably to do with the `cron` job setting. User `mailman` should have a crontab entry something like this: `@daily /opt/mailman/venv/bin/mailman digests --periodic` Running `mailman digests -h` seems to indicate that should work if done daily, but if there's a problem (bug?), then maybe an entry with `mailman digests --list $list_name --send` would force the digests to be sent? ``` mailman digests -h -l, --list list Operate on this mailing list. Multiple --list options can be given. The argument can either be a List-ID or a fully qualified list name. Without this option, operate on the digests for all mailing lists. -s, --send Send any collected digests right now, even if the size threshold has not yet been met. ... -v, --verbose Print some additional status. -p, --periodic Send any collected digests for the List only if their digest_send_periodic is set to True. ``` rb

1 year, 10 months

[MM3-users] Re: "held for moderation" - alias domain details sought

by Jeremy Stanley

On 2024-11-01 11:04:07 -0700 (-0700), Greg Newby via Mailman-users wrote: > Hi friends. I've viewed this old thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > and documentation here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > (and the Postfix docs it links to). Those documents don't seem to guide my > situation, or maybe I just need a more specific example. > > The problem is that when messages are delivered to the alias domain, they > are held for moderation. I.e., mail to the alias domain like > testlist(a)domain.tld is held for moderation, but mail from the same > subscribed, non-moderated user to testlist(a)lists.domain.tld is posted > immediately without moderation. [...] I manage a similar setup (though with Exim instead of Postfix), and when migrating from Mailman v2 to v3 kept the same basic settings which seemed to work: notably, under Message Acceptance I set the alias addresses for the list in the Acceptable aliases field. If memory serves, not doing that caused messages addressed to those aliases to be unconditionally held for moderation. -- Jeremy Stanley

1 year, 4 months

[MM3-users] Re: django fake users

by Andrew Hodgson

Stephen J. Turnbull wrote: >r.woithe(a)callassoftware.com writes: > > is there a opportunity to avoid django fake users? > > Because of it is not stopping, further and further fake users are > subscribing. >Require moderator approval for subscribing. I don't think this would help the issue. What I am seeing here is users signing up through Postorius using the sign up option which then creates an account in Django (but not Mailman). Yesterday alone I had over 700 of these accounts created. I don't know whether they pass email confirmation or not (I don't see this in Django admin), however they don't get added as users in Mailman and they don't attempt to subscribe to any list. >It may be possible to do something automatic, but you need to explain how you know these users are "fake", and it has to be something that can easily be detected with a few lines of Python. If it becomes at all complex, it will almost surely make trouble for "real" subscribers. I agree, this is why I am taking the route of running a regular Cron job to delete the users as explained earlier. Andrew.

5 years, 1 month

[MM3-users] Re: Cannot connect to SMTP server

by Mark Sapiro

On 8/13/22 15:14, mkummini(a)cmi.ac.in wrote: > > However, I get the following line each time I do a restart > Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 > I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. You only see this message once at startup because it is only issued once until there is a successful delivery. This error can occur for reasons other than an inability to connect to the smtp server. In particular, if there are errors in decorating the message with a header and/or a footer because of permissions or other problems in retrieving a list:member:regular:header or list:member:regular:footer template, this will occur. Have you put templates in Mailman's var/templates directory (possibly named /var/lib/mailman/templates in the debian package). If so, can the Mailman user (I think `list` in a debian package) find and read them? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

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

by Mark Sapiro

On 1/31/25 21:44, Stephen J. Turnbull wrote: > > I don't think that's the best we can do, though. Especially if > Convert HTML to plain is also yes, we want to preserve the HTML part > and convert it, don't we? Not if we're collapsing alternatives. If we're collapsing a multipart/alternative part with text/plain and text/html alternatives to just the first alternative we don't keep the text/html part. The only html parts we keep and possibly convert to plain text are ones that aren't a second or later alternative in a multipart/alternative part. > I think a better (or additional) strategy > would be to check the selected alternative for blank, and if so, drop > it and try again for an appropriate type. The collapsing of a two part multipart message with an empty first part into a single part message with just the second part is the last thing that's done after all other content filtering. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: RHEL 7 + Mailman 3 : Need help and guidance

by Abhilash Raj

On Tue, Jul 9, 2019, at 11:39 AM, vgandhi(a)fdu.edu wrote: > Hi, > > We would like to use the latest Mailman 3 in our environment. We are > planning to set up RHEL 7 virtual machine. I am trying to figure out > best method (if possible - step-by-step guide) for installing and > configuring Mailman3 on RHEL 7 . You will need Python 3.5 or newer(preferably, 3.6+, since 3.5 is no longer maintained) in order to install Mailman3. I am not entirely sure if it is available on RHEL 7, but you can definitely install it from EPEL. There aren't any maintained RPMs that we know of, so you may have to do a manual install from PyPI packages. Here[1] is a document describing the installation steps for Mailman packages in a virtual environment. [1]: http://docs.mailman3.org/en/latest/prodsetup.html > Can someone please provide me some guidance or point me in direction. > > Thank you. > _______________________________________________ > 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: Footer from templates not working - DB issue?

by Hans Mayer

Hi Mark, many thanks for this hint. I updated table "template" and replaced "localhost" with the real name and it worked. // Hans -- On 25.09.22 19:28, Mark Sapiro wrote: > On 9/25/22 05:26, mailman--- via Mailman-users wrote: >> Dear All, >> I have a similar issue. Also on Debian 11. Also installed as Debian >> PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) >> I am using sqlite3. When I do the SQL-query I get an URI which is in >> multiple reasons wrong >> http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… >> > > The initial part of that URL is set from the Django setting > `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to > `http://localhost/mailman3/`, it should probably be just > `http://localhost/`. > > >> OK - the hostname could be changed but the path is not existing at all. >> There is no file "list:member:regular:footer" on the complete >> filesystem. > > It's not a file. It refers to an entry in the postorius_emailtemplate > table in the database which is retrieved via the Postorius API. >

3 years, 5 months

[MM3-users] Re: Migration advice

by Mark Sapiro

On 08/28/2018 06:42 PM, Quanah Gibson-Mount wrote: > Hi, > > I'm looking at migrating from an old server running mailman 2.1.15 > (Debian wheezy) to a new Ubuntu 18.04 LTS system. I'd like to upgrade > to mailman3 as a part of this migration. I was reading the migration > docs (<http://docs.mailman3.org/en/latest/migration.html>), which seem > to require both mailman2 and mailman3 be installed concurrently on the > same system. Is that correct, or can I rsync the mailman2 list > information onto the new server without mailman2 itself being present, > and import from there? Short answer - Yes. You need only a Mailman 3 installation. You also need a copy of the Mailman 2 lists/LISTNAME/config.pck file for input to 'mailman import21' and a copy of the Mailman 2 archives/private/LISTNAME.mbox/LISTNAME.mbox file for input to the Django management hyperkitty_import command. It would be good to check the archives/private/LISTNAME.mbox/LISTNAME.mbox file with the Mailman 2 bin/cleanarch command, but you can do that on the Mailman 2 system before copying the mbox. -- 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: Using REST with CLI using curl .... help needed

by Mark Sapiro

On 12/8/20 2:01 AM, Krešimir Mihalj wrote: > Hi ! > I need simple add/delete member to list using rest ..... but all documentation is for python and not helpfull for me, .... and I need these in CLI using curl command .... Have you seen <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > To add member using CLI i tried this command: > > curl -d "{'list_id' : 'list.domain.com', 'subscriber' : 'user(a)email.com'}" -H 'Content-Type: application/json' --user restadmin:restpass http://localhost:8001/3.0/members Try this: > curl --user restadmin:restpass --data-raw 'list_id=list.domain.com&subscriber=user(a)email.com' http://localhost:8001/3.0/members > Also, if someone is willing to give example: delete user: user(a)email.com from list: list(a)domain.com First find the member_id with something like > curl -urestadmin:restpass http://localhost:8001/3.0/lists/list.domain/member/user@email.com which will return json including the value of member_id Then you can do > curl -urestadmin:restpass -X DELETE http://localhost:8001/3.0/members/xxxx where xxx is the member_id. -- 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: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 3:12 PM, Jens Günther wrote: > > > -> the first one works and leeds to > https://mailman.xyz.de/mailman3/postorius/lists > -> the second one redirects to > https://mailman.xyz.de/mailman/postorius/lists > -> which does not exist, since Apache-alias is only for mailman3 Sorry, I missed that it was mailman vs mailman3. > > I only use the apache-conf given in the documentation: > > <code> > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 > unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > </code> I don't use uwsgi so I can't advise on its configuration, but do you have USE_X_FORWARDED_HOST = True SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') in your Django settings? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Disabled by bounce

by Jan Eden

On 2023-02-17 21:39, denise.mcgeachy--- via Mailman-users wrote: > Hi all - new to this forum but am trying to work out a similar issue raised by a list member's IT department. I'm a bit out of my depth here and hoping you all can help. > > They have recommended: > > - When the mailing list relay an email from a member of the list to other members, the email from address should be the mailing list and not the user sending the original email. For example: list-name(a)mydomain.ca (on behalf of Sally Brown) > - The mailing list should not modify the original email and thus breaking the DKIM signature > > I have clicked the DMARC mitigation unconditionally option which seems to solve the second point but haven't managed to have it sent by the list name but not as suggested in the first point. I either get "my email via list(a)mylist.ca" or list(a)mylist.ca" > Is anyone aware of a setting to do this? To distribute messages with valid DKIM signatures, I set remove_dkim_headers: yes in /etc/mailman3/mailman.cf and add a new DKIM signature for my mailing list domain. - Jan

3 years

Search results for query "dO"