- Mailman-users - lists.mailman3.org

Adding a domsin
by Allan Hansen 13 Jan '20

13 Jan '20

Hi all, I’m still working on setting up my lists in a domain that was added after MM3 installation. It’s mostly working but the Postorius page and the ‘noreply’ emails still sport the old domain name. I hav looked at all the py and cfg files where the old name appeared, and they no longer hold the old name. My coadmin now tells me that the database has a table with the old name. Any suggestion as to whether that can cause the issue and if it’s safe to change the table. Yours, Allan Hansen P.O. Box 2423 Cypress, CA 90630

3 3

Cannot setup HTTPS support for mailman3-web
by jean-christophe manciot 11 Jan '20

11 Jan '20

Ubuntu 20.04 mailman3 3.2.2-1 mailman3-web 0+20180916-10 python3-django 2:2.2.9-2ubuntu1 In ```/etc/mailman3/uwsgi.ini``` (example.org is defined in the local /etc/hosts as 10.0.0.1): ``` [uwsgi] # Port on which uwsgi will be listening. ### suwsgi: uwsgi protocol over TLS uwsgi-socket = example.org:8430 # https://uwsgi-docs.readthedocs.io/en/latest/HTTPS.html?highlight=ssl https = /etc/ssl/example.org.crt,/etc/ssl/example.org_rsakey.pem.decrypted,HIGH ... # Drop privileges and don't run as root. uid = www-data gid = www-data ... ``` I suppose that uwsgi reads the certificate & its private key before dropping root privileges. Right now, uwsgi cannot access them as ```www-data```. In ```/etc/mailman3/mailman-web.py``` (symlinked to django settings.py) : ``` ... SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https') # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' ... POSTORIUS_TEMPLATE_BASE_URL = 'https://example.org:8430' ``` In ```/etc/nginx/sites-enabled/example.org.conf``` ``` ... location / { include /etc/nginx/uwsgi_params; # upstream app server uwsgi_pass suwsgi://example.org:8430; } ``` uwsgi is listening on the right address/port: ``` # networks-list-connections.sh | grep :8430 tcp 0 0 10.0.0.1:8430 0.0.0.0:* LISTEN 33 54336045 1768187/uwsgi ``` Despite those settings and all the relevant systemd services restarted, I get ```502 Bad Gateway``` while browsing to ```https://example.org/postorius/lists/?all-lists``` (or any other page) with the following error nginx message: ``` *1 peer closed connection in SSL handshake while SSL handshaking to upstream, client: 10.0.0.1, server: example.org, request: "GET /postorius/lists/?all-lists HTTP/2.0", upstream: "suwsgi://10.0.0.1:8430", host: "example.org", referrer: "https://example.org/postorius/lists/" ``` Of course, without those specific https/suwsgi settings, everything works fine. What am I missing/doing incorrectly? Does uwsgi need access to the certificate/private key while running as non-root for instance?

3 3

Default values for new lists
by Sten Aus 11 Jan '20

11 Jan '20

Hi I haven't found out where I could choose or edit default list values (when creating new list). For example I would like that all new lists would be with *private archive* (and change this when it is needed). This is great that I can choose not to advertise list in Index (which I can choose from list creation interface) but I would like to choose other options too. Right now only solution is to create list and then choose Archiving and then select "private archives". Another thing is that I would like to choose default subscription policy to "Moderate". If anyone has encountered this problem, let me know! All the best Sten

4 5

bounce processing on this list
by Mark Sapiro 09 Jan '20

09 Jan '20

I have just installed the latest Mailman core for this list. This version now actually processes bounces. As a result of the huge backlog of unprocessed, queued bounces, some members may receive one or more bounce probe messages. As long as the probes don't bounce, your subscription will be unaffected and you can ignore the probe message. Sorry for the noise. Hopefully it's just a one time catch-up. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

FILTER_VHOST for 3.2.1 not working after install
by Élodie BOSSIER 08 Jan '20

08 Jan '20

Hello, I'm using Mailman 2.1.29 since several years and all was perfect except the virtual_host which was "faked" : it was possible to have several mailing list by domain linked to their own domain and url but not same mailing list name for multiple domains. Example (with lighttpd) : - at http://ml.bossier.fr/listinfo we can see ONLY mailing list "test2@", "Test3@" and "Test4@" for @ml.bossier.fr - and at http://ml.franceserv.fr/listinfo we can see ONLY mailing list "bar@", "newsletter@" and "test@" for @ml.franceserv.fr Each url_host have their "own" mailing list. It's the main reason I would like migrate and use Mailman 3 and be able to have "test(a)ml.bossier.fr" and "test(a)ml.franceserv.fr". So I installed Mailman 3.2.1 and I have set "FILTER_VHOST = True" into /etc/mailman3/mailman-web.py then : mailman create --language fr --owner admin(a)franceserv.fr --domain test(a)ml.franceserv.fr mailman create --language fr --owner admin(a)franceserv.fr --domain test2(a)ml.bossier.fr And I have this result (with nginx as front) : - at http://ml.franceserv.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" - and at http://ml.bossier.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" (same result) And it's my problem, I would like be able to see the linked mailing list to their own url. I would like with Mailman 3.2.1 see into : - "example1.com/postorius/lists/" only the mailing list related to example1, - and into "example2.com/postorius/lists/" only the mailing list related to example2 as Mailman 2.1.x do it. I don't understand what I missed, could you help me please ? Best regards, Élodie PS. Sorry for my english language I'm french.

