- Mailman-users - lists.mailman3.org

Hyperkitty Archives Empty
by jon.kokko＠us.fujitsu.com 02 May '18

02 May '18

I've installed the mailman bundle located here (https://github.com/iomarmochtar/mailman3_ei) and, minus a pip package or two, it was straightforward. Mail & list functionality appears to be working well but I have no archives/thread discussions after posting messages. Delivery, etc.. is all good. Can you offer some suggestions on how to debug the archiving piece? Thanks, ./JK

3 2

Domain admin
by Johannes Winter 29 Apr '18

29 Apr '18

Hello everybody, We would like to give our users the priviledge to create lists per domain. I Haven't found any options for that in the web interface. Is this possible somehow with mailman3? Best regards, Johannes

2 2

Rejecting held emails
by Darren Smith 26 Apr '18

26 Apr '18

Hello, We recently had a phishing message make it through our spam filters and arrive at a mailing list. The good news is that since it was not from a list member it was in the held message queue. I was able to find the message in the var/messages directory by searching for a keyword in the subject. However, after rejecting the message from Postorius, the message doesn't seem to be removed from the var/messages directory. Is this expected behavior? I know that infosec people won't be too happy about a phishing email sitting around on our disk. (Infosec guys are notoriously paranoid. :) ) Is there some sort of cleanup process that would remove these messages? If not, does this pose an issue where over time disk usage will creep up? This could be a pretty significant problem if that is the case. What do you think, sirs? -Darren

2 2

Disabling Gravatar
by Marvin Gülker 26 Apr '18

26 Apr '18

Hi everyone, I want to make you aware of a potential privacy problem in Mailman's Hyperkitty. Under the upcoming EU General Data Protection Regulation (GDPR)[1], which will be in force as of 2018-05-25, it is illegal to transmit data to third parties without a right to do so. Without going into the details, the inclusion of third party services into one's website is usually deemed such a transmission, and unless one has explicit consent of the user (e.g., by an optional (!), unticked ticking box) this is normally illegal (if one targets EU users). The GDPR does not affect private and family use (Art. 2(2)(c) GDPR), but the exact reach of that clause is yet to be determined; it certainly does not exclude company use of Mailman. I've found it's possible to disable the social login providers quite easily (we had this discussion here on the mailinglist recently), but I don't see an option to disable Gravatar. If there is one, please enlighten me, but anyway I want to propose this as a feature request against Hyperkitty. A GDPR-compliant implementation of Gravatar in Mailman would look like this: * In order to not transmit website visitor's data (IP address, browser info, etc) to Gravatar, Hyperkitty has to request the avatar image itself and not leave that to the user's browsers to do. In other words, the HTTP GET request needs to come from the server running Hyperkitty and the user's browser then just requests the avatar from the Hyperkitty server. Most likely easiest way to do this is to pre-download the avatar when an email is archived. * In order to not transmit the subscribers' data (email address, allows Gravatar to track the subscriber) to Gravatar illegally, the retrieval of the avatar image from Gravatar has to be disabled by default. Instead, an option needs to be added to the subscriber's control panel which he has to actively enable in order to have his Gravatar downloaded and thus used (privacy-by-default rule). I'm not saying Gravatar tracks people and sells the information gathered, though I have doubts on how Automattic makes money with the service. I'm just outlining the legal duties under the upcoming GDPR for service owners, which are independant of how Automattic processes the data in this specific case. Please don't dismiss this as some side feature not needed. The fines that can be imposed on service owners due to violation of the GDPR are very high (up to 20,000,000 € [that's 20 million euros, really]). Marvin [1]: http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1510481733260&uri=CELEX:… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

5 5

Mailman not able to process "big" requests
by Jonas Felber 24 Apr '18

24 Apr '18

