From andrew.bernard@gmail.com Thu Aug 1 10:16:51 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Re: Replies unthreading Date: Thu, 01 Aug 2019 10:16:48 +0000 Message-ID: <156465460888.22504.2836350256633781657@mailman.iad1.psf.io> In-Reply-To: <20190731155448.ygxeop4icn5urhbm@atlantis> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7131088795850057515==" --===============7131088795850057515== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Looking at that issue #216, it appears to be fixed in 1.2.3 at least. However, this reply jumping out problem still persists. Therefore I suppose i= t must be something else. How can I raise a bug? It's quite a bad one, because it renders the web interface as a very messy pl= ace, and users don't know which thread to reply to, when there should only be= one thread. To the point where I am looking for alternate mailing list softw= are! (but I would really like to stick with GNU Mailman 3). Andrew --===============7131088795850057515==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Thu Aug 1 19:38:04 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] Replies unthreading Date: Fri, 02 Aug 2019 04:37:56 +0900 Message-ID: <23875.16276.234003.324493@turnbull.sk.tsukuba.ac.jp> In-Reply-To: <156457337984.22503.13894231353606867035@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7597086895171955673==" --===============7597086895171955673== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Andrew Bernard writes: > Replies to threads from that mailer keep sometimes being properly > threaded in Hyperkitty and then randomly jumping out into a new > thread. I don't understand what you're describing here. Is the archive public so that we can look at it? > Yet the threading appears to be correct in mail programs such as > Thunderbird, Then it's probably a Mailman (HyperKitty) bug. #216 looks like it might be responsible, although in another message you say you think it's fixed in your instance. Again, we need more information to be sure. It's sometimes the case that for various reasons a site has multiple versions installed and the one the site thinks is running isn't actually handling the mail or the archive or whatever. > Possibly some interaction with other RFC-822 headers? Seems unlikely. Some threading algorithms use only References, others use both References and In-Reply-To. However, in most cases In-Reply-To is just a copy of the most recent message ID in References. To check hypotheses about a threading bug we really need to see the Message-IDs, References, and In-Reply-To from the problematic messages and the immediate replies, at least. --===============7597086895171955673==-- From phil@riverbankcomputing.com Mon Aug 5 17:06:09 2019 From: Phil Thompson To: mailman-users@mailman3.org Subject: [MM3-users] Hyperkitty 403 Forbidden Error Date: Mon, 05 Aug 2019 15:44:52 +0100 Message-ID: <8f70bf9ec5c26aae93cc50be1cc5201c@riverbankcomputing.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4294551355269043922==" --===============4294551355269043922== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit I'm in the process of setting up mailman3. The only problem I seem to be having is getting Hyperkitty to archive messages. Rather than the authorisation problems people have previously asked about on the list, I am getting a 403 error... Aug 05 15:38:40 2019 (10229) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: Forbidden

Access is forbidden

(403) Aug 05 15:38:58 2019 (10222) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: Forbidden

Access is forbidden