2 1

Migration from 2.1 to 3
by brunol＠agro.uba.ar 08 Jan '20

08 Jan '20

Hi, I am in the process to migrate an old 2.1 installation to 3.2.1 (Debian 10.1) Following the 2.1 to 3 docs: - Create a new list - Use the import21 command The command runs successfully (at least no errors in stdout). There is a problem when sending an email to the newly imported list, the message never get send to the members. I do get moderation emails, and if i do a mass subscribe, the welcome email is received by the new members. In a fresh 3 new list (not imported from 2.1) this does not happen. I already tried looking for clues in the logs [logging.smtp] path: debug.log level: debug [logging.smtp-failure] path: debug.log level: debug [logging.error] path: debug.log level: debug But i haven't seen anything useful yet. Any hints on this?

4 14

Hyperkitty - not sending from GUI & reply-thread
by sunil soprey 08 Jan '20

08 Jan '20

With latest release (HK 1.3.1), does anyone have an issue with no emails from reply-thread? I able to send/receive emails to/from mailman. I see MTA delivered emails, just no emails from HK GUI. No errors logs (py exception) nor mailman. ideaS? Versions: mailman-hyperkitty (1.1.0) - Mailman archiver plugin for HyperKitty INSTALLED: 1.1.0 (latest) HyperKitty (1.3.1) - A web interface to access GNU Mailman v3 archives INSTALLED: 1.3.1 (latest) mailman (3.3.0) - Mailman -- the GNU mailing list manager INSTALLED: 3.3.0 (latest) postorius (1.3.1) - A web user interface for GNU Mailman INSTALLED: 1.3.1 (latest) django-mailman3 (1.3.1) - Django library to help interaction with Mailman INSTALLED: 1.3.1 (latest) mailmanclient (3.3.0) - mailmanclient -- Python bindings for Mailman REST API INSTALLED: 3.3.0 (latest) f

2 1

Re: [Mailman-Users] MM3 startup issues
by Mark Sapiro 07 Jan '20

07 Jan '20

Restoring original Subject:, and doesn't this thread belong on mailman-users(a)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 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? Stop Mailman and then start it. > 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

3 3

MM3 shunting mails
by Anders Nilsson 03 Jan '20

03 Jan '20

I'm running a Mailman 3.1.0 installation on a CentOS 7 machine. Using RPMs from https://repos.fedorapeople.org/repos/abompard/hyperkitty/el-7/x86_64/ I do have problems with some lists occasionally going into some kind of shunt mode, where alla mails sent to them gets shunted. In the Mailman log I get entries for each shunted email: Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 171, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/core/runner.py", line 264, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3.4/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 121, in process process(mlist, msg, msgdata) File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 70, in process archiver_set = IListArchiverSet(mlist) File "/usr/lib/python3.4/site-packages/zope/component/hookable.py", line 33, in __call__ return self.__implementation(*args, **kw) File "/usr/lib/python3.4/site-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib64/python3.4/site-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.4/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", line 2733, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) SHUNTING: 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 And so far my Google-fu hasn't been good enough to give me any useful answers to why this happens. If I dump one of the pickles using qfile I cannot see any complaints. Most of the times, if I remove and recreate a failing list and run unshunt the shunted emails get processed and sent. Anyone seen something similar? Regards, Anders Nilsson -- Anders Nilsson, Ph.D. <andersn(a)control.lth.se> Dep. of Automatic Control, Lund University Phone: +46 (0)46 222 87 94, Fax: +46 (0)46 13 81 18 Mob: +46 (0)703 22 57 67

4 4

Mark a list to prevent it being shown as inactive on HyperKitty
by Steven Maddox 03 Jan '20

03 Jan '20

Lo Folks, Subject says it all really, is there anyway to mark a list as one which should never be shown as inactive on the HyperKitty web interface? We've got a list which we consider to be "active", it's just that there might be the odd month here or there which it won't show activity. Failing having such a setting (as described above)... maybe there is a way of changing what it considers to be 'inactive' (I'm assuming that it is 30 days?). At the moment (in order to counteract commit 156f4cda) I've dropped this into templates/hyperkitty/bottom.html to uncheck the "Hide Inactive" checkbox... but that doesn't actually stop HyperKitty from considering it inactive - just shows it in dark grey. <script> document.querySelector("input[type='checkbox'][value='inactive']").checked = false; </script> -- Steven Maddox Lantizia

2 1