Mailman 3 January 2020 - Mailman-Users

Re: [Mailman-Users] Mailman-Users Digest, Vol 191, Issue 3
by Allan Hansen Jan. 6, 2020

Jan. 6, 2020

Thanks again, Mark! My responses below. > On 1/4/20 5:47 PM, Allan Hansen wrote: >> >> a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in >> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? > > > What are the setytings in Postorius -> Settings -> Archiving? Archive policy: Private archives Archive archivers: hyperkitty, prototype > > >> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. > > > Set > > FILTER_VHOST = True > > in settings_local.py > Yes, Brian told me to do the same. This is the what I wrote back: hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py Edited the setting to: # Only display mailing-lists from the same virtual host as the webserver FILTER_VHOST = True Then Brian told me to restart qcluster: hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the setting. Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >> >> Something went wrong >> Mailman REST API not available. Please start Mailman core. > > > Postorius is unable to access core's REST API. Is Mailman running? Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but nothing explicitly with a ‘mailman’ string. > If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's > called - defined as `filename` in the `file` handler in the LOGGING > definition in settings(_local).py. hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log return Site.objects.get_current(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current return self._get_site_by_request(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request SITE_CACHE[domain] = self.get(domain__iexact=domain) File "/opt/mailman/mm/venv/lib/python3.7/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.7/site-packages/django/db/models/query.py", line 408, in get self.model._meta.object_name django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. [ABH] At this point I click to accept a subsription request: ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen chunked=chunked, File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse response.begin() File "/usr/lib/python3.7/http/client.py", line 296, in begin version, status, reason = self._read_status() File "/usr/lib/python3.7/http/client.py", line 265, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response So yes, the REST API is not there. How can I get it going? Before we added the new domain, I was able to accept subscription requests to the previous domain’s lists. No more. Yours, Allan > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

2 1

msg marked as spam 554 5.7.1 [P4]
by Jim Dory Jan. 6, 2020

Jan. 6, 2020

So I'm just a volunteer who doesn't understand much about email systems.. just rudimentary - and I am managing an email list for community announcements and trade, by subscription only. We have about 1500 subscribers. I have one problem that when a particular user (the city) sends an announcement, it tends to bounce hundreds of mainly one ISP's users.. that ISP being Alaska's GCI.com . Other users, say on hotmail, yahoo, etc.. don't get bounced. I manage the emails via gmail and lately I've been "locked out of gmail due to suspicious email activity" which is a pain in the rear. Also causes my host (Hawkhost) grief.. the overhead they dislike though they haven't complained lately. So I'm motivated to look into this a bit. Sometimes I do get this: host mx1.arandomserver.com [198.252.100.64] SMTP error from remote mail server after end of data: 550 Headers contain illegal BOM on my personal email from the same sender (city), but not sure that is same issue. The city usually includes a link to the city codes on a public webpage - perhaps that triggers GCI. I could post one of the headers in total but it is probably about 3 pages worth. Everything sort of looks ok to me except I notice this: BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [34.212.96.103 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message The link in the messages is https://www.codepublishing.com/AK/Nome/ . I can post more of the header if need be. Could it be that GCI needs to whitelist or something? thx, Jim

4 6

MM3 startup issues
by Allan Hansen Jan. 5, 2020

Jan. 5, 2020

After having MM3 installed, I’m trying to get it setup up correctly for my lists. I have a couple of issues at this point: a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? The instructions we received were these: How to setup an additional domain to the Mailman 3 server: • Add the additional domain name to Django Sites and Mail domains via the Django admin panel. This will require superuser access. • Make sure the list admin(s) of any list is registered with Django. • Setup the new list domain in nginx (/etc/nginx/conf.d). You can copy and paste the existing record there to the new record. Just make sure you modify the server_name directive in the record to the new domain name. The record file name should be newdomainname.com.conf. This will need to be done via shell with sudo privileges. • Test nginx configuratin (nginx -t) • Reload nginx (nginx -s reload) • Generate LetsEncrypt Cert (certbot --nginx -d newdomainname.com) Before doing this make sure the appropriate DNS records are setup pointing the new list domain to your Mailman 3 server otherwise this part will fail. • Add the new list domain to /opt/mailman/mm/settings_local.py in the ALLOWED_HOSTS section. • Add list domain to Postorius. • Create the list in Postorius using the new list domain. b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: Something went wrong Mailman REST API not available. Please start Mailman core. Oh, and Happy New Year to all, Allan Hansen

2 1

Mailman 3.0 Documentation
by Allan Hansen Jan. 1, 2020

Jan. 1, 2020

All, I have spent some time now trying to understand the list admin interface to Mailman 3.0. There is no context-sensitive help and looking around at the Mailman sites, I mostly find instructions on how to install Mailman 3.0, but no documentation on using it (other than for end users - which is much improved over MM2). I also looked in the FAQ. Is there such docs and, if so, where can I find them. It’s about terminology and how to mangle the headers, etc. Oh, and a big thanks to Brian Carpenter of EMWD for his help installing MM3, as I ran into a wall in my own attempt. MM3 appears to be a big end-user improvement over MM2. Thanks also, developers, for the work on MM3 development. I can see that it was a mountain of work to get that done. Yours, Allan

2 1