Re: [Mailman-Users] msg marked as spam 554 5.7.1 [P4]
On Sun, Jan 5, 2020 at 7:21 PM Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > > I'd need to see that > message's full header to debug that fully, but it sounds like GCI is > generally not doing a great job here. > > > Ok - just for curiosity sake, here is full header. I've 'ed out names. But Bruce and Stephen are probably correct in that I need to contact GCI. I will also put out a request to subscribers of our list to ask that people don't mark these messages as spam. I have done this in the past probably to no avail.. what helps there is getting on email providers' feedback loops where I've been able to solve yahoo.com user problems. But I haven't found one with GCI. For clarity, I have my email address set as admin that is my own domain hosted on Hawkhost. It is POP3'd to gmail, so that's the first part of the header where gmail gets involved. The list is nome-annou...@nomekennelclub.com (the kennelclub just lets us use their domain), also on Hawkhost, who uses arandomserver.com as their DNS server, I believe. Alaskan.com is a GCI.net domain, as well as a few others. GCI is the one blocking these messages from the city to its subscribers. The city domain is nomealaska.org . Delivered-To: @gmail.com Received: by 2002:ac8:4912:0:0:0:0:0 with SMTP id e18csp19003587qtq; Fri, 3 Jan 2020 11:56:18 -0800 (PST) X-Google-Smtp-Source: APXvYqwk2NggdPGoR1J3DEcdLZMVhDU2UAjEn8UBHjRZFns/bzyDwsAyaLWiml3ZpNgU9VgmRWhOKdATxXI= X-Received: by 2002:ac8:d86:: with SMTP id s6mr59784558qti.237.1578081378216; Fri, 03 Jan 2020 11:56:18 -0800 (PST) Authentication-Results: mx.google.com; spf=neutral (google.com: 198.252.100.64 is neither permitted nor denied by best guess record for domain of mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com) smtp.mailfrom= mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com Received-SPF: neutral (google.com: 198.252.100.64 is neither permitted nor denied by best guess record for domain of mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com) client-ip=198.252.100.64; Received: by 2002:ac8:7104:: with POP3 id z4mf28611506qto.6; Fri, 03 Jan 2020 11:56:18 -0800 (PST) X-Gmail-Fetch-Info: james@.com 1 mail..com 110 james@.com Return-Path: < mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com> Delivered-To: james@.com Received: from lax003.hawkhost.com by lax003.hawkhost.com with LMTP id eJ7WCJSYD15vFQAAva6gig (envelope-from < mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com>) for .com>; Fri, 03 Jan 2020 11:40:04 -0800 Return-path: < mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com> Envelope-to: james@.com Delivery-date: Fri, 03 Jan 2020 11:40:04 -0800 Received: from se001.arandomserver.com ([198.252.100.64]:48764) by lax003.hawkhost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from < mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com>) id 1inSnj-0001sJ-TR for james@.com; Fri, 03 Jan 2020 11:40:04 -0800 Received: from cloud.nomekennelclub.com ([198.252.100.6]) by se001.arandomserver.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from < mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com>) id 1inSni-000Hqn-Aw for james@.com; Fri, 03 Jan 2020 14:40:03 -0500 Received: from [127.0.0.1] (port=35254 helo= cloud.nomekennelclub.com.cloud.nomekennelclub.com) by cloud.nomekennelclub.com with esmtp (Exim 4.92) (envelope-from < mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com>) id 1inSnh-000IHZ-Gi; Fri, 03 Jan 2020 19:40:01 + Received: from [127.0.0.1] (port=35252 helo= cloud.nomekennelclub.com.cloud.nomekennelclub.com) by cloud.nomekennelclub.com with esmtp (Exim 4.92) (envelope-from < nome-announce-boun...@nomekennelclub.com>) id 1inSng-000IHH-Fe for nome-announce-ow...@nomekennelclub.com; Fri, 03 Jan 2020 19:40:00 + Subject: Bounce action notification From: mail...@nomekennelclub.com To: nome-announce-ow...@nomekennelclub.com MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===7118919187349444018==" Message-ID: < mailman.423.1578080399.54331.nome-announce_nomekennelclub@nomekennelclub.com > Date: Fri, 03 Jan 2020 19:39:59 + Precedence: list X-BeenThere: nome-annou...@nomekennelclub.com X-Mailman-Version: 2.1.29 List-Id: Trade and Community Announcements X-List-Administrivia: yes Errors-To: mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com Sender: Nome-announce < mailman-boun...@cloud.nomekennelclub.com.cloud.nomekennelclub.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud.nomekennelclub.com X-AntiAbuse: Original Domain - .com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - cloud.nomekennelclub.com.cloud.nomekennelclub.com X-Get-Message-Sender-Via: cloud.nomekennelclub.co
Re: [Mailman-Users] MM3 startup issues
Restoring original Subject:, and doesn't this thread belong on mailman-us...@msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: > > 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 Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> 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 You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > 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 you do `ps ax|grep runner=`, what do you see? If you don't see at least three processes with `--runner=rest:0:1`, stop Mailman and start Mailman. >> 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. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [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 rec
