From brunol@agro.uba.ar Thu Jan 2 16:50:51 2020 From: brunol@agro.uba.ar To: mailman-users@mailman3.org Subject: [MM3-users] Re: Migration from 2.1 to 3 Date: Thu, 02 Jan 2020 16:50:48 +0000 Message-ID: <157798384812.26384.13312159455319862186@mailman.iad1.psf.io> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8640062977930203388==" --===============8640062977930203388== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable That message is also present when i post to the other list (the one that is n= ot imported from 2.1) and the message is delivered, that's odd. It is listening on 127.0.0.1 on port 25 and i've tried changing it to an uppe= r port (2525) with no luck. Thanks for the help so far, i'll keep digging. --===============8640062977930203388==-- From s.maddox@lantizia.me.uk Thu Jan 2 23:16:28 2020 From: Steven Maddox To: mailman-users@mailman3.org Subject: [MM3-users] Mark a list to prevent it being shown as inactive on HyperKitty Date: Thu, 02 Jan 2020 23:16:22 +0000 Message-ID: <9ea8d129-9b31-79b6-4a7b-e2bb252551cf@lantizia.me.uk> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4064661370320063129==" --===============4064661370320063129== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Lo Folks, Subject says it all really, is there anyway to mark a list as one which should never be shown as inactive on the HyperKitty web interface? We've got a list which we consider to be "active", it's just that there might be the odd month here or there which it won't show activity. Failing having such a setting (as described above)... maybe there is a way of changing what it considers to be 'inactive' (I'm assuming that it is 30 days?). At the moment (in order to counteract commit 156f4cda) I've dropped this into templates/hyperkitty/bottom.html to uncheck the "Hide Inactive" checkbox... but that doesn't actually stop HyperKitty from considering it inactive - just shows it in dark grey. -- Steven Maddox Lantizia --===============4064661370320063129==-- From brunol@agro.uba.ar Fri Jan 3 15:55:44 2020 From: brunol@agro.uba.ar To: mailman-users@mailman3.org Subject: [MM3-users] Re: Migration from 2.1 to 3 Date: Fri, 03 Jan 2020 15:55:40 +0000 Message-ID: <157806694071.26381.371752329885419771@mailman.iad1.psf.io> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2526469803987729480==" --===============2526469803987729480== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I've found something, the imported list preferred language is Spanish (es), c= hanging it to 'en' : mailman shell -l lispruebas(a)mailman3.agro.uba.ar m._preferred_language 'es' m._preferred_language =3D 'en' seems to fix everything, as soon as i hit ctrl+d the messages are delivered p= roperly. Even when i set it to french which has the same charset as spanish it works a= s expected. Any ideas why? --===============2526469803987729480==-- From maxking@asynchronous.in Fri Jan 3 20:59:52 2020 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mark a list to prevent it being shown as inactive on HyperKitty Date: Fri, 03 Jan 2020 12:59:23 -0800 Message-ID: <91238e1f-9ce9-4be4-9a28-9a5147d8efad@www.fastmail.com> In-Reply-To: <9ea8d129-9b31-79b6-4a7b-e2bb252551cf@lantizia.me.uk> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6007173609876970172==" --===============6007173609876970172== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 2, 2020, at 3:16 PM, Steven Maddox wrote: > Lo Folks,=09 > =09 > Subject says it all really, is there anyway to mark a list as one which > should never be shown as inactive on the HyperKitty web interface?=09 > =09 > We've got a list which we consider to be "active", it's just that there > might be the odd month here or there which it won't show activity.=09 > =09 > Failing having such a setting (as described above)... maybe there is a > way of changing what it considers to be 'inactive' (I'm assuming that it > is 30 days?).=09 > =09 > At the moment (in order to counteract commit 156f4cda) I've dropped this > into templates/hyperkitty/bottom.html to uncheck the "Hide Inactive" > checkbox... but that doesn't actually stop HyperKitty from considering > it inactive - just shows it in dark grey.=09 > =09 > =09 Firstly, I think this is something that should be configurable by the adminis= trator. To show or hide the inactive lists by default. I have created an issu= e for this: https://gitlab.com/mailman/hyperkitty/issues/276 On to your question, there is currently no way to change what is considered a= n inactive list, without changing the source code of couse. The current logic to determine if a list is inactive is based on whether it h= ad any posts in "recent date" (search for "inactive" keyword in templates/hyp= erkitty/index.html and you'll find the logic to add an "inactive" class to th= e UI elements of the list).=20 What is considered a "recent date" is defined as 32 days in hyperkitty/models= /mailinglist.py#L112[1]. I think it would be reasonable to make this configur= able too, although, it would affect more things than just the list of inactiv= e lists. For example, the "Recent threads" on the MailingList's info page is = calculated based on these dates. [1]: https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/models/mail= inglist.py#L107=20 --=20 thanks, Abhilash Raj (maxking) --===============6007173609876970172==-- From mark@msapiro.net Fri Jan 3 22:01:39 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: MM3 shunting mails Date: Fri, 03 Jan 2020 14:01:27 -0800 Message-ID: <0a7c9a91-cb05-94da-340e-c207e9d4e553@msapiro.net> In-Reply-To: <157558204917.24893.6718923076932597184@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7237522826502979328==" --===============7237522826502979328== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 12/5/19 1:40 PM, ikemulder(a)hotmail.com wrote: >=20 > In the script I am filtering for 'mhonarc' ListArchivers, since the duplica= te ListArchivers always seem to be mhonarc archivers. >=20 > If this is not the appropriate place, please let me know - I would like to = get to the bottom of this :). I see you've also filed . Thank you for that. We are as puzzled as you are by this. It would help if you could detect this duplication when it happens and try to get more information. The problem is I can't see how to do that. I would start by adding some logging to the patch_put method of the ListArchivers class in mailman/rest/lists.py to log the list and the request. Then when you see the duplicate, you can check this log to see if anything suspicious happened just prior to that? --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============7237522826502979328==-- From mark@msapiro.net Fri Jan 3 22:49:08 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Migration from 2.1 to 3 Date: Fri, 03 Jan 2020 14:48:54 -0800 Message-ID: <91743e9f-5503-f49d-315c-ab6719a200e2@msapiro.net> In-Reply-To: <157806694071.26381.371752329885419771@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3143683164268965161==" --===============3143683164268965161== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/3/20 7:55 AM, brunol(a)agro.uba.ar wrote: > I've found something, the imported list preferred language is Spanish (es),= changing it to 'en' : ... > seems to fix everything, as soon as i hit ctrl+d the messages are delivered= properly. >=20 > Even when i set it to french which has the same charset as spanish it works= as expected. Any ideas why? Actually, since Mailman 3.2.1, the default charset for 'fr' is utf-8, not iso-8859-1, although I don't offhand understand why the language would affect this even if the encoding is different. In any case, at this level the message should be pure ascii with any non-ascii having been base64 or quoted_printable encoded. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============3143683164268965161==-- From mark@msapiro.net Mon Jan 6 18:02:14 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: [Mailman-Users] MM3 startup issues Date: Mon, 06 Jan 2020 10:02:03 -0800 Message-ID: <178e6ba3-186e-19e4-344e-0b4be85864ad@msapiro.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1395562111491143127==" --===============1395562111491143127== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Restoring original Subject:, and doesn't this thread belong on mailman-users(a)msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: >=20 > Thanks again, Mark! > My responses below. >=20 >> On 1/4/20 5:47 PM, Allan Hansen wrote: >>> >>> a. The server was set up with the wrong domain name (our fault), so I had= to add the =E2=80=98correct=E2=80=99 one. I had seen the command =E2=80=98Ad= d Domain=E2=80=99 in >>> the UI and thought that would do it, but Brian kindly sent me a list of a= dditional instructions, which we then implemented. That made it possible to c= reate a list in the new domain, subscribe people and post messages. However, = messages are not archived. What extra step is needed to enable archiving?=20 >> >> >> What are the setytings in Postorius -> Settings -> Archiving? >=20 > Archive policy: Private archives > Archive archivers: hyperkitty, prototype Are the messages in Mailman's var/archives/prototype/LIST(a)DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> b. When go to the server using the new domain (both before and after logg= ing in), I see not just the lists I created in the new domain, but the lists = created in the old domain. These lists of lists are domain specific and shoul= d not be listed together. That=E2=80=99s just IMHO, but not serious, as I wil= l soon get rid of anything in the old domain. So feel free to ignore this one= if this is intended, which I could see might be the case. >> >> >> Set >> >> FILTER_VHOST =3D True >> >> in settings_local.py >> >=20 > Yes, Brian told me to do the same. This is the what I wrote back: >=20 > hansen(a)rccrmail:/opt/mailman/mm$ sudo vi settings.py >=20 > Edited the setting to: > # Only display mailing-lists from the same virtual host as the webserver > FILTER_VHOST =3D True You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen(a)rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > I then logged in, but the same lists are showing. It either takes the syste= m a long time to reset or it has ignored the=20 > setting. > Just tried it again, and the lists are all showing. Do I need to manually r= ecompile the file? >=20 >> >>> c. I then moved on to the templates and added a template for the message = text to send to new subscribers. That resulted in the following error message= when I went in as moderator to approve of a new subscription: >>> >>> Something went wrong >>> Mailman REST API not available. Please start Mailman core. >> >> >> Postorius is unable to access core's REST API. Is Mailman running? >=20 > Well, I was able to post to the lists, so I assume it is. Listing at proces= ses, I see a bunch of postgres, python3, nginx, django-adminp but > nothing explicitly with a =E2=80=98mailman=E2=80=99 string. If you do `ps ax|grep runner=3D`, what do you see? If you don't see at least three processes with `--runner=3Drest:0:1`, stop Mailman and start Mailman. >> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as `filename` in the `file` handler in the LOGGING >> definition in settings(_local).py. >=20 > hansen(a)rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sit= es/models.py", line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sit= es/models.py", line 45, in _get_site_by_request > SITE_CACHE[domain] =3D self.get(domain__iexact=3Ddomain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/m= anager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/q= uery.py", line 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not= exist. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [ABH] At this point I click to accept a subsription request: >=20 > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not= available > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection= pool.py", line 672, in urlopen > chunked=3Dchunked, > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection= pool.py", line 421, in _make_request > six.raise_from(e, None) > File "", line 3, in raise_from > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection= pool.py", line 416, in _make_request > httplib_response =3D conn.getresponse() > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > response.begin() > File "/usr/lib/python3.7/http/client.py", line 296, in begin > version, status, reason =3D self._read_status() > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without respon= se >=20 > So yes, the REST API is not there. How can I get it going?=20 Stop Mailman and then start it. > Before we added the new domain, I was able to accept subscription requests = to the previous domain=E2=80=99s lists. No more. >=20 > Yours, >=20 > Allan --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============1395562111491143127==-- From hansen@rc.org Tue Jan 7 16:12:55 2020 From: hansen@rc.org To: mailman-users@mailman3.org Subject: [MM3-users] Re: [Mailman-Users] MM3 startup issues Date: Tue, 07 Jan 2020 07:16:03 +0000 Message-ID: <157838136301.21046.2132325785602268856@mailman.iad1.psf.io> In-Reply-To: <178e6ba3-186e-19e4-344e-0b4be85864ad@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3124938475184248174==" --===============3124938475184248174== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Mark Sapiro wrote: > Restoring original Subject:, and doesn't this thread belong on > mailman-users(a)msailman3.org - CCing there. Sorry about both, Mark. I'm now here. Didn't know this one existed and was to= ld to use the other list server. > > On 1/4/20 5:47 PM, Allan Hansen wrote: > > > > > a. The server was set up with the wrong domain > > name (our fault), so I had to add the =E2=80=98correct=E2=80=99 one. I ha= d seen the command =E2=80=98Add Domain=E2=80=99 > > in > > the UI and thought that would do it, but Brian kindly sent me a list of a= dditional > > instructions, which we then implemented. That made it possible to create = a list in the new > > domain, subscribe people and post messages. However, messages are not arc= hived. What extra > > step is needed to enable archiving? > > What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > > Archive archivers: hyperkitty, prototype > Are the messages in Mailman's var/archives/prototype/LIST(a)DOMAIN/new > directory? Yes! I found them. But the message files end with the name of the old host, n= ot the new host name under the new domain. > Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? There are 5 .pck files there dated 1/5/2002. > What's the setting for base_url in mailman-hyperkitty.cfg? It's base_url: https:///archives I suppose it should be changed to base_url: https:///archives But: What if we decided to have more than one domain, as the UI indicates is koshe= r? > Are there any errors in var/logs/mailman.log? Yep. Lots. They all are of this nature: Exception in "hyperkitty" archiver Traceback: ... File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.p= y", line 430, in _match_hostname match_hostname(cert, asserted_hostname) File "/usr/lib/python3.7/ssl.py", line 327, in match_hostname % (hostname, dnsnames[0])) ssl.SSLCertVerificationError: ("hostname 'OLDHOSTNAME' doesn't match 'NEWHOST= NAME'",) > > b. When I go to the server using the new domain (both > > before and after logging in), I see not just the lists I created in the n= ew domain, but > > the lists created in the old domain. These lists of lists are domain spec= ific and should > > not be listed together. That=E2=80=99s just IMHO, but not serious, as I w= ill soon get rid of > > anything in the old domain. So feel free to ignore this one if this is in= tended, which I > > could see might be the case. > Set > FILTER_VHOST =3D True > in settings_local.py > > Yes, Brian told me to do the same (well, settings.py).=20 > > This is the what I wrote back: > > hansen(a)rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > > # Only display mailing-lists from the same virtual host as the webserver > > FILTER_VHOST =3D True > You shouldn't edit settings.py. You should override the setting by > putting it in settings_local.py. Silly. I should have remembered that from back in the days. But if the local file is overriding, it should have worked, I'd think. > > Then Brian told me to restart qcluster: > > hansen(a)rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster > qcluster is not what you need to restart. You need to restart whatever > is supporting the wsgi interface to Django. This may be uwsgi or > gunicorn or ??. Whatever it is, that's what needs to be restarted. Beats me, Mark. Brian, do you know? > > I then logged in, but the same lists are showing. It > > either takes the system a long time to reset or it has ignored the=20 > > setting. > > Just tried it again, and the lists are all showing. Do I need to manually= recompile the > > file? > > > > c. I then > > moved on to the templates and added a template for the message text to se= nd to new > > subscribers. That resulted in the following error message when I went in = as moderator to > > approve of a new subscription: > > Something went wrong > > Mailman REST API not available. Please start Mailman core. > > Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at proc= esses, I > > see a bunch of postgres, python3, nginx, django-adminp but > > nothing explicitly with a =E2=80=98mailman=E2=80=99 string. > If you do ps ax|grep runner=3D, what do you see? If you don't see at > least three processes with --runner=3Drest:0:1, stop Mailman and start > Mailman. Yep. I did not get the whole string before. With your options I see three of these rest:0:1 processes. So I guess the REST stuff is running anyway. > If so, what's > in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's > called - defined as filename in the file handler in the LOGGING > definition in settings(_local).py. > hansen(a)rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sit= es/models.py", > line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sit= es/models.py", > line 45, in _get_site_by_request > SITE_CACHE[domain] =3D self.get(domain__iexact=3Ddomain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/m= anager.py", > line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/q= uery.py", line > 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not= exist. > This is because of the domain change. In settings(_local).py you have a > setting for SITE_ID. Possibly, setting that in settings_local.py to a > value one greater that the current setting will do.=20 Trying setting it to 1 (it was 0 before). > To be certain of the > correct value, you need to look at the django_site table in mailman's > database. That table has 3 columns, id, domain and name. The id for the > row of your domain is what needs to be set as SITE_ID. You lost me here. No idea how to access the Mailman database. Brian, do you know? > > [ABH] At this point I click to accept a subsription > > request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API n= ot available > > Traceback (most recent call last): > > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connecti= onpool.py", line > > 672, in urlopen > > chunked=3Dchunked, > > File "/opt/mailman/mm/venv/lib/python3.7/site packages/urllib3/connecti= onpool.py", line > > 421, in _make_request > > six.raise_from(e, None) > > File "", line 3, in raise_from > > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connecti= onpool.py", line > > 416, in _make_request > > httplib_response =3D conn.getresponse() > > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > > response.begin() > > File "/usr/lib/python3.7/http/client.py", line 296, in begin > > version, status, reason =3D self._read_status() > > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > > raise RemoteDisconnected("Remote end closed connection without" > > http.client.RemoteDisconnected: Remote end closed connection without resp= onse > > So yes, the REST API is not there. How can I get it going? > Stop Mailman and then start it. No idea here, either. I looked online and found this: $ from mailman.commands.cli_control import Stop But it complained: from: too many arguments Must have found an out-of-date page. :-) Yours, Allan --===============3124938475184248174==-- From brian_carpenter@emwd.com Tue Jan 7 16:49:34 2020 From: Brian Carpenter To: mailman-users@mailman3.org Subject: [MM3-users] Re: [Mailman-Users] MM3 startup issues Date: Tue, 07 Jan 2020 11:49:30 -0500 Message-ID: In-Reply-To: <157838136301.21046.2132325785602268856@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9159593808120981580==" --===============9159593808120981580== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/7/20 2:16 AM, hansen(a)rc.org wrote: > Beats me, Mark. Brian, do you know? Yes sir. Here are the three startup scripts that you will need to know. I should have included that in the communication I sent you and I apologize for that: systemctl start/stop/restart/status mailman (this is for Mailman core) systemctl start/stop/restart/status qcluster (this is for Django) systemctl start/stop/restart/status gunicorn (this is for web access to postorius/hyperkitty) -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/ --===============9159593808120981580==-- From mark@msapiro.net Tue Jan 7 17:57:28 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: [Mailman-Users] MM3 startup issues Date: Tue, 07 Jan 2020 09:57:17 -0800 Message-ID: <8c8d9847-1e26-4569-c6f5-e9362d7df1f4@msapiro.net> In-Reply-To: <157838136301.21046.2132325785602268856@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4695769241239241544==" --===============4695769241239241544== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/6/20 11:16 PM, hansen(a)rc.org wrote: > Mark Sapiro wrote: >=20 >> What's the setting for base_url in mailman-hyperkitty.cfg? >=20 > It's > base_url: https:///archives >=20 > I suppose it should be changed to > base_url: https:///archives That's part of it, but see below. > But: > What if we decided to have more than one domain, as the UI indicates is kos= her? Again, see below. >> Are there any errors in var/logs/mailman.log? >=20 > Yep. Lots. They all are of this nature: >=20 > Exception in "hyperkitty" archiver > Traceback: > ... > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection= .py", line 430, in _match_hostname > match_hostname(cert, asserted_hostname) > File "/usr/lib/python3.7/ssl.py", line 327, in match_hostname > % (hostname, dnsnames[0])) > ssl.SSLCertVerificationError: ("hostname 'OLDHOSTNAME' doesn't match 'NEWHO= STNAME'",) OK. So the real issue is you are trying to access HyperKitty via an https URL and the certificate presented by the web server doesn't allow the domain in the URL. The domain in the URL doesn't really matter as long as it resolves to the HyperKitty host, but if it's an https URL the host's certificate must include that domain. It looks like in your case, the certificate is for 'NEWHOSTNAME', so setting base_url: https:///archives should be enough >> qcluster is not what you need to restart. You need to restart whatever >> is supporting the wsgi interface to Django. This may be uwsgi or >> gunicorn or ??. Whatever it is, that's what needs to be restarted. >=20 > Beats me, Mark. Brian, do you know? Brian has answered: systemctl restart gunicorn >> If you do ps ax|grep runner=3D, what do you see? If you don't see at >> least three processes with --runner=3Drest:0:1, stop Mailman and start >> Mailman. >=20 > Yep. I did not get the whole string before. With your options I see three > of these rest:0:1 processes. So I guess the REST stuff is running anyway. OK >> If so, what's >> in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as filename in the file handler in the LOGGING >> definition in settings(_local).py. >=20 >> hansen(a)rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log >> return Site.objects.get_current(request) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/si= tes/models.py", >> line 60, in get_current >> return self._get_site_by_request(request) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/si= tes/models.py", >> line 45, in _get_site_by_request >> SITE_CACHE[domain] =3D self.get(domain__iexact=3Ddomain) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/= manager.py", >> line 82, in manager_method >> return getattr(self.get_queryset(), name)(*args, **kwargs) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/= query.py", line >> 408, in get >> self.model._meta.object_name >> django.contrib.sites.models.Site.DoesNotExist: Site matching query does no= t exist. >=20 >> This is because of the domain change. In settings(_local).py you have a >> setting for SITE_ID. Possibly, setting that in settings_local.py to a >> value one greater that the current setting will do.=20 >=20 > Trying setting it to 1 (it was 0 before). OK. You can just shotgun trying numbers until one works, or >> To be certain of the >> correct value, you need to look at the django_site table in mailman's >> database. That table has 3 columns, id, domain and name. The id for the >> row of your domain is what needs to be set as SITE_ID. >=20 > You lost me here. No idea how to access the Mailman database. > Brian, do you know? It depends on the database engine. In the database section in your mailman.cfg there is a class: definition which will mention sqlite, mysql or postgresql. The tools for interacting with these are sqlite3, mysql and psql respectively. >> Stop Mailman and then start it. >=20 > No idea here, either. I looked online and found this: >=20 > $ from mailman.commands.cli_control import Stop > But it complained: > from: too many arguments That's a Python statement, not a shell command. You would do systemctl stop mailman systemctl start mailman alternatively, you could do /path/to/bin/mailman stop /path/to/bin/mailman start but that appears to not be the issue. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============4695769241239241544==-- From sunil@derigotech.com Wed Jan 8 02:59:29 2020 From: sunil soprey To: mailman-users@mailman3.org Subject: [MM3-users] Hyperkitty - not sending from GUI & reply-thread Date: Wed, 08 Jan 2020 02:46:14 +0000 Message-ID: <157845157473.21045.8792995304507428431@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8508571522109818853==" --===============8508571522109818853== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable With latest release (HK 1.3.1), does anyone have an issue with no emails fro= m reply-thread? I able to send/receive emails to/from mailman. I see MTA= delivered emails, just no emails from HK GUI.=20 No errors logs (py exception) nor mailman. ideaS? Versions: mailman-hyperkitty (1.1.0) - Mailman archiver plugin for HyperKitty INSTALLED: 1.1.0 (latest) HyperKitty (1.3.1) - A web interface to access GNU Mailman v3 archiv= es INSTALLED: 1.3.1 (latest) mailman (3.3.0) - Mailman -- the GNU mailing list manager INSTALLED: 3.3.0 (latest) postorius (1.3.1) - A web user interface for GNU Mailman INSTALLED: 1.3.1 (latest) django-mailman3 (1.3.1) - Django library to help interaction with= Mailman INSTALLED: 1.3.1 (latest) mailmanclient (3.3.0) - mailmanclient -- Python bindings for Ma= ilman REST API INSTALLED: 3.3.0 (latest) f --===============8508571522109818853==-- From mark@msapiro.net Wed Jan 8 03:31:50 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Hyperkitty - not sending from GUI & reply-thread Date: Tue, 07 Jan 2020 19:31:39 -0800 Message-ID: <44dc5acb-ad3f-696a-e179-d734dc9012f0@msapiro.net> In-Reply-To: <157845157473.21045.8792995304507428431@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5926715922757683925==" --===============5926715922757683925== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/7/20 6:46 PM, sunil soprey wrote: > With latest release (HK 1.3.1), does anyone have an issue with no emails f= rom reply-thread? I able to send/receive emails to/from mailman. I see M= TA delivered emails, just no emails from HK GUI.=20 If you look in Mailman's logs/access.log or in your web server logs do you see an entry like "POST /archives/list/LIST_ADDRESS/message/MESSAGE_HASH/reply HTTP/1.1" 200 ... Or maybe it's "POST /hyperkitty/list/LIST_ADDRESS/message/MESSAGE_HASH/reply HTTP/1.1" 200 ... Where LIST_ADDRESS is like list(a)domain and MESSAGE_HASH is the hash if the message-id that you're replying to. If it's there and the status is not 200, is there something in error.log? --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============5926715922757683925==-- From admin@franceserv.fr Wed Jan 8 17:49:44 2020 From: =?utf-8?q?=C3=89lodie?= BOSSIER To: mailman-users@mailman3.org Subject: [MM3-users] FILTER_VHOST for 3.2.1 not working after install Date: Wed, 08 Jan 2020 11:33:47 +0100 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5326361205957228116==" --===============5326361205957228116== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello, I'm using Mailman 2.1.29 since several years and all was perfect except the virtual_host which was "faked" : it was possible to have several mailing list by domain linked to their own domain and url but not same mailing list name for multiple domains. Example (with lighttpd) : - at http://ml.bossier.fr/listinfo we can see ONLY mailing list "test2@", "Test3@" and "Test4@" for @ml.bossier.fr - and at http://ml.franceserv.fr/listinfo we can see ONLY mailing list "bar@", "newsletter@" and "test@" for @ml.franceserv.fr Each url_host have their "own" mailing list. It's the main reason I would like migrate and use Mailman 3 and be able to have "test(a)ml.bossier.fr" and "test(a)ml.franceserv.fr". So I installed Mailman 3.2.1 and I have set "FILTER_VHOST = True" into /etc/mailman3/mailman-web.py then : mailman create --language fr --owner admin(a)franceserv.fr --domain test(a)ml.franceserv.fr mailman create --language fr --owner admin(a)franceserv.fr --domain test2(a)ml.bossier.fr And I have this result (with nginx as front) : - at http://ml.franceserv.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" - and at http://ml.bossier.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" (same result) And it's my problem, I would like be able to see the linked mailing list to their own url. I would like with Mailman 3.2.1 see into : - "example1.com/postorius/lists/" only the mailing list related to example1, - and into "example2.com/postorius/lists/" only the mailing list related to example2 as Mailman 2.1.x do it. I don't understand what I missed, could you help me please ? Best regards, Élodie PS. Sorry for my english language I'm french. --===============5326361205957228116==-- From ryan.morash@questar.org Wed Jan 8 17:50:23 2020 From: Ryan Morash To: mailman-users@mailman3.org Subject: [MM3-users] Re: Migration from 2.1 to 3 Date: Wed, 08 Jan 2020 14:38:17 +0000 Message-ID: <157849429768.21045.17974097557699386438@mailman.iad1.psf.io> In-Reply-To: <91743e9f-5503-f49d-315c-ab6719a200e2@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1365828805976729503==" --===============1365828805976729503== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I'm running into the same issue, but after some troubleshooting I think the i= ssue isn't with the import21 command. I'm running into the same issue when I = create a list using 'mailman create' without importing anything. New lists cr= eated through Postorius work fine. --===============1365828805976729503==-- From mark@msapiro.net Wed Jan 8 18:20:18 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Migration from 2.1 to 3 Date: Wed, 08 Jan 2020 10:20:05 -0800 Message-ID: In-Reply-To: <157849429768.21045.17974097557699386438@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0647521278480453288==" --===============0647521278480453288== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/8/20 6:38 AM, Ryan Morash wrote: > I'm running into the same issue, but after some troubleshooting I think the= issue isn't with the import21 command. I'm running into the same issue when = I create a list using 'mailman create' without importing anything. New lists = created through Postorius work fine. Can you please post the `mailman create` command options you are using to create the list. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============0647521278480453288==-- From Ryan.Morash@questar.org Wed Jan 8 18:24:48 2020 From: Ryan Morash To: mailman-users@mailman3.org Subject: [MM3-users] Re: Migration from 2.1 to 3 Date: Wed, 08 Jan 2020 18:24:44 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0858784546617541869==" --===============0858784546617541869== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I figured it out. It was a stupid mistake on my part, running the =E2=80=98ma= ilman create=E2=80=99 commands as root=E2=80=A6 chown=E2=80=99ing the /var/li= b/mailman3/lists directories to lists:lists solved the issues. From: Mark Sapiro Date: Wednesday, January 8, 2020 at 1:20 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Migration from 2.1 to 3 On 1/8/20 6:38 AM, Ryan Morash wrote: > I'm running into the same issue, but after some troubleshooting I think the= issue isn't with the import21 command. I'm running into the same issue when = I create a list using 'mailman create' without importing anything. New lists = created through Postorius work fine. Can you please post the `mailman create` command options you are using to create the list. -- 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://linkprotect.cudasvc.com/url?a=3Dhttps%3a%2f%2flists.mailman3.org%2fma= ilman3%2flists%2fmailman-users.mailman3.org%2f&c=3DE,1,h15CfHaOdoO_ah1ID2WFa9= 0FdJqrh3TMHkipShbxTwqnSUtPwoySMcv5o1ahU8KCaJGOlf8KYGScId7zFUqIOEHa06wwK74ZmXI= baNDz7tbSlLjjJ5DncEG8Bw,,&typo=3D1 Confidential Transmission This correspondence is confidential and may contain= privileged materials or information. It is intended for the use of the addre= ssee only and all others are prohibited from copying or disseminating this me= ssage or its contents. If you have received this transmission in error, delet= e it immediately and notify the sender. --===============0858784546617541869==-- From mark@msapiro.net Wed Jan 8 18:44:10 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: FILTER_VHOST for 3.2.1 not working after install Date: Wed, 08 Jan 2020 10:44:03 -0800 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0883041739423107330==" --===============0883041739423107330== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On 1/8/20 2:33 AM, Élodie BOSSIER via Mailman-users wrote: > > I would like with Mailman 3.2.1 see into : > - "example1.com/postorius/lists/" only the mailing list related to example1, > - and into "example2.com/postorius/lists/" only the mailing list related > to example2 as Mailman 2.1.x do it. > > I don't understand what I missed, could you help me please ? It works for me. I suspect in your case it has something to do with how ngnix is set up to forward to Django. What are your nginx settings for this? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============0883041739423107330==-- From mark@msapiro.net Thu Jan 9 00:41:02 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] bounce processing on this list Date: Wed, 08 Jan 2020 16:40:49 -0800 Message-ID: <7f6415e5-13ad-c29e-7e2b-907d0f24f8bf@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1658965815554897134==" --===============1658965815554897134== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit I have just installed the latest Mailman core for this list. This version now actually processes bounces. As a result of the huge backlog of unprocessed, queued bounces, some members may receive one or more bounce probe messages. As long as the probes don't bounce, your subscription will be unaffected and you can ignore the probe message. Sorry for the noise. Hopefully it's just a one time catch-up. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============1658965815554897134==-- From actionmystique@gmail.com Fri Jan 10 12:13:49 2020 From: jean-christophe manciot To: mailman-users@mailman3.org Subject: [MM3-users] Cannot setup HTTPS support for mailman3-web Date: Fri, 10 Jan 2020 12:13:46 +0000 Message-ID: <157865842683.11191.1326728145303736013@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8727095026589452869==" --===============8727095026589452869== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Ubuntu 20.04 mailman3 3.2.2-1 mailman3-web=C2=A00+20180916-10 python3-django=C2=A02:2.2.9-2ubuntu1 In ```/etc/mailman3/uwsgi.ini``` (example.org is defined in the local /etc/ho= sts as 10.0.0.1): ``` [uwsgi] # Port on which uwsgi will be listening. ### suwsgi: uwsgi protocol over TLS uwsgi-socket =3D example.org:8430 # https://uwsgi-docs.readthedocs.io/en/latest/HTTPS.html?highlight=3Dssl https =3D /etc/ssl/example.org.crt,/etc/ssl/example.org_rsakey.pem.decrypted,= HIGH ... # Drop privileges and don't run as root. uid =3D www-data gid =3D www-data ... ``` I suppose that uwsgi reads the certificate & its private key before dropping = root privileges. Right now, uwsgi cannot access them as ```www-data```. In ```/etc/mailman3/mailman-web.py``` (symlinked to django settings.py) : ``` ... SECURE_PROXY_SSL_HEADER =3D ('HTTP_X_FORWARDED_PROTO', 'https') SECURE_PROXY_SSL_HEADER =3D ('HTTP_X_FORWARDED_SCHEME', 'https') # Other security settings # SECURE_SSL_REDIRECT =3D True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT =3D [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE =3D True # SECURE_CONTENT_TYPE_NOSNIFF =3D True # SECURE_BROWSER_XSS_FILTER =3D True # CSRF_COOKIE_SECURE =3D True # CSRF_COOKIE_HTTPONLY =3D True # X_FRAME_OPTIONS =3D 'DENY' ... POSTORIUS_TEMPLATE_BASE_URL =3D 'https://example.org:8430' ``` In ```/etc/nginx/sites-enabled/example.org.conf``` ``` ... location /=20 { include /etc/nginx/uwsgi_params; # upstream app server uwsgi_pass suwsgi://example.org:8430; } ``` uwsgi is listening on the right address/port: ``` # networks-list-connections.sh | grep :8430 tcp 0 0 10.0.0.1:8430 0.0.0.0:* LISTEN 33= 54336045 1768187/uwsgi =20 ``` Despite those settings and all the relevant systemd services restarted, I get= ```502 Bad Gateway``` while browsing to ```https://example.org/postorius/lis= ts/?all-lists``` (or any other page) with the following error nginx message: ``` *1 peer closed connection in SSL handshake while SSL handshaking to upstream,= client: 10.0.0.1, server: example.org, request: "GET /postorius/lists/?all-l= ists HTTP/2.0", upstream: "suwsgi://10.0.0.1:8430", host: "example.org", refe= rrer: "https://example.org/postorius/lists/" ``` Of course, without those specific https/suwsgi settings, everything works fin= e. What am I missing/doing incorrectly? Does uwsgi need access to the certificat= e/private key while running as non-root for instance? --===============8727095026589452869==-- From mark@msapiro.net Fri Jan 10 22:51:04 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cannot setup HTTPS support for mailman3-web Date: Fri, 10 Jan 2020 14:50:53 -0800 Message-ID: <72052957-1798-363d-9224-66067f6f4bb5@msapiro.net> In-Reply-To: <157865842683.11191.1326728145303736013@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1899465445501887937==" --===============1899465445501887937== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/10/20 4:13 AM, jean-christophe manciot wrote: >=20 > Of course, without those specific https/suwsgi settings, everything works f= ine. > What am I missing/doing incorrectly? Does uwsgi need access to the certific= ate/private key while running as non-root for instance? I think so. Have you tried making the key file group readable and group www-data? --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============1899465445501887937==-- From cavejunkie@hotmail.com Sat Jan 11 00:56:37 2020 From: Jim Ward To: mailman-users@mailman3.org Subject: [MM3-users] Manage Member(s) Mailman Settings / Display Names Date: Sat, 11 Jan 2020 00:55:20 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4349193872743772132==" --===============4349193872743772132== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Mailman2 allowed me to list my members and modify a number of their attribute= s (display_name, etc) Postorius is a beautiful interface BUT I am evidently not finding how to mana= ge my members to the extent that I could in Mailman2 Am I missing something? --===============4349193872743772132==-- From mark@msapiro.net Sat Jan 11 01:05:19 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Manage Member(s) Mailman Settings / Display Names Date: Fri, 10 Jan 2020 17:05:07 -0800 Message-ID: In-Reply-To: =?utf-8?q?=3CDM5PR17MB1098274F1E133DF8D83C1F44C83B0=40DM5PR17MB?= =?utf-8?q?1098=2Enamprd17=2Eprod=2Eoutlook=2Ecom=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6369912473482200424==" --===============6369912473482200424== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/10/20 4:55 PM, Jim Ward wrote: > Mailman2 allowed me to list my members and modify a number of their attribu= tes (display_name, etc) >=20 > Postorius is a beautiful interface BUT I am evidently not finding how to ma= nage my members to the extent that I could in Mailman2 It's not like MM 2.1 where you have a membership list with columns of checkboxes, but if you pull down the Users menu and select Members or Non-Members, each user has an options link that allows you to set/change options. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============6369912473482200424==-- From hansen@rc.org Sat Jan 11 07:16:45 2020 From: hansen@rc.org To: mailman-users@mailman3.org Subject: [MM3-users] Re: Default values for new lists Date: Sat, 11 Jan 2020 07:16:42 +0000 Message-ID: <157872700210.5265.482088031373131919@mailman.iad1.psf.io> In-Reply-To: <5e17ac65-6c4c-0826-fddc-903d010f6b42@eenet.ee> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0583061552527174812==" --===============0583061552527174812== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I just moved from MM2 to MM3. I have some 50 lists I need to configure and th= ey all need the same settings (private archives, max 2 recipients, etc.). I o= ften add and remove lists. I'm pleased that I now can set domain-level templa= tes, but I really need domain-level default list settings as well. The archived 'Deault values for new lists' thread indicates that a new versio= n is needed to get this into the UI. Is there a back-door way to alter these = defaults in the mean-time? --===============0583061552527174812==-- From cavejunkie@hotmail.com Sat Jan 11 10:43:47 2020 From: Jim Ward To: mailman-users@mailman3.org Subject: [MM3-users] Re: Manage Member(s) Mailman Settings / Display Names Date: Sat, 11 Jan 2020 10:43:43 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1979608586746239773==" --===============1979608586746239773== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I will admit I was partial to the MM 2.1 columns and checkboxes but the end r= esult is the same, HOWEVER: 1) The member 'Display Name' does not seem to be available to be managed by m= e the domain/list administrator. 2) The 'Search Members' function appears to be limited to the email address o= nly and does not include display name These items are important to me as the list I am running includes many that a= re not, nor will they really ever be, technically savvy enough to access and = manage their own account. ________________________________ From: Mark Sapiro Sent: Friday, January 10, 2020 7:05 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Manage Member(s) Mailman Settings / Display Names On 1/10/20 4:55 PM, Jim Ward wrote: > Mailman2 allowed me to list my members and modify a number of their attribu= tes (display_name, etc) > > Postorius is a beautiful interface BUT I am evidently not finding how to ma= nage my members to the extent that I could in Mailman2 It's not like MM 2.1 where you have a membership list with columns of checkboxes, but if you pull down the Users menu and select Members or Non-Members, each user has an options link that allows you to set/change options. -- 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://eur04.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Flists.mai= lman3.org%2Fmailman3%2Flists%2Fmailman-users.mailman3.org%2F&data=3D02%7C= 01%7C%7C013b70971b5048051e9908d796325517%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7= C1%7C0%7C637143015222989516&sdata=3DcAn86GHQdYCSEA3CeqDF%2BfphkxPLF1oiTjf= IyoTgZL0%3D&reserved=3D0 --===============1979608586746239773==-- From actionmystique@gmail.com Sat Jan 11 12:42:56 2020 From: jean-christophe manciot To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cannot setup HTTPS support for mailman3-web Date: Sat, 11 Jan 2020 12:42:52 +0000 Message-ID: <157874657267.5265.18158902200744536193@mailman.iad1.psf.io> In-Reply-To: <72052957-1798-363d-9224-66067f6f4bb5@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8196035142870214494==" --===============8196035142870214494== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Giving group read access for www-data to both certificate and private key fi= les leads to the exact same error. --===============8196035142870214494==-- From mark@msapiro.net Sat Jan 11 18:14:04 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Manage Member(s) Mailman Settings / Display Names Date: Sat, 11 Jan 2020 10:13:54 -0800 Message-ID: <110d471b-ce66-213e-0e6c-d330cbeca7f5@msapiro.net> In-Reply-To: =?utf-8?q?=3CDM5PR17MB1098AE37CDDDA8711BF7105CC83B0=40DM5PR17MB?= =?utf-8?q?1098=2Enamprd17=2Eprod=2Eoutlook=2Ecom=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5450296974959761710==" --===============5450296974959761710== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/11/20 2:43 AM, Jim Ward wrote: > I will admit I was partial to the MM 2.1 columns and checkboxes but the end= result is the same, HOWEVER: >=20 > 1) The member 'Display Name' does not seem to be available to be managed by= me the domain/list administrator. > 2) The 'Search Members' function appears to be limited to the email address= only and does not include display name >=20 > These items are important to me as the list I am running includes many that= are not, nor will they really ever be, technically savvy enough to access an= d manage their own account. Part of this is because of the architecture of Mailman 3. In mailman 2.1, we have lists and members of those lists and no connection between a member of one list and a member of another list, even if their email addresses are the same. Thus, a member of a list and that member's display name are things associated only with that list, and can be manipulated by the list admin. Mailman 3 is different. In mailman 3 we have users and addresses. A user has a display name and one or more addresses, one of which is preferred, and each address has a display name. These are independent of any list and belong to the user. Then, a list member can be a user, in which case, the address associated with this member is the user's preferred address and the display name is the user's display name (or maybe the display name of that address, I'm not sure). Or, a list member can be an address in which case, the member's display name is the display name associated with that address. Thus, in Mailman 3 the display name associated with a list member can be one of several, and these belong to the user, not to the list. As far as not searching display names is concerned, this is . --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============5450296974959761710==-- From mark@msapiro.net Sat Jan 11 20:14:41 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Default values for new lists Date: Sat, 11 Jan 2020 12:14:30 -0800 Message-ID: <9b2cec21-3cec-f0ba-59b6-6c0331d6b1bb@msapiro.net> In-Reply-To: <157872700210.5265.482088031373131919@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1333736697588272142==" --===============1333736697588272142== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/10/20 11:16 PM, hansen(a)rc.org wrote: > I just moved from MM2 to MM3. I have some 50 lists I need to configure and = they all need the same settings (private archives, max 2 recipients, etc.). I= often add and remove lists. I'm pleased that I now can set domain-level temp= lates, but I really need domain-level default list settings as well. > The archived 'Deault values for new lists' thread indicates that a new vers= ion is needed to get this into the UI. Is there a back-door way to alter thes= e defaults in the mean-time? For lists you import from Mailman 2.1 using the `mailman import21` command, the Mailman 2.1 list settings are applied to the Mailman 3 list. As far as new lists you create in MM 3 goes, you can define more styles to be applied to newly created lists. See . However, you can't just create a style via `mailman shell` as described there because it won't persist. You need to create a plugin that implements the style. See for info on this. Note the Components section discusses adding a plugin implementing an IRule, but one implementing one or more IStyle classes would be similar. Another possibility, which I haven't tested but which may work is to create Mailman 2.1 lists with the desired styles, but no members, owners, moderators, etc and save their config.pck files. Then you should be able to apply those settings to a Mailman 3 list using the `mailman import21` command. This will probably still require fixing some things on the MM 3 list such as Description, Information, Display name and Subject prefix, but it may help. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============1333736697588272142==-- From maxking@asynchronous.in Sat Jan 11 20:30:50 2020 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cannot setup HTTPS support for mailman3-web Date: Sat, 11 Jan 2020 12:30:24 -0800 Message-ID: <571f47b0-8a25-4239-aa34-86480b1acb00@www.fastmail.com> In-Reply-To: <157874657267.5265.18158902200744536193@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4636607185529636010==" --===============4636607185529636010== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sat, Jan 11, 2020, at 4:42 AM, jean-christophe manciot wrote: > Giving group read access for www-data to both certificate and private=20 > key files leads to the exact same error. I personally think you might find better help in one of the uwsgi supports li= sts. I almost always use just uwsgi protocol between nginx and uwsgi and SSL = termination happens at the Nginx, so I don't have a sample configuration to h= elp you out with. > _______________________________________________ > 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) --===============4636607185529636010==-- From maxking@asynchronous.in Mon Jan 13 02:42:47 2020 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Another set of new releases Date: Sun, 12 Jan 2020 18:42:19 -0800 Message-ID: <397d2ef9-f798-4746-86ba-1c2522ae0da8@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8036173634426771175==" --===============8036173634426771175== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.2 - Django-mailman3 1.3.2 - Hyperkitty 1.3.2 This release was required as it turned out 1.3.1 releases did not includes tr= anslations in the tarballs that I created and uploaded to PyPI. They do inclu= de a couple of bugfixes and more translations. - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) All three of these releases also officially drop support for Django 1.11. Alt= hough, there hasn't been any code change that breaks compatibility with 1.11.= It has just been dropped form our CI machinery since our dependencies no lon= ger support 1.11.=20 All the releases are available on PyPI, as usual! --=20 Thanks Abhilash Raj --===============8036173634426771175==-- From hansen@rc.org Mon Jan 13 21:34:02 2020 From: Allan Hansen To: mailman-users@mailman3.org Subject: [MM3-users] Adding a domsin Date: Mon, 13 Jan 2020 13:33:56 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2942998480194741697==" --===============2942998480194741697== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, I=E2=80=99m still working on setting up my lists in a domain that was added a= fter MM3 installation.=20 It=E2=80=99s mostly working but the Postorius page and the =E2=80=98noreply= =E2=80=99 emails still sport the old domain name. I hav looked at all the py = and cfg files where the old name appeared, and they no longer hold the old na= me. My coadmin now tells me that the database has a table with the old name. = Any suggestion as to whether that can cause the issue and if it=E2=80=99s saf= e to change the table.=20 Yours, Allan Hansen P.O. Box 2423 Cypress, CA 90630 --===============2942998480194741697==-- From brian_carpenter@emwd.com Mon Jan 13 21:43:07 2020 From: Brian Carpenter To: mailman-users@mailman3.org Subject: [MM3-users] Re: Adding a domsin Date: Mon, 13 Jan 2020 16:43:02 -0500 Message-ID: <00c3803e-498e-c212-7e36-8078f27a8ffe@emwd.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2108165720088851653==" --===============2108165720088851653== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/13/20 4:33 PM, Allan Hansen wrote: > Hi all, > > I=E2=80=99m still working on setting up my lists in a domain that was added= after MM3 installation. > > It=E2=80=99s mostly working but the Postorius page and the =E2=80=98noreply= =E2=80=99 emails still sport the old domain name. I hav looked at all the py = and cfg files where the old name appeared, and they no longer hold the old na= me. My coadmin now tells me that the database has a table with the old name. = Any suggestion as to whether that can cause the issue and if it=E2=80=99s saf= e to change the table. > > Yours, > > Allan Hansen > P.O. Box 2423 > Cypress, CA 90630 > _______________________________________________ > 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/ Hi Allan, I saw the changes you made to the two files, settings_local.py and=20 mailman.cfg. They look correct. Did you restart the=20 mailman/qcluster/gunicorn services after you made the change? --=20 Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/ --===============2108165720088851653==-- From mark@msapiro.net Mon Jan 13 21:57:53 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Adding a domsin Date: Mon, 13 Jan 2020 13:57:45 -0800 Message-ID: <22f1c61b-cf20-dc7e-f40a-59f411e76904@msapiro.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0172330056025332887==" --===============0172330056025332887== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/13/20 1:33 PM, Allan Hansen wrote: >=20 > It=E2=80=99s mostly working but the Postorius page and the =E2=80=98noreply= =E2=80=99 emails still sport the old domain name. I hav looked at all the py = and cfg files where the old name appeared, and they no longer hold the old na= me. My coadmin now tells me that the database has a table with the old name. = Any suggestion as to whether that can cause the issue and if it=E2=80=99s saf= e to change the table.=20 Look in Mailman's var/templates/directory. I suspect you have a site/en/ subdirectory with templates containing the old name. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============0172330056025332887==-- From mark@msapiro.net Mon Jan 13 22:02:27 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Adding a domsin Date: Mon, 13 Jan 2020 14:02:14 -0800 Message-ID: In-Reply-To: <22f1c61b-cf20-dc7e-f40a-59f411e76904@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8129819251731732581==" --===============8129819251731732581== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/13/20 1:57 PM, Mark Sapiro wrote: > > Look in Mailman's var/templates/ directory. I suspect you have a site/en/ > subdirectory with templates containing the old name. If that is the case, and you are replacing the old domain with the new one, you can just edit the templates, but if you actually want to support multiple domains, templates including a domain should be in var/templates/domains/DOMAIN.NAME/en/. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============8129819251731732581==-- From dancab@caltech.edu Wed Jan 15 19:03:56 2020 From: dancab@caltech.edu To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman shell tutorial Date: Wed, 15 Jan 2020 19:03:52 +0000 Message-ID: <157911503298.6166.3585963037996697106@mailman.iad1.psf.io> In-Reply-To: <3c346d5b-ec3d-a2ba-e7ba-b8a48d59096a@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8904005786768731238==" --===============8904005786768731238== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I'm attempting to run some tests on a test instance of Mailman3 hosted via Do= cker container. I can access the web interface, I've imported lists, etc. I'm now trying to do some simple injection testing via command line. But I se= em to be missing something. I've tried using mailman inject with the filename option to one of the lists = I've imported but still no luck.=20 I've also followed the tutorial here: https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/inject.html I was hoping to see my injected message to show up as held for moderation in = the web interface.=20 Please advise! -- Dan --===============8904005786768731238==-- From mark@msapiro.net Wed Jan 15 19:18:47 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman shell tutorial Date: Wed, 15 Jan 2020 11:18:35 -0800 Message-ID: In-Reply-To: <157911503298.6166.3585963037996697106@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8391197916794706865==" --===============8391197916794706865== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/15/20 11:03 AM, dancab(a)caltech.edu wrote: >=20 > I'm now trying to do some simple injection testing via command line. But I = seem to be missing something. >=20 > I've tried using mailman inject with the filename option to one of the list= s I've imported but still no luck.=20 What is the command you are giving? It should be something like mailman inject -f your_file listname.example.com You could also specify `-q in` but that's the default. What does the message in your_file look like? Does it have a complete set of headers including To:, From:, Subject:, Date: and Message-ID:, and is To: the list posting address? --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============8391197916794706865==-- From dieter.leupold@elster.de Thu Jan 16 13:16:06 2020 From: Dieter Leupold To: mailman-users@mailman3.org Subject: [MM3-users] Settings for https support Date: Thu, 16 Jan 2020 14:15:58 +0100 Message-ID: <461128f2-a255-7cd1-7981-4cd8d1466641@elster.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9103257148468422022==" --===============9103257148468422022== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, I configured Postorius (via Apache2) to use https, which looks fine. But the connection to hyperkitty failed with "code 400, message Bad request syntax". I tried serveral settings....without success. Could you give me an example, which settings are to configure? Thanks for your help! -- Dieter --===============9103257148468422022==-- From tlehker@cviewllc.com Thu Jan 16 17:18:37 2020 From: Thomas Lehker To: mailman-users@mailman3.org Subject: [MM3-users] Listing/Exporting member list error: Mailman REST API not available. Please start Mailman core. Date: Thu, 16 Jan 2020 17:18:33 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5322347846901944484==" --===============5322347846901944484== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Our MailMan3 server is extremely slow and when trying to list or export membe= rs for a larger list it is throwing 'Mailman REST API not available. Please = start Mailman core'. In Mailman core logs I am seeing [27] [CRITICAL] WORKER TIMEOUT (pid:40) [43] [INFO] Booting worker with pid: 43 Has anyone seen this issue? Is there any way to increase 'timeouts'? Thanks for any help! Tom Mailman Novice 16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests = HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?cou= nt=3D50&page=3D1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 = 347 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com/roster/owner H= TTP/1.1" 200 634 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/list.somelist.com/roster/moderat= or HTTP/1.1" 200 638 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:01 +0000] "GET /3.1/lists/somelist(a)somelist.com/config H= TTP/1.1" 200 2257 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:05 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP= /1.1" 200 81 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/list.somelist.com/archivers HTTP= /1.1" 200 81 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:08 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests= HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:10 +0000] "GET /3.1/lists/list.somelist.com/member/somelis= t(a)somelist HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:16 +0000] "GET /3.1/lists/somelist(a)somelist.com/requests= HTTP/1.1" 200 982 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:19 +0000] "GET /3.1/lists/somelist(a)somelist.com/held?cou= nt=3D50&page=3D1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [16/Jan/2020:16:56:26 +0000] "GET /3.1/lists/list.somelist.com HTTP/1.1" 200 = 347 "-" "GNU Mailman REST client v3.3.0" [2020-01-16 16:56:58 +0000] [27] [CRITICAL] WORKER TIMEOUT (pid:40) [2020-01-16 16:57:00 +0000] [43] [INFO] Booting worker with pid: 43 DISCLAIMER: The information contained in this message is privileged and confi= dential. If the reader of this message is not the intended recipient, or an e= mployee or agent responsible for delivering this message to the intended reci= pient, you are hereby notified that any dissemination, distribution or copyin= g of this communication is strictly prohibited. If you have received this com= munication in error, please reply to the message and delete/destroy any copy = of this message. Information in this message that does not relate to the offi= cial business of the firm shall be understood as neither given nor endorsed b= y it. --===============5322347846901944484==-- From torgeriedel@gmx.de Thu Jan 16 18:49:43 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail Date: Thu, 16 Jan 2020 19:49:38 +0100 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4596381907915920713==" --===============4596381907915920713== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, we migrated successfully to mailman3 so far. I have some questions regarding = handling of SPAM mails in mailman, here is the first, second comes in a separ= ate post: The list moderator currently receives a copy of the original mail in the info= mail he gets for moderation. This is bad in case it was a SPAM mail, cause w= e have seen that such an info mail is detected also as SPAM. That might rise = problems cause other mail servers might block the info mail as SPAM and if th= is happens too often blocking the whole server. I fear. At least I see that m= y rspamd starts learning the info mail as SPAM. I don't want that to happen. I searched mailman web interface for a setting to disable adding a copy to th= e info mail. But have not found it. Is it missing or where do I have to look? Best regards Torge --===============4596381907915920713==-- From torgeriedel@gmx.de Thu Jan 16 18:51:43 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Handling of SPAM mails in mailman3 - Check for X-Spam Header Date: Thu, 16 Jan 2020 19:51:38 +0100 Message-ID: <4c937e0e-7f18-78a5-3dd6-56ac5f28b1f3@gmx.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3903015857858156428==" --===============3903015857858156428== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, we migrated successfully to mailman3 so far. I have some questions regarding = handling of SPAM mails in mailman, this is the second question: Such SPAM mails are currently hold for moderation with reason "not from a lis= t member". Is there no check for the "X-Spam: Yes" header or is this check do= ne later? I would prefer that a check for such a header is done first and is = reported as the reason. Which is IMHO a very important information. Or maybe = show "This is detected as SPAM" in big bold red letters in a new column in th= e list of mails to moderate for such a mail. Maybe there is more eye-candy so= lution for it. Sometimes mail accounts of allowed users are hacked and we do not want spread= SPAM accidently. On my setup all mails are checked by rspamd before local de= livery and I see that the "X-Spam" header is set for such mails. So even mail= s from allowed members with header "X-Spam: Yes" should be hold for moderatio= n. Maybe this is already the case, did not gave it a try yet. Best regards Torge --===============3903015857858156428==-- From terri@toybox.ca Thu Jan 16 19:22:40 2020 From: Terri Oda To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail Date: Thu, 16 Jan 2020 11:22:31 -0800 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5450915054664522389==" --===============5450915054664522389== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I don't *think* we have a checkbox for this, but I've definitely seen this be= haviour in Mailman 2 and had trouble with Mailman getting blocked as a result= , so I think this would be a very nice feature request. Terri On January 16, 2020 10:49:38 a.m. PST, Torge Riedel wr= ote: >Hi, > >we migrated successfully to mailman3 so far. I have some questions >regarding handling of SPAM mails in mailman, here is the first, second >comes in a separate post: > > >The list moderator currently receives a copy of the original mail in >the info mail he gets for moderation. This is bad in case it was a SPAM >mail, cause we have seen that such an info mail is detected also as >SPAM. That might rise problems cause other mail servers might block the >info mail as SPAM and if this happens too often blocking the whole >server. I fear. At least I see that my rspamd starts learning the info >mail as SPAM. I don't want that to happen. > >I searched mailman web interface for a setting to disable adding a copy >to the info mail. But have not found it. Is it missing or where do I >have to look? > > >Best regards >Torge >_______________________________________________ >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/ --===============5450915054664522389==-- From maxking@asynchronous.in Thu Jan 16 19:47:54 2020 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Listing/Exporting member list error: Mailman REST API not available. Please start Mailman core. Date: Thu, 16 Jan 2020 11:47:30 -0800 Message-ID: <66836f36-ccb5-4fd2-b9b4-b40860b9b480@www.fastmail.com> In-Reply-To: =?utf-8?q?=3CBN7PR06MB5138986F8FFAD73379BCEE05D1360=40BN7PR06MB?= =?utf-8?q?5138=2Enamprd06=2Eprod=2Eoutlook=2Ecom=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1924283266071784588==" --===============1924283266071784588== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 16, 2020, at 9:18 AM, Thomas Lehker wrote: > Our MailMan3 server is extremely slow and when trying to list or export=20 > members for a larger list it is throwing 'Mailman REST API not=20 > available. Please start Mailman core'. In Mailman core logs I am seeing >=20 > [27] [CRITICAL] WORKER TIMEOUT (pid:40) > [43] [INFO] Booting worker with pid: 43 >=20 > Has anyone seen this issue? Is there any way to increase 'timeouts'? How did you install Mailman3 and which version are you on? Mailman 3, since I think 3.3.0 uses gunicorn for REST API, which does have a = setting to increase the timeout for the worker to get killed[1], the default = I think is 30seconds. You can add a new `gunicorn.cfg` next to your `mailman.= cfg` and add the additional options. You can also increase the total number of workers, but that wouldn't help spe= ed up queries, which I think is what you are actually looking for. The slower queries could be because of too many database calls, can you speci= fically tell which endpoint is taking over 30seconds for you? I see that you = are using mailmanclient to call the API. [1]: https://docs.gunicorn.org/en/stable/settings.html#timeout >=20 > Thanks for any help! >=20 > Tom > Mailman Novice >=20 >=20 > 16/Jan/2020:16:55:58 +0000] "GET=20 > /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU=20 > Mailman REST client v3.3.0" > [16/Jan/2020:16:55:58 +0000] "GET=20 > /3.1/lists/somelist(a)somelist.com/held?count=3D50&page=3D1 HTTP/1.1" 200 9= 0=20 > "-" "GNU Mailman REST client v3.3.0" > [16/Jan/2020:16:55:58 +0000] "GET /3.1/lists/list.somelist.com=20 > HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0" > [16/Jan/2020:16:55:58 +0000] "GET=20 > /3.1/lists/list.somelist.com/roster/owner HTTP/1.1" 200 634 "-" "GNU=20 > Mailman REST client v3.3.0" > [16/Jan/2020:16:56:01 +0000] "GET=20 > /3.1/lists/list.somelist.com/roster/moderator HTTP/1.1" 200 638 "-"=20 > "GNU Mailman REST client v3.3.0" > [16/Jan/2020:16:56:01 +0000] "GET=20 > /3.1/lists/somelist(a)somelist.com/config HTTP/1.1" 200 2257 "-" "GNU=20 > Mailman REST client v3.3.0" > [16/Jan/2020:16:56:05 +0000] "GET=20 > /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU=20 > Mailman REST client v3.3.0" > [16/Jan/2020:16:56:08 +0000] "GET=20 > /3.1/lists/list.somelist.com/archivers HTTP/1.1" 200 81 "-" "GNU=20 > Mailman REST client v3.3.0" > [16/Jan/2020:16:56:08 +0000] "GET=20 > /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU=20 > Mailman REST client v3.3.0" > [16/Jan/2020:16:56:10 +0000] "GET=20 > /3.1/lists/list.somelist.com/member/somelist(a)somelist HTTP/1.1" 404 26=20 > "-" "GNU Mailman REST client v3.3.0" > [16/Jan/2020:16:56:16 +0000] "GET=20 > /3.1/lists/somelist(a)somelist.com/requests HTTP/1.1" 200 982 "-" "GNU=20 > Mailman REST client v3.3.0" > [16/Jan/2020:16:56:19 +0000] "GET=20 > /3.1/lists/somelist(a)somelist.com/held?count=3D50&page=3D1 HTTP/1.1" 200 9= 0=20 > "-" "GNU Mailman REST client v3.3.0" > [16/Jan/2020:16:56:26 +0000] "GET /3.1/lists/list.somelist.com=20 > HTTP/1.1" 200 347 "-" "GNU Mailman REST client v3.3.0" > [2020-01-16 16:56:58 +0000] [27] [CRITICAL] WORKER TIMEOUT (pid:40) > [2020-01-16 16:57:00 +0000] [43] [INFO] Booting worker with pid: 43 >=20 >=20 > DISCLAIMER: The information contained in this message is privileged and=20 > confidential. If the reader of this message is not the intended=20 > recipient, or an employee or agent responsible for delivering this=20 > message to the intended recipient, you are hereby notified that any=20 > dissemination, distribution or copying of this communication is=20 > strictly prohibited. If you have received this communication in error,=20 > please reply to the message and delete/destroy any copy of this=20 > message. Information in this message that does not relate to the=20 > official business of the firm shall be understood as neither given nor=20 > endorsed by it. > _______________________________________________ > 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) --===============1924283266071784588==-- From maxking@asynchronous.in Thu Jan 16 19:49:54 2020 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Settings for https support Date: Thu, 16 Jan 2020 11:49:28 -0800 Message-ID: <20d8c74d-d7b4-49d1-ae26-5503493aed4d@www.fastmail.com> In-Reply-To: <461128f2-a255-7cd1-7981-4cd8d1466641@elster.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8399093688310921457==" --===============8399093688310921457== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 16, 2020, at 5:15 AM, Dieter Leupold via Mailman-users wrote: > Hi, >=20 > I configured Postorius (via Apache2) to use https, which looks fine. But=20 > the connection to hyperkitty failed with "code 400, message Bad request=20 > syntax". I tried serveral settings....without success. Could you give me=20 > an example, which settings are to configure? > Thanks for your help! When you say "connection to hyperkitty failed", did you mean in the browser o= r when archiving the emails? If it is in browser, you can add `DEBUG=3DTrue` in your settings.py and get m= ore details, which can be helpful to determine what is happening here. I am n= ot completely sure why would HK have problem when P works fine, given that th= ey are both served from the same Django server. > --=20 >=20 > Dieter >=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 -- thanks, Abhilash Raj (maxking) --===============8399093688310921457==-- From brian_carpenter@emwd.com Thu Jan 16 20:09:55 2020 From: Brian Carpenter To: mailman-users@mailman3.org Subject: [MM3-users] Re: Listing/Exporting member list error: Mailman REST API not available. Please start Mailman core. Date: Thu, 16 Jan 2020 20:09:51 +0000 Message-ID: <157920539198.6164.17671454412443531246@mailman.iad1.psf.io> In-Reply-To: <66836f36-ccb5-4fd2-b9b4-b40860b9b480@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2150509928028034938==" --===============2150509928028034938== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Abhilash, Thomas is one of my clients and I helped install the Mailman 3 setup he is us= ing. I installed MM3 using your docker images. He is currently running versio= n 3.1. Lists with a smaller amount of members are exporting fine. However on = a list with around 1100 members, the request is timing out. Brian --===============2150509928028034938==-- From mark@msapiro.net Thu Jan 16 20:44:03 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header Date: Thu, 16 Jan 2020 12:43:54 -0800 Message-ID: In-Reply-To: <4c937e0e-7f18-78a5-3dd6-56ac5f28b1f3@gmx.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3136674399664904565==" --===============3136674399664904565== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/16/20 10:51 AM, Torge Riedel wrote: > > Such SPAM mails are currently hold for moderation with reason "not from > a list member". Is there no check for the "X-Spam: Yes" header or is > this check done later? If you set a Header Filter (in Postorius the Header filters tab) those checks are done before non-member moderation. This won't work for posts from members because the header checks are done between member moderation checks and non-member moderation checks, but if you create a Header Filter for header 'x-spam' and pattern 'yes' with action hold, a message from a non-member which has an X-Spam: Yes header should be held for that reason. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============3136674399664904565==-- From torgeriedel@gmx.de Sat Jan 18 14:13:45 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Mailman runners missing - nothing in logs Date: Sat, 18 Jan 2020 15:13:40 +0100 Message-ID: <6b9fdac0-5c6b-60b9-33bf-1b6911e8ddc9@gmx.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8842180537380413486==" --===============8842180537380413486== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, since migration from mailman2 to mailman3 I had twice the following, last tim= e today: When sending a mail to a list I get the following reply from postfix after a = while: connect to 127.0.0.1[127.0.0.1]:8024: Connection refused Searched on that and found some posts, where the following shell command is n= amed to check what is running: ps -fwwu mailman And I get this as output: UID=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 PID=C2=A0 PPID=C2=A0 C STIME TT= Y=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 TIME CMD mailman=C2=A0=C2=A0 1166=C2=A0=C2=A0=C2=A0=C2=A0 1=C2=A0 0 Jan07 ?=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 00:00:01 /opt/mailman/core/venv/bin/python3= /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg mailman=C2=A0=C2=A0 1180=C2=A0 1166=C2=A0 0 Jan07 ?=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 00:03:09 /opt/mailman/core/venv/bin/python3 /opt/mailman/c= ore/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=3Drest:0:1 mailman=C2=A0=C2=A0 1212=C2=A0 1180=C2=A0 0 Jan07 ?=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 00:01:10 /opt/mailman/core/venv/bin/python3 /opt/mailman/c= ore/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=3Drest:0:1 mailman=C2=A0 11039 11036=C2=A0 0 06:25 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 00:00:03 /usr/bin/uwsgi-core --ini mailman3.ini mailman=C2=A0 11064 11039=C2=A0 0 06:25 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 00:00:00 /usr/bin/uwsgi-core --ini mailman3.ini mailman=C2=A0 11065 11039=C2=A0 0 06:25 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 00:00:01 /usr/bin/uwsgi-core --ini mailman3.ini mailman=C2=A0 17257=C2=A0 1180=C2=A0 0 Jan12 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 00:00:37 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/ve= nv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=3Drest:0:1 Lots of expected runners are missing. After restarting the service the output= of the same command is: UID=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 PID=C2=A0 PPID=C2=A0 C STIME TT= Y=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 TIME CMD mailman=C2=A0 11039 11036=C2=A0 0 06:25 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 00:00:03 /usr/bin/uwsgi-core --ini mailman3.ini mailman=C2=A0 11064 11039=C2=A0 0 06:25 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 00:00:00 /usr/bin/uwsgi-core --ini mailman3.ini mailman=C2=A0 11065 11039=C2=A0 0 06:25 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 00:00:01 /usr/bin/uwsgi-core --ini mailman3.ini mailman=C2=A0 14430=C2=A0=C2=A0=C2=A0=C2=A0 1 13 14:50 ?=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailma= n/core/venv/bin/master -C /opt/mailman/core/mailman.cfg mailman=C2=A0 14434 14430 18 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Darchive:0:1 mailman=C2=A0 14435 14430 20 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Dbounces:0:1 mailman=C2=A0 14436 14430 18 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Dcommand:0:1 mailman=C2=A0 14437 14430 17 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Din:0:1 mailman=C2=A0 14438 14430 17 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Dlmtp:0:1 mailman=C2=A0 14439 14430 17 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Dnntp:0:1 mailman=C2=A0 14440 14430 19 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Dout:0:1 mailman=C2=A0 14441 14430 20 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Dpipeline:0:1 mailman=C2=A0 14442 14430 20 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Drest:0:1 mailman=C2=A0 14443 14430 17 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Dretry:0:1 mailman=C2=A0 14444 14430 17 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Dvirgin:0:1 mailman=C2=A0 14445 14430 18 14:50 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 00:00:01 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/ru= nner -C /opt/mailman/core/mailman.cfg --runner=3Ddigest:0:1 So now back to good. I checked all the logs prior to restarting the service i= n directory /opt/mailman/var/log, but I do not see any errors. And the master= was still running, I would expect that the master will start / restart a run= ner in case it died? Fun fact: First time of this problem was two weeks from now, which was two we= eks after migration to mailman3. I'm excited if it will happen in two weeks a= gain. Installed packages for core: mailman (3.3.0) mailman-hyperkitty (1.1.0) Any suggestions where I should have a deeper look and maybe find the root cau= se of this problem? Thanks in advance Torge --===============8842180537380413486==-- From torgeriedel@gmx.de Sat Jan 18 14:18:47 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Re: Another set of new releases Date: Sat, 18 Jan 2020 15:18:43 +0100 Message-ID: <3c650141-eb07-e884-64d4-32628f198135@gmx.de> In-Reply-To: <397d2ef9-f798-4746-86ba-1c2522ae0da8@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3138844797836303702==" --===============3138844797836303702== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am 13.01.20 um 03:42 schrieb Abhilash Raj: > - Django-mailman3 1.3.2 Hi, are there somewhere release notes for Django-mailman3? Thanks for your work and regards Torge --===============3138844797836303702==-- From torgeriedel@gmx.de Sat Jan 18 14:58:23 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header Date: Sat, 18 Jan 2020 15:58:19 +0100 Message-ID: <71ba7865-b82b-0372-6ee6-4a6d01923d24@gmx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1382185501224971547==" --===============1382185501224971547== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 16.01.20 um 21:43 schrieb Mark Sapiro: > On 1/16/20 10:51 AM, Torge Riedel wrote: >> Such SPAM mails are currently hold for moderation with reason "not from >> a list member". Is there no check for the "X-Spam: Yes" header or is >> this check done later? > > If you set a Header Filter (in Postorius the Header filters tab) those > checks are done before non-member moderation. > > This won't work for posts from members because the header checks are > done between member moderation checks and non-member moderation checks, > but if you create a Header Filter for header 'x-spam' and pattern 'yes' > with action hold, a message from a non-member which has an X-Spam: Yes > header should be held for that reason. > > Hi Mark, thank you for your answer. Just to understand that right: In case a posting w= ith an "X-Spam: Yes" header comes from a member, it will not be held? It will= be directly forwarded to the list? If yes, is there any chance to change or extend this? Best regards Torge --===============1382185501224971547==-- From torgeriedel@gmx.de Sat Jan 18 15:11:27 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail Date: Sat, 18 Jan 2020 16:11:22 +0100 Message-ID: <4ba6e465-b5ec-0ea2-02b2-528b633ef9f4@gmx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4503528968299007897==" --===============4503528968299007897== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 16.01.20 um 20:22 schrieb Terri Oda: > but I've definitely seen this behaviour in Mailman 2 and had trouble with M= ailman getting blocked as a result, so I think this would be a very nice feat= ure request. Hi Terri, I agree. So how to proceed on that? Get developers involved, post somewhere a= feature request? To be honest I don't know how this is handled in developmen= t community of mailman3. Best regards Torge --===============4503528968299007897==-- From maxking@asynchronous.in Sat Jan 18 18:30:58 2020 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Another set of new releases Date: Sat, 18 Jan 2020 10:30:30 -0800 Message-ID: <6ac2198f-12c1-40dd-afa7-b21e8e1d2bc4@www.fastmail.com> In-Reply-To: <3c650141-eb07-e884-64d4-32628f198135@gmx.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6030313991666928282==" --===============6030313991666928282== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sat, Jan 18, 2020, at 6:18 AM, Torge Riedel wrote: > Am 13.01.20 um 03:42 schrieb Abhilash Raj: > > - Django-mailman3 1.3.2 >=20 > Hi, >=20 > are there somewhere release notes for Django-mailman3? Unfortunately, no. I've been meaning to create one, but mostly it is an inter= nal library and any user facing changes are documented in the changelog for P= ostorius and Hyperkitty. If you look at the commits[1] since last release, there wasn't much changed e= xcept for new translations. https://gitlab.com/mailman/django-mailman3/compare/1.3.1...1.3.2 >=20 > Thanks for your work and regards > Torge > _______________________________________________ > 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) --===============6030313991666928282==-- From mark@msapiro.net Sat Jan 18 18:38:48 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header Date: Sat, 18 Jan 2020 10:38:35 -0800 Message-ID: In-Reply-To: <71ba7865-b82b-0372-6ee6-4a6d01923d24@gmx.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4647683136723894519==" --===============4647683136723894519== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/18/20 6:58 AM, Torge Riedel wrote: > Am 16.01.20 um 21:43 schrieb Mark Sapiro: >> >> This won't work for posts from members because the header checks are >> done between member moderation checks and non-member moderation checks, >> but if you create a Header Filter for header 'x-spam' and pattern 'yes' >> with action hold, a message from a non-member which has an X-Spam: Yes >> header should be held for that reason. >> >> > Hi Mark, > > thank you for your answer. Just to understand that right: In case a > posting with an "X-Spam: Yes" header comes from a member, it will not be > held? It will be directly forwarded to the list? No. I apologize for being unclear. A post from a member will first be handled according to that member's moderation action which may be the list's default action for posts from members or a specific action for that member. If that moderation action is reject, discard or hold, the post will be rejected, discarded or held as a moderated member post regardless of any header filters. If the action is accept, the post will be accepted without any further checks including the header checks. If the action is defer (default processing) the message will be held for matching the X-Spam: Yes header. What I meant was if the member's (or default) action was hold, the post would be held, but the reason would be moderated member, not header match. The bottom line here is the moderation action of accept should only be used in cases of a highly trusted member (such as a list owner) because it bypasses other checks, but the address is still subject to spoofing. In the normal case where a moderation hold is not desired, use the defer (default processing) action. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============4647683136723894519==-- From mark@msapiro.net Sat Jan 18 18:45:12 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail Date: Sat, 18 Jan 2020 10:45:03 -0800 Message-ID: In-Reply-To: <4ba6e465-b5ec-0ea2-02b2-528b633ef9f4@gmx.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5055901837321653057==" --===============5055901837321653057== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/18/20 7:11 AM, Torge Riedel wrote: > > I agree. So how to proceed on that? Get developers involved, post > somewhere a feature request? To be honest I don't know how this is > handled in development community of mailman3. You can post to mailman-developers(a)python.org, but such things tend to get put aside and forgotten. The best way to report a bug, feature request, issue, etc is to use the trackers at gitlab.com. In the case of Mailman core, this is -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============5055901837321653057==-- From mark@msapiro.net Sat Jan 18 22:14:45 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman runners missing - nothing in logs Date: Sat, 18 Jan 2020 14:14:33 -0800 Message-ID: In-Reply-To: <6b9fdac0-5c6b-60b9-33bf-1b6911e8ddc9@gmx.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8824834052766448323==" --===============8824834052766448323== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/18/20 6:13 AM, Torge Riedel wrote: > > So now back to good. I checked all the logs prior to restarting the > service in directory /opt/mailman/var/log, but I do not see any errors. > And the master was still running, I would expect that the master will > start / restart a runner in case it died? What's in /opt/mailman/var/log/mailman.log? There should be entries like Jan 18 13:51:11 2020 (11700) xxxx runner started. for each runner every time it starts and like Jan 18 13:47:31 2020 (10096) xxxx runner caught SIGTERM. Stopping. Jan 18 13:47:31 2020 (10096) xxxx runner exiting. for each runner every time it stops, but with perhaps a reason other than `caught SIGTERM` That should at least tell you when they stopped. Also, if they stopped for some reason. The master will only restart runners that exit if they exit because of SIGUSR1 or some internal error and even then, only the configured max_restarts number of times. Do you have a logrotate script for the logs in /opt/mailman/var/log, and if so, does it have a postrotate script that signals Mailman to reopen logs other than by a `mailman reopen` command, perhaps by signaling the master with other than SIGHUP? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============8824834052766448323==-- From ghalpern@shemesh.co.il Sun Jan 19 09:22:51 2020 From: Gila Halpern To: mailman-users@mailman3.org Subject: [MM3-users] Header and footer templates in MM3 Date: Sun, 19 Jan 2020 11:15:44 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1865132258128137872==" --===============1865132258128137872== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit I read the earlier message from Peter Mueller about message decoration, and where the templates are in the file system. However, when I edit the header and footer templates in Postorius, those templates do not appear in the location specified. Should I be looking somewhere else? (I intend to write a program to rotate though several headers/footers, so I need to know where to have it write to.) Gila Halpern --===============1865132258128137872==-- From torgeriedel@gmx.de Sun Jan 19 11:07:56 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Re: Another set of new releases Date: Sun, 19 Jan 2020 12:07:51 +0100 Message-ID: In-Reply-To: <6ac2198f-12c1-40dd-afa7-b21e8e1d2bc4@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3603423387815268618==" --===============3603423387815268618== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 18.01.20 um 19:30 schrieb Abhilash Raj: > any user facing changes are documented in the changelog for Postorius and H= yperkitty. Hi, I already thought that it might be only a library. And documenting the user f= acing changes should be enough. Thanks Torge --===============3603423387815268618==-- From torgeriedel@gmx.de Sun Jan 19 14:17:39 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman runners missing - nothing in logs Date: Sun, 19 Jan 2020 15:17:33 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1170674262939702773==" --===============1170674262939702773== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 18.01.20 um 23:14 schrieb Mark Sapiro: > On 1/18/20 6:13 AM, Torge Riedel wrote: >> So now back to good. I checked all the logs prior to restarting the >> service in directory /opt/mailman/var/log, but I do not see any errors. >> And the master was still running, I would expect that the master will >> start / restart a runner in case it died? > > What's in /opt/mailman/var/log/mailman.log? There should be entries like > > Jan 18 13:51:11 2020 (11700) xxxx runner started. > > for each runner every time it starts and like > > Jan 18 13:47:31 2020 (10096) xxxx runner caught SIGTERM. Stopping. > Jan 18 13:47:31 2020 (10096) xxxx runner exiting. > > for each runner every time it stops, but with perhaps a reason other > than `caught SIGTERM` > > That should at least tell you when they stopped. Also, if they stopped > for some reason. The master will only restart runners that exit if they > exit because of SIGUSR1 or some internal error and even then, only the > configured max_restarts number of times. > > Do you have a logrotate script for the logs in /opt/mailman/var/log, and > if so, does it have a postrotate script that signals Mailman to reopen > logs other than by a `mailman reopen` command, perhaps by signaling the > master with other than SIGHUP? > Hi Mark, I checked the logs for such entries and I do only see them when the logrotati= on runs and from yesterday where I restarted the service by myself. So - yes, I have logrotation configured. The logrotation has a postrotate scr= ipt configured which executes `systemctl reload mailman` and I see in the log= s, that it handles SIGUSR1. This happens daily in the morning and runs - for = what I see - without any problems. If I understand you right I should change it to "reopen" instead of "reload".= I think this is something I have to pass to mailman executable itself instea= d to systemctl, right? Best regards Torge --===============1170674262939702773==-- From torgeriedel@gmx.de Sun Jan 19 14:30:42 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail Date: Sun, 19 Jan 2020 15:30:37 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8236053779747280261==" --===============8236053779747280261== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Am 18.01.20 um 19:45 schrieb Mark Sapiro: > The best way to report a bug, feature request, issue, etc is to use the > trackers at gitlab.com. In the case of Mailman core, this is > Hi Mark, just opened a new issue: https://gitlab.com/mailman/mailman/issues/670 Best regards Torge --===============8236053779747280261==-- From torgeriedel@gmx.de Sun Jan 19 14:43:02 2020 From: Torge Riedel To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header Date: Sun, 19 Jan 2020 15:42:57 +0100 Message-ID: <0b057f85-fa63-77a4-6905-20d29447cd00@gmx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6879256639732644611==" --===============6879256639732644611== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am 18.01.20 um 19:38 schrieb Mark Sapiro: > On 1/18/20 6:58 AM, Torge Riedel wrote: >> Am 16.01.20 um 21:43 schrieb Mark Sapiro: >>> This won't work for posts from members because the header checks are >>> done between member moderation checks and non-member moderation checks, >>> but if you create a Header Filter for header 'x-spam' and pattern 'yes' >>> with action hold, a message from a non-member which has an X-Spam: Yes >>> header should be held for that reason. >>> >>> >> Hi Mark, >> >> thank you for your answer. Just to understand that right: In case a >> posting with an "X-Spam: Yes" header comes from a member, it will not be >> held? It will be directly forwarded to the list? > No. I apologize for being unclear. > > A post from a member will first be handled according to that member's > moderation action which may be the list's default action for posts from > members or a specific action for that member. > > If that moderation action is reject, discard or hold, the post will be > rejected, discarded or held as a moderated member post regardless of any > header filters. > > If the action is accept, the post will be accepted without any further > checks including the header checks. > > If the action is defer (default processing) the message will be held for > matching the X-Spam: Yes header. > > What I meant was if the member's (or default) action was hold, the post > would be held, but the reason would be moderated member, not header match. > > The bottom line here is the moderation action of accept should only be > used in cases of a highly trusted member (such as a list owner) because > it bypasses other checks, but the address is still subject to spoofing. > In the normal case where a moderation hold is not desired, use the defer > (default processing) action. > Hi Mark, thanks for clarification. I will add a header filter. One final question: When adding a new header filter I can select between diff= erent actions. And there is one named "Default Anti-Spam action" (roughly tra= nslated from German). I cannot find anything else about this somewhere else i= n the settings (Postorius). So what it is the "Default Anti-Spam action"? Best regards Torge --===============6879256639732644611==-- From mark@msapiro.net Sun Jan 19 23:40:04 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header Date: Sun, 19 Jan 2020 15:39:51 -0800 Message-ID: <80a64d66-3693-da54-8b6f-848df3b491cc@msapiro.net> In-Reply-To: <0b057f85-fa63-77a4-6905-20d29447cd00@gmx.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6343250143767736776==" --===============6343250143767736776== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/19/20 6:42 AM, Torge Riedel wrote: > > One final question: When adding a new header filter I can select between > different actions. And there is one named "Default Anti-Spam action" > (roughly translated from German). I cannot find anything else about this > somewhere else in the settings (Postorius). So what it is the "Default > Anti-Spam action"? There is a configuration setting with default [antispam] jump_chain: hold "Default Anti-Spam action" should set the action for that rule to None which means use the configured [antispam]jump_chain: value. However, there is a bug in REST in core that doesn't allow setting `None` so you can't chose that setting anyway. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============6343250143767736776==-- From phonig@cosmos.esa.int Tue Jan 21 16:51:39 2020 From: Paul Honig To: mailman-users@mailman3.org Subject: [MM3-users] start_chain not present in migrated lists Date: Tue, 21 Jan 2020 15:22:19 +0100 Message-ID: <06ca89e1-70ae-4953-83c2-d8222385b519@cosmos.esa.int> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4914045418794762932==" --===============4914045418794762932== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, Please let me know where I can post my question if this list is not the=20 right place. I'm configuring a mailing list server, migrating from Mailman 2.1 to=20 3.2.2, and I can't get the migrated mailing lists to work. When I create new mailing lists there is no problem. Here are the versions of Mailman I run : mailman 3.2.2 mailman-hyperkitty (1.1.0) django-mailman3 (1.2.0) postorius (1.3.2) mailmanclient (3.2.2) HyperKitty (1.2.2) The command line I use the migrate the mailing list: /opt/mailman_venv/bin/mailman -C /opt/mailman_venv/var/etc/mailman.cfg=20 import21 mltest(a)test.domain /var/vmail/mig/data/lists/mltest/config.pck When I send an email to a migrated list, of which I made myself a=20 member, no mail is sent, and I get the following stack trace in the log: =3D=3D> /var/log/mailman/mailman.log <=3D=3D Jan 21 15:02:37 2020 (15948) Uncaught runner exception: None Jan 21 15:02:37 2020 (15948) Traceback (most recent call last): =C2=A0 File=20 "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/runner.py",=20 line 173, in _one_iteration =C2=A0=C2=A0=C2=A0 self._process_one_file(msg, msgdata) =C2=A0 File=20 "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/runner.py",=20 line 266, in _process_one_file =C2=A0=C2=A0=C2=A0 keepqueued =3D self._dispose(mlist, msg, msgdata) =C2=A0 File=20 "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/runners/incoming.py"= ,=20 line 79, in _dispose =C2=A0=C2=A0=C2=A0 process(mlist, msg, msgdata, start_chain) =C2=A0 File=20 "/opt/mailman_venv/lib64/python3.6/site-packages/mailman/core/chains.py",=20 line 40, in process =C2=A0=C2=A0=C2=A0 chain =3D config.chains[start_chain] KeyError: None Jan 21 15:02:37 2020 (15948) SHUNTING:=20 1579615357.5331464+c5918e305ec281d47ef0caaed070c8c4bde26ee3 It seems like the start_chain has value 'None' and that prevents the=20 mail from processed, but I can't find where to correctly set the=20 start_chain. Please let me know how I can remedy this issue. Kind regards, Paul Honig This message is intended only for the recipient(s) named above. It may contai= n proprietary information and/or protected content. Any unauthorised disclosu= re, use, retention or dissemination is prohibited. If you have received this = e-mail in error, please notify the sender immediately. ESA applies appropriat= e organisational measures to protect personal data, in case of data privacy q= ueries, please contact the ESA Data Protection Officer (dpo(a)esa.int). --===============4914045418794762932==-- From mark@msapiro.net Tue Jan 21 17:33:53 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: start_chain not present in migrated lists Date: Tue, 21 Jan 2020 09:33:40 -0800 Message-ID: <9ecede11-f8ce-ad4d-0d6c-f5bf403ea38f@msapiro.net> In-Reply-To: <06ca89e1-70ae-4953-83c2-d8222385b519@cosmos.esa.int> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4017944092909486086==" --===============4017944092909486086== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/21/20 6:22 AM, Paul Honig wrote: > > It seems like the start_chain has value 'None' and that prevents the > mail from processed, but I can't find where to correctly set the > start_chain. You are correct. Every list has a 'posting_chain' attribute and it seems for your imported lists, that attribute's value is None. I don't know how that can happen. How did you create the lists before importing them? > Please let me know how I can remedy this issue. You can use `mailman shell` mailman shell -l mltest(a)test.domain Welcome to the GNU Mailman shell The variable 'm' is the mltest(a)test.domain mailing list >>> print(m.posting_chain) None >>> m.posting_chain = 'default-posting-chain' >>> commit() -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============4017944092909486086==-- From frank@heuveltop.nl Wed Jan 22 00:30:43 2020 From: Frank van den Heuvel To: mailman-users@mailman3.org Subject: [MM3-users] Cannot locate manage.py Date: Wed, 22 Jan 2020 01:08:05 +0100 Message-ID: <6d9359a0-9724-006f-2976-d78c64832209@heuveltop.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4802785120081857395==" --===============4802785120081857395== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, While following https://docs.mailman3.org/en/latest/migration.html, I=20 want to execute: python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/arc= hives/private/foo-list.mbox/foo-list.mbox Of course edited with values for my list. But I already get stuck in not=20 being able to locate "manage.py". When I run "locate manage.py", I get: /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template= /manage.py-tpl /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py Which one is the right one? With kind regards and thanks for your work! Frank van den Heuvel BTW: This is a debian 10.2 with Mailman3: Django Version: 2.2.9 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.7.3 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '= /usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload= ', '/opt/mailman/mm/venv/lib/python3.7/site-packages'] Server time: Tue, 21 Jan 2020 08:34:45 -0800 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', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google') 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') --===============4802785120081857395==-- From mark@msapiro.net Wed Jan 22 00:56:40 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cannot locate manage.py Date: Tue, 21 Jan 2020 16:56:28 -0800 Message-ID: In-Reply-To: <6d9359a0-9724-006f-2976-d78c64832209@heuveltop.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8474731070036086073==" --===============8474731070036086073== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/21/20 4:08 PM, Frank van den Heuvel wrote: > Hello, >=20 > While following https://docs.mailman3.org/en/latest/migration.html, I > want to execute: >=20 > =C2=A0=C2=A0=C2=A0=C2=A0python manage.py hyperkitty_import -l foo-list(a)ex= ample.com > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox >=20 > Of course edited with values for my list. But I already get stuck in not > being able to locate "manage.py". >=20 > When I run "locate manage.py", I get: >=20 > /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_templa= te/manage.py-tpl >=20 > /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py > /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py >=20 > Which one is the right one? Probably none of those. I'm not that familiar with the file layout in the Debian package if that's what you installed, but I would expect to find it in /opt/mailman/mm/venv/bin/ and I'd expect to find the files django_admin and django_admin.py. Both of those will run the Django management interface, but they won't work because they won't access your settings. I put the following executable in /opt/mailman/mm/bin #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=3D/opt/mailman/mm export DJANGO_SETTINGS_MODULE=3Dsettings django-admin $@ This assumes my settings.py file is /opt/mailman/mm/settings.py. If yours is elsewhere you may need to adjust PYTHONPATH and/or DJANGO_SETTINGS_MODULE. For example, on another server with the settings at /opt/mailman/mm/mailman_web/production.py I have export DJANGO_SETTINGS_MODULE=3Dmailman_web.production --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============8474731070036086073==-- From shashikanth.komandoor@gmail.com Thu Jan 23 16:36:09 2020 From: Shashikanth Komandoor To: mailman-users@mailman3.org Subject: [MM3-users] Cannot see the cron jobs for Mailman 3 Installed Date: Thu, 23 Jan 2020 18:19:47 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3379916977637719781==" --===============3379916977637719781== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, I have setup the Mailman 3 on my RHEL 7.5 box and found it was working fine. But I found that I am not getting daily summary notifications for which I learnt after browsing through different websites, there should be an entry of *checkdb* in the cron job list. But I did not find any such nor I don't find any cron job updated after the installation of mailman 3. So, please guide how to get those cron jobs of mailman 3 installed again without disturbing the already installed setup. Thanks in advance. -- Thanks & Regards, Shashi Kanth.K 9052671936 --===============3379916977637719781==-- From mark@msapiro.net Thu Jan 23 18:05:13 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cannot see the cron jobs for Mailman 3 Installed Date: Thu, 23 Jan 2020 10:05:03 -0800 Message-ID: <5c1b8992-2adc-0695-b8cd-e985d9ef7bb0@msapiro.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5176963295446773868==" --===============5176963295446773868== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/23/20 4:49 AM, Shashikanth Komandoor wrote: > Hi, > > I have setup the Mailman 3 on my RHEL 7.5 box and found it was working > fine. But I found that I am not getting daily summary notifications for > which I learnt after browsing through different websites, there should be > an entry of *checkdb* in the cron job list. checkdbs is a Mailman 2.1 job The equivalent Mailman 3 job is `mailman notify` > But I did not find any such nor I don't find any cron job updated after > the installation of mailman 3. See and If you installed Mailman from a package and the cron's weren't installed, report this to the packager. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============5176963295446773868==-- From shashikanth.komandoor@gmail.com Fri Jan 24 08:10:38 2020 From: Shashikanth Komandoor To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cannot see the cron jobs for Mailman 3 Installed Date: Fri, 24 Jan 2020 12:59:29 +0530 Message-ID: In-Reply-To: <5c1b8992-2adc-0695-b8cd-e985d9ef7bb0@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2892408203894284746==" --===============2892408203894284746== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Thank you Mark Sapiro. As per your suggestion, I have gone through the mentioned URLs and understood that the command "mailman notify" is responsible to send the periodic notifications to the owners of the list which of course should be as part of the cron job list (but it is not in my case). FYI, I am using mailman 3.2.3. And in my case, when I run the command "mailman notify" I am getting an error saying that the command "notify" is not present. *(venv3) [root(a)mailman3 commands]# mailman notifyUsage: mailman [OPTIONS] COMMAND [ARGS]...Try "mailman -h" for help.Error: No such command "notify".* And I also saw the help menu of mailman where I don't find any command displaying "notify" and its explanation. I don't understand where I had done wrong. Could you please help me in this regard? On Thu, Jan 23, 2020 at 11:35 PM Mark Sapiro wrote: > On 1/23/20 4:49 AM, Shashikanth Komandoor wrote: > > Hi, > > > > I have setup the Mailman 3 on my RHEL 7.5 box and found it was > working > > fine. But I found that I am not getting daily summary notifications for > > which I learnt after browsing through different websites, there should be > > an entry of *checkdb* in the cron job list. > > > checkdbs is a Mailman 2.1 job The equivalent Mailman 3 job is `mailman > notify` > > > > But I did not find any such nor I don't find any cron job updated > after > > the installation of mailman 3. > > > See > < > https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs > > > and > < > https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required > > > > If you installed Mailman from a package and the cron's weren't > installed, report this to the packager. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936 --===============2892408203894284746==-- From mark@msapiro.net Fri Jan 24 15:26:24 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cannot see the cron jobs for Mailman 3 Installed Date: Fri, 24 Jan 2020 07:26:11 -0800 Message-ID: <7485b4e9-1980-3bd0-e9a7-e07b341966bf@msapiro.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1053896412888930534==" --===============1053896412888930534== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/23/20 11:29 PM, Shashikanth Komandoor wrote: > Thank you Mark Sapiro. > > As per your suggestion, I have gone through the mentioned URLs and > understood that the command "mailman notify" is responsible to send the > periodic notifications to the owners of the list which of course should be > as part of the cron job list (but it is not in my case). > > FYI, I am using mailman 3.2.3. There was no `mailman notify` command, and thus no way to get these periodic notifications, prior to Mailman 3.3.0. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============1053896412888930534==-- From mark@msapiro.net Fri Jan 24 19:56:04 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Header and footer templates in MM3 Date: Fri, 24 Jan 2020 11:55:54 -0800 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6138248498006376352==" --===============6138248498006376352== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/19/20 1:15 AM, Gila Halpern wrote: > I read the earlier message from Peter Mueller about message decoration, and > where the templates are in the file system. However, when I edit the > header and footer templates in Postorius, those templates do not appear in > the location specified. Should I be looking somewhere else? The templates created in Postorius are created in the postorius_emailtemplate table in Mailman's database and referenced via URLs like 'https://example.com/mailman3/api/templates/list//'. I.e., they are not stored in the file system. > (I intend to > write a program to rotate though several headers/footers, so I need to know > where to have it write to.) If Postorius has set a template for a list, it has set the URI for that template and list to one similar to that above and that URI ultimately references the template in the database. You have choices. You can set the templates in Postorius and your program can do database queries to rotate the template text, or you can set the template URIs via Mailman's TemplateManager to file system paths or not set them and use the default paths (deleting them in Postorius will leave them unset). See --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============6138248498006376352==-- From shashikanth.komandoor@gmail.com Sat Jan 25 06:11:57 2020 From: Shashikanth Komandoor To: mailman-users@mailman3.org Subject: [MM3-users] Can I install Mailman 3.3 on RHEL 8 ? Date: Sat, 25 Jan 2020 07:55:01 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1956836936717386914==" --===============1956836936717386914== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi Team/Sir, Can Mailman 3.3 be installed on RHEL 8? I got this query because while I was trying to install the prerequisites for Mailman 3.3 as per the website http://docs.mailman3.org/en/latest/devsetup.html I found nodejs-less is also to be installed. But I don't find the nodejs-less as part of BaseOS packages or the AppStream modules. Please suggest how to go ahead. -- Thanks & Regards, Shashi Kanth.K 9052671936 --===============1956836936717386914==-- From ghalpern@shemesh.co.il Sun Jan 26 13:11:43 2020 From: ghalpern@shemesh.co.il To: mailman-users@mailman3.org Subject: [MM3-users] Re: Header and footer templates in MM3 Date: Sun, 26 Jan 2020 13:11:40 +0000 Message-ID: <158004430095.9939.2776561253081975720@mailman.iad1.psf.io> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6526208421132282163==" --===============6526208421132282163== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I think that database queries would be better for my purposes, but it does le= ad me to a new problem. My MM3 installation is with Docker, which means that= Docker set up the PostgreSQL database automatically, which means that I do n= ot know the password for said database. Do I have any hope of finding it, or= will I have to take a different option? --===============6526208421132282163==-- From ghalpern@shemesh.co.il Sun Jan 26 13:35:42 2020 From: Gila Halpern To: mailman-users@mailman3.org Subject: [MM3-users] Re: Header and footer templates in MM3 Date: Sun, 26 Jan 2020 13:35:39 +0000 Message-ID: <158004573922.9943.12681027869797011646@mailman.iad1.psf.io> In-Reply-To: <158004430095.9939.2776561253081975720@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8304845890264228019==" --===============8304845890264228019== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Never mind, I found it. For everyone else's edification, the username and pa= ssword can be found in docker-compose.yaml --===============8304845890264228019==-- From hansen@rc.org Mon Jan 27 00:43:33 2020 From: Allan Hansen To: mailman-users@mailman3.org Subject: [MM3-users] DMARC Mitigation Wrap Date: Sun, 26 Jan 2020 16:43:27 -0800 Message-ID: <1AB005A8-764C-46CD-8AB9-E5484F8B16F5@rc.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8755680852377564186==" --===============8755680852377564186== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable All, After a reinstall I=E2=80=99m back to thinking about the MM3 DMARC mitigation= issue. Until munging can be improved, I will be using the option to wrap: MM3 has the option to wrap the main message with a wrap_message. It appears, = however, that MM3 is oblivious to all my attempts to include whitespace, in t= his case a . When the enclosed message is automatically unwrapped by the = receiving client, this causes the wrap and enclosed message's From: header to= butt up against each other, which is rather ugly. I tried many tricks, but n= one worked, such as, , SPACE+, TAB+, , SHIFT-RETURN, two RETUR= NS, \r\n and UTF-8 codes. They all either got ignored or copied as entered to= the output message. Here=E2=80=99s an example. I just want to put a divider = after the wrap_message main text. The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list.\r\n -------------------------- ----------------------------------------------------------------------\r\n From: Allan Hansen > Subject: [Testlist] wrap with divider and BLANKLINE Which coding option am I missing? I have searched for one online. Yours, Allan Hansen allan_hansen(a)icloud.com --===============8755680852377564186==-- From hansen@rc.org Mon Jan 27 00:43:35 2020 From: Allan Hansen To: mailman-users@mailman3.org Subject: [MM3-users] DMARC Munging Date: Sun, 26 Jan 2020 16:43:30 -0800 Message-ID: <4AFF3D3D-72BD-4BD7-85E6-24A8FE891D34@rc.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0002831624281659615==" --===============0002831624281659615== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable All, The munged From: header in MM3 still says 'name' via =E2=80=98listname=E2=80=99 <=E2=80=98listaddress=E2=80=99> This caused me and my subscribers a lot of grief in MM2: Some mail clients use the first part up to the From for future key-ahead for = new email to =E2=80=99name=E2=80=99, hiding the address, so what they think i= s a personal message for =E2=80=99name=E2=80=99, instead goes to the entire l= ist. Red faces all around. Stephen Thurnbull earlier suggested further munging by replacing the list add= ress in the From: header like this: 'name' via =E2=80=98listname=E2=80=99 <=E2=80=98whoopsieaddress=E2=80=99> Which will return an automated reply explaining the issue. I like this option= . How can I get that in? Yours, Allan Hansen allan_hansen(a)icloud.com PS: I always use sender in Reply-To. --===============0002831624281659615==-- From mark@msapiro.net Mon Jan 27 06:33:08 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: DMARC Munging Date: Sun, 26 Jan 2020 22:32:55 -0800 Message-ID: In-Reply-To: <4AFF3D3D-72BD-4BD7-85E6-24A8FE891D34@rc.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7054373452737643970==" --===============7054373452737643970== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/26/20 4:43 PM, Allan Hansen wrote: > All, >=20 > The munged From: header in MM3 still says > 'name' via =E2=80=98listname=E2=80=99 <=E2=80=98listaddress=E2=80=99> >=20 > This caused me and my subscribers a lot of grief in MM2: > Some mail clients use the first part up to the From for future key-ahead fo= r new email to =E2=80=99name=E2=80=99, hiding the address, so what they think= is a personal message for =E2=80=99name=E2=80=99, instead goes to the entire= list. Red faces all around. >=20 > Stephen Thurnbull earlier suggested further munging by replacing the list a= ddress in the From: header like this: >=20 > 'name' via =E2=80=98listname=E2=80=99 <=E2=80=98whoopsieaddress=E2=80=99> >=20 > Which will return an automated reply explaining the issue. I like this opti= on. How can I get that in? You can file an issue at .=20 That will at least get it on the table, but there are no guarantees as=20 to if/when it would be implemented. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============7054373452737643970==-- From mark@msapiro.net Mon Jan 27 06:55:57 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: DMARC Mitigation Wrap Date: Sun, 26 Jan 2020 22:55:44 -0800 Message-ID: <3618d8e5-494e-9832-fec1-bd81f398378d@msapiro.net> In-Reply-To: <1AB005A8-764C-46CD-8AB9-E5484F8B16F5@rc.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7230370270418806542==" --===============7230370270418806542== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/26/20 4:43 PM, Allan Hansen wrote: >=20 > MM3 has the option to wrap the main message with a wrap_message. It appears= , however, that MM3 is oblivious to all my attempts to include whitespace, in= this case a . When the enclosed message is automatically unwrapped by th= e receiving client, this causes the wrap and enclosed message's From: header = to butt up against each other, which is rather ugly. I tried many tricks, but= none worked, such as, , SPACE+, TAB+, , SHIFT-RETURN, two RET= URNS, \r\n and UTF-8 codes. They all either got ignored or copied as entered = to the output message. Here=E2=80=99s an example. I just want to put a divide= r after the wrap_message main text. >=20 > The From address of this message has been replaced with the list > address, while the From name has 'via list' appended. Please be > careful when using 'via list' addresses later for new emails, as they > will be sent to the whole list.\r\n -------------------------- > ----------------------------------------------------------------------\r\n > From: Allan Hansen > > Subject: [Testlist] wrap with divider and BLANKLINE >=20 > Which coding option am I missing? I have searched for one online. I assume you are entering your text in Postorius in the DMARC wrapped=20 message text box. There are a number of things going on here. Postorius is wrapping and=20 filling the text and stripping trailing whitespace. If you want more=20 whitespace, I suggest following your text with one or more empty lines=20 and a single dot as in The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list. ------------------------------------------------------------------- . In the above, the blank lines before and after the line of dashes will=20 be preserved as will the final dot which should be unobtrusive enough. More importantly, the rendering of the received message is up to your=20 mail client. Your's apparently begins the wrapped message immediately=20 after the wrapper's text, but many will not do that. Unless you actually=20 view the received message in every mail client used by your user's, you=20 won't know what they actually see. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============7230370270418806542==-- From shashikanth.komandoor@gmail.com Tue Jan 28 14:55:21 2020 From: Shashikanth Komandoor To: mailman-users@mailman3.org Subject: [MM3-users] Cron of Mailman notify is not working Date: Tue, 28 Jan 2020 16:33:28 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1039554249210393776==" --===============1039554249210393776== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hello, With your help, I was able to setup mailman 3.3 on my RHEL 7.5 machine and running well and good. For daily notification I have added the below line in the crontab: 00 08 * * * /var/lib/mailman/venv3/bin/mailman notify But this cron job is not working while I was able to run the same command manually at my CLI. Please help if there is any issue with mailman 3.3 or cronjob. -- Thanks & Regards, Shashi Kanth.K 9052671936 --===============1039554249210393776==-- From mark@msapiro.net Tue Jan 28 16:38:36 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cron of Mailman notify is not working Date: Tue, 28 Jan 2020 08:38:22 -0800 Message-ID: <9336783e-8b18-3972-c20e-7f3a35879354@msapiro.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2521510168098187250==" --===============2521510168098187250== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/28/20 3:03 AM, Shashikanth Komandoor wrote: > Hello, > > With your help, I was able to setup mailman 3.3 on my RHEL 7.5 > machine and running well and good. > > For daily notification I have added the below line in the crontab: > > 00 08 * * * /var/lib/mailman/venv3/bin/mailman notify > > But this cron job is not working while I was able to run the same > command manually at my CLI. Into exactly what crontab did you put it? That is the correct line if you put it in the mailman user's crontab, but if you put it in a system crontag, e.g./etc/cron.d/mailman, it needs a 'user_name' argument between the date/time fields and the commands. E.g., 00 08 * * * mailman /var/lib/mailman/venv3/bin/mailman notify although the Mailman user may not be 'mailman' in your case. You should see some errors from cron in /var/log/syslog at 08:00 that would give you a hint. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============2521510168098187250==-- From jeffrey@bit.nl Tue Jan 28 16:57:17 2020 From: Jeffrey D To: mailman-users@mailman3.org Subject: [MM3-users] Mass subscribe gives HTTP Error 500 when using custom template Date: Tue, 28 Jan 2020 14:15:28 +0000 Message-ID: <158022092832.9940.357497016256534263@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7294737313047774535==" --===============7294737313047774535== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, I have some issues with the Mass Subscribe option on Mailman 3.2.1. When usin= g a custom "The notice sent to a member when they are subscribed to the maili= ng list." template, Postorius will throw an exception after pushing the "Subs= cribe Users" button on Mass Subscribe. In the web interface you will see a red notification bar with the text: "HTTP= Error 500: b'A server error occurred. Please contact the administrator.'". A= nd in the Mailman.log you will see the following error message: Traceback (most recent call last): File "/usr/lib/python3.7/wsgiref/handlers.py", line 137, in run self.result =3D application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line= 50, in wrapper rtn =3D function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 216, in= __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ File "falcon/api.py", line 189, in falcon.api.API.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/members.py", line 266, in= on_post pre_approved=3Dpre_approved) File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 52= 0, in register list(workflow) File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in = __next__ return step() File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 32= 6, in _step_do_subscription self.member =3D self.mlist.subscribe(self.subscriber) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line= 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 49= 4, in subscribe notify(SubscriptionEvent(self, member)) File "/usr/lib/python3/dist-packages/zope/event/__init__.py", line 31, in n= otify subscriber(event) File "/usr/lib/python3/dist-packages/mailman/app/membership.py", line 169, = in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3/dist-packages/mailman/app/notifications.py", line 52= , in send_welcome_message 'list:user:notice:welcome', mlist, language=3Dlanguage.code)) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 188, = in get name, lookup_context, **substitutions) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line= 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 109, = in get contents =3D protocols.get(actual_uri, **auth) File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line = 38, in get response =3D requests.get(url, timeout=3DREQUEST_TIMEOUT, **kws) File "/usr/lib/python3/dist-packages/requests/api.py", line 75, in get return request('get', url, params=3Dparams, **kwargs) File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request return session.request(method=3Dmethod, url=3Durl, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in re= quest resp =3D self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in se= nd r =3D adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 516, in se= nd raise ConnectionError(e, request=3Drequest) requests.exceptions.ConnectionError: HTTPConnectionPool(host=3D'localhost', p= ort=3D8000): Max retries exceeded with url: /postorius/api/templates/list//list:user:notice:welcome (Caused by NewConnectionError(': Failed to establish a new= connection: [Errno 111] Connection refused')) Postorius/Mailman is running on port 8001, only Postorius still connecting on= port 8000. Anyone seen something similar? Thanks in advance! Jeffrey --===============7294737313047774535==-- From mark@msapiro.net Tue Jan 28 20:36:31 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mass subscribe gives HTTP Error 500 when using custom template Date: Tue, 28 Jan 2020 12:36:20 -0800 Message-ID: In-Reply-To: <158022092832.9940.357497016256534263@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0737974228831601068==" --===============0737974228831601068== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/28/20 6:15 AM, Jeffrey D wrote: > Hi, >=20 > I have some issues with the Mass Subscribe option on Mailman 3.2.1. When us= ing a custom "The notice sent to a member when they are subscribed to the mai= ling list." template, Postorius will throw an exception after pushing the "Su= bscribe Users" button on Mass Subscribe. ... > requests.exceptions.ConnectionError: HTTPConnectionPool(host=3D'localhost',= port=3D8000): Max retries exceeded with url: /postorius/api/templates/list/<= MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError(': Failed to establish a n= ew connection: [Errno 111] Connection refused')) >=20 > Postorius/Mailman is running on port 8001, only Postorius still connecting = on port 8000. What is your setting in settings(_local).py for=20 POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default POSTORIUS_TEMPLATE_BASE_URL =3D 'http://localhost:8000' It should be the base URL for connecting to Postorius. I.e., if you=20 normally connect to Postorius via https://www.example.com/postorius, it=20 should be https://www.example.com You say Postorius/Mailman is running on port 8001. Mailman core's rest=20 server should be listening on port 8001, but your web server can't proxy=20 to Postorius on that port. Normally, the wsgi server that supports wsgi=20 access to Django (Postorius and HyperKitty) listens on port 8000, at=20 least if it is gunicorn or uwsgi proxied from your web server, or if=20 it's Apache and mod_wsgi, proxying is not involved. Again, it looks like you may be using Apache and mod_wsgi in which case=20 you could have POSTORIUS_TEMPLATE_BASE_URL set to something like=20 https://www.example.com or even http://localhost or http://localhost:80,=20 but not port 8000 if no wsgi server is listening there. Also, the URL is now in the database entry for this template in the=20 postorius_emailtemplate table, so even after you fix=20 POSTORIUS_TEMPLATE_BASE_URL, you'll probably have to delete and recreate=20 the template in Postorius. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============0737974228831601068==-- From shashikanth.komandoor@gmail.com Wed Jan 29 08:01:11 2020 From: Shashikanth Komandoor To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cron of Mailman notify is not working Date: Wed, 29 Jan 2020 08:01:07 +0000 Message-ID: <158028486721.9938.14213406645760658426@mailman.iad1.psf.io> In-Reply-To: <9336783e-8b18-3972-c20e-7f3a35879354@msapiro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5755481349680076928==" --===============5755481349680076928== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thank you Mark Sapiro. I have tried as per your suggestion but failed unfortunately might be because= of my improper setup. But I learnt one thing and fixed it and would like to share with you so that = you may correct me if I am wrong or it would be useful for others. I observed that the "notify" subcommand can be run only while I am in the /va= r/lib/mailman/mailman directory where my mailman core is installed (through G= ITHUB). And moreover I installed all the components of the mailman using the root use= r only and so there is no mailman user on my machine. And hence I wrote the below entry in the crontab directly and found it is wor= king fine. 00 08 * * * cd /var/lib/mailman/mailman; /var/lib/mailman/venv3/bin/python /v= ar/lib/mailman/venv3/bin/mailman notify Please correct me if my analysis is wrong or please also suggest me if I coul= d work it out in a more optimal manner. --===============5755481349680076928==-- From shashikanth.komandoor@gmail.com Wed Jan 29 12:06:08 2020 From: Shashikanth Komandoor To: mailman-users@mailman3.org Subject: [MM3-users] where to configure max_days_to_hold on MM3 GUI interface? Date: Wed, 29 Jan 2020 10:12:43 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3167824419516980122==" --===============3167824419516980122== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi Sir, I came to know that the held messages can be restricted to be processed after a specific no of days or can be discard after some days using the parameter *max_days_to_hold*. But I could see that parameter value configurable on MM2 GUI interface in General Options but I don't see the same on the MM3 GUI interface. Could you please help me if I am missing something? -- Thanks & Regards, Shashi Kanth.K 9052671936 --===============3167824419516980122==-- From mark@msapiro.net Wed Jan 29 17:50:10 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface? Date: Wed, 29 Jan 2020 09:49:59 -0800 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6910620083619179668==" --===============6910620083619179668== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: >=20 > But I could see that parameter value configurable on MM2 GUI > interface in General Options but I don't see the same on the MM3 GUI > interface. There are many core settings not (yet) exposed in Postorius.=20 max_days_to_hold. is one of them. It can be set via `mailman shell` or=20 via the REST API=20 . --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============6910620083619179668==-- From mark@msapiro.net Wed Jan 29 18:06:16 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cron of Mailman notify is not working Date: Wed, 29 Jan 2020 10:06:08 -0800 Message-ID: <9fe34d28-77cf-0372-68c3-15f9b965a1b3@msapiro.net> In-Reply-To: <158028486721.9938.14213406645760658426@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8010508636151820263==" --===============8010508636151820263== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/29/20 12:01 AM, Shashikanth Komandoor wrote: >=20 > I observed that the "notify" subcommand can be run only while I am in the /= var/lib/mailman/mailman directory where my mailman core is installed (through= GITHUB). I think you mean GitLab, but in any case, the reason for this is you=20 have to be in that directory for the mailman command to find your=20 mailman.cfg file. I deal with this by creating a separate bin/ directory for these=20 commends, in my case /opt/mailman/mm/bin because Mailman is installed in=20 /opt/mailman/mm/, and my /opt/mailman/mm/bin/mailman file contains #!/bin/bash exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ > And moreover I installed all the components of the mailman using the root u= ser only and so there is no mailman user on my machine. >=20 > And hence I wrote the below entry in the crontab directly and found it is w= orking fine. >=20 > 00 08 * * * cd /var/lib/mailman/mailman; /var/lib/mailman/venv3/bin/python = /var/lib/mailman/venv3/bin/mailman notify The /var/lib/mailman/venv3/bin/python is probably not needed as=20 /var/lib/mailman/venv3/bin/mailman should contain the shebang line #!/var/lib/mailman/venv3/bin/python --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============8010508636151820263==-- From maxking@asynchronous.in Wed Jan 29 18:31:00 2020 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman3 on Debian 10 Date: Wed, 29 Jan 2020 10:30:34 -0800 Message-ID: <831e8a1c-9cc5-467d-b3f3-3406bdfba92b@www.fastmail.com> In-Reply-To: =?utf-8?q?=3CLO2P265MB0704A8E624F7389ECC35377198050=40LO2P265MB?= =?utf-8?q?0704=2EGBRP265=2EPROD=2EOUTLOOK=2ECOM=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5274819248938169751==" --===============5274819248938169751== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Please use mailman-users(a)mailman3.org for questions related to Mailman 3. On Wed, Jan 29, 2020, at 9:22 AM, Bala Mutyam wrote: > Hi there, >=20 > I=E2=80=99m trying to install Mailman3 on Debian 10 as follows . > 1) Installed MariaDB, created databases, users for mailman3 and mailman3-web > 2) Then installed mailman3-full', 'dbconfig-mysql', 'python-pymysql', 'pyth= on3-pymysql', 'python3-mysqldb', 'nginx using Anisble script. > 3) I have removed Apache2 as it was installed with mailman3-full. > 4) Created a symbolic link for /etc/mailman3/nginx.conf and updated config = files for mailman.cfg, mailman-hyperkitty.cfg, 25_mm3_macros, 455_mm3_router = and 55_mm3_transport >=20 > but the mailman service is not able to start it=E2=80=99s giving below erro= r. Could you help me how to resolve it please? And also instructions for to i= nstall Mailman3 using Debian packages mailman3-full. I would like to use MySQ= l as backend and Exim4 as mail server. I couldn=E2=80=99t find new mailing l= ist using the command line utility (/usr/sbin/newlist? >=20 > Please see the attached Traceback. >=20 > On webUI I=E2=80=99m seeing > Server error > An error occurred while processing your request. >=20 >=20 > *Attachments:* > * Mailman3 Errors.txt -- thanks, Abhilash Raj (maxking) --===============5274819248938169751==-- From mark@msapiro.net Wed Jan 29 22:24:11 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman3 on Debian 10 Date: Wed, 29 Jan 2020 14:23:59 -0800 Message-ID: In-Reply-To: <831e8a1c-9cc5-467d-b3f3-3406bdfba92b@www.fastmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1618236727115629584==" --===============1618236727115629584== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable > On Wed, Jan 29, 2020, at 9:22 AM, Bala Mutyam wrote: >=20 >> but the mailman service is not able to start it=E2=80=99s giving below err= or. Could you help me how to resolve it please? And also instructions for to = install Mailman3 using Debian packages mailman3-full. I would like to use MyS= Ql as backend and Exim4 as mail server. I couldn=E2=80=99t find new mailing = list using the command line utility (/usr/sbin/newlist? Questions about the installation of Debian packages should be directed=20 to Debian. >> Please see the attached Traceback. Which said in part: > urllib.error.HTTPError: HTTP Error 401: b'{\n "title": "401 Unauthorized= ",\n "description": "REST API authorization failed"\n}' The most likely cause of this is your Django settings in=20 settings(_local).py for MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS do not match the mailman.cfg [webservice] settings=20 for admin_user and admin_pass (defaults restadmin and restpass). --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============1618236727115629584==-- From hansen@rc.org Thu Jan 30 00:40:02 2020 From: Allan Hansen To: mailman-users@mailman3.org Subject: [MM3-users] Re: DMARC Munging Date: Wed, 29 Jan 2020 16:39:58 -0800 Message-ID: <0FC9CA07-2AA4-4AE1-B907-5759E2CB334E@rc.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7536696997447979445==" --===============7536696997447979445== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Mark, et al., I have entered a ticket at gitlab. Thanks. Is there a way for me to make this change to the From header munging until it= is implemented in the production version? I made MM2 do the munging using su= ch a change on your recommendation and it has worked. Our installation is from source, which might make it possible/easier? I have played a lot with the wrapping option and have come to the conclusion = that it will not work. In some cases, the Apple Mail client for the desktop s= imply did not display the internal message, while iOS worked fine. The header= munging is safer. Yours, Allan Hansen allan_hansen(a)icloud.com > On Jan 26, 2020, at 22:32 , Mark Sapiro wrote: >=20 > On 1/26/20 4:43 PM, Allan Hansen wrote: >> All, >> The munged From: header in MM3 still says >> 'name' via =E2=80=98listname=E2=80=99 <=E2=80=98listaddress=E2=80=99> >> This caused me and my subscribers a lot of grief in MM2: >> Some mail clients use the first part up to the From for future key-ahead f= or new email to =E2=80=99name=E2=80=99, hiding the address, so what they thin= k is a personal message for =E2=80=99name=E2=80=99, instead goes to the entir= e list. Red faces all around. >> Stephen Thurnbull earlier suggested further munging by replacing the list = address in the From: header like this: >> 'name' via =E2=80=98listname=E2=80=99 <=E2=80=98whoopsieaddress=E2=80=99> >> Which will return an automated reply explaining the issue. I like this opt= ion. How can I get that in? >=20 >=20 > You can file an issue at . That = will at least get it on the table, but there are no guarantees as to if/when = it would be implemented. >=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/ --===============7536696997447979445==-- From mark@msapiro.net Thu Jan 30 00:53:57 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: DMARC Munging Date: Wed, 29 Jan 2020 16:53:45 -0800 Message-ID: <297c000a-9cfb-7ba9-8027-0cef21af18ff@msapiro.net> In-Reply-To: <0FC9CA07-2AA4-4AE1-B907-5759E2CB334E@rc.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3184963908520603845==" --===============3184963908520603845== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/29/20 4:39 PM, Allan Hansen wrote: >=20 > Is there a way for me to make this change to the From header munging until = it is implemented in the production version? I made MM2 do the munging using = such a change on your recommendation and it has worked. See --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============3184963908520603845==-- From ghalpern@shemesh.co.il Thu Jan 30 09:50:25 2020 From: Gila Halpern To: mailman-users@mailman3.org Subject: [MM3-users] SUBSCRIBE_FORM_SECRET in MM3? Date: Thu, 30 Jan 2020 09:50:23 +0000 Message-ID: <158037782339.9943.6914229941389133640@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5774457224501658502==" --===============5774457224501658502== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I've been looking into ways to prevent spam on my company's list, and one thi= ng I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configur= ation, which embeds a CSRF token into the form, and prevents it from being su= bmitted until five seconds after it renders, to keep bots from subscribing. = Unfortunately, the information I found pertained to Mailman 2. Does this opt= ion exist in MM3 as well, or is there a similar option? --===============5774457224501658502==-- From jeffrey@bit.nl Thu Jan 30 15:37:47 2020 From: Jeffrey D To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mass subscribe gives HTTP Error 500 when using custom template Date: Thu, 30 Jan 2020 15:37:45 +0000 Message-ID: <158039866504.9938.11789645149434363810@mailman.iad1.psf.io> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4699461618041080494==" --===============4699461618041080494== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Mark Sapiro wrote: > On 1/28/20 6:15 AM, Jeffrey D wrote: > > What is your setting in settings(_local).py for > POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > It should be the base URL for connecting to Postorius. I.e., if you > normally connect to Postorius via https://www.example.com/postorius, it > should be https://www.example.com Thanks, changing the POSTORIUS_TEMPLATE_BASE_URL fixing the issue. --===============4699461618041080494==-- From mark@msapiro.net Thu Jan 30 17:01:28 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: SUBSCRIBE_FORM_SECRET in MM3? Date: Thu, 30 Jan 2020 09:01:18 -0800 Message-ID: In-Reply-To: <158037782339.9943.6914229941389133640@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8224737259940513282==" --===============8224737259940513282== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/30/20 1:50 AM, Gila Halpern wrote: > I've been looking into ways to prevent spam on my company's list, and one t= hing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman config= uration, which embeds a CSRF token into the form, and prevents it from being = submitted until five seconds after it renders, to keep bots from subscribing.= Unfortunately, the information I found pertained to Mailman 2. Does this o= ption exist in MM3 as well, or is there a similar option? This feature in MM 2.1 is not very effective. On mail.python.org, this=20 feature as well as reCAPTCHA is enabled (e.g.=20 ) and we still=20 get periodic attacks of robotic subscribes that get around these measures. To answer your question, no, this does not exist in Postorius which is=20 an entirely different, Django based web UI. Django may have some=20 protections built in; I'm not sure about that, but there's nothing in=20 Postorius itself like this MM 2.1 feature. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============8224737259940513282==-- From phils@caerllewys.net Thu Jan 30 17:08:55 2020 From: Phil Stracchino To: mailman-users@mailman3.org Subject: [MM3-users] Re: SUBSCRIBE_FORM_SECRET in MM3? Date: Thu, 30 Jan 2020 12:08:45 -0500 Message-ID: <5824f938-57c2-fa4d-b51d-c4e2e6bedd04@caerllewys.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9086999476412943900==" --===============9086999476412943900== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 2020-01-30 12:01, Mark Sapiro wrote: > On 1/30/20 1:50 AM, Gila Halpern wrote: >> I've been looking into ways to prevent spam on my company's list, and one = thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman confi= guration, which embeds a CSRF token into the form, and prevents it from being= submitted until five seconds after it renders, to keep bots from subscribing= . Unfortunately, the information I found pertained to Mailman 2. Does this = option exist in MM3 as well, or is there a similar option? >=20 >=20 > This feature in MM 2.1 is not very effective. On mail.python.org, this=20 > feature as well as reCAPTCHA is enabled (e.g.=20 > ) and we still=20 > get periodic attacks of robotic subscribes that get around these measures. Human verification vs. verification-defeating countermeasures is an ongoing arms race which, frankly, humans have been losing for a long time. I have more than once commented, not entirely joking, that we're reaching a point where *FAILURE* to complete the CAPTCHA is evidence that you're a human. We need to come up with a better verification paradigm than presenting increasingly difficult puzzles which AI agents are better overall at solving than humans are. --=20 Phil Stracchino Babylon Communications phils(a)caerllewys.net phil(a)co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 --===============9086999476412943900==-- From tom@gather.coop Thu Jan 30 17:30:36 2020 From: tom@gather.coop To: mailman-users@mailman3.org Subject: [MM3-users] Deliverability and Spam Filtering Date: Thu, 30 Jan 2020 16:44:58 +0000 Message-ID: <158040269864.9943.7182437994316453030@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1038294676957512224==" --===============1038294676957512224== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi folks! First time poster, long time Mailman user. I am setting up a new Mailman 3 instance, and am super excited about the REST= API. I plan to use it to enable tight integration with a separate web app th= at I maintain. As I am setting up the mail server, I am wondering about two related things: = deliverability (for outgoing mail) and spam filtering (for incoming mail). What solutions have folks used for these? I know it is generally common now t= o outsource this critical task to a cloud provider like Mailgun or etc. Have = folks needed this or is running ones own incoming and outgoing mail not a big= deal? So many horror stories out there... As far as Mailgun goes, I think it should be straightforward to configure it = for outgoing mail, but I'm not sure how I'd use it for incoming. Mailgun can = forward mail via HTTP or to another email address. Neither I think would work= out of the box. It would be great if there were a REST API endpoint for inco= ming mail, but I don't think such a thing exists, right? Perhaps I could add = one? Another thought I had was that I could write a simple HTTP server that receiv= es mail from Mailgun and forwards it to Mailman via LMTP. But it seems simple= r to go right to Mailman's core API given that one exist already. Or am I thinking about this all wrong? Are there other more suitable services= out there? I looked for cloud MTA providers but didn't turn up much except f= or in the large enterprise space, which I'm sure I can't afford. Thanks for any thoughts! --===============1038294676957512224==-- From agranzot@mailbox.org Thu Jan 30 17:31:06 2020 From: Alberto Granzotto To: mailman-users@mailman3.org Subject: [MM3-users] Cannot setup announce-only mailing list Date: Thu, 30 Jan 2020 14:42:17 +0100 Message-ID: <73f206dc-e22e-6124-692f-694778bd07bd@mailbox.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9167658151747600282==" --===============9167658151747600282== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Dear all, I don't understand how to set up an "announce only" mailing list using Postorius Version 1.2.4. What I do is the following: - Click on "Create New List" - From "List Style", select "Announce only mailing list style." - Fill all other fields in the form - Click "Create list" At this point people can subscribe to the newly created announce mailing list. If they add themselves they end up in "List Members", and if they email the announce mailing list, their email is relayed to all other members, just like a normal mailing list :/ Moreover, subscribers get this message, inviting them to post to the announce only mailing list: > Welcome to the "Test-announce" mailing list! > > To post to this list, send your email to: > > test-announce(a)lists.dist0rtion.com Of course, I want to keep this mailing list "read only" for members, and I want only selected people to post to that mailing list. Any idea on how to achieve that? Best, Alberto --===============9167658151747600282==-- From mark@msapiro.net Thu Jan 30 17:58:15 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Cannot setup announce-only mailing list Date: Thu, 30 Jan 2020 09:58:03 -0800 Message-ID: <4bf3e8b2-f439-ff08-3379-3133c321f5db@msapiro.net> In-Reply-To: <73f206dc-e22e-6124-692f-694778bd07bd@mailbox.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3261075669575648264==" --===============3261075669575648264== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > Of course, I want to keep this mailing list "read only" for members, and > I want only selected people to post to that mailing list. > > Any idea on how to achieve that? There is only one difference between the `Discussion` and `Announce` list styles, and that is for an `Announce` list, the `allow_list_posts` attribute is set to `False`. In turn, all that does is cause the List-Post: header to be set to NO rather than the list posting address. There is a discussion at of how to set up an announce list for Mailman 2.1. Most of this translates straightforwardly to Mailman 3, although not all the relevant settings are exposed in Postorius. In short, you need to set this up manually using things like moderation settings and custom templates for the welcome message. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============3261075669575648264==-- From maxking@asynchronous.in Thu Jan 30 21:06:48 2020 From: Abhilash Raj To: mailman-users@mailman3.org Subject: [MM3-users] Re: Deliverability and Spam Filtering Date: Thu, 30 Jan 2020 13:06:22 -0800 Message-ID: In-Reply-To: <158040269864.9943.7182437994316453030@mailman.iad1.psf.io> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8416712949671389773==" --===============8416712949671389773== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On Thu, Jan 30, 2020, at 8:44 AM, tom(a)gather.coop wrote: > Hi folks! First time poster, long time Mailman user. > > I am setting up a new Mailman 3 instance, and am super excited about > the REST API. I plan to use it to enable tight integration with a > separate web app that I maintain. > > As I am setting up the mail server, I am wondering about two related > things: deliverability (for outgoing mail) and spam filtering (for > incoming mail). > > What solutions have folks used for these? I know it is generally common > now to outsource this critical task to a cloud provider like Mailgun or > etc. Have folks needed this or is running ones own incoming and > outgoing mail not a big deal? So many horror stories out there... > > As far as Mailgun goes, I think it should be straightforward to > configure it for outgoing mail, but I'm not sure how I'd use it for > incoming. Mailgun can forward mail via HTTP or to another email > address. Neither I think would work out of the box. It would be great > if there were a REST API endpoint for incoming mail, but I don't think > such a thing exists, right? Perhaps I could add one? There does exist a way to insert messages into Mailman via REST API, if you want to do that. It is done via Queue API, which exposes the internal store where messages sit after they are received from LMTP before they are processed. You can just inject the message in "IN" queue and it should be processed like a regular incoming message. https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/queues.html Although, it seems to only accept string representation of Email, which may not be ideal for your use case. It might be some work to make it work for raw bytes. > > Another thought I had was that I could write a simple HTTP server that > receives mail from Mailgun and forwards it to Mailman via LMTP. But it > seems simpler to go right to Mailman's core API given that one exist > already. > > Or am I thinking about this all wrong? Are there other more suitable > services out there? I looked for cloud MTA providers but didn't turn up > much except for in the large enterprise space, which I'm sure I can't > afford. > > Thanks for any thoughts! > _______________________________________________ > 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) --===============8416712949671389773==-- From tom@gather.coop Thu Jan 30 21:58:35 2020 From: "Tom @ Gather" To: mailman-users@mailman3.org Subject: [MM3-users] Re: Deliverability and Spam Filtering Date: Thu, 30 Jan 2020 16:58:25 -0500 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6573782830178636897==" --===============6573782830178636897== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Interesting! Does the `in` queue also work for emails to subaddresses like foo-owner, etc? Or is it only for list posts? Relatedly, why is `list_id` a required parameter? Isn't that information contained in the email? Struggling to understand this fully... Thanks for the help. On Thu, Jan 30, 2020 at 4:06 PM Abhilash Raj wrote: > On Thu, Jan 30, 2020, at 8:44 AM, tom(a)gather.coop wrote: > > Hi folks! First time poster, long time Mailman user. > > > > I am setting up a new Mailman 3 instance, and am super excited about > > the REST API. I plan to use it to enable tight integration with a > > separate web app that I maintain. > > > > As I am setting up the mail server, I am wondering about two related > > things: deliverability (for outgoing mail) and spam filtering (for > > incoming mail). > > > > What solutions have folks used for these? I know it is generally common > > now to outsource this critical task to a cloud provider like Mailgun or > > etc. Have folks needed this or is running ones own incoming and > > outgoing mail not a big deal? So many horror stories out there... > > > > As far as Mailgun goes, I think it should be straightforward to > > configure it for outgoing mail, but I'm not sure how I'd use it for > > incoming. Mailgun can forward mail via HTTP or to another email > > address. Neither I think would work out of the box. It would be great > > if there were a REST API endpoint for incoming mail, but I don't think > > such a thing exists, right? Perhaps I could add one? > > There does exist a way to insert messages into Mailman via REST API, if > you want to do that. It is done via Queue API, which exposes the internal > store where messages sit after they are received from LMTP before they are > processed. > > You can just inject the message in "IN" queue and it should be processed > like a regular incoming message. > > > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/queues.html > > Although, it seems to only accept string representation of Email, which > may not be ideal for your use case. It might be some work to make it work > for raw bytes. > > > > > Another thought I had was that I could write a simple HTTP server that > > receives mail from Mailgun and forwards it to Mailman via LMTP. But it > > seems simpler to go right to Mailman's core API given that one exist > > already. > > > > Or am I thinking about this all wrong? Are there other more suitable > > services out there? I looked for cloud MTA providers but didn't turn up > > much except for in the large enterprise space, which I'm sure I can't > > afford. > > > > Thanks for any thoughts! > > _______________________________________________ > > 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) > --===============6573782830178636897==-- From mark@msapiro.net Thu Jan 30 22:40:58 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Deliverability and Spam Filtering Date: Thu, 30 Jan 2020 14:40:49 -0800 Message-ID: <63fbcedf-3335-e6e9-c3f1-acd67c42ea42@msapiro.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2931952862842685651==" --===============2931952862842685651== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 1/30/20 1:58 PM, Tom @ Gather wrote: > Interesting! Does the `in` queue also work for emails to subaddresses like > foo-owner, etc? Or is it only for list posts? -bounces goes to bounces -confirm, -join, -leave (and their synonyms -subscribe and -unsubscribe) and -request go to command -owner goes to in. But there's more to it that that. There's also things put in the metadata in the queue entry such as mail to -owner sets to_owner = True > Relatedly, why is `list_id` a required parameter? Isn't that information > contained in the email? Possibly not. The recipient list is the envelope recipient which may or may not be in the message headers - it could be a Bcc to the list. Thus, listid needs to be set in the metadata as well. You need to look at mailman/runners/lmtp.py and emulate what it does. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============2931952862842685651==-- From mark@msapiro.net Fri Jan 31 04:34:49 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman3 on Debian 10 Date: Thu, 30 Jan 2020 20:34:41 -0800 Message-ID: <78b048b9-84e0-9593-0d42-f06bfb1a5f00@msapiro.net> In-Reply-To: =?utf-8?q?=3CLO2P265MB0704685ED676781A0D0AB2D198040=40LO2P265MB?= =?utf-8?q?0704=2EGBRP265=2EPROD=2EOUTLOOK=2ECOM=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2493031551828688601==" --===============2493031551828688601== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/30/20 9:22 AM, Bala Mutyam wrote: > Sorry one more issue, >=20 > Mailman settings page giving me below error. >=20 > Server error > An error occurred while processing your request. >=20 > Error logs: >=20 > ERROR 2020-01-30 17:20:11,331 16285 django.request Internal Server Error: /= postorius/accounts/subscriptions/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py",= line 41, in inner > response =3D get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line= 187, in _get_response > response =3D self.process_exception_by_middleware(e, request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line= 185, in _get_response > response =3D wrapped_callback(request, *callback_args, **callback_kwar= gs) > File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py",= line 23, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/postorius/views/user.py", line 306,= in user_subscriptions > mm_user =3D MailmanUser.objects.get_or_create_from_django(request.user) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 164, in = get_or_create_from_django > return self.get(address=3Duser.email) > File "/usr/lib/python3/dist-packages/postorius/models.py", line 86, in g= et > return method(*args, **kwargs) > File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 322,= in get_user > return User(self._connection, content['self_link'], content) > KeyError: 'self_link' Just prior to this is a call to the REST API to GET=20 /users/user(a)example.com (or whatever the user's address is). It appears=20 that that user doesn't exist in core. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============2493031551828688601==-- From mark@msapiro.net Fri Jan 31 04:36:31 2020 From: Mark Sapiro To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman3 on Debian 10 Date: Thu, 30 Jan 2020 20:36:20 -0800 Message-ID: In-Reply-To: =?utf-8?q?=3CLO2P265MB0704149BB8ECAAE43DF1CB7498040=40LO2P265MB?= =?utf-8?q?0704=2EGBRP265=2EPROD=2EOUTLOOK=2ECOM=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2202103783762052720==" --===============2202103783762052720== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 1/30/20 8:24 AM, Bala Mutyam wrote: > Hi Mark, >=20 > Thanks for the update and I managed to resolve the errors on the UI. >=20 > I have 2 more questions about the mailman3. >=20 > 1) how to create Mailing Lists? You can create lists with the `mailman create` command lint tool or via=20 Postorius as a superuser. > 2) super user login is not working even with correct login credentials and = giving me - The username and/or password you specified are not correct. How did you create the super user? You should do it with the django=20 admin createsuperuser command. > 3) Password Reset Email urls and email confirmation web pages giving me - T= his site can't be reached error. If this is an error from your browser, there is something wrong with the=20 host portion of the URL. --=20 Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan --===============2202103783762052720==--