(403) Any suggestions would be appreciated. Phil --===============4294551355269043922==-- From dancab@caltech.edu Mon Aug 5 22:38:45 2019 From: dancab@caltech.edu To: mailman-users@mailman3.org Subject: [MM3-users] Re: exposing Mailman3 API securely Date: Mon, 05 Aug 2019 22:38:42 +0000 Message-ID: <156504472225.8463.16410823333110589811@mailman.iad1.psf.io> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1872759259552122042==" --===============1872759259552122042== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I was out on vacation for a couple of weeks, so just getting back around to t= his. I downloaded the latest Mailman Client from Gitlab and installed it. I'm now getting slightly different errors. See output below. >>> client.system {'mailman_version': 'GNU Mailman 3.2.2 (La Villa Strangiato)', 'python_versio= n': '3.6.8 (default, Apr 25 2019, 21:02:35) \n[GCC 4.8.5 20150623 (Red Hat 4.= 8.5-36)]', 'api_version': '3.1', 'self_link': 'http://localhost:8001/3.1/syst= em/versions', 'http_etag': '"a4e539145192f2cd02e837a2b905583fe4649fdc"'} ">>> client.domains Traceback (most recent call last): File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/conn= ection.py", line 159, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/util= /connection.py", line 80, in create_connection raise err File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/util= /connection.py", line 70, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/conn= ectionpool.py", line 600, in urlopen chunked=3Dchunked) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/conn= ectionpool.py", line 354, in _make_request conn.request(method, url, **httplib_request_kw) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 12= 39, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 12= 85, in _send_request self.endheaders(body, encode_chunked=3Dencode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 12= 34, in endheaders self._send_output(message_body, encode_chunked=3Dencode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 10= 26, in _send_output self.send(msg) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 96= 4, in send self.connect() File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/conn= ection.py", line 181, in connect conn =3D self._new_conn() File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/conn= ection.py", line 168, in _new_conn self, "Failed to establish a new connection: %s" % e) urllib3.exceptions.NewConnectionError: : Failed to establish a new connection: [Errno 111] Con= nection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/requests/ada= pters.py", line 449, in send timeout=3Dtimeout File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/conn= ectionpool.py", line 638, in urlopen _stacktrace=3Dsys.exc_info()[2]) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/urllib3/util= /retry.py", line 398, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host=3D'localhost', port= =3D8001): Max retries exceeded with url: /3.1/domains/caltech.edu (Caused by = NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/mailmanclien= t/restbase/connection.py", line 96, in call headers=3Dheaders) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/requests/api= .py", line 60, in request return session.request(method=3Dmethod, url=3Durl, **kwargs) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/requests/ses= sions.py", line 533, in request resp =3D self.send(prep, **send_kwargs) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/requests/ses= sions.py", line 646, in send r =3D adapter.send(request, **kwargs) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/requests/ada= pters.py", line 516, in send raise ConnectionError(e, request=3Drequest) requests.exceptions.ConnectionError: HTTPConnectionPool(host=3D'localhost', p= ort=3D8001): Max retries exceeded with url: /3.1/domains/caltech.edu (Caused = by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused'= ,)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "", line 1, in File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/mailmanclien= t/restobjects/domain.py", line 35, in __repr__ return ''.format(self.mail_host) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/mailmanclien= t/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/mailmanclien= t/restbase/base.py", line 85, in _get return self.rest_data.get(key) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/mailmanclien= t/restbase/base.py", line 74, in rest_data response, content =3D self._connection.call(self._url) File "/opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/mailmanclien= t/restbase/connection.py", line 119, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect t= o Mailman API" --===============1872759259552122042==-- From maxking@asynchronous.in Tue Aug 6 02:38:17 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty 403 Forbidden Error Date: Mon, 05 Aug 2019 19:38:11 -0700 Message-ID: In-Reply-To: <8f70bf9ec5c26aae93cc50be1cc5201c@riverbankcomputing.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7161317754935547539==" --===============7161317754935547539== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: > I'm in the process of setting up mailman3. The only problem I seem to be=20 > having is getting Hyperkitty to archive messages. Rather than the=20 > authorisation problems people have previously asked about on the list, I=20 > am getting a 403 error... >=20 > Aug 05 15:38:40 2019 (10229) HyperKitty failure on=20 > http://localhost/mailman3/hyperkitty/api/mailman/urls:=20 > Forbidden >

Access is forbidden

(403) > Aug 05 15:38:58 2019 (10222) HyperKitty failure on=20 > http://localhost/mailman3/hyperkitty/api/mailman/archive:=20 > Forbidden >

Access is forbidden

(403) >=20 > Any suggestions would be appreciated. How did you install Hyperkitty? You probably need to the set the API key correctly in both Core and Hyperkitt= y. Have you looked at documentation here[1]? [1]: https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-m= ailman Note that the MAILMAN_ARCHIVER_KEY =3D "value" (this value should be in quote= s, single or double, doesn't matter) in your settings.py for Web (Django) sho= uld be same as the `api_key : value` (without quotes here in hyperkitty.cfg c= onfig file).=20 >=20 > Phil > _______________________________________________ > 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/ > --=20 thanks, Abhilash Raj (maxking) --===============7161317754935547539==-- From phil@riverbankcomputing.com Tue Aug 6 08:49:03 2019 From: Phil Thompson To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty 403 Forbidden Error Date: Tue, 06 Aug 2019 09:48:59 +0100 Message-ID: <966f5e06f9fc4ee34e431382d0d57a4e@riverbankcomputing.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8232057348674184373==" --===============8232057348674184373== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 06/08/2019 03:38, Abhilash Raj wrote: > On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >> I'm in the process of setting up mailman3. The only problem I seem to=20 >> be >> having is getting Hyperkitty to archive messages. Rather than the >> authorisation problems people have previously asked about on the list,=20 >> I >> am getting a 403 error... >>=20 >> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >> http://localhost/mailman3/hyperkitty/api/mailman/urls: >> Forbidden >>

Access is forbidden

(403) >> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >> http://localhost/mailman3/hyperkitty/api/mailman/archive: >> Forbidden >>

Access is forbidden

(403) >>=20 >> Any suggestions would be appreciated. >=20 > How did you install Hyperkitty? On Ubuntu... apt-get install mailman3-full > You probably need to the set the API key correctly in both Core and=20 > Hyperkitty. >=20 > Have you looked at documentation here[1]? >=20 > [1]: > https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail= man >=20 > Note that the MAILMAN_ARCHIVER_KEY =3D "value" (this value should be in > quotes, single or double, doesn't matter) in your settings.py for Web > (Django) should be same as the `api_key : value` (without quotes here > in hyperkitty.cfg config file). That's all correct. I'm familiar with the authorisation issues that=20 other people have had. The only thing I'm doing differently (as far as I am aware) is that I'm=20 using a URL prefixed with /mailman3 which is stripped off in my nginx=20 configuration... # mailman3. location /mailman3/ { uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; include uwsgi_params; uwsgi_param SERVER_ADDR $server_addr; uwsgi_modifier1 30; uwsgi_param SCRIPT_NAME /mailman3; } location /mailman3/static { alias /var/lib/mailman3/web/static; } location /mailman3/static/favicon.ico { alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; } ...but I don't see this affecting the mailman to Hyperkitty=20 communication. Posting to lists and the Postorius and Hyperkitty=20 frontends seem to work fine. Phil --===============8232057348674184373==-- From l.schimmer@cgv.tugraz.at Wed Aug 7 09:57:27 2019 From: Lars Schimmer To: mailman-users@mailman3.org Subject: [MM3-users] Error in mailman3 debian package, python error Date: Wed, 07 Aug 2019 11:57:13 +0200 Message-ID: <784eba29-c9c0-2b9f-dffa-c186e15f1af5@cgv.tugraz.at> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2249086194896132290==" --===============2249086194896132290== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi! Mailman Core Version GNU Mailman 3.2.1 (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] Since yesterday our mailman3 (debian package) throws this error: Internal Server Error: /mailman3/hyperkitty/api/mailman/archive OperationalError at /hyperkitty/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column `mailman3web`.`hyperkitty_email`.`subject` at row 1") Request Method: POST Request URL: http://localhost/mailman3/hyperkitty/api/mailman/archive?key=3DzMxTGlteq4tqkL= 5Mj4y3%2BzypuUwC6P%2Ff Django Version: 1.11.22 Python Executable: /usr/bin/uwsgi-core Python Version: 3.7.3 Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Wed, 7 Aug 2019 08:03:47 +0000 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 101. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 250. self.errorhandler(self, exc, value) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in defaulterrorhandler 50. raise errorvalue File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 247. res =3D self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 411. rowcount =3D self._do_query(q) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _do_query 374. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 292. _mysql.connection.query(self, query) The above exception ((1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column `mailman3web`.`hyperkitty_email`.`subject` at row 1")) was the direct cause of the following exception: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 41. response =3D get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 187. response =3D self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 185. response =3D wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py" in inner 40. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in _decorator 69. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py" in wrapped_view 58. return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in archive 115. add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py" in add_to_list 151. email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save 808. force_update=3Dforce_update, update_fields=3Dupdate_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save_base 838. updated =3D self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _save_table 924. result =3D self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _do_insert 963. using=3Dusing, raw=3Draw) File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 85. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in _insert 1079. return query.get_compiler(using=3Dusing).execute_sql(return_id) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py" in execute_sql 1112. cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py" in __exit__ 94. six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python3/dist-packages/django/utils/six.py" in reraise 685. raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 64. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 101. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 250. self.errorhandler(self, exc, value) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in defaulterrorhandler 50. raise errorvalue File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 247. res =3D self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 411. rowcount =3D self._do_query(q) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _do_query 374. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 292. _mysql.connection.query(self, query) Exception Type: OperationalError at /hyperkitty/api/mailman/archive Exception Value: (1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column `mailman3web`.`hyperkitty_email`.`subject` at row 1") Request information: USER: AnonymousUser Has anyone a idea what went wrong or howto fix it? MfG, Lars Schimmer --=20 ------------------------------------------------------------- TU Graz, Institut f=C3=BCr ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 --===============2249086194896132290== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlGMEVBUkVDQUIwV0lRUjB3eGtKUm1hbVk5 a3JZN0daYUc0VFNwc1hJd1VDWFVxZ2VnQUtDUkNaYUc0VFNwc1gKSTBaeEFKNG16dDM2WlRFeEFI eXM5ZnN1ZjVwUXppbzVQUUNmUklzTkgwdU94UFFKSTRCZkhFM1FkNVVFWjZrPQo9U2tSLwotLS0t LUVORCBQR1AgU0lHTkFUVVJFLS0tLS0K --===============2249086194896132290==-- From post+mm3-users@guelker.eu Wed Aug 7 10:49:34 2019 From: Marvin =?utf-8?q?G=C3=BClker?= To: mailman-users@mailman3.org Subject: [MM3-users] Re: Error in mailman3 debian package, python error Date: Wed, 07 Aug 2019 12:49:27 +0200 Message-ID: <20190807104927.ou3qj2df2oy73ma2@atlantis> In-Reply-To: <784eba29-c9c0-2b9f-dffa-c186e15f1af5@cgv.tugraz.at> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3391474515461571526==" --===============3391474515461571526== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am 07. August 2019 um 11:57 Uhr +0200 schrieb Lars Schimmer: > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column > `mailman3web`.`hyperkitty_email`.`subject` at row 1") > > [...] > Has anyone a idea what went wrong or howto fix it? U+1F34E RED APPLE (which is what the string value above evaluates to in UTF-8) is not a valid e-mail address. If you didn't create user accounts via another way than the Hyperkitty UI, this looks like a bug in Hyperkitty's e-mail validator to me. Such a value should never have entered the database. Maybe you can delete the user with that "e-mail address" with your DB's command line tool. Marvin -- Blog: https://mg.guelker.eu --===============3391474515461571526==-- From phil@riverbankcomputing.com Wed Aug 7 15:40:27 2019 From: Phil Thompson To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty 403 Forbidden Error Date: Wed, 07 Aug 2019 16:40:21 +0100 Message-ID: In-Reply-To: <966f5e06f9fc4ee34e431382d0d57a4e@riverbankcomputing.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3199137702935107637==" --===============3199137702935107637== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 06/08/2019 09:48, Phil Thompson wrote: > On 06/08/2019 03:38, Abhilash Raj wrote: >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >>> I'm in the process of setting up mailman3. The only problem I seem to=20 >>> be >>> having is getting Hyperkitty to archive messages. Rather than the >>> authorisation problems people have previously asked about on the=20 >>> list, I >>> am getting a 403 error... >>>=20 >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >>> Forbidden >>>

Access is forbidden

(403) >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >>> Forbidden >>>

Access is forbidden

(403) >>>=20 >>> Any suggestions would be appreciated. >>=20 >> How did you install Hyperkitty? >=20 > On Ubuntu... >=20 > apt-get install mailman3-full >=20 >> You probably need to the set the API key correctly in both Core and=20 >> Hyperkitty. >>=20 >> Have you looked at documentation here[1]? >>=20 >> [1]: >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mai= lman >>=20 >> Note that the MAILMAN_ARCHIVER_KEY =3D "value" (this value should be in >> quotes, single or double, doesn't matter) in your settings.py for Web >> (Django) should be same as the `api_key : value` (without quotes here >> in hyperkitty.cfg config file). >=20 > That's all correct. I'm familiar with the authorisation issues that > other people have had. >=20 > The only thing I'm doing differently (as far as I am aware) is that > I'm using a URL prefixed with /mailman3 which is stripped off in my > nginx configuration... >=20 > # mailman3. > location /mailman3/ { > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > include uwsgi_params; > uwsgi_param SERVER_ADDR $server_addr; > uwsgi_modifier1 30; > uwsgi_param SCRIPT_NAME /mailman3; > } >=20 > location /mailman3/static { > alias /var/lib/mailman3/web/static; > } >=20 > location /mailman3/static/favicon.ico { > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > } >=20 > ...but I don't see this affecting the mailman to Hyperkitty > communication. Posting to lists and the Postorius and Hyperkitty > frontends seem to work fine. I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my=20 public IP address). However I now get a 400 Bad Request error. I have traced this to the archive() function in=20 hyperkitty/views/mailman.py which is expect a POST but is actually=20 getting a GET, specifically... GET '/mailman3/hyperkitty/api/mailman/archive?key=3D...' ...which seems to be a fairly fundamental problem. Again, any suggestions would be welcome. Phil --===============3199137702935107637==-- From maztec@gmail.com Wed Aug 7 15:52:20 2019 From: maztec@gmail.com To: mailman-users@mailman3.org Subject: [MM3-users] MM3 + Postfix + Dovecot + PostfixAdmin Date: Tue, 06 Aug 2019 08:50:53 +0000 Message-ID: <156508145338.8465.4537914225455966427@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4990977298370284289==" --===============4990977298370284289== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable System: Debian Buster Install: Functioning Postfix w/ Dovecot using PostfixAdmin for virtual domai= n and mailbox management Definitions: Host.TLD =3D my server's domain name; List.TLD =3D listserv's d= omain name; ListName =3D list's name. Issue: Postfix LMTP does not pass messages onto MM3:LMTP. Instead the behavi= or summary is as follows: =20 postfix/lmtp[...]: ###: to=3D, orig_to= =3D, relay=3DHost.TLD[private/dovecot-lm= tp], delay=3D439, delays=3D439/0.03/0.01/0.01, dsn=3D5.1.1, status=3Dbounced = (host Host.TLD[private/dovecot-lmtp] said: 550 5.1.1 <"mailman3:[127.0.0.1]:8= 024"@Host.TLD> User doesn't exist: mailman3:[127.0.0.1]:8024(a)Host.TLD (in r= eply to RCPT TO command)) The problem appears to be that Postfix defaults the relay to being private/do= vecot-lmtp and not the general lmtp protocol or the mailman3 dedicated lmtp p= rotocol. ---------------------------------------- ---------------------------------------- Details: # cat /proc/version Linux version 4.19.0-5-amd64 (debian-kernel(a)lists.debian.org) (gcc version = 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.37-5+deb10u1 (2019-07-19) ---------------------------------------- # postconf -n alias_database =3D hash:/etc/aliases alias_maps =3D hash:/etc/aliases append_dot_mydomain =3D no biff =3D no broken_sasl_auth_clients =3D yes compatibility_level =3D 2 debug_peer_level =3D 4 html_directory =3D /usr/share/doc/postfix/html inet_interfaces =3D all inet_protocols =3D ipv4 local_recipient_maps =3D $virtual_mailbox_maps,regexp:/var/lib/mailman3/data/= postfix_lmtp local_transport =3D virtual mailbox_size_limit =3D 0 mydestination =3D localhost myhostname =3D rijr.com mynetworks =3D 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin =3D /etc/mailname owner_request_special =3D no policy-spf_time_limit =3D 3600s readme_directory =3D /usr/share/doc/postfix recipient_delimiter =3D + relay_domains =3D $mydestination,regexp:/var/lib/mailman3/data/postfix_domains relayhost =3D smtp_tls_loglevel =3D 1 smtp_tls_security_level =3D may smtp_tls_session_cache_database =3D btree:${data_directory}/smtp_scache smtpd_banner =3D $myhostname ESMTP $mail_name (Debian/GNU) smtpd_recipient_restrictions =3D permit_mynetworks, permit_sasl_authenticated= , reject_unauth_destination smtpd_relay_restrictions =3D permit_mynetworks, permit_sasl_authenticated, re= ject_unauth_destination smtpd_sasl_auth_enable =3D yes smtpd_sasl_local_domain =3D $mydomain smtpd_sasl_path =3D private/auth smtpd_sasl_security_options =3D noanonymous smtpd_sasl_tls_security_options =3D $smtpd_sasl_security_options smtpd_sasl_type =3D dovecot smtpd_tls_auth_only =3D yes smtpd_tls_cert_file =3D /etc/ssl/private/vmail.crt smtpd_tls_key_file =3D /etc/ssl/private/vmail.key smtpd_tls_loglevel =3D 1 smtpd_tls_received_header =3D yes smtpd_tls_security_level =3D may smtpd_tls_session_cache_database =3D btree:${data_directory}/smtpd_scache smtpd_use_tls =3D yes transport_maps =3D hash:/etc/postfix/transport,regexp:/var/lib/mailman3/data/= postfix_lmtp virtual_alias_domains =3D proxy:mysql:/etc/postfix/virtual_alias_domains.cf virtual_alias_maps =3D proxy:mysql:/etc/postfix/virtual_alias_maps.cf,proxy:m= ysql:/etc/postfix/virtual_alias_domains_maps.cf,regexp:/var/lib/mailman3/data= /postfix_lmtp virtual_gid_maps =3D static:5000 virtual_mailbox_base =3D /home/vmail virtual_mailbox_domains =3D proxy:mysql:/etc/postfix/virtual_mailbox_domains.= cf virtual_mailbox_limit =3D 512000000 virtual_mailbox_maps =3D regexp:/var/lib/mailman3/data/postfix_lmtp,proxy:mys= ql:/etc/postfix/virtual_mailbox_maps.cf virtual_minimum_uid =3D 5000 virtual_transport =3D lmtp:unix:private/dovecot-lmtp virtual_uid_maps =3D static:5000 # cat master.cf [grep'd for lmtp and mailman3] lmtp unix - - y - - lmtp mailman3 unix - - - - - lmtp -o lmtp_send_xforward_command=3Dyes -o disable_dns_lookups=3Dyes ---------------------------------------- # cat mailman.cfg [mta section only] [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 lmtp_host: 127.0.0.1 lmtp_port: 8024 configuration: /etc/mailman3/postfix-mailman.cfg ---------------------------------------- # cat /var/lib/mailman3/data/postfix_lmtp # AUTOMATICALLY GENERATED BY MAILMAN ON 2019-08-06 06:39:21 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Aliases which are visible only in the @List.TLD domain. /^List(a)List\.TLD$/ mailman3:[127.0.0.1]:8024 /^List-bounces(\+.*)?@List\.TLD$/ mailman3:[127.0.0.1]:8024 /^List-confirm(\+.*)?@List\.TLD$/ mailman3:[127.0.0.1]:8024 /^List-join(a)List\.TLD$/ mailman3:[127.0.0.1]:8024 /^List-leave(a)List\.TLD$/ mailman3:[127.0.0.1]:8024 /^List-owner(a)List\.TLD$/ mailman3:[127.0.0.1]:8024 /^List-request(a)List\.TLD$/ mailman3:[127.0.0.1]:8024 /^List-subscribe(a)List\.TLD$/ mailman3:[127.0.0.1]:8024 /^List-unsubscribe(a)List\.TLD$/ mailman3:[127.0.0.1]:8024 ---------------------------------------- # cat postfix-mailman.cfg [postfix] # if I don't have postmap_command set, mailman errors out, even though transp= ort_file_type is regex. postmap_command: /usr/sbin/postmap transport_file_type: regex ---------------------------------------- # cat mail.debug =20 Aug 6 01:03:28 Host dovecot: lmtp(23055): Connect from local Aug 6 01:03:28 Host dovecot: auth: Debug: master in: USER#0112#011mailman3:[= 127.0.0.1]:8024(a)Host.TLD#011service=3Dlmtp Aug 6 01:03:28 Host dovecot: auth: userdb(?): Username character disallowed = by auth_username_chars: 0x3a (username: mailman3:[127.0.0.1]:8024(a)Host.TLD) Aug 6 01:03:28 Host dovecot: auth: Debug: userdb out: NOTFOUND#0112 Aug 6 01:03:28 Host postfix/cleanup[22970]: 2937FB0: message-id=3D<201908060= 80328.2937FB0(a)rijr.com> Aug 6 01:03:28 Host postfix/lmtp[23054]: CA030AA: to=3D, orig_to=3D, relay=3DHost.TLD[private/dovecot-lmtp], delay=3D43= 9, delays=3D439/0.03/0.01/0.01, dsn=3D5.1.1, status=3Dbounced (host Host.TLD[= private/dovecot-lmtp] said: 550 5.1.1 <"mailman3:[127.0.0.1]:8024"@Host.TLD> = User doesn't exist: mailman3:[127.0.0.1]:8024(a)Host.TLD (in reply to RCPT TO= command)) Aug 6 01:03:28 Host dovecot: lmtp(23050): Disconnect from local: Client has = quit the connection (state=3DREADY) Aug 6 01:03:28 Host postfix/lmtp[22981]: C0EEEA8: to=3D, orig_to=3D, relay=3DHost.TLD[private/dovecot-lmtp], delay=3D566, = delays=3D566/0.04/0.01/0.01, dsn=3D5.1.1, status=3Dbounced (host Host.com[pri= vate/dovecot-lmtp] said: 550 5.1.1 <"mailman3:[127.0.0.1]:8024"@Host.TLD> Use= r doesn't exist: mailman3:[127.0.0.1]:8024(a)Host.TLD (in reply to RCPT TO co= mmand)) ---------------------------------------- I have played with dozens of variations on the configuration files and tracin= g what is going on. The only reason I see that relay=3DHost.TLD[private/dove= cot-lmtp] is because of:=20 virtual_transport =3D lmtp:unix:private/dovecot-lmtp =20 Hopefully I can get this figured out .... - Jay --===============4990977298370284289==-- From maxking@asynchronous.in Wed Aug 7 16:04:08 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty 403 Forbidden Error Date: Wed, 07 Aug 2019 09:04:03 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7912959294798925508==" --===============7912959294798925508== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: > On 06/08/2019 09:48, Phil Thompson wrote: > > On 06/08/2019 03:38, Abhilash Raj wrote: > >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: > >>> I'm in the process of setting up mailman3. The only problem I seem to=20 > >>> be > >>> having is getting Hyperkitty to archive messages. Rather than the > >>> authorisation problems people have previously asked about on the=20 > >>> list, I > >>> am getting a 403 error... > >>>=20 > >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on > >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: > >>> Forbidden > >>>

Access is forbidden

(403) > >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on > >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: > >>> Forbidden > >>>

Access is forbidden

(403) > >>>=20 > >>> Any suggestions would be appreciated. > >>=20 > >> How did you install Hyperkitty? > >=20 > > On Ubuntu... > >=20 > > apt-get install mailman3-full > >=20 > >> You probably need to the set the API key correctly in both Core and=20 > >> Hyperkitty. > >>=20 > >> Have you looked at documentation here[1]? > >>=20 > >> [1]: > >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-m= ailman > >>=20 > >> Note that the MAILMAN_ARCHIVER_KEY =3D "value" (this value should be in > >> quotes, single or double, doesn't matter) in your settings.py for Web > >> (Django) should be same as the `api_key : value` (without quotes here > >> in hyperkitty.cfg config file). > >=20 > > That's all correct. I'm familiar with the authorisation issues that > > other people have had. > >=20 > > The only thing I'm doing differently (as far as I am aware) is that > > I'm using a URL prefixed with /mailman3 which is stripped off in my > > nginx configuration... > >=20 > > # mailman3. > > location /mailman3/ { > > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > > include uwsgi_params; > > uwsgi_param SERVER_ADDR $server_addr; > > uwsgi_modifier1 30; > > uwsgi_param SCRIPT_NAME /mailman3; > > } > >=20 > > location /mailman3/static { > > alias /var/lib/mailman3/web/static; > > } > >=20 > > location /mailman3/static/favicon.ico { > > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > > } > >=20 > > ...but I don't see this affecting the mailman to Hyperkitty > > communication. Posting to lists and the Postorius and Hyperkitty > > frontends seem to work fine. >=20 > I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my=20 > public IP address). However I now get a 400 Bad Request error. >=20 > I have traced this to the archive() function in=20 > hyperkitty/views/mailman.py which is expect a POST but is actually=20 > getting a GET, specifically... >=20 > GET '/mailman3/hyperkitty/api/mailman/archive?key=3D...' >=20 > ...which seems to be a fairly fundamental problem. >=20 > Again, any suggestions would be welcome. It should be sending POST request to archive emails[1]. How did you grab the = above request? Was it from logs? Do you have anything else in the logs? There should be something in the Mailm= an Core or web logs should have something. [1]: https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman_hyperk= itty/__init__.py#L198 --=20 thanks, Abhilash Raj (maxking) --===============7912959294798925508==-- From phil@riverbankcomputing.com Wed Aug 7 16:49:36 2019 From: Phil Thompson To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty 403 Forbidden Error Date: Wed, 07 Aug 2019 17:49:28 +0100 Message-ID: <23d8e5e8ecd0099753410ed1f8c46271@riverbankcomputing.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0332926925250535163==" --===============0332926925250535163== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 07/08/2019 17:04, Abhilash Raj wrote: > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: >> On 06/08/2019 09:48, Phil Thompson wrote: >> > On 06/08/2019 03:38, Abhilash Raj wrote: >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >> >>> I'm in the process of setting up mailman3. The only problem I seem to >> >>> be >> >>> having is getting Hyperkitty to archive messages. Rather than the >> >>> authorisation problems people have previously asked about on the >> >>> list, I >> >>> am getting a 403 error... >> >>> >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >> >>> Forbidden >> >>>

Access is forbidden

(403) >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >> >>> Forbidden >> >>>

Access is forbidden

(403) >> >>> >> >>> Any suggestions would be appreciated. >> >> >> >> How did you install Hyperkitty? >> > >> > On Ubuntu... >> > >> > apt-get install mailman3-full >> > >> >> You probably need to the set the API key correctly in both Core and >> >> Hyperkitty. >> >> >> >> Have you looked at documentation here[1]? >> >> >> >> [1]: >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-= mailman >> >> >> >> Note that the MAILMAN_ARCHIVER_KEY =3D "value" (this value should be in >> >> quotes, single or double, doesn't matter) in your settings.py for Web >> >> (Django) should be same as the `api_key : value` (without quotes here >> >> in hyperkitty.cfg config file). >> > >> > That's all correct. I'm familiar with the authorisation issues that >> > other people have had. >> > >> > The only thing I'm doing differently (as far as I am aware) is that >> > I'm using a URL prefixed with /mailman3 which is stripped off in my >> > nginx configuration... >> > >> > # mailman3. >> > location /mailman3/ { >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; >> > include uwsgi_params; >> > uwsgi_param SERVER_ADDR $server_addr; >> > uwsgi_modifier1 30; >> > uwsgi_param SCRIPT_NAME /mailman3; >> > } >> > >> > location /mailman3/static { >> > alias /var/lib/mailman3/web/static; >> > } >> > >> > location /mailman3/static/favicon.ico { >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; >> > } >> > >> > ...but I don't see this affecting the mailman to Hyperkitty >> > communication. Posting to lists and the Postorius and Hyperkitty >> > frontends seem to work fine. >>=20 >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my >> public IP address). However I now get a 400 Bad Request error. >>=20 >> I have traced this to the archive() function in >> hyperkitty/views/mailman.py which is expect a POST but is actually >> getting a GET, specifically... >>=20 >> GET '/mailman3/hyperkitty/api/mailman/archive?key=3D...' >>=20 >> ...which seems to be a fairly fundamental problem. >>=20 >> Again, any suggestions would be welcome. >=20 > It should be sending POST request to archive emails[1]. How did you > grab the above request? Was it from logs? Yes, I added DEBUG=3DTrue in mailman-web.py and captured the HTML from=20 mailman.log. > Do you have anything else in the logs? There should be something in > the Mailman Core or web logs should have something. There's nothing useful in the core log. There are 3 preceding entries in the web log... GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&key=3D... GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&msgid=3D...&key=3D... GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&msgid=3D...&key=3D... There is one item in the spool directory. These were all (apparently) successful. It seems odd that the last two=20 entries were identical. Phil --===============0332926925250535163==-- From maxking@asynchronous.in Thu Aug 8 01:12:03 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty 403 Forbidden Error Date: Wed, 07 Aug 2019 18:11:54 -0700 Message-ID: In-Reply-To: <23d8e5e8ecd0099753410ed1f8c46271@riverbankcomputing.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3597505443964313920==" --===============3597505443964313920== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Wed, Aug 7, 2019, at 9:49 AM, Phil Thompson wrote: > On 07/08/2019 17:04, Abhilash Raj wrote: > > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: > >> On 06/08/2019 09:48, Phil Thompson wrote: > >> > On 06/08/2019 03:38, Abhilash Raj wrote: > >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: > >> >>> I'm in the process of setting up mailman3. The only problem I seem to > >> >>> be > >> >>> having is getting Hyperkitty to archive messages. Rather than the > >> >>> authorisation problems people have previously asked about on the > >> >>> list, I > >> >>> am getting a 403 error... > >> >>> > >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on > >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: > >> >>> Forbidden > >> >>>

Access is forbidden

(403) > >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on > >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: > >> >>> Forbidden > >> >>>

Access is forbidden

(403) > >> >>> > >> >>> Any suggestions would be appreciated. > >> >> > >> >> How did you install Hyperkitty? > >> > > >> > On Ubuntu... > >> > > >> > apt-get install mailman3-full > >> > > >> >> You probably need to the set the API key correctly in both Core and > >> >> Hyperkitty. > >> >> > >> >> Have you looked at documentation here[1]? > >> >> > >> >> [1]: > >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-t= o-mailman > >> >> > >> >> Note that the MAILMAN_ARCHIVER_KEY =3D "value" (this value should be = in > >> >> quotes, single or double, doesn't matter) in your settings.py for Web > >> >> (Django) should be same as the `api_key : value` (without quotes here > >> >> in hyperkitty.cfg config file). > >> > > >> > That's all correct. I'm familiar with the authorisation issues that > >> > other people have had. > >> > > >> > The only thing I'm doing differently (as far as I am aware) is that > >> > I'm using a URL prefixed with /mailman3 which is stripped off in my > >> > nginx configuration... > >> > > >> > # mailman3. > >> > location /mailman3/ { > >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > >> > include uwsgi_params; > >> > uwsgi_param SERVER_ADDR $server_addr; > >> > uwsgi_modifier1 30; > >> > uwsgi_param SCRIPT_NAME /mailman3; > >> > } > >> > > >> > location /mailman3/static { > >> > alias /var/lib/mailman3/web/static; > >> > } > >> > > >> > location /mailman3/static/favicon.ico { > >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > >> > } > >> > > >> > ...but I don't see this affecting the mailman to Hyperkitty > >> > communication. Posting to lists and the Postorius and Hyperkitty > >> > frontends seem to work fine. > >>=20 > >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my > >> public IP address). However I now get a 400 Bad Request error. > >>=20 > >> I have traced this to the archive() function in > >> hyperkitty/views/mailman.py which is expect a POST but is actually > >> getting a GET, specifically... > >>=20 > >> GET '/mailman3/hyperkitty/api/mailman/archive?key=3D...' > >>=20 > >> ...which seems to be a fairly fundamental problem. > >>=20 > >> Again, any suggestions would be welcome. > >=20 > > It should be sending POST request to archive emails[1]. How did you > > grab the above request? Was it from logs? >=20 > Yes, I added DEBUG=3DTrue in mailman-web.py and captured the HTML from=20 > mailman.log. DEBUG=3DTrue doesn't print anything more useful around the 400 error response? >=20 > > Do you have anything else in the logs? There should be something in > > the Mailman Core or web logs should have something. >=20 > There's nothing useful in the core log. >=20 > There are 3 preceding entries in the web log... >=20 > GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&key=3D... > GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&msgid=3D...&key=3D... > GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&msgid=3D...&key=3D... >=20 > There is one item in the spool directory. >=20 > These were all (apparently) successful. It seems odd that the last two=20 > entries were identical. The only other thing that I can think of is, ALLOWED_HOSTS. What settings do = you have in your ALLOWED_HOSTS in settings.py for Django? You need to have 'localhost' or whatever is the value of the "Host" in the "b= ase_url" in your hyperkitty.cfg file in Mailman Core. I am not sure what is t= he default value in Ubuntu system. If you don't know, you can debug by adding a '*' in your ALLOWED_HOSTS and se= e if the problem goes away, this will bypass the Host header check. --=20 thanks, Abhilash Raj (maxking) --===============3597505443964313920==-- From maxking@asynchronous.in Thu Aug 8 01:20:05 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Error in mailman3 debian package, python error Date: Wed, 07 Aug 2019 18:19:57 -0700 Message-ID: <86e60c48-12e5-4ce9-9592-c7c96a708d77@www.fastmail.com> In-Reply-To: <20190807104927.ou3qj2df2oy73ma2@atlantis> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0977219786179041263==" --===============0977219786179041263== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Wed, Aug 7, 2019, at 3:50 AM, Marvin G=C3=BClker wrote: > Am 07. August 2019 um 11:57 Uhr +0200 schrieb Lars Schimmer: > > OperationalError at /hyperkitty/api/mailman/archive > > (1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column > > `mailman3web`.`hyperkitty_email`.`subject` at row 1") > > > > [...] > > Has anyone a idea what went wrong or howto fix it? >=20 > U+1F34E RED APPLE (which is what the string value above evaluates to in > UTF-8) is not a valid e-mail address. If you didn't create user accounts > via another way than the Hyperkitty UI, this looks like a bug in > Hyperkitty's e-mail validator to me. Such a value should never have > entered the database. It is not in the database, the exception originates from Mailman Core trying = to archive a message coming from this sender and Hyperkitty failing to archiv= e the message.=20 This should have been handled properly and a better exception message should = have been raised instead of this error traceback.=20 Can you open a bug report about this Hyperkitty's issue tracker? https://gitlab.com/mailman/hyperkitty/issues > Maybe you can delete the user with that "e-mail address" with your DB's > command line tool. >=20 > Marvin >=20 > --=20 > Blog: https://mg.guelker.eu > _______________________________________________ > 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/ > --=20 thanks, Abhilash Raj (maxking) --===============0977219786179041263==-- From phil@riverbankcomputing.com Thu Aug 8 08:21:17 2019 From: Phil Thompson To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty 403 Forbidden Error Date: Thu, 08 Aug 2019 09:21:10 +0100 Message-ID: <7b3d2697d70a4a5c85a1c7e08f622968@riverbankcomputing.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2194786653507285565==" --===============2194786653507285565== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 08/08/2019 02:11, Abhilash Raj wrote: > On Wed, Aug 7, 2019, at 9:49 AM, Phil Thompson wrote: >> On 07/08/2019 17:04, Abhilash Raj wrote: >> > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: >> >> On 06/08/2019 09:48, Phil Thompson wrote: >> >> > On 06/08/2019 03:38, Abhilash Raj wrote: >> >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >> >> >>> I'm in the process of setting up mailman3. The only problem I seem = to >> >> >>> be >> >> >>> having is getting Hyperkitty to archive messages. Rather than the >> >> >>> authorisation problems people have previously asked about on the >> >> >>> list, I >> >> >>> am getting a 403 error... >> >> >>> >> >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >> >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >> >> >>> Forbidden >> >> >>>

Access is forbidden

(403) >> >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >> >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >> >> >>> Forbidden >> >> >>>

Access is forbidden

(403) >> >> >>> >> >> >>> Any suggestions would be appreciated. >> >> >> >> >> >> How did you install Hyperkitty? >> >> > >> >> > On Ubuntu... >> >> > >> >> > apt-get install mailman3-full >> >> > >> >> >> You probably need to the set the API key correctly in both Core and >> >> >> Hyperkitty. >> >> >> >> >> >> Have you looked at documentation here[1]? >> >> >> >> >> >> [1]: >> >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-= to-mailman >> >> >> >> >> >> Note that the MAILMAN_ARCHIVER_KEY =3D "value" (this value should be= in >> >> >> quotes, single or double, doesn't matter) in your settings.py for Web >> >> >> (Django) should be same as the `api_key : value` (without quotes here >> >> >> in hyperkitty.cfg config file). >> >> > >> >> > That's all correct. I'm familiar with the authorisation issues that >> >> > other people have had. >> >> > >> >> > The only thing I'm doing differently (as far as I am aware) is that >> >> > I'm using a URL prefixed with /mailman3 which is stripped off in my >> >> > nginx configuration... >> >> > >> >> > # mailman3. >> >> > location /mailman3/ { >> >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; >> >> > include uwsgi_params; >> >> > uwsgi_param SERVER_ADDR $server_addr; >> >> > uwsgi_modifier1 30; >> >> > uwsgi_param SCRIPT_NAME /mailman3; >> >> > } >> >> > >> >> > location /mailman3/static { >> >> > alias /var/lib/mailman3/web/static; >> >> > } >> >> > >> >> > location /mailman3/static/favicon.ico { >> >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; >> >> > } >> >> > >> >> > ...but I don't see this affecting the mailman to Hyperkitty >> >> > communication. Posting to lists and the Postorius and Hyperkitty >> >> > frontends seem to work fine. >> >> >> >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my >> >> public IP address). However I now get a 400 Bad Request error. >> >> >> >> I have traced this to the archive() function in >> >> hyperkitty/views/mailman.py which is expect a POST but is actually >> >> getting a GET, specifically... >> >> >> >> GET '/mailman3/hyperkitty/api/mailman/archive?key=3D...' >> >> >> >> ...which seems to be a fairly fundamental problem. >> >> >> >> Again, any suggestions would be welcome. >> > >> > It should be sending POST request to archive emails[1]. How did you >> > grab the above request? Was it from logs? >>=20 >> Yes, I added DEBUG=3DTrue in mailman-web.py and captured the HTML from >> mailman.log. >=20 > DEBUG=3DTrue doesn't print anything more useful around the 400 error=20 > response? It prints the usual Django debug html, including the Python traceback,=20 which is how I knew which line of code was raising the 400 error. >> > Do you have anything else in the logs? There should be something in >> > the Mailman Core or web logs should have something. >>=20 >> There's nothing useful in the core log. >>=20 >> There are 3 preceding entries in the web log... >>=20 >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&key=3D... >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&msgid=3D...&key=3D... >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=3D...&msgid=3D...&key=3D... >>=20 >> There is one item in the spool directory. >>=20 >> These were all (apparently) successful. It seems odd that the last two >> entries were identical. >=20 > The only other thing that I can think of is, ALLOWED_HOSTS. What > settings do you have in your ALLOWED_HOSTS in settings.py for Django? >=20 > You need to have 'localhost' or whatever is the value of the "Host" in > the "base_url" in your hyperkitty.cfg file in Mailman Core. I am not > sure what is the default value in Ubuntu system. >=20 > If you don't know, you can debug by adding a '*' in your ALLOWED_HOSTS > and see if the problem goes away, this will bypass the Host header > check. ALLOWED_HOSTS is ['*']. Phil --===============2194786653507285565==-- From l.schimmer@cgv.tugraz.at Thu Aug 8 10:07:42 2019 From: Lars Schimmer To: mailman-users@mailman3.org Subject: [MM3-users] Re: Error in mailman3 debian package, python error Date: Thu, 08 Aug 2019 12:07:24 +0200 Message-ID: <52e7a9d3-38d9-986c-eb72-4a7fe69318c5@cgv.tugraz.at> In-Reply-To: <86e60c48-12e5-4ce9-9592-c7c96a708d77@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7230867442396506071==" --===============7230867442396506071== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 08.08.2019 03:19, Abhilash Raj wrote: > On Wed, Aug 7, 2019, at 3:50 AM, Marvin G=C3=BClker wrote: >> Am 07. August 2019 um 11:57 Uhr +0200 schrieb Lars Schimmer: >>> OperationalError at /hyperkitty/api/mailman/archive >>> (1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column >>> `mailman3web`.`hyperkitty_email`.`subject` at row 1") >>> >>> [...] >>> Has anyone a idea what went wrong or howto fix it? >> >> U+1F34E RED APPLE (which is what the string value above evaluates to in >> UTF-8) is not a valid e-mail address. If you didn't create user accounts >> via another way than the Hyperkitty UI, this looks like a bug in >> Hyperkitty's e-mail validator to me. Such a value should never have >> entered the database. >=20 > It is not in the database, the exception originates from Mailman Core tryin= g to archive a message coming from this sender and Hyperkitty failing to arch= ive the message.=20 >=20 > This should have been handled properly and a better exception message shoul= d have been raised instead of this error traceback.=20 >=20 > Can you open a bug report about this Hyperkitty's issue tracker? >=20 > https://gitlab.com/mailman/hyperkitty/issues It is issue #248 now. >> Maybe you can delete the user with that "e-mail address" with your DB's >> command line tool. >> >> Marvin >> >> --=20 >> Blog: https://mg.guelker.eu >> _______________________________________________ >> 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/ >> >=20 MfG, Lars Schimmer --=20 ------------------------------------------------------------- TU Graz, Institut f=C3=BCr ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 --===============7230867442396506071== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjIKCmlFWUVBUkVD QUFZRkFsMUw5RndBQ2drUW1XaHVFMHFiRnlQdXZBQ2ZRbnBQTmUvNzU3bjlYdS94TXNYb0RJWUYK RlFZQW5SZUVDamQ4Rk45bklEeHQzbEIyRTdOUWo1cGgKPXh0d24KLS0tLS1FTkQgUEdQIFNJR05B VFVSRS0tLS0tCg== --===============7230867442396506071==-- From l.schimmer@cgv.tugraz.at Thu Aug 8 10:09:33 2019 From: Lars Schimmer To: mailman-users@mailman3.org Subject: [MM3-users] Re: Error in mailman3 debian package, python error Date: Thu, 08 Aug 2019 12:09:15 +0200 Message-ID: <628e72ae-aac6-9385-ce99-f14840d5e88a@cgv.tugraz.at> In-Reply-To: <86e60c48-12e5-4ce9-9592-c7c96a708d77@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1346851132538987879==" --===============1346851132538987879== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 08.08.2019 03:19, Abhilash Raj wrote: > On Wed, Aug 7, 2019, at 3:50 AM, Marvin G=C3=BClker wrote: >> Am 07. August 2019 um 11:57 Uhr +0200 schrieb Lars Schimmer: >>> OperationalError at /hyperkitty/api/mailman/archive >>> (1366, "Incorrect string value: '\\xF0\\x9F\\x8D\\x8E' for column >>> `mailman3web`.`hyperkitty_email`.`subject` at row 1") >>> >>> [...] >>> Has anyone a idea what went wrong or howto fix it? >> >> U+1F34E RED APPLE (which is what the string value above evaluates to in >> UTF-8) is not a valid e-mail address. If you didn't create user accounts >> via another way than the Hyperkitty UI, this looks like a bug in >> Hyperkitty's e-mail validator to me. Such a value should never have >> entered the database. >=20 > It is not in the database, the exception originates from Mailman Core tryin= g to archive a message coming from this sender and Hyperkitty failing to arch= ive the message.=20 >=20 > This should have been handled properly and a better exception message shoul= d have been raised instead of this error traceback.=20 >=20 > Can you open a bug report about this Hyperkitty's issue tracker? >=20 > https://gitlab.com/mailman/hyperkitty/issues But, as it is not in the database, howto fix this? thank you. >> Maybe you can delete the user with that "e-mail address" with your DB's >> command line tool. >> >> Marvin >> >> --=20 >> Blog: https://mg.guelker.eu >> _______________________________________________ >> 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/ >> >=20 MfG, Lars Schimmer --=20 ------------------------------------------------------------- TU Graz, Institut f=C3=BCr ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 --===============1346851132538987879== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjIKCmlFWUVBUkVD QUFZRkFsMUw5TXNBQ2drUW1XaHVFMHFiRnlQdTB3Q2JCTks1VWlrU2pVb05CdmFHK2lTU0hoaloK Q1JjQW5qUk1taDZSMHNHVFZ5dUYxK3NWWTd1N1B1aEsKPTN2YWMKLS0tLS1FTkQgUEdQIFNJR05B VFVSRS0tLS0tCg== --===============1346851132538987879==-- From andrew.bernard@gmail.com Fri Aug 9 01:25:22 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Internal server error Date: Fri, 09 Aug 2019 01:25:19 +0000 Message-ID: <156531391936.8463.4884307168356731343@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3075338338329524980==" --===============3075338338329524980== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable My mailbox is filling up with dozens of notification of an internal server er= ror. i wont post the whole mail as it is long, but here is the top: Internal Server Error: /archives/list/jackrail-meta(a)jackrail.org/recent-thr= eads TypeError at /archives/list/jackrail-meta(a)jackrail.org/recent-threads 'datetime.date' object is not iterable Request Method: GET Request URL: https://list.jackrail.org/archives/list/jackrail-meta(a)jackrail= .org/recent-threads Django Version: 2.1.9 Python Executable: /opt/mailman/mm/venv/bin/uwsgi Python Version: 3.7.3 What is causing this? [Assuming that knowing the cause will lead to me fixing= it.] Andrew --===============3075338338329524980==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Fri Aug 9 05:14:18 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] Internal server error Date: Fri, 09 Aug 2019 14:14:10 +0900 Message-ID: <23885.290.845658.178501@turnbull.sk.tsukuba.ac.jp> In-Reply-To: <156531391936.8463.4884307168356731343@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2934337677221248184==" --===============2934337677221248184== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Andrew Bernard writes: > My mailbox is filling up with dozens of notification of an internal > server error. i wont post the whole mail as it is long, but here is > the top: > > Internal Server Error: > /archives/list/jackrail-meta(a)jackrail.org/recent-threads > > TypeError at /archives/list/jackrail-meta(a)jackrail.org/recent-threads > 'datetime.date' object is not iterable This is not your error, this a bug in Mailman (unlikely), Django (plausible), or some library Django uses. It could be a broken email, but that's still a validation bug somewhere in the Mailman stack. Googling "'datetime.date' object is not iterable django" suggests there may have been a Django or library bug in 2016 or so (I did *not* go past the blurbs Google returns). Without a backtrace, I can't identify this. If the "long" email is long because of the backtrace, please do post it. If not, set DEBUG=True in your config, restart Mailman long enough to get the message, find the backtrace in the message or log, and post that. If you're shy about posting long texts of uncertain value to the -users list (I understand the feeling), feel free to post to the GitLab issue tracker or mailman-developers(a)python.org. Steve --===============2934337677221248184==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Fri Aug 9 05:14:49 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] MM3 + Postfix + Dovecot + PostfixAdmin Date: Fri, 09 Aug 2019 14:14:44 +0900 Message-ID: <23885.324.622744.980600@turnbull.sk.tsukuba.ac.jp> In-Reply-To: <156508145338.8465.4537914225455966427@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8827193618991728219==" --===============8827193618991728219== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit maztec(a)gmail.com writes: > Issue: Postfix LMTP does not pass messages onto MM3:LMTP. I don't understand why this is a Mailman problem. Seems like Postfix user lists would be a better venue to get expert help with this. Among other things, our most responsive Postfix guy is out of cell coverage for now. I would post this To: the relevant Postfix list, Cc: this list, and set Reply-To and Mail-Followups-To to the Postfix list to get everybody who can contribute on the same page. If it is a Mailman problem, you have my apologies and I'm listening. Steve --===============8827193618991728219==-- From gazorg@gmail.com Sun Aug 11 19:42:52 2019 From: David Krantz To: mailman-users@mailman3.org Subject: [MM3-users] Question after upgrade to mm 3.2.3 and latest postorius Date: Sun, 11 Aug 2019 21:42:35 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6449201136583008575==" --===============6449201136583008575== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, I have just upgraded to mailman 3.2.3. My installation is from the git sources and I use two different venv:s, one for the web part as I did not want to compile the web server plugin to a newer python version than 3.5, and one venv for the rest running python 3.7. Apart from some missing dependencies and some changes that affected the django config I just have two issues with postorius: 1. The index page with all lists is not sorted in any useful way although it is based on something as the order seems to be stable. Prior to the upgrade the lists were sorted in alphabetical order after list name which is a lot more usable for me as admin. If I click the link at the bottom with "click to view all lists" I get the old behaviour. 2. The template menu simply does not work, it seems as if some database table is missing even after running migrations. Django logs the following: ERROR 2019-08-11 20:58:55,038 exception 11837 139756347221760 Internal Server Error: /mailman3/lists/TESTLIST/templates Traceback (most recent call last): File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) psycopg2.errors.UndefinedTable: relation "postorius_emailtemplate" does not exist LINE 1: ...ext", "postorius_emailtemplate"."identifier" FROM "postorius.. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/exception.py", line 35, in inner response =3D get_response(request) File "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", line 158, in _get_response response =3D self.process_exception_by_middleware(e, request) File "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", line 156, in _get_response response =3D response.render() File "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", line 106, in render self.content =3D self.rendered_content File "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", line 83, in rendered_content content =3D template.render(context, self._request) File "/...VENV3.5/lib/python3.5/site-packages/django/template/backends/django.py= ", line 61, in render return self.template.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 943, in render bit =3D node.render_annotated(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 910, in render_annotated return self.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", line 155, in render return compiled_parent._render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 943, in render bit =3D node.render_annotated(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 910, in render_annotated return self.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", line 67, in render result =3D block.nodelist.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 943, in render bit =3D node.render_annotated(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", line 910, in render_annotated return self.render(context) File "/...VENV3.5/lib/python3.5/site-packages/django/template/defaulttags.py", line 313, in render if match: File "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", line 276, in __bool__ self._fetch_all() File "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", line 1179, in _fetch_all self._result_cache =3D list(self._iterable_class(self)) File "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", line 54, in __iter__ results =3D compiler.execute_sql(chunked_fetch=3Dself.chunked_fetch, chunk_size=3Dself.chunk_size) File "/...VENV3.5/lib/python3.5/site-packages/django/db/models/sql/compiler.py", line 1063, in execute_sql cursor.execute(sql, params) File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 68, in execute return self._execute_with_wrappers(sql, params, many=3DFalse, executor=3Dself._execute) File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers return executor(sql, params, many, context) File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) File "/...VENV3.5/lib/python3.5/site-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", line 85, in _execute return self.cursor.execute(sql, params) django.db.utils.ProgrammingError: relation "postorius_emailtemplate" does not exist LINE 1: ...ext", "postorius_emailtemplate"."identifier" FROM "postorius... Cheers // David --===============6449201136583008575==-- From maxking@asynchronous.in Sun Aug 11 20:03:24 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Question after upgrade to mm 3.2.3 and latest postorius Date: Sun, 11 Aug 2019 13:03:07 -0700 Message-ID: <899e3e4f-81f6-4651-859e-f843fb0ed399@www.fastmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0455186402710893412==" --===============0455186402710893412== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sun, Aug 11, 2019, at 12:43 PM, David Krantz wrote: > Hi all, >=20 > I have just upgraded to mailman 3.2.3. My installation is from the git > sources and I use two different venv:s, one for the web part as I did > not want to compile the web server plugin to a newer python version > than 3.5, and one venv for the rest running python 3.7. Apart from > some missing dependencies and some changes that affected the django > config I just have two issues with postorius: I would recommend that you bump up to 3.7 for the web part too, mostly becaus= e 3.5 is now has been in security maintenance state for a while. We will drop= support for 3.5 after this next release (so you do have some time :), but I = fear there *could* potentially be other dependent libraries who might have dr= opped 3.5 support.=20 Even though we do run CI and we'd (hopefully) know when there is a dependent = library seriously breaking, but since we don't pin down versions, newer relea= ses can cause problems. The web-server plugin I assume is mod_wsgi?=20 If you use a separate wsgi server than the one embedded in web-server, you ca= n bump versions a bit more easily. gunicorn or uwsgi are recommended options.= Do note that the new version of Mailman Core also uses gunicorn now. >=20 > 1. The index page with all lists is not sorted in any useful way > although it is based on something as the order seems to be stable. > Prior to the upgrade the lists were sorted in alphabetical order after > list name which is a lot more usable for me as admin. If I click the > link at the bottom with "click to view all lists" I get the old > behaviour. This change was made so that you will see only the lists you are a member of = either as a subscriber, moderator or owner. This is default when you are logg= ed-in, but when logged-out, you will see the old view with all lists alphabet= ically sorted. > 2. The template menu simply does not work, it seems as if some > database table is missing even after running migrations.=20 Are you sure the migrations are there? I can see the following list on the la= test git master of Postorius (all the ones after 0004_ are related to emailte= mplate): ``` $ python manage.py showmigrations postorius [X] 0001_initial [X] 0002_auto_20160210_0721 [X] 0003_drop_addressconfirmationprofile [X] 0004_create_email_template [X] 0005_auto_20180707_1107 [X] 0006_auto_20180711_1359 [X] 0007_auto_20180712_0536 [X] 0008_auto_20190310_0717 [X] 0009_auto_20190508_1604 ``` > Django logs > the following: >=20 > ERROR 2019-08-11 20:58:55,038 exception 11837 139756347221760 Internal > Server Error: /mailman3/lists/TESTLIST/templates Traceback > (most recent call last): File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) > psycopg2.errors.UndefinedTable: relation "postorius_emailtemplate" > does not exist LINE 1: ...ext", "postorius_emailtemplate"."identifier" > FROM "postorius.. >=20 > The above exception was the direct cause of the following exception: >=20 > Traceback (most recent call last): File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/exception.p= y", > line 35, in inner response =3D get_response(request) File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", > line 158, in _get_response response =3D > self.process_exception_by_middleware(e, request) File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", > line 156, in _get_response response =3D response.render() File > "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", > line 106, in render self.content =3D self.rendered_content File > "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", > line 83, in rendered_content content =3D template.render(context, > self._request) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/backends/django.= py", > line 61, in render return self.template.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 175, in render return self._render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 167, in _render return self.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit =3D node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", > line 155, in render return compiled_parent._render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 167, in _render return self.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit =3D node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", > line 67, in render result =3D block.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit =3D node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/defaulttags.py", > line 313, in render if match: File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 276, in __bool__ self._fetch_all() File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 1179, in _fetch_all self._result_cache =3D > list(self._iterable_class(self)) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 54, in __iter__ results =3D > compiler.execute_sql(chunked_fetch=3Dself.chunked_fetch, > chunk_size=3Dself.chunk_size) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/sql/compiler.py= ", > line 1063, in execute_sql cursor.execute(sql, params) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 68, in execute return self._execute_with_wrappers(sql, params, > many=3DFalse, executor=3Dself._execute) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 77, in _execute_with_wrappers return executor(sql, params, > many, context) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/utils.py", line > 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from > exc_value File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) > django.db.utils.ProgrammingError: relation "postorius_emailtemplate" > does not exist LINE 1: ...ext", > "postorius_emailtemplate"."identifier" FROM "postorius... >=20 > Cheers > // David > _______________________________________________ > 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/ > --=20 thanks, Abhilash Raj (maxking) --===============0455186402710893412==-- From gazorg@gmail.com Sun Aug 11 21:49:03 2019 From: David Krantz To: mailman-users@mailman3.org Subject: [MM3-users] Re: Question after upgrade to mm 3.2.3 and latest postorius Date: Sun, 11 Aug 2019 23:48:48 +0200 Message-ID: In-Reply-To: <899e3e4f-81f6-4651-859e-f843fb0ed399@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6527198402525389815==" --===============6527198402525389815== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thank you for your quick reply! Comments below. On Sun, Aug 11, 2019 at 10:03 PM Abhilash Raj wro= te: > I would recommend that you bump up to 3.7 for the web part too, mostly beca= use 3.5 is now has been in security maintenance state for a while. We will dr= op support for 3.5 after this next release (so you do have some time :), but = I fear there *could* potentially be other dependent libraries who might have = dropped 3.5 support. > > Even though we do run CI and we'd (hopefully) know when there is a dependen= t library seriously breaking, but since we don't pin down versions, newer rel= eases can cause problems. > > The web-server plugin I assume is mod_wsgi? Good information. Of course it is mod_wsgi. > If you use a separate wsgi server than the one embedded in web-server, you = can bump versions a bit more easily. gunicorn or uwsgi are recommended option= s. Do note that the new version of Mailman Core also uses gunicorn now. That might be simpler although I probably still will have to use apache as passthrough as there are other things on that server using port 443 (80) and yet another server running is not what I'd like even if wsgi is a server process anyway as I understand it. I'll consider that and change it. > 1. The index page with all lists is not sorted in any useful way > > although it is based on something as the order seems to be stable. > > Prior to the upgrade the lists were sorted in alphabetical order after > > list name which is a lot more usable for me as admin. If I click the > > link at the bottom with "click to view all lists" I get the old > > behaviour. > > This change was made so that you will see only the lists you are a member o= f either as a subscriber, moderator or owner. This is default when you are lo= gged-in, but when logged-out, you will see the old view with all lists alphab= etically sorted. That is very good. It still is strange that this view is not sorted. > Are you sure the migrations are there? I can see the following list on the = latest git master of Postorius (all the ones after 0004_ are related to email= template): I thought so, but it seems as if they are not. That said I have not used django for anything else. After setting up the django-admin-script and modifying a few paths I got it to work correctly. The run I had made did not work although it also failed silently. Had I been used to django I'd known that it should print "OK" and ticked boxes for performed migrations, but I just use django for mailman-things. So now it works. Great. Thanks! // David --===============6527198402525389815==-- From maxking@asynchronous.in Sun Aug 11 22:18:39 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Question after upgrade to mm 3.2.3 and latest postorius Date: Sun, 11 Aug 2019 15:18:33 -0700 Message-ID: <7535c5c3-16bc-455e-90e9-ceaf9191522e@www.fastmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4590449470920400873==" --===============4590449470920400873== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sun, Aug 11, 2019, at 2:49 PM, David Krantz wrote: > Thank you for your quick reply! Comments below. >=20 > On Sun, Aug 11, 2019 at 10:03 PM Abhilash Raj w= rote: > > I would recommend that you bump up to 3.7 for the web part too, mostly be= cause 3.5 is now has been in security maintenance state for a while. We will = drop support for 3.5 after this next release (so you do have some time :), bu= t I fear there *could* potentially be other dependent libraries who might hav= e dropped 3.5 support. > > > > Even though we do run CI and we'd (hopefully) know when there is a depend= ent library seriously breaking, but since we don't pin down versions, newer r= eleases can cause problems. > > > > The web-server plugin I assume is mod_wsgi? >=20 > Good information. Of course it is mod_wsgi. >=20 > > If you use a separate wsgi server than the one embedded in web-server, yo= u can bump versions a bit more easily. gunicorn or uwsgi are recommended opti= ons. Do note that the new version of Mailman Core also uses gunicorn now. >=20 > That might be simpler although I probably still will have to use > apache as passthrough as there are other things on that server using > port 443 (80) and yet another server running is not what I'd like even > if wsgi is a server process anyway as I understand it. I'll consider > that and change it. Right, using a webserver for passthrough (and, serving static content) is act= ually recommended practice since they are more battle tested for security + l= oad than wsgi servers.=20 We use gunicorn + nginx for running this very list. >=20 > > 1. The index page with all lists is not sorted in any useful way > > > although it is based on something as the order seems to be stable. > > > Prior to the upgrade the lists were sorted in alphabetical order after > > > list name which is a lot more usable for me as admin. If I click the > > > link at the bottom with "click to view all lists" I get the old > > > behaviour. > > > > This change was made so that you will see only the lists you are a member= of either as a subscriber, moderator or owner. This is default when you are = logged-in, but when logged-out, you will see the old view with all lists alph= abetically sorted. >=20 > That is very good. It still is strange that this view is not sorted. Noted, thanks! https://gitlab.com/mailman/postorius/issues/379 >=20 > > Are you sure the migrations are there? I can see the following list on th= e latest git master of Postorius (all the ones after 0004_ are related to ema= iltemplate): >=20 > I thought so, but it seems as if they are not. That said I have not > used django for anything else. After setting up the > django-admin-script and modifying a few paths I got it to work > correctly. The run I had made did not work although it also failed > silently. Had I been used to django I'd known that it should print > "OK" and ticked boxes for performed migrations, but I just use django > for mailman-things. I would love to have some more time and sort out some minor annoyances with D= jango :(=20 This might be a great opportunity for someone with Django experience to help = make it easier, I have some ideas there which should already be in the issue = tracker. --=20 thanks, Abhilash Raj (maxking) --===============4590449470920400873==-- From gazorg@gmail.com Mon Aug 12 21:49:40 2019 From: David Krantz To: mailman-users@mailman3.org Subject: [MM3-users] ARC Date: Mon, 12 Aug 2019 23:49:24 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3190952809056062169==" --===============3190952809056062169== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, Is the documentation correct that ARC should be as simple to configure in mailman 3 as to add the private DKIM key and restarting mailman? (https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign.= html) I've tried that without finding any effect in my so far limited tests. I have not found anything in logs although I might have missed looking in one. Are there any known limitations? I have previously a working DKIM signature on outgoing mail as well as correctly set up SPF in DNS and SPF-checking on received mail. The verification on incoming mail adds a few headers but I do not think that that should be an issue, neither would the DKIM signing change anything should mailman add new headers. I now run Mailman 3.2.3 (La Villa Strangiato) on Python 3.7.4. Cheers // David --===============3190952809056062169==-- From mark@msapiro.net Tue Aug 13 01:16:45 2019 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: MM3 + Postfix + Dovecot + PostfixAdmin Date: Mon, 12 Aug 2019 18:16:34 -0700 Message-ID: <4af83837-4cfe-3d87-f3e7-a2c2be191d77@msapiro.net> In-Reply-To: <23885.324.622744.980600@turnbull.sk.tsukuba.ac.jp> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7721394655518913701==" --===============7721394655518913701== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 8/8/19 10:14 PM, Stephen J. Turnbull wrote: > maztec(a)gmail.com writes: > > > Issue: Postfix LMTP does not pass messages onto MM3:LMTP. > > I don't understand why this is a Mailman problem. Seems like Postfix > user lists would be a better venue to get expert help with this. > Among other things, our most responsive Postfix guy is out of cell > coverage for now. I have a window of availability - and it's longer than I thought because my second of three back-country trips has been canceled :( > I would post this To: the relevant Postfix list, Cc: this list, and > set Reply-To and Mail-Followups-To to the Postfix list to get > everybody who can contribute on the same page. I don't have much to add to what Steve has said except our recommended config includes transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp in Postfix main.cf. This should contain (per your log message) things like ListName-confirm(a)ListServer.TLD lmtp:[127.0.0.1]:8024 to tell Postfix to deliver that address via lmtp to port 8024 on the local host. Dovecot should not be involved. There is something in your config that trumps this and delivers via lmtp to Dovecot for mailman3:[127.0.0.1]:8024. Does your transport_maps look like the above or perhaps like ListName-confirm(a)ListServer.TLD mailman3:[127.0.0.1]:8024 If so, I don't know where mailman3 instead of lmtp: comes from. Also, even if it is lmtp: I don't know that Dovecot can deliver via lmtp. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============7721394655518913701==-- From l.schimmer@cgv.tugraz.at Tue Aug 13 08:59:45 2019 From: Lars Schimmer To: mailman-users@mailman3.org Subject: [MM3-users] task runjobs minutely uses 100% cpu Date: Tue, 13 Aug 2019 10:59:20 +0200 Message-ID: <65ee4cfd-22f9-c6d2-c720-587ae90925cc@cgv.tugraz.at> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3478352492213779376==" --===============3478352492213779376== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hi! Since we do run roughly 40 mailinglists on mailman3, the schedules/cronjob task python3 /usr/share/mailman3-web/manage.py runjobs minutely uses 1 CPU core 100% all the time. Any idea howto see why? debian mailma3n-full package 3.2.1-1 Mailman Core Version GNU Mailman 3.2.1 (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] MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 --===============3478352492213779376== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjIKCmlFWUVBUkVD QUFZRkFsMVNlK2dBQ2drUW1XaHVFMHFiRnlQZG9RQ1pBUU1lTUg0VVI1TGxFTlM2NVg1bFExeksK YkRZQW5pMVhRTlAvUkxtS0ZLbmJ5bGVUeXlRNWl6YlkKPXlGTGQKLS0tLS1FTkQgUEdQIFNJR05B VFVSRS0tLS0tCg== --===============3478352492213779376==-- From post+mm3-users@guelker.eu Tue Aug 13 12:04:26 2019 From: Marvin =?utf-8?q?G=C3=BClker?= To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Tue, 13 Aug 2019 14:04:16 +0200 Message-ID: <20190813120416.zdd2hu2uib52ymhc@atlantis> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3514287533362092655==" --===============3514287533362092655== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am 12. August 2019 um 23:49 Uhr +0200 schrieb David Krantz: > Is the documentation correct that ARC should be as simple to configure > in mailman 3 as to add the private DKIM key and restarting mailman? Do any large e-mail providers actually support ARC? Smaller ones like Fastmail appearently do at least semi-manually[1], but what about the relevant ones -- GMail, Microsoft, Yahoo (and in Germany, GMX et al.)? I infer from the spare results of searching for "ARC suport" that even with a perfectly set-up ARC infrastructure, the large e-mail providers are still going to reject DMARC-protected mailing list e-mail, because they simply don't support ARC. [1]: https://www.fastmail.com/help/technical/senderauthentication.html -- Blog: https://mg.guelker.eu --===============3514287533362092655==-- From mark@msapiro.net Tue Aug 13 12:42:23 2019 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Tue, 13 Aug 2019 05:42:11 -0700 Message-ID: <188e1253-2245-6cee-00f8-bd948005a39f@msapiro.net> In-Reply-To: <20190813120416.zdd2hu2uib52ymhc@atlantis> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4587375367037322292==" --===============4587375367037322292== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On 8/13/19 5:04 AM, Marvin Gülker wrote: > > Do any large e-mail providers actually support ARC? Smaller ones like > Fastmail appearently do at least semi-manually[1], but what about the > relevant ones -- GMail, Microsoft, Yahoo (and in Germany, GMX et al.)? Gmail does. The question is not whether they support ARC, but whether they will trust you. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============4587375367037322292==-- From maxking@asynchronous.in Tue Aug 13 15:42:46 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: task runjobs minutely uses 100% cpu Date: Tue, 13 Aug 2019 08:42:40 -0700 Message-ID: In-Reply-To: <65ee4cfd-22f9-c6d2-c720-587ae90925cc@cgv.tugraz.at> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2178890025463805549==" --===============2178890025463805549== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tue, Aug 13, 2019, at 2:00 AM, Lars Schimmer wrote: > Hi! >=20 > Since we do run roughly 40 mailinglists on mailman3, the > schedules/cronjob task > python3 /usr/share/mailman3-web/manage.py runjobs minutely uses 1 CPU > core 100% all the time. >=20 > Any idea howto see why? So, the minutely job updates the fulltext index, which uses a Python based in= dexing library called Whoosh. Whoosh is good for testing but doesn't work wel= l for prod environments at scale. There is a need to update the docs, but it would be great to move to a better= indexing engine like Xapian or ElasticSearch (which we have been using on th= is list for a while).=20 As a short-term fix, you can move the minutely cron job to run every 15minute= s or even 1 hour. The only delay you will see is that it will take new emails= upto 1hour to be indexed via search, which I don't think is a big deal. > debian mailma3n-full package 3.2.1-1 > Mailman Core Version GNU Mailman 3.2.1 (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] >=20 >=20 >=20 > MfG, > Lars Schimmer > --=20 > ------------------------------------------------------------- > TU Graz, Institut f=C3=BCr ComputerGraphik & WissensVisualisierung > Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at > Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 >=20 >=20 > _______________________________________________ > 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/ >=20 >=20 > *Attachments:* > * signature.asc -- thanks, Abhilash Raj (maxking) --===============2178890025463805549==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Tue Aug 13 15:53:51 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] Question after upgrade to mm 3.2.3 and latest postorius Date: Wed, 14 Aug 2019 00:53:44 +0900 Message-ID: <23890.56584.289283.855396@turnbull.sk.tsukuba.ac.jp> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8574890360346410626==" --===============8574890360346410626== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit David Krantz writes: > I have just upgraded to mailman 3.2.3. My installation is from the git > sources and I use two different venv:s, one for the web part as I did > not want to compile the web server plugin to a newer python version > than 3.5, I see elsewhere that this is mod_wsgi. I forget exactly what my story was, but I did recompile on Linux and it was straightforward. Of course there are a million reasons why you might not want to do that. I just wanted to take this chance to report that for 3.6 and 3.7 this was very straightforward, in case anybody else is thinking about doing it. --===============8574890360346410626==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Tue Aug 13 15:54:04 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] ARC Date: Wed, 14 Aug 2019 00:53:59 +0900 Message-ID: <23890.56599.36095.388727@turnbull.sk.tsukuba.ac.jp> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0686363952894703636==" --===============0686363952894703636== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable David Krantz writes: > Is the documentation correct that ARC should be as simple to configure > in mailman 3 as to add the private DKIM key and restarting mailman? > (https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_si= gn.html) You need to enable ARC by adding the ARC section to mailman.cfg and setting "enabled =3D yes" in it. I've submitted a pull request to update the documents. > I've tried that without finding any effect in my so far limited tests. What do you mean by "effect"? Is the "effect" that you're not seeing the presence of ARC header fields in outgoing mail? If so, you probably haven't set the enabled flag. If the effect you're looking for is that Google and several other participants in the ARC protocol accept your mail when they didn't before, you'll have to ask them about it. > I have not found anything in logs although I might have missed looking > in one. I don't recall that anything is logged by the module under normal circumstances, there may be some error logging. What would you expect to be logged? > Are there any known limitations? Of what kind? It's a simple protocol: if there is authentication information (DKIM or ARC) in the incoming message, validate it. Then package up the validation in the ARC-AR, ARC-Signature, and ARC-Seal fields. Those are the operations the module performs. Steve --=20 Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN --===============0686363952894703636==-- From post+mm3-users@guelker.eu Tue Aug 13 18:42:05 2019 From: Marvin =?utf-8?q?G=C3=BClker?= To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Tue, 13 Aug 2019 20:41:58 +0200 Message-ID: <20190813184158.ld5olllcid6vbozo@atlantis> In-Reply-To: <188e1253-2245-6cee-00f8-bd948005a39f@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5030126548084841311==" --===============5030126548084841311== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am 13. August 2019 um 05:42 Uhr -0700 schrieb Mark Sapiro: > The question is not whether they support ARC, but whether they will > trust you. Well. That's nothing new, given that GMail and Microsoft liberally reject e-mail from small providers for no reason anyway (I have experienced it myself). If this situation doesn't change with ARC, I can live with this (by paying for an SMTP relay provider that proxies my e-mail). However, I thought the entire point in ARC was fixing automatic rejections caused by DMARC invalidation by mailing lists, which are vital for so many open-source projects (including Mailman iself). If ARC falls short of solving that problem, because the large providers do not automatically trust ARC, then supporting ARC on my mailing list server is kind of void. Why should almighty Microsoft trust my small personal mailing list server? ARC can only achieve its goal with black-listing untrusted relays rather than white-listing known good ones, because it is simply unfeasable to manually maintain a list of all open-source project mailing lists in the entire world. I could set a new one up tomorrow, how should you know? -- Blog: https://mg.guelker.eu --===============5030126548084841311==-- From gazorg@gmail.com Wed Aug 14 14:23:38 2019 From: David Krantz To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Wed, 14 Aug 2019 16:23:20 +0200 Message-ID: In-Reply-To: <23890.56599.36095.388727@turnbull.sk.tsukuba.ac.jp> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6325059207740655483==" --===============6325059207740655483== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tue, Aug 13, 2019 at 5:54 PM Stephen J. Turnbull wrote: > You need to enable ARC by adding the ARC section to mailman.cfg and > setting "enabled =3D yes" in it. Aha! That was the missing config. Thank you! > What do you mean by "effect"? Is the "effect" that you're not seeing > the presence of ARC header fields in outgoing mail? If so, you > probably haven't set the enabled flag. No, I hadn't as it was not present in the documentation. Tested that and received a stacktrace where authres (of which I know nothing) throws an exception complaining on a syntax error when parsing the AuthenticationResultsHeader. It seems as if it requires an authserv-id field but the few examples of the AuthenticationResultsHeader I've looked at just starts with the server name followed by a semicolon, with no preceeding tag for that server name value. Aug 14 13:43:25 2019 (28958) ACCEPT: Aug 14 13:43:26 2019 (28962) Uncaught runner exception: Syntax error: Expected authserv-id at: ; dkim=3Dpass header.d=3Ddomain.tld; arc=3Dnone... Aug 14 13:43:26 2019 (28962) Traceback (most recent call last): File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/c= ore/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/c= ore/runner.py", line 266, in _process_one_file keepqueued =3D self._dispose(mlist, msg, msgdata) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/r= unners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/c= ore/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/h= andlers/arc_sign.py", line 71, in process sign(msg, msgdata) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/h= andlers/arc_sign.py", line 50, in sign standardize=3D('ARC-Standardize' in msgdata)) File "...VENV/lib/python3.7/site-packages/authheaders-0.11.0-py3.7.egg/auth= headers/__init__.py", line 256, in sign_message return ARC(msg, logger=3Dlogger).sign(selector, domain, privkey, srv_id, include_headers=3Dsig_headers, timestamp=3Dtimestamp, standardize=3Dstandardize) File "...VENV/lib/python3.7/site-packages/dkimpy-0.9.3-py3.7.egg/dkim/__ini= t__.py", line 953, in sign for res in ar_headers] File "...VENV/lib/python3.7/site-packages/dkimpy-0.9.3-py3.7.egg/dkim/__ini= t__.py", line 953, in for res in ar_headers] File "...VENV/lib/python3.7/site-packages/authres-1.2.0-py3.7.egg/authres/_= _init__.py", line 206, in parse return authres.core.AuthenticationResultsHeader.parse(core_features(), string) File "...VENV/lib/python3.7/site-packages/authres-1.2.0-py3.7.egg/authres/c= ore.py", line 442, in parse return self.parse_value(feature_context, string) File "...VENV/lib/python3.7/site-packages/authres-1.2.0-py3.7.egg/authres/c= ore.py", line 454, in parse_value header._parse() File "...VENV/lib/python3.7/site-packages/authres-1.2.0-py3.7.egg/authres/c= ore.py", line 504, in _parse raise SyntaxError('Expected authserv-id', self._parse_text) authres.core.SyntaxError: Syntax error: Expected authserv-id at: ; dkim=3Dpass header.d=3Ddomain.tld; arc=3Dnone... Aug 14 13:43:26 2019 (28962) SHUNTING: 1565790206.708188+e4196a80c2afc177ddc001ce8bbd8789f8d08912 > Of what kind? It's a simple protocol: if there is authentication > information (DKIM or ARC) in the incoming message, validate it. Then > package up the validation in the ARC-AR, ARC-Signature, and ARC-Seal > fields. Those are the operations the module performs. Limitations in Mailman3. I really should have written "other requirements or known incompatibilities". Thanks // David --===============6325059207740655483==-- From robl@lentil.org Wed Aug 14 15:14:27 2019 From: Robert Lister To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty 403 Forbidden Error Date: Wed, 14 Aug 2019 16:14:19 +0100 Message-ID: In-Reply-To: <7b3d2697d70a4a5c85a1c7e08f622968@riverbankcomputing.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1803464213250738219==" --===============1803464213250738219== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit I had the same problem when getting Hyperkitty to work. It was caused by a global redirect on my web server which was redirecting every web request received for *:80 to https://... url. This is enabled by default if you run certbot, for example to automagically update your web server config, enable https and redirect all non-https to https. mailman3 conf doesn't know about that, of course. I had to explicitly create a non-https port 80 listener for localhost: (in apache2, but nginx has similar conf:) ... ServerName localhost # Mailman3 conf: Include conf-available/mailman3.conf ... /etc/apache2/conf-available/mailman3.conf is just a symlink to the example provided in /etc/mailman3/apache.conf Similar example is provided for nginx. >>> >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >>> >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >>> >> >>> Forbidden >>> >> >>>

Access is forbidden

(403) >>> >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >>> >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >>> >> >>> Forbidden >>> >> >>>

Access is forbidden

(403) >>> >> >>> >>> >> >>> Any suggestions would be appreciated. >>> >> >> -- Robert Lister - email: robl(a)lentil.org - tel: 020 7043 7996 --===============1803464213250738219==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Wed Aug 14 17:08:16 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Thu, 15 Aug 2019 02:08:09 +0900 Message-ID: <23892.16377.686788.518291@turnbull.sk.tsukuba.ac.jp> In-Reply-To: <20190813184158.ld5olllcid6vbozo@atlantis> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4649286574215417144==" --===============4649286574215417144== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Marvin Gülker writes: > However, I thought the entire point in ARC was fixing automatic > rejections caused by DMARC invalidation by mailing lists, which are > vital for so many open-source projects (including Mailman iself). Yes. s/fixing/making it possible to fix/ and s/mailing lists/indirect mail/ (the REALLY big losers in April 2014 were small businesses which had a large percentage of their invoices become undeliverable). That doesn't help you one bit with your "rejection with no reason" problem, though. It helps you with one specific reason (DMARC p=reject). > If ARC falls short of solving that problem, because the large > providers do not automatically trust ARC, then supporting ARC on my > mailing list server is kind of void. Why should almighty Microsoft > trust my small personal mailing list server? The answer to that is "why shouldn't they?" I've never had a problem with any of the big services. There are reasons why some hosts might have problems due to no misbehavior of their own, and they wouldn't necessarily know about them either. But mostly the mail does go through. If the mail itself gets through, I see no reason why they wouldn't trust your ARC fields, so you won't get DMARC rejections, as long as nobody downstream of you breaks your ARC signatures. If you're seeing something different (ARC-authenticated messages getting rejected for DMARC alignment failure), let us know and I'll talk to a guy who knows this gal. My experience is good, the people I talk to are happy. If your experience is different, the ARC developers should know about it, otherwise we can't do anything about it. > ARC can only achieve its goal with black-listing untrusted relays > rather than white-listing known good ones, The goal of ARC is to keep users at p=reject sites happy. A lot of the people involved both at the IETF and at the DMARC Consortium are old-timers who are very sympathetic to mailing lists. But the day-to- day tuning of algorithms is targeted at users with mailboxes, not the lists that fill those mailboxes. Sad to say, users care more about spam (that's their provider's fault) than about mailing lists (which they assess as the mailing list's fault). Last I heard the Google folks and the IETF are very happy with ARC. > because it is simply unfeasable to manually maintain a list of all > open-source project mailing lists in the entire world. I could set > a new one up tomorrow, how should you know? That's not how this works. All of these services use huge databases of spam, ham, hosts, and mailing lists, and apply machine-learning algorithms to that data to create classifiers. It may take them some time to tune them for ARC, but the principle is there's no black or white here, it's all grey. Steve --===============4649286574215417144==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Wed Aug 14 17:11:00 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Thu, 15 Aug 2019 02:10:55 +0900 Message-ID: <23892.16543.270681.370117@turnbull.sk.tsukuba.ac.jp> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3987362550358055985==" --===============3987362550358055985== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit David Krantz writes: > Tested that and received a stacktrace where authres (of which I > know nothing) throws an exception complaining on a syntax error > when parsing the AuthenticationResultsHeader. It seems as if it > requires an authserv-id field but the few examples of the > AuthenticationResultsHeader I've looked at just starts with the > server name followed by a semicolon, with no preceeding tag for > that server name value. There is no tag for the authserv-id field; it is a value immediately after the field name and the colon, followed by a semicolon and the results for the various methods. It appears from the log messages that there is no value there. I believe that this field may not be empty according to RFC 8601. Without the message header, I can't verify that it was or wasn't, but I don't see why the log message would not contain the whole body of the AR or AAR header field. > line 504, in _parse > raise SyntaxError('Expected authserv-id', self._parse_text) > authres.core.SyntaxError: Syntax error: Expected authserv-id at: ; > dkim=pass header.d=domain.tld; arc=none... > Aug 14 13:43:26 2019 (28962) SHUNTING: > 1565790206.708188+e4196a80c2afc177ddc001ce8bbd8789f8d08912 Steve --===============3987362550358055985==-- From post+mm3-users@guelker.eu Wed Aug 14 20:05:43 2019 From: Marvin =?utf-8?q?G=C3=BClker?= To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Wed, 14 Aug 2019 22:05:35 +0200 Message-ID: <20190814200535.at4krwo5umsixcpi@atlantis> In-Reply-To: <23892.16377.686788.518291@turnbull.sk.tsukuba.ac.jp> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3731818522870613836==" --===============3731818522870613836== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 15. August 2019 um 02:08 Uhr +0900 schrieb Stephen J. Turnbull: > That doesn't help you one bit with your "rejection with no reason" > problem, though. It helps you with one specific reason (DMARC > p=3Dreject). I don't have that problem anymore since I pay for my SMTP relay provider. For me, the issue is solved. Before my personal mail (I'm not talking about mailing lists, just simple direct e-mail) was pretty much always sorted into the recipient's spam folder or directly rejected at the SMTP level (this was the case with both Microsoft and AOL; GMail usually filed my e-mail als spam). I looked up the reasons they gave in the SMTP reject; it was always bad reputation of IPs. Tools like mail-tester on the other hand say my e-mail and IP was fine, and delivery to small providers always went nicely. My mail server has never sent a single spam e-mail. I run it since years, and I am very sure that this never has happened. This mail server only hosts my and my family's e-mail. I have no AOL contacts anymore, so I left that is it was. For Microsoft (i.e. outlook.com), I went through their IP unblocking formula (which at the time contained a CAPTCHA that I'm sure a computer could solve better than me simple human) multiple times, and I received "conditionally mitigated" as a response each time. After a few months, the rejections would start again. Thus, I say they were rejecting my e-mail for no reason. Might be a hyperbole, but from my point of view, there was no reason. Again, the problem is now past with my workaround, so there is no need to investigate any further. I've given up on it. I don't believe you can have a VPS that directly delivers e-mail to the large providers successfully. The workaround with the SMTP relay provider still allows me to self-host, which fulfills my needs. > The answer to that is "why shouldn't they?" I hope it goes like that. > I've never had a problem with any of the big services. There are > reasons why some hosts might have problems due to no misbehavior of > their own, and they wouldn't necessarily know about them either. But > mostly the mail does go through. Lucky you. My experience was the complete contrary, and it's not just me. Take a look: > If the mail itself gets through, I see no reason why they wouldn't > trust your ARC fields, so you won't get DMARC rejections, as long as > nobody downstream of you breaks your ARC signatures. So, my situation currently is this. I have no (public) mailing lists on my own mail server, so there is no need for DMARC or ARC. Then, I'm involved in an open-source project that does have a mailing list and I'm considering to add ARC support for the list (one of the reasons why I constantly read this very mailing list). The project is small, so we'd like to avoid any effort that is fruitless anyway. Finally, I moderate the German ruby-de mailing list without any kind of influence on the software stack running it. That mailing list server runs Mailman 2.1.15 and this is not something I have any influence on. All of these list servers currently do not do ARC, hence I've not seen any rejections of ARC-signed messages (as there are none). I'm only evaluating how likely it'd be to see them. Please don't get me wrong; I appreciate all the effort that went into ARC! It looks like a good solution to the DMARC problems. > If you're seeing something different (ARC-authenticated messages > getting rejected for DMARC alignment failure), let us know and I'll > talk to a guy who knows this gal. This is a nice move. Thank you for this offer. When that happens, I'm going to post here! > But the day-to-day tuning of algorithms is targeted at users with > mailboxes, not the lists that fill those mailboxes. I am aware of that. See, when DMARC was spread over the world, ARC was not available. Even the Mailman wiki itself said and still says that DMARC has "negative consequences for mailing lists" and is "breaking long established mailing list norms, standards, and behaviors."[1] The problem still exists. On the ruby-de mailing list I moderate, there was a problem with a person sending e-mail from a p=3Dreject domain to the list[2] (which is, remember, run by Mailman 2.1.15). Two subscribers were force-unsubscribed for the DMARC bounces. I had to manually re-subscribe them and had to explain the p=3Dreject problem to the person sending the e-mails. This was... frustrating. And I think my statements on DMARC show my frustration. > Last I heard the Google folks and the IETF are very happy with ARC. I appreciate it. I hope it solves these problems. It's just that I'm reluctant to believe there's a quick solution available. It sounds to good to be true. > > because it is simply unfeasable to manually maintain a list of all > > open-source project mailing lists in the entire world. I could set > > a new one up tomorrow, how should you know? >=20 > That's not how this works. I'm afraid it does. Fastmail does it exactly like that: manual white list, see . Quote of the relevant passage: > Until the list of ARC enabled forwarders grows we maintain lists of > known good email forwarders and mailing lists, which we use to > whitelist known-good mail forwarders, and apply this list when > evaluating DMARC policies for inbound mail. To do them justice, they say a little further down that a failed DMARC check at a p=3Dreject policy domain does not cause an actual reject, but only increases the spam score. What worries me is that other providers might go that whitelisting approach, but don't follow the second part and still obey p=3Dreject. If everything goes well, nobody is going to do that and ARC is successful. I'm all in for that result, but I lack the knowledge to judge what is likely and what not. Which is why I'm asking here. >From your answer, I see that you think such behaviour is unlikely. That's good news, and it answers my question. Thanks! [1] https://wiki.list.org/DEV/DMARC [2] See July archive: https://lists.ruby-lang.org/pipermail/ruby-de/2019-July= /thread.html --=20 Blog: https://mg.guelker.eu --===============3731818522870613836==-- From brian@emwd.com Wed Aug 14 20:44:08 2019 From: brian@emwd.com To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Wed, 14 Aug 2019 20:44:06 +0000 Message-ID: <156581544698.8464.3966447158164829766@mailman.iad1.psf.io> In-Reply-To: <20190814200535.at4krwo5umsixcpi@atlantis> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7695677483705375672==" --===============7695677483705375672== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Marvin G=C3=BClker wrote: > > I don't have that problem anymore since I pay for my SMTP relay > provider. For me, the issue is solved. Before my personal mail (I'm not > talking about mailing lists, just simple direct e-mail) was pretty much > always sorted into the recipient's spam folder or directly rejected at > the SMTP level (this was the case with both Microsoft and AOL; GMail > usually filed my e-mail als spam). I looked up the reasons they gave in > the SMTP reject; it was always bad reputation of IPs. Tools like > mail-tester on the other hand say my e-mail and IP was fine, and > delivery to small providers always went nicely. My mail server has never > sent a single spam e-mail. I run it since years, and I am very sure that > this never has happened. This mail server only hosts my and my family's > e-mail. Did you keep an eye on the reputation on the IP addresses you were sending fr= om? Sometimes an IP address just doesn't send enough volume of mail to build = one up. I do agree some providers do ignore the IP reputation of an IP addres= s. For instance we had one that actually had a 100% reputation from SenderSco= re and it ran into a block with Microsoft. However the server had only been o= nline for a few months and we placed a client there that increased the volume= to Microsoft users. We did get that fixed. The key to Microsoft is to sign u= p for their Hotmail Feedback Loop. They also provide a nice interface (SNDS) = that shows you what they think of your IP addresses so you can mitigate any p= otential delivery issues ahead of time. > Thus, I say they were rejecting my e-mail for no reason. Might be a > hyperbole, but from my point of view, there was no reason. Again, the > problem is now past with my workaround, so there is no need to > investigate any further. I've given up on it. I don't believe you can > have a VPS that directly delivers e-mail to the large providers > successfully. The workaround with the SMTP relay provider still allows > me to self-host, which fulfills my needs. I disagree. We are a list hosting provider (Mailman 2 and 3) that has about a= dozen of VPS servers that are categorized as high volume senders and we see = great delivery rates. Our clients all use their own domain or sub-domains as = for their list as well. The key for us has been to keep our clients' lists cl= ean by enforcing reasonable bounce settings and screening new clients to make= sure we don't mistakenly take on a spammer. We do work hard to maintain our = IP reputations. Yahoo is the worst. They ignore everything, are hard to get a= hold of, says they want you to join their feedback loop but don't actually r= espond to your attempts at doing so, etc. However once the IP address "warms = up" (Yahoo's language, not ours) delivery rates are as good as the others. The majority reason why messages ends up in Spam folders has nothing to do wi= th the mail server at all. It is because the content of the message comes acr= oss as spammy, i.e. a message that contains several URLs, using exclamation p= oints, etc. Brian --===============7695677483705375672==-- From post+mm3-users@guelker.eu Thu Aug 15 07:16:58 2019 From: Marvin =?utf-8?q?G=C3=BClker?= To: mailman-users@mailman3.org Subject: [MM3-users] Re: ARC Date: Thu, 15 Aug 2019 09:16:50 +0200 Message-ID: <20190815071650.xouocjuwef4qbyga@atlantis> In-Reply-To: <156581544698.8464.3966447158164829766@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3449261173074590335==" --===============3449261173074590335== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am 14. August 2019 um 20:44 Uhr -0000 schrieb brian(a)emwd.com: > Did you keep an eye on the reputation on the IP addresses you were > sending from? Sometimes an IP address just doesn't send enough volume > of mail to build one up. This mail server ever only sent my personal and my family's e-mail -- no public mailing lists. The volume was very low. Maybe about ten e-mails a week in average, sometimes no e-mail a week at all. If low e-mail volume is indeed a criterion, then it could be the cause. But low volume as a spam criterion strikes me as doubtful, because a spammer specifically wants to issue mass e-mail. The server was online since I think 2013 and always had the same IP. It wasn't a shared IP, i.e. this mail server was the only one sending from that IP. The spam classification problem was there from the very beginning. > We did get that fixed. The key to Microsoft is to sign up for > their Hotmail Feedback Loop. They also provide a nice interface (SNDS) > that shows you what they think of your IP addresses so you can > mitigate any potential delivery issues ahead of time. I'm leaving that to my SMTP relay provider now. I find it too much hassle to sign up for such services just for my private e-mail. I'm not getting paid for sinking my time into this; keeping the server running and clean is enough of time investment into my hobby (I use it for other things than e-mail, too). Microsoft is not the only e-mail provider, so if all e-mail providers did it like that, you'd have to create dozens and hundreds of accounts. Microsoft's pure size is what allows them to pose such a restriction successfully. The real problem is the centralisation of services at only a few providers. > Yahoo is the worst. Luckily, Yahoo e-mail addresses are so rare in Germany that I can ignore them. I don't have anyone with a Yahoo address in my address book currently. outlook.com is much more common, but from my experience most German e-mail addresses are hosted by the United Internet group (GMX et al.), which I never had problems delivering to. They do a decent job. As for GMail, after a few attempts with followup questions my contacts started looking into their spam folder. That's why I was fine without the SMTP relay provider for years. But since recently, more and more people use outlook.com, which outright rejected. > The majority reason why messages ends up in Spam folders has nothing > to do with the mail server at all. It is because the content of the > message comes across as spammy, i.e. a message that contains several > URLs, using exclamation points, etc. Normal private 1-1 correspondence usually does not fulfill these criteria, and I've still been filed/rejected as spam (and likewise other family members). I felt like Don Quixote fighting the windmills. Today's e-mail infrastructure makes things difficult for private individuals who want to self-host. Anyway, I think this subthread has grown large enough. My questions were answered. Thanks to everybody who commented! -- Blog: https://mg.guelker.eu --===============3449261173074590335==-- From maxking@asynchronous.in Fri Aug 16 18:04:13 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty reply indent Date: Fri, 16 Aug 2019 11:04:04 -0700 Message-ID: <7af65b86-4f15-4048-9a3d-19841621aae8@www.fastmail.com> In-Reply-To: <8ec7bbe5-c2b4-49d7-a196-525b82b6cc8b@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3807526212851493455==" --===============3807526212851493455== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sun, Jul 21, 2019, at 5:07 PM, Abhilash Raj wrote: >=20 >=20 > On Sun, Jul 21, 2019, at 1:13 AM, Andrew Bernard wrote: > > Hi Abilash, > >=20 > > I took a quick look through the Hyperkitty source code to try to find=20 > > where the indent is computed, to no avail, not being experienced with=20 > > that code base. > >=20 > > But wouldn't there be some simple code that increments an indent value=20 > > somewhere that could easily be modified? >=20 > https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/templates/hype= rkitty/ajax/replies.html#L6 >=20 > You could remove the "margin-left" on the class to get rid of the indent > if you want to patch your installation. >=20 > I want to basically disable this based on the screen size and set this > value null for smaller screens only since this is helpful in threaded > conversations in larger screens. I recently worked on this and removed the indent on smaller screens. Please c= heck out https://gitlab.com/mailman/hyperkitty/merge_requests/171 if you want= to do this on your own server right now. I cut a release soon. --=20 thanks, Abhilash Raj (maxking) --===============3807526212851493455==-- From andrew.bernard@gmail.com Sat Aug 17 00:19:16 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] qcluster CPU usage Date: Sat, 17 Aug 2019 00:19:14 +0000 Message-ID: <156600115428.11277.16019268067334611679@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2548605193302683186==" --===============2548605193302683186== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Recently the qcluster program is engaging the CPU continuously at about 5% CP= U. While that may not be much, previously it was not doing this. What could b= e the cause of this? I cant see any warnings in the logs. --===============2548605193302683186==-- From andrew.bernard@gmail.com Sat Aug 17 00:27:30 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Download errors Date: Sat, 17 Aug 2019 00:27:28 +0000 Message-ID: <156600164814.11276.12729112002981100156@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2305967322732389036==" --===============2305967322732389036== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Whenever i try to download an archive, the file seems to be generated and it = downloads, but it will never open, with errors like 'an error occurred while = extracting files'. What can be causing this? --===============2305967322732389036==-- From andrew.bernard@gmail.com Sat Aug 17 00:30:52 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Re: Download errors Date: Sat, 17 Aug 2019 00:30:49 +0000 Message-ID: <156600184952.11278.10450155228647314168@mailman.iad1.psf.io> In-Reply-To: <156600164814.11276.12729112002981100156@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5559782142305965064==" --===============5559782142305965064== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Can I add to this that Archive Manager on Ubuntu shows a file in the archive = 50.3MB, but the actual gzip file is only 10 bytes in size on disk. Am I missing some compression program, or something similar? --===============5559782142305965064==-- From mark@msapiro.net Sat Aug 17 01:28:35 2019 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Download errors Date: Fri, 16 Aug 2019 18:28:24 -0700 Message-ID: In-Reply-To: <156600184952.11278.10450155228647314168@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7211158252599847155==" --===============7211158252599847155== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 8/16/19 5:30 PM, Andrew Bernard wrote: > Can I add to this that Archive Manager on Ubuntu shows a file in the archiv= e 50.3MB, but the actual gzip file is only 10 bytes in size on disk. It appears your download is truncated. what happens if you go to This should download mailman-users(a)mailman3.org.mbox.gz which is about 1.2 MB and is a gzip of a 5.4 MB mailman-users(a)mailman3.org.mbox. This works for me. If it doesn't work for you, it's probably a browser issue. If it does work for you, the issue may be a timeout or similar in your web server. Does downloading a single thread or a single month work? --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============7211158252599847155==-- From andrew.bernard@gmail.com Sat Aug 17 02:19:00 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Compression error Date: Sat, 17 Aug 2019 02:18:57 +0000 Message-ID: <156600833750.11278.4768554968387086950@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0526887638436886763==" --===============0526887638436886763== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I did a git pull today. Now I get the following error and the archives wont d= isplay: compressor.exceptions.OfflineGenerationError: You have offline compression en= abled but key "b5ae52a1ebb585c556edceb45a148cb948b2a2673d133a340a90cd02fdd348= 28" is missing from offline manifest. You may need to run "python manage.py compress". Here= is the original content: Any clues? --===============0526887638436886763==-- From mark@msapiro.net Sat Aug 17 02:32:01 2019 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Compression error Date: Fri, 16 Aug 2019 19:31:51 -0700 Message-ID: <674353a6-b0a9-4ecb-ae60-592ec72dd692@msapiro.net> In-Reply-To: <156600833750.11278.4768554968387086950@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0514700057098086866==" --===============0514700057098086866== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 8/16/19 7:18 PM, Andrew Bernard wrote: > I did a git pull today. Now I get the following error and the archives wont= display: >=20 > compressor.exceptions.OfflineGenerationError: You have offline compression = enabled but key "b5ae52a1ebb585c556edceb45a148cb948b2a2673d133a340a90cd02fdd3= 4828" is missing > from offline manifest. You may need to run "python manage.py compress". He= re is the original content: >=20 > Any clues? Did you do what it says, i.e. run "python manage.py compress" or however you spell your django admin command? It isn't always necessary, but I recommend that every time you do an update, you run all four of $DJANGO_CONTROL_SCRIPT collectstatic --clear --noinput --verbosity 0 $DJANGO_CONTROL_SCRIPT compress $DJANGO_CONTROL_SCRIPT compilemessages $DJANGO_CONTROL_SCRIPT migrate where $DJANGO_CONTROL_SCRIPT is the command to run django-admin or manage.py or however you spell it. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============0514700057098086866==-- From andrew.bernard@gmail.com Sat Aug 17 08:25:04 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Re: Compression error Date: Sat, 17 Aug 2019 08:25:01 +0000 Message-ID: <156603030103.11278.4336839448282019395@mailman.iad1.psf.io> In-Reply-To: <674353a6-b0a9-4ecb-ae60-592ec72dd692@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4227341867730792766==" --===============4227341867730792766== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Thank you Mark, this is very helpful information. Andrew --===============4227341867730792766==-- From andrew.bernard@gmail.com Sat Aug 17 08:26:40 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Idle connections to Postgres Date: Sat, 17 Aug 2019 08:26:37 +0000 Message-ID: <156603039784.11275.12356706201163796565@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6025240736486318192==" --===============6025240736486318192== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I have 20 idle connections to Postgres with Mailman 3. What are these for, an= d what are they doing (apart from apparently nothing)? main: mailman3 mailman3 ::1(46058) idle Andrew --===============6025240736486318192==-- From andrew.bernard@gmail.com Sat Aug 17 08:58:37 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Some threads donw download Date: Sat, 17 Aug 2019 08:58:35 +0000 Message-ID: <156603231560.11277.13379055999103160502@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7913627065613954818==" --===============7913627065613954818== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Further to my previos queries about download failures - the generated file is= corrupt, I turned up debugging and I now see this on the threads that don't = download. [pid: 25261|app: 0|req: 27/27] 59.167.198.231 () {48 vars in 1198 bytes} [Sat= Aug 17 08:55:15 2019] GET /archives/list/jackrail(a)jackrail.org/export/jack= rail(a)jackrail.org-CKOK7BEELMHIFF2MTPUZXQXQYZZGWF3D.mbox.gz?thread=3DCKOK7BE= ELMHIFF2MTPUZXQXQYZZGWF3D =3D> generated 0 bytes in 55 msecs (HTTP/1.1 200) 5= headers in 241 bytes (0 switches on core 0) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.2.3-py3= .7.egg/hyperkitty/views/mlist.py", line 327, in stream_mbox msg =3D email.as_message() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.2.3-py3= .7.egg/hyperkitty/models/email.py", line 188, in as_message subtype=3Dmimetype[1], filename=3Dattachment.name) File "/usr/lib/python3.7/email/message.py", line 1147, in add_attachment self._add_multipart('mixed', *args, _disp=3D'attachment', **kw) File "/usr/lib/python3.7/email/message.py", line 1135, in _add_multipart part.set_content(*args, **kw) File "/usr/lib/python3.7/email/message.py", line 1162, in set_content super().set_content(*args, **kw) File "/usr/lib/python3.7/email/message.py", line 1092, in set_content content_manager.set_content(self, *args, **kw) File "/usr/lib/python3.7/email/contentmanager.py", line 35, in set_content handler =3D self._find_set_handler(msg, obj) File "/usr/lib/python3.7/email/contentmanager.py", line 58, in _find_set_ha= ndler raise KeyError(full_path_for_error) KeyError: 'builtins.NoneType' What is this saying? Andrew [Somewhat perplexed at why Mailman 3 is behaving so badly for me...] --===============7913627065613954818==-- From andrew.bernard@gmail.com Sun Aug 18 01:53:48 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Re: Some threads donw download Date: Sun, 18 Aug 2019 01:53:45 +0000 Message-ID: <156609322519.11276.16832051376548290160@mailman.iad1.psf.io> In-Reply-To: <156603231560.11277.13379055999103160502@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3325630298379490909==" --===============3325630298379490909== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable As a possible clue, I use the filesystem to store attachments. For some reas= on I found that using Postgres if they are stored in the database they don't = download in the Hyperkitty view mode for a post, although listed as present. Could this be a bug relating to being unable to package up attachments if the= y are in the filesystem? Andrew --===============3325630298379490909==-- From mark@msapiro.net Sun Aug 18 03:24:01 2019 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Some threads donw download Date: Sat, 17 Aug 2019 20:23:54 -0700 Message-ID: <354e6a2f-8ee4-0241-7a1a-5eddf802a0fa@msapiro.net> In-Reply-To: <156609322519.11276.16832051376548290160@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3015402640305459351==" --===============3015402640305459351== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 8/17/19 6:53 PM, Andrew Bernard wrote: > As a possible clue, I use the filesystem to store attachments. For some re= ason I found that using Postgres if they are stored in the database they don'= t download in the Hyperkitty view mode for a post, although listed as present. Is this perhaps , although I don't store attachments in the file system? > Could this be a bug relating to being unable to package up attachments if t= hey are in the filesystem? In my case even though I can't retrieve the attachment via the link in the HyperKitty thread view, if I download the thread mbox, there is no issue and the attachment is there. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============3015402640305459351==-- From maztec@gmail.com Mon Aug 19 05:02:31 2019 From: Jay Gairson To: mailman-users@mailman3.org Subject: [MM3-users] Re: MM3 + Postfix + Dovecot + PostfixAdmin Date: Sun, 18 Aug 2019 22:02:15 -0700 Message-ID: In-Reply-To: <23885.324.622744.980600@turnbull.sk.tsukuba.ac.jp> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7063647258758385902==" --===============7063647258758385902== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Steve: Fair enough. The issue ultimately was with Postfix, but I only encountered it because I misread the Mailman3 configuration wiki as setting "virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap" to be /path-to-mailman/var/data/postfix_lmtp. The lmtp versus vmap distinction made a large difference. I'm not sure where I picked that error up or whether I just imagined it myself. Fixed now! Thank you. Jay On Thu, Aug 8, 2019 at 10:14 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > maztec(a)gmail.com writes: > > > Issue: Postfix LMTP does not pass messages onto MM3:LMTP. > > I don't understand why this is a Mailman problem. Seems like Postfix > user lists would be a better venue to get expert help with this. > Among other things, our most responsive Postfix guy is out of cell > coverage for now. > > I would post this To: the relevant Postfix list, Cc: this list, and > set Reply-To and Mail-Followups-To to the Postfix list to get > everybody who can contribute on the same page. > > If it is a Mailman problem, you have my apologies and I'm listening. > > Steve > --===============7063647258758385902==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Mon Aug 19 07:29:54 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] Re: MM3 + Postfix + Dovecot + PostfixAdmin Date: Mon, 19 Aug 2019 16:29:47 +0900 Message-ID: <23898.20459.222296.891935@turnbull.sk.tsukuba.ac.jp> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6068956382724207129==" --===============6068956382724207129== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Jay Gairson writes: > Steve: Fair enough. The issue ultimately was with Postfix, but I > only encountered it because I misread the Mailman3 configuration > wiki as setting > "virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap" > to be /path-to-mailman/var/data/postfix_lmtp. Thanks for the followup! For future reference for those who are following along, while that's technically a Postfix configuration issue, it's the kind of thing that people like Mark and Abhilash are at least as likely to notice as most of the folks on Postfix lists. Bottom line: don't hesitate to report these issues to us, but if it could be the MTA, report to their users' list too. More eyes, etc. Steve --===============6068956382724207129==-- From maztec@gmail.com Mon Aug 19 19:04:24 2019 From: Jay Gairson To: mailman-users@mailman3.org Subject: [MM3-users] Re: MM3 + Postfix + Dovecot + PostfixAdmin Date: Mon, 19 Aug 2019 12:04:10 -0700 Message-ID: In-Reply-To: <23898.20459.222296.891935@turnbull.sk.tsukuba.ac.jp> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1807400749820385975==" --===============1807400749820385975== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Exactly as Steve said. I did report it to the Postfix lists and then had my running in circles for completely unrelated issues. They were convinced that specifying Mailman3 as an LMTP instead of an SMTP server was incorrect, because if it was LMTP I should be pointing at a socket instead of localhost. At the end of the day I figured it out by reading problems other people were having in their configurations that sounded like the same thing, and someone made a side comment about virtual_alias_maps. I double-checked, saw my configuration error, and fixed it. I think I made this mistake because I had started with a hash-based configuration and then realized I needed to use regexp. The hash-based configuration has a side case that requires postfix_vmap to be defined. When changing to regexp I simply changed the labels to regexp, saw my error log spitting out that there was no postfix_vmap file, looked at the regexp configuration saw that there was no vmap for it and instead of deleting the vmap changed it over to lmtp. My own fault all the way around, but worth noting at this point since others might be tired or in a hurry and make the same mistake. A mistake that doesn't really report an error in a way that makes it stand out. On Mon, Aug 19, 2019 at 12:29 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Jay Gairson writes: > > > Steve: Fair enough. The issue ultimately was with Postfix, but I > > only encountered it because I misread the Mailman3 configuration > > wiki as setting > > "virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap" > > to be /path-to-mailman/var/data/postfix_lmtp. > > Thanks for the followup! > > For future reference for those who are following along, while that's > technically a Postfix configuration issue, it's the kind of thing that > people like Mark and Abhilash are at least as likely to notice as most > of the folks on Postfix lists. Bottom line: don't hesitate to report > these issues to us, but if it could be the MTA, report to their users' > list too. More eyes, etc. > > Steve > --===============1807400749820385975==-- From turnbull.stephen.fw@u.tsukuba.ac.jp Tue Aug 20 16:52:55 2019 From: "Stephen J. Turnbull" To: mailman-users@mailman3.org Subject: [MM3-users] Re: MM3 + Postfix + Dovecot + PostfixAdmin Date: Wed, 21 Aug 2019 01:52:48 +0900 Message-ID: <23900.9568.361553.363663@turnbull.sk.tsukuba.ac.jp> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4695848780043273526==" --===============4695848780043273526== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Jay Gairson writes: > They were convinced that specifying Mailman3 as an LMTP instead of > an SMTP server was incorrect, because if it was LMTP I should be > pointing at a socket instead of localhost. Did they say why? I understand why a socket MAY be used, but is there a reason why localhost SHOULD NOT be used? (If it's complicated or unclear and this was all on their public lists, point me that-a-way.) > My own fault all the way around, Well, maybe we can provide a better default, somehow. > A mistake that doesn't really report an error in a way that makes > it stand out. Reporting that error is pretty much out of Mailman's reach, correct? (Except by implementing config consistency checking that we should contribute to Postfix, I mean.) Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN --===============4695848780043273526==-- From ugniusviln@gmail.com Fri Aug 23 15:20:15 2019 From: ugniusviln@gmail.com To: mailman-users@mailman3.org Subject: [MM3-users] Mailman 3 installation, no mails in hyperkitty, unable to add footer. Date: Fri, 23 Aug 2019 15:11:36 +0000 Message-ID: <156657309662.6727.2417244460785920037@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4235035947814740028==" --===============4235035947814740028== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I have read documentation, but still have stupid questions, could You please = help, because I can't make it working. I do not understand something importan= t. I have no experience with python at all. I have mailman 3, python 3.5 in m= y debian OS system, and additional packages like uwsgi and ect. using https:/= /buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman.pdf abou= t till chapter 6. I understand mailman suite has hyperkitty already. But I a= m not sure about: 1. Does mailman-suite have hyper-kitty inside? Because if I run $python mana= ge.py runserver - it runs. In installed it under dedicated OS user home and f= onfigured to run.=20 I can create lists, event add lists to hyperkitty page using: $django-admin r= unjob new_lists_from_mailman list server sends messages to list members as w= ell. But nothing happens more. No emails come to hyperkitty, arciver log 0 s= ize. =20 $ python manage.py runjobs -l shows the lists of the jobs, so seems nothing = to add.=20 Except uwsgi.ini, I have only 2 configuration files in mailman-suite project = directory: settings.py and mailman.cfg So I do not understand what did I co= nfigured badly.=20 2. If I (using Postorius web interface) add footer template to my list under= regular message, something strange happens. Mailman stops to send messages f= or list members. No any entries in the logs. Just Mailman log writes: "unabl= e to connect localhost port 25" and no more explanation. If I delete list's = footer template (web interface), mailman starts working again. What is bad h= ere? How to add custom footer? In mailman 2 if was working so good and was = easy to setup. --===============4235035947814740028==-- From mark@msapiro.net Fri Aug 23 17:28:32 2019 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer. Date: Fri, 23 Aug 2019 10:28:21 -0700 Message-ID: In-Reply-To: <156657309662.6727.2417244460785920037@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7523381329952349954==" --===============7523381329952349954== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > I have read documentation, but still have stupid questions, could You pleas= e help, because I can't make it working. I do not understand something import= ant. I have no experience with python at all. I have mailman 3, python 3.5 in= my debian OS system, and additional packages like uwsgi and ect. using https= ://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman.pdf ab= out till chapter 6. I understand mailman suite has hyperkitty already. But I= am not sure about: >=20 > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python ma= nage.py runserver - it runs. In installed it under dedicated OS user home and= fonfigured to run.=20 > I can create lists, event add lists to hyperkitty page using: $django-admin= runjob new_lists_from_mailman list server sends messages to list members as= well. But nothing happens more. No emails come to hyperkitty, arciver log 0= size. =20 > $ python manage.py runjobs -l shows the lists of the jobs, so seems nothin= g to add.=20 How exactly did you install Mailman? The document you reference gives alternatives. You don't say exactly what you did. > 2. If I (using Postorius web interface) add footer template to my list und= er regular message, something strange happens. Mailman stops to send messages= for list members. No any entries in the logs. Just Mailman log writes: "una= ble to connect localhost port 25" and no more explanation. If I delete list'= s footer template (web interface), mailman starts working again. What is bad= here? How to add custom footer? In mailman 2 if was working so good and wa= s easy to setup. It appears that no MTA is listening on localhost port 25. Is your MTA even running? It is extremely unlikely that this has anything to do with adding a termplate in Postorius. You might be better off installing Debian's 'mailman3-full' package . --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============7523381329952349954==-- From ugniusviln@gmail.com Fri Aug 23 19:17:40 2019 From: Ugnius S To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer. Date: Fri, 23 Aug 2019 22:17:23 +0300 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6897060163289875310==" --===============6897060163289875310== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, Mark. Thank You for trying to help me. I do not remember how exactly I installed mailman or by apt-get or: $ sudo pip3 install mailman ---I think, have tried this way, but it already was installed. ~/mailman-suite$ mailman info GNU Mailman 3.2.2 (La Villa Strangiato) Python 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516] config file: /home/user/mailman-suite/mailman.cfg db url: sqlite:////home/user/mailman-suite/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:Rest_password MTA works correctly. Yes, I understand the error is very strange, but this exactly happens when I add footer custom template to list's regular message via web interface. "telnet loclhost 25" answers correctly. Messages about new members adding and new list creating works and reach the recipients. But Mailman for some strange reasons could not to sent messages from member to other list's members. And nothing to do more: it is enough to delete template and mailman starts send new messages correctly. One remark all messages during with customs template was active remain somewhere in between and do not go out even if template is deleted. I can't even imagine how to debug that. I have noticed that by experience - method to check does mailman work after every small update. This system is so easy to make not working, and then is so hard to understand what did happen. It would be good to read about working example how to setup, and which moments are important. There are many places documented about separate packages, but not full example. I have found one here https://lab.uberspace.de/guide_mailman-3.html, but here part of steps seems are not written as well. For example uwsgi ini and pre required environment. It could happen that for author these steps were trivial, but for person from side some small explanations are very important to understand whole picture of setup and why small parameters where set exactly that way. Of course I am very thankful for authors of that example, because that helped me as well. 2019-08-23, pn, 20:28 Mark Sapiro ra=C5=A1=C4=97: > On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > > I have read documentation, but still have stupid questions, could You > please help, because I can't make it working. I do not understand something > important. I have no experience with python at all. I have mailman 3, > python 3.5 in my debian OS system, and additional packages like uwsgi and > ect. using > https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman= .pdf > about till chapter 6. I understand mailman suite has hyperkitty already. > But I am not sure about: > > > > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python > manage.py runserver - it runs. In installed it under dedicated OS user home > and fonfigured to run. > > I can create lists, event add lists to hyperkitty page using: > $django-admin runjob new_lists_from_mailman list server sends messages to > list members as well. But nothing happens more. No emails come to > hyperkitty, arciver log 0 size. > > $ python manage.py runjobs -l shows the lists of the jobs, so seems > nothing to add. > > > > How exactly did you install Mailman? The document you reference gives > alternatives. You don't say exactly what you did. > > > > 2. If I (using Postorius web interface) add footer template to my list > under regular message, something strange happens. Mailman stops to send > messages for list members. No any entries in the logs. Just Mailman log > writes: "unable to connect localhost port 25" and no more explanation. If > I delete list's footer template (web interface), mailman starts working > again. What is bad here? How to add custom footer? In mailman 2 if was > working so good and was easy to setup. > > > It appears that no MTA is listening on localhost port 25. Is your MTA > even running? It is extremely unlikely that this has anything to do with > adding a termplate in Postorius. > > You might be better off installing Debian's 'mailman3-full' package > < > https://packages.debian.org/search?keywords=3Dmailman3-full&searchon=3Dname= s&suite=3Dall§ion=3Dall > >. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > --===============6897060163289875310==-- From mark@msapiro.net Fri Aug 23 20:18:25 2019 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer. Date: Fri, 23 Aug 2019 13:18:16 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0307705857631609173==" --===============0307705857631609173== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 8/23/19 12:17 PM, Ugnius S wrote: > > It would be good to read about working example how to setup, and which > moments are important. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============0307705857631609173==-- From paul@arenson.org Mon Aug 26 04:49:07 2019 From: paul@arenson.org To: mailman-users@mailman3.org Subject: [MM3-users] Status of hosting options after a year for non techies Date: Mon, 26 Aug 2019 04:40:44 +0000 Message-ID: <156679444455.6728.14609842989108618968@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7998315989281382317==" --===============7998315989281382317== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all This is Paul Arenson in Japan. I temporarily dropped off the list year ago wh= en it was clear there was no Cpanel Solution forthcoming. I thought I would = check in again. I used to be on CPanel and I was advised it might be a wait. 1) I am now on Plesk. I heard Plesk might allow Docker and installation may b= e possible. Am I misinformed or a possibility? --->Assuming no, I guess jump to question 4. 2) Assuming yes, I see a list of people who can possibly help install. https://wiki.list.org/COM/Mailman%20consulting%20services Only a few people on it. Has anyone used any or can recommend someone. 3) There is also a Python list, but before I submit a request, is this someth= ing that works on general. For example, when a new version or bug release com= es up, will I need to call on the person or persons again? Is it still bette= r to wait? 4) Hosting services: Only a few listed at https://wiki.list.org/COM/Mailman%2= 0hosting%20services are or Mailman 3.=20 Has anyone used this: https://mailman3.com The site seems incomplete. Or this: https://maadix.net/en/servers Looks good. Might be a bit expensive for my use. Or this: https://www.mailmanhost.com/mailman-3-hosting/ Also looks good. A long time ago we corresponded. They seem reasonable. My l= ist is about 700 people. These seem to be the same people: https://www.emwd.com/mailman-3-shared-list= -hosting/ Any others I should know about? Thanks in advance. paul arenson japan --===============7998315989281382317==-- From krinetzki@itc.rwth-aachen.de Mon Aug 26 06:51:35 2019 From: Stephan Krinetzki To: mailman-users@mailman3.org Subject: [MM3-users] Internal Server Error by Clicking on OrmQ Queue Date: Mon, 26 Aug 2019 06:51:31 +0000 Message-ID: <156680229111.1694.5893842035472282816@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0458895012224949609==" --===============0458895012224949609== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Dear list, on our Mailman 3 system we are hitting the following error by clicking a link= to admin/django_q/ormq/: Server Error The Log prints: --- ERROR 2019-08-26 08:48:01,704 10311 django.request Internal Server Error: /ad= min/django_q/ormq/ Traceback (most recent call last): File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/db/model= s/options.py", line 566, in get_field return self.fields_map[field_name] KeyError: 'task_id' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/utils.py", line 276, in lookup_field f =3D _get_non_gfk_field(opts, name) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/utils.py", line 307, in _get_non_gfk_field field =3D opts.get_field(name) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/db/model= s/options.py", line 568, in get_field raise FieldDoesNotExist("%s has no field named '%s'" % (self.object_name,= field_name)) django.core.exceptions.FieldDoesNotExist: OrmQ has no field named 'task_id' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/core/han= dlers/exception.py", line 35, in inner response =3D get_response(request) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/core/han= dlers/base.py", line 158, in _get_response response =3D self.process_exception_by_middleware(e, request) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/core/han= dlers/base.py", line 156, in _get_response response =3D response.render() File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /response.py", line 106, in render self.content =3D self.rendered_content File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /response.py", line 83, in rendered_content content =3D template.render(context, self._request) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 175, in render return self._render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /loader_tags.py", line 155, in render return compiled_parent._render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /loader_tags.py", line 155, in render return compiled_parent._render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /loader_tags.py", line 67, in render result =3D block.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /loader_tags.py", line 67, in render result =3D block.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /library.py", line 214, in render _dict =3D self.func(*resolved_args, **resolved_kwargs) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/templatetags/admin_list.py", line 326, in result_list 'results': list(results(cl))} File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/templatetags/admin_list.py", line 302, in results yield ResultList(None, items_for_result(cl, res, None)) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/templatetags/admin_list.py", line 293, in __init__ super().__init__(*items) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/templatetags/admin_list.py", line 212, in items_for_result f, attr, value =3D lookup_field(field_name, result, cl.model_admin) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/utils.py", line 289, in lookup_field value =3D attr() File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/models= .py", line 200, in task_id return self.task()['id'] File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/models= .py", line 194, in task return SignedPackage.loads(self.payload) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/signin= g.py", line 31, in loads serializer=3DPickleSerializer) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/core_s= igning.py", line 38, in loads return serializer().loads(data) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/signin= g.py", line 44, in loads return pickle.loads(data) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1: ordin= al not in range(128) ERROR 2019-08-26 08:48:01,704 10311 django.request Internal Server Error: /ad= min/django_q/ormq/ Traceback (most recent call last): File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/db/model= s/options.py", line 566, in get_field return self.fields_map[field_name] KeyError: 'task_id' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/utils.py", line 276, in lookup_field f =3D _get_non_gfk_field(opts, name) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/utils.py", line 307, in _get_non_gfk_field field =3D opts.get_field(name) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/db/model= s/options.py", line 568, in get_field raise FieldDoesNotExist("%s has no field named '%s'" % (self.object_name,= field_name)) django.core.exceptions.FieldDoesNotExist: OrmQ has no field named 'task_id' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/core/han= dlers/exception.py", line 35, in inner response =3D get_response(request) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/core/han= dlers/base.py", line 158, in _get_response response =3D self.process_exception_by_middleware(e, request) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/core/han= dlers/base.py", line 156, in _get_response response =3D response.render() File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /response.py", line 106, in render self.content =3D self.rendered_content File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /response.py", line 83, in rendered_content content =3D template.render(context, self._request) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 175, in render return self._render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /loader_tags.py", line 155, in render return compiled_parent._render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /loader_tags.py", line 155, in render return compiled_parent._render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /loader_tags.py", line 67, in render result =3D block.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /loader_tags.py", line 67, in render result =3D block.nodelist.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 943, in render bit =3D node.render_annotated(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /base.py", line 910, in render_annotated return self.render(context) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/template= /library.py", line 214, in render _dict =3D self.func(*resolved_args, **resolved_kwargs) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/templatetags/admin_list.py", line 326, in result_list 'results': list(results(cl))} File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/templatetags/admin_list.py", line 302, in results yield ResultList(None, items_for_result(cl, res, None)) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/templatetags/admin_list.py", line 293, in __init__ super().__init__(*items) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/templatetags/admin_list.py", line 212, in items_for_result f, attr, value =3D lookup_field(field_name, result, cl.model_admin) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django/contrib/= admin/utils.py", line 289, in lookup_field value =3D attr() File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/models= .py", line 200, in task_id return self.task()['id'] File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/models= .py", line 194, in task return SignedPackage.loads(self.payload) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/signin= g.py", line 31, in loads serializer=3DPickleSerializer) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/core_s= igning.py", line 38, in loads return serializer().loads(data) File "/opt/mailman/mailman-venv/lib/python3.6/site-packages/django_q/signin= g.py", line 44, in loads return pickle.loads(data) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1: ordin= al not in range(128) --- Any ideas how to see the complete queue an maybe delete some defunct entries? --===============0458895012224949609==-- From ugniusviln@gmail.com Mon Aug 26 10:34:29 2019 From: Ugnius To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer. Date: Mon, 26 Aug 2019 13:34:22 +0300 Message-ID: <8BC4406F-CD23-4AB0-A872-E071C0DE88C4@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0581669340021088798==" --===============0581669340021088798== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Mark, Thank You for your guidance. Yes, seems my installed mailman3 package i= s not full. I have tried to install it on my Debian 9, but I got package bro= ken error and all possible proposals how to fix it did not help. But it is no= rmal - official OS version 9 has no this package included. Then I have decid= ed to play on another machine where is installed Debian 10. I have successfu= lly installed mailman3-full. It already came pre-configured with keys include= d. Mailman3-web packige was something new for me. I understand it replaces = mailman- suite, but like I did not find where to read about it, I did not f= ind how to open the administration or postorius site.=20 Kind regards=20 Ugnius=20 > On 23 Aug 2019, at 23:18, Mark Sapiro wrote: >=20 >> On 8/23/19 12:17 PM, Ugnius S wrote: >>=20 >> It would be good to read about working example how to setup, and which >> moments are important. >=20 >=20 > See . >=20 >=20 > --=20 > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ --===============0581669340021088798==-- From brian@emwd.com Mon Aug 26 10:42:49 2019 From: Brian Carpenter To: mailman-users@mailman3.org Subject: [MM3-users] Re: Status of hosting options after a year for non techies Date: Mon, 26 Aug 2019 06:42:44 -0400 Message-ID: <2d5501d55bfa$fe5ce4b0$fb16ae10$@emwd.com> In-Reply-To: <156679444455.6728.14609842989108618968@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2903212996933719180==" --===============2903212996933719180== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi Paul, I believe we are the only shared Mailman 3 service at the moment. Other companies that offer Mailman 3 hosting seem to only offer it on a dedicated environment which can be expensive for a single list owner. However we also offer that option but mainly has a cost savings alternative to those who need to host more than 10 lists. We have found Mailman 3 to require more maintenance than Mailman 2 and it seems to require more server resources. I believe we are also the only company that provides an installation service on those who want it on their own dedicated environment however we only do this for CentOS 7 and we utilize the Docker version of Mailman 3. The positive side is we setup the whole shebang including Nginx, Exim, and Let's Encrypt. I doubt cPanel (or any other Hosting control panel) will ever offer Mailman 3 in their package. Have a great day! Brian Carpenter EMWD.com brian(a)emwd.com -----Original Message----- From: paul(a)arenson.org Sent: Monday, August 26, 2019 12:41 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Status of hosting options after a year for non techies Hi all This is Paul Arenson in Japan. I temporarily dropped off the list year ago when it was clear there was no Cpanel Solution forthcoming. I thought I would check in again. I used to be on CPanel and I was advised it might be a wait. 1) I am now on Plesk. I heard Plesk might allow Docker and installation may be possible. Am I misinformed or a possibility? --->Assuming no, I guess jump to question 4. 2) Assuming yes, I see a list of people who can possibly help install. https://wiki.list.org/COM/Mailman%20consulting%20services Only a few people on it. Has anyone used any or can recommend someone. 3) There is also a Python list, but before I submit a request, is this something that works on general. For example, when a new version or bug release comes up, will I need to call on the person or persons again? Is it still better to wait? 4) Hosting services: Only a few listed at https://wiki.list.org/COM/Mailman%20hosting%20services are or Mailman 3. Has anyone used this: https://mailman3.com The site seems incomplete. Or this: https://maadix.net/en/servers Looks good. Might be a bit expensive for my use. Or this: https://www.mailmanhost.com/mailman-3-hosting/ Also looks good. A long time ago we corresponded. They seem reasonable. My list is about 700 people. These seem to be the same people: https://www.emwd.com/mailman-3-shared-list-hosting/ Any others I should know about? Thanks in advance. paul arenson japan _______________________________________________ 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/ --===============2903212996933719180==-- From paul@arenson.org Mon Aug 26 12:03:01 2019 From: paul@arenson.org To: mailman-users@mailman3.org Subject: [MM3-users] Re: Status of hosting options after a year for non techies Date: Mon, 26 Aug 2019 12:02:59 +0000 Message-ID: <156682097909.6725.2244102097823355966@mailman.iad1.psf.io> In-Reply-To: <2d5501d55bfa$fe5ce4b0$fb16ae10$@emwd.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4010649934286252390==" --===============4010649934286252390== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thank you Brian. I remember that I to you in reference to MM3 and a small gr= oup I was hosting for. Probably before you started offering MN3. This time it= is for my own personal mailing list, which I hope to make a discussion list.= Problem will be low usage based on past experience with various other lists-= Dada, MM 2, and way back, Topica, etc. As you said, the other group test offers MM 3 does it in an environment of mu= ltiple tools, which I don=E2=80=99t need.=20 I think I would like to set up an instance. We have 600 or 700 users on Maile= r-lite at the moment. May I contact you in a couple of days on your website? = Thanks,=20 Paul=20 In Japan, where it is now 9 pm Monday while probably 8 AM Monday in North (?)= Carolina. --===============4010649934286252390==-- From brian@emwd.com Mon Aug 26 12:49:04 2019 From: Brian Carpenter To: mailman-users@mailman3.org Subject: [MM3-users] Re: Status of hosting options after a year for non techies Date: Mon, 26 Aug 2019 08:48:59 -0400 Message-ID: <2fbf01d55c0c$a1a92f00$e4fb8d00$@emwd.com> In-Reply-To: <156682097909.6725.2244102097823355966@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1473041845149362529==" --===============1473041845149362529== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sure Paul. That would be great. Have a great day! Brian Carpenter EMWD.com brian(a)emwd.com -----Original Message----- From: paul(a)arenson.org =20 Sent: Monday, August 26, 2019 8:03 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Status of hosting options after a year for non techi= es Thank you Brian. I remember that I to you in reference to MM3 and a small gr= oup I was hosting for. Probably before you started offering MN3. This time it= is for my own personal mailing list, which I hope to make a discussion list.= Problem will be low usage based on past experience with various other lists-= Dada, MM 2, and way back, Topica, etc. As you said, the other group test offers MM 3 does it in an environment of mu= ltiple tools, which I don=E2=80=99t need.=20 I think I would like to set up an instance. We have 600 or 700 users on Maile= r-lite at the moment. May I contact you in a couple of days on your website? = Thanks,=20 Paul=20 In Japan, where it is now 9 pm Monday while probably 8 AM Monday in North (?)= Carolina. _______________________________________________ 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/ --===============1473041845149362529==-- From mailman3@malevil.cc Tue Aug 27 14:14:12 2019 From: mailman3@malevil.cc To: mailman-users@mailman3.org Subject: [MM3-users] still up to date? Date: Tue, 27 Aug 2019 14:14:09 +0000 Message-ID: <156691524979.6727.14072652880133244288@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4883208681106008159==" --===============4883208681106008159== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I have subscribed to the following rss feeds to keep track of updates: https://libraries.io/pypi/mailman/versions.atom https://libraries.io/pypi/mailman-hyperkitty/versions.atom https://libraries.io/pypi/HyperKitty/versions.atom https://libraries.io/pypi/postorius/versions.atom https://gitlab.com/mailman/mailman-suite/commits/master?feed_token=3DyitiVdhX= QgBnb4PP3RZa&format=3Datom but none of them was updated for half a year, is that actually the status? No= current releases or updates for mailman3? --===============4883208681106008159==-- From maxking@asynchronous.in Tue Aug 27 18:44:23 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: still up to date? Date: Tue, 27 Aug 2019 11:43:54 -0700 Message-ID: In-Reply-To: <156691524979.6727.14072652880133244288@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1002641168477416450==" --===============1002641168477416450== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tue, Aug 27, 2019, at 7:14 AM, mailman3(a)malevil.cc wrote: > I have subscribed to the following rss feeds to keep track of updates: >=20 > https://libraries.io/pypi/mailman/versions.atom > https://libraries.io/pypi/mailman-hyperkitty/versions.atom > https://libraries.io/pypi/HyperKitty/versions.atom > https://libraries.io/pypi/postorius/versions.atom > https://gitlab.com/mailman/mailman-suite/commits/master?feed_token=3DyitiVd= hXQgBnb4PP3RZa&format=3Datom >=20 > but none of them was updated for half a year, is that actually the=20 > status? No current releases or updates for mailman3? I am planning a new release, but waiting to find some time to fix a blocker issue in Hyperkitty. > _______________________________________________ > 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/ > --=20 thanks, Abhilash Raj (maxking) --===============1002641168477416450==-- From maxking@asynchronous.in Tue Aug 27 18:44:58 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: still up to date? Date: Tue, 27 Aug 2019 11:44:34 -0700 Message-ID: <0e661268-bf4d-4785-ba56-917cc9db893c@www.fastmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8015159226937779056==" --===============8015159226937779056== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Specifically, this one https://gitlab.com/mailman/hyperkitty/merge_requests/1= 75 On Tue, Aug 27, 2019, at 11:43 AM, Abhilash Raj wrote: > On Tue, Aug 27, 2019, at 7:14 AM, mailman3(a)malevil.cc wrote: > > I have subscribed to the following rss feeds to keep track of updates: > >=20 > > https://libraries.io/pypi/mailman/versions.atom > > https://libraries.io/pypi/mailman-hyperkitty/versions.atom > > https://libraries.io/pypi/HyperKitty/versions.atom > > https://libraries.io/pypi/postorius/versions.atom > > https://gitlab.com/mailman/mailman-suite/commits/master?feed_token=3Dyiti= VdhXQgBnb4PP3RZa&format=3Datom > >=20 > > but none of them was updated for half a year, is that actually the=20 > > status? No current releases or updates for mailman3? >=20 > I am planning a new release, but waiting to find some time to > fix a blocker issue in Hyperkitty. >=20 >=20 >=20 > > _______________________________________________ > > 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/ > > >=20 > --=20 > thanks, > Abhilash Raj (maxking) --=20 thanks, Abhilash Raj (maxking) --===============8015159226937779056==-- From andrew.bernard@gmail.com Sat Aug 31 08:47:56 2019 From: Andrew Bernard To: mailman-users@mailman3.org Subject: [MM3-users] Suspend a list temporarily Date: Sat, 31 Aug 2019 08:47:52 +0000 Message-ID: <156724127297.6728.9433334402487212488@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8476796109964596342==" --===============8476796109964596342== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Is there any way to do this, while keeping other lists running? --===============8476796109964596342==-- From maxking@asynchronous.in Sat Aug 31 15:13:32 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Suspend a list temporarily Date: Sat, 31 Aug 2019 08:13:05 -0700 Message-ID: <01c09c06-3d64-4942-80fa-fff5d638e8a1@www.fastmail.com> In-Reply-To: <156724127297.6728.9433334402487212488@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1648714528743903757==" --===============1648714528743903757== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On Sat, Aug 31, 2019, at 1:47 AM, Andrew Bernard wrote: > Is there any way to do this, while keeping other lists running? What is your definition of disabled in this case though? 1. Mail server rejects the messages to it saying this list doesn't exist? 2. Mailman rejects the messages to it saying this list is suspended? While there is direct way to achieve this, you can configure your list to reject emails from everyone and the text to your response which says that this list has been temporarily suspended. There should be templates to configure the text sent when a message is rejected. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking) --===============1648714528743903757==-- From paul@arenson.org Sat Aug 31 16:27:38 2019 From: paul@arenson.org To: mailman-users@mailman3.org Subject: [MM3-users] Trying to configure a list (hosted) Date: Sat, 31 Aug 2019 16:27:34 +0000 Message-ID: <156726885499.6728.5713325100932773954@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2427312940657405398==" --===============2427312940657405398== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Is there a how to on how to configure a list? For example, using a hosted option, I see this menu: Subscription requests Held messages Users Templates Settings Mass operations = Banned addresses Header filters And cling on settings, for example. I have already removed my list from the l= ist of lists on the server since I want my website users to only see my list.= They can either do that here https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogressi= ve.org/ or here https://list.tokyoprogressive.org/accounts/signup/ I actually do not WANT people to join without being able to use the web inter= face because it is intended to be a discussion list. So the option to subscr= ibe without creating an account. is confusing to me, which is why I prefer th= e latter. BUT...using a test of signing up myself (using 3 other email addresses I have= ), some using the subscription option and some using the bottom one (no accou= nt), all the email addresses end up in my members list and non end up in my n= on members list. (So I am wondering what a non member is. I had thought it was someone who sig= ned up without registering (just name, no password), but if so i wonder why a= ll 3 of my addresses end up in the members place. Lastly, I want to configure it as a discussion list. However, I do not see th= at option, which was clear in MAILMAN 2. (And I understand that if someone registers without making an account, I cann= ot set them myself to have an account enabling them to see the archives and p= ost from the web? If it IS possible, that would be great, because the purpose= of the archives in my case is to enable better discussions than if one has o= nly to refer to their past emails.) That is about it for now, but I am stuck on this right now and a user manual = for non techie people, if it exists, would be nice. I see one for list member= s but not administrators. Maybe I am looking in the wrong place? Thanks paul --===============2427312940657405398==-- From maxking@asynchronous.in Sat Aug 31 17:34:37 2019 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: [Mailman-Developers] Re: SSL error while connecting to hyperkitty Date: Sat, 31 Aug 2019 10:34:10 -0700 Message-ID: <503810d1-3c02-402a-ab94-6a9ec3d8f2a1@www.fastmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0654746146656335405==" --===============0654746146656335405== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sat, Aug 31, 2019, at 10:20 AM, sandeep kumar wrote: > Hi Abhilash >=20 > Thanks for the reply. >=20 > Just two more answers please -:) >=20 > Can I use the sample apache.conf in example_project in my webserver virtual= host...??=20 See this thread for the apache configuration: https://lists.mailman3.org/archives/list/mailman-users(a)mailman3.org/thread/= H2LPFZGQRKQYDNTVXG4SACWVDE7CCOUG/ You'd need to adjust the paths and SSL configuration. >=20 > And what should be the configuration details to be given in uwsgi server...= ?? http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-a-wsgi-server >=20 > Regards > Sandeep >=20 >=20 > On Sat, Aug 31, 2019 at 10:25 PM Abhilash Raj w= rote: >> __ >> On Sat, Aug 31, 2019, at 8:49 AM, sandeep kumar wrote: >>> Hi Abhilash >>>=20 >>> Thanks for your reply. -:) >>>=20 >>> We are using apache httpd as webserver to redirect. >>>=20 >>> the proxy pass in webserver is=20 >>>=20 >>> ProxyPass / http://localhost:8000 >>> ReverseProxyPass / http://localhost:8000 >>=20 >>=20 >> Can you put `base_url: http://localhost:8000/hyperkitty` in your mailman-h= yperkitty.cfg and see that it works? :) >>=20 >> This should not try any funny SSL redirection. >>=20 >>> I don't have idea of deploying this in production, so I just went on sear= ching and I found wsgi (say uwsgi) is required to send the requests from webs= erver to mailman. Correct me if I am wrong. >>>=20 >>> I have few queries listed below. Please reply to them. >>>=20 >>> Should I use the wsgi.py present in the directory of mailman-suite ...?? = >>=20 >> Yes, that is the one which is supposed to be used. >>=20 >>>=20 >>> What should be the ProxyPass ..?? Where should the first hit go from webs= erver ---> uwsgi ---> ?? >>=20 >> uwsgi is web server running Mailman's web componenet. It doesn't need to h= it anything. You can restart it directly when you want to restart Mailman's w= eb component, you don't need to do anything to your web server (httpd) for th= is. >>=20 >>=20 >>=20 >>>=20 >>> Can we run "python manage.py runserver" every time to start mailman suite= ..?? Can we make mailman-suite start/stop just by restarting the HTTPD..?? >>=20 >>=20 >> No, use a wsgi server, like uwsgi or gunicorn to run mailman-suote. `pytho= n manage.runserver` is a command used during development shouldn't be used at= all in prod. >>=20 >>>=20 >>> What should be the entry in Hyperkitty.cfg file after all the above steps= ..?? I mean at the end >>>=20 >>> Please reply to the above queries. Thanks for your help >>> Regards >>> Sandeep >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>> On Sat, Aug 31, 2019 at 8:45 PM Abhilash Raj = wrote: >>>> On Sat, Aug 31, 2019, at 1:36 AM, sandeep kumar wrote: >>>> > Hi Team >>>> >=20 >>>> > Iam seeing following errors while mailman is trying to archive in >>>> > mailman.log >>>> >=20 >>>> >=20 >>>> > This is my base URL in mailman-hyperkitty.cfg >>>> >=20 >>>> > base_url: http://localhost/hyperkitty >>>>=20 >>>> Are you sure this is the URL? this is http and Mailman shouldn't try to = connect to this using HTTPS. >>>>=20 >>>> Is your web server configured to redirect all HTTP traffic to HTTPS? If = that is the case, then it is going to fail. >>>>=20 >>>> Which wsgi server are you using? uwsgi? >>>>=20 >>>> Can you also show your ProxyPass configuration? >>>>=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> >=20 >>>> > *During handling of the above exception, another exception >>>> > occurred:Traceback (most recent call last): File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/adapters.py", >>>> > line 449, in send timeout=3Dtimeout File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/urllib3-1.24.1-p= y3.6.egg/urllib3/connectionpool.py", >>>> > line 638, in urlopen _stacktrace=3Dsys.exc_info()[2]) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/urllib3-1.24.1-p= y3.6.egg/urllib3/util/retry.py", >>>> > line 398, in increment raise MaxRetryError(_pool, url, error or >>>> > ResponseError(cause))urllib3.exceptions.MaxRetryError: >>>> > HTTPSConnectionPool(host=3D'domain.com ', port=3D44= 3):=20 >>>> > Max >>>> > retries exceeded with url: >>>> > /hyperkitty/api/mailman/archive?key=3DSecretArchiverAPIKey (Caused by >>>> > SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate=20 >>>> > verify >>>> > failed (_ssl.c:841)'),))During handling of the above exception, another >>>> > exception occurred:Traceback (most recent call last): File >>>> > "/var/lib/mailman/mailman-hyperkitty/mailman_hyperkitty/__init__.py", = >>>> > line >>>> > 154, in _archive_message url =3D self._send_message(mlist, msg) File >>>> > "/var/lib/mailman/mailman-hyperkitty/mailman_hyperkitty/__init__.py", = >>>> > line >>>> > 201, in _send_message files=3D{"message": ("message.txt",=20 >>>> > message_text)}) >>>> > File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/api.py", >>>> > line 116, in post return request('post', url, data=3Ddata, json=3Djson, >>>> > **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/api.py", >>>> > line 60, in request return session.request(method=3Dmethod, url=3Durl, >>>> > **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/sessions.py", >>>> > line 533, in request resp =3D self.send(prep, **send_kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/sessions.py", >>>> > line 668, in send history =3D [resp for resp in gen] if allow_redirects >>>> > else [] File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/sessions.py", >>>> > line 668, in history =3D [resp for resp in gen] if >>>> > allow_redirects else [] File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/sessions.py", >>>> > line 247, in resolve_redirects **adapter_kwargs File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/sessions.py", >>>> > line 646, in send r =3D adapter.send(request, **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-= py3.6.egg/requests/adapters.py", >>>> > line 514, in send raise SSLError(e, >>>> > request=3Drequest)requests.exceptions.SSLError: >>>> > HTTPSConnectionPool(host=3Ddomain.com ', port=3D443= ): Max >>>> > retries exceeded with url: >>>> > /hyperkitty/api/mailman/archive?key=3DSecretArchiverAPIKey (Caused by >>>> > SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate=20 >>>> > verify >>>> > failed (_ssl.c:841)'),))* >>>> >=20 >>>> >=20 >>>> > Rgrds >>>> > Sandeep >>>> >=20 >>>> > On Sat, Aug 31, 2019 at 10:20 AM sandeep kumar >>>> > wrote: >>>> >=20 >>>> > > Team any help >>>> > > >>>> > > Sent from my iPhone >>>> > > >>>> > > > On 30-Aug-2019, at 11:18 PM, sandeep kumar >>>> > > wrote: >>>> > > > >>>> > > > Hi Team >>>> > > > >>>> > > > Iam using httpd to work with ssl on mailman 3 using proxy pass. >>>> > > > >>>> > > > After this configuration Iam not able to connect to hyperkitty. It= is >>>> > > throwing ssl certificate error in mailman.log file. >>>> > > > >>>> > > > What should be the configuration of hyperkitty while using https in >>>> > > mailman..? >>>> > > > >>>> > > > Please help me with this Iam struck here from past 4 days >>>> > > > >>>> > > > Rgrds >>>> > > > Sandeep >>>> > > > >>>> > > > Sent from my iPhone >>>> > > >>>> >=20 >>>> >=20 >>>> > --=20 >>>> > Regards >>>> > Sandeep Kumar >>>> > +91-9642669192 >>>> > _______________________________________________ >>>> > Mailman-Developers mailing list -- mailman-developers(a)python.org >>>> > To unsubscribe send an email to mailman-developers-leave(a)python.org >>>> > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ >>>> > Mailman FAQ: https://wiki.list.org/x/AgA3 >>>> >=20 >>>> > Security Policy: https://wiki.list.org/x/QIA9 >>>> > >>>>=20 >>>> --=20 >>>> thanks, >>>> Abhilash Raj (maxking) >>>=20 >>>=20 >>> --=20 >>> Regards >>> Sandeep Kumar >>> +91-9642669192 >>>=20 >>=20 >> -- >> thanks, >> Abhilash Raj (maxking) >>=20 >>=20 >=20 >=20 > --=20 > Regards > Sandeep Kumar > +91-9642669192 >=20 -- thanks, Abhilash Raj (maxking) --===============0654746146656335405==--