Search results for "2021" - Mailman-users

HyperKitty archiver <h1>Server Error (500</h1>

by Daniel Erlendson

Hello all, I'm getting the following in the logs in our MM server: Nov 01 14:00:17 2021 (26843) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <h1>Server Error (500)</h1> (500) Nov 01 14:00:17 2021 (26843) Exception in the HyperKitty archiver: <h1>Server Error (500)</h1> Nov 01 14:00:17 2021 (26843) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <h1>Server Error (500)</h1> which is mirrored in the mailman-web.log with this 21:57:07 [Q] INFO Enqueued 1962530 21:57:08 [Q] INFO Process-1:36 processing [sender_mailman_id] 21:57:08 [Q] INFO Processed [sender_mailman_id] ERROR 2021-11-01 21:57:07,969 17847 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): plus a bunch of python errors and this: ValueError: A string literal cannot contain NUL (0x00) characters. ERROR 2021-11-01 21:57:07,969 17847 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): We are on v3.1 on Ubuntu 18.04. I do have a project beginning to move to Ubuntu 20.04 eventually. For now, I'm struggling to find the resolution to this error. I've looked at the site here, did a rebuild on the whoosh index, I've found and tested the suggestions to add a localhost non-https in apache for HyperKitty, I've edited HyperKitty to be https rather than HTTP, none of these settings / changes seem to resolve the issue. Oddly for all intents and purposes, the server appears to run fine, the archive might be a bit slow but it doesn't seem to have issues other than the constant errors coming into the admin emails. Happy to post any configs or detail anything, appreciate any replies. Respectfully,

3 years, 8 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Fri, May 14, 2021 at 11:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 12:50 PM, Odhiambo Washington wrote: > > On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 5/14/21 5:02 AM, Odhiambo Washington wrote: > >>> On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > >>> > >>>> > >>>> > >>>> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > >>>> wrote: > >>>> > >>>> /bin/sh: sass: Permission denied* > ... > >> Try `which sass` > >> > > > > root@gw:/usr/home/wash # su mailman3 > > (venv) [mailman3@gw /usr/home/wash]$ which sass > > (venv) [mailman3@gw /usr/home/wash]$ > > > > There is no sass. > > > There has to be. You can't get a permissions error on sass if it doesn't > exist (well, maybe if you don't have permission to search a > superordinate directory, but that's unlikely). > > Try `find /usr -name sass` > /usr/local/include/sass That is the only thing found that is in the base system. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

Re: Postorius no connection to REST API

by Richard Rosner

I included now: SSLProxyEngine on SSLProxyMachineCertificateChainFile /etc/ssl/certs/dfnca.pem (same as SSLCertificateChainFile, I hope that's correct) SSLProxyMachineCertificateFile /etc/ssl/certs/lists.domain.de.cert_key.pem (basically just copied SSLCertificateFile and SSLCertificateKeyFile into one file; and since the keyfile starts with "BEGIN RSA PRIVATE KEY" it seems to fulfill the criteria). SSLProxyProtocol all -SSLv3 -TLSv1 -TLSv1.1 but no change. From apache error log: [Sun Aug 15 09:19:52.318582 2021] [core:notice] [pid 19706:tid 140315143705728] AH00094: Command line: '/usr/sbin/apache2' [Sun Aug 15 09:19:52.732381 2021] [proxy_http:error] [pid 19707:tid 140314912167680] (20014)Internal error (specific information not available): [client 37.201.214.82:9292] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:19:53.929213 2021] [proxy_http:error] [pid 19707:tid 140314912167680] (20014)Internal error (specific information not available): [client 37.201.214.82:9292] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:19:59.463974 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:03.328416 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:04.605617 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9311] AH01102: error reading status line \ from remote server 127.0.0.1:8000 [Sun Aug 15 09:20:10.178979 2021] [proxy_http:error] [pid 19708:tid 140314828240640] (20014)Internal error (specific information not available): [client 37.201.214.82:9305] AH01102: error reading status line \ from remote server 127.0.0.1:8000

3 years, 10 months

Re: Out runner not sending emails, stuck on recvFrom.

by Mark Sapiro

On 10/20/21 11:03 AM, 01ste02(a)gmail.com wrote: > My mta is logging a connection, which times out every three minutes. The strace for the out runner shows the following: > ... > connect(21, {sa_family=AF_INET, sin_port=htons(465), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 > recvfrom(21, > > And the mailman smtp-log shows: > > Oct 20 19:58:04 2021 (1262375) <163474270655.1243104.7078333516263200191@xxx> delivery to xxx@xxx failed with code 444, Connection unexpectedly closed > Oct 20 19:58:04 2021 (1262375) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f219bf93310> > Oct 20 19:58:04 2021 (1262375) Connecting to 127.0.0.1:465 Is the local MTA listening on 127.0.0.1:465? If so, is some firewall blocking that connect? We are waiting for a response from the MTA to the connect and it never comes, Even if [mta] settings like smtp_user: smtp_pass: smtp_secure_mode: smtp_verify_cert: smtp_verify_hostname: are somehow not correct or appropriate, we don't seem to be getting that far. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: django request error

by github＠lunique.fr

A new update in Debian 10 for apache2 relaxes the behaviour ... I haven't tested if reverting the syntax works but the new syntax described above is still working. ``` apache2 (2.4.38-3+deb10u7) buster-security; urgency=medium * Fix possible NULL dereference or SSRF in forward proxy configurations (CVE-2021-44224) * lua: improve error handling (Closes: CVE-2021-44790) * mod_proxy_uwsgi: Remove duplicate slashes at the beginning of PATH_INFO (relaxes the behaviour introduced by the CVE-2021-36160 fix) -- Yadd <yadd(a)debian.org> Tue, 21 Dec 2021 17:50:43 +0100 ```

3 years, 6 months

Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > On 8/12/21 12:01 AM, Richard Rosner wrote: > > All the mailman processes should run as list and all mailman related > things should be readable and writable by list. I have set both /usr/bin/uwsgi-core and /usr/share/mailman3-web to be owned by lists, no changes yet. But at least mailman3-web now can actually be started without throwing an error. > > Yes, I meant if you want those URLs to work, you have to pass them to > uwsgi. You don't need all of them. mailman2 and postorius are > synonyms as are archives and hyperkitty > However, you could try using TCP to communicate with uwsgi rather than a > Unix socket. > This means replacing > uwsgi-socket = /run/mailman3-web/uwsgi.sock > with > uwsgi-socket = 0.0.0.0:8000 > in your uwsgi.ini file and using directives like > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/django" "http://127.0.0.1:8000/django" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > > > in apache. I tried that switch and got ERR_HTTP2_PROTOCOL_ERROR. From the apache log: [Fri Aug 13 16:08:38.871462 2021] [mpm_event:notice] [pid 27808:tid 140008999584896] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 \ Python/3.7 configured -- resuming normal operations [Fri Aug 13 16:08:38.871603 2021] [core:notice] [pid 27808:tid 140008999584896] AH00094: Command line: '/usr/sbin/apache2' [Fri Aug 13 16:08:42.881615 2021] [proxy_http:error] [pid 27809:tid 140008751261440] (20014)Internal error (specific information not available): [c\ lient 134.61.99.193:36563] AH01102: error reading status line from remote server 127.0.0.1:8000 [Fri Aug 13 16:08:44.072665 2021] [proxy_http:error] [pid 27809:tid 140008751261440] (20014)Internal error (specific information not available): [c\ lient 134.61.99.193:36563] AH01102: error reading status line from remote server 127.0.0.1:8000 [Fri Aug 13 16:08:49.277000 2021] [proxy_http:error] [pid 27810:tid 140008709297920] (20014)Internal error (specific information not available): [c\ lient 134.61.99.193:36696] AH01102: error reading status line from remote server 127.0.0.1:8000 I set them all to https. which solved the https error. But I still get Error 500. From apache log: [Fri Aug 13 15:47:58.833305 2021] [mpm_event:notice] [pid 26720:tid 139986206332032] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 \ Python/3.7 configured -- resuming normal operations [Fri Aug 13 15:47:58.833436 2021] [core:notice] [pid 26720:tid 139986206332032] AH00094: Command line: '/usr/sbin/apache2' [Fri Aug 13 15:49:41.673108 2021] [ssl:error] [pid 26722:tid 139985899259648] [remote 127.0.0.1:8000] AH01961: SSL Proxy requested for lists.fsmuw.\ rwth-aachen.de:443 but not enabled [Hint: SSLProxyEngine] [Fri Aug 13 15:49:41.905868 2021] [proxy:error] [pid 26722:tid 139985899259648] AH00961: https: failed to enable ssl support for 127.0.0.1:8000 (12\ 7.0.0.1) [Fri Aug 13 15:59:25.049708 2021] [ssl:error] [pid 26722:tid 139985899259648] [remote 127.0.0.1:8000] AH01961: SSL Proxy requested for lists.fsmuw.\ rwth-aachen.de:443 but not enabled [Hint: SSLProxyEngine] [Fri Aug 13 15:59:25.059217 2021] [proxy:error] [pid 26722:tid 139985899259648] AH00961: https: failed to enable ssl support for 127.0.0.1:8000 (12\ 7.0.0.1) From the mailman-web log: uwsgi socket 0 bound to TCP address 0.0.0.0:8000 fd 4 Python version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] Python main interpreter initialized at 0x561db180adf0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** WSGI app 0 (mountpoint='') ready in 3 seconds on interpreter 0x561db180adf0 pid: 26851 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 26851) spawned uWSGI worker 1 (pid: 26861, cores: 2) [uwsgi-daemons] spawning "python3 manage.py qcluster" (uid: 38 gid: 38) 13:48:04 [Q] INFO Q Cluster-26864 starting. 13:48:04 [Q] INFO Process-1:1 ready for work at 26866 13:48:04 [Q] INFO Process-1:2 ready for work at 26867 13:48:04 [Q] INFO Process-1:3 monitoring at 26868 13:48:04 [Q] INFO Process-1 guarding cluster at 26865 13:48:04 [Q] INFO Q Cluster-26864 running. 13:48:04 [Q] INFO Process-1:4 pushing tasks at 26869 So at least that seems to be fine now > I am not familiar enough with apache/uwsgi configuration to be of more > help. Have you seen https://wiki.list.org/x/12812344 and have you asked > Debian for help with their package. They are the ones who should be > supporting it https://www.debian.org/support. I'll open an error report on mailman3-web. Maybe they have some input to that.

3 years, 10 months

Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark for your immediate response. The below are the tracebacks I could find in the mailman log. *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback (most recent call last): File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line 59, in process addrs = getaddresses(msg.get_all(header, [])) File "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* In the shunt file, I see something like this as below in CC while To is good: *Cc: =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* Also, I came to know that two of the recipients in CC block have their mail ID display name in their local language. While I am not sure, I doubt if it could be the issue of getting shunted. Please confirm and suggest any solution. On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: > > > > Is there any chance to find out the reason for shunting of the > > mails through any means ? > > > > > Look in Mailman's var/logs/mailman.log for the tracebacks associated > with the shunted messages. > > -- > Mark Sapiro <mark(a)msapiro.net> 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years

Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Dear Mark, FYI, I observed this issue with the postfix that receives the mails from the previous MTA and hands it over to the mailman. But I fixed at postfix by upgrading it to the version postfix 3. But still Mailman is not able to understand Hindi (Indian local language) in which language the display names of the email ids are there. So, now what to do at Mailman so that it can also understand local languages or any work around or other alternate solutions for these sort of cases. On Fri, Jun 18, 2021 at 4:04 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Thank you Mark for your immediate response. > > The below are the tracebacks I could find in the mailman log. > > > > > > > > > > > > > > > > > *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: > expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback > (most recent call last): File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in > _one_iteration self._process_one_file(msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in > _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in > _dispose process(mlist, msg, msgdata, pipeline) File > "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in > process handler.process(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line > 59, in process addrs = getaddresses(msg.get_all(header, [])) File > "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = > COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str > instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: > 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* > > In the shunt file, I see something like this as below in CC while To is > good: > > > > > > > > > *Cc: > =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* > > Also, I came to know that two of the recipients in CC block have their > mail ID display name in their local language. While I am not sure, I doubt > if it could be the issue of getting shunted. > > Please confirm and suggest any solution. > > > > On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: >> > >> > Is there any chance to find out the reason for shunting of the >> > mails through any means ? >> > >> >> >> Look in Mailman's var/logs/mailman.log for the tracebacks associated >> with the shunted messages. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> 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/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years

Re: Does anyone have a working DKIM/ARC configuration?

by Philip Colmer

An update on what I've changed and what works and what still doesn't work ... I've switched off the ARC/DKIM processing within Mailman 3. I've installed OpenARC as a second milter for Postfix, so all DKIM/ARC processing is now being done by Postfix. If I send a test email manually from the Mailman 3 server to a test email address, it seems to be valid: Delivered-To: philip.colmer(a)codelinaro.org Received-SPF: pass (zohomail.com: domain of mm3.lavasoftware.org designates 3.230.84.86 as permitted sender) client-ip=3.230.84.86; envelope-from=philip.colmer(a)mm3.lavasoftware.org; helo=mm3.lavasoftware.org; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of mm3.lavasoftware.org designates 3.230.84.86 as permitted sender) smtp.mailfrom=philip.colmer(a)mm3.lavasoftware.org; arc=pass (i=1 dmarc=pass fromdomain=mm3.lavasoftware.org) ARC-Seal: i=2; a=rsa-sha256; t=1631777446; cv=pass; d=zohomail.com; s=zohoarc; b=Sf9f7Vc4utokJHB/AhzIBiYUQABBaJmLA5x/oY3fq5yPXxuAW+a5qed5oCPJEHzwopQXN8u/4hzxFa3+8sXJC5tIYMiuG4dr9EyW+oxSMz6vveiiybchxVGMqw/i9gPT5CWT4Q6eHMdiu/3AsBXdwTBqHZy61y6OACk4BbpI8FA= ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1631777446; h=Date:From:Message-ID:Subject:To; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=BDNvyCqYEUnD61N5OAtR3W/67HOciIm0eLZdMB4aiigaRO8rlalyM5u5Y41ADg5GJl5gyE9LgkQxpGhQfDlTAD7NvEjsh/LGElk+Esxcf7LFxhRDc9i4MqZvgXu30boDquKFQrSJVZPlpoCY3wOLkKa0F6PKz9hKGLvx8OxweOk= ARC-Authentication-Results: i=2; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of mm3.lavasoftware.org designates 3.230.84.86 as permitted sender) smtp.mailfrom=philip.colmer(a)mm3.lavasoftware.org; arc=pass (i=1 dmarc=pass fromdomain=mm3.lavasoftware.org) Return-Path: <philip.colmer(a)mm3.lavasoftware.org> Received: from mm3.lavasoftware.org (mm3.lavasoftware.org [3.230.84.86]) by mx.zohomail.com with SMTPS id 1631777446561547.6433787962904; Thu, 16 Sep 2021 00:30:46 -0700 (PDT) Received: by mm3.lavasoftware.org (Postfix, from userid 1000) id 11CC0BE198; Thu, 16 Sep 2021 07:30:45 +0000 (UTC) ARC-Seal: i=1; a=rsa-sha256; d=mm3.lavasoftware.org; s=mailman; t=1631777445; cv=none; b=ld42BgcROQcdXFNd9MorNvDrjS/EDoFKRFfCJBolfRF3Cg093kCAD8/3lIf5E7v8/9I/qePgswN9BgLbbqxr1WvIlJBZP7aBdULMZ5NlfGDuR7q3TA14hWaaS2AFsYp6rVDPSuyBl8Nl86zHfWvNDsg8ZVkDQSDvy+2BMKKRkFY= ARC-Message-Signature: i=1; a=rsa-sha256; d=mm3.lavasoftware.org; s=mailman; t=1631777445; c=relaxed/relaxed; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; h=DKIM-Signature:To:Subject:X-Mailer:Message-Id:Date:From; b=SpnEUbFx9bzXUUvWy3symoTeZlDzDPhfcoPVsvHN1zlh3alvvADoi2/UUTRF0l+bX6Iagtgn8eswO9x4Z5YnJtak3bYqd2p59xf9oMswiUvR0piY4sVx3WEE5rqQMibRJrzBmQqTan2xsmOxpCmWSgbv2o+yI+CYg++5pXEDjC4= ARC-Authentication-Results: i=1; mm3.lavasoftware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mm3.lavasoftware.org; s=mailman; t=1631777445; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; h=To:Subject:Date:From:From; b=VizzJTtzye+R1HGgm7JcpB/a/KqImAjxyDLUvLucTLiquO0xjwD1HCR6N8UXDpV5t nwNULTm0DhjyBrbZMs7jP0hTyS92PXOsIela2IypJUV3KGCagi4+ax6THHlkMgHNv3 zNnTDhTjJPUyGHKwBu9g4vT0SRaVV4VFuQGuBSBw= To: <philip.colmer(a)codelinaro.org> Subject: Testing X-Mailer: mail (GNU Mailutils 3.7) Message-Id: <20210916073045.11CC0BE198(a)mm3.lavasoftware.org> Date: Thu, 16 Sep 2021 07:30:45 +0000 (UTC) From: Ubuntu <philip.colmer(a)mm3.lavasoftware.org> X-ZohoMail-DKIM: pass (identity @mm3.lavasoftware.org) X-ZohoMail-Owner: <20210916073045.11CC0BE198(a)mm3.lavasoftware.org>+zmo_0_philip.colmer(a)mm3.lavasoftware.org However, if I manually send an email from the Mailman 3 server to a list on the same server with the external email address as a subscriber to the list, the headers are no longer valid: Delivered-To: philip.colmer(a)codelinaro.org Received-SPF: pass (zohomail.com: domain of mm3.lavasoftware.org designates 3.230.84.86 as permitted sender) client-ip=3.230.84.86; envelope-from=test-bounces+philip.colmer=codelinaro.org(a)mm3.lavasoftware.org; helo=mm3.lavasoftware.org; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of mm3.lavasoftware.org designates 3.230.84.86 as permitted sender) smtp.mailfrom=test-bounces+philip.colmer=codelinaro.org(a)mm3.lavasoftware.org; arc=fail (Bad Signature) Return-Path: <test-bounces+philip.colmer=codelinaro.org(a)mm3.lavasoftware.org> Received: from mm3.lavasoftware.org (mm3.lavasoftware.org [3.230.84.86]) by mx.zohomail.com with SMTPS id 1631778422868332.996514603768; Thu, 16 Sep 2021 00:47:02 -0700 (PDT) Received: from ip-172-31-73-169.ec2.internal (localhost [127.0.0.1]) by mm3.lavasoftware.org (Postfix) with ESMTP id A710EBDF0B for <philip.colmer(a)codelinaro.org>; Thu, 16 Sep 2021 07:47:01 +0000 (UTC) Received: by mm3.lavasoftware.org (Postfix, from userid 1001) id B116FBE198; Thu, 16 Sep 2021 07:46:59 +0000 (UTC) ARC-Seal: i=2; a=rsa-sha256; d=mm3.lavasoftware.org; s=mailman; t=1631778421; cv=none; b=Yj1zJeE+QqxFKwCi6Bmr4kGpoEAF3blzJEnimK/whxz9TJUQEzfTMTHV4i+ENdF79Bm++wJTSBfASZGxtLYWLjuf1WwIgs/CPmJI5vFLFpVvPIlCPzoUcKpZ2rPpanbI1w1ZD5R9L5TYqLKk2X0LBX8h+2m2lX12QPqTnDM/omI= ARC-Message-Signature: i=2; a=rsa-sha256; d=mm3.lavasoftware.org; s=mailman; t=1631778421; c=relaxed/relaxed; bh=7okxo56bDMUeGIn5d8B+1XloabAmDiswrokeAElWGvo=; h=DKIM-Signature:ARC-Message-Signature:ARC-Authentication-Results: Received:To:X-Mailer:Message-Id:Date:Message-ID-Hash: X-Message-ID-Hash:X-MailFrom:X-Mailman-Rule-Misses: X-Mailman-Version:Precedence:Subject:List-Id:Archived-At: List-Archive:List-Help:List-Owner:List-Post:List-Subscribe: List-Unsubscribe:From:Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding; b=nhhYvCuj3zPh1mEVm6BOlhNeekhBeKb2l9SIMRqZqGp8VYG6xYt8754K8qjULqn2r92Vzux1lFXqnaT0ezdGI3CADLN9jgB6NVZzZYZBigh3yAtNWlr4aT6m0wSDVUxfJbAaYFXDVLuDmzTEJfEWqPAzNmHOl7rXVqBN5FvMeow= ARC-Authentication-Results: i=2; mm3.lavasoftware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mm3.lavasoftware.org; s=mailman; t=1631778421; bh=7okxo56bDMUeGIn5d8B+1XloabAmDiswrokeAElWGvo=; h=To:Date:Subject:List-Id:List-Archive:List-Help:List-Owner: List-Post:List-Subscribe:List-Unsubscribe:From:Reply-To:From; b=mLPHnhHmIOkzYTVq3NqBQepuvzC/Df3lKTYZCaB1bmpQ6PeOOz5g98HzbVVlpX9uw afblicz/ISDs131pgU1qvHQBzWq6lKQmMSwrJzZ49CCBeksfxA9tIq4mNv4DUu09io bMk/0uAgDSXs63mAXy6qw/JvXVTDgYMv00yZ+U2U= ARC-Seal: i=1; a=rsa-sha256; d=mm3.lavasoftware.org; s=mailman; t=1631778419; cv=none; b=SiDr6n4UWUHhjTPhxl06MHsElI9ZUTD8B7qLcGf1Kdfbek6OIbPt+DapUSRkRD20bKQXeCdh5O5RdhIZPOZYvYAOclMlOtyfJb5hKNTqO5hXrnVqJ0fiRMgbjQHIM2LKP4qfYVLMXkYHR7U8hNPuw2PqapiXgK8oSddP8JNMKVE= ARC-Message-Signature: i=1; a=rsa-sha256; d=mm3.lavasoftware.org; s=mailman; t=1631778419; c=relaxed/relaxed; bh=tm5RPPTfV2Opc+Qi0lNHW09jqu2Otv/5tnp8ODwYPGM=; h=To:Subject:X-Mailer:Message-Id:Date:From; b=QnXpv4s3JciqcxnUUoumLz3GrXOh20fXnyCprPzXm5mILfC5hCLhe8sCX7CQxbsl/gRDpvQuS0DpxezG3rdvtc7yofsJ+K/oPOMHFAjjNccvmF3MUTEdPrJ8S0qNU6AWl2ApT96fi2ZtgFsJeX2dcmhExpbOWhw6p5Ap/o1gbSA= ARC-Authentication-Results: i=1; mm3.lavasoftware.org To: <test(a)mm3.lavasoftware.org> X-Mailer: mail (GNU Mailutils 3.7) Message-Id: <20210916074659.B116FBE198(a)mm3.lavasoftware.org> Date: Thu, 16 Sep 2021 07:46:59 +0000 (UTC) Message-ID-Hash: XBBXTI6IJ6NHUBSN5LLI7DNXWE6IOFZI X-Message-ID-Hash: XBBXTI6IJ6NHUBSN5LLI7DNXWE6IOFZI X-MailFrom: pjctest(a)papillonpictures.co.uk X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.4 Precedence: list Subject: [Test] Direct test List-Id: <test.mm3.lavasoftware.org> Archived-At: <> List-Archive: <> List-Help: <mailto:test-request@mm3.lavasoftware.org?subject=help> List-Owner: <mailto:test-owner@mm3.lavasoftware.org> List-Post: <mailto:test@mm3.lavasoftware.org> List-Subscribe: <mailto:test-join@mm3.lavasoftware.org> List-Unsubscribe: <mailto:test-leave@mm3.lavasoftware.org> From: pjctest--- via Test <test(a)mm3.lavasoftware.org> Reply-To: pjctest(a)papillonpictures.co.uk MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-ZohoMail-DKIM: pass (identity @mm3.lavasoftware.org) Note that I've had to use different "From" addresses in my testing because I cannot add a "local" email address (e.g. pjctest(a)mm3.lavasoftware.org) as a user to Mailman 3. The Postfix configuration for the milters is: milter_default_action = accept milter_protocol = 2 smtpd_milters = inet:localhost:8892, unix:/var/run/openarc/openarc.sock non_smtpd_milters = inet:localhost:8892, unix:/var/run/openarc/openarc.sock I am completely stumped about this. Regards Philip

3 years, 9 months

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/13/21 7:18 AM, Richard Rosner wrote: > > I set them all to https. which solved the https error. But I still get Error 500. >>From apache log: > [Fri Aug 13 15:47:58.833305 2021] [mpm_event:notice] [pid 26720:tid 139986206332032] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 \ > Python/3.7 configured -- resuming normal operations > [Fri Aug 13 15:47:58.833436 2021] [core:notice] [pid 26720:tid 139986206332032] AH00094: Command line: '/usr/sbin/apache2' > [Fri Aug 13 15:49:41.673108 2021] [ssl:error] [pid 26722:tid 139985899259648] [remote 127.0.0.1:8000] AH01961: SSL Proxy requested for lists.fsmuw.\ > rwth-aachen.de:443 but not enabled [Hint: SSLProxyEngine] > [Fri Aug 13 15:49:41.905868 2021] [proxy:error] [pid 26722:tid 139985899259648] AH00961: https: failed to enable ssl support for 127.0.0.1:8000 (12\ > 7.0.0.1) > [Fri Aug 13 15:59:25.049708 2021] [ssl:error] [pid 26722:tid 139985899259648] [remote 127.0.0.1:8000] AH01961: SSL Proxy requested for lists.fsmuw.\ > rwth-aachen.de:443 but not enabled [Hint: SSLProxyEngine] > [Fri Aug 13 15:59:25.059217 2021] [proxy:error] [pid 26722:tid 139985899259648] AH00961: https: failed to enable ssl support for 127.0.0.1:8000 (12\ > 7.0.0.1) You need SSLProxyEngine on and possibly one or more of the SSLProxyMachineCertificate* directives in your apache config to proxy via https. See <https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslproxymachinecertifica…> et seq. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Mailman-users search results for query "2021"