Mailman 3 February 2015 - Mailman-Developers

fqdn_listname - is it strict in what type of input it accepts?
by Andrew Stuart 16 Feb '15

16 Feb '15

As I understand it, fqdn_listname is effectively the email address of a mailing list. i.e. testlist(a)example.org The RFC 2369 list-id is the same thing but with a dot instead of an @ symbol. i.e. testlist.example.org My question: is Mailman strict about accepting only email addresses in fqdn_listname fields? Or does it also accept RFC 2369 list-id in fqdn_listname fields? I’m trying to wrap my head around some inconsistencies where some methods that use fqdn_listname seem to accept list-id, bt I can’t see how it possible to determine domain from a list-id, so how is it possible to accept either in a fqdn_listname field? thanks as

2 1

Re: [Mailman-Developers] A couple of archiving questions
by Barry Warsaw 16 Feb '15

16 Feb '15

On Feb 16, 2015, at 05:01 AM, Pranjal Yadav wrote: >So it should be possible to choose one (or more) of them in postorius. In >/mailman/src/mailman/archiving/docs/common.rst ; It says we have Mail-Archive >and MHonArc archivers available however there are some issues with the >non-public lists. Note that MHonArc is typically a local archiver and I believe there are ways to make some of its archives private. Launchpad uses MHonArc internally and supports private lists with private archives, but it may be through some custom hacks (I don't remember). While the system itself must define the available archivers, each individual list can opt in or out of any that are enabled system-wide. Cheers, -Barry

1 0

Re: [Mailman-Developers] Building plug-ins for mailman.
by Aanand Shekhar Roy 16 Feb '15

16 Feb '15

---------------------------- Original Message ---------------------------- Subject: Re: [Mailman-Developers] Building plug-ins for mailman. From: "Aanand Shekhar Roy" <2013001(a)iiitdmj.ac.in> Date: Mon, February 16, 2015 9:32 am To: 2013165(a)iiitdmj.ac.in -------------------------------------------------------------------------- Hi everyone, > * Aanand Shekhar Roy <2013001(a)iiitdmj.ac.in>: >> Hi all, >> I am currently finding good plugin ideas that might make there way into >> mailman 3 system.I had discussed the same with @terri on irc.Some ideas >> i >> have already found good are: >> 1. DNS BlockList > > where would you put DNSBL support? > > On SMTP level? I'd let the MTA take care of it. > On HTTP level? I'd let the HTTP take care of it. > 1. I totally agree with you that DNSBL suits better in MTA, my interest on bulding it as a plugin is for the reason that a user might want to block a particular domain not because it is a spam but due to reasons better known and genuine to him or her.To let let them do that with ease without worrying about shell access and other complexities. > Sorry, if I sound harsh. I don't mean it. I just can't imagine where DNSBL > would make sense without reinventing something that has been done yet. > > >> 3. SpamAsassin as it is > > I'd leave that to an MTA too, unless there's a non-SMTP way how mail > enters > mailman. > > p@rick > Spamassasin is better placed in the MTA support and works quite more effieciently but again for the ease of acces for some list admins who want to keep there spam level threshold low or high according to their needs may find it difficult to regulate it without an easy available chunk in user interface.Also option for marking a domain spam (I am not sure but as far as my knowledge about it is ,it isn't there yet in mailman3) might be a good idea > 2. Confirmation from user before posting phone nos in email > -- > [*] sys4 AG > I am going through the archives of user-list to gain more insight on this topic.This one by far sounds the most interesting.Also,as suggested by Stephen J. Turnbull,i am thinking of extending it further to other confidential Thanks everyone for correcting me.I have also thought of a few more ideas, reading about them before discussing them here. Aiming towards more improvement in these ideas.. > https://sys4.de, +49 (89) 30 90 46 64 > FranziskanerstraÃe 15, 81669 MÃ¼nchen > > Sitz der Gesellschaft: MÃ¼nchen, Amtsgericht MÃ¼nchen: HRB 199263 > Vorstand: Patrick Ben Koetter, Marc Schiffbauer > Aufsichtsratsvorsitzender: Florian Kirstein > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > https://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: > http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: > https://mail.python.org/mailman/options/mailman-developers/2013001%40iiitdm… > > Security Policy: http://wiki.list.org/x/QIA9

1 0

Is there a way to get member id via REST API?
by Andrew Stuart 14 Feb '15

14 Feb '15

GET /addresses/{email}/memberships GET /members Both seem to return member id in self_link but I can’t see it elsewhere. Anywhere I can get member id without parsing it out of the self_link? Maybe I’m not looking in the right place. thanks as

2 2

Re: [Mailman-Developers] Support for X-No-Archive
by Stephen J. Turnbull 14 Feb '15

14 Feb '15

Jeff Breidenbach writes: > I checked Thank you! > and these two lists are responsible. One uses 'No' and the other > uses 'no' for every message. I can't speak to the intention. There > are an impressive number of headers on each message including DKIM > but I don't see a clue as to the list server software. I took a quick look at the archives for one of them. From the disclaimer in the footer it seems pretty clear that they intend to make all of those posts public, which isn't surprising given that they use your service. :-) However, since it's on all posts and they also add a disclaimer to each post, I conclude that it's something in their mailing list system (whether it's actually coded in the MTA or the MLM, who could guess). It's possible that their MLM suppresses "X-No-Archive: yes" posts, so they never reach mail-archive.com, but again, we'd have to ask them. More likely, they didn't catch the nuance that there's only one value for X-No-Archive, and that is "yes" -- otherwise don't insert the field at all. So I think we can conclude that (1) individuals who intentionally use "X-No-Archive: no" are *extremely* rare, and (2) the example of these lists doesn't provide any guidance to Mailman since Mailman provides no facility for generating X-No-Archive itself. Maybe it should? Ie, for lists with "private" archives, maybe it would be a good idea to add "X-No-Archive: yes" to the header to advise chained lists not to archive?

2 2

Question about member role and PATCH /members/{id}
by Andrew Stuart 13 Feb '15

13 Feb '15

When a user is subscribed to a list, they can be assigned a role, one of member, owner, moderator nonmember. The PATCH /members/{id} method does not allow changes to the role and display_name. I’m just wondering what the thinking is behind this - is there a reason that role cannot be changed? thanks

2 1

Adding CSS to mailman archives
by Andrew Daviel 13 Feb '15

13 Feb '15

A little while ago (November 2012 probably) I changed a mailing list from Hypermail to Mailman and wanted to keep some of the look-and-feel of the archives, e.g. background colour and fonts. So I patched mailman 2.1.9 in CentOS 5 to include a CSS stylesheet link in each generated HTML page, replacing e.g. <BODY BGCOLOR="#ffffff"> with just <body> and adding e.g. body {background-color: #ffffff ; color: black; } in /pipermail/mailman.css, so that HTML style such as FONT and SIZE is removed from the Python code. (I only have one list on that server and didn't implement per-list style) I also changed a few things e.g. content-type to get zero warnings and errors from the W3C online validator. Now if I want to get DMARC functionality I'll have to jump past the RedHat/CentOS release and build 2.1.18, and re-patch for CSS. I was wondering if there was any interest in incorporating CSS into the official releases. -- Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 (Pacific Time)

7 17

Date normalization - opinions sought
by Andrew Stuart 12 Feb '15

12 Feb '15

Does Mailman normalize dates on emails to UTC? It seems like a good idea to me to normalise dates on emails to UTC but you guys would know best. What would be the pros and cons of email date normalisation to UTC? Are there good reasons not to? Which date field on an email is even the right one to use? Sent date or received date? And WHICH received date , because there can be various dates can’t there? thanks as

3 2

Getting error with the tests mailman3 core
by Aanand Shekhar Roy 12 Feb '15

12 Feb '15

Hi, I am working on bug #967951.Following is the diff file for my changes. http://pastebin.com/x7LMiTCR I am getting the following error on running the tests. http://pastebin.com/NFU3Gbrc Can someone please help as i unable to understand why i am getting these errors! Any help would be appreciated

1 0

Help with the bug
by Aanand Shekhar Roy 12 Feb '15

12 Feb '15

Hi, I am working on bug #967951.Following is the diff file for my changes. http://pastebin.com/x7LMiTCR I am getting the following error on running the tests. http://pastebin.com/NFU3Gbrc Can someone please help as i unable to understand why i am getting these errors! Any help would be appreciated

1 0