Hi, We migrated from mailman2 to mailman3 a week ago. Since then we are unable to send messages the our students through the mailing list. Here are some symptoms: 1. I go to mass subscribe and subscribe 400 emails 2. I click subscribe, the browser (in my case safari) tries to load the page for a few seconds 3. The request times out 4. Once the service becomes responsible again, I see that only part of my emails got subscribed (~50 in this case). For me this really looks like the emails are sent on the "web-thread" that gets killed once the request times out. Looking at this https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p… <https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p…> seems to confirm my suspicions. Some quick overview of our infrastructure: The TCP endpoints are: browser -> haproxy in kubernetes-entry-router -> nginx in kubernetes-ingress -> nginx in mailman -> mailman We mitigated the issue by giving it more CPU power and increasing the timeouts in one of the nginx endpoints. We also have a problem with sending out emails to "large" (>50) groups, as they seem to not getting sent out at all. Do you have any idea what the problem here could be? We would be really glad if you can help us getting our mailman up and running, as I currently have to send emails out by "hand". I will happily provide you with more details about our configuration, just let me know what you need. Kind regards, Jonas Jonas Felber <jonas.felber(a)vis.ethz.ch <mailto:jonas.felber@vis.ethz.ch>> Aktuar & CTF Präsident VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch <https://www.vis.ethz.ch/>

4 4

Another interesting error...
by Darren Smith 24 Apr '18

24 Apr '18

So it appears that there was a message sent to one of our mailing lists that was put into the held message queue. However, when attempting to go to the message to do the moderation, the web page returns and Error 500. Looking in the mailman log, I found this: Apr 23 14:21:02 2018 (17878) REST request handler error: Traceback (most recent call last): File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/transac tion.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/wsgiapp.py" , line 214, in __call__ return super().__call__(environ, start_response) File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", line 227 , in __call__ responder(req, resp, **params) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera tion.py", line 167, in on_get resource = self._make_collection(request) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/helpers.py" , line 159, in _make_collection for resource in collection] File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/helpers.py" , line 159, in <listcomp> for resource in collection] File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera tion.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera tion.py", line 100, in _make_resource make_header(decode_header(resource['subject']))) File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, in make_he ader h.append(s, charset) File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, in append s = s.decode(input_charset, errors) UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: illegal multibyte sequence It LOOKS as if there might be a character in the email somewhere - possibly in the subject or sender fields? - that is somehow unexpected. I am attempting to find the held message - can someone point me where I can go to see the message so that I can see what might be causing the problem? -Darren

4 11

sass error
by Alexander Klotz 20 Apr '18

20 Apr '18

Hi everybody, we tried to make a fresh installation out of the current version following the readme.md - we encounter the following error trying to do so. As mentioned elsewhere, 'sass' has been replaced by 'sassc', however, maybe somewhere there is still a reference to it that may have been overlooked? The answer to a similar error posted to this list in August 2017 unfortunately didn't help either. Any help would be appreciated! Thanks, Alex ERROR 2018-04-19 09:07:49,096 29 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 217, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 215, in _get_response response = response.render() File "/usr/local/lib/python2.7/site-packages/django/template/response.py", line 107, in render self.content = self.rendered_content File "/usr/local/lib/python2.7/site-packages/django/template/response.py", line 84, in rendered_content content = template.render(context, self._request) File "/usr/local/lib/python2.7/site-packages/django/template/backends/django.py", line 66, in render return self.template.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 207, in render return self._render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/site-packages/compressor/templatetags/compress.py", line 131, in render return self.render_compressed(context, self.kind, self.mode, forced=forced) File "/usr/local/lib/python2.7/site-packages/compressor/templatetags/compress.py", line 107, in render_compressed rendered_output = compressor.output(mode, forced=forced) File "/usr/local/lib/python2.7/site-packages/compressor/css.py", line 49, in output ret.append(subnode.output(*args, **kwargs)) File "/usr/local/lib/python2.7/site-packages/compressor/css.py", line 51, in output return super(CssCompressor, self).output(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/compressor/base.py", line 295, in output output = '\n'.join(self.filter_input(forced)) File "/usr/local/lib/python2.7/site-packages/compressor/base.py", line 235, in filter_input for hunk in self.hunks(forced): File "/usr/local/lib/python2.7/site-packages/compressor/base.py", line 205, in hunks precompiled, value = self.precompile(value, **options) File "/usr/local/lib/python2.7/site-packages/compressor/base.py", line 268, in precompile return True, filter.input(**kwargs) File "/usr/local/lib/python2.7/site-packages/compressor/filters/base.py", line 229, in input return super(CachedCompilerFilter, self).input(**kwargs) File "/usr/local/lib/python2.7/site-packages/compressor/filters/base.py", line 196, in input raise FilterError(err) FilterError: /bin/sh: sass: not found

