- Mailman-users - lists.mailman3.org

API errors making member changes to one list but not others
by Stephen Willey Mats Mats Jan. 28, 2021

Jan. 28, 2021

We had an issue with the UI getting API timeouts for a single list for specific functions but not other lists or other functions. This started happening after we accidentally filled the disk partition used by most of the system including the database. There was a single person testing at the time when the disk fullness happened and it was only the single list that got ‘damaged’. After disk cleanup and restarting the docker images the single list would give API errors ("HTTP Error 400: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5)” ) on the screen and logged errors (below) when list members were either subscribed or removed. The issue was repeatable in Postorius and did not ‘heal’. Oddly the issue was resolved by making seemingingly the same API calls from the command line via curl. Making the below call to add a member succeeded and fixed being able to add members in the UI. Similarly sending a DELETE cal from curl worked where unsubscribe requests from postorius (either mass removal or picking addresses from the list member and unsubscribing selected) failed. Again, the unsubscribe from the curl DELETE call ‘healed’ the list such that subsequent unsubscribes in Postorius worked. curl --user user:password -X POST -d 'list_id=laura-test.mm3.aca-aws.s.uw.edu' -d 'subscriber=ssw(a)uw.edu' -d 'pre_verified=true' -d 'pre_confirmed=true' -d 'pre_approved=true' http://172.19.199.2:8001/3.1/members We’re running the current rolling docker images (up to date as of 25Jan2021) Obviously, people should run their servers better than letting disk partitions fill-up but it’s going to happen and mailman3 should do a better job of reporting errors and recovering when accidents happen. thanks, steve I’ve included mailman.log lines from going to the mass subscribe [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 434 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:01 +0000] "GET /3.1/lists/laura-test.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 434 "-" "GNU Mailman REST client v3.3.2" Jan 26 20:43:07 2021 (48) deque: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 426, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 421, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.8/http/client.py", line 1347, in getresponse response.begin() File "/usr/lib/python3.8/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.8/http/client.py", line 268, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.8/socket.py", line 669, in readinto return self._sock.recv_into(b) socket.timeout: timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 724, in urlopen retries = retries.increment( File "/usr/lib/python3.8/site-packages/urllib3/util/retry.py", line 403, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/lib/python3.8/site-packages/urllib3/packages/six.py", line 735, in reraise raise value File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen httplib_response = self._make_request( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 428, in _make_request self._raise_timeout(err=e, url=url, timeout_value=read_timeout) File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 335, in _raise_timeout raise ReadTimeoutError( urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 343, in _step_do_subscription self.member = self.mlist.subscribe( File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 507, in subscribe notify(SubscriptionEvent( File "/usr/lib/python3.8/site-packages/zope/event/__init__.py", line 32, in notify subscriber(event) File "/usr/lib/python3.8/site-packages/mailman/app/membership.py", line 176, in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3.8/site-packages/mailman/app/notifications.py", line 51, in send_welcome_message welcome_message = wrap(getUtility(ITemplateLoader).get( File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 188, in get contents = getUtility(ITemplateManager).get( File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 110, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3.8/site-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3.8/site-packages/requests/api.py", line 76, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3.8/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 530, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 643, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 529, in send raise ReadTimeout(e, request=request) requests.exceptions.ReadTimeout: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) [26/Jan/2021:20:43:07 +0000] "POST /3.1/members HTTP/1.1" 400 130 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:07 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:07 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" Then the results of a successful subscribe: [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 388 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "POST /3.1/members HTTP/1.1" 201 0 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2” >

2 1

Perplexing unsubscribing notification problem
by Brian Carpenter Jan. 27, 2021

Jan. 27, 2021

Hi MM3 Users, I have a perplexing issue with one of our Mailman 3 servers. It doesn't want to send out unsubscribe notifications when a List Owner removes a list member. The server sends out welcome messages and subscription notifications fine just not unsubscribe notifications when a List Owner removes a list member. It will send out an unsubscribe notification if the list member sends an email to listname-leave@listdomain both to the List Owner and List Member. Nothing is showing in the logs as far as I can tell. -- Brian Carpenter Harmonylists.com Emwd.com

1 1

I like your style, but what is it?
by Stephen Willey Mats Mats Jan. 27, 2021

Jan. 27, 2021

How do I get a dump of list settings for each style. Thanks, steve p.s. the search on https://mailman.readthedocs.io/en/latest/README.html gives results but every link needs to have ‘projects/mailman/‘ removed from the url to work.

2 1

Problem updating mailman
by Odhiambo Washington Jan. 26, 2021

Jan. 26, 2021

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) (Gem::MissingSpecError) Checked in 'GEM_PATH=/opt/mailman/.gem/ruby/2.7:/usr/local/lib/ruby/gems/2.7', execute `gem env` for more information from /usr/local/lib/ruby/site_ruby/2.7/rubygems/specification.rb:1446:in `block in activate_dependencies' from /usr/local/lib/ruby/site_ruby/2.7/rubygems/specification.rb:1435:in `each' from /usr/local/lib/ruby/site_ruby/2.7/rubygems/specification.rb:1435:in `activate_dependencies' from /usr/local/lib/ruby/site_ruby/2.7/rubygems/specification.rb:1417:in `activate' from /usr/local/lib/ruby/site_ruby/2.7/rubygems.rb:305:in `block in activate_bin_path' from /usr/local/lib/ruby/site_ruby/2.7/rubygems.rb:304:in `synchronize' from /usr/local/lib/ruby/site_ruby/2.7/rubygems.rb:304:in `activate_bin_path' from /usr/local/bin/sass:23:in `<main>' The other output from this process is so long so I pasted it here: https://pastebin.ubuntu.com/p/tsB2CCNrQG/ Thanks -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

3 4

Language Support In Templates
by Brian Carpenter Jan. 26, 2021

Jan. 26, 2021

Hello MM3 Users, I have a question regarding the use of templates in different languages. I created a template for the unsubscribe notification in Postorius in Greek. The template shows up fine in Greek via Postorius. However the email that is sent out has a bunch of question marks where the Greek should be: ??????????? ?????????? ???????? ?????????? email ???? ???, ????? ????? ? ??????????? GNU Mailman ???? ????? $. ?????? ??? ?????? ????????? ??? ?? ????????? email $user_email ?????? ?? GNU Mailman ?????? ?? ?????????? ??? ??????? ???, ?????? ????? ?? ????????????? ?? ?????? ???. ???????? ?? ?? ?????? ????? ?????????? ?? ???? ?? ??????. ? ?? ?????? ?? ????????????? ??? ???????? ?????? - ??? ???? ?? ???????? line - ?? ??? ?????? ???? ?? $ request_email: confirm $token ????????? ??? ? ???? ???????? "?????????" ?? ???? ?? ?????? ?????? ?? ?????????? ?? ???????????? ?????????? ?????????????. ??? ??? ?????? ?? ??????????? ??? ????? ?? ????????? ???????????? ????????????, ????? ???????? ??? ??????. ??? ????????? ??? ??????????? ????????? ??? ?? ?????, ? ????? ????? ?????????, ???????? ?? ?????????????? $owner_email What does it take to get templates to send out messages in a different language then the interface itself. -- Brian Carpenter Harmonylists.com Emwd.com

2 2

How to approve moderated messages via email?
by Brian Carpenter Jan. 24, 2021

Jan. 24, 2021

What is the protocol to approve moderated messages via email? I hope I asking the question correctly. -- Brian Carpenter Harmonylists.com Emwd.com

3 5

False attachments in Outlook 2019?
by Brian Olesen Jan. 24, 2021

Jan. 24, 2021

Dear Mailman 3 users, I seriously think of upgrading from Mailman 2.1.33 to this new RC2 or the final one, when it comes out. But there is an annoying issue that I'd like to ask you about. It's the false attachments that Outlook creates for the footer. Is this still an issue when using Mailman 3, or have you made some sort of work around? I mean here in 2021 it could be nice to use html as the default mail format to be able to create nice looking mails, and due to EU regulations an unsubscription is a requirement. Best regards Brian Olesen from Denmark P.S. If this issue has been solved I will happily translate the mail templates into Danish if wanted.

2 1

Blocked by Hotmail
by Tom ＠ Gather Jan. 23, 2021

Jan. 23, 2021

I am getting rejections from Hotmail Jan 18 14:42:22 mail postfix/smtp[6571]: 046713F914: to=< helen_maryd(a)hotmail.com>, relay=hotmail-com.olc.protection.outlook.com[104.47.58.161]:25, delay=0.14, delays=0.06/0.03/0.04/0.01, dsn=5.7.1, status=bounced (host hotmail-com.olc.protection.outlook.com[104.47.58.161] said: 550 5.7.1 Unfortunately, messages from [167.99.151.239] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3140). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [ BN8NAM11FT014.eop-nam11.prod.protection.outlook.com] (in reply to MAIL FROM command)) I have submitted a ticket to https://support.microsoft.com/en-us/supportrequestform/8ad563e3-288e-2a61-8… Not sure why they are blocking me. Not on any other blacklists per mxtoolbox... Anyone else experienced this? How to resolve? My mail server is on Digital Ocean if that makes any difference. Thanks for any help -- Tom for the Gather Team https://info.gather.coop

5 4

django fake users
by r.woithe＠callassoftware.com Jan. 23, 2021

Jan. 23, 2021

Hello, is there a opportunity to avoid django fake users? Because of it is not stopping, further and further fake users are subscribing. Would be nice to have a possibility to stop this.

6 10

"Unsubscribe all" failed with large lists
by Alan So Jan. 21, 2021

Jan. 21, 2021

We are currently testing latest mailman suite (w/Postorius 1.3.3) and notice that that the the API call /3.1/lists/listname.domain/roster/member failed when using "Unsubscribe all" on Postorius for a large list (~15000 members). Not sure whether the issue has been already reported or not.

2 3

Unable to retrieve <800 members of Mailman list through Curl command
by Shashikanth Komandoor Jan. 20, 2021

Jan. 20, 2021

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values. I am almost running 2000 lists with 128 GB RAM and 24 Cores on a single VM and on which all the mailman 3 components are running. It is observed for most of the lists having members more than 500 is displaying "Mailman REST API not available. Please restart Mailman Core" message on the postorius window and on running the CURL command over REST API of Mailman it is reaching the time limit 30 seconds and showing the below error. *curl: (52) Empty reply from serverNo JSON object could be decoded* The same behavior is observed on browsing the held messages for few lists either through the browser or through CURL and REST API. How to resolve this issue ? What other details I can provide to make you get an idea ? -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 1

Easiest way to install a new mailman3 deployment?
by ieso＠johnwillson.com Jan. 18, 2021

Jan. 18, 2021

So I've been trying for the last two weeks to get a new mailman3 server running on a virtualized server (any server), and I'm turning to this list after having failed many times and running out of holiday time. I started trying a non-docker installation on Ubuntu 18.04 (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) , which got me the closest. Except I had a problem with inbound email only being triggered when it came from certain accounts. But that clearly wasn't good enough for production, so after many attempts to figure out where it was failing, I decided to turn to docker as a solution that should be cleaner. A few attempts at doing a docker installation on digitalocean.com failed, which I realized might be due to it not routing private IP addresses, so I moved to AWS after checking that their VPC policy would fit mailman's docker requirements. I found a great but slightly outdated guide on how to do this (https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) By this point I knew enough to correct a number of places where the environment had changed since the procedure was written, but postorius still failed at the curl test. The challenge for me has been the difficulty to know how to troubleshoot the different different systems and network infrastructure that are used to keep mailman3 humming. I've tried about 7 different installation walkthroughs (there are no recent ones on Youtube by the way, in case anyone wants to seize that opportunity!), and the good guides provide ways to check each stage to try to help you a bit on that front. Nonetheless, I feel stuck and thought I'd ask the simple question... for a completely basic, barebones new installation, what's the easiest way to get a mailman3 installation up-and running? (e.g. Which server provider? Which operating system and version? Docker or otherwise?) Any pointers highly appreciated. Google Groups is clearly on its way out, as it no longer allows for people to easily join groups by sending an email or clicking a link, so that should be a big opportunity for mailman3 to step up and help give those mailing list migrants a new home... which is what we're looking for. We're just not quite as smart as you guys. ;-)

15 25

Mailman 3 Installation
by bruce.dubbs＠gmail.com Jan. 17, 2021

Jan. 17, 2021

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

4 5

New release candidates for Postorius and Hyperkitty
by Abhilash Raj Jan. 17, 2021

Jan. 17, 2021

Hey Everyone, Happy new year to everyone! I am pleased to announce new release candidates for Postorius and Hyperkitty along with new releases for Mailmanclient and Django-mailman3! These include both new features and bug fixes. Complete change log for each components: Postorius 1.3.4rc1: https://docs.mailman3.org/projects/postorius/en/latest/news.html Hyperkitty 1.3.4rc1 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Mailmanclient 3.3.2.: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… Django-mailman3 1.3.5: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst These releases require Mailman Core 3.3.2 and Python 3.6+. Since these are pre-releases, you can install them using: $ pip install --pre --upgrade postorius hyperkitty Or you can also specify the exact versions: $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' Unless there is a release-blocker bug, stable versions for Postorius and Hyperkitty will be released in 2 weeks time. If you can test these releases, we encourage you to report any bugs to us on Gitlab. If you'd like to help out with translations for some of the new strings in your native language, the documentation is available here[1] on how to do that. [1]: https://docs.mailman3.org/en/latest/translation.html -- thanks, Abhilash Raj (maxking) On behalf of GNU Mailman Team

1 1

subscribing to any list is not possible
by r.woithe＠callassoftware.com Jan. 17, 2021

Jan. 17, 2021

Hello, after i solved the qcluster error with a new installation i have still an error with subscribing. It is not possible to subscribe to any list via email or web-interface. The mass subcribtion as admin via the web-interface is possible and the unsubscribing also. But i can not get any error messages in any log file, nothing. Also the django users are fine, django users can subscribe without a problem. But subscribing to any list is not possible via the web-interface, with the error message "A Server Error occured please conntact the Administrator",also subscribing via email is not possible(mail.log is fine the mail is delivered), but there is no additionally error message in any log file. System: ubuntu 20.04.01 Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0]

2 4

Re: New release candidates for Postorius and Hyperkitty
by Abhilash Raj Jan. 16, 2021

Jan. 16, 2021

+cc: mailman-usersmailman3.org for more visibility. On Sat, Jan 16, 2021, at 2:20 PM, Ruth Ivimey-Cook wrote: > Hi, > > Is there a recommended method for upgrading an existing, running, server > from Python 3.6 to 3.8, especially in such a way as to enable downgrade > if something breaks? It depends on how did you install Mailman. If you installed using virtualenv, you can create another virtualenv and install new versions, that use the same configuration and switch between new and old versions, > > [When I upgraded a server distribution without enough preparation, it > broke mailman3 because I lost python3.6, and getting it working again > needed a lot of work to reinstall it without zapping needed state.] > > Regards > > Ruth > > > On 16/01/2021 20:38, Abhilash Raj wrote: > > Hey Everyone, > > > > Happy new year to everyone! > > > > I am pleased to announce new release candidates for Postorius and Hyperkitty along with new releases for Mailmanclient and Django-mailman3! > > > > These include both new features and bug fixes. Complete change log for each components: > > > > Postorius 1.3.4rc1: https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4rc1 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Mailmanclient 3.3.2.: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > Django-mailman3 1.3.5: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > > > These releases require Mailman Core 3.3.2 and Python 3.6+. > > > > Since these are pre-releases, you can install them using: > > > > $ pip install --pre --upgrade postorius hyperkitty > > > > Or you can also specify the exact versions: > > > > $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' > > > > Unless there is a release-blocker bug, stable versions for Postorius and Hyperkitty will be released in 2 weeks time. If you can test these releases, we encourage you to report any bugs to us on Gitlab. > > > > If you'd like to help out with translations for some of the new strings in your native language, the documentation is available here[1] on how to do that. > > > > [1]: https://docs.mailman3.org/en/latest/translation.html > > > -- > Software Manager & Engineer > Tel: 01223 414180 > Blog: http://www.ivimey.org/blog > LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/ > > -- thanks, Abhilash Raj (maxking)

1 0

Subscription request cannot be moderated: 404 Not Found
by Eric Broens Jan. 16, 2021

Jan. 16, 2021

For one of our mailinglists we also have a problem with accepting a subscription request. When Clicking "Accept", we get a 404 Not found error. See the attached screenshot. Is there a way to solve this? Best Regards,Eric

2 8

Mailman 'requests' API call timeout when there are a number of pending members
by Alan So Jan. 15, 2021

Jan. 15, 2021

We are currently testing latest mailman suite and notice that the requests API call will timeout if there are a number of pending requests. Since the latest Postorious allow unchecking Pre confirm and Pre approved during mass subscribe, our support staff tried to add large number of email addresses to the list. We then found that we cannot click into the list from the web UI to administer it and an error message showing that "Mailman REST API not available. Please start Mailman core." Further checked that the requests API call failed to complete when we click the list on the web interface. Looks like the UI should not try to load all the pending members just for the sake of showing the number of pending requests. Of course in normal situations, there should not be that many pending requests.

2 1

Re: Mails for 1 specific mailinglist not being send and looping in out queue
by Eric Broens Jan. 14, 2021

Jan. 14, 2021

In my mailclient it looks like the LF's have been removed. I'll attach the log extracts to make them better readable. Best Regards, Eric On Saturday, January 9, 2021, 02:17:18 PM GMT+1, Eric Broens <ebroens(a)yahoo.com> wrote: ----- Forwarded Message ----- From: Eric Broens via Mailman-users <mailman-users(a)mailman3.org>To: Mailman Users <mailman-users(a)mailman3.org>Sent: Saturday, January 9, 2021, 02:14:42 PM GMT+1Subject: [MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue For some reason, the mail for 1 specific mailinglist doesn't get distributed. It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail. The mailman3 error log show that there is a connection failure to port 25. A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail. Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail. Using qfile, the pck file of this mail looks fine. New emails on this specific mailinglist are not distributed either. For all other mailinglists on this server, and which are on the same domain, there are no problems. Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue? Below are the relevant extracts from the log files for the particular case. mailman smtp.log: Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost... Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to *** mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25 mailman debug.log Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>... Thanks in advance,Eric _______________________________________________ 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/

2 3

Header Filter madness
by Brian Carpenter Jan. 14, 2021

Jan. 14, 2021

I have a client whose header filters seemed to have stop working. No matter what I try, it seems none of their header filters are being applied. Other lists on the same server that use header filters, are working fine. This particular header is the subject header. I can duplicate their problem but only with their list. If I create the exact same header on a test list using the exact same subject line, the header filter does its job (moderate). Just not with this one list. -- Brian Carpenter Harmonylists.com Emwd.com

2 7

The future is here?
by ieso＠johnwillson.com Jan. 9, 2021

Jan. 9, 2021

In my quest to figure out how even us idiots can successfully install a mailman3 server, I keep looking ways to reduce the process to the simplest possible set of instructions. So far, I haven't been doing very well with that, but I've been learning a ton. In particular, while I still haven't got a fully functioning mailman3 server yet, someone pointed me, off list, to Ansible, which I wasn't aware of before and which has completely blown me away by its power and simplicity. For those who aren't aware of it, it's an agentless, multi-platform automation technology. For our purposes, it replaces "how to install mailman3" guides with a single script that aims to actually do the entire thing for you. One of the particularly interesting points is that you can write complex scripts/data structures (or 'collections') that allow for a single collection to cover a broad range of use cases, such as [this person's](https://github.com/rivimey/) exim Ansible collection, which covers 3 very different use cases from a private domain email relay up to a full multi-domain email handler with IMAP integration. I haven't quite got the mailman3 one working yet, but I've just started playing with it. Here are some pointers in case anyone else is interested in trying, and I'd be very interested in whether or not I'm actually the last person to discover this technology, and if one of these solutions succeeds in delivering mailman3 "out of the box". 1. [Install Ainsible](https://docs.ansible.com/ansible/latest/installation_guide/intro_…, make sure you're on at least version 2.9, if not 2.10. Some distributions are still on 2.7, which is not compatible with more recent collections. The "Galaxy" collection is apparently only tested on Debian 10. 2. Pick your mailman3 Ansible collection of choice and install it (https://galaxy.ansible.com/ucr/mailman3, or https://github.com/rivimey/ansible-mailman3) Command to install official collection - ansible-galaxy install ucr.mailman3 3. Write playbook.yml with key variables (mailman3 example below) _________________________ mailman3-playbook.yml _________________________ - hosts: mailman3 vars: mailman3_domain: example.com # It will install and create a certificate using certbot, its nignx plugin and http validation (Public IP required). If false, it will install a self sign cert mailman3_install_certbot: true # install and create certificate # secrets, please change them mailman3_secret_key: "change_secretkey" mailman3_rest_api_pass: "change_api_pass" mailman3_archiver_key: "change_archiver_key" mailman3_db_pass: "change_db_pass" mailman3_web_db_pass: "change_web_db_pass" mailman3_web_admin_pass: "change_web_admin_pass" roles: - ucr.mailman3

6 13

Mails for 1 specific mailinglist not being send and looping in out queue
by Eric Broens Jan. 9, 2021

Jan. 9, 2021

For some reason, the mail for 1 specific mailinglist doesn't get distributed. It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail.The mailman3 error log show that there is a connection failure to port 25.A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail.Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail.Using qfile, the pck file of this mail looks fine. New emails on this specific mailinglist are not distributed either.For all other mailinglists on this server, and which are on the same domain, there are no problems. Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue?Below are the relevant extracts from the log files for the particular case. mailman smtp.log: Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost... Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to *** mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25 mailman debug.log Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>... Thanks in advance,Eric

1 0

export and import database?
by Andreas Barth Jan. 4, 2021

Jan. 4, 2021

Hi, is there an recommended way to export and import all of the configuration in the database (so that I could change the database on import, i.e. not on database level)? Regards, Andi

2 1

required cron entries?
by Andreas Barth Jan. 2, 2021

Jan. 2, 2021

Hi together, as I found some mails in queue/shunt, I thought who should be running them. On my (standard debian) reference system, there are no cron entries for mailman3 but only for mailman3-web. Looking in the source code, there is a ./cron/crontab.in.in however references to scripts in port_me/ directory. Should I (still) install (parts of) the crontab? Or are these functions handled elsewhere? Also, who picks up mails in queue/shunt? Or are they lost somehow? (Or did I miss the documentation somewhere?) Regards, Andi

3 8

Syncing Real Name between user account and membership
by Andreas Barth Dec. 31, 2020

Dec. 31, 2020

Hi together, a user was mass-subscribed (with a wrong name) and now registered and changed his name via the web interface but the list entry is not changed. On looking further at that, I got to the following json outputs: curl -urest:pass http://localhost:8001/3.0/addresses/user@example.com/user { "created_on": "2020-11-26T15:43:24.928285", "is_server_owner": false, "self_link": "http://localhost:8001/3.0/users/123456", "user_id": 123456 "display_name": "Fixed Name", } curl -urest:pass http://localhost:8001/3.0/addresses/user@example.com { "email": "user(a)example.com", "original_email": "user(a)example.com" "registered_on": "2020-11-26T15:43:24.896405", "self_link": "http://localhost:8001/3.0/addresses/user@example.com", "display_name": "Broken Name", "verified_on": "2020-11-26T15:43:24.965784", "user": "http://localhost:8001/3.0/users/123456" } Should the fix of the name propagate? Or what would be the appropriate action here? Regards, Andi

4 9

Upgrade to 3.3.2 fails
by Joel Lord Dec. 28, 2020

Dec. 28, 2020

I've just upgraded python to 3.7, so now I can upgrade mailman from 3.3.1 to 3.3.2. Take it down, "pip install --upgrade mailman", and try a "mailman info". It fails hard, and what I think are the important parts of the stack trace are: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1118, 'Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs') [SQL: ALTER TABLE mailinglist ADD COLUMN archive_rendering_mode INTEGER] (Background on this error at: http://sqlalche.me/e/13/e3q8) Looks to me like the mailinglist table has been using awfully close to the default mysql max row length, and this added column pushes me over? Is there some other fix other than a terrifyingly gigantic process of dumping all my databases, changing my page size, and restoring them all? This DB server isn't serving just mailman... Thanks -- Joel Lord

3 7

WEB UI fail to reply and create new thread
by Milan P. Stanić Dec. 23, 2020

Dec. 23, 2020

Hi, Alpine Linux is testing mailman3 as system for project mailing lists. We created docker-compose which can be seen here https://gitlab.alpinelinux.org/alpine/infra/compose/mailman We installed it and run in testing system here https://lists-test.alpinelinux.org/hyperkitty/ Sending mail by mail clients works and mails are sent to subscribers properly. Most other 'things' works but we have problem with reply to posts and creating new threads using web ui. When replying to post with web ui it says that the everything is ok and post is sent but post doesn't arrive to mailing list. Same happens with creating new thread. Our debug says "KeyError: 'display_fixed'" but we are not sure what should be changed/fixed/set for this problem. Attached is excerpt from debug log. TIA, mps

4 5

Docker Core Configuration "MUST" Documentation
by James Bowery Dec. 23, 2020

Dec. 23, 2020

The docker core configuration README says: "These are the variables that you MUST change before deploying:" Does this mean: "The following variables MUST be set in /opt/mailman/core/mailman-extra.cfg (on the host) to match the values in docker-compose.yaml before deploying:" ?

2 1

Re: Equivalent Apache2 Directives for Those From the Docker Nginx Documentation?
by James Bowery Dec. 22, 2020

Dec. 22, 2020

Thanks. That configuration worked for me -- at least to the point that I got this in my apache error log, which means the proxy pass was working: [Sun Dec 20 22:45:02.548267 2020] [proxy:error] [pid 18049] (111)Connection refused: AH00957: uwsgi: attempt to connect to 172.19.199.3:8080 (172.19.199.3) failed [Sun Dec 20 22:45:02.548294 2020] [:error] [pid 18049] [client ....:59424] AH10101: failed to make connection to backend: 172.19.199.3:8080 On Mon, Dec 14, 2020 at 10:03 PM <matthew(a)alberti.us> wrote: > James, > This is what I put in my apache2 conf for the mailman virtual host: > > #Mailman3 Web Configuration > Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico > > Alias /static /opt/mailman/web/static > <Directory /opt/mailman/web/static> > Require all granted > </Directory> > > ProxyPassMatch ^/static ! > ProxyPassMatch ^/favicon.ico ! > ProxyPass / uwsgi://172.19.199.3:8080/ > > I don't believe I did anything to uwsgi's conf. One thing I did > notice is that the '/' on the end of the 'ProxyPass' command (last line) is > relevant. I think it didn't work right without it. > > I am interested to hear from others if that configuration is > complete. It works as far as I know. > > - Matt Alberti > > -----Original Message----- > From: James Bowery <jabowery(a)gmail.com> > Sent: Monday, December 14, 2020 8:27 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Equivalent Apache2 Directives for Those From the > Docker > Nginx Documentation? > > The Docker documentation at: > > https://asynchronous.in/docker-mailman/#dependencies > > I've installed and enabled proxy_uwsgi for Apache and made a rough cut at a > configuration for the lists.* subdomain in question but it's failing. > > What follows are the document's Nginx directives for which I would greatly > appreciate the Apache2 equivalents. I'm attempting to move a mailing list > off of Yahoo groups onto my hosted server using an Apache2's virtual host > on > the 'lists' subdomain: > > Setting up your web server: > > # Nginx configuration. > > location / { > # First attempt to serve request as file, then > > proxy_pass http://172.19.199.3:8000; > include uwsgi_params; > uwsgi_read_timeout 300; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > > uwsgi: > > # Nginx configuration. > > location / { > # First attempt to serve request as file, then > > uwsgi_pass 172.19.199.3:8080; > include uwsgi_params; > uwsgi_read_timeout 300; > } > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe > send > an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

3 8

Message Sent to A Re-Created List Results In Error
by matthew＠alberti.us Dec. 17, 2020

Dec. 17, 2020

I created a list in the Postorius interface, used it, and then deleted it. A week or so later, I re-created the list, and things were fine thru the creation and subscription process. But when I sent a message to the list, a "550 user unknown" error was sent back. I tried to determine if this is a known issue by searching the issues in Gitlab; but didn't find anything. But wanted to ask if this was a known issue or not? Thanks. - Matt Alberti

4 5

moderator cannot login to the list
by Gregory Edigarov Dec. 17, 2020

Dec. 17, 2020

Hello, I am using this mailman: GNU Mailman 3.2.1 (La Villa Strangiato) Python 3.7.3 (default, Jul 25 2020, 13:03:44) I've imported some lists from mailman-2.1 using 'mailman import21' command. the import went fine, I am able to login into postorius as admin, and see all imported mail list data. but login as a moderator member of a list. I tried to reset moderator password via rest api. That doesn't help. how is that supposed to be done? thank you. -- With best regards, Gregory Edigarov

3 2

Mailman automatic accept notification
by tambet.paide＠mkm.ee Dec. 16, 2020

Dec. 16, 2020

How can I configure mailman so that all the users in mailing list won't get automatic accept notification (uncaught bounce notification)? I'n mailman configure I cant find nothing about disabling bounce message. I'm using Mailman 3 and cat figure it out

4 8

Handling of (un)subscribe mails for already (un)subscribed users
by Andreas Barth Dec. 15, 2020

Dec. 15, 2020

Hi, I noticed that a mail to -subscribe for an already subscribed user doesn't get any response (about line 225 in mailman/src/mailman/app/subscriptions.py). Same but different for unsubscribe for users not on the list. I'd need these kind of mails however in hope that users complain less. Would that be generally interessting, and if so, any special requirements for submitting patches, or should I just do that locally? Regards, Andi

3 7

Equivalent Apache2 Directives for Those From the Docker Nginx Documentation?
by James Bowery Dec. 15, 2020

Dec. 15, 2020

The Docker documentation at: https://asynchronous.in/docker-mailman/#dependencies I've installed and enabled proxy_uwsgi for Apache and made a rough cut at a configuration for the lists.* subdomain in question but it's failing. What follows are the document's Nginx directives for which I would greatly appreciate the Apache2 equivalents. I'm attempting to move a mailing list off of Yahoo groups onto my hosted server using an Apache2's virtual host on the 'lists' subdomain: Setting up your web server: # Nginx configuration. location / { # First attempt to serve request as file, then proxy_pass http://172.19.199.3:8000; include uwsgi_params; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } uwsgi: # Nginx configuration. location / { # First attempt to serve request as file, then uwsgi_pass 172.19.199.3:8080; include uwsgi_params; uwsgi_read_timeout 300; }

2 1

Data too long for column 'data' in workflowstate
by Morris Jones Dec. 14, 2020

Dec. 14, 2020

I ran into this error attempting to add a user to a mailing list: (pymysql.err.DataError) (1406, "Data too long for column 'data' at row 1") [SQL: INSERT INTO workflowstate (token, step, data) VALUES (%(token)s, %(step)s, %(data)s)] [parameters: {'token': '7394fbf654b3faffc6a65eb95e0616eea6651b9e', 'step': 'do_confirm_verify', 'data': '{"pre_approved": false, "pre_confirmed": false, "pre_verified": false, "invitation": false, "address_key": "dorothyxxxxxxxx(a)gmail.com", "subscriber_key": 1, "user_key": "00201c01dcc443c3a0d8f6d1ea42e230", "token_owner_key": 1, "send_welcome_message": null}'}] In MySQL I see that column 'data' in workflowstate is VARCHAR(255), and the data in the query is 259 characters. If I have a moment I'll write a bug or patch ... but I'm not really current on schema migrations. Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

2 2

Permission denied for /list:member:digest:header.txt
by Eric Broens Dec. 14, 2020

Dec. 14, 2020

Hi, despite mailman is running as mailman user and the required periodic jobs have all been created in crontab for the mailman user, a permission denied exception for the digest file has been logged in mailman.log: Dec 14 11:31:42 2020 (399913) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/templates/lists/...//list:member:digest:header.txt' The subdirectories and files of the templates subdirectory got the root owner and group: drwxr-xr-x. 3 mailman mailman 4096 Dec 12 17:58 templates drwxr-xr-x. 11 root root 4096 Dec 12 19:20 lists -rw-rw----. 1 root root 16 Dec 12 19:19 list:member:digest:header.txt How can this be avoided? Best Regards,Eric

3 8

Importing config and archives only partially succeeded?
by Eric Broens Dec. 13, 2020

Dec. 13, 2020

Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. The imported members and other settings are correctly shown in the postorius page. Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails. Thanks in advance,Eric

2 11

troubleshooting hyperkitty
by Morris Jones Dec. 10, 2020

Dec. 10, 2020

Working on a new installation -- lists seem to be working in terms of distributing postings. But none of the postings are appearing in an archive yet. I created a mailman-hyperkitty.cfg file in /opt/mailman/var/etc/. It has a base_url for the "hyperkitty installation," and I'm not sure where that's supposed to be. The comment says "This address will be used by Mailman to forward incoming emails to Hyperkitty for archiving." I set base_url to http://mailman.whiteoaks.com/hyperkitty (changing "localhost" from the example). It redirects to https:, I set new secret keys here and in mailman.cfg. No new posts appear, and nothing archive related shows up in mailman's log. The mailman qcluster is running. The runner=archive job is running. Can someone suggest a troubleshooting strategy? 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>

3 10

Hyperkitty Recommended mySQL Database Setup & Archive Importing
by matthew＠alberti.us Dec. 10, 2020

Dec. 10, 2020

Hi, I've been working for quite a while to setup a production mailman3. Using the docker containers, I have been pretty successful getting it to work. Part of the challenge now is that there are a lot of issues when importing archives from mailman2. This of course is more common on lists that are over 10 years old. From what I've been reading, it seems like Mailman3 expects the mysql database to use UTF8 encoding. It appears, by default, that when using the docker-mailman containers, that the character set is set to latin1. This may explain why there are lots of import errors, and maybe also why there are a lot of errors when threads are deleted in hyperkitty's UI. Is it the case that UTF8 is the preferred character set? I also saw some threads indicating that maybe utf8mb4 is more preferred. I'd like to try to change the character_set on the database, if that is advisable. Also, is Hyperkitty 1.3.4 officially released? I see that the list.org instance is using it, but the latest announce I've seen is for 1.3.3. Thanks. - Matt Alberti

3 8

Version mismatch
by Andrew Bernard Dec. 9, 2020

Dec. 9, 2020

In the annoucement mail, the new version is - Mailman Core 3.3.0 (Tom Swayer) but on my webpage I see: Mailman Core Version GNU Mailman 3.3.0 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0] Why is the version name from the previous release? is my setup wrong? [There are so many issues I keep reporting here about Mailman that get no response that I wonder if there is something fundamentally wrong with my site.] Andrew

4 3

Message moderatin without login
by Michael Lorenzen Dec. 8, 2020

Dec. 8, 2020

Hi, are there any plans to allow message moderation without having to login to posterious? I am very pleased with the new web interface and the rest api, but i miss the ability to moderate messages either by mail, with different reply addresses to discard, reject or accept hold messages or by html links with one time codes to achieve the same. I tried to reply on the mail attachment with the confirm ... subject, but that did not seem to work (neither reject nor accept with approved: placed into the first line of the mail). Best regards, Michael

2 1

Moderated Signup with "info" box?
by chris＠zimmerman.to Dec. 8, 2020

Dec. 8, 2020

Hi all, we have a mailman deployment that we are using for a private neighborhood community board. We have the list setup for moderated approval signup. The trouble is, when someone signs up, we only get a request with their email address. I would like to be able to use the web form, but have a "notes" field that would get submitted with the signup request. the notes field would be where the user would note name/home address. So when one of our moderators get the request, they can figure out quick who the request is coming from. Can anyone provide some guidance or assistance on how to make that happen?

5 8

Spam getting in for moderated list
by Quanah Gibson-Mount Dec. 6, 2020

Dec. 6, 2020

I have a list that has the following settings: List members -> Hold: This holds the message for approval by the list moderators. Non-subscribers -> Silent discard And yet, spam emails from a spammer that signed up to the list are going straight through and being delivered. Is this a known bug in mailman 3.2.1? Example: <https://lists.openldap.org/hyperkitty/list/openldap-bugs@openldap.org/threa…> It even has this list header: X-Mailman-Rule-Hits: member-moderation and version is X-Mailman-Version: 3.2.1 I think it was sent via the web interface? User-Agent: HyperKitty on https://lists.openldap.org/ I checked the settings for this subscribed spam user, and it specifically says "list default" for moderation, so it should have been moderated. Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

2 2

mailman-suite scheduled tasks
by Eric Broens Dec. 6, 2020

Dec. 6, 2020

Hi, The documentation https://docs.mailman3.org/en/latest/config-web.html includes a section on scheduled tasks that need to be included in cron. "runjobs" seems to be available only from "manage.py". Do these scheduled tasks need to be executed from the python virtual environment?If so, is there a way to do that directly from cron, or should I create a script for these tasks which can be called from by cron? Best Regards,Eric

2 2

Server name in new account confirmation email
by Meehan, John Dec. 3, 2020

Dec. 3, 2020

Hi, when someone creates a new account (Sign Up), an email is sent to them to confirm their email address. It has the form below. Does anyone know how I can change the server name in the URL (From server.example.com to something else)? I have an SSL proxy server that I want to direct users through. Thanks. - John Hello from example.com! You're receiving this e-mail because user johndoe has given yours as an e-mail address to connect their account. To confirm this is correct, go to https://server.example.com/accounts/confirm-email/Mg:1kkdMg:i4i4ycbBdukoSMd… Thank you from example.com! example.com

3 3

mailman3 OWNERS_CAN_ENABLE_PERSONALIZATION option
by Henry S Dec. 3, 2020

Dec. 3, 2020

I am trying to change email "To" field to user's email instead of mailing list's email. e.g. "To: <user(a)gmail.com>" instead of "To: <mailman-users(a)mailman3.org>" I looked around old mailman configs they mentioned about adding OWNERS_CAN_ENABLE_PERSONALIZATION option in mm_cfg.py is this feature still available in mailman3 ? Can I do it via Postorius or REST API? Thanks.

2 2

Initial success: Mailman 3.3 integrated with Zimbra 8.8
by Morris Jones Dec. 2, 2020

Dec. 2, 2020

I have a very old existing mail server running Zimbra 6 with a mailman 2.1 instance alongside. I needed to rebuild my mail server for some compelling reasons (the old server used outdated TLS protocol, I could no longer compile clamav, nothing could really be updated). The final straw was a lack of support for my old commercial SSL certificates. I patched in a letsencrypt certificate to get through the past six months. I'm in the process of commissioning a new mail server using an 8GB Linode, Ubuntu 18, Zimbra 8.8, and Mailman 3.3. A couple of days ago I had my first successful list creation, with user confirmation working by email. I have django running with uwsgi, and am using Zimbra's installed nginx proxy to reverse proxy http traffic to Postorius and Hyperkitty. Nginx is doing the SSL layer. The mailman core mta hooks are all done using Zimbra's "local configuration" technique. In theory I should be able to do Zimbra upgrades with a minimum of hassle. I've written up a "case history" of how it came together. I have a .rst file in a gitlab project here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration I suppose this is a crazy project, but it's worthwhile to me. (Mark, thank's so much for integrating the virtual domain maps. It took me about three days to recognize that they were the solution to bounced mails to list-owner@...) Now I can spend some time migrating my email accounts (only four) from the old server to the new one, and move a dozen or so mailing lists to the new mailman3 instance. I'll have to get accustomed to a new way to manage the mail lists, and already really like what I've seen. Thank you. :) 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>

1 0

Mailmansuite.log Entries
by Brian Carpenter Dec. 2, 2020

Dec. 2, 2020

I see the following log entries in mailmansuite.log: INFO 2020-11-28 00:00:52,242 29142 hyperkitty.lib.mailman 2117 emails left to refresh, checked 1000 INFO 2020-11-28 00:01:00,600 29142 hyperkitty.lib.mailman 2117 emails left to refresh, checked 2000 INFO 2020-11-29 00:00:52,135 15513 hyperkitty.lib.mailman 2117 emails left to refresh, checked 1000 INFO 2020-11-29 00:01:00,192 15513 hyperkitty.lib.mailman 2117 emails left to refresh, checked 2000 INFO 2020-11-30 00:00:52,484 22622 hyperkitty.lib.mailman 2117 emails left to refresh, checked 1000 INFO 2020-11-30 00:01:00,758 22622 hyperkitty.lib.mailman 2117 emails left to refresh, checked 2000 INFO 2020-12-01 00:00:50,246 11946 hyperkitty.lib.mailman 2117 emails left to refresh, checked 1000 INFO 2020-12-01 00:00:59,688 11946 hyperkitty.lib.mailman 2117 emails left to refresh, checked 2000 I assume this is a result of importing archives from a MM2 mbox file. This happen months ago however. Why are these entries still showing up? -- Brian Carpenter Harmonylists.com Emwd.com

2 3

12/24 hour clock ?
by Per Jessen Nov. 28, 2020

Nov. 28, 2020

Hi all at openSUSE we have recently migrated to mailman3, and we seem to be having a couple of teething issues: a) hyperkitty and postorius both seem to insist on using a 12 hour clock format, no matter what the user has set. Is there a way of changing it system-wide ? b) overriding the default set of footers - despite having set the template "list:member:regular:footer" to empty for a specific list, I am still getting the default footers attached. We are using version 1.3.3. thanks Per Jessen

2 2

No styling for web apps?
by Morris Jones Nov. 27, 2020

Nov. 27, 2020

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. (Happy Thanksgiving!) Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

2 3