Mailman 3 February 2015 - Mailman-Developers

Ideas for injecting test messages
by Andrew Stuart Feb. 25, 2015

Feb. 25, 2015

I want to inject some test messages into Mailman to test moderation functions via the REST API. Any ideas on a simple way to do that? Ideally I need to be able to clear them out somehow too. thanks as

3 3

Re: [Mailman-Developers] Approach for plugin ideas
by Aanand Shekhar Roy Feb. 25, 2015

Feb. 25, 2015

Hi Abhilash, Thanks for guiding me through. I'll work on the details as suggested by you. :) > Hi Aanand, > > On 23 February 2015 at 17:11, Aanand Shekhar Roy <2013001(a)iiitdmj.ac.in> > wrote: >> Hi everyone, >> >> This is my approach for plug-in ideas : >> >> BANNED WORDS: >> 1. We create a common set of words that are to be banned in a mail. > > How do you create such a list, who decides which words are banned? > Will this list be list specific or global to one mailman installation? > Would it be possible to add/remove words from these lists from postorius? > >> 2. In list settings we create an option for list admin to choose action >> taken if a mail has banned words. > > What according to you should be sane default for this? Is is possible that > the banned words be removed or replaced with ****** and the mail be sent > to > the list so as to ease the life of list-admins? > >> 3. We need to create a new rule in mailman/src/mailman/rules that checks >> for banned words in a msg string. > > When you mention url relative to a project, you don't need to add the name > of > the root directory. Like 'mailman/src/mailman/rules' should be > 'src/mailman/rules/'. > Also, include them inside quotes to differentiate it from normal text. > >> 4. This rule is to be implemented in >> mailman/src/mailman/chains/builtin.py >> where it takes the action as chosen by list admin and then the control >> is >> passed further depending on the action taken. >> >> CONFIDENTIAL INFORMATION CHECK: >> 1. We need to create another rule which check for confidential info. >> like >> phone no and address credit card no. using regexp search. > > How do you do that check? How can you differentiate any number from > phone number, > or credit card number? (Using reg-ex, yes, but what would the rules be?) > Why is address a confidential information and how do you actually decide > what > level of confidentiality you want to maintain? Will that be > configurable per-list or > globally in a mailman installation? > >> 2. If found we hold that message, and then we send an auto-reply to >> sender >> asking for confirmation if he >> intends to post such information. >> 3. This system works similar to the mail-back verification procedure >> during confirmation of email while subscribing where potential >> subscriber's reply decides the further action to be taken. > > How will you parse the response of the sender, will there be a > pre-defined format > like email commands in mailman? Will you provide option in postorius too > for the > same? If yes, how? > >> 4.Based on the user's response the held message will be processed >> further. > > Where will the message be stored while mailman waits for the reply > from the sender? > Will there be a timeout for response after which the email will > automatically be > rejected (or discarded? ) or will mailman wait forever for the > response? If you plan > to timeout what would be default value? > >> TIMED VACATION: >> In member's preference form we already have an option for enabling and >> disabling mail delivery. We can >> extend it to another option called "Vacation period" which takes the >> duration of vacation and disables receiving emails and >> automatically enables mails after the vacation period ends. > > This project is about *plugins* and not extending core to do such things. > Once it is decided what and how the filtering is to be done, its fairly > easy to > write a rule. What you need to figure out is how to actually add this as > an > optional plug-in to mailman. If you make the options configurable by > list-admin > you would need to add options in postorius as well, again as a plug-in. > > Have you read if mailman supports plug-ins at all right now? If yes, how? > If no, > how will you do that? You have suggested 4 ideas for plugins, but I > think it would > be better if you choose any two of them which you can best implement in > the time > frame given to you. In case you finish early, you can extend your > project and create > more plugins. > > I hope my questions help you figure out the minute details of your > project. > > thanks, > Abhilash >

1 0

Approach for plugin ideas
by Aanand Shekhar Roy Feb. 25, 2015

Feb. 25, 2015

Hi everyone, This is my approach for plug-in ideas : BANNED WORDS: 1. We create a common set of words that are to be banned in a mail. 2. In list settings we create an option for list admin to choose action taken if a mail has banned words. 3. We need to create a new rule in mailman/src/mailman/rules that checks for banned words in a msg string. 4. This rule is to be implemented in mailman/src/mailman/chains/builtin.py where it takes the action as chosen by list admin and then the control is passed further depending on the action taken. CONFIDENTIAL INFORMATION CHECK: 1. We need to create another rule which check for confidential info. like phone no and address credit card no. using regexp search. 2. If found we hold that message, and then we send an auto-reply to sender asking for confirmation if he intends to post such information. 3. This system works similar to the mail-back verification procedure during confirmation of email while subscribing where potential subscriber's reply decides the further action to be taken. 4.Based on the user's response the held message will be processed further. TIMED VACATION: In member's preference form we already have an option for enabling and disabling mail delivery. We can extend it to another option called "Vacation period" which takes the duration of vacation and disables receiving emails and automatically enables mails after the vacation period ends. AUTO-MODERATION SYSTEM FOR LIMITING POST: I want your suggestions on how to approach this issue. Also,I wish to seek your views on these approaches.