2 2

Re: Question regarding serve_from_domain
by Alexander Klotz 20 Apr '18

20 Apr '18

Hi Steve, thanks for your answer - we've made a completely new installation and don't encounter this specific error anymore, so we won't need an answer for that at the moment. Best, Alex Am 20.04.18 um 09:47 schrieb Stephen J. Turnbull: > Did you ever get an answer to this? I will have some time to look > into it over the weekend (I've been away from coding in core dev for a > while, so no answer offhand), but I'd like to know if you still need > an answer before spending time on it. :-) > > Steve > > Alexander Klotz writes: > > Hello, > > > > we're currently unsure in which file the serve_from_domain-entry > > described in the readme.md regarding mailman-web. We just updated the > > docker and encounter the following error, which might correspond to the > > missing entry: > > > > OSError: [Errno 13] Permission denied: '/opt/mailman-web/fulltext_index' > > > > Any help would be appreciated - thanks! > > > > > > -- > > Regards, > > Alex Klotz > > > > (culturebase editorial staff) > -- Mit freundlichen Grüßen, Alexander Klotz (redaktion kulturserver) mailto:alexk@kulturserver.de Stiftung kulturserver.de gGmbH Lothringerstraße 23 D-52062 Aachen http://ggmbh.kulturserver.de Geschäftsführer: Wolfgang Knauff Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 Umsatzsteuer-Identifikations-Nr.:DE DE 230868040

1 0

Outgoing messages fro Mailman fails DMARC
by Henrik Rasmussen 19 Apr '18

19 Apr '18

I have set up Postfix to DKIM sign outgoing mails from GNU Mailman 3.2.0a1 which validates nicely ("dkim=pass (signature was verified)"), but DMARC fails ("dmarc=fail action=none") on the recipient end, probably because the "header.from=gmail.com;" (or similar) which means that DKIM d= will not match. According to dmarc.org*) "Mailing lists usually do not take authorship of the emails they relay" so I should "consider to apply specific rules for emails coming from mailing lists". Also according to dmarc.org*) Mailman (Mailman 2 that is, and I presume Mailman 3 does too) "include features to interoperate with DMARC senders". I assume that the dmarc mitigations list settings in Mailman is for incoming messages, but how do I set Mailman to cope with this on outgoing messages? Note: I have more than one list domain in Mailman 3. *) https://dmarc.org/wiki/FAQ#Is_there_special_handling_required_to_receive_DM… /Henrik

2 3

Upgrade
by Darren Smith 16 Apr '18

16 Apr '18

Hello all, I'm working on upgrading our mailman3 instance. The current running instance is 3.1.0, and I am attempting to move to 3.2.0a1. Partially because La Villa Strangiato is a better song than Between the Wheels, but mostly because we want some of the bug fixes, and we are nailing down our upgrade process for the future. Initially after updating when I ran the "mailman info" command, I got this: Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 7, in <module> from mailman.bin.mailman import main File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/bin/mailman.py", line 19, in <module> import click ModuleNotFoundError: No module named 'click' So I went and installed click - easy enough to do. But then I get this error: "Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 696, in main with self.make_context(prog_name, args, **extra) as ctx: File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 621, in make_context self.parse_args(ctx, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 1018, in parse_args rest = Command.parse_args(self, ctx, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 880, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 1404, in handle_parse_result self.callback, ctx, self, value) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 78, in invoke_param_callback return callback(ctx, param, value) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/bin/mailman.py", line 93, in initialize_config initialize(value) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/core/initialize.py", line 219, in initialize initialize_2(propagate_logs=propagate_logs) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/core/initialize.py", line 178, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/factory.py", line 54, in create database.initialize() File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/base.py", line 107, in initialize url, isolation_level='READ UNCOMMITTED', pool_pre_ping=True) File "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/engine/__init__.py", line 387, in create_engine return strategy.create(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components." Anyone able to point me where to go to look for a solution for this? We're running postgresql as the database, and psycopg2 has been installed. Thoughts? -Darren

2 7