Mailman 3 November 2016 - Mailman-Developers

Mailman Sprint happening NOW at PyCon 2016 Canada
by Stephen J. Turnbull Nov. 17, 2016

Nov. 17, 2016

Just to let you know. Also, I've done a little tracker curation (specifically HyperKitty), mostly tagging -- probably you should assume nothing important is happening if you get notices. Steve

5 9

Re: [Mailman-Developers] Attachment in mail
by Mark Sapiro Nov. 16, 2016

Nov. 16, 2016

On 11/15/2016 01:17 PM, Leon wrote: > Hi developers. I was wondering if mailman can block attachments in mails. > Mails sent out by mailman may have various attachments eg. logo in mail > template. I know mailman can block mails with attachments, but that is not > what we want. We hope to send out mails without attachments. This post really belongs on Mailman-users <https://mail.python.org/mailman/listinfo/mailman-users>. Please address any follow-ups to that list. Check out the Content filtering section in the web list admin UI. If you have further questions about this, please join the Mailman-users list at <https://mail.python.org/mailman/listinfo/mailman-users> and post them there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 1

Attachment in mail
by Leon Nov. 15, 2016

Nov. 15, 2016

Hi developers. I was wondering if mailman can block attachments in mails. Mails sent out by mailman may have various attachments eg. logo in mail template. I know mailman can block mails with attachments, but that is not what we want. We hope to send out mails without attachments. -- Best wishes, Leon

1 0

Adding gitlab group members and permissions
by Stephen J. Turnbull Nov. 14, 2016

Nov. 14, 2016

I added a new group member (mdupuis) with Reporter permission, and upgraded existing members (adammendoza, aniketshukla, khushbuparakh) to "Reporter". Dunno what policy is but Reporter looks pretty harmless, and Guest is pretty crippled (can't even set tags). WDOT? Steve

1 0

Adding gitlab group members and permissions
by Stephen J. Turnbull Nov. 14, 2016

Nov. 14, 2016

I added a new group member (mdupuis) with Reporter permission, and upgraded existing members (adammendoza, aniketshukla, khushbuparakh) to "Reporter". Dunno what policy is but Reporter looks pretty harmless, and Guest is pretty crippled (can't even set tags). WDOT? Steve

3 2

Re: [Mailman-Developers] MM3 DMARC mitigations
by Mark Sapiro Nov. 8, 2016

Nov. 8, 2016

On 10/31/2016 03:08 PM, Eric Searcy wrote: > > That reminds me. I have a proposed idea for another nice-to-have, that > I'm mentioning now in case it has any impact on the architecture you are > describing. Some email systems (e.g. Exchange) do not accept any > inbound email crossing their edge that uses their own From domain. It's > like a tiny microcosm of DMARC but only for their domain, and there is > no way for the outside world to know about their policy. However, when > a member of the community says they get all list messages *except those > from their colleagues*, it's clear they have this kind of setup. It > would be great to have a customizable-by-sender-domain munge-or-wrap > filter that let me add other domains to get the same treatment as > domains that don't publish DMARC -- even if not needed for general > receipt of their messages, so that emails to others at the same domain > on the list can be received. (This functionality doesn't exist in mm2 > either.) Adding Mailman-Developers to the recipients. As I noted in the original thread, this would not be difficult to add, but it won't be in the initial implementation of DMARC mitigations for MM 3 (see <https://gitlab.com/mailman/mailman/merge_requests/215> for more on that). However, I've just become aware that Microsoft has implemented another "feature". So far, the info I have is this is limited to their "hosted mail services", but it may well spread. What they are doing is looking at incoming mail for signs of spoofing/phishing and if found, they place a prominent notice This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing> in the message. The issue for us is that one of the tests is the To: and From: addresses are the same. That means that any message To: a list with DMARC mitigations applied will be sent From: the list and any recipients using these Microsoft services will see that warning in the list message[1]. How long will it be before this spreads to all Microsoft email services <sigh>? [1] I first became aware of this via the thread at <http://lists.mailscanner.info/pipermail/mailscanner/2016-November/104001.ht…>. There it was the poster who saw the warning in his copy of the list message and mistakenly thought it was a rejection of his post to the list. The reply at <http://lists.mailscanner.info/pipermail/mailscanner/2016-November/104017.ht…> has interesting info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 5

Camera-ready option to mitigate DMARC issues
by Alessandro Vesely Nov. 6, 2016

Nov. 6, 2016

Dear all, I'd like to probe the feasibility of this option. The idea is to add a footer only in case it is not present, similar to what is done with subject_prefix. By properly setting both of them, a sender can submit what can be called a camera-ready post. Since no change applies, no DKIM signature breaks. Hence, dmarc_moderation_action is not needed for such posts. It is not even necessary to check author's domain policy. I'm not familiar with Mailman administration, so I ask your opinion. How long would it take to code this option? How useful would it be? Camera-ready posts would be created by hands, by cleverly configuring some email client, or by using purposely written add-ons. They could also be done by MSAs who care about the damage they cause by publishing p=reject --the process can certainly be standardized and automated. TIA for any reply, and thanks for a great product Ale

3 6

Re: [Mailman-Developers] Problems signing up for the new tox-dev mailing list.
by Mark Sapiro Nov. 4, 2016

Nov. 4, 2016

Resending with correct mailman-developers(a)python.org addressee. On 11/4/16 6:37 AM, Laura Creighton wrote: > > I subscribed, which required registering to HyperKitty. This worked fine. > Subscribing was odd. I had to click on the 'Hide inactive' checkbox to find > the list. Apparently I am the first person to try to subscribe to this list > as there were 0 participants and 0 discussions. But I think it would be > better if spanking new lists were not classified as inactive, for the > benefit of extremely naive users. So a little bad. HyperKitty is the archiver. The list was inactive from HyperKitty's point of view because there were no recent posts (no posts at all) in the archive. Had you gone to Postorius (the web list management UI) at <https://mail.python.org/mm3/mailman3/lists/>, you would have seen the list. It appears that the issue is that the sign-up process, once completed redirects you to HyperKitty at <https://mail.python.org/mm3/archives/> rather than back to Postorius at <https://mail.python.org/mm3/mailman3/lists/>. You can get back to Postorius from HyperKitty by clicking "Manage lists" at the top right. I agree this is confusing. You may wish to file an issue with HyperKitty about this at <https://gitlab.com/mailman/hyperkitty/issues>. > The very bad news was when I tried to edit my options for this list. > I got: > https://mail.python.org/mm3/mailman3/accounts/list-options/tox-dev.python.o… > Server Error (500) Thanks very much for the report. I'll investigate and report back. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 1

Silly usability problem in mailman3.
by Laura Creighton Nov. 4, 2016

Nov. 4, 2016

I wanted to subscribe to the spanking-new mailing list, tox-dev. In order to get to do this, I had to uncheck the checkbox on the top 'Hide inactive' Apparently I was the first person to subscribe to the list, as there were 0 subscribers and 0 discussions. Whatever algorithm is being used to determine if a list is inactive or not should be tweaked to understand that absolutely spanking-new mailing lists -- which mailman3 already knows how to recognise -- are not considered inactive. Thank you. Laura

2 1