2 1

/3.0/addresses/cris@example.com/user' - multi purpose REST API method
by Andrew Stuart Feb. 24, 2015

Feb. 24, 2015

TLDR - This API methods does multiple things and depends on information apart from the URL to define its behaviour mode, making it hard to give a clear authentication scope to. I wonder if it should be broken out into individual REST API methods, each with a single purpose and a clear authentication scope. As background information, from the documentation: “”"To link an address to a user, a POST request can be sent to the ``/user`` sub-resource of the address. If the user does not exist, it will be created.””" >>> dump_json('http://localhost:9001/3.0/addresses/cris@example.com/user', ... {'display_name': 'Cris X. Person’}) My question is - I am interested to understand the thinking behind this REST method. It is effectively a multi purpose method. In one case it *creates an email address* and *creates a new user* and which are linked to each other. In one case it *creates an email address* and links that address to an existing user, when given a POSTed user_id. In one case it *creates an email address* and does not link it to any user, if the auto_create POST option is False. In terms of building an authentication system this REST method is problematic. All (I think at this stage anyway) other methods in the REST API can be given a clear authentication scope/role based only on the URL. This REST API method, dual to its multi purpose, mode options-in-the-POST-data behaviour, cannot be given an authentication scope based only on the URL. Each of the above behaviours have a different authentication scope/role. For example: (permitted by superuser only) In one case it *creates an email address* and *creates a new user* and which are linked to each other. (permitted by superuser only, permitted by existing user) In one case it *creates an email address* and links that address to an existing user, when given a POSTed user_id. (permitted by superuser only) In one case it *creates an email address* and does not link it to any user, if the auto_create POST option is False. I’m interested to hear thoughts on this. It would be good if the authentication scope of every REST API URL could be defined based only on the URL, without the need to know either options provided in the form data, or whether or not other records such as user records exist. In summary - This API methods does too many things and depends on information apart from the URL to define its behaviour, making it hard to give a clear authentication scope to. I wonder if it should be broken out into individual REST API methods, each with a single purpose and a clear authentication scope.

2 4

Is there a direct way to create an address via the REST API?
by Andrew Stuart Feb. 24, 2015

Feb. 24, 2015

I can create an address that is not linked to a user by 1: creating a user with an address 2: unlinking the address from the user Is there a more direct route to creating an address via REST? I thought there was a POST /addresses method but I can’t seem to see it now - maybe it was never there. thanks as

1 1

MIME footers
by Murray S. Kucherawy Feb. 24, 2015

Feb. 24, 2015

Hi there, A while back I introduced an experimental draft about DKIM signature generation that's sensitive to MIME structure. I'm planning to revisit and maybe even implement this to get some experimentation going. It would help guide the design work if I knew this: How does, or how would, Mailman add a footer to a MIME message? My guess is that it would make a multipart that contains the original message (message/rfc822) as one part and the footer as a text/plain in a second part, but that's purely a guess. Equally important: What would it do to sign a message that's not MIME to begin with? Could it be compelled to turn it into a MIME message, perhaps treating the original as a single-part text/plain message and doing the same wrapping I described? Thanks, -MSK

1 0

Redesign of List.org
by Athyuttam Reddy Feb. 23, 2015

Feb. 23, 2015

Hello all, I’m a student of computer science and design at Brown University. Having recently worked with Mailman setup, I’ve also been following the developer conversations. I notice that on the to-do list, one of the entries is: "Update visual style and information architecture of list.org and the wiki to feel more unified, be more navigable, and present a modern appearance” How can I contribute to the redesign? I’d love to work alongside anyone already taking the lead on this, and put my branding + UI/UX experience to use. Sorry if this wasn’t the best way to post this request, but thanks very much in advance. Best, Atty Eleti

2 1

Re: [Mailman-Developers] [GSoC14] Full Anonymization Project Idea
by Rashi Karanpuria Feb. 22, 2015

Feb. 22, 2015

I totally understand that claiming to provide total privacy to any individual could be vague and debatable in this case. And if we apply the usual encryption it becomes very easy to hack. So using normal cryptography is ruled out. But if we could implement salting. We generate a salt when a user is joins this list. It is stored in the database with the individual's password and other details (assuming the SQL database used is secure and does not give access rights to the moderator or any one else). When user sends a mail we store the salt used and fake mail id generated in another database (follows the previous assumptions). In case of reply to same address we lookup the fake mail id and corresponding salt and regenerate the address simultaneously applying the process of fake mail id generation to the sender's mail id this time. Also we need to filter the header from all the possible traces. But then it depends on the accessibility of the database in question. Also if we need to implement these processes someplace that is secure from middle men or malware (server may be). Or may be I guess the only way around is to trust the list admin but then it won't be able to serve the needs when we wish to keep this thing out of the hands of the admin. It then only keeps users anonymous from each other while the admin knows everything. If I am still thinking it all the wrong way. Please guide me as to how do I approach the problem.

3 2

Re: [Mailman-Developers] Prospective applicant for GSoC-2015
by Aanand Shekhar Roy Feb. 22, 2015

Feb. 22, 2015

Hi, Welcome! You may start off by setting up your development environment. You may refer to http://wiki.list.org/DEV/A%205%20minute%20guide%20to%20get%20the%20Mailman%… .If you run into any problem, you can also contact on IRC channel #mailman. :) > Hello! > My name is Aditya, studying Computer Science at Bangalore. I am currently > in the third year and have good experience with Python. > How may I start contributing to mailman? > > Regards, > > -- > Aditya Dalwani > P.E.S Institute of Technology, > Bangalore, India > _______________________________________________ > 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

Re: [Mailman-Developers] Prospective applicant for GSoC-2015
by Pranjal Yadav Feb. 21, 2015

Feb. 21, 2015

Hello Aditya I would suggest mailman wiki and setting up mailman would be a good start and from there your can to jump beginner friendly bugs. http://wiki.list.org/DEV/A%205%20minute%20guide%20to%20get%20the%20Mailman%… https://pythonhosted.org/mailman/src/mailman/docs/START.html Above 2 links will give you a good start, also you can join mailman on IRC. For GSoC 2015 go through http://wiki.list.org/DEV/Google_Summer_of_Code_2015 and try to select and understand any one of the projects ( you can of course come up with your own ideas and projects however you can trust me that mailman admins design these projects very carefully and practically as well as they are aligned with mailman milestones, so your own idea might need a evaluation before proceeding) On Sat, Feb 21, 2015 at 4:55 PM, Aditya Dalwani <adit.39(a)gmail.com> wrote: > Hello! > My name is Aditya, studying Computer Science at Bangalore. I am currently > in the third year and have good experience with Python. > How may I start contributing to mailman? > > Regards, > > -- > Aditya Dalwani > P.E.S Institute of Technology, > Bangalore, India > _______________________________________________ > 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/godricglow%40gma… > > Security Policy: http://wiki.list.org/x/QIA9 > -- *Pranjal Yadav* *IIT Kharagpur*

1 0

Introduction and Issues with the mailman interface.
by Acho Arnold Feb. 21, 2015

Feb. 21, 2015

Good day comrades. My name is Acho Arnold and I am a junior full stack web developer and I would like to contribute to this project. I have been using mailman for a long time now and I've always wondered why the interface looked **poor** in my opinion. The UI is composed of mainly text and it looks dirty to me. I would like to know if you guys (developers) also share my pain or if there is a specific reason why the UI hasn't been cleaned up? I talked with the developers on the Freenode irc channel and i leaned that there is a plan for the UI improvements. I would like to contribute in making this change. Please can someone give me an update on the status of the UI improvements? PS: Is there anyone here from Cameroon or Africa? Thanks -- Acho Arnold Ewin <http://goo.gl/2hwP4m> Telephone: (+237) 695 233 475 Buea, Cameroon arnold(a)archlinux.info <mailto:arnold@archlinux.info>

2 1

Prospective applicant for GSoC-2015
by Aditya Dalwani Feb. 21, 2015

Feb. 21, 2015

Hello! My name is Aditya, studying Computer Science at Bangalore. I am currently in the third year and have good experience with Python. How may I start contributing to mailman? Regards, -- Aditya Dalwani P.E.S Institute of Technology, Bangalore, India

1 0

Plug-in Ideas for Gsoc 2015
by Aanand Shekhar Roy Feb. 20, 2015

Feb. 20, 2015

Hi everyone, We had discussed few plug-in ideas here among which following were found to be suitable: 1.Automoderation system for limiting post - Fexible automoderation system. Lot of moderators (and even more subscribers!) who would love to have long threads throttled (the first 10 messages delivered immediately, the next 10 with 3 hours delay, the next 10 with 6 hours delay, and after that doubling delay every 10 posts. 2.Asking for confirmation if a member's post include confidential information. 3.Timed vacations, allowing a user to postpone or discard emails on some lists for a certain number of days or weeks. So,I wish to ask can we put (1) and (3) on mailman wiki page of idea list for Gsoc'15. Among all ideas that have been accepted and discussed,I am interested in the following: The three mentioned above along with Banned word list as mentioned on the wiki.

1 0

Postorius test debugging problem : tests_forms.py
by Pranjal Yadav Feb. 20, 2015

Feb. 20, 2015

I started writing tests to improve the coverage for postorius and I ran into few problems which I couldn't solve for past few days. I added few new test cases and re-ran tox. It seems somehow none of the tests ran although the tox output says "ran 11 tests in 72.332s, failures = 3" Here is the link to my tests : http://pastebin.com/1jLhVsr2 I did change a few things in forms.py : http://pastebin.com/2P3vXW7W After running these tests I realized UserNewTest and ListNewTest never runs, though tox outputs it ran 11 test and failed 3 (mainly the assertTrue for listname, password and email methods), when I tried tox -e py27-django1.7 -- postorius.tests.test_forms.UserNewTest, it says 0 tests ran in 0.001s 1) So I don't understand why the assertTrue validation is failing though all the inputs to the form is prefect? I talked to Aurelien and Abhliash and also followed ( https://docs.djangoproject.com/en/1.7/ref/forms/validation/#validating-fiel…) however it left me with the same situation. 2) If the tests run with tox then why do they not run when a particular testcase is tested? 3) I discussed this problem with Aurelien and he mentioned "Form class shouldn't do anything in its __init__ function" however we do have __inti__ functions in our forms.py. So do we need to modify something there? -- *Pranjal Yadav*

1 0

Should REST API /addresses data be including the user_id field?
by Andrew Stuart Feb. 19, 2015

Feb. 19, 2015

This command: curl --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/addresses Returns this data: {"entries": [{"http_etag": "\"3045a243ea206ca6e112269f4c0ce8c4a66a92bf\"", "registered_on": "2015-02-19T03:52:55.460036", "display_name": "Server Owner", "self_link": "http://localhost:8001/3.0/addresses/theboss@example.org", "email": "theboss(a)example.org", "user": "http://localhost:8001/3.0/users/49955403891644350774308934370095835248", "original_email": "theboss(a)example.org"}, {"http_etag": "\"140a3ed1b92f9e14eab51b1183ba87c271191a0c\"", "registered_on": "2015-02-19T23:39:43.340973", "user": "http://localhost:8001/3.0/users/316531173466190680782932225868344081837", "self_link": "http://localhost:8001/3.0/addresses/testuser@example.org", "email": "testuser(a)example.org", "original_email": "testuser(a)example.org"}], "start": 0, "http_etag": "\"cb2df4aad285c85f0128b030ca4ce786308a0b4b\"", "total_size": 2} Should the address entries include the user_id field? thanks as

1 0

Removal of REST API method /lists/{list_identifier}/config/{sub_resource}
by Andrew Stuart Feb. 18, 2015

Feb. 18, 2015

####################################################################### exhibit 1: The REST API provides GET /lists/{list_identifier}/config PUT /lists/{list_identifier}/config PATCH /lists/{list_identifier}/config This allows reading of all list config variables (see bottom of this message for which ones). It also allows for setting of any individual config variable. ####################################################################### exhibit 2: The REST API also provides GET /lists/{list_identifier}/config/{config_variable} PATCH /lists/{list_identifier}/config/{config_variable} Which allows any individual config variable to be read and modified. ####################################################################### Effectively exhibit2 completely duplicates exhibit1 for no substantial gain. exhibit2 significantly increases the complexity of the overall system due to its fine grained duplication of everything in exhibit1. Right now I’m facing write a bunch of code to handle the fine grained config variable setting, all the while thinking “but this is all duplicate functionality”. I’m wondering if anyone would miss exhibit 2 if it was deleted from the REST API, saving on testing and complexity but losing nothing. Have I missed something? MAYBE its possible that different config items might have different user access requirements, justifying fine grained control, however I can’t see how right now. Thoughts? ... dict( ... acceptable_aliases=['one(a)example.com', 'two(a)example.com'], ... admin_immed_notify=False, ... admin_notify_mchanges=True, ... administrivia=False, ... advertised=False, ... anonymous_list=True, ... archive_policy='never', ... autorespond_owner='respond_and_discard', ... autorespond_postings='respond_and_continue', ... autorespond_requests='respond_and_discard', ... autoresponse_grace_period='45d', ... autoresponse_owner_text='the owner', ... autoresponse_postings_text='the mailing list', ... autoresponse_request_text='the robot', ... display_name='Fnords', ... description='This is my mailing list', ... include_rfc2369_headers=False, ... allow_list_posts=False, ... digest_size_threshold=10.5, ... posting_pipeline='virgin', ... filter_content=True, ... first_strip_reply_to=True, ... convert_html_to_plaintext=True, ... collapse_alternatives=False, ... reply_goes_to_list='point_to_list', ... reply_to_address='bee(a)example.com', ... send_welcome_message=False, ... subject_prefix='[ant]', ... welcome_message_uri='mailman:///welcome.txt', ... default_member_action='hold', ... default_nonmember_action='discard', ... )

1 1

REST API PUT versus PATCH - is there in any point in PUT and PATCH?
by Andrew Stuart Feb. 18, 2015

Feb. 18, 2015

There are several cases in the REST API where there is a PUT method that requires all fields to be present, and also a PATCH method which is the same except that not all fields are required. Is there any actual benefit in those PUT methods? I can’t see what they offer over the PATCH methods. Maybe its worth thinking about removing all PUT methods that don’t offer any substantial gain over the PATCH methods, reducing need for testing, documentation and complexity. Here are the PUT and PATCH methods in the REST API: AddressesVARUserPUT ListsVARArchiversPATCH ListsVARArchiversPUT ListsVARConfigPATCH ListsVARConfigPUT ListsVARConfigVARPATCH MembersVARPATCH MembersVARPreferencesPATCH MembersVARPreferencesPUT UsersVARPATCH UsersVARPUT UsersVARPreferencesPATCH UsersVARPreferencesPUT as

2 2

Re: [Mailman-Developers] [GSoC14] Full Anonymization Project Idea
by Rashi Karanpuria Feb. 18, 2015

Feb. 18, 2015

Hi I am a prospective Gsoc'15 applicant. I found the Anonymous mailing list idea for project interesting. While researching about the same I found this thread. I have a queries regarding this : Can't we keep our encryption application away from the site admins by creating an interface between sender and the switchboard ,what I'm trying to imply here is, can't we process the encryption before the mail goes to switchboard or server for further processing. Let say,the email sent by the sender gets into the interface first where it strips out the message header and encrypts the email address, so when the email goes to the switchboard it is already modified, does not contain original sender's address but has the details about where it is to be sent. Now when the receiver sends the reply then the email gets to the list moderator and after that it passes through the same interface which now decrypts it to the original address and forwards it after encrypting the sender's address. Stephen J. Turnbull writes: > In general, what is missing from these "anonymization" proposals are > use cases, user stories which display the reasons for anonymity and the > definition of anonymity (for example, should repeated posts from a > given subscriber have the same "From" field or not?) For example, the > following organizations want a "fully anonymized" list: > > 1. An Alcoholics Anonymous meeting. > 2. A therapy group for battered wives led by a professional therapist > (whose identity is known to all, and who knows all realspace > identities -- but maybe can't match them to list identities). > 3. A corporate whistleblower/suggestion box. > 4. A terrorist cell. (I'm not suggesting we should *care* about > serving these people well, and maybe we should try *not* to serve > them -- it's an intellectual exercise.) > 5. A tax evaders users' group. (ditto) > > How do their needs differ? How are they similar? How well does your > proposal serve their needs? I'm not too serious about that specific > list, individual students may or may not have experience and knowledge > of those use cases. But I would strongly prefer to work with a > student who thinks about these issues *explicitly* and *concretely* in > terms of use cases. In particular, it may seem obvious that we can't > protect the subscriber database against the site admin/root, but then > we have to give up on use case 3 above. Or do we? > > These are hard, *hard*, HARD questions. Even Bruce Schneier (if you > don't know who he is, find out!) might not get the answers at first > try. I don't ask you to get the hard ones at all! But sometimes the > answer is obvious from just asking the question (use case 3 vs root > access), so you'd best ask some of those easy ones. :-) > > About this specific proposal: > > Kshitij Gupta writes: > > > As I understand, we can do this in the following ways: > > 1. For each subscriber on the mailing list generate a random encryption > and > > decryption key, which will be store in the database. > > If the keys never leave the database, why not use symmetric > encryption? Why do different subscribers need different keys? > > If they do leave the database, how are they distributed? How is the > distribution protected from the standard attacks (eg, man in the > middle)? > > > 2. Everytime user sends the mail we can encrypt the email to a hash > which > > will then be used as the pseudo id for the user. To do this we can > either > > use salt (as in time) to ensure a new email id is generated everytime > > I don't understand why you would ever want this, let alone why there > is a use case common enough to be worth implementing in Mailman. > > That doesn't mean there isn't any, but please explain. > > > or without salt which equivalently fixes a single id for the user. > > 3. From the email we can cleanup headers, converting the users timezone > to > > a standard UTC timezone. > > You also probably need to handle Message-ID specially. > > > 4. We can also hash the users original email id and append it as a > > signature to sign the mail, ensuring the authenticity of mail in a > > conversation. > > That's not how digital signatures are done, and only those with access > to a descryption key can check authenticity. > > > 5. For replies, the person replying can respond to the message, the > email > > address will then be decrypted by matching against the list of all > > decryption keys and matching the digest of the mail id for additional > > security and forwarding it to the intended user. > > I'm not sure I understand the "additional security part." In any > case, if you have a "digest", why not use that as a unique key into > the user database, so that the actual decryption becomes an > authentication, and only needs to be done once? > > > The above steps (in my understanding): > > 1. Will allow users to anonymously post to mailing lists. > > Except that the site admin knows where to find each user. The site > admin had better be the only entity with such access. > > > 2. Ensure nobody can pretend to be someone else in a thread via the > > personal salt. > > But how about spoofing subscriptions? Do we care about that? What if > a user happens to know the address of another user, and spoofs that? > > > 3. Allow users to communicate in threads and reply to each other. > > 4. Use a constant space for users in the database, at the cost of > matching > > against multiple decryption keys and then checking against the hashed > email. > > Is constant space really an issue? > > > Look forward to some feedback and hope to contribute to the mailman > > community. > > > > [1]- https://code.launchpad.net/apparmor-profile-tools , however the > code > > was recently merged into the branch upstream at: > > https://code.launchpad.net/apparmor where development continues. > > > > Regards, > > Kshitij Gupta > > _______________________________________________ > > 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/stephen%40xemacs… > > > > Security Policy: http://wiki.list.org/x/QIA9 > _______________________________________________ > 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/archive%40jab.org > > Security Policy: http://wiki.list.org/x/QIA9 >

2 3

Building plug-ins for mailman.
by Aanand Shekhar Roy Feb. 18, 2015

Feb. 18, 2015

Thanks everyone for your invaluable suggestions,I was also thinking about having features as plug-ins like 1.As discussed with @Rashi007-Timed delay or timed delivery of messages - Suppose I wish to post a message to list but instead of composing and sending I prefer to send it delayed like I wish to post a message at 4am but since i would be sleeping at that time so what I can do,I will post my message at 10pm at night and a delaying or timed delivery plugin can deliver it at 4am. 2.Limited post by specific members - Being the list owner, I wish to restrict the number of posts one can do on the mailing list.Like a specific set of members can post 1 post per day,another set of members can do 10 posts per day. 3.Gmail has a plug-in system that allows listing of all your email subscriptions and unsubscribe with one-click from every list you dont read anymore...that will save much time unsubscribing to a lot of email lists and newsletters that you never read.Can we have one for mailman? Based on the discussions held previously on this topic,few ideas that have been found suitable are: 1.Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. 2.Asking for confirmation if a member's post include confidential information.

2 1

Building plug-ins for mailman.
by Aanand Shekhar Roy Feb. 18, 2015

Feb. 18, 2015

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 2. Confirmation from user before posting phone nos in emails 3. SpamAsassin as it is I wish to ask you all about other problems that mailman users face that may be solved by a plugin application or any other ideas you wish to see in the form of plugins .Any suggestions would be of great help. Thanks in advance

5 7

Re: [Mailman-Developers] authentication, authorization and permissions FYI
by Andrew Stuart Feb. 17, 2015

Feb. 17, 2015

Sorry I meant SAML looks similar to JWT but XML based. On 18 Feb 2015, at 10:45 am, Dick Visser <visser(a)terena.org> wrote: sorry meant to sent to list, just did that now On Wed, Feb 18, 2015 at 12:42 AM, Andrew Stuart <andrew.stuart(a)supercoders.com.au> wrote: > Hi Dick, > > If you re-post as a reply to the mailing list I can send a reply there. > > thanks > > as > > > On 18 Feb 2015, at 10:40 am, Dick Visser <visser(a)terena.org> wrote: > > Hi Andrew > > Is this about the MM3 web interface? > If so, I wonder if it could work with SAML authentication. > This can be done with PySAML2 (https://github.com/rohe/pysaml2), or in > an Apache module (mod_mellon). > The latter takes care of the authentication, and any web app protected > by it an rely on (for instance) REMOTE_USER always being available. > > Thanks > > Dick > > > On Sun, Feb 15, 2015 at 9:05 AM, Andrew Stuart > <andrew.stuart(a)supercoders.com.au> wrote: >> I’ve just finished (mostly) implementing most of the authentication, authorization and permissions systems. Thought you might be interested in a little on how it works. >> >> To discuss this further I need to explain a few things - apologies to those who i am teaching to suck eggs. >> >> The auth server needs a few key subsystems to get the job done - authorization, authentication and permissions. >> >> AUTHENTICATION - this is the process of the end user identifying themselves in the first place (in this case, by logging in with a username and password), then for every request beyond that, providing evidence that they are who they say they are - in this case, that’s done by giving them a token when they log in successfully, then requiring that the token be returned along with each subsequent request. >> >> AUTHORIZATION - this is the process of determining if the authorized user is allowed - according to the rules of our application - to access the resource that they have requested. For example, user Jenny sends a request to access the members of a list named supermaillinglist(a)marketingcompany.com. Before we can execute that request we need to determine if she is *authorized* to do so. >> >> PERMISSIONS - for the authorization process to do its job, it needs information about WHO is allowed WHAT LEVEL OF ACCESS to WHICH RESOURCE. This is the *permissions system*. It’s VERY easy to understand. Nothing more to it than a database table that looks like this >> user_id = Column(String, nullable=False) >> role = Column(String, nullable=False) >> resource_id = Column(String, nullable=False) >> resource_type = Column(Enum('list', 'domain', 'archive','server','domain', name='resource_type'), nullable=False) >> >> The permissions system is a small extension of the existing Mailman permissions system. >> user_id = the Mailman user id >> role = one of ['domainowner', 'serverowner', 'userowner', 'listowner', 'listmember', 'listmoderator'] >> resource_type one of ['list', 'domain', 'archive','server',’domain'] >> resource_id = Mailman list_id or Mailman domain or ‘server’ or ‘user' >> >> So with four pieces of information you can define access for any user to any Mailman resource. The permissions system is nothing more than a plain SQL table with four columns, that’s all. The important thing is that it unifies all Mailman resources into those four pieces of permission information. >> >> Tying it all together - the auth proxy: >> >> 1: receives an inbound HTTP API request >> 2: determines (from the token that came with the request) the authenticated identity of the requesting user >> 3: determines (from the request URL/field params) which Mailman resource is being requested (i.e. a list or a domain or something else) >> 4: determines (from the request URL/field params) the type of activity that the requesting user wishs to carry out against that resource (create new, delete, rename, for example) >> 5: asks the authorization process “is this user allowed to carry out this type of activity against this resource?” >> 6: the authorization process has its own set of business rules for working out if a particular user is allowed to carry out the requested activity against the requested resource. It uses the permissions table to work out if user is allowed to access resource in the requested manner. >> 7: finally, if the authorisation process approves, then the request is carried out. >> >> Phew! >> >> Any questions welcome. I’m hoping to have working code to show before Pycon. I want to get it sufficiently complete such that it works when I first release it. >> >> >> >> _______________________________________________ >> 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/visser%40terena.… >> >> Security Policy: http://wiki.list.org/x/QIA9 > > > > -- > Dick Visser > Sr. System & Networking Engineer > GÉANT Association, Amsterdam Office (formerly TERENA) > Singel 468D, 1017 AW Amsterdam, the Netherlands > Tel: +31 (0) 20 530 4488 > > GÉANT Association > Networking. Services. People. > > Learn more at: http://www.géant.org > -- Dick Visser Sr. System & Networking Engineer GÉANT Association, Amsterdam Office (formerly TERENA) Singel 468D, 1017 AW Amsterdam, the Netherlands Tel: +31 (0) 20 530 4488 GÉANT Association Networking. Services. People. Learn more at: http://www.géant.org

1 0

Re: [Mailman-Developers] authentication, authorization and permissions FYI
by Andrew Stuart Feb. 17, 2015

Feb. 17, 2015

Hi Dick, >>>Is this about the MM3 web interface? No I’m working on a REST API proxy which uses JSON web token for authentication - sounds like SAML is somewhat similar but JSON based. Postorius/Hyperkitty provides an end user web interface to MM3. I’m not sure what mechanism they use for user authentication - maybe Mozilla Persona, which I think uses JSON web token anyway. as On 18 Feb 2015, at 10:45 am, Dick Visser <visser(a)terena.org> wrote: Hi Andrew Is this about the MM3 web interface? If so, I wonder if it could work with SAML authentication. This can be done with PySAML2 (https://github.com/rohe/pysaml2), or in an Apache module (mod_mellon). The latter takes care of the authentication, and any web app protected by it can rely on (for instance) REMOTE_USER always being available. Thanks Dick On Sun, Feb 15, 2015 at 9:05 AM, Andrew Stuart <andrew.stuart(a)supercoders.com.au> wrote: > I’ve just finished (mostly) implementing most of the authentication, authorization and permissions systems. Thought you might be interested in a little on how it works. > > To discuss this further I need to explain a few things - apologies to those who i am teaching to suck eggs. > > The auth server needs a few key subsystems to get the job done - authorization, authentication and permissions. > > AUTHENTICATION - this is the process of the end user identifying themselves in the first place (in this case, by logging in with a username and password), then for every request beyond that, providing evidence that they are who they say they are - in this case, that’s done by giving them a token when they log in successfully, then requiring that the token be returned along with each subsequent request. > > AUTHORIZATION - this is the process of determining if the authorized user is allowed - according to the rules of our application - to access the resource that they have requested. For example, user Jenny sends a request to access the members of a list named supermaillinglist(a)marketingcompany.com. Before we can execute that request we need to determine if she is *authorized* to do so. > > PERMISSIONS - for the authorization process to do its job, it needs information about WHO is allowed WHAT LEVEL OF ACCESS to WHICH RESOURCE. This is the *permissions system*. It’s VERY easy to understand. Nothing more to it than a database table that looks like this > user_id = Column(String, nullable=False) > role = Column(String, nullable=False) > resource_id = Column(String, nullable=False) > resource_type = Column(Enum('list', 'domain', 'archive','server','domain', name='resource_type'), nullable=False) > > The permissions system is a small extension of the existing Mailman permissions system. > user_id = the Mailman user id > role = one of ['domainowner', 'serverowner', 'userowner', 'listowner', 'listmember', 'listmoderator'] > resource_type one of ['list', 'domain', 'archive','server',’domain'] > resource_id = Mailman list_id or Mailman domain or ‘server’ or ‘user' > > So with four pieces of information you can define access for any user to any Mailman resource. The permissions system is nothing more than a plain SQL table with four columns, that’s all. The important thing is that it unifies all Mailman resources into those four pieces of permission information. > > Tying it all together - the auth proxy: > > 1: receives an inbound HTTP API request > 2: determines (from the token that came with the request) the authenticated identity of the requesting user > 3: determines (from the request URL/field params) which Mailman resource is being requested (i.e. a list or a domain or something else) > 4: determines (from the request URL/field params) the type of activity that the requesting user wishs to carry out against that resource (create new, delete, rename, for example) > 5: asks the authorization process “is this user allowed to carry out this type of activity against this resource?” > 6: the authorization process has its own set of business rules for working out if a particular user is allowed to carry out the requested activity against the requested resource. It uses the permissions table to work out if user is allowed to access resource in the requested manner. > 7: finally, if the authorisation process approves, then the request is carried out. > > Phew! > > Any questions welcome. I’m hoping to have working code to show before Pycon. I want to get it sufficiently complete such that it works when I first release it. > > > > _______________________________________________ > 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/visser%40terena.… > > Security Policy: http://wiki.list.org/x/QIA9 -- Dick Visser Sr. System & Networking Engineer GÉANT Association, Amsterdam Office (formerly TERENA) Singel 468D, 1017 AW Amsterdam, the Netherlands Tel: +31 (0) 20 530 4488 GÉANT Association Networking. Services. People. Learn more at: http://www.géant.org

1 0

authentication, authorization and permissions FYI
by Andrew Stuart Feb. 17, 2015

Feb. 17, 2015

I’ve just finished (mostly) implementing most of the authentication, authorization and permissions systems. Thought you might be interested in a little on how it works. To discuss this further I need to explain a few things - apologies to those who i am teaching to suck eggs. The auth server needs a few key subsystems to get the job done - authorization, authentication and permissions. AUTHENTICATION - this is the process of the end user identifying themselves in the first place (in this case, by logging in with a username and password), then for every request beyond that, providing evidence that they are who they say they are - in this case, that’s done by giving them a token when they log in successfully, then requiring that the token be returned along with each subsequent request. AUTHORIZATION - this is the process of determining if the authorized user is allowed - according to the rules of our application - to access the resource that they have requested. For example, user Jenny sends a request to access the members of a list named supermaillinglist(a)marketingcompany.com. Before we can execute that request we need to determine if she is *authorized* to do so. PERMISSIONS - for the authorization process to do its job, it needs information about WHO is allowed WHAT LEVEL OF ACCESS to WHICH RESOURCE. This is the *permissions system*. It’s VERY easy to understand. Nothing more to it than a database table that looks like this user_id = Column(String, nullable=False) role = Column(String, nullable=False) resource_id = Column(String, nullable=False) resource_type = Column(Enum('list', 'domain', 'archive','server','domain', name='resource_type'), nullable=False) The permissions system is a small extension of the existing Mailman permissions system. user_id = the Mailman user id role = one of ['domainowner', 'serverowner', 'userowner', 'listowner', 'listmember', 'listmoderator'] resource_type one of ['list', 'domain', 'archive','server',’domain'] resource_id = Mailman list_id or Mailman domain or ‘server’ or ‘user' So with four pieces of information you can define access for any user to any Mailman resource. The permissions system is nothing more than a plain SQL table with four columns, that’s all. The important thing is that it unifies all Mailman resources into those four pieces of permission information. Tying it all together - the auth proxy: 1: receives an inbound HTTP API request 2: determines (from the token that came with the request) the authenticated identity of the requesting user 3: determines (from the request URL/field params) which Mailman resource is being requested (i.e. a list or a domain or something else) 4: determines (from the request URL/field params) the type of activity that the requesting user wishs to carry out against that resource (create new, delete, rename, for example) 5: asks the authorization process “is this user allowed to carry out this type of activity against this resource?” 6: the authorization process has its own set of business rules for working out if a particular user is allowed to carry out the requested activity against the requested resource. It uses the permissions table to work out if user is allowed to access resource in the requested manner. 7: finally, if the authorisation process approves, then the request is carried out. Phew! Any questions welcome. I’m hoping to have working code to show before Pycon. I want to get it sufficiently complete such that it works when I first release it.

2 1

Soliciting feedback on idea for rounding out the permissions model.
by Andrew Stuart Feb. 17, 2015

Feb. 17, 2015

I had an idea about rounding out the Mailman permissions model, interested in hearing thoughts on it. Obviously there has been considerable discussion on this topic before. Mailman already carries much of the information needed for determining user permissions to Mailman resources. Only two things are missing: 1: the ability to define a user as being a “serverowner” 2: the ability to define a user as being a “domainowner” (You’ll need to look at this email in plain text to see the table properly). The Mailman permissions model currently looks like this: resource_type roles resource_id user_identifier where to find permission --------------------------------------------------------------------------------------------------------- user userowner n/a UUID (defined in user record) list listowner list_id subscriber (defined in list member record) list listmember list_id subscriber (defined in list member record) list listmoderator list_id subscriber (defined in list member record) list listnonmember list_id subscriber (defined in list member record) I am suggesting adding two further permissions to the existing permissions model, which would look like this: resource_type roles resource_id user_id where to find permission --------------------------------------------------------------------------------------------------------- server serverowner n/a UUID (not currently defined in Mailman) domain domainowner mail_host UUID (not currently defined in Mailman) To implement, it would need to be possible to define as user as being a ‘serverowner’, and also to be able to define a user as being a ‘domainowner’ for any given domain. If it were possible to do so within the Mailman core then there would be a completely usable permissions model entirely within Mailman, and no need to store any additional permissions data outside Mailman. The permissions model would allow definition of user access to any Mailman resource including domains and servers. The interpretation of the permissions would still be up to the application that consumes the REST API, as is currently the case. Thoughts? as

3 6

A couple of archiving questions
by Andrew Stuart Feb. 16, 2015

Feb. 16, 2015

Can anyone point me in the direction of a good explanation of how archiving works? I’ve found bits and pieces but the picture isn’t totally clear - it appears that archiving requires some sort of archive handler function to be written and installed as part of Mailman? Is there any reason why it should not be possible to be able to pull messages scheduled for archiving out through the REST API as file attachments? thanks

5 9