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

[MM3-users] Re: restricting public lists per virtual domain

by David Newman

On 12/16/21 2:40 PM, Mark Sapiro wrote: > On 12/16/21 12:25 PM, David Newman wrote: >> Can lists set to be viewable on the index page be limited to the >> virtual domain they are a part of? >> > > > Have you set > > FILTER_VHOST = True > > in your Django settings? I had not, and this was the variable I was looking for. Thank you! This works for HyperKitty and works partially > for Postorius. For Postorius, it doesn't work if there are multiple > domains with different email hosts which have the visiting host as their > web host[1] but works otherwise. > > See https://gitlab.com/mailman/postorius/-/merge_requests/500 and > https://gitlab.com/mailman/postorius/-/issues/394 > > In your case, as long as the domains lists.dom1.tld and lists.dom2.tld > have different mail hosts, this should work. > > [1] An example of what doesn't work in Postorius is the following: > > Visit https://lists.example.com/mailman3/lists. If there are 2 domains > with web host lists.example.com, one of which has mail host example.com > and the other has mail host lists.example.com, all lists will be shown > regardless of domain. On the other hand, if all the domains with web > host lists.example.com have the same email host, say example.com, then > only lists with email host example.com will be shown. Awhile back Stephen Turnbull suggested a terminology guide that included an MM3-specific definition of FQDNs. Also in an MM3 context, I think it would be useful to distinguish between mail hosts and web hosts and domains (all in the general Internet sense) and mail domains and sites (in the MM3/Django/Postorious/Hyperkitty sense). Not sure I fully understand these distinctions yet, but I can take a crack at it. dn

4 years, 10 months

[MM3-users] Re: translating templates

by Guillermo Hernandez (Oldno7)

On 16/2/21 22:47, Mark Sapiro wrote: > On 2/16/21 2:59 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> /usr/local/lib/python3.7/site-packages/mailman # ls templates/es >> domain:admin:notice:new-list.txt list:member:regular:header.txt >> help.txt list:user:action:invite.txt >> list:admin:action:post.txt list:user:action:subscribe.txt >> list:admin:action:subscribe.txt list:user:action:unsubscribe.txt >> list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt >> list:admin:notice:disable.txt list:user:notice:hold.txt >> list:admin:notice:removal.txt list:user:notice:no-more-today.txt >> list:admin:notice:subscribe.txt list:user:notice:post.txt >> list:admin:notice:unrecognized.txt list:user:notice:probe.txt >> list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt >> list:member:digest:header.txt list:user:notice:rejected.txt >> list:member:digest:masthead.txt list:user:notice:warning.txt >> list:member:generic:footer.txt list:user:notice:welcome.txt >> >> But mailman isn't aware of them (I restarted the server). May I have to >> execute some process as "compilemessages" to mailman be capable to use >> them? Now mailman is using the "en" templates for sure. > Does Mailman have permission to search the templates/es directory and > read the templates? They have exactly the same permissions that the other templates directories. > Are there overriding templates in Mailman's > var/templates/ directory? Not at all. > > Are you sure your tests access the templates in a Spanish language > context? Yes, I think so, but it could be that I'm missing something here. I double check this tomorrow as for your answer It seems there is no ulterior process as with messages. Anyway, I could just substitute all the en templates, but it's not the way to maintain language flexibility, you know :) Thanks for your answer P.S.: anyway, I did a merge request in gitlab as you advised. > >

5 years, 8 months

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

by Odhiambo Washington

On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 9:12 AM, Odhiambo Washington wrote: > > On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 7/26/20 3:15 AM, Odhiambo Washington wrote: > >> > >>> There is still some confusion on my part about the directives in the > file > >>> so allow me to seek some clarifications. > >>> > >>> The following are the contents of a file I have created and placed in > my > >>> Apache Includes/ directory. > >>> I was hoping that with it, I can now access http://lists.my.server/mm3 > >> and > >>> get the UI. > >>> > >>> <CUT> > >>> > >>> # Global section > >>> WSGIDaemonProcess mailman-web display-name=mailman-web > >>> maximum-requests=1000 umask=0002 user=mailman3 \ > >>> group=mailman3 > >>> > >> > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > >>> \ > >>> python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > >>> WSGIRestrictSignal Off > >>> > >>> <VirtualHost *:80> > >>> ServerName lists.my.server > >>> ServerAdmin odhiambo(a)gmail.com > >>> > >>> # (I'm not sure that WSGIRestrictSignal Off is required, but it was in > >> the > >>> # provided example so I kept it. I also made changes to > WSGIDaemonProcess > >>> # based on my own mod_wsgi experience elsewhere.) > >>> > >>> ErrorLog /var/log/myserver-error.log > >>> LogLevel debug > >>> > >>> # This goes in the VirtualHost block for the domain. > >>> > >>> # Mailman 3 stuff > >>> Alias /static "/var/spool/mailman-web/static" *<----- Where is this > >>> directory supposed to be and what/who creates it and with what > >> permissions?* > >> > >> > >> It is created/updated by the mailman-post-update script based on CONFDIR > >> and STATIC_DIR. > >> > > > > The fact that I have run the mailman-post-update script and these > > directories aren't created means there is a problem in my setup, yes? > > > If your mailman-post-update script is essentially the same as > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > and it ran successfully, it would have created opt/mailman/mm/static and > populated it. What was the output when you ran it? > > > Yes, I have these files: > > (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* > > -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 > > /opt/mailman/mm/settings.py > > -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 > > /opt/mailman/mm/settings_local.py > > > Is there an empty /opt/mailman/mm/__init__.py file? > No. root@gw:/usr/local/mailman # ls -al /opt/mailman/mm/ total 88 drwxr-xr-x 8 mailman3 wheel 512 Jul 26 14:55 . drwxr-xr-x 6 mailman3 wheel 512 Jul 26 18:38 .. drwxr-xr-x 8 root wheel 512 Jul 25 22:16 .sass-cache drwxr-xr-x 2 mailman3 wheel 512 Jul 26 16:35 __pycache__ drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:42 bin -rw-r--r-- 1 mailman3 wheel 248 Jul 25 14:37 gunicorn.conf -rw-r--r-- 1 mailman3 wheel 266 Jul 26 15:34 gunicorn.conf.py lrwxr-xr-x 1 mailman3 wheel 24 Jul 25 14:39 logs -> /opt/mailman/mm/var/logs -rw-r--r-- 1 mailman3 wheel 370 Jul 25 14:32 mailman-hyperkitty.cfg -rw-r--r-- 1 mailman3 wheel 1291 Jul 26 17:12 mailman.cfg -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 settings.py -rw-r--r-- 1 mailman3 wheel 15805 Jul 26 21:22 settings_local.py drwxr-xr-x 9 mailman3 wheel 512 Jul 25 22:16 static -rw-r--r-- 1 mailman3 wheel 1395 Jul 25 14:35 urls.py drwxr-xr-x 12 mailman3 wheel 512 Jul 26 19:30 var drwxr-xr-x 5 mailman3 wheel 512 Jul 26 17:11 venv -rw-r--r-- 1 mailman3 wheel 1170 Jul 26 11:39 wsgi.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 :) > > > It does `sudo -u $USER ...` so that it runs Mailman as the Mailman user > as it should. Have you set > > USER=mailman3 > in yours? > Yes. However, that also means the /opt/mailman should be owned by mailman3, right? So I wasn't quite mistaken. PS: There is the issue with qcluster, which doesn't seem to have been documented in details from your "experience". I see the configuration file and the init script, but not how to install it, or whether the procedure already installed it. Kindly clarify. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 3 months

[MM3-users] Re: urls.py location on venv install

by Torsten

Am 2026-08-12 07:09, schrieb Mark Sapiro: > On 8/11/26 21:47, Torsten wrote: >> >> The question then would by why pip did not install mailman core 3.3.10 >> but 3.3.9 > > Yes, that's the question. I don't know, but maybe you had an old > version from your Debian package. > > With your venv active, do > ``` > pip install --upgrade mailman > ``` > to get 3.3.10. Tried that already: But it seems that 3.3.10 depends on nntplib >= 3.13 which could not be fetched via pip: 1 location(s) to search for versions of nntplib: * https://pypi.org/simple/nntplib/ Fetching project page and analyzing links: https://pypi.org/simple/nntplib/ Getting page https://pypi.org/simple/nntplib/ Found index url https://pypi.org/simple/ https://pypi.org:443 "GET /simple/nntplib/ HTTP/1.1" 404 13 Could not fetch URL https://pypi.org/simple/nntplib/: 404 Client Error: Not Found for url: https://pypi.org/simple/nntplib/ - skipping Skipping link: not a file: https://pypi.org/simple/nntplib/ Given no hashes to check 0 links for project 'nntplib': discarding no candidates INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. Will try a different candidate, due to conflict: mailman 3.3.10 depends on nntplib; python_version >= "3.13" I have, nevertheless, standard-nntplib 3.13 already installed but there is no nntplib on Pypi. > >>> The database(s) should be in the location(s) pointed to by the >>> [databases] section of mailman.cfg and the DATABASES attribute in >>> settings.py. In an installation per >>> https://docs.mailman3.org/en/latest/install/virtualenv.html these are >>> postgresql databases accessed via the postgresql server. >> >> My installation is rather small, therefore I am using SQLite here. > > OK, but those settings should then point to the SQLite db(s) They do

3 months

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

by Rafael Mora

Hello! Just to let you know, the problem with the email reception was that I was thinking that the email was coming from my hostgator panel, but I was wrong, it's coming from Google (as I use gmail) so that was the problem, I have to open the port 25 to any computer not just my hostgator server.. Have a great day. Bye. On Thu, Aug 3, 2017, 16:25 tlhackque via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 03-Aug-17 17:14, Rafael Mora wrote: > > > > > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users > > (<mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > > escribió: > > > > You've said you're working with labbrands.com <http://labbrands.com > >. > > > > labbrands.com <http://labbrands.com> has address > 192.185.51.89 > > mail.labbrands.com <http://mail.labbrands.com> has address > > 192.185.51.89 > > www.labbrands.com <http://www.labbrands.com> is an alias for > > labbrands.com <http://labbrands.com>. > > > > telnet proves that Exim is running on that IP address. Either you're > > running it, or hostgator is redirecting the SMTP ports. > > > > You added: > > lists.labbrands.com <http://lists.labbrands.com> has address > > 190.145.27.66 > > > > Presumably that's a different machine. > > > > So that now needs an MX record, and a firewall routing. > > > > > > I added the MX record on our hostgator hosting like this: > > image.png > > > > Is it correct??? > > > No. And sending images to the mailing list doesn't get you help. > > You set up lists.labbrands.com as a secondary server, not an independent > mail domain. This will cause you serious grief. > > You need to get some help from a more suitable list. Setting this up is > not mailman-specific, and getting it right is more than a quick note. > > Try the Postfix documentation & mailing lists. > > > > > > > And the SPF > > records ... and spam and virus filters, and all the other stuff > > you need > > to setup an independent, public-facing smtp server. > > > > But at least you won't have to relay. > > > > Good luck. > > > > On 03-Aug-17 16:55, Rafael Mora wrote: > > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > > escribió: > > > > > >> I think you're confused. > > >> > > >> You already have mail.labbrands.com <http://mail.labbrands.com> > > set up as the MX record for > > >> labbrands.com <http://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 <http://mail.labbrands.com> 25 > > >> Trying 192.185.51.89... > > >> Connected to mail.labbrands.com <http://mail.labbrands.com> > > (192.185.51.89). > > >> Escape character is '^]'. > > >> help > > >> 220-gator4137.hostgator.com > > <http://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 <http://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 <mailto:mark@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 <mailto:mark@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 <mailto:mark@msapiro.net>> > > The highway is for gamblers, > > >>>> San Francisco Bay Area, California better use your sense - > > B. Dylan > > >>>> _______________________________________________ > > >>>> Mailman-users mailing list > > >>>> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > > >>>> > > > 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 <mailto:mailman-users@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 <mailto:mailman-users@mailman3.org> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > > > -- > 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

9 years, 3 months

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

by Marco van Tol

Op 29 jan 2024, om 18:29 heeft Mark Sapiro <mark(a)msapiro.net> het volgende geschreven: > On 1/29/24 03:09, Marco van Tol wrote: >> Right now I’m back at the original issue as I see no other solution than to go back to whoosh. >> Thanks! >> Marco van Tol >> Paste: >> ---- >> Indexing 194620 emails >> [ERROR/MainProcess] Failed indexing 156001 - 157000 (retry 5/5): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… (pid 32): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… > > > I'm not sure why the patch you are using doesn't avoid this, but you could try the other patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> instead. If that fails, you could always find the offending message in the database maybe with a query like > ``` > SELECT * FROM hyperkitty_email Where subject LIKE 'http://www.google.com/url?q=\%68\%74\%74%'; > ``` > and modify or delete it - it's probably spam anyway. I tried the other patch, which looked very promising until something that had come in over SMTP some day threw a spanner in the wheels: ``` [ERROR/MainProcess] Failed indexing 287001 - 288000 (retry 5/5): Term too long (> 245): XTEXTº@[åeèúp¢i*h{õimô;]>ò&žôyþiýã#dzç8"¹ë= ;æmyš€vqe.âés:æä>üzúõœ'âú·ž[]kzñ-µ€3æfdñù£8çô<bœkkñ/ãžæjïw¿òþp-ùšã7/'ûvksqé (pid 404): Term too long (> 245): XTEXTº@[ åeèúp¢i*h{õimô;]>ò&žôyþiýã#dzç8"¹ë=;æmyš€vqe.âés:æä>üzúõœ'âú·ž[]kzñ-µ€3æfdñù£8çô<bœkkñ/ãžæjïw¿òþp-ùšã7/' ûvksqé ``` I agree that this is very likely the result of some spam, but the main point is that something that comes in over SMTP shouldn’t cause manual work on the listserver side. I’ll try it with a maximum length of 122 which should never explode into more than 244 bytes, unless I overlook something. I really wish Xapian would have a reliable fix for this. Will keep you posted. Marco van Tol

2 years, 9 months

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

by Jim Popovitch

On Wed, 2021-03-24 at 14:00 -0400, Jim Popovitch via Mailman-users wrote: > On Wed, 2021-03-24 at 10:57 -0700, Mark Sapiro wrote: > > On 3/24/21 7:58 AM, Brian Carpenter wrote: > > > On 3/24/21 9:54 AM, Ralph Weber wrote: > > > > Comments received directly from one of the people who developed the > > > > AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively > > > > established that AWS Mailman is *not* intended to interact with AWS > > > > SES when receiving email messages > > > > > > I don't think there is a Mailman 4 and the person who is marketing his > > > services under that name is sending a confusing message to the public. > > > > Danil Smirnov owns both the mailman3.com and mailman4.com domains. > > Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". > > In response to our request, the following is included at the bottom of > > <https://mailman3.com/>;;: > > > > Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain > > used to coordinate development of the Mailman 3 free software suite. The > > Mailman 3 core developers are not involved with Mailman3.com, and cannot > > answer any questions or provide any support related to its operations. > > If you are looking for resources for development of the Mailman 3 free > > software suite, please see mailman3.org. > > > > Yes, this is all ripe for confusion ... > > Just to add, Danil also owns mailman2.com, and I own (and parked) > mailman2.org. Apologies to this list and Danil who has informed me that mailman2.com is not theirs. This of course means that there is another stakeholder out there somewhere.... ;) -Jim P.

5 years, 7 months

[MM3-users] Re: mailman admin (django) interface does not work anymore after deleting website example.com

by Abhilash Raj

On Sun, Mar 10, 2019, at 9:00 AM, Torge Riedel wrote: > Am 10.03.19 um 16:44 schrieb Mark Sapiro: > > On 3/10/19 8:18 AM, Torge Riedel wrote: > >> I deleted the existing "example.com" and added a new one > >> "lists.mydomain.de". > >> > >> Now the admin (django) interface always gives "An error occurred while > >> processing your request". After one of the first navigation clicks I saw > >> a message that "site with id 1 is missing". > > > > In your Django settings your have > > > > SITE_ID = 1 > > > > which pointed to the example.com domain you deleted. > > > > You need to override this in settings_local.py. Probably > > > > SITE_ID = 2 > > > > but if that doesn't work, try '0' > > > Ah, thank you Mark. That makes a kind of sense. I changed the database > directly to fix it. And renamed example.com to lists.mydomain.de. Now > the error is gone. > > I'm wondering why the initial database set up of postorius (?) adds > "example.com". Is there a way to directly add my domain instead? > Somewhere in settings_local.py? Django does that and there doesn't seem to be a way to override that to something else during initial migration. Or nothing I have found yet. Only way is to edit "example.com" to something you'd like or add another domain entry and change SITE_ID to point o that. > _______________________________________________ > 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, 8 months

[MM3-users] Re: Problem updating mailman

by Brian Carpenter

Mark Sapiro wrote: > On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't > > remember consciously > > installing that because it was never in the guide I followed (which is your > > own writeup). > > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update > > > > '[' False == False ']' > > mkdir -p /opt/mailman/mm/static > > /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > /opt/mailman/mm/bin/django-admin compress > > CommandError: An error occurred during rendering > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > > /bin/sh: sass: not found > > > > You can't just uninstall rubygem-sass. You have to replace it. Here's > one recipe for Ubuntu > cd /usr/local/lib > # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the > # appropriate version. > wget > https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5-... > sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz > sudo chmod -R o-w dart-sass > sudo ln -s dart-sass/sass /usr/local/bin/sass > rm dart-sass-1.32.5-linux-x64.tar.gz > Then you should see the command > sass --version > prints > 1.32.5 > Then, because dart-sass doesn't recognize the short form -t option for > --style, you have to edit your settings(_local).py and change > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > to > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass --style compressed {infile} {outfile}'), > ('text/x-sass', 'sass --style compressed {infile} {outfile}'), > ) I had to do a new installation of Mailman 3 with Postorius/Hyperkitty today and these directions were very helpful. Thank you, Mark.

5 years, 9 months

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

by Mark

On 2024-11-18 01:38, Mark Sapiro wrote: > 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. It's just the one list that is using French. Others are in English I've edited the order of the middleware settings in this file ... /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/settings/base.py I reordered as below, restarted everything but no joy :-( ... at Line 76 ... MIDDLEWARE = ( 'allauth.account.middleware.AccountMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.middleware.common.CommonMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ... I'm thinking this is not the file I'm looking for. Apologies for my cluelessness here.

1 year, 11 months

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gilles Filippini

Mark Sapiro a écrit le 23/04/2020 à 19:02 : > On 4/23/20 2:48 AM, Gelpi Andrea wrote: >> >> I saw the change in the file. >> >> As I'm not a programmer How can I test your fix? >> >> My system was installed via Debian 10 stable repository. >> >> I upgrade with testing repository postorius, django and mailmanclinet >> >> Postorius V 1.3.2 >> Django V. 2.2.12 >> Django filters V 2.1.0 >> Djanog mailman V 1.3.2 >> mailmanclient V 3.3.0 > > > I don't know where the Debian package puts things, but you have to find > the location of postorius/views/list.py. Something like > > locate views/list.py On debian this file is part of the python3-django-postorius package, and is installed here: /usr/lib/python3/dist-packages/postorius/views/list.py > > should find it. Then you need to download > <https://gitlab.com/mailman/postorius/-/merge_requests/500.diff> and > edit it to remove the first 15 lines so the first remaining line is the > > diff --git a/src/postorius/views/list.py b/src/postorius/views/list.py > > line. Then make a backup copy of postorius/views/list.py and run the command > > patch postorius/views/list.py path/to/500.diff > > where postorius/views/list.py is actually the full path to > postorius/views/list.py and 500.diff is the edited file you downloaded. You'll have also to remove the compiled files from the __pycache__ directory: $ sudo rm /usr/lib/python3/dist-packages/postorius/views/__pycache__/list.cpython-*.pyc > Then restart uWSGI. If anything goes wrong, restore your backup copy of > postorius/views/list.py and restart uWSGI. The best way to restore is to force the re-installation of the package: $ sudo apt-get install --reinstall python3-django-postorius It will take care of the compilation part. _g.

6 years, 6 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Tue, Dec 27, 2022 at 11:23 AM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > El 26/12/22 a las 23:57, Mark Sapiro escribió: > > ... > >> I don't want to put more noise in the list. But I'm confused because > >> I always updated via pip the apache mod_wsgi thinking is was needed > >> for my configuration. If it is not, I will stop updating it. > > > > Based on the above you ARE using Apache mod_wsgi and if you are still > > also running uwsgi as > > > > /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & > > > > that is unnecessary. > > It clarifies a pair of things. Thanks a lot. > > I'll try deactivating that in one of my servers (the "quieter" one) and > see how it goes. > > Again, thanks for your kind support. > I have actually deactivated mine, and life is still good with my MM3. And just so that my mind is in the clear, there are three ways of getting the full MM3 functionality, viz: 1. Mailman core, Django's cluster, and Gunicorn 2. Mailman core, Django's cluster, and uWSGI 3. Mailman core, Django's cluster, and mod_wsgi And something that has not been quite clear to me: What is the purpose of Django's cluster in all this? I am asking because on my FreeBSD server, I usually see not less than 30 PIDs for: /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/django-admin qcluster --pythonpath /opt/mailman/mm/ --settings settings (python3.9) And there is a time I found it having 240 PIDs. Would there be a problem if I limit the number of workers to "8"? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

[MM3-users] Re: Setting up Admin Account

by Stephen J. Turnbull

Pierre Abbat writes: > On Friday, November 17, 2017 1:51:15 PM EST Simon Hanna wrote: > > You are not supposed to create the directory mailman-suite_project but > > clone the mailman-suite project from gitlab and use it. > > None of the manage.py commands listed by your search are the right ones. > > The correct one is the one included in the repository of mailman-suite > > It appears that setting up Mailman 3 requires knowledge of Django, which I > don't have. I'm going to try something else. You're welcome to do so since you know your needs better than we do, but please allow me to advise you that running Mailman 3 in most cases doesn't require knowledge of Django as long as (1) you follow the instructions *exactly*, and of course (2) assuming those instructions are correct. Mailman 3 being just on the edge of becoming the industry standard for mailing list managers, yes, assumption (2) is occasionally violated. In my experience, (1) is a more frequent source of user troubles. Either way, we[1] are one heck of a lot faster at responding than most commercial and open source products when users have trouble. And we do have reason to lay claim to "industry standard". Footnotes: [1] By "we" I really mean Mark Sapiro, Abhilash Raj, and off and on Simon Hanna. It's rare that it takes as much as 24 hours to get attention from one of them, and if Mark can handle it, usually you get an immediate solution. I haven't been able to keep up for months, but I hope to get back into the rotation soonish (in the new year). -- Associate Professor Division of Policy and Planning Science http://turnbull/sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

8 years, 11 months

[MM3-users] Bug in email.generator:_handle_text? [was: store/export existing Mailman lists ...]

by Stephen J. Turnbull

Oops, premature send. I did grep through the whole mailman core code base for "del", and didn't come up with anything that looks like it would delete fields like Content-Type and Message-ID (assuming the default for anonymous_list_keep_headers, I wish I had thought to ask about that, but who changes it?) I assumed Content-Type is modified by direct assignment in handlers that delete parts or transform them to a different MIME type. I wonder if his Python is old enough to not recognize negated regexps? That should be logged in errors. Or (as you guessed), the '(?!x-)' regexp (or the whole content of anonymous_list_keep_headers) has been removed? Stephen J. Turnbull writes: > Mark Sapiro writes: > > > This apparently confuses the Python email package so that the > > get_payload() method returns a list of strings rather than a list of > > message objects. > > Yes, I got that far too. I'm guessing that in the absence of a > Content-Type, which then *should* default to text/plain, the email > package goes ahead and detects the MIME headers anyway (although I > don't think it should do that) and breaks the message into MIME > parts. I would think we'd raise an Exception here. > > If there's a reason for the email package to do that detection > (*shrug*, it seems to work), then the dispatching in _handle_text > should be done on the Python type rather than the MIME Content-Type. > > I forget exactly how the code is structured, the relevant dispatching > may be in _dispatch or in _dispatch_meth. > > Steve > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 1 month

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Henrik Rasmussen

Abhilash Raj wrote: > On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: > > each other, but Postfix is trying to deliver mail via lmtp to > > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > > listening on port 8024. Either that is not the case or that port is not > > exposed to Postfix on IP 172.19.199.2. > > Right, that is what I was wondering, you verify that by using telnet > on the specified IP and Port (172.19.199.2:8024). Yes, the postfix container listens on 172.19.199.2:8024 ``` [root@postfix /]# nc -v 172.19.199.2 8024 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.19.199.2:8024. 220 mailman-core GNU Mailman LMTP runner 2.0 ``` > docker-compose ps lists all the running containers, do you see all > the containers running? That also seem to be okay ``` [root@lstapp01pl ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bddc80799b8c maxking/mailman-web:0.2 "docker-entrypoint.sh" 16 hours ago Up 16 hours 8000/tcp, 8080/tcp mailman-web be098b18aeca maxking/mailman-core:0.2 "docker-entrypoint.sh" 16 hours ago Up 16 hours 8001/tcp, 8024/tcp mailman-core c47fd8ccf19d postgres:9.6 "docker-entrypoint.sh" 16 hours ago Up 16 hours 5432/tcp mailman_database_1 699264501acd mailman3-mime_htmlizer "container-entrypoint" 16 hours ago Up 16 hours 8080/tcp postmime 90f381a74709 mailman3-postfix:v1.1 "./entrypoint.sh" 16 hours ago Up 16 hours 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp, 0.0.0.0:26->25/tcp postfix ``` And netstat in the mailman-core container shows: ``` Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 172.19.199.2:8024 0.0.0.0:* LISTEN` ``` > You mentioned that Mailman is not receiving enough emails, do you get > any emails from Mailman? I am trying to see if this is a perf problem > or if Mailman's LMTP isn't reachable at all. Mailman do send out mails like when someone signs up for an account. Thanks to both.

7 years, 1 month

[MM3-users] Re: templates

by Christian

Okay I sent a test message this morning and subscribers are reporting they did not receive it. The smtp.log shows 'smtp to degrowcali(a)lists.ccalternatives.org for 25 recips, completed in 3276.275292634964 seconds' (see below) I alone received it however and it is listed in the archive. Below is the excerpt from smtp.log. Two of my 5 lists are exhibiting this behavior, while 2 other lists are working normally. Please advise. Thank you. root@zarathustra:/opt/mailman/mm/var/logs# vi smtp.log May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) recip: degrowcali-bounces+vortexanthony=hotmail.com(a)lists.ccalternatives.org May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) >> b'DATA' May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) >> b'QUIT' May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) connection lost May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) Connection lost during _handle_client() May 05 08:11:35 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:11:35 2023 (768) Peer: ('127.0.0.1', 60312) May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) handling connection May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'MAIL FROM:<> SIZE=9885 BODY=8BITMIME' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) sender: <> May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'RCPT TO:<degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org>' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) recip: degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'DATA' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'QUIT' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) connection lost May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) Connection lost during _handle_client() May 05 08:13:46 2023 (771) <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> smtp to degrowcali(a)lists.ccalternatives.org for 25 recips, completed in 3276.275292634964 seconds May 05 08:13:46 2023 (771) <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> post to degrowcali(a)lists.ccalternatives.org from christian(a)degrowthcalifornia.org, 5012 bytes May 05 08:13:46 2023 (771) <168329874052.765.12737190159456781981(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.011698722839355469 seconds May 05 08:13:46 2023 (771) <168329874052.765.12737190159456781981(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalternat ives.org, 11445 bytes May 05 08:13:46 2023 (771) <168329886073.765.17844938860507947692(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.00799560546875 seconds May 05 08:13:46 2023 (771) <168329886073.765.17844938860507947692(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+62749dfe16f9d39e2cd0c3e94754723efbe8169d(a)lists.ccalternat ives.org, 11400 bytes May 05 08:13:46 2023 (771) <168329958151.765.3625387421642934590(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.008965730667114258 seconds May 05 08:13:46 2023 (771) <168329958151.765.3625387421642934590(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalternat ives.org, 11426 bytes May 05 08:13:46 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:13:46 2023 (768) Peer: ('127.0.0.1', 39046) May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) handling connection May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'MAIL FROM:<> SIZE=15076 BODY=8BITMIME' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) sender: <> May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'RCPT TO:<degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalte rnatives.org>' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) recip: degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalternat ives.org May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'DATA' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'QUIT' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) connection lost May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) Connection lost during _handle_client() May 05 08:13:46 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:13:46 2023 (768) Peer: ('127.0.0.1', 39050) May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) handling connection May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'MAIL FROM:<> SIZE=15049 BODY=8BITMIME' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) sender: <> May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'RCPT TO:<degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalte rnatives.org>' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) recip: degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalternat ives.org May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'DATA' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'QUIT' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) connection lost -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, May 4, 2023 12:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/4/23 11:15, Christian via Mailman-users wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists > have templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > mailto:var/templates/lists/redlatinleg@lists.ccalternatives.org/ derectory > that Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in > Mailman's var/templates (as I stated, I do not even lave a 'lists' > subdirectory under Mailman's var/templates). My subscribers are not > receiving message distributions from my lists, even while some of them > are listed in the archives. See the original thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U HWOG6S57FM2SIQWHEPWM3CDUSAMLOOP/ (which you hijacked about 4 messages in) and particularly the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ NZ7G3JMYXFTQNVJ2DYGJ6PETEQT55SKB/ Without further information, I can't say more than that. -- Mark Sapiro <mailto:mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailto:mailman-users@mailman3.org To unsubscribe send an email to mailto:mailman-users-leave@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/ GJNYZK3DK4UZYAILV7JZ62PPVPDPKNOZ/ This message sent to mailto:csa@web-analysts.net

3 years, 6 months

[MM3-users] Re: Speed up importing mailman2 lists

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/19/25 06:08, t.maintz(a)fz-juelich.de wrote: > > We are currently planning to migrate from mailman2 to mailman3 as > > a container, have around 1500 lists and would like to complete > > the migration ideally in a few hours. I've done two massive migrations in the last year. In the first (~20k lists), the lists were down for maybe two hours, but it took 22 hours for HyperKitty to populate, mostly in Xapian indexing we realized in post-mortem analysis. In the second (~1k lists), no perceptible downtime because they have their own bespoke archiver that has a list-manager-agnostic API. The trick to zero delivery downtime is that you can configure your MTA to route to Mailman 3 if the list exists there, if not route to Mailman 2 if the list exists there, and if not continue to any lower priority routes. It worked as designed (mops sweat off brow ;-). We did take Postorius and the Mailman 2 management CGIs and email command addresses offline for the duration (3 hours in the first case, 30 mminutes in the second). This is sraightforward if Mailman 2 and Mailman 3 are running on the same host. Life is more complex if you're spinning up Mailman 3 in a separate node but it should be possible. I think if you're migrating to HyperKitty you can speed up the migration by shutting off indexing, and doing that later at the cost of confusing people who expect the lists to be indexed. I'm not sure if it's possible to migrate the archives concurrently with accepting new posts, or maybe to migrate archives in advance and backfill any posts that arrive during the list migration. And there's no reason why you can't leave the legacy Mailman 2 archives up for browsing as a backup for as long as needed. Steve

1 year, 8 months

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

by Henrik Rasmussen

Mark Sapiro wrote: > I don't understand the question? Are you asking why the log contains > "invalid FilterAction: discard. Treating as discard"? If so, that's a No, that was just log messages I thought would help explain the problem. > If you are asking why the message is empty after filtering and > discarded, It is presumably because it is a text/html message as opposed > to a multipart/alternative message with text/plain and text/html > alternative parts. The Content-Type of the mail sent to the list is multipart/mixed From: SENDER <sender(a)senderdep.example.com> To: "LISTNAME(a)lists.example.com" <LISTNAME(a)lists.example.com> Subject: =?utf-8?B?QW50cm9wb2xvZ2VyIGkgcHJha3NpczogVGlsbWVsZGluZyDDpWJlbg==?= Thread-Topic: =?utf-8?B?QW50cm9wb2xvZ2VyIGkgcHJha3NpczogVGlsbWVsZGluZyDDpWJlbg==?= Thread-Index: AdT/QIb18JA+6hcSTYycFCI+5NuYoQEwPZ/Q Date: Mon, 6 May 2019 13:53:23 +0200 Message-ID: <250E794B36C1E646AF3D81E1F15348C79DA8CA83(a)P2KITMBX06WC03.unicph.domain> Content-Language: en-US X-MS-Has-Attach: yes X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: Content-Type: multipart/mixed; boundary="_006_250E794B36C1E646AF3D81E1F15348C79DA8CA83P2KITMBX06WC03u_" MIME-Version: 1.0 > There are list attributes filter_types and pass_types (also > filter_extensions and pass_extensions, but those probably aren't My Python isn't that great, but this looks like i'm missing something >>> m.filter_content True >>> m.pass_types <generator object pass_types at 0x7f66d407bba0> >>> m.filter_extensions <generator object filter_extensions at 0x7f66d407bdb0> m.pass_extensions <generator object pass_extensions at 0x7f66d407be08> > Presumably, the combination of filter_types and pass_types is not > allowing text/html. I am thinking that as the "Filter content" (postorius) refers to "the settings below", this setting is needed in case list admin wants an explicit reply-to address or change other switches in Alter Messages. But this shouldn't affect the content, even it is text/html, I think, at least not emptying the mail, I think. > You need to examine these settings in mailman shell, e.g. > > list(m.pass_types) >>> list(m.pass_types) ['multipart/mixed', 'multipart/alternative', 'text/plain'] -- Henrik Rasmussen

7 years, 6 months

[MM3-users] Re: MM3 on debian - redirect problem

by Gelpi Andrea

Il 28/04/20 18:31, Mark Sapiro ha scritto: > On 4/27/20 8:17 AM, Gelpi Andrea wrote: >> Hi, >> on a debian10 I have mm3 installed via apt-get >> >> apt-get install mailman3-full >> dpkg-reconfigure mailman3 >> dpkg-reconfigure mailman3-web >> >> I have this minor issue >> >> https://webserver/mailman3 redirects to >> http://webserver/mailman/postorius/lists/ >> >> that doesn't exist. >> >> The same problem form django admin page to return to lists >> >> https://website/mailman3/admin/sites/site >> >> In the upper right corner I have a link to https://webserver/mailman3 >> that redirects to https://mailman/postorius/lists/ >> >> I searched for a redirect but without success. > > > The redirection must be a web server issue. > > There is a urls.py file probably in the same directory as your django > settings - probably /usr/share/mailman3-web/urls.py in your case. > > You can make a URL like http://webserver/mailman/postorius/lists/ work > by adding > > url(r'^mailman/postorius/', include('postorius.urls')), > > to the urlpatterns list in the urls.py file. > > The problem seems to be inside the uwsgi proxy. Also django admin web interface has the some problem. I add /mailman in the apache mailman config installed by the debian package. --------------------------------------- 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/ ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> ------------------------------------- -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

6 years, 6 months

[MM3-users] Re: Unknown templates being used

by Tom Stoddard

On 2/14/2021 1:31 PM, Mark Sapiro wrote: > That message is not built from a template. It comas from the `mailman > notify` command which currently says > ```> def _send_notice(mlist, count, detail): >> """Creates and sends the notice to the list administrators.""" >> subject = _('The {} list has {} moderation requests waiting.').format( >> mlist.fqdn_listname, count) >> # XXX This should be a template. >> text = _("""The {} list has {} moderation requests waiting. > ``` > I.e., we know it should be a template, but it currently isn't. That's fine but it doesn't explain why I have received messages that were built by a template for some subscription requests. In other words, why is there a template being used in some instances and on others a "mailman notify command" is being used? Are there different methods for people to use to request a subscription? Please understand that I'm new to mailman 3 and don't have knowledge of its source code. From reading some of the messages that have been sent by this list, I assume it's written in python, which is a language I have not year learned. I'm asking this because I help to administer several different lists and there are some other moderators who have very limited technical skills. I try to help them the best I can, which is why I'm trying to understand why these messages seem to differ so that I can explain it to others. By the way, Brian at EMWD has been extremely helpful to me already and, as he stated, he informed me that this is an issue with Mailman 3 so I thought I'd try getting the answer directly from this group. Thank you for your time. I do recognize and appreciate the time and effort that goes into creating and maintaining open source software.

5 years, 8 months

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

by Allan Hansen

Thank you, Mark. I have Postorius Version 1.3.4 I see no 'Users' in Postorius, but I do see it in Django. I'll assume that my Postorius is out of date and will take steps to update it. Yours, Allan On 1/11/22, 10:38 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 1/11/22 9:24 AM, Allan Hansen wrote: > Thank youi, Stephen. > > Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. > The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. > > I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. > Nevertheless, the new subscriptions still show up as 'B'. A user has a user record and one or more address records. Each of these has a display name. Removing users from lists does not remove these records. If you have recent Postorius, you should have a `users` item at the top of Postorius pages. Go there, find the user and click "Manage". You can change Display Name there. Otherwise, in `mailman shell` for example ``` >>> usr = getUtility(IUserManager).get_user('user(a)example.com') >>> usr.display_name = 'First Last' >>> for adr in usr.addresses: ... adr.display_name = 'First Last' ... >>> commit() ``` -- 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, 10 months

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

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [231110 23:54]: > On 11/10/23 12:39, Andreas Barth wrote: > > > >is there some way to find an ID to follow an email through mailman? In > >the exim logfile there is only something like C="250 Ok" (whereas in > >mails sent to another exim there is something like C="250 OK id=…"). > >(What I sometimes need to do is to follow an mail whether it is sent > >through mailman and to where.) > > Every message should have a unique Message-ID: header. According to > my reading of https://www.exim.org/exim-html-current/doc/html/spec_html/ch-log_files.html > Exim should create a => log entry with an id= field containing the > Message-ID when the message is received for delivery to Mailman and > another similar entry when the message is received from Mailman for > delivery to one or more list members. There is the message-id as part of the mail itself, and set by the user. That one is not unique, e.g. if a mail is bounced to the list. Exim has an internal id, and that is also part of the log (also if a mail is delivered to a remote mailserver, the id there is logged). This works fine. However, mailman doesn't have an internal id I can use to follow the message (or at least, it doesn't transfer one to exim upon delivery). I can indeed use the user set message id for following mail. However, I would prefer some internal id, and also to have logged the IDs exim (or probably any other MTA) transmits upon delivering the mails when handing the mails over to the MTA again. (Probably in some format as "mailman-ID recepient MTA-id" so that it's easy for me to grep for message if a user complains.) Regards, Andi

3 years

[MM3-users] Re: Auth question

by David Krantz

On Thu, Mar 30, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > 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) > I tried to upgrade today. The result is a broken install which fails when trying to upgrade the database. $> ./bin/mailman-post-update [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() django.db.utils.IntegrityError: update or delete on table "auth_user" violates foreign key constraint "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on table "social_auth_usersocialauth" DETAIL: Key (id)=(3) is still referenced from table "social_auth_usersocialauth". I have tried to drop and recreate the databases but I get the above result anyway. The description in https://wiki.list.org/DOC/Mailman%203%20installation%20experience is very hazy. The process of symlinking in libraries is fiddly to say the least. I get mailman to start but not any web interface. I have not tested mailman so if it works rather than just start I do not know. There is a description for a clean install for development at http://docs.mailman3.org/en/latest/devsetup.html, but I suspect that it isn't usable for anything other than development. I have read it parallell to try to interpret the installation experience description which in turn describes more of what I am trying to do. No luck though. regards // David

9 years, 7 months

[MM3-users] Re: mailman-cli tools

by Dmitry Makovey

On 09/27/2017 10:20 AM, Abhilash Raj wrote: > On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: >> On 09/27/2017 08:26 AM, Dmitry Makovey wrote: >>> On 09/27/2017 08:25 AM, Dmitry Makovey wrote: >>>> I've come across mailman-cli docs: >>>> >>>> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… >>>> > > This is basically one of our GSoC projects which hasn't yet been merged > with MailmanClient. It uses the REST API to to provide a command line > client for Mailman, while there hasn't been any in-compatible changes in > API since this project was finished, I am not sure about the current > status of it. > >>>> yet I cannot figure out what's the official source for the installation. > > Official source for MailmanClient is at gitlab.com/mailman/mailmanclient > and it doesn't have a CLI, the Github project you linked to says right > on the top that it is not official project (Thanks for that Rajeev!). I did see that, thus I was asking the question here. > Also, I would say not to use this client to remotely access Mailman, the > REST API is not meant to be exposed over internet (unless you have a VPN > or other sort of setup to securely access the box remotely). > in my case - I need to use REST API since we're deploying with docker and pieces that need to integrate with mailman commands now live in a different container (and very likely on a different machine). I do need to be able to execute commands remotely - I can handle securing of that connection, but it is not an option for me to run "fat" docker containers thus the only interconnect is via sockets (either UNIX or TCP). -- Sr System and DevOps Engineer SoM IRT

9 years, 1 month

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-30 16:25, Mark Sapiro wrote: > Jan Eden wrote: > > I tried setting permissions on /opt/mailman/fulltext_index to 777 > > temporarily, but the issue remained (as expected). It occurs in the > > Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > > > if self.use_file_storage and not os.path.exists(self.path): > > > > > > os.makedirs(self.path) > > > > > > where self.path is referenced, which is defined in line 110 (as part of > > the __init__ function): > > > def __init__(self, connection_alias, **connection_options): > > > super().__init__(connection_alias, **connection_options) > > > self.setup_complete = False > > > self.use_file_storage = True > > > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > > > self.path = connection_options.get("PATH") > > > > > > Unfortunately, I cannot see where the PATH key for connection_options is > > defined. > > > It is defined in the HAYSTACK_CONNECTIONS dictionary in your Django settings. The dictionary contains the following: > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': "fulltext_index", > }, > } Changing the PATH value to a full path (/opt/mailman/fulltext_index) and restarting mailman-web generates a different error: > ERROR 2022-11-30 16:38:37,953 1028315 django.request Internal Server Error: /archives/list/testing@lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner > response = get_response(request) > File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner > return func(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 454, in reattach_suggest > sugg_thread = msg.object.thread > AttributeError: 'NoneType' object has no attribute 'thread' - Jan

3 years, 11 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 0:44): > On 4/6/25 14:40, via Mailman-users wrote: > >> Is your login a member of the list? > > > > It's supposed to be – when I click „Manage subscription” in the very > same thread, it reveals that I'm subscribed. This is why I can't subscribe > again. Yet I still can't post from HyperKitty, however I can by e-mail. > > > > However, when I checked the member list, I also found my address as a > „nonmember” (besides being listed as „member” too). I removed myself as > „nonmember”, but I still can't post to the list from HyperKitty. > > > What response do you get when you click `reply` on a message? and what > when you click `Start a new thread`. Do you get an error immediately or > do you get a composition dialog and only get an error when you click > `Send`. What do the errors look like? > I get a composition dialog and can type my message, but when I click send, I get the error message: „This list is moderated, please subscribe to it before posting.”. Upon reply, a red rectangle appears to enclose this message. Upon trying to create a new thread, a white page loads which only contains this error message. What do you see in Django's logs when you do this? > I don't know where to look – I don't see anything outstanding, only a few HTTP requests appear in mailman.log on mailman side and uwsgi.log on web side. None of these indicate any error. What HyperKitty version is this and is it installed from PyPI or is it a > downstream package? Version 1.3.12. It is installed through pip with the virtualenv method.

1 year, 7 months

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

by Franklin Weng

Hi Mark, Great thanks to you and everyone in this discussion. Mark Sapiro <mark(a)msapiro.net> 於 2019年10月30日週三 23:13 寫道： > On 10/30/19 12:52 AM, Franklin Weng wrote: > > > > If I use > > > > base_url: https://lists.slat.org/mailman3/hyperkitty/ > > > > The log became > > > > Oct 30 15:25:50 2019 (6256) HyperKitty failure on > > https://lists.slat.org/mailman3/hyperkitty/api/mailman/urls: > > <html><title>Auth required</title><body> > > > > <h1>Authorization Required</h1> > > </body></html> (401) > > > > In my mailman-web.py: > > > > MAILMAN_ARCHIVER_KEY = 'my-key,same as in mailman-hyperkitty.cfg' > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > > > Not sure what to change here. > > > There have been other reports of authorization failures even though the > keys match. See the last few posts at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > >. > The solution there was to change both the api_key setting in > /etc/mailman3/mailman-hyperkitty.cfg and the MAILMAN_ARCHIVER_KEY > setting in /etc/mailman3/mailman-web.py to new values. > I didn't change the key. When I follow the thread and print the keys getting from web and in the settings I found that one with single quote and the other not. In the mailman-web.py the value of MAILMAN_ARCHIVER_KEY should be single quoted, **but** the api_key in [general] SHOULD NOT single quoted. Therefore I set my hyperkitty base URL to https://lists.slat.org/mailman's/hyperkitty/ and removed the quote in mailman-hyperkitty.cfg it finally works. Maybe adding a comment to explain it a bit more would help later people not to step on the mine again. Thanks for your help! Regards, Franklin

7 years

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

by Torge Riedel

Am 02.02.19 um 19:06 schrieb Mark Sapiro: > On 2/2/19 5:31 AM, Torge Riedel wrote: >> A call to >> >> mysql -umailman -p >> >> successfully uses the socket on the machine and logs in. > > Yet you haven't specified -S or --socket > > >> I tried >> >> mysql+pymysql://mailman:mailmanpass@127.0.0.1/mailman3?charset=utf8&use_unicode=1&unix_socket=/var/run/mysqld/mysqld.sock >> >> >> as the connection string but it says that mysql server is not available. >> Which is the same if remove the "unix_socket" parameter. I have found >> this parameter when searching the net, but I'm not sure if it is supported. > > I think it should be, but the actual connection is via the the > sqlalchemy create_engine() function. It appears this should be passed to > the pymysql Connection() function per > <https://docs.sqlalchemy.org/en/rel_1_2/core/engines.html#custom-dbapi-args> > > What happens if in a Python 3 session, you do > > from pymysql import connect > conn = connect('127.0.0.1', > user='mailman', > password='mailmanpass', > database='mailman3', > charset='utf8', > use_unicode=1, > unix_socket='/var/run/mysqld/mysqld.sock') > > As I understand it, that's what sqlalchemy should be doing with your > database url. In my testing, the above works with or without the > unix_socket= argument, so I suspect something else is wrong in your case. > Hi, thanks a lot for your answer. Yes, sounds valid that something else is (or was) wrong in my environment. I'm new to docker containers and might have overseen something. I now managed it a different way: I used rinetd on the host to redirect connections from docker host ip of a bridged network to 127.0.0.1 to make MySQL accessible in the docker container. This works and avoids mapping the mysqld.sock file into the container. Thanks again Torge

7 years, 9 months

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

by William Oliver

On Sun, 2021-12-26 at 16:47 -0800, Mark Sapiro wrote: > On 12/26/21 3:06 PM, William Oliver wrote: > > > > When running mailman3, do I need to set up a completely different > > virtual domain for it to run in? > > No. > > > > My "real" domain name is > > libertyfp.org, and I'm trying to make mailman work on that domain, > > e.g. > > "testlist(a)libertyfp.org." I'm starting to get the idea that I need > > to > > stick a completely different domain in there for the mailinglist. > > No. > > DNS or anywhere outside your server. > > Have you actually set an alias domain in Postorius for the > libertyfp.org > domain. It doesn't matter what name it is as long as it isn't > a real domain. A good choice is x.libertyfp.org. Have you set that > or > things like > > testlist(a)libertyfp.org testlist(a)x.libertyfp.org > testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org > testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org > ... [snip] Ah. I misunderstood you. I thought you meant that I had to tweak *postfix* to get this done. It's not that you weren't clear, it's that when I read the mailman3 instructions, I got the impression that *mailman* would set the alias domain automatically, so I was dead set on munging postfix. This makes more sense, and I can back out of some of the changes I made in postfix, which for the last couple of rounds was mostly flailing about randomly -- I've heard that's often not a good admin strategy. So.. if I need to do it myself, can you point me to what file I need to create/modify in the /opt/mailman/mm tree to set up the alias? Thanks! billo

4 years, 10 months

[MM3-users] Re: Subscription Request asking for Confirmation instead of Moderation

by Henry Hartley

> -----Original Message----- > From: Stephen J. Turnbull <steve(a)turnbull.jp> > Sent: Friday, August 29, 2025 03:36 > > Last I looked, *moderators* don't have access to Mass Subscribe, only > *owners* do. Has that changed? I don't think this would have any effect on the > misqueueing issue, however. Our moderators are also owners so that's not a problem. > Hm. Do you have a reason for sending email from Drupal to Mailman through > Microsoft servers? Note: "yes" is a sufficient answer, I have no need to know > more. If it's just an accident, you can ensure that Drupal's mail will reach > Mailman by configuring it for local delivery, which you can make safe from > spam filters and DMARC processing. > > I don't think this would resolve the misqueueing issue, though. The reason for the Microsoft server being involved is that's the way our Systems folks insisted we set it up. So, main to our particular domain goes through that and is routed to our server. In other words, "yes". > > We definitely could rewrite our code to use the REST API[...]. But > maybe we > need to do that sooner rather than later. > > This should resolve the misqueueing issue. It's not that hard. In fact, it might be > easier that doing it by email (except that of course you already have the code for > doing it by email). The reason we didn't use the REST API is that we had code that worked (or at least that we thought worked). I've recommended to the site maintainers that they update their code to use the API and we'll deal with these things manually until that's done. Thank you and Mark Sapiro for your responses. -- Henry Hartley Westat RB 2151

1 year, 2 months

[MM3-users] Re: Can disabled users enable themself?

by Stephen J. Turnbull

Mark Sapiro writes: > On 7/4/26 6:13 AM, Stephen J. Turnbull wrote: > > On the other hand, if Mailman sends mail to your user for > > any reason, and it does *not* bounce, they will be re-enabled > > automatically. > > I don't think this is correct unless you have some local > modification to do this. Thank you for the correction. Likely I misremembered that it would be re-enabled. I guess the stock process is the bounce count gets reset to zero after a time period with no bounces, but this isn't immediate and doesn't reenable. When the bounce count is reset, if it's "disabled by bounce", we could then re-enable. That's like a two-line change. Perhaps with a more complex algorithm (eg, store an indicator of that Address's recent bounce history in the database, and re-disable more quickly if it has a history of bouncing recently). A complex algorithm would be more invasive (database schema addition) and I'm not suggesting that yet. > Even then, how would it work? A bounce might come from downstream > MTA and possibly not for days. Nothing that depends on bounce by DSN is reliable though. Heck, you can't even be sure that that status "250 OK" isn't somebody treating you like a spammer and eating your mail. And if you're heavy on Gmail and Yahoo users, most bounces are likely to come very quickly and reliably. It might work pretty well for some lists and horribly for others. I guess we'd have to do more parsing of the local MTA's DSNs in that case, though. Hmmm. At least we know the stock behavior of the four we support. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 1 week

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Thu, 21 Mar 2019 16:58:45 -0000, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Thu, Mar 21, 2019, at 8:47 AM, Malcolm Austen wrote: >> On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> >> wrote: >> >> > However, this is apparently not relevant because both the Member and >> > Non-Member actions are Hold. Thus, the post should be held unless it >> has >> > an Approved: header with the list's moderator_password attribute if >> > there is one, or it matches a Header filter rule with an accept >> action. >> >> At the risk of getting this really wrong - I have only limited MM3 >> knowledge - I will ask what is, I fancy, a closely related question ... >> >> My only experience of MM3 is with Ancestry's 'RootsWeb' installation. >> From >> the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't >> find >> anything to identify Postorius which is the only interface I have to the >> system. >> >> From symptoms seen and described by others, I have deduced that the >> Postorius admin-per-user moderation options of "Default processing" and >> "List default" mean that a user may be set (by default on the rootsweb >> system!) to use the system default moderation settings rather than the >> list default settings. > > "Default Processing" means the default pipeline defined in Thanks, I will do some (more!) reading. > List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This > pipeline is > system wide and is defined in source code, so it can't be customized by > site administrator. Unfortunately, that is not available to list-owners on the system concerned. Ancestry must have removed it. Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

7 years, 7 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 16:44 -0800, Mark Sapiro escribió: > On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > > very significant date for me (it is my wedding anniversary) and I'm 90% > > sure that I dedicated time to Weblate after that date... > > With respect to Mailman core, all I'm doing is downloading the .po for > Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po > from the Mailman core 3.3.3 package on PyPI and they are identical. > > If there are translated strings on weblate that are different from that, > they don't show up in the downloaded > <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>;. And you are very right and I have fallen as a newbee ... and first of all I apologise for the noise. I've been doing diffs with files downloaded from Weblate and those installed on the server by pip. As I should have done from the start. Mailman core and hyperkitty show no differences. Postorius shows a bunch and django_mailman3 just a couple. I leave for others a more detailed check of the strings between downloaded .po files and Weblate online strings, it's too late here. > > And I too want to help. It would be a help to me if you can give me > examples of specific strings whose weblate translation differs from > what's in the distributed .po files. And you have helped me, making me thing twice and stop moaning and going for the facts. Apologetic-thankful-big-mouth-shut-ly, Victoriano. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 9 months

[MM3-users] Re: Disabled by bounce

by Stephen J. Turnbull

On 2/2/23 04:54, Danil Smirnov wrote: > > Isn't this a bug? Eye of the beholder. I will argue it's a doc bug. > > We are now showing users' bounce scores on the Members > > page and this would be misleading. If you mean the member's own page, yes, confusion is a problem. If you mean it's the Members page that the admins see, documentation and education is the answer, IMO. > > Is it difficult from internals > > perspective to have the bounce score reset immediately? Mark Sapiro writes: > Yes, it is not difficult, but it's a lot of processing. It would require > something like a task runner task to periodically look at each row in > the member table and if the bounce score is > 0, find the associated > list's bounce_info_stale_after and if last_bounce_received + > bounce_info_stale_after < now, reset the score. Aside: In programming, all problems are solved by another level of indirection. In databases, all problems are solved by another index. :-) You'd still need a runner, but it would be a simple "update these rows to zero", I guess. About the education and documentation for subscribers: I would argue that we can document the bounce score as a "recent highwater mark", since delivery isn't disabled yet. That's useful information for those with ears to hear it. That is, if you see "0" 95% of the time, occasionally "1", and today it's "2", maybe you wanna have a talk with your postmaster? On the other hand, if we reset immediately, I bet most users will rarely see anything greater than 0 because most visits are triggered by list posting, Admins would be similar, except that they might see correlations with remote domains, or if there was a wave across domains it might be a symptom of getting registered on an RBL or two.

3 years, 9 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/

by Mark Dadgar

On May 18, 2021, at 5:34 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/18/21 4:06 PM, Mark Dadgar wrote: >> I have a user attempting to access the list archives and he’s generating this login error. I have verified that he does have a django account. I’ve never seen this one before and I didn’t find anything relevant in the lit archives. >> >> Any ideas what’s going on here? > ... >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 134, in _has_verified_for_login >> emailaddress = EmailAddress.objects.get_for_user(user, email) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/managers.py", line 54, in get_for_user >> ret = self.get(user=user, email__iexact=email) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 82, in manager_method >> return getattr(self.get_queryset(), name)(*args, **kwargs) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/query.py", line 419, in get >> raise self.model.MultipleObjectsReturned( >> >> Exception Type: MultipleObjectsReturned at /accounts/login/ >> Exception Value: get() returned more than one EmailAddress -- it returned 2! >> Request information: >> USER: AnonymousUser > > > Go to the Django admin users page - something like > http(s)://example.com/admin/auth/user/ - and search for the email > address. This search is case-insensitive and I'm guessing it will find > two users differing in case. > > In any event, django allauth is trying to find this user and is finding > multiple EmailAddress.objects for this address or username. I had actually done this but checked the Users section and had overlooked the Email Addresses section. It was as you suggested - duplicate emails differing only in case. Given that there was only one user account, how does this happen? List subscription without associated user account creation with slightly different case? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: Importing archive from mm21

by Lars Bjørndal

On Mon, Nov 27, 2023 at 01:26:03PM -0800, Mark Sapiro wrote: > On 11/27/23 13:01, Lars Bjørndal wrote: > > I imported an archive from a list created in September 2013 with the > > following command: > > > > mailman-web hyperkitty_import -l annonsering(a)hodr.no --since 2013-09-01 <mbox file> > > > If it's a new list with no current archive, I typically don't use --since. > If there might be messages in the archive, I normally use something like > `--since 1970-01-01` just to be sure I get everything. There was some new messages in the archive prior to the import. > > No errors reported. > > > And this should have imported all messages with Date: header dates >= > 2013-09-01 plus any without Date: headers. > > > I then did > > > > mailman-web update_index_one_list annonsering(a)hodr.no > > > > No, when I go to https://hodr.no/archives/list/annonsering@hodr.no/, I > > cannot choose mails earlier than January 2023. > > > > What's the problem, do you think? > > The messages are there. I went to > https://hodr.no/archives/list/annonsering@hodr.no/ and only saw messages > from 2023, but then I went to > https://hodr.no/archives/list/annonsering@hodr.no/latest?count=200&page=2 > and started seeing all the messages even at > https://hodr.no/archives/list/annonsering@hodr.no/. > > What do you see now? Now, all messages are visible. > I also note your pages seem to be missing the styling as the references to > the styles, etc at https://hodr.no/static/* all return 404. Thank you. I had `Alias /mailman3/static /opt/mailman3/web/static` instead of `Alias /static /opt/mailman3/web/static`. As I'm blind, I didn't notice that missed icons/styling. > Is the issue fixed for you now? I don't understand what caused the issue. Tyank you, the issue is fixed. Lars

2 years, 11 months

[MM3-users] Re: Implicit destination

by David Krantz

On Mon, Aug 27, 2018 at 2:50 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > That is not the issue. Sending the held message notice to a spammer, if > it reaches the spammer, is probably inconsequential. The issue is that > virtually always in spam the sender address is either undeliverable or > is the address of an innocent 3rd party. Sending these notices to > innocent 3rd parties is called backscatter and is a bad thing. > > To avoid this backscatter, you can set the list's > respond_to_post_requests attribute to False. There are two problems > here. One is this setting is not currently exposed in Postorius, and the > other is this will also stop desired held message notices such as those > from list members. Aha. That was a simple solution although with a bad consequence. Will it stop moderation mails to the moderator as well? I'll try. Otherwise it will not be a problem in my case. The lists where I have this problem are more of function addresses for a number of persons (like a board or workgroup) so they accept posts from non-members. I use mailman as a simple forward gets legit mail caught in the receivers spam filters and might cause more black-list problems. You are of course entirely correct in that backscatter is the real problem, I should have thought of that. The thing in the spam I've received lately is somewhat sophisticated: the senders have correct (albeit strange) domains and correct SPF records so they try to seem legit although the senders are located in unexpected parts of the world. I just checked one example, in that case the MX pointed to the sender IP, the SPF was very sloppy (~all) and everything looked correct except for the fact that we usually do not receive mail from Ukraine and the cryptocurrency scam in the body. It almost got caught in the spam filter, but not quite. cheers // David

8 years, 2 months

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/25 20:50, Mark Sapiro wrote: > On 7/24/24 06:35, Roland Giesler via Mailman-users wrote: >> I have managed thus far to get things working on my new install, but >> I need to use a secure logon to send mail from an external MTA. I >> have set up: >> >> /etc/mailman/mailman.cfg: >> >> smtp_host: box2.gtahardware.co.za >> smtp_port: 465 >> smtp_user: roland(a)giesler.za.net >> smtp_pass: <hidden> >> smtp_secure_mode: smtps >> smtp_verify_cert: no >> smtp_verify_hostname: no > > This looks OK, but > >> I'll get a cert installed later, for now just want to get it going. > > The `no` values for smtp_verify_cert and smtp_verify_hostname may be > part of your issue. After re-reading the documentation I realised that and changed it to "yes" for both since box2.gtahardware.co.za has valid certs. > > ... >> "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", >> line 125, in _send >> self.connection.sendmail(from_email, recipients, >> message.as_bytes(linesep='\r\n')) >> File "/usr/lib/python3.10/smtplib.py", line 901, in sendmail >> raise SMTPRecipientsRefused(senderrs) >> smtplib.SMTPRecipientsRefused: {'roland(a)giesler.za.net': (454, >> b'4.7.1 <roland(a)giesler.za.net>: Relay access denied')} >> >> However, the mailserver is in daily use and accept logon all the >> time. I believe I'm missing something that should be installed to >> make SMTPS (SSL) work, but what? > > It is the mail server at box2.gtahardware.co.za that is refusing to > relay this message. I think this issue needs to be resolved in that > MTA's configuration. Indeed that is so, but that box is in daily use by a few different users and they authenticate and send email without any problems. I'm checking out the link you shared in my other thread now.

2 years, 3 months

[MM3-users] Re: Template path

by Seth Seeger

> On Sep 17, 2020, at 12:54 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> I followed previous emails on this list which told me to set POSTORIUS_TEMPLATE_BASE_URL in /opt/mailman/web/settings_local.py, but that doesn’t seem to make any difference. (I set it to a different value and the error message didn’t change. I also tried setting it in /opt/mailman/core/settings_local.py to no effect. After each change, I restarted mailman-web and mailman-core containers.) > > > How did you create the template? In Postorius or by manually creating a > file somewhere? If by creating a file, POSTORIUS_TEMPLATE_BASE_URL is > not relevant, but ensure that the file is findable and readable by Mailman. I created the template in Postorius. >> From within mailman-web and mailman-core containers, I can reach “mailman-web:8000”. >> >> In the webpage, I see: Mailman REST API not available. Please start Mailman core. > > > The REST APT is normally exposed on port 8001, not 8000 (See `port` in > `mailman conf -s webservice`. Yes, it’s 8001: [webservice] hostname: 172.19.199.2 [webservice] port: 8001 > What is your setting for MAILMAN_REST_API_URL? does the port match? I’m not overriding it: ./postorius/mailman-web/settings.py:MAILMAN_REST_API_URL = os.environ.get('MAILMAN_REST_URL', 'http://mailman-core:8001') > >> In /opt/mailman/core/var/logs/mailman.log, I get: >> >> [17/Sep/2020:16:23:29 +0000] "GET /3.1/lists/xxx.example.com HTTP/1.1" 200 416 "-" "GNU Mailman REST client v3.3.1" > > It appears you are connecting to the REST API, but ... > ... >> urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) > > > Something appears to be trying to connect to REST on port 8000 Is this a red herring? Is something else wrong? Setting POSTORIUS_TEMPLATE_BASE_URL in settings_local.py doesn’t seem to make any difference. Having set the POSTORIUS_TEMPLATE_BASE_URL, I deleted the template and recreated it. Now, when I approve a pending subscription it goes through, but the welcome email is blank. Seth

6 years, 1 month

[MM3-users] Re: To have mailman3 start at boot, trying to configure the systemd mailman3.service unit, but having issues

by Odhiambo Washington

On Sun, Jun 9, 2024 at 1:03 AM Ron <admin(a)bclug.ca> wrote: > On 2024-06-08 14:48, Mark Sapiro wrote: > > > The "PermissionError: [Errno 13] Permission denied: '//var/templates'" > > is what it says. It is trying to create the absolute path /var/templates > > and user mailman3 doesn't have permission to create a templates/ > > directory in /var. > > > > I'm not sure why this is. It should be trying > > /opt/mailman3/mm/var/templates. What does > > > I experienced the fun of having /var being where mailman3 tried to > create files & folders. > > Some combo of the following worked for me: > > > mailman3.service > Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" > > > /etc/mailman3/mailman.cfg > [paths.here] > var_dir: /opt/mailman/mm/var > You see, you are mixing /opt/mailman with /opt/mailman3. WHY? > I explicitly set many / most of the other vars in that section too (i.e. > lock_dir was one that also caused issues). > > > > This might be the Wrong Way, but it solved issues similar to the ones > being discussed. > If you followed the virtualenv installation method as documented here: https://docs.mailman3.org/en/latest/install/virtualenv.html, then everything should be pointed to the home of the MM3 user you created at the step - https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mailman-u…. Then you wouldn't even need to get mixed up with paths and setting unnecessary environment variables. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 5 months

[MM3-users] Re: Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?

by Odhiambo Washington

On Wed, Dec 20, 2023 at 11:28 AM Pierre Malard via Mailman-users < mailman-users(a)mailman3.org> wrote: > Le 20 déc. 2023 à 09:14, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > > On December 20, 2023 7:20:17 AM GMT, Pierre Malard via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Ok, don’t throw any more away! > >> > >> If you really don't recommend the Debian packaged solution, I just have > one question: > >> Why have you included it in the Debian "main" repositories for so long? > > > > We have no control over what's in Debian repositories. Maintenance and > distribution of the Debian packages is done by Debian. > > > > We would love it if all the downstream distributions included up to date > and bug free Mailman packages. The problem is when people encounter > difficulty with a downstream package, we are often unable to help because > we don't know the details of that package. > > Ok Mark, > > Sorry, I thought that the creation of the repository depended directly on > you or, at least, on someone from the team. Obviously this is not really > the case and I will address the person in charge: Jonas Meurer I presume? > Still, the packages will always be lagging. With virtualenv, you have a container that only relies on very minimal apps from the base OS (python3-dev python3-venv sassc lynx), the MTA, the web server, and the DB backend and is mostly self-contained, besides the fact that you also get to run the latest code. -- 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] Re: High memory usage

by Philip Colmer

Thanks, Stephen. I think that the reason Prasanth & I wanted to check with this list first was to see if anyone was seeing similar behaviour. Our servers are *only* running Mailman 3 and associated packages like PostgreSQL and Postfix. Regards Philip On Wed, 16 Feb 2022 at 09:35, Stephen Daniel <swd(a)pobox.com> wrote: > I'm not an expert, and you might be better served by posting this question > in one of the communities that serves sysadmins; however, my reading says > that the oom-killer is invoked when the system cannot allocate more virtual > memory, not more physical memory. The graph in your screenshot is physical > memory usage. > > The first thing I would try is increasing the size of your swap > partition. That adds to the amount of available virtual memory, without > the need for actually buying more RAM. If you really need more RAM the > result will be that the system stays up, oom-killer stays quiet, but > performance is bad and the "si" and "so" columns in vmstat get into the > triple digits or higher. > > On Wed, Feb 16, 2022 at 3:18 AM Philip Colmer <philip.colmer(a)linaro.org> > wrote: > >> Thank you for the replies from Mark and Stephen. >> >> One of the reasons why Prasanth & I are concerned with this specific >> system >> is because the first time memory usage crept up, it got to the point where >> oomkiller stepped in and, as is usual for that particular mechanism, one >> of >> the processes it killed was sshd, thus removing access to the system :(. I >> know that oomkiller can be tuned to stop it killing processes like sshd >> but >> it will, nevertheless, start killing *some* processes if it sees an out of >> memory situation. >> >> So, as Prasanth said, we doubled the memory available and stuck an alarm >> on >> it to trigger when usage exceeded 85% for 5 minutes. I've saved a >> screenshot of the monitored memory usage over the last couple of weeks: >> >> https://1drv.ms/u/s!Aq7dn8GDGLdCodsU-pybJBdckxWU1A?e=BJY1UA >> >> (It is stored on OneDrive in case you don't recognise the URL format) >> >> We changed the server on 4th February to the larger memory size. On 11th >> Feb, it triggered the alarm and we rebooted the server. Memory usage is >> starting to climb again, albeit not at the pace that it was previously. >> >> What is particularly curious for us is that we have four Mailman 3 >> servers. >> Two of them are single domain and two are hosting two domains. This server >> is one of the servers hosting two domains, but it is also the ONLY one of >> the four servers exhibiting this memory pattern. By comparison, the memory >> usage for the other server hosting two domains looks like this: >> >> https://1drv.ms/u/s!Aq7dn8GDGLdCodsVyEufkeQqit_cGA?e=ifrJHs >> >> The biggest difference we are aware of with the "problematic" server is >> that some of the list archives are quite large by comparison with our >> other >> servers. The largest is 15K messages, then 2K then 1K. The other three >> servers have lists with relatively small archives by comparison (double or >> triple digits at worst). >> >> Finally, and just FYI, we're using PostgreSQL for the database and Xapian >> for the indexing engine. >> >> Regards >> >> Philip >> >> On Tue, 15 Feb 2022 at 16:36, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> > On 2/15/22 08:11, Stephen Daniel wrote: >> > > TL;DR: quite likely your system has plenty of memory and is operating >> > > normally. >> > ... >> > > On Tue, Feb 15, 2022 at 5:28 AM Prasanth Nair < >> prasanth.nair(a)linaro.org> >> > > wrote: >> > > >> > >> Hi, >> > >> >> > >> We are having an issue with high memory usage on our Mailman3 server. >> > >> Initially, our server had 16GB RAM and the memory usage went up from >> 5% >> > to >> > >> 92% within a week. So, we increased the memory capacity to 32GB RAM >> and >> > we >> > >> can see that the memory usage is going up in the same pattern. >> > >> >> > >> Any idea why it is happening? or any suggestions? >> > >> > >> > Just for reference, mail.python.org supports 231 MM 2 lists and 182 MM >> 3 >> > lists with 16 GB of ram and no swap. >> > >> > The server that supports this list and also the www.list.org web site >> > has 4 GB of ram and no swap. >> > >> > -- >> > 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/ >> > >> _______________________________________________ >> 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, 8 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Eggert Ehmke

Hello Mark, I am also using MySql/MariaDb, I followed your suggestion. This would uninstall a lot of other packages, is that safe? I did not continue. $ pip uninstall psycopg2_binary Found existing installation: psycopg2-binary 2.9.6 Uninstalling psycopg2-binary-2.9.6: Would remove: /opt/mailman/venv/lib/python3.11/site-packages/psycopg2/* /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary-2.9.6.dist-info/* /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libcom_err-2abe824b.so.2.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libcrypto-2cd0ac56.so.1.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libgssapi_krb5-497db0c6.so.2.2 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libk5crypto- b1f99d5c.so.3.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkeyutils- dfe70bd6.so.1.5 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkrb5- fcafa220.so.3.3 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkrb5support- d0bcff84.so.0.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ liblber-69811697.so.2.0.200 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libldap- e7812872.so.2.0.200 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libpcre-9513aab5.so.1.2.0 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libpq-227f62f1.so.5.15 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libsasl2-883649fd.so.3.0.0 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libselinux-0922c95c.so.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libssl-0331cfe8.so.1.1 Proceed (Y/n)? n Regards, Eggert Am Donnerstag, 19. Oktober 2023, 20:31:08 CEST schrieb Mark Sapiro: > On 10/19/23 05:02, Wikinaut wrote: > > (venv) mailman-web migrate > > > Traceback (most recent call last): > ... > > > File > > "/opt/mailman/venv/lib/python3.11/site-packages/django/contrib/postgre > > s/search.py", line 1, in <module>> > > import psycopg2 > > > > File > > "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", > > line 51, in <module>> > > from psycopg2._psycopg import ( # noqa > > > > SystemError: initialization of _psycopg raised unreported exception > > Since you are using MySql and not PostgreSQL, in your venv do > ``` > pip uninstall psycopg2_binary > ```

3 years

[MM3-users] Mailman Suite release announcement

by Abhilash Raj

Hi All, I am pleased to announce new releases for Mailman Suite, including - Mailman Core 3.3.0 (Tom Swayer) - Mailmanclient 3.3.0 - django-mailman3 1.3.0 - Postorius 1.3.0 - Hyperkitty 1.3.0 This is a feature release and also includes a bunch of bugfixes. I am really really thankful to a lot of contributors who have helped out with this release. It is really nice to see Mailman 3 gaining more users and contributors. Python 3.5 is the minimum supported version, but all the releases have been tested to work with Python 3.5-3.7. This is the last release to support Python 3.5 since it has been in security only maintenance mode for a while now. Some of the highlights of this release includes: Mailman Core 3.3.0 - Support for ARC signing. Thanks to Gene Shuman and Stephen Turnbull. - Many many improvements to "mailman import21" command. Thanks to Mark Sapiro. - Addition of French templates. Thanks to Stéphane Parunakian. - A better and more scalable REST API server using Gunicorn. - Support for SMTPS/STARTTLS. Thanks to J08ny. A full copy of change log is available at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html Postorius 1.3.0 - Many more settings for MailingList configuration exposed, including preferred language, digest related settings. - Support for FILTER_VHOST to filter MailingLists based on the serving domain. Thanks to Nate Coraor. - Ability to write MailingList info in Markdown to render info in HTML instead of Plaintext. A full copy of change log is available at: https://postorius.readthedocs.io/en/latest/news.html Hyperkitty 1.3.0 - Unread messages, when logged in, are more easily recognizable with blue envelope icon. - Improved thread view with colored background for quoted parts of messages. - Improved readability on small screens by removing the indentation in thread view. A full copy of the change log is available at: https://hyperkitty.readthedocs.io/en/latest/news.html All the packages are available to download from PyPi (https://pypi.org) https://pypi.org/project/postorius/ https://pypi.org/project/hyperkitty/ https://pypi.org/project/django-mailman3/ https://pypi.org/project/mailman/ https://pypi.org/project/mailmanclient/ -- thanks, Abhilash Raj (maxking)

7 years, 2 months

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

by Flo

On 10/11/25 04:45, Mark Sapiro wrote: > On 10/10/25 3:46 PM, Flo via Mailman-users wrote: >> >> /var/lib/mailman3/web# sqlite3 mailman3web.db >> SQLite version 3.46.1 2024-08-13 09:16:08 >> Enter ".help" for usage hints. >> sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON >> site_id = django_site.id; >> ... >> ... >> 8|lists.example.com|7|7|Lists of Example|lists.example.com >> sqlite> >> > > The fields in order are: > > 1. the id of the django_mailman3_maildomain entry > 2. the mail_domain in the django_mailman3_maildomain entry > 3. the site_id the django_mailman3_maildomain entry > 4. the id of the django-site entry > 5. the domain name in the django-site entry > 6. the display name in the django-site entry > For me it looks like that 5 is the display name and 6 the domain name > The important things are 2. and 5. which are the mail host and the web > host that you see in the Postorius domains view. 3. and 4. are what we > joined on so they will always be the same. They aren't related to 1. > which is just sequentially assigned when entries are created. 1., 3. and > 4. being equal in some cases is a coincidence. > > The question is what are the other 2 entries. In particular are all 3 > values for 2. different and all 3 values for 5. different or are some > the same? > > If 2 of those entries have the same value for 5. and different values > for 2., that explains the issue when accessing Postorius at 5. because > that web host does not have a unique mail host. > For each of the lines mail_domain (field 2) is the same as the domain name (field 6, if I am right). Any domain name (and mail_domain, which has the same value) differs from the ones in any other line. So they are unique. Flo

1 year, 1 month

[MM3-users] Re: Confirmation emails aren't sent to users.

by Stephen J. Turnbull

Ibiam Chihurumnaya via Mailman-users writes: > Mark Sapiro wrote: > > > OK, this is Django. The default EMAIL_BACKEND from > > mailman_web/settings/base.py is > > django.core.mail.backends.smtp.EmailBackend and unless you've changed > > that or added overrides various other defaults are > > EMAIL_HOST = "localhost" > > EMAIL_PORT = 25 > > EMAIL_HOST_USER = "" > > EMAIL_HOST_PASSWORD = "" > > EMAIL_USE_TLS = False > > EMAIL_USE_SSL = False > > EMAIL_SSL_CERTFILE = None > > EMAIL_SSL_KEYFILE = None > > Are those appropriate? Do you have an outgoing MTA listening on > > localhost:25? What's in it's logs? > > I don't have any of those set, didn't realize I needed to have them > set, the docs didn't make it obvious too. Those defaults *are* set in the mailman_web settings files. You can override them in /etc/mailman3/settings.py, but often you don't need to. > I also didn't notice them in schema.cfg in mailman. This is for Django, whose configuration is in /etc/mailman3/settings.py, with defaults set in the mailmanweb package in your venv's site-package in the files in .../mailman_web/settings/. > smtp_port is currently set to 25, and I do have an outgoing MTA > listening on localhost:25. If Mailman can distribute posts that way, Django should be able to send mail with the default settings. > Nothing shows up in the MTA logs about this particular email. Not sure what to say about that. I'm not sure Postorius or Django log outgoing mail messages but I think they use the mailmanweb.log file by default if they log mail at all. (This is separate from the MTA logs which should record any connections from localhost and mail submitted.) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months

[MM3-users] Re: Moderate mails from owner

by Abhilash Raj

On Thu, Mar 21, 2019, at 8:47 AM, Malcolm Austen wrote: > On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: > > > However, this is apparently not relevant because both the Member and > > Non-Member actions are Hold. Thus, the post should be held unless it has > > an Approved: header with the list's moderator_password attribute if > > there is one, or it matches a Header filter rule with an accept action. > > At the risk of getting this really wrong - I have only limited MM3 > knowledge - I will ask what is, I fancy, a closely related question ... > > My only experience of MM3 is with Ancestry's 'RootsWeb' installation. From > the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't find > anything to identify Postorius which is the only interface I have to the > system. > > From symptoms seen and described by others, I have deduced that the > Postorius admin-per-user moderation options of "Default processing" and > "List default" mean that a user may be set (by default on the rootsweb > system!) to use the system default moderation settings rather than the > list default settings. "Default Processing" means the default pipeline defined in List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This pipeline is system wide and is defined in source code, so it can't be customized by site administrator. > > Are my deductions correct? And if so, could this be the explanation of the > issue detailed in this thread? > > Apologies if I'm barking up entirely the wrong tree, Malcolm. > > -- > Malcolm Austen <malcolm.austen(a)weald.org.uk> > _______________________________________________ > 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, 7 months

[MM3-users] Re: Mailman3 on FreeBSD

by Abhilash Raj

On Sat, 12 Aug 2017 18:10:49 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/12/2017 04:51 PM, Barry Warsaw wrote: > > On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> > > wrote: > >> > >> On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however > >> I don't see any indication as to what I should put in this file > >> and if it was in /usr/local/etc/mailman.cfg then how would mailman > >> find it? > > > > It wouldn’t by default. Right now Mailman does not search > > for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult > > change to add. I’m not sure whether that would makes sense as a > > general default or not. I’m not up on the FreeBSD conventions and > > standards here; can you explain why /usr/local/etc is preferred > > over /etc on that distro? > > > I was hoping Abhilash would chime in here, because I think John is > using the docker image and there's probably a specific path for > mailman.cfg. As per his first message, I think John is using the prod setup from the documentaion[1]. I don't have anything much to add on top of what Barry mentioned, it looks like something is wrong with the Python install and missing Sqlite3 module. The documentation does mention the paths where Core looks for configuration file and anything else can be specified using -C or MAILMAN_CONFIG_FILE environment variable. [1]: http://docs.mailman3.org/en/latest/prodsetup.html > As far as what goes in it, it could even be empty if you want to > accept all the defaults, but you probably want at least > > [mailman] > site_owner: real_person(a)example.com > > I expect if you do > > find -name mailman.cfg > > in your installation, you'll find at least examples. > thanks, Abhilash

9 years, 3 months

[MM3-users] Re: Unusual behavior: Standard discussion lists with prefix are sometimes having prefix *dropped*

by Thomas Ward

On 10/19/23 13:41, Mark Sapiro wrote: > On 10/19/23 10:02, Thomas Ward via Mailman-users wrote: >> I noticed some unusual behavior in Mailman3 stable release on PyPI >> and such. Namely, there are instances where replies are being >> processed and the prefix tags are simply being **lost** and dropped >> by Mailman3, instead of being properly prepended where they're >> supposed to go. >> >> Is this a known bug or does it need its own bug in the gitlab tracker? > > > Are you sure you are looking at messages from the list and not > messages received by direct To:, CC: or BCC:? > > I have never seen an issue where list posts would sometimes have the > subject prefix prepended and sometimes not. If you are seeing this, we > would ideally like to see a thread in the hyperkitty archive where > some of the messages have the prefix in the message view and some > don't, or at least see some of the raw Subject: headers. This might be a MUA quirk because we (read: my employer, like my other messages) are using Outlook which we all know does Weirdness. Upon examination of the actual message's source it has the proper subject line with a prefix: > Subject: [Test] Emailing Test But the way this is displayed in Outlook is weird. It may be that Microsoft is seeing the message as CC'd (reply-all was used!) and then stripping prefix, etc. because it realized there was some stupidness or such at the message-id level or something. This is looking more like a MUA issue because my other address which is subscribed and uses Thunderbird to access the mailbox instead sees the headers right with the proper prefix, suggesting this is something specific to Outlook as a MUA. Thomas

3 years

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

by Odhiambo Washington

On Sun, Feb 5, 2023 at 8:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/5/23 01:13, Odhiambo Washington wrote: > > > > So in my case, I should at least increase the value of > > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? > > > It probably isn't even set in your case and defaults to 900 if it isn't > set. I have never seen this config option in any of the settings files and so believe that no one has it set - except the DEVs, maybe. > Yes, you can set it to a larger value. If your archive search > engine is woosh and your archive is even moderately large, 1800 probably > isn't nearly enough. Yes, my archive search engine is whoosh. And my archives size is 2.5GB+ For starters I will make it 3600 and observe next time. > There was no indication of timing in your OP, but you should determine > when that cron job started and when the error was > reported. The difference is the absolute minimum you should set > for HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin > to that. > Sadly I deleted the email. I will have to determine those aspects next time. I need to make a request for a small improvement on the documentation at: https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m… The problem I am facing (the subject of this thread is that of a race between the "monthly hyperkitty update_and_clean_index" job and the hourly "hyperkitty update_index job" Would it be possible to add such details to the section, so that it is clear what the corn jobs do and perhaps what can lead to such race conditions (if that's not too much to ask)? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 9 months

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

by Tim Cutts

> On 12 Jul 2022, at 16:28, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/12/22 12:34 AM, Julian Kippels wrote: >> Hi, >> We have recently upgraded from Mailman 2 to Mailman 3. Since then I >> have observed many user reports that mails to mailing lists don't reach >> all members. My suspicion is that there are too many "dead" members on >> those lists. This was not a problem on Mailman 2, but has become a >> problem on Mailman 3. It seems to me that for example Mailman 3 sends >> mails to the first 5 existing member addresses from domain A, then >> encounters several (20 or so seems to be the threshold) "dead" member >> addresses from domain A that generate a bounce and then does not even >> attempt to reach the remaining 800 member adresses from domain A and >> only sends to members on domain B and domain C. >> Is there a way to globaly ignore bounces and send out mails to all >> members of a list, no matter what? > > > Mailman's outgoing runner should not be quitting because of bounces at SMTP time. It seems like there may by some issue causing Mailman's outgoing runner to die. What's in Mailman's var/queue/shunt/ and Mailman's var/logs/mailman.log. Good point. Mailman3 needs a great deal more RAM than Mailman2, especially if you’re running the web and core on the same machine. I used to comfortably run my small mailing list server on a 1GB VM, but on Mailman3 I found it often ran out of memory and bits of mailman3 would get shot by the kernel’s OOM killer, and had to move to a larger VM. So I’d check your kernel logs and see if you’ve got OOM messages in there. Tim

4 years, 4 months

[MM3-users] Re: External MTA incoming mail: configuration

by Odhiambo Washington

On Wed, Jul 31, 2024 at 2:35 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2024/07/30 22:39, Mark Sapiro wrote: > > It appears you have a situation where the MX for the Mailman domains > > is not the Mailman server. You need to configure the MTA on > > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > > You can to this by configuring that MTA to use transport_maps, etc as > > if it were the Mailman server. In order to get Mailman's generated > > files on the other server, you need to create a process to do that. > > When Mailman makes changes by adding or deleting lists or when it is > > started, it updates the postfix_lmtp and postfix_domains files and > > calls a command (normally postmap) to update the corresponding .db > > files. The command can be set by setting `postmap_command` in the > > `[postfix]` section in mailman.cfg. > > > I'm not able to find any documentation about `postmap_command`, not even > in the schema.cfg. If I have to provide method to update the > postfix_lmtp and postfix_domains on another server, then it would have > to something like sftp? mailman changes the files on the mailman server > (in a location I set) and then postmap_command copies those files to the > destination on the MTA server. Is that in principle what needs to be done? > > thanks again! > Read this thread and take a keen look at the solution provided by @Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> : https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 3 months

[MM3-users] GSoC task: shell completions for the 'mailman' utility was: Is there a bin/find_member in MM3

by Stephen J. Turnbull

Mark Sapiro writes: > mailman findmember -h > Usage: mailman findmember [OPTIONS] PATTERN IWBNI we had shell completions for bash and zsh at least. I've been out of it, should have got to this sooner, but GSoC org applications are open until Feb 3, so I'll try to rustle one up. If anybody is willing to serve as backup org admin and second mentor, please let me know. Qualifications: org admin fills out GSoC paperwork 2-3 times a season, keeps track of mentor-student relations, and usually serves as a mentor. Note: Mailman has never called on a backup org admin in 10+ seasons of GSoC. Mostly second mentors just read email a couple times a week and comment when they have something to contribute. No real Python-specific skills required, mostly hand-holding and occasionally pumping the brakes on hair-brained deviations from proposed work, and I guess you'd be uncomfortable if you're not comfortable with at least one high level language. Python is often characterized as "executable pseudo-code": it's easy to learn enough to mentor. Deep knowledge of Mailman is not needed for most projects (the bash completions project above is an example where zero knowledge is needed). Typically they add a feature, sometimes independent of Mailman internals, instead hooking into a well-defined API. Obviously Python skills are useful, and most projects will interface with Mailman code. However, it's not uncommon that I've learned Python skills during GSoC, mostly from studying the Mailman code (Barry is not known as the Friendly Language Uncle for Life aka FLUFL for nothing, you know), but often from the student. So it's a learning opportunity for most mentors. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months, 2 weeks

[MM3-users] Re: exim4 + mailman3 lmtp failure

by Thomas Drillich

Hello Mark, thank you four your fast response, yes I use the default port 8024 netstat -atp: tcp 0 0 localhost:8024 0.0.0.0:* LISTEN 26555/python >grep MM3_LMTP_PORT /var/lib/exim4/config.autogenerated MM3_LMTP_PORT=8024 lines from exim4/mainlog 2020-05-06 21:48:08.506 [5776] 1jWQ1Y-0001VA-2A <= th(a)drillich.com H=mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 P=esmtps L- X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7313 M8S=0 DKIM=drillich.com RT=0.146s id=bb5a020a-bcc3-81a2-b5ab-6d89eaf5b28d(a)drillich.com from <th(a)drillich.com> for seebruecke(a)listen.td3.eu 2020-05-06 21:48:08.517 [5776] SMTP connection from mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 closed by QUIT 2020-05-06 21:48:08.787 [5777] 1jWQ1Y-0001VA-2A ** seebruecke(a)listen.td3.eu F=<th(a)drillich.com> P=<th(a)drillich.com> R=mailman3_router T=mailman3_transport: all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) Am 06.05.20 um 20:55 schrieb Mark Sapiro: > On 5/6/20 10:54 AM, Thomas Drillich wrote: >> Hello, >> >> I tried to setup exim4 + mailman3 but it seems to stuck at lmtp delivery of mailman3. >> Could you give me a hint, to detect the reason of failure ? > ... >> # /etc/exim4/conf.d/transport/55_mm3_transport >> mailman3_transport: >> driver = smtp >> protocol = lmtp >> allow_localhost >> hosts = localhost >> port = MM3_LMTP_PORT >> rcpt_include_affixes = true > Have you defined MM3_LMTP_PORT and is it the same value as the > lmtp_port: setting in the [mta] section of mailman.cfg - default 8024? > > And is Mailman core and particularly its lmtp runner running and is it > listening on the relevant port? > > Is there more information about "all hosts for 'listen.td3.eu' have been > failing for a long time" in exim's logs? > > > _______________________________________________ > 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/ -- mit freundlichem Gruss -- regards Thomas Drillich Heugasse 4 / D-55116 Mainz / Germany fon +49-6131-570-2621 mobil +49-162-469-5875

6 years, 6 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Abhilash Raj

On Mon, Mar 30, 2020, at 5:33 AM, Ralph Seichter wrote: > * Mark Sapiro: > > >> $ grep ^EMAIL settings.py > >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > >> EMAIL_HOST = 'localhost' > >> EMAIL_PORT = 25 > > > > but is this perhaps overridden in a settings_local.py file? > > I don't have a local settings file. I cloned the suite from GitLab[1] > master branch and modified the existing settings.py, based on Mailman's > documentation. > > [1] https://gitlab.com/mailman/mailman-suite.git > > I just verified that EMAIL_BACKEND is not redefined anywhere: > > $ grep -r 'mail\.backends' . > Binary file ./__pycache__/settings.cpython-38.pyc matches > ./settings.py:EMAIL_BACKEND = > 'django.core.mail.backends.smtp.EmailBackend' > ./settings.py:# EMAIL_BACKEND = > 'django.core.mail.backends.filebased.EmailBackend' > > I commented out the "if DEBUG == True" lines, which explains match > number three. As far as I can see, the mail backed definition for Django > is as it should be. > > I could provide the differences between my settings.py and the Git HEAD > version if you think that might help. It definitely would help if you paste the diff of the settings required. Also, can you jump into a django shell and see if you can get any exceptions trying to send emails: $ python manage.py shell >>> from django.core.mail import send_mail >>> send_mail( 'Subject here', 'Here is the message.', 'from(a)example.com', ['to(a)example.com'], fail_silently=False, ) I picked it up from the Django's docs and perhaps fail_silently=False would give some exceptions. Please make sure you tail the logs for any connections. Abhilash > > -Ralph > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/07/31 13:47, Odhiambo Washington via Mailman-users wrote: > On Wed, Jul 31, 2024 at 2:35 PM Roland Giesler via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> On 2024/07/30 22:39, Mark Sapiro wrote: >>> It appears you have a situation where the MX for the Mailman domains >>> is not the Mailman server. You need to configure the MTA on >>> box2.gtahardware.co.za to relay Mailman's mail to the mailman server. >>> You can to this by configuring that MTA to use transport_maps, etc as >>> if it were the Mailman server. In order to get Mailman's generated >>> files on the other server, you need to create a process to do that. >>> When Mailman makes changes by adding or deleting lists or when it is >>> started, it updates the postfix_lmtp and postfix_domains files and >>> calls a command (normally postmap) to update the corresponding .db >>> files. The command can be set by setting `postmap_command` in the >>> `[postfix]` section in mailman.cfg. >> >> I'm not able to find any documentation about `postmap_command`, not even >> in the schema.cfg. If I have to provide method to update the >> postfix_lmtp and postfix_domains on another server, then it would have >> to something like sftp? mailman changes the files on the mailman server >> (in a location I set) and then postmap_command copies those files to the >> destination on the MTA server. Is that in principle what needs to be done? >> > Read this thread and take a keen look at the solution provided by @Stephen > J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> : > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Excellent! I think I can get the sshfs route working, but the pending database solution is elegant! I love it! Thanks for the pointer.

2 years, 3 months

[MM3-users] Re: SPF check fails for lists subdomain

by Jan Eden

On 2023-01-05 08:55, Jan Eden via Mailman-users wrote: > On 2023-01-04 15:07, Mark Sapiro wrote: > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > Although I could specify the IP address in my SPF records directly (as > > > you suggested), I do hope that my understanding of DNS records laid out > > > above is not entirely misguided. My current setup does work as expected > > > for eden.one, after all. > > > > As I said at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > I was misreading your DNS and now I am as puzzled as you about the failure. > > It gets even more mysterious. I tried sending messages from both > lists.eden.one and janeden.net (my other domain) to a gmail account and > to another mail provider. Both messages passed the SPF checks on both > services (s. the relevant headers quoted below). Now because I send > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > check operates (and succeeds) on e.g. > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > (and not on somethingsomething(a)lists.eden.one or > somethingsomething(a)janeden.net) Could this be the reason for the failed > SPF checks in Yahoo's and Google's DMARC reports? There was never a mystery, just my complete ignorance wrt DMARC and alignment[1]. Changing the DMARC DNS entry for lists.eden.one (more specifically, the aspf tag) solved the issue: <policy_published> <domain>lists.eden.one</domain> <adkim>s</adkim> <aspf>r</aspf> <p>quarantine</p> <sp>quarantine</sp> <pct>75</pct> </policy_published> <record> <row> <source_ip>123.123.123.123</source_ip> <count>1</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>pass</spf> </policy_evaluated> </row> For other domains, I would need to turn off SRS, which is not possible for independent reasons. - Jan [1] https://en.wikipedia.org/wiki/DMARC#Alignment

3 years, 10 months

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

by Claus-Justus Heine

I have fixed the bug on forks of mailman-core, postorius and mailman-client. C Am 02.09.2017 um 14:36 schrieb Claus-Justus Heine via Mailman-users: > I think I found the bug; I have posted a comment to the issue mentioned > by Mark > > https://gitlab.com/mailman/postorius/issues/58 > > Regards > > Claus > > Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users: >> Oh well. >> >> Am 01.09.2017 um 23:44 schrieb Mark Sapiro: >>> On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >>>> >>>> Seemingly, at some point in the deep dungeons of the source code the >>>> "Acceptable aliases" Text-Box is not interpreted correctly. >>>> >>>> Specifically, at the start it contains the string >>>> >>>> [] >>> >>> >>> See <https://gitlab.com/mailman/postorius/issues/58>. >> >> there they talk about fancy "uni-code thinks" (email addresses?) where >> the task is to convert a new-line separated text-field into an array. Oops. >> >> Kind thanks anyway. >> >>> >>> In order to set things on this page, you need to clear the Acceptable >>> aliases box before submitting changes. You can't actually set Acceptable >>> aliases via Postorius until this is fixed. >> >> The issue seems not to be overly active. I thought -- coming from >> Mailman v2 -- that the configuration of acceptable submitters to an >> email list (e.g. keep everyone moderated?) would be a central and >> prominent and important configuration issue. Seems not to be a central >> point. Mmmh. >> >> Thanks >> >> Claus >> >> > -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

9 years, 2 months

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

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

thanks again, Mark, for your detailed answer. On 3/15/22 17:21, Mark Sapiro wrote: > See https://gitlab.com/mailman/mailman/-/issues/901 > > You can add something like > ``` > Alternatively, you can confirm by going to the URL > > https://$domain/mailman3/lists/$list_id/confirm/?token=$token > ``` hmm. the list-url (e.g. where you can subscribe to the list) for my instance looks like https://$domain/postorius/lists/$list_id/ (that is: it spells "postorius" rather than "mailman3"). so i guess the URL should be https://$domain/postorius/lists/$list_id/confirm/?token=$token, which unfortunately returns 404. also, my postorius/urls.py does not contain an url-pattern for "confirm", unlike the current one as found on <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83> so i guess this was not possible yet with postorius 1.2.4 > to the list:user:action:subscribe template. Note that `$domain` may not > be appropriate here because it is the email domain which may not be the > web domain. > >> also: the confirmation mail says that the subject must be kept intact. >> however, i noticed that the actual "From" address of the confirmation >> mail already contains the token. > > The current template > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l… > doesn't say that. yes. the *current* template. but not the template that came with mailman3 3.2.1 > >> finally: what else is required to approve the confirmation? will the >> sender's email-address be taken into account? (e.g. if they subscribed >> "foo+mylist(a)example.com" but send the confirmation-reply from >> "foo(a)example.com", will that still work? > > > Yes. Only the token is required. > cool thanks. together with the not-yet-expired tokens, i think i can create some ad-hoc web-service that translates URLs to confirmation replies. mfd IOhannes

4 years, 7 months

[MM3-users]Re: Sass and where to find core rest logs

by Simon Hanna

On 05/05/2016 04:15 AM, Mark Sapiro wrote: > On 05/04/2016 09:45 AM, Andrew Hodgson wrote: > >> Anyway, I have compiled Mailman3, and the web interface is coming up. Bringing up the list of lists initially gave me an exception, and I saw a 5xx error in the mailman.log file in /opt/mailman/var/logs. I read up on this and as a result downgraded Falcon<1.0 in the Python 3.4 venv. >> >> I am still unable to browse the list of lists with a 500 error, only this time I am not getting an entry in the mailman.log indicating there is an issue, and I am wondering if there are more detailed logs that can be switched on? > > > There are the web server logs and there is the mailman-web configured in > LOGGING:handlers:file in (using bundler) > mailman-bundler/mailman-web/production.py (or testing.py). The > production default is /var/log/mailman-web/mailman-web.log; the testing > default is /opt/mailman/var/mailman-web/hyperkitty.log. > You might also get a 500 error because of a django error. If you have debugging enabled, you should see the trace in the browser. If not, then you should get an email (If you configured am admin email) Otherwise the files above should contain information about it. > >> The other question I have is on Sassc. I believe the default Mailman web interface has now switched to the Ruby implementation of Sass, but is this correct? The documentation on the Mailman-Bundler site seems to suggest that Sassc is still the default. > > > I think the bundler doc is out of date on this. > Hyperkitty switched from less to sass. Which sass compiler you use is irrelevant. You can use the ruby implementation (but it pulls in ruby as a dep). I am using the C preprocessor from libsass.org I will go over the docs and see if that section is unclear.

10 years, 6 months

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

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [220315 22:18]: > On 3/15/22 12:22, IEM Network Operation Center (IOhannes m zmölnig) wrote: > >yes. > >the *current* template. > >but not the template that came with mailman3 3.2.1 > > Which is over 3 years old. > > You should really be taking up these issues with Debian. Maybe if > they got enough pressure from users, they would update their > package. Debian (as all distributions) freezes their packages when releasing, that's why it's called stable. If someone wants newer packages, it's possible to use stable-backports (see below). Debian oldstable has mailman3 version 3.2.1. Debian stable has mailman3 version 3.3.1. So, in this case, the version in Debian oldstable is used. Which is, well, a bit behind stable, because oldstable is one release behind from the current stable. From (any) software point of view, distributions are always too old. However, having a frozen version of packages has great benefits for admins and reduces efforts. That's why distributions exists. As I said multiple times (also here), my recommendation is: if the software in the distribution works for you, use it. If not, use your own. However, don't assume that pressure works here at all - distributions are freezing packages for very good reason. As Debian is an volunteer effort, however it is always possible to help the distribution and get what you want by that. A good way is stable-backports, because this allows the admin to select to have single packages from the more current testing branch of Debian. However, this only happens if someone does the necessary handholding. So far nobody volunteered for mailman, therefor mailman isn't in stable-backports. If I'd like to have a current mailman on Debian, that would be my path forward (together with running Debian stable, not oldstable); but that's not an easy one if you are not involved with debian yet. Andi

4 years, 7 months

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

by Stephen J. Turnbull

Jens Günther writes: > Am 09.12.23 um 00:27 schrieb Mark Sapiro: > > You need a PUT command, not POST. Try the above with `-X PUT`. > > With the `-X PUT`-command, there is the following error: > {"title": "400 Bad Request", "description": "Unexpected parameters: > bounces_address, created_at, digest_last_sent_at, fqdn_listname, > http_etag, join_address, last_post_at, leave_address, list_name, > mail_host, next_digest_number, no_reply_address, owner_address, post_id, > posting_address, request_address, usenet_watermark, volume"} You should post the exact command or interactive conversation you're using. My guess is that the REST API is expecting a single JSON object, and you sent it multiple parameters. Have you played with the REST API interactively? The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… is really quite good as a tutorial. It's not a full API reference, and not organized that way, although the table of contents is very useful for what it does mention. But I think what you need (if you want to explore it that deeply) is a tutorial to get a "feel" for how the REST API "likes to talk". > Is there another way to preserve these information about the > members? You can query the REST API (you might need to fetch the subscriber roster, then iterate over that to get the details), or you can dump the database table (or the whole database) using SQL-based utilities like psql (Postgres, I forget the MySQL equivalent). > (in general I don't think a lot of people put in effort to > customize there memeberships ... and furthermore they would need to > register, right?) Not sure what you mean by "register", but every address that writes to Mailman gets a temporary user until a "real" user claims it via the mailbox ownership dance. If they receive mail in a mailbox, they've done the ownership dance for that mailbox. If you don't preserve that record, they'll have to do it again. Steve

2 years, 10 months

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

by Gerald Vogt

On 23.10.24 00:09, Mark Sapiro wrote: > How are you creating the template? If you are creating it via Postorius, Yes, via Postorius created using the url https://lists.example.org/mailman3/lists/community.lists.example.com/templa… > what is your setting for POSTORIUS_TEMPLATE_BASE_URL and what does the I did not set POSTORIUS_TEMPLATE_BASE_URL in settings.py. > entry in the template table in the database look like? in mailman.template: mailman=# select * from template where id = 6; 6|list:user:action:subscribe|community.lists.example.com|http://localhost:8… in mailmanweb.template: mailmanweb=# select * from postorius_emailtemplate where id = 6; 6|list:user:action:subscribe|test1234||2024-09-09 13:52:22.377792+02|2024-10-14 15:11:43.029873+02|list|community.lists.example.com > POSTORIUS_TEMPLATE_BASE_URL should be the same URL you use to access > Postorius up to but not including the `/postorius/` or `/mailman3/` > part. I.e, for this list whose info page is at https:// > lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/, the > setting is > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` For testing I have set POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' to the URL of our main domain, however, if I test an anonymous subscribe through the list info page I still get the timeout error ``` HTTPConnectionPool(host='localhost', port=8000): Read timed out. (read timeout=5) ``` Logs still show the same behaviour: the request for the template comes into the server but is finished and logged after 5 seconds: 127.0.0.1 - - [23/Oct/2024:05:51:38 +0000] "GET /mailman3/api/templates/list/community.lists.example.com/list:user:action:subscribe HTTP/1.1" 200 8 "-" "python-requests/2.32.3" The tcpdump of the tcp conection also looks the same: the response is pushed with the termination of the connection. I can access http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… with curl and immediately get the response. So it still looks to me as if the response is stuck in the tcp buffers of the connection and not pushed immediately, but only once the requestor times out after 5 seconds and closes the connection. Thanks, Gerald

2 years

[MM3-users] Re: archiving problem & updates

by Christian Stalberg

I see two messages waiting to be archived. Below is excerpt from the logfile: Feb 10 13:40:49 2021 (974) held message approved, message-id: <CAGrL7FsaX8EG9pMUZreJrQt1xkEyR3ySuw2-xn3m443O0N3j1A(a)mail.gmail.com> [10/Feb/2021:13:40:49 +0000] "POST /3.1/lists/ncpoa(a)lists.ccalternatives.org/held/5 HTTP/1.1" 204 0 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:49 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:49 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:50 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:40:50 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" Feb 10 13:40:55 2021 (846) HyperKitty failure on https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M (413) Feb 10 13:40:55 2021 (846) Exception in the HyperKitty archiver: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M Feb 10 13:40:55 2021 (846) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M Feb 10 13:40:56 2021 (846) HyperKitty failure on https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M (413) Feb 10 13:40:56 2021 (846) Exception in the HyperKitty archiver: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M Feb 10 13:40:56 2021 (846) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html>^M <head><title>413 Request Entity Too Large</title></head>^M <body bgcolor="white">^M <center><h1>413 Request Entity Too Large</h1></center>^M <hr><center>nginx/1.14.2</center>^M </body>^M </html>^M [10/Feb/2021:13:41:38 +0000] "GET /3.1/domains HTTP/1.1" 200 321 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:38 +0000] "GET /3.1/domains/lists.ccalternatives.org HTTP/1.1" 200 216 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:38 +0000] "POST /3.1/lists/find HTTP/1.1" 200 1013 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/owner HTTP/1.1" 200 668 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/config HTTP/1.1" 200 3173 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/archivers HTTP/1.1" 200 100 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/archivers HTTP/1.1" 200 100 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:53 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/member/christian%40safecomputing.o rg HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:41:54 +0000] "GET /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org HTTP/1.1" 200 453 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/owner HTTP/1.1" 200 668 "-" "GNU Mailman REST client v3.3.1" [10/Feb/2021:13:42:19 +0000] "GET /3.1/lists/ncpoa.lists.ccalternatives.org/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, February 18, 2021 10:33 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: archiving problem & updates On 2/18/21 10:00 AM, Christian Stalberg via Mailman-users wrote: > Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please? Start by looking at Mailman's logs and also see if there are messages to be archived in Mailman's var/archives/hyperkitty/spool/ directory. > Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also? There are some instructions at <https://docs.mailman3.org/en/latest/upgrade-3.2.html>. Bug fixes are listed in each project's 'news', e.g., <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS. html> for Mailman core and <https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html> for HyperKitty. -- 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, 8 months

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

by Claus-Justus Heine

Am 02.09.2017 um 01:57 schrieb Mark Sapiro: > On 09/01/2017 04:20 PM, Claus-Justus Heine via Mailman-users wrote: >> >> The issue seems not to be overly active. I thought -- coming from >> Mailman v2 -- that the configuration of acceptable submitters to an >> email list (e.g. keep everyone moderated?) would be a central and >> prominent and important configuration issue. Seems not to be a central >> point. Mmmh. > > > > Acceptable aliases corresponds directly to MM 2.1 Privacy options... -> > Recipient filters -> acceptable_aliases. It has nothing to do with > submitters. It is a list of other addresses that can be in the To: or > Cc: of a post to avoid and "implicit destination" hold if the list > posting address is not there. However, the point here is that this bug makes the entire configuration tab unusable. I could live WITHOUT acceptable_aliases. This bug spoils the possibility to set ANY message acceptance settings _easily_. Of course, I can work around: * delete the text field for acceptable aliases before hitting submit * insert a fance @ character there, and give a damn about the fancy stuff mailman3 does with this However, the possibility to make an entire mailing list moderated -- ALL POSTS -- is a central point. Or not? If this is so complicated then one option might be to remove the entire "acceptable aliases" field. It does not work anyway, and spoils other useful things (read: all other settings in the "Message Acceptance" tab) The point is not so much what this particular setting is for, but: it is broken for more than a year now and spoils other useful settings in the configuration dialog that it is located at. The "Message Acceptance" dialog is a central point IMHO. You make have another opinion about that. Cheers Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

9 years, 2 months

[MM3-users] Re: Archiver "prototype" and disabling archiving at all

by Abhilash Raj

On Thu, Mar 28, 2019, at 9:18 AM, Torge Riedel wrote: > Am 24.03.19 um 16:49 schrieb Mark Sapiro: > > On 3/24/19 5:40 AM, Torge Riedel wrote: > >> in the settings of a mailing list I can choose two archivers: > >> "Hyperkitty" and "prototype". What is this archive "prototype" and how > >> can I disable/remove/deinstall it? And how can I disable archiving at > >> all, so no archiver can be chosen in the settings. > > > > The prototype archiver stores messages individually in > > var/archives/prototype/LIST_NAME/. > > > > You can disable the prototype archiver by putting > > > > [archiver.prototype] > > enable: no > > > > in your mailman.cfg. To disable all archiving, just remove all the > > [archiver.*] sections from your mailman.cfg or set them to 'enable: no' > > > > > Hi Mark, > > thanks. This disabled the archivers, but there is still the "Archives" > link on top of the page. Is it possible to remove it? Cause there is > nothing to see there. I tried commenting "'hyperkitty'," in > INSTALLED_APPS, but then I got a 500. INSTALLED_APPS = ( 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'django_gravatar', 'allauth', 'allauth.account', 'allauth.socialaccount', ) This is how it should look like if you want to remove Hyperkitty. There are a few other settings you should remove. https://gitlab.com/mailman/postorius/blob/master/example_project/settings.py This is a Postorius only configuration for reference. > _______________________________________________ > 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, 7 months

[MM3-users] Re: Deleting A List

by Odhiambo Washington

On Thu, May 2, 2024 at 8:11 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/2/24 03:42, Odhiambo Washington wrote: > > I have deleted a list (list(a)nog.ke) - list_id = list.nog.ke. > > I can see from Django Admin UI that the archives are still intact. > > I created a new list (list(a)lists.nog.ke) - list_id = list.lists.nog.ke > > Is there a way to move the archives from the old list to the new list? > > > Change the `name` and `list_id` in the list's entry in the > `hyperkitty_mailinglist` table in the database. If there is already an > entry there for the new list, delete it > > ``` mysql> select id, name, list_id from hyperkitty_mailinglist; +----+----------------------------+----------------------------+ | id | name | list_id | +----+----------------------------+----------------------------+ | 1 | skunkworks(a)lists.my.co.ke | skunkworks.lists.my.co.ke | | 2 | list(a)nog.ke | list.nog.ke | | 3 | eanog(a)lists.my.co.ke | eanog.lists.my.co.ke | | 4 | isoc(a)lists.my.co.ke | isoc.lists.my.co.ke | | 5 | kazi(a)lists.my.co.ke | kazi.lists.my.co.ke | | 6 | kenog(a)lists.my.co.ke | kenog.lists.my.co.ke | | 7 | mechanics(a)lists.my.co.ke | mechanics.lists.my.co.ke | | 8 | science(a)lists.my.co.ke | science.lists.my.co.ke | | 9 | security(a)lists.my.co.ke | security.lists.my.co.ke | | 10 | vmware_tech(a)lists.my.co.ke | vmware_tech.lists.my.co.ke | | 11 | water(a)lists.my.co.ke | water.lists.my.co.ke | | 12 | wordpress(a)lists.my.co.ke | wordpress.lists.my.co.ke | | 13 | list(a)lists.nog.ke | list.lists.nog.ke | +----+----------------------------+----------------------------+ 13 rows in set (0.00 sec) mysql> delete from hyperkitty_mailinglist where id = 13; ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key constraint fails (`mailmansuite`.`hyperkitty_mailinglist_owners`, CONSTRAINT `hyperkitty_mailingli_mailinglist_id_a47e04ec_fk_hyperkitt` FOREIGN KEY (`mailinglist_id`) REFERENCES `hyperkitty_mailinglist` (`id`)) ``` Is there an easier way? I need to delete id=13 then rename id=2 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 6 months

[MM3-users] Re: Mailing list resends same email multiple times

by 朱超

在 2023-03-10 04:54:28，"Mark Sapiro" <mark(a)msapiro.net> 写道： >On 3/9/23 04:18, 朱超 wrote: >> Hello, I need your help. There have question about Scenes: >> >> Add mailbox a and mailbox b to mailing lists c and mailing lists d, and send mail to mailing list c and mailing list d through mailbox b , among which a has received many mails sent by b, check the log and find: The file about path:/opt/mailman /var/queue/bounces has the content of retrying mail, but I turned off process bounces. >> >> Mailing list sends mail via exim, logs found in exim： 023-03-09 00:54:47 1pa4YR-001xk5-0y <= <> R=1pa4YM-001xje-1F U=exim P=local S=7672 T="Mail delivery failed: returning message to sender" from <> > >I need more information. Even though the list isn't brocessing bounces, >bounces will still be returned to the -bounces address and queued in >/opt/mailman/var/queue/bounces. If they remain there, the bounce runner >is not processing them. If the list's bounce processing is turned off, >the bounce runner should just dequeue the message and discard it. > >If multiple messages go to the list, something is returning them to the >list posting address instead of the list-bounces address. > Yes, You are right, I found the real reason and found that someone intercepted the mail sent through the mailing list, and then reposted the mail to the mailing list, resulting in multiple sending of mail. I only need to add spf detection in mta. 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 >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >This message sent to tom_toworld(a)163.com

3 years, 8 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Thu, Dec 29, 2022 at 10:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/29/22 00:31, Odhiambo Washington wrote: > > > > Exactly, and I have entered all the credentials from the "OAuth 2.0 > Client > > ID and Client Secret" > > of the twitter developer portal. > > > > https://webmail.kictanet.or.ke/~wash/twitter-oauth.png > > > Try adding lists.kictanet.or.ke to Chosen sites along with > mm3-lists.kictanet.or.ke Even with that added, still same error. ERROR 2022-12-29 15:26:40,224 70236 django.request Internal Server Error: /accounts/twitter/login/ Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth/views.py", line 43, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/base/mixins.py", line 18, in dispatch return self.login(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth/views.py", line 75, in login client = self._get_client(request, callback_url) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth/views.py", line 49, in _get_client app = provider.get_app(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/base/provider.py", line 30, in get_app return adapter.get_app(request, self.id) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 204, in get_app app = SocialApp.objects.get_current(provider, request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 31, in get_current app = self.get(sites__id=site.id, provider=provider) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", line 650, in get raise self.model.DoesNotExist( allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching query does not exist. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

[MM3-users] Re: Database permission problem?

by Bill Oliver

On Tue, 2024-10-15 at 17:20 -0700, Mark Sapiro wrote: > On 10/15/24 14:45, Bill Oliver wrote: > > > > In any case, here it is changed back: > > > > ls -l > > total 68 > > -rw-rw-r-- 1 mailman mailman 0 Oct 15 12:53 postfic_vmap.db > > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 postfic_vmap.db.db > > Were these created manually? They should not be there. Likewise the > .db.db files below. See previous reply. > > > -rw-rw---- 1 mailman mailman 353 Oct 15 13:37 postfix_domains > > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_domains.db > > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 > > postfix_domains.db.db > > -rw-rw---- 1 mailman mailman 1155 Oct 15 13:37 postfix_lmtp > > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_lmtp.db > > -rw-rw-r-- 1 mailman mailman 12288 Oct 15 12:53 postfix_lmtp.db.db > > -rw-rw---- 1 mailman mailman 1118 Oct 15 13:37 postfix_vmap > > -rw-r----- 1 mailman mailman 12288 Oct 15 13:37 postfix_vmap.db > > > Does Postfix have read and search ('x') on all of /opt, /opt/mailman, > /opt/mailman/mm, /opt/mailman/mm/var and /opt/mailman/mm/var/data? > > Perhaps there is a SELinux issue. Yes. The directory is globally searchable: ls -l total 44 drwxr-xr-x 4 mailman mailman 4096 Oct 10 18:29 archives drwxr-xr-x 2 mailman mailman 4096 Oct 5 20:45 cache drwxr-xr-x 2 mailman mailman 4096 Oct 15 22:26 data drwxr-xr-x 2 mailman mailman 4096 Oct 5 20:45 etc drwxr-xr-x 3 mailman mailman 4096 Oct 10 18:20 lists drwxr-xr-x 2 mailman mailman 4096 Oct 15 22:30 locks drwxr-xr-x 2 mailman mailman 4096 Oct 5 20:45 logs -rw-rw---- 1 mailman mailman 5 Oct 15 22:26 master.pid drwxr-xr-x 2 mailman mailman 4096 Oct 5 20:45 messages drwxr-xr-x 14 mailman mailman 4096 Oct 5 20:45 queue drwxr-xr-x 2 mailman mailman 4096 Oct 5 20:45 templates SELinux is not installed on this machine yet. That will come later. Thanks for the replies. billo >

2 years

[MM3-users] Re: Issue with Held Messages

by Jean-Luc Wasmer

On 2016-08-19 17:58, Mark Sapiro wrote: > On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >> >> No matter what action I set for member posts (Hold for moderator, >> Reject) they are always delivered. > > > I don't know why this would be. Perhaps the member's moderation is set > to Accept immediately - you can see this on ther member's options page > in Postorius when logged in as a list owner. Apart from "Mode of Delivery" that is set to "Regular" for the user, none of the following attributes are set: Mail Delivery Receive own posts to the list Receive acknowledgement mails Conceal address from the subscriber list Avoid duplicate copies of messages > When the message is delivered, what are the X-Mailman-Rule-Hits: and > X-Mailman-Rule-Misses: headers? > There is no X-Mailman-Rule-Hits header. X-Mailman-Rule-Misses: approved; emergency; loop; member-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header; nonmember-moderation By the way, I didn't mention before but in Settings | Message Acceptance, the "Acceptable aliases:" box contains "[]". When I try to Save changes after modifying something, I gut "An error occured: []" in the yellow banner (instead of "The settings have been updated."). >> When I tried from a non-member email address, the message got held but >> when I try to see it I get a Server Error (500) page. The log files >> shows: >> >> ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server >> Error: /mailman3/lists/test.mydomain.com/held_messages >> Traceback (most recent call last): > ... >> File >> "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", >> line 443, in held >> moderation_reasons=entry['moderation_reasons'], >> KeyError: u'moderation_reasons' > > > This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> > fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> Any ETA when this will be pushed to "mailman-bundler"? Cheers, Jena-Luc

10 years, 2 months

[MM3-users] Re: Mailman 3 - Header Filter

by Henrik Rasmussen

Mark Sapiro wrote: > On 4/22/19 2:34 PM, Thomas Lehker wrote: > > I am a Mailman neophyte and need help with filtering posts based on the subject field. We have a few list owners that want 'Out of Office' replies discarded. When using the below syntax in Postorius/Header filter the post is not discarded but ends up in 'Held Messages'. Is there any syntax I am missing or a setting in the lists that needs to be disabled/enabled to get these posts dropped? Any help is much appreciated. > The issue may be that in Mailman core's 'builtin' chain, the checking of > header_matches occurs after the check for member moderation so if the > member moderation check results in the message being held, the > header_matches aren't checked. There may me a newer thread about this, but I haven't found it. In my case I would be more interested in holding or discarding mails with subject 'Out of Office' if the mail would otherewise be send the to the list members due to a non-moderated list. I would emagine that the order of "check for member moderation" and header_matches would not be significant if holding or discarding the mail due to header_matches, am I right? 🤞🏻 If so, I would think that Header "subject:" or "subject" with Pattern "^(?i)(.*)autosvar(.*)" - without the double quotes - and Function "Hold for moderation" or "Discard" should either hold or discard any message with "Autosvar" (danish word for "Out of Office reply") somewhere in the subject, but that doesn't happen. What is the correct syntax? I know that filtering out Out of Office replies is just as hard as spam filtering, since it varies, but at least there is some kind of consistency in the wording, so I would give it a try. *) In a prevous mail I was told that ^ would tell Mailman that it is a regex. -- Henrik Rasmussen her(a)adm.ku.dk Copenhagen, Denmark

3 years, 1 month

[MM3-users] Re: urls.py location on venv install

by Torsten

Hi Mark, Am 2026-08-08 23:42, schrieb Mark Sapiro: > On 8/8/26 12:58, Torsten wrote: >> >> I have just nearly finished the migration of Mailman 3 from Debian >> packages to venv and mailman (master and runner) is up and running and >> uwsgi is also up and running. >> Just when I go to the web page https://<mydomain.tld>/mailman3 I get a >> server error and looking at the mailman web log I see that the >> ROOT_URLCONF seems to be missing. > > > What is the full log message including traceback if any. > > Note that if you followed > <https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu…> > The value for ROOT_URLCONF is imported from mailman_web.settings.base > and is 'mailman_web.urls' which should be correct. > the traceback is this: Traceback (most recent call last): File "/opt/mailman/web/venv/lib/python3.13/site-packages/django/core/handlers/wsgi.py", line 124, in __call__ response = self.get_response(request) File "/opt/mailman/web/venv/lib/python3.13/site-packages/django/core/handlers/base.py", line 139, in get_response set_urlconf(settings.ROOT_URLCONF) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.13/site-packages/django/conf/__init__.py", line 104, in __getattr__ val = getattr(_wrapped, name) AttributeError: 'Settings' object has no attribute 'ROOT_URLCONF' [pid: 25054|app: 0|req: 2/2] 80.152.151.47 () {76 vars in 1372 bytes} [Sun Aug 9 02:27:03 2026] GET /mailman3/ => generated 0 bytes in 5 msecs (HTTP/1.1 500) 0 headers in 0 bytes (1 switches on core 1) Where should mailman_web.urls be located, also in /etc/mailman3 or rather in the venv of mailman_web in /opt/mailman...? >> Following this thread: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> I added urls.py to /etc/mailman3 together with the other configuration >> files (settings.py, mailman.cfg and uwsgi.ini) and have added >> ROOT_URLCONF = 'urls' to /etc/settings.py but after restarting mailman >> (core) and mailman (web) the error is still there. > > You shouldn't need to do that. That thread is for an unusual case.

3 months

[MM3-users] Re: Postorius & multi domain

by Gelpi Andrea

Thank You so much for your quickly answer and explanation. I understand that the web server name must be equal to the email domain. I read the issue. I'm not a python programmer so I ask you if it'd be long to implement a workaround like this. If the web server is a.example.com and the email domain is example.com It'd be possible to drop the "a" and send the email domain only in the query? It's a workaround. Can you help me in this? Regards, -- AG Il 22/04/20 18:22, Mark Sapiro ha scritto: > On 4/22/20 8:14 AM, Gelpi Andrea wrote: >> >> I search internet for a while and I discovered that using >> FILTER_VHOST = True >> seems to solve the problem. >> >> >From posotrius config page: >> >> FILTER_VHOST >> Filter the list of available lists in Postorius and Hyperkitty >> depending on the domain they are being currently served from. Mailman 3 >> supports multiple domains in a single installation. >> >> But it doesn't work. I got err 500 form apache. > > > FILTER_VHOST is currently broken unless each domain has the same value > for the web and email domains. See the thread at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > and the issue at <https://gitlab.com/mailman/postorius/-/issues/394>. > > >> Were can I find an explanation or a how to configure the system to have >> 2 webserver with different domains working on the some server as it was >> with mailman 2? > > > If each domain has the same value for the web and email hosts, > FILTER_VHOST will work. > > Currently though if you have domains like web host = lists.example.com > and email host = example.com, FILTER_VHOST is broken. > -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

6 years, 6 months

[MM3-users] Re: MTA setup

by Arte Chambers

Is the mailman lmtp runner a cron job? Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Tue, Dec 24, 2024 at 12:31 PM Arte Chambers <paul.m.robey(a)gmail.com> wrote: > Looks like the from header is the email address I am using for testing: From: > Arte Chambers <paul.m.robey(a)gmail.com> > > > > ``` > $mailman qfile > /opt/mailman/mm/var/archives/hyperkitty/spool/1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck > [----- start pickle -----] > <----- start object 1 -----> > Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com > [209.85.208.182]) > by list.louisvillecommunitygrocery.com (Postfix) with ESMTPS id 3E36381ED2 > for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec 2024 > 17:02:48 +0000 (UTC) > Received: by mail-lj1-f182.google.com with SMTP id > 38308e7fff4ca-3003e203acaso44323081fa.1 > for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec > 2024 09:02:48 -0800 (PST) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=20230601; t=1734973367; x=1735578167; darn= > list.louisvillecommunitygrocery.com; > h=cc:to:subject:message-id:date:from:in-reply-to:references > :mime-version:from:to:cc:subject:date:message-id:reply-to; > bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; > > b=SFr5MsvE4S5GUIy9pEuqDHdEW5nW16briFnXG6ARqjLiFgAX12TU5ozUgw5NCJobcx > > RQWkL64TyXv2C2CTKHjcBH26jiLo1p7h2edLXSBCmd374QbRYQPbv5yZb4jmwX5kfMzr > > fc/I3pSk6ruN/j+JPGLVxBJBreyLRDV+YL0rDJts83a8hcPHghGMkRTmi2Z1vLYgqThA > > 2fV/IYwrOe/q4c2+/AwlKQFUuClaxFN4AniNi++Hk7eql7q4ceDtURp1pHW/h4+8UXgJ > > 2DQ+zwPapOiU5POtfka1fAHTJgykuOoMCmO0YiwfP9p51lXmr4GmdFjFgDOiQwzhx8dH > vAEw== > X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=1e100.net; s=20230601; t=1734973367; x=1735578167; > h=cc:to:subject:message-id:date:from:in-reply-to:references > > :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id > :reply-to; > bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; > > b=IwucO1D8XfIbWVT6dQ/LdKNsesrSsiekzj0khFI38CLd6WryQGJOQftxOLR5AvneNs > > 9gUbVvFAe0VENzTbMrelFr4H5DTI9HrKbNVYEbleeMrbuPypsTdtqWTrjizGhMQROhvs > > vOxl3T+UfRjDywLj9OuYBiWKTDIIaTpeQ7rR4u1lT8iMGTUre0V8kikm1BsFXwRRzl+U > > e0ghdIaZYN5kfu/bfR5veCCQhU0l0IF+DvoZzdJCgLkYgImIPhB/X7Zv0wQiUnKoebJo > > h1UFAEQIrVx2iMFHzLsHiqBhKHvJqG72PAa1bMiG0K3EsYvSJHu5zjrkTjoHXazAci4c > trXg== > X-Gm-Message-State: > AOJu0Yz8oZOnap/9jvXAOcFZnjYoReVHBQrfUnC9u6Mi6M2Ea7dkofrs > 4mAlHtOuQYGEyFxJZIOdFybTI20qdBoQBJAPF7FHL6d4mAGrLbPMgTZy3/hWFtmXfOo93a74CSu > YsRCZKH5ixK5jPHn4Vye0i/h0oilWXQ== > X-Gm-Gg: > ASbGncsYG3zr9300F+iwV6VLqHlMKoLuiS2mnT5tGiid8o6Ojd4JIrOBQI0BVNx1aeO > FVisNFC7AKewms0adY+Ug4HLKEtg8GwSIz0i32IOtPNA+tNxEAac47wHBGkcv+H2EfTOMsD/p > X-Google-Smtp-Source: > AGHT+IFNyfqXALTZ0zcO0GJZfpIf/4WT9IZ2EG3oThjt5aoZP3sdPhxjN2UOMTqwI2axiu9io1WSiFszsjxPLHtLIs8= > X-Received: by 2002:a05:6512:1190:b0:53e:37e4:1457 with SMTP id > 2adb3069b0e04-54229550e25mr4737922e87.33.1734973365282; Mon, 23 Dec 2024 > 09:02:45 -0800 (PST) > MIME-Version: 1.0 > References: < > 77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com> > In-Reply-To: < > 77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com> > From: Arte Chambers <paul.m.robey(a)gmail.com> > Date: Mon, 23 Dec 2024 12:02:08 -0500 > Message-ID: <CAM05vAepJnJQengX825dZ4E1PVVxeEgv4ogUcmifP9tqh1i= > mg(a)mail.gmail.com> > To: Arte Chambers <paul.m.robey(a)gmail.com> > Content-Type: multipart/alternative; > boundary="00000000000021f3da0629f2f7aa" > Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG > X-Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG > X-MailFrom: paul.m.robey(a)gmail.com > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; > banned-address; emergency; member-moderation; nonmember-moderation; > administrivia; implicit-dest; max-recipients; max-size; news-moderation; > no-subject; digests; suspicious-header > CC: testing(a)list.louisvillecommunitygrocery.com > X-Mailman-Version: 3.3.10 > Precedence: list > Subject: [Testing] Re: test 12.23.24 11.57 > List-Id: For testing mailing list software < > testing.list.louisvillecommunitygrocery.com> > Archived-At: <> > List-Archive: <> > List-Help: <mailto:testing-request@list.louisvillecommunitygrocery.com > ?subject=help> > List-Owner: <mailto:testing-owner@list.louisvillecommunitygrocery.com> > List-Post: <mailto:testing@list.louisvillecommunitygrocery.com> > List-Subscribe: <mailto:testing-join@list.louisvillecommunitygrocery.com> > List-Unsubscribe: <mailto: > testing-leave(a)list.louisvillecommunitygrocery.com> > > --00000000000021f3da0629f2f7aa > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Thank you, > Paul 'Arte Chambers' Robey > 502-408-6922 > > > On Mon, Dec 23, 2024 at 2:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/23/24 09:01, Arte Chambers via Mailman-users wrote: >> > Output from mailman log after sending a test message to the list: >> > >> > Dec 23 16:52:23 2024 (684048) Traceback (most recent call last): >> > File >> > >> "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", >> > line 158, in _archive_message >> > url = self._send_message(mlist, msg) >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> > File >> > >> "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", >> > line 228, in _send_message >> > raise ValueError(result.text) >> > ValueError: >> > <!doctype html> >> > <html lang="en"> >> > <head> >> > <title>Bad Request (400)</title> >> > </head> >> > <body> >> > <h1>Bad Request (400)</h1><p></p> >> > </body> >> > </html> >> >> mailman_hyperkitty is sending the message to hyperkitty to be archived >> and receiving the 400 response. Presumably it has previously requested >> and received the list_url and the permalink to put in the message >> headers. This can be confirmed by the presence of List-Archive: and >> Archived-At: headers with values in the messages from the list. So the >> configuration seems to be correct to allow mailman_hyperkitty to >> communicate with hyperkitty. It is not clear why, but this code >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… >> is getting the ValueError. That can come from one of three places in >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming…. >> >> The lack of a Message-ID: is not it because Mailman's lmtp runner will >> add one. Most likely it is the non-ascii sender address from >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming… >> >> What do you get from >> ``` >> mailman qfile var/archives/hyperkitty/spool/xxx.pck >> ``` >> where xxx.pck is one of the (hopefully smaller) files. In particular, >> what is the From: header in that? >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to paul.m.robey(a)gmail.com >> >

1 year, 10 months

[MM3-users] Re: No styling for web apps?

by Morris Jones

On 11/26/20 10:09 PM, Mark Sapiro wrote: > On 11/26/20 8:44 PM, Morris Jones wrote: >> I have most of a new mailman suite server built and working ... >> >> collectstatic gathered a good array of static files (uncompressed so far) >> >> nginx appears to be serving them successfully >> >> The Firefox developer tools show css and js files all being delivered >> >> But none of the postorius or hyperkitty pages exhibit any styling at >> all, only bare HTML elements. >> >> The Firefox inspector will show the available styles being requested and >> delivered (style.css, bootstrap, jquery, all the things). >> >> But if I use the inspector to look at the page, nothing has any CSS >> properties. >> >> I know I'm missing something simple. > > Try running collectstatic and, if you use it, compress again. These have > to be run following various kinds of changes. > Appreciated, but to no avail: (venv) mailman@mail:~/mailman-suite/mailman-suite_project$ python manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /opt/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: yes 0 static files copied to '/opt/mailman/mailman-suite/mailman-suite_project/static', 399 unmodified. (venv) mailman@mail:~/mailman-suite/mailman-suite_project$ python manage.py compress CommandError: Compressor is disabled. Set the COMPRESS_ENABLED setting or use --force to override. And then https://mailman.whiteoaks.com I'll spend time in the Firefox developer tools to see if I can figure out what's missing. A DuckDuckGo search suggested it could be a character encoding issue. The style sheets all come up reporting "0 rules" in the developer tools. I haven't tried any other browsers either. Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 11 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Mon, Dec 26, 2022 at 7:33 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/26/22 06:14, Odhiambo Washington wrote: > > I'd like to integrate Twitter OAuth as part of the Social Accounts in my > > setup. > > I have gone through > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter, > but > > cannot find the config options to add to my settings. > > Does someone have a config block setting for "SOCIALACCOUNT_PROVIDERS =" > ? > > > The last I looked into using Twitter as an OAuth2 provider, which was > some time ago, it would not work because Twitter would not provide the > user's email address via OAuth2. Possibly this could work if the user's > name was her Twitter handle. > > As far as SOCIALACCOUNT_PROVIDERS is concerned, you don't need anything. > You just need to create your OAuth2 app and provide the keys via the > Django admin SOCIAL ACCOUNTS interface. See > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… What I did: 1. I had to uncomment the relevant line under the INSTALLED_APPS = in settings.py. I had to restart Apache so that I can get the relevant provider name at https://mysite.name/admin/socialaccount/socialapp/ 2. I would then configure the social app as per https://django-allauth.readthedocs.io/en/latest/providers.html 3. Lastly, I needed to add the relevant options under the SOCIALACCOUNT_PROVIDERS = in settings.py. Now I have this: SOCIALACCOUNT_PROVIDERS = { 'google': { 'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}, }, 'github': { 'SCOPE': [ 'user', 'repo', 'read:org', ], }, 'facebook': { 'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': [ 'email', 'name', 'first_name', 'last_name', 'locale', 'timezone', ], 'VERSION': 'v15.0', }, } And those are working but was wondering what to add for Twitter. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 4:08 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 3:33 PM, Mark Dadgar wrote: >> >> Any thoughts on how to salvage ~20 years of list archives? > > > The archives shouldn't be an issue. I don't think they are involved in > the corruption, but anyway, hopefully you still have the archive mbox > you imported. Then for the messages since then, you should be able to > get a mbox from hyperkitty with something like > > https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… > > with the obvious substitutions and appropriate start and end dates. > > The list is trickier. If you are going to start over with a clean > install, and if you have a config.pck that you imported from MM 2.1, I > suggest the following: > > Use the `mailman members` command to get a list of all members. Then > depending on how much work you want to do, also get separate lists of > plaintext and mime digest members and members with delivery disabled. > > Then on the new install, import the config.pck with `mailman import21` > and import the archive mboxes with hyperkitty_import. > > Run `mailman members --sync` with the full current membership list, and > record the [ADD]s. Then you can match the [ADD]s against the plain and > mime digest members and those with delivery disabled and set their options. > > That's a lot to do, but it should get you close. I would probably be satisfied with just exporting the current list of member email addresses + names and letting people go back and change their list settings to switch to digest, etc. if necessary. > On the other hand, if you can wait, we might be able to figure out how > to fix this, and it's even possible the underlying issue isn't database > corruption. Sure - I can wait. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 4 months

[MM3-users] Re: API timeout for one list

by Abhilash Raj

On Wed, Sep 23, 2020, at 6:33 AM, Seth Seeger wrote: > > > On Sep 22, 2020, at 4:30 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 9/22/20 12:45 PM, Seth Seeger wrote: > >> I apologize, because I think this was talked about before, but I could not find it in the archives. > >> > >> For one list, the REST API times out. Doesn’t seem to matter which page I try to go to. The uwsgi-error.log entry: > >> > > ... > >> The other lists work fine. > > > > This can happen on lists with lots of members. > > > > Try increasing the timeout. See <https://wiki.list.org/x/17892072> > > Thank you - that did solve my timeout problem. > > However, each page for this list takes between 40 and 80 seconds to > load. The list has 465 members, and it’s running (via Docker) on a 2 > core, 4 GB RAM Linode VM. I’ve watch htop during the load - one CPU > is around 20%, and the other hovers around 80%, mostly with the process > “runner”. > > Is there a way to optimize this list? There are no held messages, no > subscription requests, no templates. Are there any subscription requests pending confirmation from the User. If you go to Subscription Requests -> Pending Confirmation from list's admin page, you'll see the list there. In the past, I've noticed this caused a significant delay in every list page. This has since been fixed in the master branch, but yet to be released. > > The next biggest list has 438 members, and all those pages load very > quickly (0-2 seconds). I can’t figure out what the difference between > the two lists. > > Thanks, > Seth > _______________________________________________ > 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, 1 month

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Stephen J. Turnbull

Mark Sapiro writes: > I have had some contact [with EMWD], but not much. As far as I > know, they are still in business and offering list hosting > including Mailman 3 lists with Affinity and Empathy. They no longer > offer support for installation and maintenance of Mailman on other > people's servers. That exactly describes my experience. To jaboyib556, I recommend you contact them directly and make your own judgment. I do not know the current operators of EMWD, but I do know that the Carpenter family carefully vetted several bids. And their concentration on servers they run suggests they know what they're good at and have focus. I think they're a good bet, but only you can judge. > As far as I know, it was only EMWD that did this and for business > reasons, kept it proprietary. I corresponded with Brian about this.[1] He said that a third-party consultant (not sure if they're related to the current operators) built the Affinity and Empathy applications in PHP on a limited budget, and he felt that he needed to keep them proprietary as a temporary "no competition" measure until they could build up a nest egg to support on-going development. He said, and I have no reason to disbelieve him, that he thought it would take a year to build the reputation, another year to recoup the investment, and within that time frame he planned an open source release. I suspect he planned a Aladdin Ghostscript-like strategy: with the publication of release N, he would release N-1 as open source. He made no commitments, but I believe that was his aspiration. He was always a great supporter of Mailman, giving generously of his time and expertise to people on our lists including those hosting with other businesses. We miss him a lot. Footnotes: [1] On friendly terms: "hope for an open-source release" is not a matter of moral imperative with me, and I believe I speak for all Mailman developers on that.

3 years, 9 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 6/21/24 02:07, Mark wrote: >> ...The mmdf files don't exist in the list's directory although there >> have been many posts to the list throughout the day. On 2024-06-21 15:55, Mark Sapiro wrote: > Assuming your mailman/app/digests.py is unmodified, there is some race > condition. The code beginning at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… > finds the file and size is > 0, but by the time it gets to > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… > the file is gone. > > What other crons run at the same time? The digest.py file is out-of-the-box and unmodified. ls -la /opt/mailman/venv/lib/python3.11/site-packages/mailman/app/ ... -rw-r--r-- 1 mailman mailman 4642 Jan 30 08:06 digests.py The /var/log/cron.log shows the crons running at the same time as digest at 22:30 hours. # tail -f cron.log ... 2024-06-21T22:30:01.368407+00:00 deu CRON[3422196]: (root) CMD (sh /templates/mailman_custom_templates.sh > /dev/null) 2024-06-21T22:30:01.369050+00:00 deu CRON[3422197]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs quarter_hourly) 2024-06-21T22:30:01.371586+00:00 deu CRON[3422198]: (mailman) CMD (/opt/mailman/venv/bin/mailman notify) 2024-06-21T22:30:01.371878+00:00 deu CRON[3422199]: (mailman) CMD (/opt/mailman/venv/bin/mailman digests --periodic) 2024-06-21T22:30:01.372190+00:00 deu CRON[3422202]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) /////////////////////////////////////////////////////////////////////////////////////////////////////////////// The mailman crons are more or less out-of-the-box: MAILTO=imark(a)posteo.net 30 22 * * * /opt/mailman/venv/bin/mailman digests --periodic 30 22 * * * /opt/mailman/venv/bin/mailman notify #@daily /opt/mailman/venv/bin/mailman digests --periodic #@daily /opt/mailman/venv/bin/mailman notify # * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly # The root cron just runs a bash script every 5 minutes to copy custom templates from the mailman and mailmanweb databases and write them to files. ...

2 years, 4 months

[MM3-users] Re: ARC signing outgoing mails

by Wolfgang Bock

Hello, thanks for these hints. Now it works and outgoing mails from my lists are no longer greylisted. .... ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=xx.de ... .... ARC-Seal: i=1; s=dkim; d=xx.de .... Here my mailman.cfg (debian buster/dovecot/postfix/rspamd/mysql/mailman3) quote [ARC] enabled= yes selector= dkim privkey: /path/to/rspamd/dkim/{conf.ARC.domain}.{conf.ARC.selector}.key unquote The below mentioned hash should be deleted. In the above mentioned directory the dkim key-files are saved in following style [domain].[selector].key Regards Wolfgang Am 02.11.2019 um 01:19 schrieb Mark Sapiro: > On 11/1/19 4:04 PM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> in >> https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign… >> I found this hint >> >> "It is highly recommended that Mailman maintainers configure ARC siging >> of their outgoing email. ..." >> >> So I added in my mailman.cfg: >> " >> [ARC] >> privkey: /path/to/private.key >> " >> >> >> But I don't understand the meaning of >> >> >> "... and located at: >> " >> #{config.ARC.selector}._domainkeys.#{config.ARC.domain} –ex.– >> test._domainkeys.example.com >> " > This doesn't seem correct. The DNS TXT record should be added to > #{config.ARC.selector}._domainkey.#{config.ARC.domain} (note _domainkey, > not _domainkeys) > > I.e., this is a normal DNS TXT record containing the public key for DKIM > signing. > >> Where can I find this string or where do I have to place it. I am using >> bind9 as dns-handler. > > Read the entire ARC section beginning at > <https://gitlab.com/mailman/mailman/blob/master/src/mailman/config/schema.cf…>. > You have to configure more than just privkey. > > Once you have configured > > enabled: yes > privkey: /some/location/yourprivatekey.pem > selector: test (or whatever you want) > domain: your_domain.com > > The substitutions for #{config.ARC.selector} and #{config.ARC.domain} > should be more clear. >

7 years

[MM3-users] Re: Connection lost during _handle_client()

by Alain D D Williams

On Wed, Nov 27, 2024 at 08:47:38PM -0800, Mark Sapiro wrote: > On 11/27/24 5:58 PM, Alain D D Williams wrote: > > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) connection lost > > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) Connection lost during _handle_client() > > > > I am concerned about the connection lost message above. > > > It is normal and not a concern. > > > > Mailman sees it, the message ID matches that at the end of the first line > > in the exim log (above): > > /var/log/mailman3/mailman.log > > Nov 28 00:59:45 2024 (1268377) ACCEPT: <Z0fAe9xODd2y33N8(a)phcomp.co.uk> > > > So Mailman got the message and accepted it. > > > > Is there any more logging that I can look-at/switch-on to see what is happening ? > > Is there anything else in mailman.log? Does the message get archived? > Is there anthing in any of Mailman's var/queue/* directories? /var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are being continually read & replaced by other files of similar names - like 1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck The process doing this is a 'qrunner' I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log [pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28 17:02:18 2024] GET /mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk => generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 1) Yes: the mail list is chat(a)bray.phcomp.co.uk /var/lib/mailman3/queue/shunt/ contains 4 .pck files. > Is Mailman core running? Systemctl says so & ps shows me one 'master', several 'runner' & 2 uwsgi > Does `mailman members --nomail enabled` list any members? Yes: it gives the list that I expect. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 11 months

[MM3-users] Re: Auth question

by David Krantz

On Sat, Apr 1, 2017 at 6:36 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > No, I'm using Django 1.9.9. I suppose that means it will quit working if > I upgrade to Django 1.10. > > So, I updated my urls to > > url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), > > and updated the attached files at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. Very good. That will be helpful. Now everything works for me except the archiver. There I get strange errors where it requires authentication. I _have_ set MAILMAN_ARCHIVER_KEY (in production.py) and api_key in mailman_hyperkitty.conf to the same value within single quotes. This is probably something extremely silly that my jetlagged brain cannot see. [mailman.log] Apr 09 19:10:42 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:44 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:44 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:45 2017 (14383) HyperKitty failure on https://example.com/archives/api/mailman/archive: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:45 2017 (14383) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> Apr 09 19:10:45 2017 (14383) Traceback (most recent call last): File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> No big deal for me currently, but as I have an archiver I must find out either how to activate it or how to completely remove it. I like having the option, for some kinds of lists archives are useful. Cheers // David

9 years, 7 months

[MM3-users] Re: Bottom line of message footer

by Brian Carpenter

On 2/14/21 9:05 PM, Mark Sapiro wrote: > On 2/14/21 5:40 PM, Tom Stoddard wrote: >> Here's another question that I have. A regular message just came into my >> email from one of the lists I'm a member of and it had a 3 line footer. >> The first two lines are fine, they just include the list's email address >> and an address to send unsubscribe requests to. The third line is this: >> >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> It looks to me like it should be a link to the group's list info page. >> Is this a bug or is there something I can do to fix it? It looks like it >> might be missing a forward slash after the first "s". > This is a list whose msg_footer was imported by The Mailman 3 process > that imports Mailman 2.1 lists. This import process will recognize the > default msg_footer and not create a list specific template for it, but > other things in the footer result in a list specific template which > needs to be reviewed for issues like this. > > The way for you to fix it is to create a list:member:regular:footer (and > maybe a list:member:digest:footer) template in your web UI which will > then override the existing list specific template. The available > replacements are listed at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. > In templates they are all $ strings, e.g. $name. The %(name)s > replacements are Mailman 2.1 and won't work. Also, there is no > replacement for web_page_url because Mailman Core doesn't know what that > is, so you have to include the actual 'https://.../' value if you want > to include a web link. Thank you Mark. @Tom the templates you want to modify to add a Mailman 3 footer to replace the above are: Regular Message Footer Digest Footer -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 8 months

[MM3-users] Re: How to delete empty archives by script?

by Andreas Vetter

Am Thursday, 8 October 2026, 15:23:44 Central European Summer Time schrieb Mark Sapiro: > On 10/8/26 5:03 AM, Andreas Vetter wrote: > > Cool. And since there are a lot of empty archives: How would I find the > > empty archives to feed to this? Can MailingList.objects.get() come up > > with something like a number of archived mails or threads or used space? > > Something like > ``` > > >>> from hyperkitty.models import MailingList > > >>> for mlist in MailingList.objects.all(): > ... if len(mlist.emails.all()) == 0: > ... print(mlist.name) > ... > ``` > will print the names of all empty archived lists. either replace > `print(mlist.name)` with `mlist.delete` or add `mlist.delete` (indented > the same amount) after `print(mlist.name)` to delete them. First try, first problem: (venv) mailman@lists:~> django-admin shell Python 3.11.15 (main, Aug 14 2026, 20:29:30) [GCC] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import MailingList Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/venv/lib64/python3.11/site-packages/hyperkitty/models/ __init__.py", line 25, in <module> from .category import ThreadCategory File "/opt/mailman/venv/lib64/python3.11/site-packages/hyperkitty/models/ category.py", line 64, in <module> class ThreadCategory(models.Model): File "/opt/mailman/venv/lib64/python3.11/site-packages/django/db/models/ base.py", line 129, in __new__ app_config = apps.get_containing_app_config(module) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib64/python3.11/site-packages/django/apps/ registry.py", line 260, in get_containing_app_config self.check_apps_ready() File "/opt/mailman/venv/lib64/python3.11/site-packages/django/apps/ registry.py", line 137, in check_apps_ready settings.INSTALLED_APPS File "/opt/mailman/venv/lib64/python3.11/site-packages/django/conf/ __init__.py", line 102, in __getattr__ self._setup(name) File "/opt/mailman/venv/lib64/python3.11/site-packages/django/conf/ __init__.py", line 82, in _setup raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. I don't see INSTALLED_APPS in any of the configuration files. Where should this be defined? -- TIA, Andreas

1 month

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Thomas Ward

See, that's the oddness. There appears to be SOME weird mail loop here where $ORIGIN (MS365/Exchange) hands it once, then there's back-and-forth between SMTPPROXY and Mailman. IT's really odd how it behaves, and I have no explanation for it. Right now I'm away from the office where this happens, but when I'm back there I'll grab logs from both sides. Thomas On 12/5/23 17:54, Mark Sapiro wrote: > On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >> We use a multi-hop SMTP system to go from the inside of our network >> out to the Internet at the domain test.lists.example.com. >> >> The setup is this way for ingress: >> >> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >> Connector) -> Mailman for delivery to listserv >> >> Egress is this: >> >> Mailman -> Postfix SMTP Relay (smtpproxy) -> INTERNET >> >> -- >> >> When a message is sent an invalid list (we'll call it >> invalid(a)test.lists.example.com) we end up with a nasty side effect in >> the system. The "no such recipient" response gets sent to the >> smtpproxy machine and then *it gets redelivered back to Mailman* as a >> redelivery as if it isn't accepting a permanent-failure condition code. > > > I don't understand why this is happening. Whatever MTA is seeing the > "no such recipient" status and creating the response DSN should be > sending it to the envelope sender of the original message so it should > not be sent to the invalid mailman address. Is one of the MTAs in the > delivery chain to Mailman rewriting the envelope sender? > > What are the MTA log messages from all the MTAs whos logs you have > access to? >

2 years, 11 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >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. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew.

3 years, 1 month

[MM3-users] Re: Pd CRON mailman gatenews

by Pierre Malard

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

3 years, 7 months

[MM3-users] Re: Manual setup - permissions

by Abhilash Raj

On Mon, Sep 23, 2019, at 3:02 AM, Tobias Hachmer via Mailman-users wrote: > Hi Mark, > > thanks for your response. > > On 9/23/19 1:29 AM, Mark Sapiro wrote: > > On 9/22/19 2:11 AM, Tobias Hachmer via Mailman-users wrote: > >> > >> Now, running the scheduled tasks (which run from user+group "nginx") for > >> django I ran into permission problems, because the nginx user can't > >> access/write to the needed files in /opt/mailman3/core/... > >> > >> I would appreciate any hints how to run the different peaces of mailman3 > >> with the correct user/groups/permissions. > > > > > > Set up everything as user:group mailman3:mailman3. I.e., > > > > chown -R mailman3:mailman3 /opt/mailman3/web > > > > and set the uwsgi service to drop privileges to user+group "mailman3". > > So simple, now the scheduled tasks are working, but the whole web > service did not work because the web server user nginx can't access and > write to the uwsgi socket anymore /opt/mailman3/web/project/run/uwsgi.sock. > > # chown -R nginx:mailman3 /opt/mailman3/web > > This works for all. But isn't it a security risk that e.g. manage.py and > settings.py is read- and writeable by the webserver? You just need them to be readable, not writable. You could possibly use xattrs to do just grant read privs. You could also configure uwsgi to create a socket somewhere nginx can read it, `/var/run/uwsgi.sock` should be good enough. You can in theory also try https://uwsgi-docs.readthedocs.io/en/latest/Systemd.html for systemd setup in which case you don't have to manually create sockets as systemd can do that for you. > > Regards, > Tobias > > > _______________________________________________ > 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/ > > > *Attachments:* > * signature.asc -- thanks, Abhilash Raj (maxking)

7 years, 1 month

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

by Abhilash Raj

> On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > On Sat, 13 Mar 2021 14:46:55 -0500, > Mark Sapiro wrote: >> >> On 3/13/21 11:14 AM, John Covici wrote: >>> >>> Now one thing came up while trying to create the database, I got a >>> traceback complaining about a revision error because gentoo had a >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I >>> upgrade mailman, am I going to have to do something to the database as >>> well and why should the database have some kind of reference to the >>> mailman version? >> >> >> I don't know why this is an issue. You shouldn't need to do anything >> with the database when you upgrade. Please post the full traceback and >> error message. > > Sorry I can't reproduce it, after dropping and recreating the database > the error went away, but it was in alembic and it was talking about an > invalid revision and gave a long hex string. > My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2). But that’s just my guess without looking at the traceback. > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.com <mailto:covici@ccs.covici.com> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

5 years, 8 months

[MM3-users] Re: Confusing mailman user model

by Gilles Filippini

Mark Sapiro a écrit le 19/07/2020 à 17:30 : > On 7/19/20 8:10 AM, Gilles Filippini wrote: >> Hi, >> >> I'm trying to understand the Mailman user model, and I'm confused about >> the respective roles of tables 'auth_user' and 'user'. > > > auth_user is a Django auth table. These are the users listed in the > Django admin web UI. > > user is Mailman core's users. > > >> Both have an 'id' column referred to as 'user_id' when used as a foreign >> key. But there seems to be no relation at all between them as they use >> different ids for the same user. > > > Right, they are unrelated. > > >> Our mailman server was migrated from mailman2 to mailman3 about 1.5 year >> ago, and there is an inconsistency I'd like to fix: >> 2 of our users have a registered Mailman account with their respective >> email addresses in table 'auth_user', but these very same addresses in >> the 'address' table are linked to another old admin account in the >> 'user' table. > > Their Mailman account is the 'old' one. the auth_user account is a > Django account >> >> Then if add one of these addresses as a domain owner, it it the old >> admin address which is selected instead. How could I fix that? > > > That's because domain owner in a Mailman thing and involvs the Mailman > user. You could delete the Django users via the Django admin UI and then > re-register them via Postorius. That *might* work. When login into postorius, it is the Django account that is used, right? Then how is the mailman account retrieved from there? It seems UUIDs are used in the process, but I fail understanding how, so far. Wouldn't it be safe to retrieve the new Mailman account associated to these Django users, and link there emails from 'address' table' to them? _g.

6 years, 3 months

[MM3-users] Re: hyperkitty_import Unicode Errors

by Stephen J Turnbull

On 2023-05-07 07:39 Mark Sapiro writes: > On 5/6/23 11:27, Dave Hall via Mailman-users wrote: >> django.db.utils.OperationalError: (1366, "Incorrect string value: >> '\\xE1\\x90\\xA7\\x0A\\x0AO...' for column >> `mailman3web`.`hyperkitty_email`.`content` at row 1") >> >> Is there a known cause for this? Almost always nonconforming user clients. You write "frequently", but I'm guessing it's maybe 1% or 2% of all the messages, right? I suspect it's a particular author or institution using such a client. >> Is it fixed in some release more recent than 0+20180916? This is almost surely not something we can fix. Based on the error, it's in third party code (Django) that we import. It's possible we could provide a more explanatory message, but the only thing we can sensibly do is hold the message for an admin to edit it by hand. As long as the text in question and the Content-Type header aren't too sensitive, we can help with identifying charset (often UTF-8 as Mark suggests but why someone would be encoding FINAL MIDDLE DOT is a mystery to me). > I'm not sure what's going on here. My first thought is the database is > MySQL or MariaDB and this is a 4-byte UTF-8 encoding and the database > column charset definition is utf8 and not utf8mb4, but > '\\xE1\\x90\\xA7\\x0A\\x0A' is the 3-byte UTF-8 encoding for CANADIAN > SYLLABICS FINAL MIDDLE DOT ('\\xE1\\x90\\xA7') followed by two > newlines. so I'm not sure what the issue is. I'm guessing home-made client, possibly Asian or a spammer, which provides no content-type header. Even today I see raw 8-bit encoded text without an encoding spec from legitimate Japanese and Chinese sources, and of course with spammers all bets are off -- they might even do it deliberately to crash filters. -- University of Tsukuba　　　　　　　　　　　　 Faculty of Policy and Planning Sciences Tennodai 1-1-1, Tsukuba 305-8573 JAPAN tel/fax: +81-29-853-5091 turnbull(a)sk.tsukuba.ac.jp 　　　　　　　　　　　　　　https://turnbull.sk.tsukuba.ac.jp/

3 years, 6 months

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

by David Newman

On 1/7/22 2:48 PM, Mark Sapiro wrote: > On 1/7/22 1:51 PM, David Newman wrote: >> >> However, there's no evidence test messages to the list are going out. >> (Nondelivery was the reason I was mucking around in the admin panel in >> the first place.) >> >> The Postfix log shows delivery to the list address. >> >> MM3's smtp.log shows the usual handshake. >> >> However, I do not then see messages going out to subscribers in the >> Postfix log, and as one of those subscribers I do not receive a copy >> even though my preferences are set to receive my own posts. > > > Are the messages in Mailman's var/queue/shunt queue? There are 24 messages in the shunt queue, the most recent of which is a digest from 0000 hours today. The test messages I sent later today are not there. There are also 13 messages in the out queue. I can't read these as the filenames appear to change on every invocation of ls. > Are there errors > and tracebacks in var/logs/mailman.log? Not in response to today's test messages. Here is an entry of a test message I sent going to Hyperkitty. Jan 07 12:49:03 2022 (252309) HyperKitty archived message <6e88ec49-1326-92f9-aa17-1d4c1d6828be(a)domain.tld> to https://lists.domain.tld/archives/list/listname@lists.domain.tld/message/FH… But the Postfix log doesn't show it being distributed to me or anyone else. Oddly, neither of the two list owner emails (me and someone else) show this message in the archive via the admin panel. However if I log in as the list owner directly to the archives: https://lists.domain.tld/archives/ I can see today's test posts if logged in as the list member, but do not see the posts if logged directly into the archive as the Django superuser. The nondelivery of list mail is more serious than the archive problem, though. Thanks in advance for further troubleshooting clues. dn > >

4 years, 10 months

[MM3-users] Re: Counter-intuitive header filter processing

by Jonas Meurer

Hi Mark, Am 18.09.2018 um 20:48 schrieb Mark Sapiro: > On 09/18/2018 10:26 AM, Jonas Meurer wrote: >> >> Apparently, that's not the case. If the default message acceptance >> setting for members is set to "reject", then mails from >> *(a)freesources.org get rejected even though the header filter says >> "accept". In other words, the default message acceptance action seems to >> overrule any header filters. >> >> Is this expected behaviour? > > > Yes. Rules are normally checked in a sequence defined in > mailman/chains/builtin.py and that sequence checks several things > including member moderation before checking header matches, so if > "Default action to take when a member posts to the list" is anything > other than "Default processing", that action will take precedence over > header matches. Thanks for the clarification. Maybe then the description for chain "accept" in postorius needs to be adjusted. Currently it says "Accept immediately (bypass other rules)". This gives the impression, that it will overrule the default action. A related followup question: what configuration is recommended for an announcement list where only specific senders (e.g. sender(a)example.org) should be allowed to post and mail from all (other) subscribers should be rejected? The only way I see to achieve this currently is: * Set default action for member posts to "Default processing" * Add a header filter to accept "sender(a)example.org" * Add a header filter to reject ".*" In my eyes, that's very counter-intuitive and cumbersome to configure. But maybe I just missed a more obvious and elegant solution to achieve the same? And one more comment: if I make the list an "anonymous list" (i.e. "hide the sender of a message, replacing it with the list address"), then header filters for the "from" header don't work any longer. That's kind of unexpected as well. I would have expected mailman to process the header filters at reading the incoming mail, not after rewriting headers of the outgoing mail? Cheers jonas

8 years, 1 month

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

by Torge Riedel

Am 18.01.20 um 23:14 schrieb Mark Sapiro: > On 1/18/20 6:13 AM, Torge Riedel wrote: >> So now back to good. I checked all the logs prior to restarting the >> service in directory /opt/mailman/var/log, but I do not see any errors. >> And the master was still running, I would expect that the master will >> start / restart a runner in case it died? > > What's in /opt/mailman/var/log/mailman.log? There should be entries like > > Jan 18 13:51:11 2020 (11700) xxxx runner started. > > for each runner every time it starts and like > > Jan 18 13:47:31 2020 (10096) xxxx runner caught SIGTERM. Stopping. > Jan 18 13:47:31 2020 (10096) xxxx runner exiting. > > for each runner every time it stops, but with perhaps a reason other > than `caught SIGTERM` > > That should at least tell you when they stopped. Also, if they stopped > for some reason. The master will only restart runners that exit if they > exit because of SIGUSR1 or some internal error and even then, only the > configured max_restarts number of times. > > Do you have a logrotate script for the logs in /opt/mailman/var/log, and > if so, does it have a postrotate script that signals Mailman to reopen > logs other than by a `mailman reopen` command, perhaps by signaling the > master with other than SIGHUP? > Hi Mark, I checked the logs for such entries and I do only see them when the logrotation runs and from yesterday where I restarted the service by myself. So - yes, I have logrotation configured. The logrotation has a postrotate script configured which executes `systemctl reload mailman` and I see in the logs, that it handles SIGUSR1. This happens daily in the morning and runs - for what I see - without any problems. If I understand you right I should change it to "reopen" instead of "reload". I think this is something I have to pass to mailman executable itself instead to systemctl, right? Best regards Torge

6 years, 9 months

[MM3-users] Re: Error while mass operation, no progress display while mass operation is running

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/6/25 04:53, Markus Grandpré wrote: > > Unfortunately, I have not found any error message in the log > > files. > > If you are using uWSGI, a harakiri timeout should be logged in uWSGI's log. I think gunicorn logs to access.log and error.log in the Mailman logs directory. I would think it would log 500 level events, that indicates server trouble. > > Regardless of whether a mass operation process runs without errors or > > continues to run despite an error, I find it hard that Postorius does > > not display the progress of such a mass operation in order to monitor > > the process, as mass operations with more than 1000 members are very > > time-consuming. Perhaps this could be changed in a future version of > > Postorius? > > This is a reasonable request. The best place for such a request is > https://gitlab.com/mailman/postorius/-/issues/new It's reasonable, but for unsubscribe Postorius invokes the mass remove REST API. So to report progress there it would require new code in Mailman and mailmanclient to report progress, or Postorius could use an explicit loop over addresses as mass subscribe does -- which would be noticably slower, I suspect. Periodic heavy use of mass operations is a common use case at universities. It's not uncommon for each term to see thousands of list averaging scores of subscriptions or unsubscriptions, with both number of lists and average roster size spike at academic year transitions when departmental and university-wide lists turn over. We should look at speeding up mass operations. I suspect internally Mailman is looping over individual addresses, probably creating a separate RDBMS transaction for each one. It should be possible to batch these, allowing the RDBMS to optimize its own table locking. Perhaps for the university use case it would make sense to even have Mailman multiplex these transactions across multiple lists being accessed at the same time. Steve

1 year, 9 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/27/22 01:35, Odhiambo Washington wrote: > > 3. Lastly, I needed to add the relevant options under > > the SOCIALACCOUNT_PROVIDERS = in settings.py. > > > > Now I have this: > ... > > And those are working but was wondering what to add for Twitter. > > > I see from another post that you've decided against using Twitter, but > to answer the question, Twitter does not require adding anything to > SOCIALACCOUNT_PROVIDERS. > I tried it and ended up with: ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server Error: /accounts/twitter/login/ Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth/views.py", line 43, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/base/mixins.py", line 18, in dispatch return self.login(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth/views.py", line 75, in login client = self._get_client(request, callback_url) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth/views.py", line 49, in _get_client app = provider.get_app(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/providers/base/provider.py", line 30, in get_app return adapter.get_app(request, self.id) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 204, in get_app app = SocialApp.objects.get_current(provider, request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 31, in get_current app = self.get(sites__id=site.id, provider=provider) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", line 650, in get raise self.model.DoesNotExist( allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching query does not exist. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

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

by Jens Günther

Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… How could I check, that the setting is used!? But maybe some additional information: - I use the Debian installation on a stable buster, so mailman is version 3.2.1 - I use apache2 as my web-server and use the given alias-conf-file - Python is version 3.7.3 - Postorius is Version 1.2.4 - HyperKitty is version 1.2.2 -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains What do I miss? Or where to investigate? Thank you in advance, best regards. By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html Am 18.03.21 um 21:52 schrieb Mark Sapiro: > On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? > > Set FILTER_VHOST = True in your settings_local.py or where ever you put > your site Django settings. > >

5 years, 7 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Fri, Dec 23, 2022 at 4:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/22 16:03, Odhiambo Washington wrote: > > > > There is just one more thing - I have this in settings.py: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > And what are LOGGING['handlers']['file']['level'], > LOGGING['handlers']['file']['class'] and > LOGGING['handlers']['file']['formatter'] > Those are left as defaults in my setup.py. > > However, the referenced file is ever empty. At what point is it supposed > to > > record anything? > > What is logged depends on `level` but even with `DEBUG` not much routine > stuff is logged. See https://docs.djangoproject.com/en/3.2/topics/logging/ I will read that and see if I get to pick up something. And now I am having a problem with mod_wsgi. First, the URL displayed when I load the page looks bogus to me. While I expect the URL to be https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is an extra /mailman3! So I have; 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - working, or appears to. 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - working, or appears to. 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, or appears to 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, or appears to 5. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… - This throws an exception error when I click "Manage Subscription". -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ And while I do not quite understand the error itself, there is also one particular line that I also saw that has left me baffled: [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client 197.232.81.246:13865] AH00128: File does not exist: /usr/local/www/apache24/data/archives/list/ kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, refe rer: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

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

by Onyeibo Oku

On Thu, 13 Oct 2022 12:12:32 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/12/22 22:03, Onyeibo Oku wrote: > > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" > > which should correspond to "/usr/lib/mailman/mm/var/*" on my > > instance. However, I don't see any instructions on how to get the > > "/mm" folder and the associated sub-folders. I just have > > "/usr/lib/mailman" > > I think if you have `var_dir: /usr/lib/mailman/mm/var` in the > /etc/mailman3/mailman.cfg file you create per > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…, > then starting Mailman core `/usr/lib/mailman/venv/bin/mailman start` > will create it. > Thanks Mark, that was very helpful. I now have "mm" folder. I have reached the section "Starting Mailman automatically". After creating the cfg file. Here is what I get: # systemctl status mailman3 mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2022-10-19 19:52:03 UTC; 4min 51s ago Process: 782 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 156ms Oct 19 19:52:02 mail.server.tld systemd[1]: Starting mailman3.service - GNU Mailing List Manager... Oct 19 19:52:03 mail.server.tld mailman[782]: Traceback (most recent call last): Oct 19 19:52:03 mail.server.tld mailman[782]: File "/opt/mailman/venv/bin/mailman", line 33, in <module> Oct 19 19:52:03 mail.server.tld mailman[782]: sys.exit(load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')()) Oct 19 19:52:03 mail.server.tld mailman[782]: File "/opt/mailman/venv/bin/mailman", line 25, in importlib_load_entry_point Oct 19 19:52:03 mail.server.tld mailman[782]: return next(matches).load() Oct 19 19:52:03 mail.server.tld mailman[782]: StopIteration Oct 19 19:52:03 mail.server.tld systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Oct 19 19:52:03 mail.server.tld systemd[1]: mailman3.service: Failed with result 'exit-code'. Oct 19 19:52:03 mail.server.tld systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. Mailman starts well from virtual environment though, ... but systemd doesn't replicate that success. Regards Onyeibo

4 years

[MM3-users] Re: Confirm on mass subscription

by tlhackque

On 05-Jul-17 22:09, Mark Sapiro wrote: > On 7/5/17 1:48 PM, David Krantz wrote: > > >> Is there a way of requiring all mass subscribed users to confirm their >> email adress? I have an use case where we have a current mail list but >> when moving it to mailman I for different reasons would like to >> confirm all subscribers. Some very shallow testing suggests that if I >> just add them using mass subscribe, they will not have to confirm at >> all. >> >> I have yet to upgrade to 3.1 but I will do so in due time. > > In MM 2.1, you just send the users invitations rather than subscribing > them. In MM3/Postorius, this does not seem to be an option at present. > Actually, 2.1 lets you do it either way. The first radio button on Mass Subscriptions is: "Subscribe these users now or invite them? " MM 2.1 also allows control of whether the new subscribers and/or list owner are notified. And it allows custom text to be added to the invitation/notification (when one is sent). MM3 has none of these controls. Postorious issue #203 and mailman #362 refer to the MM 2.1 regressions. However, I read this somewhat differently: given a list with subscribers (however they were subscribed), it is sometimes useful to be able to ask the members to re-confirm their address/interest. For example, when there's a change of policy (terms of use), or when local opt-in regulations require that that opt-in be reconfirmed periodically. It's handled out-of-band now, but this would seem to be something that Mailman could manage - change users' state to "unconfirmed" and issue the re-invite/re-subscribe notice. But there are some details: re-confirmation probably doesn't want to require moderator re-approval (at least not always). How this interacts with "don't deliver mail from this list" needs definition (probably overrides), but some members (notably moderators/owners/robots) need to be exempt. And like 2.1, the user notification needs to be different to explain that it's a re-confirmation.

9 years, 4 months

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

by Quanah Gibson-Mount

--On Wednesday, March 16, 2022 7:54 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/16/22 12:56, Quanah Gibson-Mount wrote: >> >> Thanks for the response. Unfortunately I'm currently stuck with the >> junk shipped by Debian. Yet another reason to move to a standalone >> install and avoid their broken packages. > > > In the mean time, you can handle these issues via REST or via `mailman > shell`. For example: > ``` > $ mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > >>> pendings = getUtility(IPendings) > >>> sub_mgr = ISubscriptionManager(m) > >>> for token, data in pendings.find(pend_type='subscription'): > ... if data['token_owner'] != 'subscriber': > ... continue > ... if data['email'] != 'user(a)example.com': > ... continue > ... sub_mgr.confirm(token) > ... > >>> commit() > ``` > > The above will find the pending confirmation for user(a)example.com on the > list list(a)example.com and confirm it. Hi Mark, I gave this a whirl. First I just had it print out all the emails waiting for confirmation just to confirm I saw the user in question had a pending subscription request, which they did (two in fact for the same email). So then I ran your code to confirm it, and it blows up with an error: >>> for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['email'] != 'xxxxxxxx(a)xxxxx.org': ... continue ... sub_mgr.confirm(token) ... Traceback (most recent call last): File "<console>", line 6, in <module> File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 545, in confirm workflow.restore() File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 149, in restore setattr(self, attr, data[attr]) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 119, in address_key assert self.address is not None AssertionError Regards, Quanah

4 years, 7 months

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

by Henrik Rasmussen

Mark Sapiro wrote: > On 6/6/19 6:02 AM, Henrik Rasmussen wrote: > > Still, attachments (PDF) is removed by Mailman. I as > > the list admin to send a new mail, but hold it back, to see what type it is. > You have to add the MIME types for the attachments you want kept the the > list's pass_types. You need to do this via mailman shell or REST as it > isn't currently exposed in Postorius. > Here's an example from a list that wants to accept PDFs as well as word > processing and spreadsheet documents. Note that nappdf and x-pdf are > uncommon PDF subtypes that I have seen. > ['multipart', > 'message/rfc822', > 'text/plain', > 'text/html', > 'application/pdf', > 'application/nappdf', > 'application/x-pdf', > 'application/rtf', > 'application/vnd.oasis.opendocument.spreadsheet', > 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', > 'application/vnd.ms-excel', > 'application/vnd.oasis.opendocument.text', > 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', > 'application/msword' > ] Thanks, done! However, PDF's and an image is still filterd out. On May 21st the list admin tested by setting Filter content to 'No'. As expected, the mail was received as sent, with PDF attachment, inline image and HTML intact. Resending this mail to a newly created test list (from Outlook by selecting Resend, which does exactly just that, the mail was again received as sent, even the config of Alter Messages as the same as the list having the problem. The difference was that list(m.pass_types) is [] Now, setting m.pass_types = ['multipart', 'message/rfc822', 'text/plain', 'text/html', 'application/pdf', 'application/nappdf', 'application/x-pdf', 'application/rtf', 'application/vnd.oasis.opendocument.spreadsheet', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', 'application/vnd.ms-excel', 'application/vnd.oasis.opendocument.text', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/msword'] on the new testlist and resending the mail again, the mail still came out intact. So I guess the problem must be something complete different. Also I wonder why a newly created list accepts the PDF in question, when list(m.pass_types) is []. /Henrik Rasmussen

7 years, 5 months

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

by Odhiambo Washington

On Mon, Dec 23, 2024 at 1:37 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/24 05:25, Odhiambo Washington via Mailman-users wrote: > > > > Perhaps you can make a feature request in gitlab? > > And while at it, please add: mailman nonmembers LISTSPEC > > With the later, it would be easier to delete non-members from the CLI as > > well. > > > 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 ``` (venv) mailman@eu:~$ mailman members --role nonmember kictanet(a)lists.kictanet.or.ke Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/mailman/commands/cli_members.py", line 223, in members display_members(ctx, mlist, role, regular, File "/opt/mailman/mm/venv/lib/python3.11/site-packages/mailman/commands/cli_members.py", line 106, in display_members dn = address.display_name or member.user.display_name ^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'display_name' (venv) mailman@eu:~$ ``` From Postorius, there are 806 nonmembers. -- 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, 10 months

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

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: > On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> Since I made all the mailman3 enviroment wide server open (not using >> venv) I already executed the migration doing a >> >> su -m mailman3 -c "python3 manage.py collectstatic" >> su -m mailman3 -c "python3 manage.py migrate" >> >> Being mailman3 the user who runs all of mailman3 related stuff >> >> I had problems doing the migrate part, showing an error of lacking >> perms. I solved it running the migration under root (I know it could >> be trouble after, but...) > > It would be much better to identify the problem files/directories and > adjust their ownership. It is possible that running stuff as root in > the past left things owned by root causing the issue. The problem was in the intent of execute one of the migrate parts and showed about python files. I'm pretty sure that I've been very carefull not running things as root before as I know it can mess all up. But this time it was an dead end and I needed to go through. In a few days I will upgrade another server. I will document the error if I find it again. > >> >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS > I will try to trace it and comment what I find. Thaks a lot for your support. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

4 years

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Guillermo Hernandez (Oldno7)

El 4/4/23 a las 3:31, Mark Sapiro escribió: > Guillermo Hernandez (Oldno7) wrote: > >> I thought I said it: I reboot this server everyday at 06:40 CEST time. >> That's why I'm sure it's not an undetected problem for weeks. The lists >> in this last upgraded server are with daily traffic. I'm suscribed to all. > > I've looked at this a bit further. Prior to Mailman core 3.3.4 we required aiosmtpd>=1.1. In 3.3.4 we required aiosmtpd>=1.4.1 and now we require aiosmtpd>=1.4.3. The code in aiosmtpd that triggers the issue in the socket module was added in aiosmtpd==1.3.1. So it is likely that your prior Mailman core version was <3.3.4 and your aiosmtpd dependency was <1.3.1, so the Mailman upgrade would also have upgraded aiosmtpd to a version which triggered the socket issue. I think tou are completely right about the aiosmtpd changes. But I had mailman 3.3.5 installed since end of september of '21, mailman 3.3.6 since end of october '22, and mailman 3.3.7 since the beginning of december of last year. You can search the list and find my messages about that upgrades and problems I had with them. Just to make it clear: It happened upgrading from 3.3.7 to 3.3.8 The upgrade procedure I did all the times is pip install --upgrade django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi and if I see some trouble I did it with a --force-reinstall parameter (not that I remember it happened last times that I upgraded) (and then the collectstatic, etc.) If I missed something, I don't know. > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at:https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/mess… > > This message sent toguillermo(a)querysoft.es > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 7 months

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

by Mark

On 2023-10-11 04:38, Mark Sapiro wrote: > > Steve has addressed your issues with multiple Django admin commands, > some of which apparently don't reference the correct settings. > >> The format of my final line is different to yours ... > It is not a clue as to the problem. The format of that > `representation` changed in HyperKitty 1.3.5. What is your version? > HyperKitty version 1.3.4 > What happens if you do, with the appropriate Django admin and list > name, > ``` > python3 manage.py update_index_one_list thepost(a)example.com > ``` > Thank you Mark and Steve, That worked a treat! python3 manage.py update_index_one_list thepost(a)example.com Running that command returned the message "Indexing 12 emails", then returned to the shell prompt when done. It successfully indexed the messages in the archive, and I could then do a search on the existing messages. On 2023-10-11 00:54, Stephen J. Turnbull wrote: > The process of search index construction is both CPU and wall-clock > time intensive. For this reason, the cron jobs that do regular > index updating (I think once an hour?) are separate from the utility > that constructs the index in the first place when you have existing > archives (either migrated from another MLM such as Mailman 2, or if > you're upgrading to better archive software). The messages in the archive came directly from the list (ie. they weren't imported). It looks as though running that command flushed out a cobweb, as the hourly indexing is now happening. Some time after I had run that indexing command, a new message was posted to the list, and appeared in the archive. I searched (a)immediately, (b) 15 mins after, and (c)an hour and a bit after. As Steve said, the newer messages are automatically indexed hourly. So it wasn't until after that hourly index that the search terms in the newer messages were showing up in the search results. I can't say I understand the inner workings of the process yet, but we have a working archive search and I'm very happy about that. Thank you again, Mark

3 years, 1 month

[MM3-users] Re: update problems in virtualenv

by Christian H. Kuhn

Hi Mark, thank you for your answer. I did both updates, and haven't seen the warning since. KR QNo Am 05.11.2025 um 01:40 schrieb Mark Sapiro: > On 11/4/25 11:47, Christian H. Kuhn via Mailman-users wrote: >> Hi all, >> >> i followed https://docs.mailman3.org/en/latest/install/virtualenv.html >> and ran in different problems. Here's the first. >> >> All mailman-web runjobs report: >> >> System check identified some issues: >> >> WARNINGS: >> ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: >> settings.ACCOUNT_LOGIN_METHODS = {'username', 'email'} >> ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: >> settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', >> 'password2*'] > > > This is https://gitlab.com/mailman/mailman-web/-/issues/37 fixed for the > next release. There are two ways to fix this. You can upgrade mailman- > web in your venv by activating the venv and doing > > pip install --upgrade git+https://gitlab.com/mailman/mailman-web > > Or you can add the following to your settings.py after the imports from > mailman_web.settings.base and mailman_web.settings.mailman > ``` > del ACCOUNT_EMAIL_REQUIRED > del ACCOUNT_AUTHENTICATION_METHOD > ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ``` > >> (venv) mailman@bywater:~/mm/var/data$ pip install --upgrade >> mailman==3.3.10 >> Collecting mailman==3.3.10 > ... >> INFO: pip is looking at multiple versions of mailman to determine >> which version is compatible with other requirements. This could take a >> while. >> ERROR: Could not find a version that satisfies the requirement >> nntplib; python_version >= "3.13" (from mailman) (from versions: none) >> ERROR: No matching distribution found for nntplib; python_version >= >> "3.13" >> >> standard-nntplib 3.13.0 is installed. > > This is an issue with Mailman 3.3.10 and Python >= 3.13 fixed by > https://gitlab.com/mailman/mailman/-/merge_requests/1348 > > Here again if you want to upgrade Mailman core you can do > > pip install --upgrade git+https://gitlab.com/mailman/mailman > > to get the latest from gitlab. >

1 year

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/14/22 08:21, Stephen J. Turnbull wrote: > Yes. The C-T-E on all the multipart parts was quoted-printable, not > allowed under RFC 2045. That's what I expected (we're talking about Apple Mail), but thanks for confirming. > The Python email library says the message is defective. Mailman's lmtp > runner in turn rejects the defective message with a 501 status > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… > > It could accept a defective message or one with specific defects, but > this is problematic for further processing. For example, at least one > MUA, Thunderbird, renders such a message with an empty body. Sure, but that's not our problem. I mean, I have my MUA set to ignore HTML so I get empty bodies all the time! :-) We are perfectly within our rights to just let the Apple Mail and Thunderbird users fight about it. :-) If it causes problems for *our* processing, that's another matter. I don't see why it would, though. Whether we *want* to do that depends on how much trouble that causes for our main constituency (list and site admins), and whether we can provide discoverable documentation of the problem. My take is that this seems to be an extremely rare problem, and at least some MUAs are able to read the message, so we should let it through. If we wanted to be really obnoxious, we could add a header to the message This message does not conform to mail standards. Some clients may omit some or all of the content. Or we could make passing it an option, perhaps as a pseudo-content type in "Pass these content types" or as a separate option. I feel strongly enough that Postel implies "let it through" that I'll write up a PR shortly (a few days). Sleep on it, we bring in Abhilash and I guess Barry?, and if you all still don't like it, veto it -- my time is no big deal, it'll only be an hour to put it together I think. Steve

4 years, 6 months

[MM3-users] Re: HyperKitty/Mailman3 issues

by Florian Schulze

On 22 Nov 2018, at 19:53, Mark Sapiro wrote: > On 11/22/18 2:58 AM, Florian Schulze wrote: >> Hi! >> >> I tried setting up Scheduled Tasks as described in >> <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> >> >> but the "runjobs" command can't be found. I see the hyperkitty and >> mailman commands when using "help". > > > Does "help" show a list under [django_extensions] including runjob and > runjobs? > > Is 'django-extensions' in the list of INSTALLED_APPS in your Django > settings? That was the issue. Thanks! >> The "qcluster" service is working. >> >> Using Django 2.1.1 and HyperKitty 1.2.1. >> >> Maybe related to that, I have two issues with archives. >> >> 1. Changing the archiving setting in the Web-UI to something else >> than >> public seems to have no effect. The already archived messages are >> still >> accessible in public. > > > This is related. It is one of the "daily" jobs that updates this. Note > that changing to "private" will require login after the "daily" jobs > run, but changing to "do not archive" will leave the existing archive > accessible. After manually running the daily job, the archive is now private. >> 2. Related to 1., how can I remove a list archive without affecting >> other lists? > > > There's no easy way. For the "prototype" archiver, the archives for a > list are in var/archives/prototype/listname(a)example.com/ and that > directory can be removed, but that doesn't affect HyperKitty. > HyperKitty's archives are in the Mailman database and multiple tables > are involved. > > One could try just removing the row for the list from the > hyperkitty_mailinglist table. That may render the list's archive > inaccessible via the web UI, but I have no idea what would be broken > by > doing this. I hope this will be added at some point. For now I have the archive set to private. Thanks again for the pointers! Regards, Florian Schulze

7 years, 11 months

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

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS While I'm tracing the problem out, this is the configuration I had working and the error it shows after upgrade: <------- snip of settings.py> # COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) # On a production setup, setting COMPRESS_OFFLINE to True will bring a # significant performance improvement, as CSS files will not need to be # recompiled on each requests. It means running an additional "compress" # management command after each code upgrade. # http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression #### activo compresion 18/12/20 COMPRESS_OFFLINE = True ###COMPRESS_OFFLINE = False <---------- end snip> And below is the error it shows: /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" Traceback (most recent call last): File "/usr/local/mailman3/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 279, in fetch_command klass = load_command_class(app_name, subcommand) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 49, in load_command_class return module.Command() File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 274, in __init__ raise TypeError("requires_system_checks must be a list or tuple.") TypeError: requires_system_checks must be a list or tuple. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

4 years

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

by Mark Dadgar

Thanks for the al the help - much appreciated! Mailman3 is a HUGE step up from 2.1.x. Running the commands as the correct user solved my issues. Specially, I ran the import21 command as the “list” user (created by the debian/ubuntu package) and the hyperkitty import command as the “www-data” user. I had to add login shells to the passwd entries for those users to make it happen as they get installed with nologin. I imported a 24G archive inbox and something went wrong along the way - the archives for many months consist of just a single identical thread. Re-running the import results in the following in just a few seconds: www-data@mail:/tmp$ python /usr/share/mailman3-web/manage.py hyperkitty_import -l trackjunkies(a)pdc-racing.net /backups/trackjunkies.mbox Importing from mbox file /backups/trackjunkies.mbox to trackjunkies(a)pdc-racing.net Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now. Any thoughts on how I can re-run the full import to make sure that all the archives are present? Thanks! - Mark ----- mark(a)pdc-racing.net | 408-348-2878 > On Oct 3, 2019, at 9:25 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/3/19 5:17 PM, Mark Dadgar wrote: >> >> I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. >> >> Importing lists from 2.1 has been a real problem. >> >> I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: >> >> — >> mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck >> Traceback (most recent call last): >> File "/usr/bin/mailman", line 11, in <module> >> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() >> File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main >> initialize(config_path) >> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize >> initialize_2(propagate_logs=propagate_logs) >> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 >> mailman.core.logging.initialize(propagate_logs) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize >> _init_logger(propagate, sub_name, log, logger_config) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger >> handler = ReopenableFileHandler(sub_name, path_abs) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ >> self._stream = self._open() >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open >> return codecs.open(self.filename, 'a', 'utf-8') >> File "/usr/lib/python3.6/codecs.py", line 897, in open >> file = builtins.open(filename, mode, buffering) >> PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' > > > This is the issue. I don't know how the Debian packages do this, but I > recommend having a 'mailman' user that owns everything and running > commands as that user. > > >> Error in atexit._run_exitfuncs: >> Traceback (most recent call last): >> File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown >> h.flush() >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush >> if self._stream: >> AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' > > > This is due to the prior permissions error. > >> If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: > > > If there are a lot of members to add, that can take a long time. The > current version of import21 has a progress thermometer for this. > >> — >> Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 >> Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' >> Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration >> msg, msgdata = self.switchboard.dequeue(filebase) >> File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue >> with open(filename, 'rb') as fp: >> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' > > First, I don't know what these messages are. Normally import21 doesn't > send any mail. I'm guessing it's trying to send 'you are subscribed' > notices to the users, but it shouldn't be doing this. > > All these files should wind up in Mailman's var/queue/bad/ directory > with a .psv extension. You should be able to examine them with the > 'mailman qfile' command. > > Whatever they are, the error comes from virgin runner so import21 should > have actually succeeded. Did it import the list? > > >> It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? > > > It makes a weak effort at converting the list's msg_footer and > digest_footer into MM 3 templates in > templates/list/<list-id>/<list-lang>/. These are owned by root in your > case because you ran import21 as root. > > >> Any thoughts on what’s going wrong here? > > > It looks like this may be an issue with the Debian package, at least the > sending of messages part. > > As for the rest, the Debian package should install stuff as a Mailman > user, perhaps 'mailman' or 'list', and you should be running all > commands as that user. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 1 month

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

by Eggert Ehmke

I have a file /opt/mailman/.bashrc file with this line: source /opt/mailman/venv/bin/activate works quite well with systemd. My service file looks like this: [Unit] Description=GNU Mailing List Manager After=syslog.target network.target mysqld.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop [Install] WantedBy=multi-user.target Eggert Am Donnerstag, 20. Oktober 2022, 08:38:05 CEST schrieb Mark Sapiro: > On 10/19/22 21:23, Stephen J. Turnbull wrote: > > Onyeibo Oku writes: > > > Mailman starts well from virtual environment though, ... but systemd > > > doesn't replicate that success. > > > > systemd doesn't know anything about venv. If it's possible to source > > (not call as a command!) the venv bin/activate script via systemd, > > that should fix it. If not, we'll have to figure out what it is that > > the venv provides that the current systemd config does not. I would > > guess that after sourcing the venv's bin/activate > > Our suggested systemd script at > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman > -automatically has > > ExecStart=/opt/mailman/venv/bin/mailman start > ExecReload=/opt/mailman/venv/bin/mailman restart > ExecStop=/opt/mailman/venv/bin/mailman stop > > /opt/mailman/venv/bin/mailman should work whether or not a venv is active. > > Judging from the traceback, Onyeibo Oku's /opt/mailman/venv/bin/mailman > is quite different from mine which is just > ``` > #!/opt/mailman/venv/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' > __requires__ = 'mailman==3.3.5' > 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( > load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')() > ) > ``` > What is yours? and can you start mailman as the mailman user with > ``` > /opt/mailman/venv/bin/mailman start > ``` > without activating the venv?

4 years

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 12:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > > I'm not sure what you mean by drop and recreate the databases. You > should just drop the `social_auth*` tables, or if there's nothing in the > database you want, just starting with an empty database should work. Very good! Thank you very much, I got a bit further. The database contained a couple of test lists that I can recreate, so nothing of value. The strange thing was that drop database followed by create database did not yield an empty database in Postgres. I probably forgot a commit somewhere. I got a bit further. The problem with not being an expert on Django is that the configuration of all web frameworks is that is a bit involved. I have no experience of Django outside of this and I just want to get it running in this case. Now I get the following errors in the mailman_web-log, somehow complaining on the url mapping. ERROR 2017-03-31 00:51:31,558 exception 2456 140113416898304 Internal Server Error: /mailman3/lists/ Traceback (most recent call last): [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/template/defaulttags.py", line 458, in render url = reverse(view_name, args=args, kwargs=kwargs, current_app=current_app) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/base.py", line 91, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/resolvers.py", line 497, in _reverse_with_prefix raise NoReverseMatch(msg) NoReverseMatch: Reverse for 'hk_user_login' not found. 'hk_user_login' is not a valid view function or pattern name. The Django 1.18 points to a Django 1.11rc1, should probably be mentioned. My urls.py (a copy from the docs, I think) from django.conf.urls import include, url from django.core.urlresolvers import reverse_lazy from django.views.generic import RedirectView from django.contrib import admin # Comment the next two lines to disable the admin: #admin.autodiscover() urlpatterns = [ url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', include(admin.site.urls)), ] cheers // David

9 years, 7 months

[MM3-users] Re: Random characters in "The results of your email commands" e-mail

by Jeffrey D

Mark Sapiro wrote: > To understand what's going on, We would like to see the complete, raw > response message. Also, the headers of the message sent to the -request > address, in particular the Content-Type: header of the first text/plain > part and its charset param. I didn't check the source headers... Mailman isn't the issue, my mail client (Evolution) is the problem. Messages sent to the -request@ with Subject: help and message body with my mail signature are working fine. I received the expected response from Mailman. Messages sent to the -request@ with Subject: help and empty message body, gives the random characters response. Instead of leaving the body empty, Evolution paste "Cgo=" into the message body. Mailman reply with the expected "No such command: cg0k" and Evolution couldn't decode the message. Long story short, don't use Evolution ;-) Thanks for pointing me in the right direction! Mail headers: Sent message -request@ (with empty body) ===================================== Message-ID: <eaa8bc6bec172bf3e19700959d6f86f637a3d59c.camel(a)domain.tld> Subject: help From: Jeffrey <jeffrey(a)domain.tld> To: test-jeffrey-request(a)domain.tld Date: Mon, 17 Feb 2020 10:54:13 +0100 Content-Type: text/plain User-Agent: Evolution 3.34.1-3 MIME-Version: 1.0 Content-Transfer-Encoding: base64 X-Evolution-Identity: 1f54715bb67ff0bd5b87ec47786956d762aec607 X-Evolution-Fcc: folder://f23e08ef4c9736554f0b631ce301539d32916444/Sent X-Evolution-Transport: 6fd443d2352de0b9c1126fe4334605581b1903c2 X-Evolution-Source: Cgo= Response message ===================================== Subject: The results of your email commands From: test-jeffrey-bounces(a)domain.tld To: jeffrey(a)domain.tld Content-Transfer-Encoding: base64 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <158193325438.30764.17876047045035004661(a)domain.tld> Date: Mon, 17 Feb 2020 10:54:14 +0100 Precedence: bulk X-Mailman-Version: 3.2.1 X-Evolution-Source: f23e08ef4c9736554f0b631ce301539d32916444 The results of your email command are provided below. - Original message details: From: Jeffrey <jeffrey(a)domain.tld> Subject: help Date: Mon, 17 Feb 2020 10:54:13 +0100 Message-ID: <eaa8bc6bec172bf3e19700959d6f86f637a3d59c.camel(a)domain.tld> - Results: confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end'. subscribe - An alias for 'join'. unsubscribe - An alias for 'leave'. No such command: cg0k - Done.

6 years, 8 months

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

by mhazan＠mandint.org

Le 2022-05-02 17:32, Mark Sapiro a écrit : > On 5/2/22 06:39, Michael Hazan wrote: >> Hello, >> >> When creating a list via postorius, i can see 3 style appear >> (announce, discussion, private). Is it possible to either create a new >> style and add it to that list or modify one of those style ? > > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Thanks i will look into setting up that plugin, hopefully an easier way to do that can make it's way to the default install. >> Also, coming from mailman2, you could directly set the members post >> moderation action when subscribing, now you can only do it via the >> user menu, is there a way to automate this in mm3 ? > > > I don't understand what you mean here. In MM 2.1 a member had only one > setting - moderated yes or no and if moderated there was a list > setting for the moderation action. There was also a list setting for > whether new members were moderated by default. How were you setting > the new member's moderation when subscribing? > > You are correct that when subscribing a new member, the member gets > the default action for members and different action has to be set in a > separate operation. I don't think this is significantly different from > MM 2.1. Also, can you describe what you mean by "automate this". in MM2.1, if you set the list to moderated and default action to hold posting, you can set a some member to be un-moderated (mod bit off) to automatically allow their posting. In the web interface of MM2.1 there is a checkbox with moderated bit on/off on the member list itself, in the postorius interface for MM3 you have to open each members settings page to access that. For automation, as list owner, upon registering a member (via mass subscription) the possibility to change that ? also the me too/dupe setting for example. Thanks

4 years, 6 months

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

by Abhilash Raj

On Mon, Feb 11, 2019, at 2:08 PM, Marvin Gülker wrote: > Hi, > > Am 11. Februar 2019 um 13:20 Uhr -0800 schrieb Mark Sapiro: > > I downloaded the February mbox from > > <https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/export/wlug@l…> > > and imported it to a test list with 'django-admin hyperkitty_import and > > see the same issue. > > Here's the Hyperkitty Mbox for my affected mailinglist: > <https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch…> > > Maildir from my local machine as received from Mailman via e-mail: > <https://files.guelker.eu/misc/tsc-devel.tar.gz> > > > Examination of the mbox shows for the first message [...] > > Note the folding of the header and the double angle brackets. > > I can confirm that I see this behaviour for my affected mailinglist as > well. The Message-ID header is broken over two lines with double angle > brackets in the Hyperkitty MBox linked above: > > Message-ID: < > <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org>> > > However, the original message as it was delivered by Mailman to me does > not have such a weird message-id header: > > Message-ID: > <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org> > > In this message, the header is broken exactly as shown above after the > colon of "Message-ID:". Maybe some problem with parsing long Message-ID > headers, or ones folded over multiple lines? > > With regard to bug reporting on gitlab.com: I already have accounts on a > ton of sites, and at some point I'd actually like to stop creating new > ones all the time... I created an issue on Gitlab for this with this thread: https://gitlab.com/mailman/hyperkitty/issues/216 > > Marvin > > -- > Blog: https://mg.guelker.eu > PGP/GPG ID: F1D8799FBCC8BC4F > _______________________________________________ > 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, 9 months

[MM3-users] Re: Importing Mailman 2 Lists apart from Django

by Brian Carpenter

On 4/30/20 11:59 AM, Mark Sapiro wrote: > On 4/30/20 7:59 AM, Brian Carpenter wrote: >> Hello Mailman Users, >> >> Are there instructions on importing a Mailman 2 list into a Mailman 3 >> core installation only? Does the import21 script not need >> Django/Postorius/Hyperkitty? > > import21 requires only Mailman core. > > >> It seems Django is required to import archives I guess because of the >> use of Hyperkitty. How about importing archives without having a Django >> installation? Is that what the prototype archiver for? > > The only current archive import we support is `django-admin > hyperkitty_import` which imports archive .mbox files into HyperKitty. > > The prototype archiver is just a maildir format collection of messages. > > Converting an mbox file to a maildir is trivial. > > from mailbox import Maildir, mbox > mb = mbox('/path/to/mbox', create=False) > md = Maildir('/path/to/maildir', create=True) > for msg in mb: > md.add(msg) > > >> We are getting ready to start working on a custom forum application for >> Mailman 3 (called Empathy) and I am would like to import some mailman 2 >> archives into the development server to work with. > > First you have to decide how Empathy will store messages. Look at > <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/management/c…>. > This is how HyperKitty gets messages from a mbox and adds them to its > database. It's actually fairly simple - a lot of the code is handling > exceptions due to defective messages. > > Presumably Empathy will have a method for adding a message to the > archive, so importing is just getting messages from the mbox and using > Empathy's method to add it. > Thank you Mark. Your response was very helpful. This should help my developer make some decisions. -- 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/

6 years, 6 months

[MM3-users] Re: Archive download - unexpected end of file

by Mark

>> On 3/1/25 13:58, Mark wrote: >> >> I have a MM3 list to whose archive I recently added an mbox file of >> older emails. >> >> Viewing/searching the archive (Hyperkitty) is working fine. >> >> Downloading archives "for the month" or "last 30 days" delivers the >> expected ".mbox.gz" file and those are fine. >> >> However, when I download the "Entire archive" and attempt to gunzip >> that ".mbox.gz" file I get the error: " ... unexpected end of file". ?On 2025-03-01 23:04, Mark Sapiro wrote: > > The process creating the zip for download times out. You can increase > the timeout. If your wsgi server is Gunicorn, see > https://docs.gunicorn.org/en/stable/settings.html#timeout - for uwsgi > see > https://uwsgi-docs-additions.readthedocs.io/en/latest/Options.html#harakiri > > However, it's probably easier to get it in pieces. You can prpbably > get chunks bigger than a month. Look at the URL for a month, e.g. for > Jun, 2005 it will be something like > > https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2025-02.mbox.gz?start=2025-01-01&end=2025-02-01 > > The <fqdn-listname>-2025-02.mbox.gz can be any arbitrary file name. > The start and end parameters determine what's included. E.g. for all > of 2024 > > https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2024.mbox.gz?start=2024-01-01&end=2025-01-01 > > Note that the end date is the first date not included, i.e. the day > after the last date included. Thank you very much Mark, for your detailed advice. Increasing the timeout from the default of 30 seconds to 360 now sees the entire archive downloading successfully. # /etc/mailman3/gunicorn.conf # bind = ['127.0.0.1:8000'] proc_name = "mailman-web" 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" #Added 2025-03-02 to resolve timeout on download full archive. timeout = 360 $ systemctl daemon-reload $ systemctl restart mailman3 $ systemctl restart mailmanweb $ pstree ├─gunicorn───gunicorn ├─mailman-web───mailman-web─┬─mailman-web │ └─3*[mailman-web───{mailman-web}]

1 year, 8 months

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Odhiambo Washington

On Sun, May 7, 2023 at 8:52 PM Volkmar Grote <volkmar(a)grote-family.com> wrote: > Hi Mark, > > On 07.05.23 01:31, Mark Sapiro wrote: > > On 5/6/23 16:02, volkmar(a)grote-family.com wrote: > >> > >> My urls.py: > >>> (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py > >>> from django.contrib import admin > >>> from django.urls import include, reverse_lazy, re_path > >>> from django.views.generic import RedirectView > >>> > >>> urlpatterns = [ > >>> re_path(r'^$', RedirectView.as_view( > >>> url=reverse_lazy('list_index'), > >>> permanent=True)), > >>> re_path(r'^postorius/', include('postorius.urls')), > >>> re_path(r'^hyperkitty/', include('hyperkitty.urls')), > >>> re_path(r'', include('django_mailman3.urls')), > >>> re_path(r'^accounts/', include('allauth.urls')), > >>> # Django admin > >>> re_path(r'^admin/', admin.site.urls), > >>> ] > > > > > > We and the various docs are inconsistent about 'postorius' vs > > 'mailman3' and 'hyperkitty' vs 'archives' in urls. Add these > > > > re_path(r'^mailman3/', include('postorius.urls')), > > re_path(r'^archives/', include('hyperkitty.urls')), > > > > to your urlpatterns list in urls.py to cover both variants. > > > thanks for the quick reply. > I am one step closer to a solution, > "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. > I get the functionality, but it looks ugly w/o any graphics, for which I > get yet another, slightly similar, error message: > > > > > > Page not found (404) > You can run: '/opt/mailman/mm/bin/django-admin clear_cache' as the mailman user. After that you can also restart Nginx, then test again and see if everything works. -- 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]

3 years, 6 months

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

by Odhiambo Washington

On Mon, Nov 4, 2024 at 10:34 AM Gerald Vogt <vogt(a)spamcop.net> wrote: > Hi, > > On 04.11.24 02:06, Mark Sapiro wrote: > > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > > We should probably cover this in the docs, but for /etc/mailman3, you > > should do > > ``` > > sudo mkdir /etc/mailman3 > > sudo chown mailman:mailman /etc/mailman3 > > sudo chmod 755 /etc/mailman3 > > ``` > > Then you can create all the subordinate files as the mailman user. For > > other things like the systemd service and the postfix and web server > > configs, you need to do them as root (via sudo). > > is it really necessary that the mailman user can write that directory? > For most services, directories and files in /etc/ may be readable for > the service but usually not writable as you don't want the service > itself change it's core configuration. > > On your server it looks like this: > > # ls -la /etc/mailman3 > total 28 > drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . > drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. > -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf > -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg > -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg > -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py > > and it works just fine. > True, but making the mailman user own the files makes life easier when you operate from the virtualenv - you do not have to exit the virtualenv to edit the files in /etc/mailman3, and then re-enter the virtualenv. You do not have to give the mailman user sudoer rights. That's the whole point about the below: ``` sudo mkdir /etc/mailman3 sudo chown mailman:mailman /etc/mailman3 sudo chmod 755 /etc/mailman3 ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years

[MM3-users] Bounce of HCL Notes invitations - CloseBoundaryNotFoundDefect() - 501 Message has defects (in reply to end of DATA command)

by Stephen J. Turnbull

Ulf R. writes: > >>> msg.defects > [CloseBoundaryNotFoundDefect()] This means that the message declares a MIME multipart Content-Type, and some part had a "start" boundary line but no "end" boundary line. > Is there a quick fix for this available? No. If the sending software isn't quite broken, this defect means that a chunk of the message was lost somewhere. Ignoring this kind of defect is obviously a bad idea, and any other fix (on the Mailman side) requires knowing precisely what's causing the defect to be detected. > Is it a problem of the python code or the format of the HCL Notes > Server? Nothing's impossible, but I would bet that the problem is in the HCL Notes format. The MIME multipart spec goes back to the early 1980s, and I'm sure the Python Email package implements it exactly by default. I can't say more without the exact MIME structure of a message that causes this error, preferably the whole message (header and body). That said, it might be something that (a) can be worked around with a slightly more lenient existing email policy, or (b) that we could create a new policy that ignores the problem. > In the .eml file I see 25 header fields calles "X-Notes-Item". May > be it is an overflow? Extremely unlikely. All header fields have been successfully processed by the time a CloseBoundaryNotFoundDefect can be detected, and the copy of the field you provide in your followup email is well-formed and contains no interesting content (such as non-ASCII characters, even after decoding the MIME-words). I cannot say why removing the first instance of the field would resolve the error without seeing the whole message. > Any ideas? Not without the full message. If you're not comfortable sending the message to the list, but do trust us enough, you can send a message that causes the error to me and/or Mark Sapiro <mark(a)msapiro.net>. Regards, Steve

1 year, 7 months

[MM3-users] Re: spanish localization

by Abhilash Raj

On Sun, Feb 14, 2021 at 01:08, Victoriano Giralt <victoriano(a)uma.es> wrote: > El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió: >> What translations are those? Please give specific examples. What I >> am >> saying is Mailman core 3.3.3 is currently up to date with weblate. >> There >> are no Spanish translations for core done after 7 November in >> weblate >> and weblate shows 100% completion for Spanish for Mailman core. > > Mark, please, how do you check when translations happened? Nov 7th is > a > very significant date for me (it is my wedding anniversary) and I'm > 90% > sure that I dedicated time to Weblate after that date... You can look at the commit history of the spanish po file to get a detailed history of when and who made the changes. For example: Core: <https://gitlab.com/mailman/mailman/-/commits/master/src/mailman/messages/es…> Postorius: <https://gitlab.com/mailman/postorius/-/commits/master/src/postorius/locale/…> You find similar histories in all the repos. Each person's changes should be an individual commit in the repo, typically all outstanding translations are committed every night in Weblate. > > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, > after > updating to the latest releases, are still in Englanish (more English > than > Spanish). Could this be because of the .mo files not being up-to-update? There used to be some strings that were translated incorrectly, but I think we fixed all of those that we found. Abhilash > This is not a fight, we want to help, but do not know how. > > Thanks! > > -- > Victoriano Giralt Innovation Director > Digital Transformation Vicerectorate University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. >> Q: Are you sure ? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting annoying in email ? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> thanks, Abhilash Raj On Sun, Feb 14, 2021 at 00:57, Victoriano Giralt <victoriano(a)uma.es> wrote: > El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) > via > Mailman-users escribió: >> On 13/2/21 20:00, Mark Sapiro wrote: >> > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> > wrote: >> > > But... here is a thing that I can not understand: If the source >> (the >> > > .po >> > > file) is from november 7th, it doesn't matter how many times you >> > > recompile it: the result will be the same. >> > Correct, but the point is if you download the latest >> > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov >> 7 >> > file >> > in the distribution, you will find they are identical, so it it >> appears >> > that the weblate translation hasn't changed since that time. >> > >> > If there are issues in this mailman.po, they exist in weblate too >> and >> > need to be fixed there. >> >> That clarifies all. Thanks. As I said in my previous message, I'll >> wait >> for the next upgrade and hopingly the translations done after 7h of >> november (by others and me) will be there. > > I've visited Weblate, all Spanish strings are translated. Spanish is > 100% > translated, but, none of them have been "approved", whatever that is. > It > seems that a reviewer needs to approve the translation in order for > them to > be incorporated or released or whatever. I was sure I had reviewed > everything between November 7th and the day Abhilash announced the > release > candidate and asked for translation review, but nothing has made it > to the > released version. > > Maybe there's something in the translation flow that we are doing > wrong. > I'm starting to miss the good old days when Mailman 2 translators just > downloaded the .po files and returned them :-) > >> > Also note that the translations on weblate only affect strings in >> the >> > core code. The Mailman core templates are not currently >> translated in >> > weblate and there are currently no Spanish language templates. One >> > would >> > need to create Spanish translations of all the templates in >> > < >> > >> <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> >> > > >> > and submit a merge request to add them to a mailman/templates/es/ >> > directory. >> > >> I will make the template translations locally, test them, and then, >> if >> they are yet lacking in the main repo, follow your suggestion. > > I'm a bit short on time, but I'll help Guillermo with that, at least > reviewing or doing a second pass. I'm not proficient enough to speak > about > Mailman core templates, but for Django templates, there is a nice tag > for > marking text with translations in the .mo files ... > > -- > Victoriano Giralt Innovation Director > Digital Transformation Vicerectorate University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. >> Q: Are you sure ? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting annoying in email ? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

5 years, 9 months

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

by John Covici

On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote: > > > > > On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > > > On Sat, 13 Mar 2021 14:46:55 -0500, > > Mark Sapiro wrote: > >> > >> On 3/13/21 11:14 AM, John Covici wrote: > >>> > >>> Now one thing came up while trying to create the database, I got a > >>> traceback complaining about a revision error because gentoo had a > >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I > >>> upgrade mailman, am I going to have to do something to the database as > >>> well and why should the database have some kind of reference to the > >>> mailman version? > >> > >> > >> I don't know why this is an issue. You shouldn't need to do anything > >> with the database when you upgrade. Please post the full traceback and > >> error message. > > > > Sorry I can't reproduce it, after dropping and recreating the database > > the error went away, but it was in alembic and it was talking about an > > invalid revision and gave a long hex string. > > > > > My guess is that you updated the database (perhaps, by invoking the mailman > command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes > up and sees a new revision for the database migration added from 3.3.3 but > can’t find the same migration in its source (because it is 3.3.2). That is sort of what happened, except in the opposite direction, it was from 3.3.3 to 3.3.2. My question is therefore, do I have to update this alembic_version when I upgrade mailman to a newer version? That is what I was getting at. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 8 months

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Mark Dadgar

On Nov 4, 2021, at 3:05 PM, Andreas Barth <aba(a)ayous.org> wrote: > * Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: >> >> >> --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro >> <mark(a)msapiro.net> wrote: >> >>> On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: >>>> >>>> My conclusion: >>>> I ask you to consider these experiences in an update for the mailman3 >>>> packages in debian bullseye. It would save time, questions and nerves. >>> >>> >>> Issues with Debian packaging should be directed to Debian. >> >> Or as previously discussed, the debian packages should be avoided entirely. > > I strongly disagree with that statement. > > Distribution packages have their own up- and downsides. Of course, how > they are done is to be discussed with the distribution, so: if > something is wrong with a debian package, please follow the > instructions on bugs.debian.org on reporting bugs. > > However, they have the advantage that they're integrated with the > distribution. They have the disadvantage that they're stable for some > time - that is why it's called a stable release. If they have all the > features someone wants, they usually work fine (and my first > mm3-installation was the default debian package). If one looks for > bleeding edge, of course that's not what one can expect from a > distribution package - but that's also a feature. You left out the fact that the distro edition of mailman3 has very poor support because Debian doesn’t know how to do it and the setup is different enough from vanilla that this community has a hard time supporting it as well. You can certainly try to run it, but I’m willing to bet that you’ll regret it. Having tried it myself, I can’t in good conscience recommend it to anyone. The bottom line is that, IMHO, distro works great for fairly mature projects. MM3 isn’t that yet. YMMV, my $0.02, you get what you pay for, etc. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-25 01:37, Mark Sapiro wrote: > I think the difference is http vs https, not the IP vs domain name. > > Also, with either of these, you are addressing the web server and not > the wsgi server. The wsgi server is presumable listening on port 8000 > and in the beginning when you had the default > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' With this default, the template URI is in the format of http://localhost:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… Looking at this URI in lynx (on the same server as Mailman) it returns the text of the custom Welcome template, as does curl and wget. And it's the same if 127.0.0.1 is used in place of localhost -- ie. http://127.0.0.1:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… And the same result if the domain name is used with https -- ie. https://mydomain.com/mailman3/api/templates/list/mytestlist.mydomain.com/li… So, the template is all good, it can be accessed by Lynx, but the part of the Mailman suite that sends out the custom Welcome message cannot access it and spits out the error. Where are the custom templates stored? Is there a permissions issue perhaps? A grep for the text of my Welcome message turns up zero results. # grep -Rnw '/' -e 'Test two million for welcome' By the way, in Lynx when the template's URI uses the public ip adress -- ie. http://my-public-ip-address/mailman3/api/templates/list/mytestlist.mydomain… ... it returns a "404 page not found" in Lynx. Given that this is pretty much an out-of-the-box installation (venv installation as per the docs) and everything else works perfectly I'm thinking surely others have encountered this. Or is it just me? It's completely done my head in, so if anyone can offer a glimmer of light I'll grab it. > <REDACTED-PUBLIC-IPv4-ADDRESS> instead of 127.0.0.1. Also, > Have you set > ALLOWED_HOSTS in your settings.py? It should be something like > ``` > ALLOWED_HOSTS = [ > "localhost", # Archiving API from Mailman, keep it. > "127.0.0.1", > "<REDACTED-PUBLIC-IPv4-ADDRESS>", > "MYDOMAIN.COM", > ] Yes.

2 years, 6 months

[MM3-users] Re: Monthly Password Reminders

by Odhiambo Washington

On Fri, Feb 3, 2023 at 3:05 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > On Thu, Feb 2, 2023 at 8:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 2/2/23 06:29, Odhiambo Washington wrote: > > > > Does MM3 send these monthly subscription reminders the way MM2 used > to > > > do? > > > > I am looking for the setting, but can't find that in the list > settings. > > > > > > No, it does not. > > > > The rationale behind the decision to toss away that feature? Security?? > > For the passwords, yes. It was frequently reported as a bug, in fact. > Mostly the reminders generate requests to know how to shut them off. > You're the first in probably a decade who's asked how to turn them on! > It's because I only recently migrated to MM3 after watching from the periphery for years :) I have been on MM2, and even there I disabled it. I was just curious. While in theory we could protect in transit with SMTP over TLS, we > can't guarantee end-to-end encryption (eg, if there's a .forward at > the subscribed address), and while TLS is widely implemented, it's > still not universal. And there's no way to protect unencrypted email > from admins at the receiving host. Receiving encrypted email is > pretty much not implemented at all, except in some specialized > communities. Also, now that passwords (if they're used) are > attributes of Users who may have several Addresses and worse, they may > have admin privileges. So Mailman 3 passwords are generally higher > value than in Mailman 2. > > I can imagine a use for the list of subscriptions part that a few > users might like, but most folks would prefer not to get another > regular mailing. > > Steve > That makes complete sense, and I am satisfied with the decision. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 9 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On May 12, 2020, at 3:46 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/12/20 3:02 PM, Mark Dadgar wrote: >> >> The second patch did not work either. Ahh, well. > > > I think you need to do something like this: > > $ mm/bin/django-admin shell > Python 3.7.1 (default, Dec 14 2018, 13:17:01) > [GCC 5.4.0 20160609] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import Email >>>> emails = Email.objects.all() >>>> for email in emails: > ... if email.content.find('\u200b'*5) >= 0: > ... print('Found in ml {}, hash {}'.format( > ... email.mailinglist.name, > ... email.message_id_hash)) > ... >>>> _NAME/message/HASH/ Finally getting around to looking into this now that I’ve migrated from sqlite3 to postgres (writeup on that coming soon for the archives). Here’s what I get when I attempt the above commands: root@mail:/usr/lib/mailman3/bin# sudo -u list django-admin shell Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email Traceback (most recent call last): File "/usr/lib/python3.8/code.py", line 90, in runcode exec(code, self.locals) File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/hyperkitty/models/__init__.py", line 25, in <module> from .category import ThreadCategory File "/usr/lib/python3/dist-packages/hyperkitty/models/category.py", line 61, in <module> class ThreadCategory(models.Model): File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 103, in __new__ app_config = apps.get_containing_app_config(module) File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 252, in get_containing_app_config self.check_apps_ready() File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 134, in check_apps_ready settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 79, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 60, in _setup raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. >>> I am in no way a django expert. Thoughts? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 5 months

[MM3-users] urllib.error --was: Re: No module named 'mailman3hyperkitty'

by Axel Rau

> Am 17.01.2022 um 00:19 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/16/22 10:24 AM, Axel Rau wrote: >> ModuleNotFoundError: No module named 'mailman3hyperkitty' > > This comes from mailman.cfg from the class: definition in the [archiver.hyperkitty] section you probable have something like > > class: mailman3hyperkitty.Archiver > > instead of > > class: mailman_hyperkitty.Archiver Correcting this, does not stop server errors. While selecting a list in the browser, I’m getting: - - - Traceback (most recent call last): File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get 'hyperkitty' in archivers and # noqa: W504 File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ self[key] File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} - - - Question: Am I missing aliases in my nginx.conf? I just have: - - - location / { uwsgi_pass unix:///tmp/uwsgi.sock; include /usr/local/etc/nginx/uwsgi_params; } location /static { alias /usr/local/mailman3/static; } location /static/favicon.ico { alias /usr/local/mailman3/static/postorius/img/favicon.ico; } - - - Any help appreciated, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

4 years, 9 months

[MM3-users] Re: How to upgrade to 3.10

by Paul Tomblin

On Tue, Mar 3, 2026, at 12:30 AM, Mark Sapiro wrote: > > But it looks like here it's trying to install 3.3.10. > >> Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) >> ... a bunch of these ... >> INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. >> Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) >> ...a bunch more... > > Is there any conflict reported in this `bunch more` to force 3.3.9? What > if you do `pip install mailman==3.3.10`? All the "...a bunch more..." lines are "Requirement already satisfied". And here's what happens when I try to do as you suggested: (venv) $ pip install mailman==3.3.10 Collecting mailman==3.3.10 Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) Requirement already satisfied: aiosmtpd>=1.4.3 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.4.6) Requirement already satisfied: alembic!=1.7.0,>=1.6.2 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.18.4) Requirement already satisfied: atpublic in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (7.0.0) Requirement already satisfied: authheaders>=0.16 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (0.16.3) Requirement already satisfied: authres>=1.0.1 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.2.0) Requirement already satisfied: click>=8.0.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (8.3.1) Requirement already satisfied: dnspython>=1.14.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (2.8.0) Requirement already satisfied: falcon>=3.1.3 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (4.2.0) Requirement already satisfied: flufl.bounce>=4.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (4.0) Requirement already satisfied: flufl.i18n>=3.2 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (6.0.0) Requirement already satisfied: flufl.lock>=5.1 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (9.0.0) Requirement already satisfied: gunicorn in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (25.1.0) Requirement already satisfied: lazr.config in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (3.1) INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13" I guess I need to upgrade my python version? -- Paul Tomblin

8 months, 1 week

[MM3-users] Re: Digests not working correctly

by Joel Lord

On 6/4/2023 9:25 PM, Mark Sapiro wrote: > On 6/4/23 11:45, Joel Lord wrote: Thanks for the explanation on size-triggered digests. >> Periodic is much more complicated, even to explain. I have the cron >> job running nightly at 11:00 PM and it certainly seems to be working, >> except for one really odd thing. The list also definitely has >> periodic digests enabled in the web UI. This is a very bursty list, >> so it will go mad with traffic for a few weeks and then will go mostly >> idle for a month or so. The first digest of a burst is definitely >> size-triggered, but pretty reliably it has the last few messages from >> the previous burst in there. So the one I got today had three >> messages from today and one message from May 4th. But that May 4th >> message should have gone out at 11:00 PM on May 4th with the daily >> digest and then gotten flushed from the pending digest queue, right? > > That's correct. Do you ever get periodic digests sent at 11:00 PM? If > not, there is some issue either with configuration or something. If you > get them sometimes, I don't know what could be wrong. The periodic digests do seem to be coming out. I also now have confirmation that the one message in this morning's digest that was from May 4th was also included in the last digest back on May 4th, so it seems that the one message was left behind in the digest queue when the periodic digest was sent. There was one earlier message to the list back on May 4th, before the one that got duplicated, but I can't tell if that triggered a size-based digest to be sent: the logs aren't clear enough on that detail for me to tell. Just to inform things: (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman django-mailman3==1.3.9 mailman==3.3.8 mailman-hyperkitty==1.2.1 mailman-web==0.0.6 mailmanclient==3.3.5 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper mailman-hyperkitty==1.2.1 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post postorius==1.3.8 -- Joel Lord

3 years, 5 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/14/19 11:10 PM, Stephen J. Turnbull wrote: > > Torge Riedel writes: > > > > > - there is a way to do this now via settings_local.py, but feels > > > a little bit risky if default configuration changes on update of > > > mailman > > > > This should not be true. If it is, we need to fix that. Will check. > > > It is more or less true [...] the only way settings_local.py can > change something like INSTALLED_APPS is to redefine INSTALLED_APPS > in it's entirety which leads to the possibility of INSTALLED_APPS > changing in settings.py and those changes not being picked up in > settings_local.py. That's a different issue from the one I believe Torge is worried about, which is an update overwriting settings_local.py. But it's not good. > The way around this is to remove the import of settings_local from > settings.py and then put > > from settings import * > > at the beginning of settings_local.py and then point Django at > settings_local rather than settings. I don't understand the ramifications of making this change (presumably Barry or somebody had a reason for the change from Mailman 2's method), but at first glance it looks like a big step in the right direction. > Then you can do things like > > try: > INSTALLED_APPS.remove('allauth.socialaccount.providers.google') > except ValueError: > pass > > in settings_local.py except there are still issues because, e.g., > INSTALLED_APPS is defined as a tuple (immutable) and not a list in > settings.py. Given the concerns of privacy advocates, I would say that it would be better to have a separate AUTH_PROVIDERS = ['allauth.socialaccount.providers.google', ...] in settings_local.py, and merge that in to INSTALLED_APPS. Of course removing specific providers would be OK too, but I think that this is a place where "deny all / accept what you want" is appropriate. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

7 years, 8 months

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

by Ruth Ivimey-Cook

Marcus, I'm with you in not understanding Mark's instructions -- I think there is a typo somewhere :-) To create a non-member user in Mailman, Go to the List Settings page in Postorius, select Non-members from the User menu, and add a user there. Of course, that does nothing for your email system, which must also be configured. I would very strongly encourage you to have the no-reply address be 'real' in the sense that the email system will agree it is valid and deliverable, or some recipient email servers will refuse to accept email from that address, either. The right thing is for email to that address accepted as normal and then immediately discarded. You could send back a message "this address is not monitored" but there is an issue with spam backscattering which makes that less good than it first seems. Regards, Ruth On 06/04/2021 10:00, marcus.granath(a)gmail.com wrote: > Thank you @Mark Sapiro for you quick reply. > > So by doing the following settings, then ALL the messages sent to the list will be hold for moderation: > > Settings -> Message Acceptance > > "Default action to take when a member posts to the list": "Hold for moderation" > "Default action to take when a non-member posts to thelist": "Hold for moderation" > > Members -> Administration options -> Moderation: "List default" > > 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? > > Also, how do I create a "non-member" user "no-reply(a)abc.com"? > Do you mean that I do that under the "Mass operations -> Mass subscriptions" ? Can I add a "fake address" there? > _______________________________________________ > 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/ -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 7 months

[MM3-users] Re: slow restart time for mailmanweb

by William Oliver

On Tue, 2021-12-28 at 13:52 -0800, Mark Sapiro wrote: > On 12/28/21 1:28 PM, William Oliver wrote: > > > > > > > These log entries are from restarting mailman, not mailmanweb Damn. Sorry about that. Brain fart. Yep, it's still slow with mailmanweb: Dec 28 17:41:00 emergenus systemd[1]: Stopping GNU Mailman Web UI... Dec 28 17:41:01 emergenus uwsgi[20860]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Dec 28 17:41:01 emergenus CRON[44474]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) Dec 28 17:41:06 emergenus kernel: [12494.670812] [UFW BLOCK] IN=eth0 Dec 28 17:42:01 emergenus CRON[44755]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) Dec 28 17:42:07 emergenus kernel: [12555.550730] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3e:ef:72:96:00:23:9c:9e:9f:c0:08:00 SRC=92.63.197.112 DST=203.159.80.234 LEN=40 TOS=0x00 PREC=0x00 TTL=253 ID=9540 PROTO=TCP SPT=57024 DPT=25238 WINDOW=1024 RES=0x00 SYN URGP=0 Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: State 'stop- sigterm' timed out. Killing. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 20860 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44476 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44477 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44478 (sh) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44480 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44483 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44484 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44485 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44486 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44487 (mailman-web) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44479 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Killing process 44481 (uwsgi) with signal SIGKILL. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Main process exited, code=killed, status=9/KILL Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Failed with result 'timeout'. Dec 28 17:42:30 emergenus systemd[1]: Stopped GNU Mailman Web UI. Dec 28 17:42:30 emergenus systemd[1]: mailmanweb.service: Consumed 2min 27.819s CPU time. >

4 years, 10 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Andy Smith

On Mon, Jul 11, 2022 at 02:44:59AM +0000, Andy Smith wrote: > Hi Mark, > > On Sat, Jul 09, 2022 at 12:05:32PM -0700, Mark Sapiro wrote: > > If the original post was the message delivered to > > users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or > > another recognizer parsed those addresses from the message body. > > For now I've configured a copy of all mails to -bounces addresses, > so if/when it happens again I can inspect the actual email that > triggered it. This just happened again. As a refresher, the issue I'm seeing is that Mailman registers a bounce against addresses that aren't subscribed, including addresses for the list itself and for the -leave address that is in some footer text. Here's the bounce.log: Sep 30 17:12:25 2022 (8428) Member [elided1](a)[elided1].force9.co.uk on list users.mailman.bitfolk.com, bounce score = 1. Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email mailto:[elided2]@gmail.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Member [elided2](a)gmail.com on list users.mailman.bitfolk.com, bounce score = 1. Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users-leave(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Member [elided3](a)[elided3].org.uk on list users.mailman.bitfolk.com, bounce score = 1. I have elided parts of the email addresses of real subscribers. Attached is the actual non-delivery report from the MTA that triggered this. In it I have done my best to elide the names and addresses of real people, but nothing else. They match the same elisions from the bounce log. Any ideas why Mailman is interpreting this NDR so over-zealously? It seems like a pretty standard one. [elided1].force9.co.uk is the subscriber who rejected the mail, yet also users(a)mailman.bitfolk.com, [elided2](a)gmail.com, users-leave(a)mailman.bitfolk.com and [elided3](a)[elided3].org.uk (sender) were punished. Thanks, Andy

4 years, 1 month

[MM3-users] Re: Does hyperkitty show JPEGs in line and what about attachments?

by Jason Glazer

Mark Thanks for the link to the test archive. That and your information has clarified things a lot. Jason On 7/12/2017 11:39 AM, Mark Sapiro wrote: > On 07/12/2017 04:47 AM, Jason Glazer wrote: >> Does anyone know if Hyperkitty can be configured to allow for inline >> images to be maintained so that an HTML file looks like a normal HTML >> message? >> >> Also, can attachments to a message under Hyperkitty preserve their name >> rather than being "scrubbed" into "attachment-*.*" files? > > The answer to some of this is at > <https://lists.mailman3.org/archives/list/test@mailman3.org/message/N3XVN3DC…>. > > One question unanswered by that post is what happens with an inline > image in an HTML message body. In the original message, the image is > referenced by an IMG tag with "src=" pointing to the image MIME part. > Since this structure is not maintained in HyperKitty, inline images > probably don't work. > > Also, with respect to Mailman 2.1, if you want the scrubber to preserve > file names and extensions, set the following in mm_cfg.py > > SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False > SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True > > and if you want scrubbed HTML to not be HTML escaped so it renders > rather than looking like raw html, set > > ARCHIVE_HTML_SANITIZER = 3 > > but note this comment from Defaults.py > >> # 3 - Remove text/html as attachments but don't HTML-escape them. Note: this >> # is very dangerous because it essentially means anybody can send an HTML >> # email to your site containing evil JavaScript or web bugs, or other >> # nasty things, and folks viewing your archives will be susceptible. You >> # should only consider this option if you do heavy moderation of your list >> # postings. > > This is an issue with HyperKitty as it appears this is what HyperKitty > does and there's no way to turn it off. > -- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

9 years, 4 months

[MM3-users] Re: Disabled by bounce

by Allan Hansen

One more, sorry: Looking in the mailman-users archive, I'm not sure if I understand the bounce settings. Is it the case that if I set the 'Bounce info stale after' to 3d then in 3 days the bounces will be reset to 0 if no further bounces have arrived? I saw a post that made me doubt this. Yours, Allan On 2/1/23, 09:59, "Mark Sapiro" <mark(a)msapiro.net> wrote: On 1/31/23 22:32, Allan Hansen wrote: > Hi all, > > Apparently Google just started to get very aggressive about DKIM settings. Some hundreds of my subscribers have had their subscriptions disabled because of Google's bounces. > > I tried to 'Enable' some of them, expecting that their bounce scores would be reset, but when I list the users, the bounce scores are still 5. > > Please advise. Will enabling them without the bounce score being reset just cause the server to disable them again. Yes, Google has started enforcing a policy which is effectively DMARC p=reject even for senders whose domains don't publish DMARC p=reject or quarantine. To avoid this issue, you may need to set DMARC Mitigate unconditionally to Yes as well as DMARC mitigation action to Replace From: with list address if it isn't already. As far as enabling without resetting the bounce score is concerned, I think you are correct that they will just be disabled again on the next bounce. This is a bug and should be fixed. However, all of the above can be avoided without any DMARC changes by enabling bounce probes. in the [mta] section of mailman.cfg, set ``` verp_probes: yes ``` Since the probe is sent From: the list's domain, it should pass googles SPF and DKIM checks and not bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/56WVO6NIOGOBAOOS2B4YCIDJN7VCIXTF/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

3 years, 9 months

[MM3-users] Re: Hyperkitty on Debian 12

by Michael Oberrauch

On Tue, 2024-03-26 at 08:06 +0100, Markus Grandpré wrote: > Dear Mr Sapiro, > > thank you very much for your help. The required command is: > > # mailman-web hyperkitty_import \ > -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ > /var/mailman21/testlist.mbox > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key > used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a > subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... > > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available > > As with Mailman 2.1, I will probably have to continue working with > Mailman3 as root. Too bad that there is no documentation for Debian > admins like me, who don't want to dive too deep into the python > framework. Or have I overlooked something? > > Best regards, > Markus > > Hi Markus, we are also running MM3 on Debian 12 from Package Repositories. First of all, you should not try to directly switch user (su) to the lists user, it's generally intended to executes commands as that user, if necessary; either using `runuser`, `sudo`, or `su -c`. However, the prepackaged scripts `mailman-wrapper` and `mailman-web` already do this and therefore you ca run those as root without permission problems. On Debian there are two relevant users for MM3: the list user runs mailman core, whereas the www-data user runs Postorius and Hyperkitty. So you have to make shure, that the www-data user can access the .mbox files while importing. Hope that helps. Cheers, Michael -- Michael Oberrauch (er/ihm) Computerreferent Fachschaft Mathematik/Physik/Informatik/Chemie Studentische Vertretung Technische Universität München Boltzmannstraße 3 85748 Garching eMail: oberrauch(a)fs.tum.de Tel: (+49) 089 289 18545 Fax: (+49) 089 289 18546 https://mpic.fs.tum.de

2 years, 7 months

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

by vogt＠spamcop.net

Mark Sapiro wrote: > On 10/23/24 13:23, Gerald Vogt wrote: > > I don't quite understand the relevance of the user accessing the > > localhost tcp port. Any local user can do that. > I am trying to duplicate what Mailman does in an attempt to find the issue. > > I can access the template content with > > curl > > http://localhost:8000/mailman3/api/templates/list/community.lists.example.co... > > as well as > > curl > > http://lists.example.org/mailman3/api/templates/list/community.lists.example... > > as any user on the mailman server. > > How about > curl -A 'python-requests/2.32.3' > http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… > > as the Mailman user? I have tried anything I could think of but I cannot reproduce the issue using curl as user mailman (or any other for that matter) Going directly for localhost:8000, using some or all of the headers I can capture with tcpdump: ``` $ curl -v -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… ``` as well as going through the local httpd: ``` $ curl -v --http1.1 -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' https://lists.example.org/mailman3/api/templates/list/community.lists.examp… ``` Running tcpdump during those runs shows me it's sending the same headers as mailman does. Thus on http protocol level it's the same, but still the server returns immediately. What I have just noticed is that the Date header in the delayed response is the "late" time. I have even compared tcp headers from either capture. They look identical down to the frame sizes. The only difference the last times is that with curl, the server side sends the ACK for the request and milliseconds later a PSH,ACK with the response headers. When it comes internally from mailman it sends the ACK for the request and then 5 seconds later it sends the PSH,ACK with the response headers. Thanks, Gerald

2 years

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

by Marco van Tol

Op 5 feb 2024, om 15:45 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: > Op 29 jan 2024, om 18:29 heeft Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> het volgende geschreven: >> On 1/29/24 03:09, Marco van Tol wrote: >>> Right now I’m back at the original issue as I see no other solution than to go back to whoosh. >>> Thanks! >>> Marco van Tol >>> Paste: >>> ---- >>> Indexing 194620 emails >>> [ERROR/MainProcess] Failed indexing 156001 - 157000 (retry 5/5): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… (pid 32): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… >> >> >> I'm not sure why the patch you are using doesn't avoid this, but you could try the other patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> instead. If that fails, you could always find the offending message in the database maybe with a query like >> ``` >> SELECT * FROM hyperkitty_email Where subject LIKE 'http://www.google.com/url?q=\%68\%74\%74%'; >> ``` >> and modify or delete it - it's probably spam anyway. > > I tried the other patch, which looked very promising until something that had come in over SMTP some day threw a spanner in the wheels: > ``` > [ERROR/MainProcess] Failed indexing 287001 - 288000 (retry 5/5): Term too long (> 245): XTEXTº@[åeèúp¢i*h{õimô;]>ò&žôyþiýã#dzç8"¹ë= > ;æmyš€vqe.âés:æä>üzúõœ'âú·ž[]kzñ-µ€3æfdñù£8çô<bœkkñ/ãžæjïw¿òþp-ùšã7/'ûvksqé (pid 404): Term too long (> 245): XTEXTº@[ > åeèúp¢i*h{õimô;]>ò&žôyþiýã#dzç8"¹ë=;æmyš€vqe.âés:æä>üzúõœ'âú·ž[]kzñ-µ€3æfdñù£8çô<bœkkñ/ãžæjïw¿òþp-ùšã7/' > ûvksqé > ``` > > I agree that this is very likely the result of some spam, but the main point is that something that comes in over SMTP shouldn’t cause manual work on the listserver side. > > I’ll try it with a maximum length of 122 which should never explode into more than 244 bytes, unless I overlook something. This ended up working. :-) Summary: Patch from https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4… But with `TERM_LENGTH_LIMIT = 122` And str() instead of force_str() Thanks so much for all your efforts! Marco van Tol

2 years, 9 months

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

by Allan Hansen

Mark, Thank you for this reminder, but it’s not really sufficient for most. The ‘Mailman Settings’ dialog does, indeed show the other preferences tags, and yes, as you say, the dialog for ‘List-based preferences’ only shows values that are not inherited and when you set a value there, it shows. There a two problems with this: a. Once a value is overridden on the ‘List-based preferences’ dialog, you cannot go back to it being inherited by removing the override. b. You cannot see, on this dialog, what the inherited value is. This is not user-friendly. May I suggest the following: That each option shows the following: o Value 1 o Value 2 (or the equivalent for pull-down menus) A box showing inheritance status: [ ] Use inherited value from address-based preference: Value2 If the ‘Use inherited value’ is chosen, then the inherited value shows. but the value radio buttons become non-selectable. If not, then whatever value the value radio box has become the value for the list, From what I see, the ‘Use inherited value’ is the default for new lists/addresses. To change a value, the user would uncheck this box, making the radio buttons selectable, and then set the desired value. Yours, Allan > On Feb 12, 2021, at 11:52 , Mark Sapiro <mark(a)msapiro.net> wrote: > >> I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? > > > If the user has a Django account, she can see all that info at (e.g. for > this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/ <https://lists.mailman3.org/mailman3/accounts/subscriptions/>> > She gets there from `Mailman settings` in the dropdown under her user > name. She can also get there via the `Manage Subscription` button on the > list's Info page. That takes her to `List-based preferences` for the > list. Any setting not selected there is inherited from the Address-based > preferences or Global Mailman preferences

5 years, 9 months

[MM3-users] Re: Lost posting in archives

by Axel Rau

> Am 22.01.2022 um 02:39 schrieb Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>>: > > 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? Yes: - - - Jan 19 16:46:59 2022 (1997) HyperKitty failure on https://lists.framail.de/hyperkitty/api/mailman/urls: <https://lists.framail.de/hyperkitty/api/mailman/urls:> <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) - - - I have: - - - MAILMAN_ARCHIVER_FROM = ('{{ fqdn }}') - - - Should I put localhost here? > If you have the original message from the list, can you go to the URL in the Archived-At: header? Is empty: - - - Archived-At: <> - - - > 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) No. > > If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list(a)example.com <mailto:var/archives/prototype/list@example.com>/new directory and that message will have the Archived-At: and Message-ID-Hash: headers. No. How can it be enabled? That’s all I have: - - - (mailman_33) [root@lists5 /usr/local/mailman3]# ls -lR var/archives total 1 drwxrwx--- 3 mailman mailman 3 18 Jan. 18:05 hyperkitty var/archives/hyperkitty: total 25 drwxrwx--- 2 mailman mailman 6 19 Jan. 16:46 spool var/archives/hyperkitty/spool: total 1310 -rw-rw---- 1 mailman mailman 838274 19 Jan. 16:46 1642610819.7180374+05663686ecac2e85272bac93299d8469aa299a6d.pck -rw-rw---- 1 mailman mailman 8888 19 Jan. 16:46 1642610819.7836225+51d3aa9170bfb408821d5d05bd50acb687f23c19.pck -rw-rw---- 1 mailman mailman 13215 19 Jan. 16:46 1642610819.846788+bdfe7825a5a718d081683cf9cfa53cc1f36e64f2.pck -rw-rw---- 1 mailman mailman 469150 19 Jan. 16:46 1642610819.9367082+6c8adeae7d43ec9f721959a57bc1d1415c0b4857.pck - - - Thanks for your time, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

4 years, 9 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Abhilash Raj

On Tue, Oct 3, 2017, at 12:28 AM, Henrik Rasmussen wrote: > > Fra: Mark Sapiro [mailto:mark@msapiro.net] > > Sendt: 2. oktober 2017 17:26 > > Emne: [MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode' > > > >> Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > > > There is no user or list admin workaround, but the defense is a fairly > > simple patch. See the MR at > > <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit > > at > > <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. > > The commit changes 7 files, but only two are needed. The rests are tests > > or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't > >necessary. > > > > The only changes you need are those to mailman/email/message.py and > > mailman/mta/connection.py. > > I am using Docker-mailman (not yet very familiar Docker and version > control). I would expect I have to wait for a Docker-mailman release > including this change, right? > > I have at least five+ lists which almost haven't been working since my > switch from Mailman 2.1 to Mailman 3.1 (Docker-mailman 0.1.1), and I am > desperate trying to figure out whether it is best to fall back to the > Mailman 2 server, for the time being, where the lists came from, or it is > better to wait for an update to the Docker-image. > > Will https://github.com/maxking/docker-mailman/milestone/2 fix my > problems regarding failed mail handling and will it become available soon > (when?) (https://github.com/maxking/docker-mailman/issues/147)? The container images have stable releases of Mailman components, so those changes will make in to the container when a new Core release happens. The next image release is pending a version upgrade of Hyperkitty, to 1.1.3, but other changes are just meant to make the process of setting up Mailman better. They do not include changes from git repo after the release. -- Abhilash Raj maxking(a)asynchronous.in

9 years, 1 month

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

by Dmitry Makovey

So our mailman got stuck again, but I did follow your advise. Here's what I've found: On 3/29/19 2:58 PM, Mark Sapiro wrote: > On 3/29/19 2:28 PM, Dmitry Makovey wrote: >> I've had encountered this situation now twice: mail is being stuck in >> "out" queue and nothing in the logs indicates the issue. Is there a way >> to ask mailman-core politely to attempt delivery (perhaps with increased >> debugging in the logs) *without* restarting the core (which does solve >> *this* problem but creates other problems, like availability of the >> mailman as a whole) > > > Is the "out" runner running? yes: # docker top mailman-core | grep -F out: 100 21681 13215 0 Mar28 ? 01:14:16 /usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C /etc/mailman.cfg > ps -fwwA |grep runner=out > > If not, you should be able to start it as the Mailman user with a > command like > > /path/to/python3 /path/to/mailman/bin/runner -C /path/to/mailman.cfg > --runner=out:0:1 > > See 'ps -fwwA|grep runner' for examples > > If the out runner is running, is there a file named *.bak along with all > the *.pck files in queue/out/ there is one, yes: # ls -l /srv/mail/mailman/core/var/queue/out/*.bak -rw-rw---- 1 100 65533 21512 Apr 14 19:45 /srv/mail/mailman/core/var/queue/out/1555296331.8386078+2c905825b82708e5a682b872b0aff320c9dd0b2e.bak what does it indicate and what should my steps be to resolve this (other than restarting queues)? > And if it's not, is there anything in Mailman's logs to indicate why it > died? > > Also, 'mailman restart' should only take a matter of seconds, but if the > out runner is running but not processing its queue, I think sending it a > SIGINT should restart it. SIGINT killed the process allright, but it didn't auto-respawn. I ended up spawning it with: /usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C /etc/mailman.cfg but soon realized it doesn't go to background nicely so I've nohup'ed it in the end. but it did solve my problem. -- Sr System and DevOps Engineer SoM IRT

7 years, 6 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > Rob's reply in this thread was garbled due to > <https://gitlab.com/mailman/mailman/issues/616>. The text of the reply > is quoted below. > > On 7/27/19 12:54 AM, Rob Lister wrote: > > > > One thing that does occur to me is that my exim header fudge will > > probably cause the Message-ID header to move around from its original > > position, and if someone is doing hashing or actually validating (gpg > > signing?) the headers haven't been tampered with, then it might > > complain, since although the message-id hasn't changed, it might be in a > > different place in the headers. I don't think this is a problem. GPG or S/MIME signing with any software I know of only signs the message body (or a MIME part). DKIM message signing isn't going to care about the order of fields because DKIM canonicalizes the order (at least for the unique fields) according to the specification in the signature field, and that will be verified on the way in. Of course adding a Message-ID will likely break DKIM for the outgoing post, but Mailman as normally used breaks DKIM anyway. This can be partly mitigated by using ARC (authenticated received chain), which is supported by Google already, and possibly some of the other usual DMARC suspects (Yahoo!, AOL). > > Probably the more correct way to do it is only add a new header if it's > > missing, and if it's there, leave it alone. True, and I think this does it: headers_add = ${if def:h_message-id:{fail}{Message-ID: ... id generator code ...}} If you like that and test it, I would really appreciate feedback so we can update the documentation. One thing *I* would like to add to this recipe is logging. I'd be curious to see how frequently it happens outside of spam and junior high school hackers using netcat as their MUA. I don't see how to do this in Exim, though. Another is using a prefix other than "E" to indicate this isn't standard Exim behavior. Steve

7 years, 3 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 10. Dezember 2019 um 10:25 Uhr -0800 schrieb Mark Sapiro: >The underlying issue here is probably ><https://bugs.python.org/issue32330>, but that knowledge doesn't help >us. We need to get rid of the offending message in the message store. >The first step is in mailman shell. Note the paths /opt/mailman/mm/bin/ >and /opt/mailman/mm/var/ will need to be adjusted. Thanks for this information. Ubuntu's mailman stores the messages below /var/lib/mailman3/messages. The "mailman" command is in the $PATH. >This should print the file name and Message-ID-Hash (two lines the same) >for each message in the messages directory until it prints only one line >followed by the UnicodeEncodeError exception. That list line is the file >name/Message-ID-Hash of the offending message. I've execucted that code, but it does not cause an exception at all. It quietly runs through. I've attached the transcript of the shell session to this mail. With a little crude use of grep(1), however I found my held message in WQ/ZS/WQZSFFJLVMWQHMG4VYKGXJEKQVQXVK67. Does the messages directory contain only held messages? I've looked at some messages and all of these I looked at were spam. The directory structure contains 40 messages in total, accumulating to 480 KiB disk space. If required, I can zip that directory up and e-mail it to you for inspection. >DELETE FROM message WHERE message_id_hash = xxx; As the exception you expected did not occur, I didn't do this yet. I can make a database and directory backup and then run it, though. Should I try? I assume after this I should also delete the respective files from the messages/ directory? >As of Mailman core 3.3.0 there is a 'mailman notify' command designed to >be run periodically by cron to notify owners/moderators of prnding requests. I did receive an e-mail to the list owner address that told me that the e-mail from my incorrect e-mail address "requires approval". That was the first time I received such an e-mail. In parallel, on the incorrect e-mail address, I received the notification for moderator approval. Marvin -- Blog: https://mg.guelker.eu

6 years, 11 months

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

by Dave Hall

Hello, Please pardon a slightly off-topic comment, but I would like to highlight a part of Odhiambo's post. Heavily nested inline replies also reflect the issue I wish to comment on, so I'm not going to. Granted, I am a slow learner, and perhaps already so mixed up after reading > the myriad HOWTOs for > installing MM3 that are available online. I am tempted to say there are > many like me who are likely to > miss "where to obtain" other settings from. and > Is it possible to modify the documentation to somehow make it obvious (in a > language that a layman can easily understand, I have seen this with several open source projects lately. There's no big picture, just 'hundreds' of cross-linked little bits of disjointed information that almost seem like documentation for individual modules. I once joined a large commercial project for a major US computer company (sorry, I won't share details). They were quite proud of their extensive documentation. The docs for their equivalent of the kernel syscall interface, when printed (two-sided) and stacked, would easily approach 2 meters tall. Yet, every bit of it was incomprehensible unless and until you called the developer and had them explain it to you. The problem that we all have, us humans, is that when we are very familiar with something, like the code we've been working on, it is very hard to describe its purpose to somebody who knows nothing about it. ("It's obvious to me, so it should be obvious to you."). So, a challenge for us all: When writing and reviewing your documentation, imagine that you're explaining your whole project face-to-face to your grandmother, or to anybody who never learned to program. From experience I promise that it's easy once you get the hang of it. Thank you and sorry for the speech. -Dave -- Dave Hall Binghamton University On Sat, Jan 28, 2023 at 2:54 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > On Fri, Jan 27, 2023 at 9:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 1/27/23 05:53, Odhiambo Washington wrote: > > > On Mon, Jan 23, 2023 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > >> Note that when following > > >> https://docs.mailman3.org/en/latest/install/virtualenv.html you > create > > >> /etc/mailman3/settings.py and it contains > > >> ``` > > >> from mailman_web.settings.base import * > > >> from mailman_web.settings.mailman import * > > >> ``` > > >> to establish a base set of settings that can be augmented or > overridden > > >> in /etc/mailman3/settings.py. mailman_web.settings.mailman in turn > > contains > > >> ``` > > >> HAYSTACK_CONNECTIONS = { > > >> 'default': { > > >> 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > > >> 'PATH': "fulltext_index", > > >> ``` > > >> which is a relative path for fulltext_index and may need to be set to > an > > >> absolute path. > > >> > > > > > > Mi Mark, > > > > > > I have read this page - > > > https://docs.mailman3.org/en/latest/install/virtualenv.html and > further > > - > > > > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-config > > > - without clicking any external links. > > > I still don't see the HAYSTACK_CONNECTIONS in the settings.py included > > on > > > that page. > > > I am missing something obvious, no? > > > > > > Please reread what I wrote above. HAYSTACK_CONNECTIONS is not in the > > suggested settings.py but it is in mailman_web.settings.mailman and is > > imported by the suggested settings.py. > > > I have reread what you wrote now and I'm beginning to get the hang of this > method. > My observation is that it can only be _obvious_ to someone very familiar > with Python config > to decipher that *additional* settings *that can be augmented or > overridden > in /etc/mailman3/settings.py* can be obtained from: > /PATH-TO/mailman_web/settings/{base|mailman}.py after they have noticed > these two lines in > the sample settings given in /etc/mailman3/settings.py: > > from mailman_web.settings.base import *from > mailman_web.settings.mailman import * > > [At first instance, it is not obvious that mailman_web.settings.base and > mailman_web.settings.mailman are > actually paths in Python - which magically translates to > mailman_web/settings/base.py and mailman_web/settings/mailman.py] > Granted, I am a slow learner, and perhaps already so mixed up after reading > the myriad HOWTOs for > installing MM3 that are available online. I am tempted to say there are > many like me who are likely to > miss "where to obtain" other settings from. > For example, my mind all along has been tuned to having a settings_local.py > for overriding the settings.py. > However, with this particular documentation, it would appear that > everything is intended to just go into /etc/mailman3/settings.py. > > Is it possible to modify the documentation to somehow make it obvious (in a > language that a layman can easily understand, > that those two "import *" _DO establish a base set of settings that can be > augmented or overridden in /etc/mailman3/settings.py_ > and that those settings are in what file(s) ? > > I am not saying @Johannes Rohr <johannes(a)rohr.org> is a layman like me, > but > I think that is what hit him. > > > -- > 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 kdhall(a)binghamton.edu >

3 years, 9 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/20/25 17:50, Cathryn McGuire wrote: > > More importantly, what are you trying to accomplish? I.e. what do > > you want to happen in the following cases? > > > Message To: the list, no Cc: -- Accepted > Message To: the list, Cc: to other address (non-member) -- Hold for moderation. > Message To: the list, Cc: to a member's address ?? Accepted > > I don't think you can accomplish this one. 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. If preventing subscribers from getting duplicates is a reason for these settings, there is a user option (I think it's "Not Me Too") that suppresses list distribution to subscribers whose addresses are in To or CC. The list owner can set this manually, one by one. The site owner (who can log in on the host) can use a simple script to do so. When this is set, only the direct message (without list decorations in Subject or footer) is received by CC'd subscribers. This probably won't affect MUAs that organize posts into threads (conversations), but may look odd to subscribers if your lists are configured to add tags or serial numbers to the Subject. If the point is to discourage resending list posts to third parties, about all you can do is use the anonymous list option to clean all addresses except the list's out of the header. "Full personalization" will substitute the subscriber's address for the list address, but I don't think it has any effect on third party addressees. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year

[MM3-users] Re: possible backscatter attack using Mailman3 servers

by David Newman

On 1/3/25 5:44 PM, Mark Sapiro wrote: >> Greetings. On a system running Mailman 3.3.9 and Postfix, I'm seeing >> about 20-30 entries per day in the Postfix queue where it appears a >> Gmail user signs up for a mailing list that requires confirmation, and >> Gmail responds that the user is too busy to handle requests. >> >> There are no publicly advertised email lists on this server, and I >> don't ever see anything in the Mailman logs indicating the user ever >> tried signing up. > > > This is an attack mail bombing the user. The requests that result in the > can come via web or email. Mailman's logging of subscribes has been > missing most events through Mailman 3.3.10. See https://gitlab.com/ > mailman/mailman/-/issues/1143 which will be fixed in 3.3.11, but > subscribes waiting user confirmation still won't be logged. > > However, the message with subject "Please Confirm Your Email Address" > comes from Django allauth so it isn't actually Mailman sending it but > rather Django allauth as a result of a request to sign up for a Django > account at https://mail.example3.com/accounts/signup/. You can probably > find that request in your web server logs, and you may find the user > and/or email in the Django admin UI. Thanks VERY much for this. No such users in the Django UI, but the web server logs have 252 attempts from 132 unique IPv4 addresses registered to different ISPs throughout Europe. So, even though Mailman support for more detailed logging of sub and unsub requests would be useful, it likely would not have helped with attacks from many source IP addresses. > > Since django-mailman3 1.3.6, you can disable these signups by putting > > ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' > > in your Django settings, but then your users won't be able to sign up > for web accounts. I have made this change. As for not having web accounts, this just means new users cannot sign up to manage their Mailman settings, correct? I presume existing web accounts will continue to work. Thanks again! dn

1 year, 10 months

[MM3-users] Re: user mail not accepted

by Christian Stalberg

No. there was no response received by the user a la "results of your email commands" message. Simply the original email sent to the list. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, April 26, 2021 5:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: user mail not accepted On 4/26/21 5:00 PM, Christian Stalberg via Mailman-users wrote: >>From smtp.log > > Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) Data: b'DATA' > Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) Data: b'QUIT' > Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) connection lost Apr 26 > 00:17:39 2021 (807) Connection lost during _handle_client() Apr 26 > 00:18:11 2021 (809) > <019301d73a31$8e8e54e0$abaafea0$(a)ncboliviapartners.org> smtp to > ncpoa(a)lists.ccalternatives.org for 83 recips, completed in > 29.13376259803772 seconds Apr 26 00:18:11 2021 (809) > <019301d73a31$8e8e54e0$abaafea0$(a)ncboliviapartners.org> post to > ncpoa(a)lists.ccalternatives.org from christian(a)ncboliviapartners.org, > 5811 bytes Apr 26 00:18:11 2021 (809) > <161939626169.810.9530678025639681522(a)zarathustra.ccalternatives.org> > smtp to ncpoa(a)lists.ccalternatives.org for 1 recips, completed in > 0.0420069694519043 seconds > Apr 26 00:18:11 2021 (809) > <161939626169.810.9530678025639681522(a)zarathustra.ccalternatives.org> > post to ncpoa(a)lists.ccalternatives.org from > ncpoa-bounces(a)lists.ccalternatives.org, 869 bytes Apr 26 11:52:22 2021 > (819) > <161943793957.929.15640398646519288095(a)zarathustra.ccalternatives.org> > smtp to ssan(a)lists.ccalternatives.org for 1 recips, completed in > 0.22335004806518555 seconds > Apr 26 11:52:22 2021 (819) > <161943793957.929.15640398646519288095(a)zarathustra.ccalternatives.org> > post to ssan(a)lists.ccalternatives.org from > ssan-bounces(a)lists.ccalternatives.org, > 765 bytes > Apr 26 11:52:22 2021 (819) > <161943793960.929.13309139087156940549(a)zarathustra.ccalternatives.org> > smtp to ssan(a)lists.ccalternatives.org for 2 recips, completed in > 0.05862092971801758 seconds > Apr 26 11:52:22 2021 (819) > <161943793960.929.13309139087156940549(a)zarathustra.ccalternatives.org> > post to ssan(a)lists.ccalternatives.org from > noreply(a)lists.ccalternatives.org, 810 bytes Apr 26 11:55:22 2021 (819) > <161943812108.929.10391982256874011271(a)zarathustra.ccalternatives.org> > smtp to ssan(a)lists.ccalternatives.org for 1 recips, completed in > 0.1459965705871582 seconds > Apr 26 11:55:22 2021 (819) > <161943812108.929.10391982256874011271(a)zarathustra.ccalternatives.org> > post to ssan(a)lists.ccalternatives.org from > ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternat > ssan-confirm+ives.o > rg, 1526 bytes > Apr 26 12:01:30 2021 (817) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Apr 26 12:01:30 2021 (817) Peer: ('127.0.0.1', 38556) Apr 26 12:01:30 > 2021 (817) ('127.0.0.1', 38556) handling connection Apr 26 12:01:30 > 2021 (817) ('127.0.0.1', 38556) Data: b'LHLO > zarathustra.ccalternatives.org' > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'MAIL > FROM:<christian(a)sewagesludgeactionnetwork.com>' > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) sender: > christian(a)sewagesludgeactionnetwork.com > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'RCPT > TO:<ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalte > rnativ > es.org>' > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) recip: > ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternat > ssan-confirm+ives.o > rg > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'DATA' > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'QUIT' It looks like the above 12:01:30 are the relevant entries, and that message was sent to ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternativ ssan-confirm+es.org which is not the list, but the list's -confirm address. Was the response received by the user a "results of your email commands" message? > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) connection lost Apr 26 > 12:01:30 2021 (817) Connection lost during _handle_client() Apr 26 > 12:01:34 2021 (819) > <161943849287.814.5890052642238479423(a)zarathustra.ccalternatives.org> > smtp to ssan(a)lists.ccalternatives.org for 2 recips, completed in > 0.06680631637573242 seconds > Apr 26 12:01:34 2021 (819) > <161943849287.814.5890052642238479423(a)zarathustra.ccalternatives.org> > post to ssan(a)lists.ccalternatives.org from > noreply(a)lists.ccalternatives.org, 821 bytes Apr 26 12:01:34 2021 (819) > <161943849292.814.6140111398379700592(a)zarathustra.ccalternatives.org> > smtp to ssan(a)lists.ccalternatives.org for 1 recips, completed in > 0.04269862174987793 seconds > Apr 26 12:01:34 2021 (819) > <161943849292.814.6140111398379700592(a)zarathustra.ccalternatives.org> > post to ssan(a)lists.ccalternatives.org from > ssan-request(a)lists.ccalternatives.org, > 1335 bytes > > > Message sent that only the user receives: What I wanted to see was not the message sent to the list, but the message received by the one user from the list. If you are saying this message is that, it didn't come from any Mailman list. > Return-Path: <christian(a)sewagesludgeactionnetwork.com> > Delivered-To: ces(a)ecovillage.cc > Received: from box.ecovillage.cc ([127.0.0.1]) > by box.ecovillage.cc with LMTP id MDucNBythmCTSwAAMoO61A > for <ces(a)ecovillage.cc>; Mon, 26 Apr 2021 05:07:56 -0700 > X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on > box.ecovillage.cc > X-Spam-Level: > X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, > DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE autolearn=ham > autolearn_force=no > version=3.4.2 > X-Spam-Report: > * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP > * 0.0 HTML_MESSAGE BODY: HTML included in message > * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature > * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not > necessarily > * valid > * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from > * author's domain > X-Spam-Score: -1.1 > Received: from authenticated-user (box.ecovillage.cc [45.79.28.18]) > (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 > bits)) > (No client certificate requested) > by box.ecovillage.cc (Postfix) with ESMTPSA id 6EADF3E8CC > for <ssan(a)lists.naturalintelligence.us>; Mon, 26 Apr 2021 05:07:54 > -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; > d=sewagesludgeactionnetwork.com; s=mail; t=1619438876; > bh=1M7F/uIS0bNG6cWjecy/a9QjskrHVwJHkjWRv+ffpM4=; > h=From:To:References:In-Reply-To:Subject:Date:From; > b=jXOswVZgFeHBB+sjIDqVkNBQqIbfZCj9ZUfpVwl10NQEkGaoxckPHNOKT6x9zIqsW > BZ7iZqqi2mWprVQ8LrK48Lp7gvCQ/ipqspMeLt3t+uljzTtryHmV6uJFEAU3hqM33Y > nQqX6Z8la8Ko40F9Ayb4h4e/MOfPdA4nadgf5hZzt/DzPFZvzUbG3V8lWcHuyJNA2y > SQkhbNubQ6iNEEB0SyBjoOjl3g3LVxjxY+9kMGGmX+1PFfW90CpDDShRmKkkscEWaA > NiV0fX6U5LENBBnc6Q9ImLgXuaLdCqlBRBumJBk+eUUr007rpXXVAPck2NvUzGyM2v > kNNGlT68hGzEg== > From: <christian(a)sewagesludgeactionnetwork.com> > To: <ssan(a)lists.naturalintelligence.us> > References: > In-Reply-To: > Subject: How US chemical industry lobbying and cash defeated > regulation in Trump era > Date: Mon, 26 Apr 2021 05:07:37 -0700 > Message-ID: > <020501d73a94$cbe17440$63a45cc0$(a)sewagesludgeactionnetwork.com> > MIME-Version: 1.0 > Content-Type: multipart/alternative; > boundary="----=_NextPart_000_0206_01D73A5A.1F831170" > Thread-Index: Adc6h7I/qzBKx1yOT6aPOuipppacoQACatZAAADW1wA= > Content-Language: en-us > > How US chemical industry lobbying and cash defeated regulation in > Trump era Industry's congressional allies defeated nearly all PFAS > legislation while the Trump EPA killed, watered down or slowalked new > rules > > https://www.theguardian.com/environment/2021/apr/26/us-chemical-compan > ies-lo > bbying-donation-defeated-regulation > > -- 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, 6 months

[MM3-users] Re: Disabled by bounce

by Allan Hansen

Thank you, Mark. By "However, all of the above can be avoided without any DMARC changes by enabling bounce probes." Do you mean that I can get rid of the 'From' mangling, which has been a frequent source of embarrassment because the list address is captured and reused by type-ahead when sending non-list messages and those messages instead going to 1000 subscribers. __ Allan On 2/1/23, 09:59, "Mark Sapiro" <mark(a)msapiro.net> wrote: On 1/31/23 22:32, Allan Hansen wrote: > Hi all, > > Apparently Google just started to get very aggressive about DKIM settings. Some hundreds of my subscribers have had their subscriptions disabled because of Google's bounces. > > I tried to 'Enable' some of them, expecting that their bounce scores would be reset, but when I list the users, the bounce scores are still 5. > > Please advise. Will enabling them without the bounce score being reset just cause the server to disable them again. Yes, Google has started enforcing a policy which is effectively DMARC p=reject even for senders whose domains don't publish DMARC p=reject or quarantine. To avoid this issue, you may need to set DMARC Mitigate unconditionally to Yes as well as DMARC mitigation action to Replace From: with list address if it isn't already. As far as enabling without resetting the bounce score is concerned, I think you are correct that they will just be disabled again on the next bounce. This is a bug and should be fixed. However, all of the above can be avoided without any DMARC changes by enabling bounce probes. in the [mta] section of mailman.cfg, set ``` verp_probes: yes ``` Since the probe is sent From: the list's domain, it should pass googles SPF and DKIM checks and not bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/56WVO6NIOGOBAOOS2B4YCIDJN7VCIXTF/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

3 years, 9 months

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

by Stephan Krinetzki

Mark Sapiro wrote: > On 1/26/22 00:11, Stephan Krinetzki wrote: > > After we enabled the "slow query log", we got in the postgresql database the following output: > > 2022-01-25 12:49:41.538 CET [16126] LOG: unexpected EOF on client connection with an open transaction > > 2022-01-25 15:34:36.047 CET [16864] LOG: duration: 30760.028 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > > 2022-01-25 15:34:36.047 CET [3900] LOG: duration: 9372.471 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > > 2022-01-25 16:42:07.243 CET [3900] LOG: unexpected EOF on client connection with an open transaction > > > > > > Pretty sounds like a database problem? > > The unexpected EOF is because the gunicorn worker timed out and was killed. > There are two DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > transactions because the first one timed out. These came from > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.p... > The accept action is processed and ultimately we get to > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.p... > and that in turn is doing the DELETE at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/pending.p... > There must be some kind of database locking causing this, but I have no > clue as to what it might be. If you haven't done so, I would stop all > the mailman services and the database server and then start them again. > I don't know if that would help, but it might. We did this and nothing changed. I even tried to lookup up potential DB locks, but they are no locks in the database. Side note: Wie have a 37GB big Database with ~4.000 Mailinglists and ~70.000 addresses > > sometimes the log (mailmansuite.log) show us this error > > That too is from the gunicorn worker timing out and being killed. Okay. We already set the timout of the gunicorn process of the mailmancore higher (6 Min) I think there is a communication problem in the chain: apache -> uwsgi -> mailmancore/API ->database but i can't dig deeper there. Let me know if i should provide more details or logs

4 years, 9 months

[MM3-users] Re: mm3 installation question

by Stephen J. Turnbull

Odhiambo Washington writes: > Mark Sapiro writes: > > Some of the `path` settings are probably not in the same order as > > in that file. The > > > > ``` > > path('mailman3/', include('postorius.urls')), > > path('archives/', include('hyperkitty.urls')), > > ``` > > settings should come after the > > ``` > > path('postorius/', include('postorius.urls')), > > path('hyperkitty/', include('hyperkitty.urls')), > > ``` > > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > > order). Or you can just delete the 'postorius/' and 'hyperkitty/' > > ones or you can add > > ``` > > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > > ``` > > to your Apache config. > The odd thing is that the HOWTO that he followed never involves the > manipulation of any urls.py at all - it's not even mentioned at any > point. So obviously the issue is caused by something else and I > suspect something within Apache needs to be re-evaluated in the > guide. I believe this is the Apache configuration the OP is using: <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/admin" "http://127.0.0.1:8000/admin" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" </IfModule> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" URI paths. It is quite unclear to me how this works at all with either the path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), version of urls.py or the reverse order version path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), I think Mark must have a configuration with ProxyPass "/" "http://127.0.0.1:8000/" in the Apache configuration in mind? Or an alias or rewrite rule. Otherwise I don't see how "/postorius" and "/hyperkitty" paths ever get transmitted to the WSGI server. Steve

2 years, 8 months

[MM3-users] Re: SPF check fails for lists subdomain

by Jan Eden

On 2023-01-05 11:13, Odhiambo Washington wrote: > On Thu, Jan 5, 2023 at 10:56 AM Jan Eden via Mailman-users < > mailman-users(a)mailman3.org> wrote: > > > On 2023-01-04 15:07, Mark Sapiro wrote: > > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > > Although I could specify the IP address in my SPF records directly (as > > > > you suggested), I do hope that my understanding of DNS records laid out > > > > above is not entirely misguided. My current setup does work as expected > > > > for eden.one, after all. > > > > > > As I said at < > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > > > I was misreading your DNS and now I am as puzzled as you about the > > failure. > > > > It gets even more mysterious. I tried sending messages from both > > lists.eden.one and janeden.net (my other domain) to a gmail account and > > to another mail provider. Both messages passed the SPF checks on both > > services (s. the relevant headers quoted below). Now because I send > > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > > check operates (and succeeds) on e.g. > > > > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > > (and not on somethingsomething(a)lists.eden.one or > > somethingsomething(a)janeden.net) Could this be the reason for the failed > > SPF checks in Yahoo's and Google's DMARC reports? > > > - Jan > > Might you be willing to use proven tools instead of trying so hard to > understand the myth? > > I use https://easydmarc.com/tools#spf-tools > It allows me to generate, lookup, test SPF, DKIM, DMARC, etc. I did use adequate tools to generate and test my DNS records, and this is why the DMARC reports quoted in my initial message are mysterious to me. Trying hard to solve a mystery might not be productive in every case, but I do not want to stop being curious. - Jan

3 years, 10 months

[MM3-users] Re: Missing bits of French translation

by iMark

>> On 5/12/26 17:30, iMark wrote: >> >> 3. Page text fails. eg. >> ENGLISH: You have to sign in to visit the archives of this list. >> FRENCH: Is in English. >> >> Looking at the .po file ... >> >> /opt/mailman/venv/lib/python3.11/site-packages/mailman/messages/fr/LC_MESSAGES/mailman.po >> >> "PO-Revision-Date: 2024-06-25 17:09+0000\n" ====================================== > On 2026-05-13 02:19, Mark Sapiro wrote: > That file is out of date. It may or may not be from the latest > Postorius released version but it has been subsequently updated for > the next release. > > That particular string is marked fuzzy in the current .po - see > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/locale/fr/…> > > It is marked fuzzy because the msgid was changed at some point from > ``` > msgid "You have to login to visit the archives of this list." > ``` > to > ``` > msgid "You have to sign in to visit the archives of this list." > ``` > > The translations are managed at Weblate. The particular French > translation for Postorius is at > <https://hosted.weblate.org/projects/gnu-mailman/postorius/fr/>. > > The above string is one of 19 that are marked for edit. > > You are more than welcome to create an account at Weblate and fix > whatever needs fixing in the French translation and Weblate will > submit a merge request to update the .po on GitLab. We would be > grateful for your help. ======================================= Thanks Mark. I edited the .po file (on my installation) for Postorius ... /opt/mailman/venv/lib/python3.11/site-packages/postorius/locale/fr/LC_MESSAGES/django.po ... for example ... msgid "You have to sign in to visit the archives of this list." msgstr "Vous devez vous identifier pour consulter les archives de cette liste." ... and recompiled the .mo file ... msgfmt -o /opt/mailman/venv/lib/python3.11/site-packages/postorius/locale/fr/LC_MESSAGES/django.mo /opt/mailman/venv/lib/python3.11/site-packages/postorius/locale/fr/LC_MESSAGES/django.po ... and the text on the webpage is now displayed in French. Happy days! I've created an account at Weblate and will get onto the .po file there. Thank you again for your help.

6 months

[MM3-users] Re: Unable to get Postfix to bounce messages to non-existent lists

by skenny＠scss.tcd.ie

Thanks Mark Sapiro and Stephen J. Turnbull for your responses. Re the output of mailq - this was initially confusing (to me anyway). The diagnostic for the message stuck in the queue was "connection timed out", but the IP listed was the Postfix mail server's not Mailman's. At a guess, Postfix was trying to send the message to Postfix's local domain after it failed to LMTP it over to the Mailman server, and was unable to do that too. Since I posted yesterday, I hit upon a solution that seems to work ... I set relay_recipient_maps to the same value as transport_maps, so that the relevant config lines now look like this: transport_maps = regexp:/var/mailman-data/postfix_lmtp local_recipient_maps = $alias_maps relay_domains = regexp:/var/mailman-data/postfix_domains relay_recipient_maps = regexp:/var/mailman-data/postfix_lmtp This seems to have the desired effect (and, I hope, no unintended consequences). If I fire a message at a non-existent list now, I get an immediate bounce message in my mail client - "Recipient address rejected: User [nonexistent-list(a)lists.scss.tcd.ie] unknown in relay recipient table". No longer is the message loitering in the Postfix queue. The Postfix documentation for relay_recipient_maps says "Optional lookup tables with all valid addresses in the domains that match $relay_domains. [...] Technically, tables listed with $relay_recipient_maps are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from the table lookup." For transport_maps, it says "Optional lookup tables with mappings from recipient address to (message delivery transport, next-hop destination). " Postfix does what we want now: bounce the message is the list name isn't found in relay_recipient_maps, forward it on to the Mailman server via LMTP (transport_maps setting) if it is. Re Stephen J. Turnbull's comment about the patch allowing Postfix to query Mailman's database and more, I think I'll hold off for the moment, but good to know. We will reconfigure when it makes it into an official release (we're using Maxking's Docker images). As ever I'm really grateful for your taking the time to respond, many thanks. Kind regards.

2 years, 8 months

[MM3-users] Re: Unable to update templates

by Mark

On 5/28/25 01:14, Mark wrote: >> >> Then I created a template using Postorius and updated the uri in >> mailman.templates to: >> >> file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use… >> - and that works. >> >> It's looking promising. Now I just need to modify my script that >> periodically copies the data from the >> "mailmanweb.postorius_emailtemplate" table to a file and updates the >> uri. On 2025-05-28 19:17, Mark Sapiro wrote: > Which says get the template from the file system at that location and > don't ask for it from Postorius at all. This would be the default > action if there were no entry for this template in the > mailman.template table at all. I.e. you now have a template in > Postorius, but it is not used. I have jumped the gun on thinking that the template as a file was working. It's not. It's the same story: the initial file template is good, but it's for sure getting cached somewhere, and an updated file is ignored. The same as when the template was being drawn from the database. Restarting mailman3 and mailmanweb didn't help, neither did rebooting the server. Looking at Gunicorn status, I see a failing connection to 127.0.0.1 which is the error message I was getting when adding a new subscriber - with the custom Welcome template in the database (which is why I moved it to file). 127.0.0.1 and locahost are in the ALLOWED_HOSTS and CSRF_TRUSTED_ORIGINS of the settings.py file I'm at a loss with this caching problem. Any other clues happily received. $ gunicorn --version gunicorn (version 21.2.0) $ gunicorn status [2025-05-29 02:29:41 +0000] [17838] [INFO] Starting gunicorn 21.2.0 [2025-05-29 02:29:41 +0000] [17838] [ERROR] Connection in use: ('127.0.0.1', 8000) [2025-05-29 02:29:41 +0000] [17838] [ERROR] Retrying in 1 second. [2025-05-29 02:29:42 +0000] [17838] [ERROR] Connection in use: ('127.0.0.1', 8000) # ps -ef | grep gunicorn root 1522331 1521736 0 22:57 pts/1 00:00:00 grep gunicorn mailman 1608073 1 0 May20 ? 00:01:24 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application mailman 1608075 1608073 1 May20 ? 02:24:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application

1 year, 5 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 2024-06-22 00:04, Mark Sapiro wrote: >>>> ...The mmdf files don't exist in the list's directory although there >>>> have been many posts to the list throughout the day. > If you look at some point prior to 22:30, are there > /opt/mailman/mm/var/lists/<list_id>/digests.mmdf files at that time? > and if so, what happins if you run `mailman digests --periodic` > manually at that point? I changed the digest and notify crons to 05:00. 0 5 * * * @daily /opt/mailman/venv/bin/mailman digests --periodic 0 5 * * * @daily /opt/mailman/venv/bin/mailman notify At ~04:50 I posted an email to the list. The message was delivered to members and archived. Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> # cd /opt/mailman/mm/var/lists/<LISTID> # ls -la total 8 drwxr-xr-x 2 mailman mailman 4096 Jun 22 04:52 . drwxr-xr-x 6 mailman mailman 4096 Mar 25 21:32 .. Then, as "mailman", I ran "mailman digests --periodic" manually and got the same error (as expected since there is nothing there) ... $ /opt/mailman/venv/bin/mailman digests --periodic Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/commands/cli_digests.py", line 126, in digests maybe_send_digest_now(mlist, force=True) File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/app/digests.py", line 106, in maybe_send_digest_now os.rename(mailbox_path, mailbox_dest) FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/mm/var/lists/<LISTID>/digest.mmdf' -> '/opt/mailman/mm/var/lists/<LISTID>/digest.6.3.mmdf'

2 years, 4 months

[MM3-users] Re: Disabling Mass operations

by iMark

> On 1/23/26 17:39, iMark wrote: >> Hi All, >> >> Can anyone give me a pointer on disabling "Mass operations" >> (subscribe/removal) in Postorius. >> >> Just removing the menu link from the list-owners administration pages >> would be a good start. On 2026-01-24 02:01, Mark Sapiro wrote: > > This patch will do that > ``` > --- a/src/postorius/templates/postorius/menu/list_nav.html > +++ b/src/postorius/templates/postorius/menu/list_nav.html > @@ -84,6 +84,7 @@ > {% if user.is_superuser or user.is_list_owner %} > <li class="nav-item"><a href="{% url 'list_template_list' > list.list_id %}" class="nav-link {% nav_active_class current > 'templates' %}">{% trans 'Templates' %}</a></li> > <li class="nav-item"><a href="{% url 'list_settings' > list.list_id %}" class="nav-link {% nav_active_class current > 'list_settings' %} ">{% trans 'Settings' %}</a></li> > + {% if user.is_superuser %} > <li class="dropdown nav-item"> > <a href="#" class="{% nav_active_class current > 'list_mass_ops' %} dropdown-toggle nav-link" data-bs-toggle="dropdown" > role="button" aria-haspopup="true" > aria-expanded="false"> > @@ -98,6 +99,7 @@ > <li><a href="{% url 'mass_removal' list.list_id %}" > class="dropdown-item">{% trans 'Mass removal' %}</a></li> > </noscript> > </li> > + {% endif %} > <li class="nav-item"><a href="{% url 'list_bans' > list.list_id %}" class="{% nav_active_class current 'list_bans' %} > nav-link">{% trans 'Ban List' %}</a></li> > <li class="nav-item"><a href="{% url 'list_header_matches' > list.list_id %}" class="nav-link {% nav_active_class current > 'list_header_matches' %}">{% trans 'Header filters' %}</a></li> > <li class="nav-item"><a href="{% url 'list_delete' > list.list_id %}" class="{% nav_active_class current 'list_delete' %} > nav-link">{% trans 'Delete' %}</a></li> > ``` > Some lines in the above may be wrapped but basically it just adds > > {% if user.is_superuser %} > > and > > {% endif %} > > around the Mass operations code. > Thank you very much Mark. That is perfect. /opt/mailman/venv/lib/python3.11/site-packages/postorius/templates/postorius/menu/list_nav.html Cheers.

9 months, 2 weeks

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

by Jens Günther

Thanks Mark for our answers, I already got a bit further. Am 09.12.23 um 00:27 schrieb Mark Sapiro: >> But it returns {"title": "405 Method Not Allowed"} and I don't know >> where to look in the docs, since it shows almost always a way through >> mailman shell. > You need a PUT command, not POST. Try the above with `-X PUT`. With the `-X PUT`-command, there is the following error: {"title": "400 Bad Request", "description": "Unexpected parameters: bounces_address, created_at, digest_last_sent_at, fqdn_listname, http_etag, join_address, last_post_at, leave_address, list_name, mail_host, next_digest_number, no_reply_address, owner_address, post_id, posting_address, request_address, usenet_watermark, volume"} -> I don't know why, since I tried it with the exact same example-list from where I got all these parameters (ex- and then import) ... do I still miss something? Or does it only work on "fresh" lists? > You can use Postorius -> Mass operations -> Mass subscribe to add the > members, but you can't do that for owners and moderators. Also you lose > information about the members such as Delivery status, Delivery mode and > other user settings. Is there another way to preserve these information about the members? (in general I don't think a lot of people put in effort to customize there memeberships ... and furthermore they would need to register, right?) >> ## registered users > > That is not the answer. Those are Mailman core users, not Django (web > login) users. You need to get the relevant entries from the auth_users > and account_emailaddress tables and add them to the new DB. Ok, that would be fine. Are there any more relations to other tables/columns that need to be set? (I just realised, that there are 2 different id in each table ... the one in auth_users is the user_id in account_emailaddress :-) scary). Do you have any suggestions on how to add them correctly? Thank you in advance for now and another big one in general to all of you on this list that try to help continouisly with all these problems. It's a great pleasure to be able to ask for help on a list like that. Thank you! Have a good rest of the year. Regards, Jens.

2 years, 10 months

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

by Rafael Mora

El jue., 3 ago. 2017 a las 14:09, Simon HANNA (<simon.hanna(a)serve-me.info>) escribió: > > > On August 3, 2017 8:50:41 PM GMT+02:00, Rafael Mora < > rafael.mora.guti(a)gmail.com> wrote: > >El jue., 3 ago. 2017 a las 13:21, Mark Sapiro (<mark(a)msapiro.net>) > >escribió: > > > >> On 08/03/2017 10:42 AM, Rafael Mora wrote: > >> > > >> > I've found the MX records on my cpanel but how do I redirect the > >emails > >> > going to my list to my private server? > >> > >> > >> You have to configure the MTA that is the MX for the domain to relay > >the > >> mail to the Mailman server. > >> > > > >Our domain is: LABBRANDS.COM We have that domain config in a Hosgator > >hosting. The emails sent to labbrands.com go to our hosting, so how do > >I > >tell cpanel in hostgator hosting that the mails sent to the list ( > >mailing(a)labbrands.com) are redirect to the MTA (postfix) in my private > >server (we have static public IP address) ?? > > > You can't redirect one email address using DNS! > If you don't want to host an entire domain on your own server, I suggest > using a subdomain (lists.example.con) instead. > Should I configure my private Centos7 server with subdomain lists.labbrands.com? Doing so how do I redirect the email to the private Centos where postfix and MM3 are installed? > You could probably also redirect one email in cpanel to the subdomain, but > I'm not sure how mailman and clients like emails with different domains... > In theory postfix can send emails using any domain. You just have to make > sure spf, dkim and PTR records are properly set. Otherwise you'll most > likely get issues with rejected mail... > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > 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

9 years, 3 months

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

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > On 21/06/2020 04:52, Mark Sapiro wrote: > > Change that to greyarea-post > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 I don't understand. I'm not in a position to test with Mailman itself right now, but the standalone gunicorn[1] does the right thing (takes an IP address and binds to the corresponding interface, or takes a domain name, resolves it to the IP address, and binds that to the corresponding interface). It does not substitute localhost. It could be a Mailman bug (Mailman 3 is usually configured with all components running on the same host, and that's how it's tested), but first, does greyarea-post resolve to a routable address on the relevant network when queried from that host? > IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed hosts to get the right connectivity, too. I'm not clear on what you're saying. An address is a rendezvous point; if you're not listening on the address that others are using, you won't meet. What good does it do to split them up? It's not clear to me why you think Mailman might want to be multihomed (which is different from the host wanting to be multihomed). I don't object to the work to make it so. But my paranoia says it's best if Mailman is cordoned off into the DMZ with webservers and other hazmat. By design, Mailman core doesn't need to talk to the Internet or to the secure internal network -- Internet functions are delegated to the MTA and the webapps, and local configuration is via shell access which in principle could be console. I'd rather not enable the complexity of a multihomed application unless there's an important use case. (I don't make the final decision, but I am listened to by Those Who Do.) Footnotes: [1] gunicorn is the Python module that manages web services for the REST interface.

6 years, 4 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/19 8:47 AM, Odhiambo Washington wrote: > > > > If you could include the missing steps that you left out then I could > > possibly be able to follow the steps :-) > > > Please help me understand what steps are missing and I will try to > provide the information. Okay. At the installation stage, you say the following: "I already had some things set up in /opt/mailman including a git subdirectory containing clones of the GitLab mailman, mailmanclient, mailman-hyperkitty, hyperkitty, django-mailman3 and postorius projects. On the third server I have added mailman-suite because I use the settings.py from that project as the basis for mine." Please assume that the reader is a newbie to python3 virtualenv and give the details of the commands they need to execute to (a) clone all the projects needed and (b) create the virtualenv. The next steps are: mkdir /opt/mailman/mm Then you say "I then created a /opt/mailman/mm directory and within that a Python 3.6 virtualenv" What happens here is something that needs clarification, because you are specific about "python3.6". I have googled and realized that one has to be specific about the python version they want to use in their virtualenv as shown here -> https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… exact command to execute to create the /opt/mailman/mm/venv exact command to execute to activate virtualenv From there, I think the newbie can follow and fumble till they come up with a working MM3 site. Come to think of it, your steps kind of look clearer than most that I have encountered. I do understand that there are only a few people working on the MM3 development, which I think is the reason there still isn't a document similar to the ones included with MM2.1x source under doc/ However, if your steps here are polished a little, they can possibly become one such doc. I think MM3 docs would come with three options - virtualenv option, docker option and package option. Installing from source seems like something not easily doable. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 10 months

[MM3-users] Re: Dealing with confirmation requests for unsubscribes

by Brian Carpenter

On 11/18/20 6:17 PM, Mark Sapiro wrote: > On 11/18/20 7:41 AM, Brian Carpenter wrote: >> Hello List, >> >> I ran into the following issue for some mailman 3 lists that I am hosting: >> >> https://gitlab.com/mailman/mailman/-/issues/768 >> >> Since there is no way for a list owner to deal with a moderation request >> for an unsubscription task, I assume I need to do something via the >> command line. This is where I need some help with. How do I deal with >> these moderation requests that are unable to be reviewed in an admin gui >> (Postorius/Affinity)? > > mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the test.msapiro.net mailing list > > This > >>>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', > token_owner=TokenOwner.moderator)) > > will return something like > > [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', > 'list_id': 'list.example.com', 'email': 'user(a)example.com', > 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': > 'moderator'})] > > What you want is the token, in this case > 'a8df55f557b5718505280d2613937e25a3109252' > > Then do > > ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') > > which will return > > (None, <TokenOwner.no_one: 0>, None) > > and finally: > >>>> commit() > > >> I do recommend removing such choices for Postorius for Member policy. I >> will be doing this for Affinity until issue 768 is resolved. > The correct thing to do is fix > <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly > will do that rather than remove the moderate and confirm then moderate > unsubscription policies. > > Worked like a charm Mark. Thank you! I forget you guys have a slower process than I when it comes to implementing gui changes. For me, once you have fixed that issue (768), it will be easy for me to reintroduce those two policies for unsubscribing. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 11 months

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Brian Carpenter

On 7/14/20 1:06 PM, Mark Sapiro wrote: > It's confusing, but after adjusting that setting, you need to restart > Mailman core, not gunicorn. > > If you are running a gunicorn service, that is what is providing WSGI > support for Django (Postorius and/or HyperKitty). You may be using > gunicorn for this or uWSGI or Apache mod_wsgi, but is any case, that is > not the gunicorn we are considering here. > > Regardless of what you use to provide WSGI support for Django, Mailman > core uses gunicorn to support the REST API, and that is the gunicorn > affected by the settings in the gunicorn.cfg pointed to by > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > If, with the above configuration, you do `ps -fwwA|grep runner=rest` you > will see something like: > > mailman 20582 20561 0 01:21 ? 00:00:16 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20722 20582 0 01:21 ? 00:01:19 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20725 20582 0 01:21 ? 00:01:18 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20726 20582 0 01:21 ? 00:01:18 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20727 20582 0 01:21 ? 00:01:50 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > > The first of these, pid 20582, is Mailman's actual REST runner. The > other 4 with parent pid 20582 are the 4 gunicorn worker processes forked > from the REST runner. > > It's the REST runner or Mailman core that needs to be restarted to pick > up that change. Thanks Mark. I knew that once but forgot it. -- 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/

6 years, 4 months

[MM3-users] Re: Reject with notification not working

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2026. márc. 24., K, 8:26): > On 3/24/26 11:30 AM, MegaBrutal via Mailman-users wrote: > > I'm creating a newsletter style mailing list where only one address is > > allowed to send e-mails, members just receive them, but they shouldn't be > > able to post to the list. Still I want to send a friendly notification if > > members accidentally try to post to the list, so I set "Reject (with > > notification)" as "Default action to take when a member posts to the > list", > > but it doesn't work: my test address didn't receive any notification > when I > > tried to send a message to the list. > > What is the moderation action for the address you posted from? > I posted if from a member address, and members are set to "Reject (with notification)". The message didn't get to the list (as expected), but no notification was sent either – basically the action was like if I set "Discard (no notification)". > I tried to define the > > "list:user:notice:rejected" template for the list, but to no avail. > What do you mean by no avail? Do you mean the template you defined > wasn't honored. If so, how did you define it? > > Or do you just mean that didn't get you the rejection email? I mean I didn't get a rejection mail. First I assumed that it's because I didn't set a rejection message, but setting one did nothing. Note that I'm managing my list on the Postorius web interface (/mailman3) and don't really know of any other way of doing it. Also I created my list as "Announce only", but this didn't seem to have any effect either. I thought it would create a mailing list that's preset to behave like a newsletter, but it just created an ordinary list where all members can post, and I manually needed to set that I don't accept e-mails from members. I'm puzzled why it even asks for a "List style" in the first place.

7 months, 3 weeks

[MM3-users] Re: Clearing webserver cache - Nginx

by Odhiambo Washington

On Mon, Aug 5, 2024 at 11:55 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/5/24 12:45, Odhiambo Washington via Mailman-users wrote: > > > > Yes, those are Cloudflare IPs and I don't know why 2! > > All I know is that in DNS, I created an A record for the hostname and > chose > > the "proxy" option in the cloudflare DNS management interface. > > OK, I know nothing about how cloudflare proxying works, so ignoring that > and assuming it's OK, ... > ... > > I don't know. However, those IPs you see in the Nginx logs, none belong > to > > me! I have two possible IPs - one domiciled in KE and another domiciled > in > > the US (when I use VPN). > > I think I've misunderstood. Is it the case that the messages you report > like /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed > (2: No such file or directory) ... are in the nginx log on the mailman > server. That's correct. > If so, see > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura…. > > Is that what you have? > Yes. > If not, post your nginx configuration. > In any case, here is my virtualhost config: ``` server { if ($host = mm3-lists.kictanet.or.ke) { return 301 https://$host$request_uri; listen 80; server_name mm3-lists.kictanet.or.ke; return 301 https://mm3-lists.kictanet.or.ke$request_uri; include snippets/letsencrypt.conf; } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name mm3-lists.kictanet.or.ke; ssl_certificate /etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/privkey.pem; ssl_trusted_certificate /etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/chain.pem; include snippets/ssl.conf; include snippets/letsencrypt.conf; access_log /var/log/nginx/mm3-lists_access.log; error_log /var/log/nginx/mm3-lists_error.log; location = /favicon.ico { log_not_found off; access_log off; } location = /robots.txt { allow all; log_not_found off; access_log off; } location /static/ { alias /opt/mailman/mm/static/; } location / { proxy_pass http://127.0.0.1:8010; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 3 months

[MM3-users] Re: Hyperkitty list overview error: thread matching query does not exist

by Darren Hart

On Wed, May 25, 2022 at 08:10:39AM -0700, Mark Sapiro wrote: > On 5/23/22 11:11, Darren Hart via Mailman-users wrote: > > When attempting to visit the hyperkitty archives list overview for one of my two lists: > > > > Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/ > > > > The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load). > > > > The following appears in /var/log/mailman3/web/mailman-web.log: > > > > > > ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist(a)mydomain.com/posted-to > > Traceback (most recent call last): > ... > > File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get > > raise self.model.DoesNotExist( > > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. > > > > Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads. > > > > The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views. > > > > The hyper kitty archives for a second list on this Mailman3 instance is working correctly. > > > > How can I fix this view of the archives? Or how can I get more information on what might be failing? > > > I'm not sure if this will help, but try running your django management > command with arguments `runjob recent_threads_cache`. Note that this will be > run daily if you are running the Cron Jobs for Mailman Web. See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=perio… Thank you Mark. These are in cron, but I ran this (and all the runjobs hourly,daily, etc. options), checking after each. The failure persisted until I restarted mailman3-web, and then it started working again. I'm not sure what combination of cron jobs and restarting resolved the issue, but it's running again. Thanks again. -- Darren Hart Ampere Computing / OS and Kernel

4 years, 5 months

[MM3-users] Re: new list not working

by Christian

See below please... -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, March 10, 2023 7:02 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/10/23 05:07, Christian via Mailman-users wrote: > There are no such messages as you describe. > > After turning on debugging I got this from a test message sent to the > new > list: > > Mar 10 04:39:51 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Mar 10 04:39:51 2023 (1005) Peer: ('127.0.0.1', 51982) Mar 10 04:39:51 > 2023 (1005) ('127.0.0.1', 51982) handling connection Mar 10 04:39:51 > 2023 (1005) ('127.0.0.1', 51982) >> b'LHLO > zarathustra.ccalternatives.org' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'MAIL > FROM:<christian(a)naturalintelligence.us> SIZE=3499' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) sender: > christian(a)naturalintelligence.us > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'RCPT > TO:<redlatinleg(a)lists.ccalternatives.org>' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) recip: > redlatinleg(a)lists.ccalternatives.org > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'DATA' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'QUIT' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) connection lost Mar > 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) Connection lost during > _handle_client() Again, that's only the post being delivered to Mailman. What comes after that in the log? Mar 10 08:39:28 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:39:28 2023 (1005) Peer: ('127.0.0.1', 55662) Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) handling connection Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'MAIL FROM:<christian(a)naturalintelligence.us> SIZE=3498' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) sender: christian(a)naturalintelligence.us Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) recip: redlatinleg(a)lists.ccalternatives.org Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'DATA' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'QUIT' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) connection lost Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) Connection lost during _handle_client() Mar 10 08:44:05 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:44:05 2023 (1005) Peer: ('127.0.0.1', 54800) Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) handling connection Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'MAIL FROM:<> SIZE=1139191' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) sender: <> Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'RCPT TO:<medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org>' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) recip: medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'DATA' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'QUIT' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) connection lost Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) Connection lost during _handle_client() Mar 10 08:45:15 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:45:15 2023 (1005) Peer: ('127.0.0.1', 38820) Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) handling connection Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'MAIL FROM:<> SIZE=1155595' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) sender: <> Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'RCPT TO:<medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org> ' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) recip: medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'DATA' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'QUIT' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) connection lost Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) Connection lost during _handle_client() And have you checked if Mailman's out runner is running? Note that if it died for some reason and wasn't restarted or used up its restarts, restarting Mailman core won't start it. You need to stop Mailman core and then start it. OK I DID THAT Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories? root@zarathustra:/opt/mailman/mm/var# ls -la queue/out total 4416 drwxrwx--- 2 mailman mailman 4096 Mar 10 04:44 . drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. -rw-rw---- 1 mailman mailman 1126829 Mar 10 04:39 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak -rw-rw---- 1 mailman mailman 1083682 Mar 8 20:00 1678334445.1113052+b43224b03f1ba2aa2610301331195b0cbaa151b7.pck -rw-rw---- 1 mailman mailman 1083744 Mar 8 20:00 1678334445.1324928+10c5ec711b7a4364407685b7899a9e8ea25a1a8b.pck -rw-rw---- 1 mailman mailman 1083680 Mar 8 20:00 1678334445.1501603+f2d2895ae7fa80ad387df77ffa17361294fe781c.pck -rw-rw---- 1 mailman mailman 2922 Mar 9 07:49 1678376944.9032273+9923c3da8724cff6ff71b585d1971a90a0ae65cb.pck -rw-rw---- 1 mailman mailman 2862 Mar 9 07:49 1678376944.9125621+2635b96fc6cd2ebb98a2c60a269d07517c1f5046.pck -rw-rw---- 1 mailman mailman 2886 Mar 9 07:57 1678377458.4585488+73f68f6f05d6ee64020e05c8ba2569378e4238f0.pck -rw-rw---- 1 mailman mailman 6600 Mar 9 07:59 1678377564.335885+63793d373c7668947ce4ef2c4a89644ba288d775.pck -rw-rw---- 1 mailman mailman 8290 Mar 9 08:25 1678379122.8619912+bfba87ac1c5e97473ea9c9645a99719d11179308.pck -rw-rw---- 1 mailman mailman 5966 Mar 9 08:48 1678380525.743866+d6f70271750015293a249f9ffae8200367eee509.pck -rw-rw---- 1 mailman mailman 6124 Mar 9 13:01 1678395691.1910245+9e087862cd317d77af8586d5390d60d483af8123.pck -rw-rw---- 1 mailman mailman 2789 Mar 9 13:31 1678397516.4386168+14bb385ad36166aef4a23e1d2b9dd92b50af254d.pck -rw-rw---- 1 mailman mailman 2752 Mar 9 13:31 1678397516.4514658+00546161e5310c988ca3b4d0be4c4a96d3295969.pck -rw-rw---- 1 mailman mailman 2321 Mar 9 13:58 1678399097.1614358+b7b3bfa9cdef9ada94045eed945862664aff065e.pck -rw-rw---- 1 mailman mailman 2390 Mar 9 13:58 1678399097.172284+7188ab4729863b3781c0890ec3b1be7de642454a.pck -rw-rw---- 1 mailman mailman 6031 Mar 9 14:07 1678399672.4968731+2caeb7c82672c9051be407b1cdb7a8b21a87d348.pck -rw-rw---- 1 mailman mailman 2095 Mar 9 14:08 1678399689.8167183+199b2da6cd1f8a00d10c1cd79ccc6cbcb4bdd503.pck -rw-rw---- 1 mailman mailman 7179 Mar 9 14:08 1678399689.8327854+a8d1dc73e5979bde43dccf48caa9bc58de575f41.pck -rw-rw---- 1 mailman mailman 8357 Mar 9 14:19 1678400356.5360696+62b6dce2428e420d6cb53c337c61db69a6fe4d44.pck -rw-rw---- 1 mailman mailman 5939 Mar 9 14:28 1678400903.3894706+d3f5dad6c67057edd0f2888e193dd71de14d2bf9.pck -rw-rw---- 1 mailman mailman 2096 Mar 10 04:43 1678452191.4875023+2e00a89aa5454f965d35a7b8be6a4f620944b8a1.pck -rw-rw---- 1 mailman mailman 7181 Mar 10 04:43 1678452191.4984088+1fd6f3aff9ef79aff269f4edc920f2424a8b35b7.pck -rw-rw---- 1 mailman mailman 6036 Mar 10 04:44 1678452252.847286+552f758b7fca32c2f082bd922f68de1f850dec2d.pck root@zarathustra:/opt/mailman/mm/var# ls -la queue/shunt total 12 drwxrwx--- 2 mailman mailman 4096 Mar 8 12:07 . drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. -rw-rw---- 1 mailman mailman 447 Apr 26 2021 1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck You say that only the new list and one other have this issue, but I wonder if the issue is not with specific lists, but rather with posts after a certain time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ JNZIPCHBZIUUAO5KAQEWQX3UPZ7CZYPV/ This message sent to csa(a)web-analysts.net

3 years, 8 months

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

by Danil Smirnov

Hi Abhilash, Thank you very much - the previous error is fixed now. But I have another one now, which causes the same 500 Server Error: bash-4.3# cat /opt/mailman-web-data/logs/uwsgi-error.log *** Starting uWSGI 2.0.18 (64bit) on [Fri Mar 1 05:42:09 2019] *** compiled with version: 6.3.0 on 01 March 2019 01:52:42 os: Linux-3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 UTC 2017 nodename: mailman-web machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /opt/mailman-web detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! setgid() to 101 setuid() to 100 chdir() to /opt/mailman-web your memory page size is 4096 bytes detected max file descriptor number: 1048576 building mime-types dictionary from file /etc/mime.types...1168 entry found lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 Python version: 3.6.8 (default, Jan 30 2019, 23:58:16) [GCC 6.3.0] Python main interpreter initialized at 0x55a2df7f57e0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 20, in import_string return getattr(module, class_name) AttributeError: module 'django.contrib.auth.middleware' has no attribute 'SessionAuthenticationMiddleware' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "wsgi.py", line 38, in <module> application = get_wsgi_application() File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application return WSGIHandler() File "/usr/local/lib/python3.6/site-packages/django/core/handlers/wsgi.py", line 136, in __init__ self.load_middleware() File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 34, in load_middleware middleware = import_string(middleware_path) File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 24, in import_string ) from err ImportError: Module "django.contrib.auth.middleware" does not define a "SessionAuthenticationMiddleware" attribute/class unable to load app 0 (mountpoint='') (callable not found or import error) *** no app loaded. going in full dynamic mode *** *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 1) spawned uWSGI worker 1 (pid: 37, cores: 2) --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- As per my investigation, this error possibly caused by Django upgrade: *The SessionAuthenticationMiddleware class is removed. It provided no functionality since session authentication is unconditionally enabled in Django 1.10.* See https://docs.djangoproject.com/en/2.0/releases/2.0/ After I've removed the line https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… from settings.py, the container is finally working. I've placed PR in github: https://github.com/maxking/docker-mailman/pull/314 Thank you for your help. Danil пт, 1 мар. 2019 г. в 04:33, Abhilash Raj <maxking(a)asynchronous.in>: > > > On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: > > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> > wrote: > > >Hi Mark, > > > > > >Actually all this stuff happens inside the container after it's started > > >and > > >initialized without errors. I didn't amend the image anyhow. > > > > > >Also I have the configuration based on docker-compose.yaml provided in > > >the > > >repository which works just fine for mailman-web image. > > > > > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) > > >fails > > >with 500 error... > > > > > >Now answering your questions: > > > > > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > > > > > >> do you have django-q in INSTALLED_APPS in your Django settings and > > >what > > >> is set for Q_CLUSTER? > > >> > > > > > >I've checked settings.py inside the container and I haven't found any > > >of > > >the mentioned configurations there. > > > > > >Does the manage.py that's being run here point to the right > > >settings.py? > > >> > > > > > >No clue. > > > > > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK > > >configured image? > > > > > > > https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > > > > Because I am a dum dum ;-) > > > > Will work on removing those crons and stuff. Would be nice if you > > opened an issue on Github so that I don't forget. > > Should now be fixed in the latest image. > > > > > >Danil > > > > > > > > > > > >> -- > > >> 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/ > > >> > > >_______________________________________________ > > >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/ > > > > > > -- > > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > thanks, > Abhilash Raj (maxking) >

7 years, 8 months

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

by Florian Schulze

On 2 Jul 2020, at 8:38, Florian Schulze wrote: > On 30 Jun 2020, at 8:22, Florian Schulze wrote: > >> On 29 Jun 2020, at 23:40, Mark Sapiro wrote: >> >>> 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? >> >> Yes >> >>> Are you running the Django periodic jobs? >> >> They were disabled because of the errors (someone else did the >> upgrade). I have enabled them again and will watch it and report >> back. > > The cronjobs seem to work fine, no errors so far. > > The queue doesn't seem to change at all. In "qmonitor" there is > nothing listed and the statusline remains the same at > ORM default Queued 303(118) > Success 100 Failures > 0 I managed to figure out how to inspect the queue in the admin interface. I just deleted all the repeatedly failing tasks and ran all cron jobs. I hope it is fine now. Regards, Florian Schulze

6 years, 4 months

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

by Abhilash Raj

On 12/14/22 03:31, Mark Sapiro wrote: > On 12/13/22 10:38, Dan Caballero wrote: >> Hi Mark, >> >> I ran the commands and it took about 35 seconds for the loop to run. >> >> Here's the result. >> >>>>> count >> 4168 > > > So that's at least part of the issue. How does 35 seconds compare to the > length of time to process one moderated message through Postorius? > Probably should've read more of the thread before previous reply ;-) So, the issue _could_ be due to latency to the remote database vs local database that we have on m.p.o. Mailman3 is not very efficient when it comes to total no. of database queries done per operation, which is something I have been (very slowly) tracking and fixing on a case-by-case basis. So, for example, handling 1 held message in m.p.o made 1.1k postgres database calls in total and even though they were each only few hundred micro-seconds each, the total added up to roughly ~2sec avg response time on the handle message API endpoint. If you handle more than 1, it scales linearly. My suspicion is that in your case Dan, due to a remote instance, the latency per call is higher (maybe in the order of few or 10s of milliseconds is my guess?) and then depending on the total no. of entries you have in pendings and pendedkeyvalue tables (with some filters, not _all_ entries), it adds up to a high value. The no. of database calls here is of order n^2, where n is the entries in pendings of type "held message" and "data" and their respective linked relationships in pendedkeyvalue table. My MR makes it such that we don't need to scan all entries of "type"="data", so that part will become constant time. And the pending of type "held message" will be limited to no. of held messages in a single MailingList(compared to all mailing lists like today), so it will help depending on the distribution of held messages in various lists. I am also exploring ways to make that 2nd query also constant time. -- thanks, Abhilash Raj (maxking)

3 years, 11 months

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

by Onyeibo Oku

On Sun, 23 Oct 2022 08:00:19 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/22/22 21:29, Onyeibo Oku wrote: > > > > Now Mailman starts, and stops as desired when running as mailman > > user (both in virtual and non-virtual environments). However, > > running the service via systemd still fails. I now get a different > > traceback: > > > > Oct 23 03:43:00 mail.server.tld mailman[19410]: Traceback (most > > recent call last): > ... > > Oct 23 03:43:00 mail.server.tld mailman[19410]: with > > open(self._claimfile, 'w') as fp: Oct 23 03:43:00 mail.server.tld > > mailman[19410]: PermissionError: [Errno 13] Permission denied: > > '/opt/mailman/mm/var/locks/mailman-cfg.lck|server.tld|19410|619270043958240354' > > Oct 23 03:43:00 mail.server.tld systemd[1]: mailman3.service: > > Control process exited, code=exited, status=1/FAILURE > > What are ownership and permissions on /opt/mailman/mm/var/locks/ > > Assuming they are > > drwxr-xr-x mailman mailman > > it must be the case that systemd is not running the > `/opt/mailman/venv/bin/mailman start` command as the `mailman` user. > I suspect this is a Fedora issue. I note that > https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administe… > does not mention User or Group. You might try replacing > ``` > ExecStart=/opt/mailman/venv/bin/mailman start > ExecReload=/opt/mailman/venv/bin/mailman restart > ExecStop=/opt/mailman/venv/bin/mailman stop > > with > > ExecStart=sudo -u mailman /opt/mailman/venv/bin/mailman start > ExecReload=sudo -u mailman /opt/mailman/venv/bin/mailman restart > ExecStop=sudo -u mailman /opt/mailman/venv/bin/mailman stop > ``` > This does not work. Systemd says it cannot find sudo (file). After updating in the commands "sudo" to "/bin/sudo" afterwards Systemd throws a different error message: PermissionError on /bin/sudo This is tiring. At this moment I am left with the possibility that SELinux may be in the way. I cannot think of a way to prove this hypothesis. This is speculation. Perhaps I should try another installation method other than Virtual. I found Mailman3 in Fedora repository. Yes, it is packaged. May be I should try that or perhaps I should try the git version. I'd be happy to have a functioning Mailman before Friday. Regards Onyeibo

4 years

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

by Mark

On Sat, 2023-09-23 at 20:28 -0700, Mark Sapiro wrote: > > 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)> > >>> > ``` Hi Mark, I'm still on this problem of one list's archive-search not returning any results. I created a new list today and it also has the same problem. In short, the older lists all seem fine -- their search results are up- to-date so that tells me the cron is okay. It's just these 2 newer lists that have the problem. It's taken me while to get my head around the Django admin command you have suggested, as I kept getting an error when starting: #django-admin shell >>> from hyperkitty.models.mailinglist import MailingList ... django.core.exceptions.ImproperlyConfigured ... That sent me down a rabbit hole which I haven't emerged from yet. But instead, starting with # python3 manage.py shell ... # python3 manage.py shell Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models.mailinglist import MailingList >>> mlist_name = 'thepost(a)example.com' >>> mlist = MailingList.objects.get(name=mlist_name) >>> mlist <MailingList: <MailingList thepost(a)example.com>> >>> The format of my final line is different to yours ... Mine: <MailingList: <MailingList thepost(a)example.com>> Yours: <MailingList listname(a)domain.com (listname.domain.com)> Does this (missing list_id) give any clue as to why the archive-search isn't working, or is just that starting with "# python3 manage.py shell" is the wrong thing to do? By the way, the list_id shows correctly in the SQL query result. select * from hyperkitty_mailinglist where name like 'thepost(a)example.com'; ... name | thepost(a)example.com | list_id | thepost.example.com ... Any ideas appreciated. Mark

3 years, 1 month

[MM3-users] Re: urls.py location on venv install

by Torsten

Hi Mark, I had a very productive session with Odhiambo today and everything is now up and running. We installed everything with the commands you mention below and after some weird issue that mailman info first used /etc/mailman3/mailman.cfg but later switched to /opt/mailman/mm/var/etc/mailman.cfg (which only consisted of comments and no real configuration) things have settled and now my instance is up and running still containing the list and all members. The only thing I lost is the archive but that is probably gone for a while now and not worth getting back. Thanks to everyone for their help, especially to Odhiambo. Am 2026-08-12 18:30, schrieb Mark Sapiro: > On 8/11/26 22:46, Torsten wrote: >> >> But it seems that 3.3.10 depends on nntplib >= 3.13 which could not be >> fetched via pip: > > That's a bug. The requirement in Mailman 3.3.10's pyproject.toml is > ``` > 'nntplib; python_version>="3.13"', > ``` > This is wrong. it should be > ``` > 'standard-nntplib; python_version>="3.13"', > ``` > nntplib was dropped from the standard library in Python 3.13 and > replaced by standard-nntplib from pip. > > Because of the above error, a pip install of mailman 3.3.10 will not > work with Python >= 3.13. > > Also note that currently, Mailman core is not compatible with Python >= > 3.14 because it depends on aiosmtpd which is not compatible with Python > 3.14. The aiosmtpd incompatibility is fixed in GitHub but the fix is > not yet released. The incompatibility is fixed by > <https://github.com/aio-libs/aiosmtpd/pull/575> and > <https://github.com/aio-libs/aiosmtpd/pull/595> > >> I have, nevertheless, standard-nntplib 3.13 already installed but >> there is no nntplib on Pypi. > > I suggest the following depending on your Python version > > For Python 3.13 or 3.14 > ``` > pip install git+https://gitlab.com/mailman/mailman.git > ``` > and for Python 3.14 > ``` > pip install git+https://github.com/aio-libs/aiosmtpd.git > ``` > Installing Mailman from GitLab with Python 3.13 should work fine. Both > this list and the lists at mail.python.org run the latest GitLab > version with no problems. The installation of aiosmtpd from GitHub is > more of an unknown, but should be OK.

3 months

[MM3-users] Re: Templates

by David Krantz

On Sat, Sep 23, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > Have you tried restarting/reloading whatever dbm (MySQL, PostgreSQL, ?) > you are using? No, that would have been strange to me; the table in the database was up to date. But now I tried that, I got no effect this time but I probably could set up a better test. I also had another problem [solved]: I get the error message "Multiple rows were found for one_or_none" when I try TemplateManager.get(name, context) for the list. There is only one matching row in the templates table so something is fishy with the ORM. This occured when I changed to the previous uri value. As the database does not have any duplicates in the templates table I suspect either a broken join or that the cache retains the old value. The traceback looks like this in the mailman shell: >>> tm.get('list:member:regular:footer', 'test.example.com') Traceback (most recent call last): File "<console>", line 1, in <module> File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/template.py", line 98, in get contents = cache_mgr.get(actual_uri) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/cache.py", line 125, in get CacheEntry.key == key).one_or_none() File ".../venv-3.5/lib/python3.5/site-packages/SQLAlchemy-1.2.0b2-py3.5-linux-x86_64.egg/sqlalchemy/orm/query.py", line 2814, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Workaround: Delete cached files in .../var/cache and run delete from file_cache in postgresql. Then that works again. The culprit was that the file got cached twice so there is a bug in the cache function. I used the ITemplateManager-util in the shell to cause the problem. >> 2. the $user_delivered_to and $user_email do not expand for some >> reason. Known problem? > > > These require that the list delivery be personalized. See > <http://mailman.readthedocs.io/en/latest/src/mailman/runners/docs/outgoing.h…>. > That explains things. Thank you! Now I got two footers, first one without personalisation and one personalised. Interesting. best regards // David

9 years, 1 month

[MM3-users] Re: templates

by Odhiambo Washington

On Fri, May 5, 2023 at 12:38 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/23 13:13, Odhiambo Washington wrote: > > Isn't that the same thing as not having them in the FS? > > If your installation is in a venv for example, the base templates are in > venv/lib/python3.x/site-packages/mailman/templates/. Isn't that part of > the FS? > <Confession> This is new knowledge that I did not posses previously as I have never seen it mentioned anywhere in the documentation that I have read. Maybe I was going to come to it one day. In the documentation that I have read, even the one from this <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>, I never imagined about the presence of some defaults so I copied the ones that you shared and edited them. I had made a point of asking a question around this statement: "There are several default templates that have incorrect or generic URLs for the web UI. To make these better, I installed these templates in /opt/mailman/mm/var/templates/site/en/ as follows.." from the above link, but it kinda escaped me. I had wondered where they were. In those days, MM3 installation process was still as scary as hell for many people, me being one of them, or was it the scare of the snake (Python) :-) True story - also one that can be gleaned from the myriad stupid questions I asked on the MM3 list over the years - it took me years to get to wrap my head around MM3! I find it hard to imagine that I have become a great supporter for this thing that scared me for ages, since the days when it was in BETA. The venv example has made the process very easy. In fact, after you and Abhilash helped me internalize what a venv is, I have been able to comfortably run other projects in virtualenv. These days I can install MM3 in just a few hours - getting all the components running - Core, Web, MTA, and Apache (whether with uWSGI, mod-wsgi or Gunicorn). </Confession> And I continue to learn new things everyday. -- 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]

3 years, 6 months

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Henrik Rasmussen

Henrik Rasmussen wrote: > Abhilash Raj wrote: > > On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro > > wrote: > > each other, but Postfix is trying to deliver > > mail via lmtp to > > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > > listening on port 8024. Either that is not the case or that port is not > > exposed to Postfix on IP 172.19.199.2. > > Right, that is what I was wondering, you verify that by using telnet > > on the specified IP and Port (172.19.199.2:8024). > > Yes, the postfix container listens on 172.19.199.2:8024 > [root@postfix /]# nc -v 172.19.199.2 8024 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.19.199.2:8024. > 220 mailman-core GNU Mailman LMTP runner 2.0 > > > docker-compose ps lists all the running containers, > > do you see all > > the containers running? > > That also seem to be okay > [root@lstapp01pl ~]# docker ps > CONTAINER ID IMAGE COMMAND CREATED > STATUS PORTS > NAMES > bddc80799b8c maxking/mailman-web:0.2 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 8000/tcp, 8080/tcp > mailman-web > be098b18aeca maxking/mailman-core:0.2 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 8001/tcp, 8024/tcp > mailman-core > c47fd8ccf19d postgres:9.6 "docker-entrypoint.sh" 16 hours ago > Up 16 hours 5432/tcp > mailman_database_1 > 699264501acd mailman3-mime_htmlizer "container-entrypoint" 16 hours ago > Up 16 hours 8080/tcp > postmime > 90f381a74709 mailman3-postfix:v1.1 "./entrypoint.sh" 16 hours ago > Up 16 hours 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp, > 0.0.0.0:26->25/tcp postfix > > And netstat in the mailman-core container shows: > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 172.19.199.2:8024 0.0.0.0:* LISTEN` > > > You mentioned that Mailman is not receiving enough > > emails, do you get > > any emails from Mailman? I am trying to see if this is a perf problem > > or if Mailman's LMTP isn't reachable at all. > > Mailman do send out mails like when someone signs up for an account. > Thanks to both. And the runner is running: `Sep 19 06:55:06 2019 (36) b'220 mailman-core GNU Mailman LMTP runner 2.0`

7 years, 1 month

[MM3-users] Re: Mailman installation results in KeyError: 'env_py'

by Marvin Gülker

Am 22. October 2017 um 07:49 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > or you can install the fix at Thanks. Applying this patch makes it work. Now I've got a different problem, though. I can't get it to connect to Postfix for sending emails it appears. After I created a superuser account using $ python manage.py createsuperuser as described on <http://postorius.readthedocs.io/en/latest/setup.html>, I tried to login using this credentials into Postorius. It then reported it sent a confirmation email to me (for an account I created on commandline?!), but Postfix' logs reveal that it didn't; there's not even a sign of an attempted delivery in /var/log/mail.log. I've configured the Postfix configuration in mailman.cfg like this: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix as was outlined on <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html>. mailman-suite's settings.py contains: # Change this when you have a real email backend EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 which was described on <http://docs.list.org/en/latest/config-web.html>. For completeness, the following is in Postfix' main.cf, but is not the cause of the problem as it affects the incoming direction, whereas I refer to the outgoing one: transport_maps = hash:/home/mailman/var/data/postfix_lmtp local_recipient_maps = hash:/home/mailman/var/data/postfix_lmtp I failed to locate any kind of logging information about the failed email, so I don't even know where I should start looking for the problem. var/logs/smtp.log is empty in the mailman directory, and likewise is logs/mailmansuite.log in the mailman-suite_project directory. That being said, the enormous number of configuration files to consider and dozens of cross-references to other pages in the docs make the installation guide hard to follow; it also lacks logical structure in my opinion, when it refers to parts of the configuration which are later explained. For someone like me who never programmed a Django application (Ruby dev) this is all pretty cryptic. Especially, that some parts of information are on <http://docs.list.org/en/latest/index.html> whereas other parts are scattered over readthedocs.io makes it very complicated. Greetings Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

9 years

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

by Brian Carpenter

On 10/29/20 11:33 AM, Mark Sapiro wrote: > On 10/29/20 5:23 AM, Brian Carpenter wrote: >> I have a list owner who had his subscription policy set to confirm. >> Apparently that was too hard for his list members to handle so he >> changed it to moderate only. If someone sent a subscription request that >> needed to be confirm, did not respond to it, and then tried subscribing >> again after the member policy changed to moderate, their 2nd >> subscription attempt still shows up in the confirmation queue. Is that >> normal behavior. My understanding is it is. Please let me know if I am >> wrong here. > > Are you certain that the request waiting confirmation is the second one > and not the first? Good point and I am not sure. I will try to note that if this pops up again. > > >> The real mystery here is when someone tried subscribing again >> (listname-subscribe@listdomain) hours after the subscription policy was >> changed to moderate and they still showed up in the confirm queue. How >> is that possible? I tested the list with two of my addresses and both >> showed up in the moderation queue as expected. As far as I can tell from >> the mailman logs, this was the person's first attempt at subscribing. > > I suspect it was not the first attempt and that the subscription waiting > confirmation was requested when the policy was confirm. The confirmation moderation notice had the date-time stamp that came a few hours AFTER the subscription policy was changed. Also I only saw one confirmation request sent out via Postfix' mail.log. I saw no other for this subscriber. Same thing with the smtp.log. I cannot duplicate this behavior when I try to subscribe. My subscription attempts went straight to moderation. > > The real question is if a user has a subscription waiting confirmation > and the policy is changed to moderate, is a second request rejected > because of the request waiting confirmation. If so, I think this is a > bug which should be fixed. > Do you think this is a bug with Mailman core or my system? -- Brian Carpenter Harmonylists.com Emwd.com

6 years

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-27 19:36, Jan Eden wrote: > On 2022-11-27 08:01, Mark Sapiro wrote: > > On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > > > > > – but the existing directory /opt/mailman/fulltext_index (and its > > > contents) are readable and writeable by mailman:mailman: > > > > > > > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > > > > > > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > > > > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > > > > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > > > > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > > > > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > > > > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > > > > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > > > > > I fail to see where haystack tries (and fails) to create the directory. > > > FWIW, deleting threads is not a problem. > > > > It is uwsgi trying to do this. What user is it running as? Maybe you need to > > add that user to the `mailman` group. > > That's what baffles me – uwsgi is run as the mailman user: > > mailman 3904667 1.3 0.5 129516 62188 ? Ss 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > mailman 3904668 0.0 0.3 203248 48796 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > mailman 3904670 0.8 0.6 220436 74464 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini I tried setting permissions on /opt/mailman/fulltext_index to 777 temporarily, but the issue remained (as expected). It occurs in the Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > if self.use_file_storage and not os.path.exists(self.path): os.makedirs(self.path) where self.path is referenced, which is defined in line 110 (as part of the __init__ function): > def __init__(self, connection_alias, **connection_options): > super().__init__(connection_alias, **connection_options) > self.setup_complete = False > self.use_file_storage = True > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > self.path = connection_options.get("PATH") Unfortunately, I cannot see where the PATH key for connection_options is defined. - Jan

3 years, 11 months

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 4/25/21 2:20 PM, Andrew Hodgson wrote: >> Hi, >> >> Hyperkitty 1.3.4. >> >> I am trying to download a complete list mbox by going to all threads view and using the download option. I have tried a couple of tools (Gunzip and Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. [...] >Depending in the web server configuration, timeouts can occur when downloading large archive mboxes. instead of downloading the entire mbox with <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, >do it in pieces by adjusting start and end. e.g. [...] >Although, I don't think timing out is the issue, and I'm not sure what is, but I think it has something to do with messages in the archive. If I try to get the 3 pieces as above, the first piece with start=2008-02-19&end=2012-12-31 works but the others don't and even the smaller Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: [2021-04-26 08:53:12 +0000] [28181] [ERROR] Error handling request Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request for item in respiter: File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox msg = email.as_message() File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message msg["Message-ID"] = "<%s>" % self.message_id File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ self._headers.append(self.policy.header_store_parse(name, val)) File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse raise ValueError("Header values may not contain linefeed " ValueError: Header values may not contain linefeed or carriage return characters I do still have the original mbox files for the imported lists which were on Mailman 2.1. The other thing is when downloading these mbox files I noticed they aren't the raw messages as we had in Mailman 2.1 but modified with headers stripped and email addresses modified. Is there any way to get the raw mbox back as in the option we had in Mailman 2.1? Thanks. Andrew.

5 years, 6 months

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

by David Partain

On Thu, 2021-02-25 at 13:24 -0800, Mark Sapiro wrote: On 2/25/21 6:32 AM, David Partain via Mailman-users wrote: In /etc/mailman3/mailman.cfg I see: class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 Should I change the latter to be something like: url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 Yes, either make it charset=utf8mb4 or I think dropping the charset= option altogether will use the database default, however I'm not clear why this would be the issue as this only controls how Mailman core accesses the database, and your issue is with HyperKitty/Django and its access is controlled by the DATABASES setting in Django's settings which you say do specify 'charset': 'utf8mb4' in OPTIONS. Also, it seems Mailman core is not even using the same database - i.e. `mailman3` whereas Django's is `mailman3web`. Hi Mark, Thanks for being patient with me. I'm still baffled but might have found the problem. I've done the above, to no avail. If I look at the queries being sent to mysql, I see stuff like this: 174 Connect mailman3web@localhost<mailto:mailman3web@localhost> on mailman3web using TCP/IP 174 Query SET sql_mode='STRICT_TRANS_TABLES' 174 Query COMMIT 174 Query SET AUTOCOMMIT = 0 174 Query SET AUTOCOMMIT = 1 174 Query SET AUTOCOMMIT = 0 I note that there is nothing about the charset, so something's clearly wonky. As previously stated, /etc/mailman3/mailman-web.py has the right thing: 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, but that latter is having no effect. I then found /var/lib/ucf/cache/:etc:mailman3:mailman-web.py which doesn't have charset (but does have init_command), but I _think_ that's only about the package management system. So... I found that /usr/share/mailman3-web/settings_local.py is just a link to /etc/mailman3/mailman-web.py (which obviously has the right thing), but what about the .pyc file? # grep -i STRICT_TRANS_TABLES /usr/share/mailman3-web/settings_local.pyc Binary file /usr/share/mailman3-web/settings_local.pyc matches # grep -i charset /usr/share/mailman3-web/settings_local.pyc # It ain't in the .pyc file. Am I overly optimistic that that might the be problem? If so, I'd be grateful if someone'd tell the newbie how to recreate that file without trashing something. Cheers, David

5 years, 8 months

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

by Abhilash Raj

On Sat, Jul 25, 2020, at 2:17 PM, Mark Sapiro wrote: > On 7/25/20 12:54 PM, Odhiambo Washington wrote: > > > > 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?? > > I manage more than one server that supports both Mailman 2.1 and Mailman > 3 running as user `mailman`. I'm not aware of any security issues. > > > > 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 > > T don't recommend using --force in init scripts. It *shouldn't* matter > because even with --force the master shouldn't break the lock if the pip > that set it still exists, but I prefer not to use it. > > > > ;; > > 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)* > > > Hmm... strange, My various MM 3 installs are running falcon 1.4.0, 2.0.0 > and 3.0.0a1 and I don't see this warning, but it is only a deprecation > warning. It doesn't mean it won't work. I have seen this during development and there is an issue open for this[1]. [1]: https://gitlab.com/mailman/mailman/-/issues/733 > > > > But: > > > > (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman > ... > > It seems Mailman core and the rest runner and its workers are all running. > > > > > > 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?? > > Yes, I think so. > > > > 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. > > > The above is all fine, but it is just Mailman core. > > > > How do I access the web UI for MM3 now? > > > The Apache config points to /opt/mailman/mm/wsgi.py, a sampole of which > is at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>. > Do you have that? > > If you installed the Apache config literally, the location for Mailman 3 > is defined by > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > and the URL would be http(s)://your.server/mm3 - have you tried that? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 3 months

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

by Élodie BOSSIER

Thank you for your response Mark, With Mailman 2.1, the lists were split on their webpage respectively. How could I do same with Mailman 3.3.3 (Tom Sawyer) please ? My domain table SQL have this result : id, mail_host, description, alias_domain 1, ml.franceserv.fr, NULL, local.ml.franceserv.fr 2, ml.viticreation.fr, NULL, local.ml.viticreation.fr mailinglist table SQL : id, list_name, mail_host, list_id, ... 1, bar, ml.franceserv.fr, bar.ml.franceserv.fr, ... 2, viticreation, ml.viticreation.fr, viticreation.ml.viticreation.fr, ... Can I do something ? A patch somewhere ? Shall I wait issues are solved and how long approximatively please ? Which don't reassure me is I can see old discussions about FILTER_VHOST there are 2 years. I can retrieve my own old question there are 2 years when I tried to migrate from Mailman 2 to Mailman 3 : https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and in 2020 you told me it was working for you at this date. It's don't reassure me to retrieve a problem I got there are 2 years. I could set in production my Mailman 3 but the problem is my customers won't understand why they can see the lists of others domains name ... and not sure about the security ... Thank you again. Le 18/02/2022 à 00:33, Mark Sapiro a écrit : > There are issues with FILTER_VHOST due to the fact that mailing lists > do not have a web host attribute. This means when you go to HyperKitty > or Postorius when FILTER_VHOST is True, we look up the domain record > for the web host you are visiting and show you all the lists whose > mail host matches the mail host for the web host domain. This has > nothing to do with alias domains. > > What that means is if all your domains records have a unique mail > host, FILTER_VHOST will work as you expect, but if multiple domains > have the same mail host FILTER_VHOST will show you the lists for the > current web host plus all those with a matching mail host. > > I.e. if in your case, the ml.franceserv.fr domain and the > ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't > separate them. If they have different mail hosts FILTER_VHOST will > separate them. >

4 years, 8 months

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by tlhackque

On 17-Oct-20 14:31, Mark Sapiro wrote: > On 10/17/20 10:39 AM, Torge Riedel wrote: >> The message is being held because: >> >> Header "Yes" matched a header rule >> >> At your convenience, visit your dashboard to approve or deny the >> request. >> >> I think this is wrong, it should read 'Header "x-spam" matched a header >> rule'. Cause the header rule is configured for header "x-spam" and >> pattern "Yes". > > The message is defined as > > 'Header "{}" matched a header rule' > > where {} is replaced with the value of the matching header. I agree it > would be better if it were something like > > 'Header value "{}" matched a header rule for {}:' > > with {}s replaced with the header value and name. That would make it in > your case > > 'Header value "Yes" matched a header rule for x-spam:' > >> I haven't found a bug report for this yet on gitlab. If someone of the >> developers confirm this is wrong, I will file a bug on gitlab for it. > > Please do file a bug. It won't be fixed until after the upcoming 3.3.2 > final release because we not making i18n changes between the candidate > and final releases. Also, if you don't like my suggestion, feel free to > suggest something else. > FWIW, I suggest: Header "{name}": rule matched value "{value}" Name tends to be short and must be simple ASCII. Value can be very long and encoded, so it may wrap. Name will be short and recognizable. Plus the name provides the context for the value - and name:value is the way the header appears in the e-mail. So I think name before value obeys the UI principle of least surprise. I might also add the rule number or config filename:line, as in Header "{name}": rule in {file}:{n} matched value "{value}" This would be helpful when backtracking from a rejected message to the cause. A sample expansion might be: Header "X-Spam": rule in foo.conf:83 matched value "yes"

6 years

[MM3-users] Re: Problem updating mailman

by Odhiambo Washington

On Sun, 24 Jan 2021 at 00:46, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/23/21 2:56 AM, Odhiambo Washington wrote: > > I am getting this error after I did a git pull and build. > > > > (venv) [mailman3@gw ~/git]$ /opt/mailman/mm/bin/mailman-post-update > > + '[' False == False ']' > > + mkdir -p /opt/mailman/mm/static > > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > +* /opt/mailman/mm/bin/django-admin compress* > > CommandError: An error occurred during rendering > > > /opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.3.4rc2-py3.7.egg/hyperkitty/templates/hyperkitty/404.html: > > /usr/local/lib/ruby/site_ruby/2.7/rubygems/dependency.rb:311:in > `to_specs': > > Could not find 'sass-listen' (~> 4.0.0) among 4 total gem(s) > ... > > > Ruby-sass is no longer supported. Please see the Sass compiler section > at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#dependencies > >. > I uninstalled rubygem-sass from the OS. I don't remember consciously installing that because it was never in the guide I followed (which is your own writeup). But I still have a problem: (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 + /opt/mailman/mm/bin/django-admin compress CommandError: An error occurred during rendering /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: */bin/sh: sass: not found* pip3 install sass fails: ..... ERROR: Command errored out with exit status 1: /opt/mailman/mm/venv/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-vnlujru1/sass_15812b8baa1b405c8130edb21a4f4316/setup.py'"'"'; __file__='"'"'/tmp/pip-install-vnlujru1/sass_15812b8baa1b405c8130edb21a4f4316/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-_f8rgww1/install-record.txt --single-version-externally-managed --compile --install-headers /opt/mailman/mm/venv/include/site/python3.7/sass Check the logs for full command output. The complete failure text is at https://pastebin.ubuntu.com/p/tsB2CCNrQG/ Maybe it's time to blow up everything in the virtualenv and start over because I am not sure what caused this. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 9 months

[MM3-users] upgraded Django & flufl.lock now do not receive own postings

by Christian

I just upgraded Django from version 3.0.11 to 3.2.15 receiving this confirmation > Successfully installed Django-3.2.15 asgiref-3.5.2 I also upgraded flufl.lock from version 7.0 to 7.1 > Successfully installed flufl.lock-7.1 Then I restarted mailman, qcluster & gunicorn Now for some reason I'm not receiving my own postings to the list whereas before I was. 'Receive own postings' is still set to yes. Thank you! -----Original Message----- From: David Newman <dnewman(a)networktest.com> Sent: Friday, July 8, 2022 11:29 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14 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? Yes > > So I would guess you can remove them. Probably you have the relevant > Ubuntu packages cached somewhere, and they're probably available from > Ubuntu if you really wanted them. This system runs Debian 11, with everything installed in a venv. I'm unclear on the relationship between the usual apt* tools and pip, and just do everything Mailman-related using pip. On 7/8/22 7:47 AM, Mark Sapiro wrote: > 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. Ahhh, that explains it. Thanks for your replies. I've deleted the ~ directories and so far have not noticed any adverse effects. dn _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 2 months

[MM3-users] Re: Message shows up individually but not in the thread

by Marvin Gülker

Am 03. November 2017 um 12:35 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > Are you running all of Django's periodic tasks? They are running. This is the excerpt from /etc/crontab: # Mailman jobs @daily mailman bash -c 'cd /home/mailman && . /home/mailman/env3/bin/activate && mailman digests --send' @hourly mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs hourly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' @daily mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs daily --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' @weekly mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs weekly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' @monthly mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs monthly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' @yearly mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs yearly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' * * * * * mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs minutely --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' 2,17,32,47 * * * * mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs quarter_hourly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings Obviously, mailman-suite is installed at /home/mailman/mailman-suite and owned by user 'mailman', with the actual Django project in the subdirectory 'mailman-suite_project', just as cloned from the Git repository. The only difference from the official guide here is that I took the liberty to place Mailman into two virtualenvs (a Python2 one for the Django project, and a Python3 one for Mailman-Core*). There are no errors reported with this in /var/log/cron.log. And before you ask, the task queue is running as well. The uWSGI config has this: # Setup the django_q related worker processes. attach-daemon = ./manage.py qcluster And the qcluster process shows both up in the process list and is happily logging away in the uWSGI log. Greetings Marvin * It'd be great if the mailman-suite was moved to Python 3 at some point. That way one wouldn't need two separate virtualenvs. -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

9 years

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

by William Oliver

On Sat, 2022-02-19 at 12:03 -0800, Mark Sapiro wrote: > On 2/19/22 08:33, William Oliver wrote: > > > > So... I run a small mailinglist using mailman3 that has been > > workiing > > great for a couple of months. Last week, all my users from gmail > > got > > kicked off because gmail decided that the list messages were > > "unsolicited email". I didn't find out about it until the users > > hit > > their mailman3 bounce limit. I *thought* would be seeing all the > > bounce messages, but apparently not. I didn't see any config > > settings > > for "see all the bounce messages" so i thought to myself, "Self, > > well > > maybe that's because my mailinglist username doesn't have a > > mailbox in > > /home/listname". > > > Assuming your Mailman core version is 3.3.5 and Postorius is 1.3.6, > you > will see settings like `Notify owner on bounce increment`, ` Notify > owner on disable` and `Notify owner on removal` under `Bounce > Processing`. Presumable you did get the notification of removal, so > delivery to the owner works. Are the increment and disable (or maybe > just disable if your versions are older) notices set to Yes? Found it. Thanks. > > > > So, I decided to try that. I created /home/listname/Maildir/* and > > logged in as fplist to see if it would put mail there. In order to > > log > > in as listname, I gave the user listname a password. > > > Can't you just reverse those steps. I.e. remove /home/listname/ and > remove the listname user? > Well, that was my inclination, but I didn't know if I needed to have a user by the name of listname. I was afraid that if I just deleted the user "listname" it would cause even more problems. I had created that user back when I was using another mailinglist package -- a Joomla plugin (that doesn't work nearly as well as mailman3). I was afraid to just type in "userdel -r" in case mailman3 needed a "real" user... So, I can just kill the listname user altogether? billo

4 years, 8 months

[MM3-users] Re: mailman-cli tools

by Abhilash Raj

On Wed, Sep 27, 2017, at 10:29 AM, Dmitry Makovey wrote: > On 09/27/2017 10:20 AM, Abhilash Raj wrote: > > On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: > >> On 09/27/2017 08:26 AM, Dmitry Makovey wrote: > >>> On 09/27/2017 08:25 AM, Dmitry Makovey wrote: > >>>> I've come across mailman-cli docs: > >>>> > >>>> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… > >>>> > > > > This is basically one of our GSoC projects which hasn't yet been merged > > with MailmanClient. It uses the REST API to to provide a command line > > client for Mailman, while there hasn't been any in-compatible changes in > > API since this project was finished, I am not sure about the current > > status of it. > > > >>>> yet I cannot figure out what's the official source for the installation. > > > > Official source for MailmanClient is at gitlab.com/mailman/mailmanclient > > and it doesn't have a CLI, the Github project you linked to says right > > on the top that it is not official project (Thanks for that Rajeev!). > > I did see that, thus I was asking the question here. > > > Also, I would say not to use this client to remotely access Mailman, the > > REST API is not meant to be exposed over internet (unless you have a VPN > > or other sort of setup to securely access the box remotely). > > > > in my case - I need to use REST API since we're deploying with docker > and pieces that need to integrate with mailman commands now live in a > different container (and very likely on a different machine). I do need > to be able to execute commands remotely - I can handle securing of that > connection, but it is not an option for me to run "fat" docker > containers thus the only interconnect is via sockets (either UNIX or > TCP). The CLI project is basically a Shell+CLI based on MailmanClient (python library for Mailman API) and Mailman Core's REST API. So, if I understand correctly, this would run commands over REST API like you want. -- Abhilash Raj maxking(a)asynchronous.in

9 years, 1 month

[MM3-users] Re: mailman-core installation on debian stretch/maria-db

by Wolfgang Bock

Am 10.03.2018 um 23:44 schrieb Mark Sapiro: > How? Did you install > <https://packages.debian.org/stretch-backports/mailman3-core>? -> No, if I had known this, I wouldn't waste my time for the last 3 days in fiddeling and googleling ... > If so, these are probably issues with the Debian package. > > You may find<https://gitlab.com/mailman/mailman/issues/455> to be of > interest. > > If you installed Mailman some other way, How? -> From here: http://docs.mailman3.org/en/latest/prodsetup.html#installing-mailman-core including dependencies > >> 1. On "mailman start" I got the error message: >> Starting Mailman's master runner >> /usr/bin/python3: can't open file '/sbin/master': [Errno 2] No such file >> or directory > Where is it? What does 'which master' show? -> /usr/local/bin/master -> After I set a symlink to /sbin/master another errormessage occurs >> 2. connection to maria-db >> In debian stretch maria-db is running. In my mailman.cfg I set: >> [database] >> class: mailman.database.mysql.MySQLDatabase >> url: >> mysql+pmysql://#username#:#user-pawo#@localhost/#databasename#?charset=utf8&use_unicode=1 > should that be mysql+pymysql ? -> Yes, according to: http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html -> Not right?? After that I decided to delete mailman via pip and took a new approach via debians apt-get ... mailman 3 So far so good, now new errormessage: Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/mailman/bin/mailman.py", line 94, in main initialize(config_path) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 189, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 160, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 52, in create database = call_name(database_class) File "/usr/local/lib/python3.5/dist-packages/mailman/utilities/modules.py", line 67, in call_name named_callable = find_name(dotted_name) File "/usr/local/lib/python3.5/dist-packages/mailman/utilities/modules.py", line 51, in find_name return getattr(sys.modules[package_path], object_name) AttributeError: module 'mailman.database.mysql' has no attribute 'MYSQLDatabase' Another question is, where can I find the sql-command within the database mailman3 like CREATE TABLE x and TABLE y as I created a database mailman3 which is empty?? Thanks for your help in advance. Regards Wolfgang

8 years, 8 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 11/2/21 20:15, Mark Sapiro wrote: > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I contributed in january to translate to spanish all the items left in >> Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I >> thought they will be used in the next upgrade, but I cannot see any >> improvement and there are many words untranslated. > > The Spanish translations for Mailman core and HyperKitty are currently > completely up to date with weblate. django-mailman3 differs in one > string that was translated on Feb 10 and hasn't yet been merged. > Postorius also differs in a few places from the Feb 10 version that > hasn't yet been merged. Ok. Thanks for checking it. I put my little contribution in Weblate and I like that it could be used by anyone. > Other than that, the translations should be good. > > >> Is there any way to upgrade the .po files in order to get the last >> translation? > > For the web UI you need to run the django management `compilemessages` > command. I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error: su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. if I try with --settings param (for I missunderstood the error message) it shows the same: su -m mailman3 -c "python3 manage.py compilemessages --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 tried to find any doc regarding the use of the "compilemessages" command but I couldn't As far as I can see (I runned it with -h parm) this had to be related to the main python module, but I cannot understand why the pip upgrade did not do the job. I'm lost. Can you, please, point me in the right direction? > For Mailman core you need to run > ``` > cd mailman/messages/es/LC_MESSAGES > msgfmt -o mailman.mo mailman.po > ``` > to compile the mailman.po file for gettext. >

5 years, 9 months

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

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/26/26 13:20, Ibiam Chihurumnaya via Mailman-users wrote: > > I'm doing it in mailman shell, list_name is a List object, and it seems to have a settings > > attribute as list_name.settings returns > > {'acceptable_aliases': [], ...} > > I would really like to know what Mailman version this is, and how it was > installed? In my case with Mailman core from the head of the GitLab branch: > $ mailman shell -l list.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> m.settings > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: 'MailingList' object has no attribute 'settings' > >>> m.settings['accept_these_nonmembers'] > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: 'MailingList' object has no attribute 'settings' > >>> Currently running Mailman 3.3.10 and I followed the instructions from https://docs.mailman3.org/en/latest/install/virtualenv.html# to install. This is the output from mine, I get the same output as you do when I try exactly what you do; mailman shell -l systems-logs(a)lists.sugarlabs.org Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the systems-logs(a)lists.sugarlabs.org mailing list >>> m.settings Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'MailingList' object has no attribute 'settings' I get something else when I do it differently - how I've been doing it so far -. 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. >>> from mailmanclient import Client >>> from mailmanclient import Client >>> client = Client('http://localhost:8001/3.1', '**', '**') >>> sg = client.domains[0] >>> sy = sg.get_lists()[-1] >>> sy <List 'systems-logs(a)lists.sugarlabs.org'> >>> sy.settings {'acceptable_aliases': [], 'accept_these_nonmembers': [], 'admin_immed_notify': True, 'admin_notify_mchanges': False, 'administrivia': True, 'advertised': False, 'allow_list_posts': True, 'anonymous_list': False, 'archive_policy': 'public', 'archive_rendering_mode': 'text', 'autorespond_owner': 'none', 'autorespond_postings': 'none', 'autorespond_requests': 'none', 'autoresponse_grace_period': '90d', 'autoresponse_owner_text': '', 'autoresponse_postings_text': '', 'autoresponse_request_text': '', 'bounces_address': 'systems-logs-bounces(a)lists.sugarlabs.org', 'bounce_info_stale_after': '7d', 'bounce_notify_owner_on_bounce_increment': False, 'bounce_notify_owner_on_disable': True, 'bounce_notify_owner_on_removal': True, 'bounce_score_threshold': 5, 'bounce_you_are_disabled_warnings': 3, 'bounce_you_are_disabled_warnings_interval': '7d', 'collapse_alternatives': True, 'convert_html_to_plaintext': False, 'created_at': '2026-02-04T21:53:10.928951', 'default_member_action': 'defer', 'default_nonmember_action': 'accept', 'description': '', 'digest_last_sent_at': '2026-02-27T11:24:11.916379', 'digest_send_periodic': True, 'digest_size_threshold': 30.0, 'digest_volume_frequency': 'monthly', 'digests_enabled': True, 'display_name': 'Systems-logs', 'discard_these_nonmembers': [], 'dmarc_mitigate_action': 'no_mitigation', 'dmarc_mitigate_unconditionally': False, 'dmarc_addresses': [], 'dmarc_moderation_notice': '', 'dmarc_wrapped_message_text': '', 'emergency': False, 'filter_action': 'discard', 'filter_content': False, 'filter_extensions': [], 'filter_types': [], 'first_strip_reply_to': False, 'forward_unrecognized_bounces_to': 'administrators', 'fqdn_listname': 'systems-logs(a)lists.sugarlabs.org', 'gateway_to_mail': False, 'gateway_to_news': False, 'hold_these_nonmembers': [], 'include_rfc2369_headers': True, 'info': '', 'join_address': 'systems-logs-join(a)lists.sugarlabs.org', 'last_post_at': '2026-02-27T11:32:51.317220', 'leave_address': 'systems-logs-leave(a)lists.sugarlabs.org', 'linked_newsgroup': '', 'list_name': 'systems-logs', 'mail_host': 'lists.sugarlabs.org', 'max_message_size': 40, 'max_num_recipients': 10, 'max_days_to_hold': 0, 'member_roster_visibility': 'moderators', 'moderator_password': None, 'newsgroup_moderation': 'none', 'next_digest_number': 60, 'nntp_prefix_subject_too': True, 'no_reply_address': 'noreply(a)lists.sugarlabs.org', 'owner_address': 'systems-logs-owner(a)lists.sugarlabs.org', 'pass_types': [], 'pass_extensions': [], 'personalize': 'none', 'post_id': 316, 'posting_address': 'systems-logs(a)lists.sugarlabs.org', 'posting_pipeline': 'default-posting-pipeline', 'preferred_language': 'en', 'process_bounces': True, 'reject_these_nonmembers': [], 'reply_goes_to_list': 'no_munging', 'reply_to_address': '', 'request_address': 'systems-logs-request(a)lists.sugarlabs.org', 'require_explicit_destination': True, 'respond_to_post_requests': True, 'send_goodbye_message': True, 'send_welcome_message': True, 'subject_prefix': '[Systems-logs] ', 'subscription_policy': 'confirm', 'unsubscription_policy': 'confirm', 'usenet_watermark': None, 'volume': 1} > > Presumably in your case, you could do > list_name.settings['accept_these_nonmembers'].append('user(a)example.com') > > or > > list_name.settings['accept_these_nonmembers'].extend(['user1(a)example.com', > 'user2(a)example.com', 'user3(a)example.com']) > > but as I've said previously, accept_these_nonmembers is not the > preferred way to do this. Something like > $ mailman addmembers --delivery disabled FILE LIST > Yes, I see now that it's not the preferred way to do it. It's difficult to know that when looking at the documentation. > where FILE contains the addresses to add, one per line and LIST is the > list name would add the addresses as members with delivery disabled. To > add them as nonmembers with moderation_action Defer: > $ mailman shell -l list.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> from mailman.app.membership import add_member > >>> addresses = ('user1(a)example.com', 'user2(a)example.com', > ... 'user3(a)example.com') > >>> for addr in addresses: > ... rr = RequestRecord(addr) > ... nm = add_member(m, rr, role=MemberRole.nonmember) > ... nm.moderation_action = Action.defer > ... > >>>commit() Thank you! > > Of course, all of this can be done, perhaps more easily, using the > Postorius web UI. Yes, but like I've mentioned in another thread, I don't have access to the web UI because I can't get a confirmation link. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: not correct language in subject(s)

by Jens Günther

Thanks Mark for the tests and your thoughts on this matter. Am 23.05.23 um 17:19 schrieb Mark Sapiro: > > That file was for a test only. The German message catalog is at > mailman/messages/de/LC_MESSAGES/. That directory should contain a > mailman.po and a mailman.mo. If there is no mailman.mo, it needs to be > created. The source distribution contains a generate_mo.sh script to > generate these for all languages, but you can do the German one by > changing to the mailman/messages/de/LC_MESSAGES/ directory in the > running installation and doing > > msgfmt mailman.po -o mailman.mo I just checked the mailman/messages/de/LC_MESSAGES directory and there was only a mailman.po. I tried to create the mo-file with the command you provided, unfortunately it doesn't work in the running docker-container (obviously the gettext-package is missing ... and can't install it with apt, but this is another docker-related problem, shall I open another thread?). I did create on OS-level the mo-file, restarted the container and now the welcome- and goodbye-subject is indeed in German, coolio! 2 thoughts on this for me is: - Shall I create all the mo-files (the other folders also only contain the po)? If so, how would it be possible? - How can I make it persistent? (probably it should be included in the repo!? also another thread or an issue regarding maxxking's repo!?) > > I just tested, and the notice to the moderator of a held message is in > the list's preferred language including the Subject: and the moderation > reason, and the notice to the user sending a held message is in the > User's preferred language for that list including the Subject: and the > moderation reason. > > I suspect your issue is you don't have the compiled mailman.mo German > message catalog. The text is in German because it comes from templates > and you presumably do have German language templates. > Exactly. What I was wondering: for the welcome-messages I did not have explicit templates for those lists/domains/site that I wrote in German, it has to be from the predefined templates, which are stored elsewhere the in the mo-files!? (actually I don't get this point exactly but wouldn't bother, if the above works). Thanks again!

3 years, 5 months

[MM3-users] Re: Removing a mail addresses and users

by Abhijith PA

Hi Mark, On 11/06/20 1:16 am, Mark Sapiro wrote: > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> I tried to remove random email address signing ups (which I signed up >> while testing) via admin panel. After removing I tried to sign up again, >> but I am getting, >> >> 'A user is already registered with this e-mail address' > > You removed the user's subscription from the list, but you didn't remove > the user from the system. > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > User's have addresses and a user or one of the user's addresses can > belong to a list with one or more roles (non-member, member, moderator > or owner) In my case these user signups were just to test postorious. These mail accounts didn't subscribed to anything. >> Combing through the database, I found auth_user table in mailman3web db >> still contain those mail address. How to wipe email address entirely >> from the db so I can signup again without the 'forget password' method > > There are a couple of things. If you log in to the web UI as a django > superuser, you can go to the django admin UI -> Users section and delete > the User, but I think that will only delete the web user and not delete > the user from Mailman core. > > You can also log in to the web UI as the user and go to > <https://lists.mailman3.org/user-profile/delete>, but that again only > deletes the web user, and if you could do that, you could just subscribe > once you're logged in, so I assume that's what you want to avoid. > > I don't think there is a way for a user as opposed to a site admin to > delete her user record from Mailman core and even for a site admin, > there's no way in Postorius to delete a user from core. It has to be > done via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or `mailman shell`. > Thanks for the link, let me try that out. --abhijith

6 years, 5 months

[MM3-users] Re: Confirmation emails aren't sent to users.

by Ibiam Chihurumnaya

Stephen J. Turnbull wrote: > Ibiam Chihurumnaya via Mailman-users writes: > > Mark Sapiro wrote: > > > OK, this is Django. The default EMAIL_BACKEND from > > mailman_web/settings/base.py is > > django.core.mail.backends.smtp.EmailBackend and unless you've changed > > that or added overrides various other defaults are > > EMAIL_HOST = "localhost" > > EMAIL_PORT = 25 > > EMAIL_HOST_USER = "" > > EMAIL_HOST_PASSWORD = "" > > EMAIL_USE_TLS = False > > EMAIL_USE_SSL = False > > EMAIL_SSL_CERTFILE = None > > EMAIL_SSL_KEYFILE = None > > Are those appropriate? Do you have an outgoing MTA listening on > > localhost:25? What's in it's logs? > > I don't have any of those set, didn't realize I needed to have them > > set, the docs didn't make it obvious too. > > Those defaults *are* set in the mailman_web settings files. You can > override them in /etc/mailman3/settings.py, but often you don't need > to. Makes sense, I didn't think I needed to. Couldn't see them with mailman conf though. > > I also didn't notice them in schema.cfg in mailman. > > This is for Django, whose configuration is in > /etc/mailman3/settings.py, with defaults set in the mailmanweb package > in your venv's site-package in the files in .../mailman_web/settings/. > > smtp_port is currently set to 25, and I do have an outgoing MTA > > listening on localhost:25. > > If Mailman can distribute posts that way, Django should be able to > send mail with the default settings. > > Nothing shows up in the MTA logs about this particular email. > > Not sure what to say about that. I'm not sure Postorius or Django log > outgoing mail messages but I think they use the mailmanweb.log file by > default if they log mail at all. (This is separate from the MTA logs > which should record any connections from localhost and mail submitted.) Is there any way I could get more logs, I had set Debug = True in settings.py a while back, but can't see anything more. > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan

9 months

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

by Odhiambo Washington

On Thu, 30 Jul 2020 at 00:13, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/29/20 12:15 AM, Odhiambo Washington wrote: > > > > Yes, the same problem. > > I created the file __init__.py in /opt/mailman/mm > > However, when I run using the wsgi.py I ended up (still do!) with the > error: > > > > [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote > > 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', > > application='mm3-lists.server.name|/mm3'): Loading Python script file > > '/opt/mailman/mm/wsgi.py'. > > What is the contend of the file /opt/mailman/mm/wsgi.py? > [wash@gw ~]$ cd /opt/mailman/mm/ [wash@gw /opt/mailman/mm]$ less wsgi.py """ WSGI config for HyperKitty project. It exposes the WSGI callable as a module-level variable named ``application``. For more information on this file, see https://docs.djangoproject.com/en/{{ docs_version }}/howto/deployment/wsgi/ """ import os # import sys # import site # For some unknown reason, sometimes mod_wsgi fails to set the python paths to # the virtualenv, with the 'python-path' option. You can do it here too. # # # Remember original sys.path. #prev_sys_path = list(sys.path) # # Add here, for the settings module #site.addsitedir(os.path.abspath(os.path.dirname(__file__))) # # Add the virtualenv #venv = os.path.join(os.path.abspath(os.path.dirname(__file__)), # '..', 'lib', 'python2.6', 'site-packages') # site.addsitedir(venv) # # Reorder sys.path so new directories at the front. # new_sys_path = [] # for item in list(sys.path): # if item not in prev_sys_path: # new_sys_path.append(item) # sys.path.remove(item) # sys.path[:0] = new_sys_path from django.core.wsgi import get_wsgi_application os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") application = get_wsgi_application() > You previously posted the setting of WSGIDaemonProcess in your Apache > config as: > > > 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 > > Is it still that? > This is from wsgi.conf in my Apache Includes/. It's a copy/paste of your version, with the only modification being the change pf python version to 3.7 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 3 months

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

by Fabian A. Santiago

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

9 years

Search results for query "sapiro"