Mailman 3 July 2014 - Mailman-Developers

[CLI Project] Command Parsing method switched to YACC
by Rajeev S 24 Jul '14

24 Jul '14

Hi, I have been a bit unhappy about the regular expression approach for command validation and array processing for command parsing to get the arguments. So I have decided to switch to the conventional and right method to do it, using the Lex-YACC duo, using the PLY module. I have already ported half of the command's processing to PLY and it works great. I will be completing the rest of commands by 25/07/2014, I expect to push r67 by 26/07/2014. I have set a soft deadline for the tasks mentioned in my proposal as 06/08/2014, Google deadline being 11/08/2014. Remaining tasks include, 1. Backup and restore tool, 2. Export data to CSV or Text 3. Man Pages 4. User Documentation -- Docstring improvement and regularization 5. Writing Installation routines for new modules All tasks except `1` are easy. So my primary focus for the next week(s) would be the backup and restore tool. Post the above mentioned soft deadline, I would be writing the unittests for the new units. I had postponed the unit test writing as it consumed lot my time.

1 0

[CLI Project] Update Preference Command added
by Rajeev S 20 Jul '14

20 Jul '14

Hi, I have pushed two revisions, r65 (19/07/2014) and r66 (20/07/2014). Here are the changes under r65: - Changes the command preprocessing workflow - Command processing invoked by using a decorator. - Removes redundant code in present in the shell, for example, at the auto complete functions. - error reporting brought to single point, as in the command tools - removes the override on the cmd.parseline function, so that the autocomplete functions work flawlessly - Commands are now processed just before the actions are performed, hence providing maximum control. http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision… Here are the changes under r66: - Introduces the `update preference` command for Mailman shell. - Regular expression based syntax verification for all commands. The regular expressions are read from the config.ini using the ConfigParser. The regex based verification helps to avoid validations when the commands are being processed for execution. - Adds docstrings for all command methods - Upon command failure or syntax error, command help and usage are displayed http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision…

1 0

listarchiver table missing from postgresql schema
by ML mail 18 Jul '14

18 Jul '14

Hi, I am currently testing Mailman3 with PostgreSQL and found out that the listarchiver table is missing from the PostgreSQL schema (database/schema/postgres.sql). It is correctly included in SQLite migration schema though (database/schema/sqlite_20130406000000_01.sql). Regards ML

2 1

[CLI Project] Completed Subscribe and Unsubscribe commands
by Rajeev S 17 Jul '14

17 Jul '14

Hi, I have completed and pushed the subscribe and unsubscribe command support as r64. This adds two commands to the shell subscribe users a(a)b.com foo(a)bar.com to list(a)domain.org unsubscribe users a(a)b.com foo(a)bar.com from list(a)domain.org The next revision, r65 will refactor code to reduce redundant code at many functions and betterment of error and exception handling and reporting. The revision 65 will also include Preferences related actions. http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision… *Regards,Rajeev S* *http://rajeevs.tk <http://rajeevs.tk>*

1 0

user table in Mailman3 with PostgreSQL
by ML mail 16 Jul '14

16 Jul '14

Hello, I am not sure it is a good idea to name the user table "user". As you can see in PostgreSQL "user" is a reserved word: \c mailman select * from user; current_user -------------- postgres (1 row) Any ideas how I can still list the content of the mailman3 user table in PostgreSQL? Regards ML

3 7

[CLI Project] Create object and Delete object functionalities
by Rajeev S 12 Jul '14

12 Jul '14

Hi, I have pushed 2 revisions r62 (10/07/2014) and r63 (12/07/2014) that implement the create object and delete object functionalities. A snapshot of the new revisions: 1. The support for automatic implicit filtering based on reserved environment variables like domain has also been implemented. Now, the user can set a reserved variable, say domain, and perform actions on the shell without specifying the domain filter in the future commands. See docs for examples and more explanation. 2. Create actions use the same functions as of the command tools. The required arguments are collected from user and user is promptly notified about the required arguments, in case if any of them are missing. 3. Delete commands use the syntax of the show command, and hence support the same level of filtering as in show command. 4. The support for turning shell environment on and off has been implemented. 5. All the commands now support auto complete feature, up to the first argument. The next set of tasks are subscription related tasks, which will be completed by Monday,14th July. http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision… http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision…

1 0

gsoc ci tool updates
by varun sharma 09 Jul '14

09 Jul '14

HI everyone, I have been trying to implement the ci-tool a different way, instead of changing the configuration in the source, i am now creating new client/server files along with the new configuration. The main advantage is that the source will remain untouched if someone just want to use the tool. Also, in default config, i've added mailman, postorius, mailmanclient, hyperkitty and kittystore. If someone wants to use it for different projects, then he can simply change the config file of client and in that case the tool will first look for those packages into the installed packages and if it does not find them there, then it will look for absolute path in config. Best possible case is when all the projects involved are installed in virtualenv using 'pip install -e package'. You can try it out by branching the repo bzr branch lp:~varun/mailman/mmci pip install -e mmci For client: mmciclient --create client_name mmciclient --pull client_name mmciclient --test client_name mmciclient --try_ client_name --create command will create a dirctory with client_name and further subdirectories (config,logs,patches) For server: mmciserver --create server_name mmciserver --start server_name In the previous implementation, i was using project names instead of client/server configuraion like: ci-tool --pull postorius ci-tool --test postorius I think the former implementation is better as it can save multiple user defined configurations for client and servers and it is bit more user friendly. Suggestions on this implementation or how can i improve it further are welcomed. Thanks Varun

1 0

Mailman3 user management
by ML mail 07 Jul '14

07 Jul '14

Hi, I installed Mailman 3 and Postorius all working fine so far but I have a question regarding user management. I got one admin user created while running the "syncdb" command in Django, but how do I now create additional users? Ideally I would like one "domain admin" user (multi-domain hosting environment) who can manage mailing lists for a specific domain, is this possible? Regards, ML

1 0

[CLI Project] Initial Commit on Command Line Shell
by Rajeev S 07 Jul '14

07 Jul '14

Hi, I have pushed the r61 [1], which makes it the first commit on the Command Line shell. As Steve suggested, I have also modified the CL tools (and shell) to support both singular and plural instance names using a naive function, that can be replaced with a prefix matching procedure, if necessary. As for the shell, it currently supports the `display objects` functionality using the `show` clause. The `show` clause supports three kinds of filters, equality, in_list and a regular expression filter. Also, r61 adds a basic version shell environment functionality, which can be used to store variables that can be reused in the queries. The feature `setting of mailman object names in the environment and using them without explicitly specifying them the queries` is yet to be built and will be a part of r62, which I expect to complete by Wednesday (09/07/2014). r62 will also include the create functions for the mailman objects. Currently, the shell supports only conjunctions in clauses. Queries can contain any number of filters specified using the conjunctions. A few sample queries that are currently supported by the shell >>>set domain domain.org >>>show lists where mail_host = $domain >>>show lists where mail_host = $domain and foo(a)bar.com in moderators >>>show users where display_name like .*foo >>>show domains >>>unset domain I have also updated the docs for the same. r62 will contain: 1. Automatic filtering of results based on predefined environment variables like domain, list and user 2. `Create object` queries, a quite straight forward one. 3. `Delete object` queries 4. Turn on/off the environment variables Footnotes [1] http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision…

1 0

DMARC discussions at IETF, WG likely to form
by Stephen J. Turnbull 04 Jul '14

04 Jul '14

Hi all, For the past few weeks I've been participating in discussions of DMARC at the IETF, and I thought I'd post an update as matters have taken a somewhat optimistic turn there. According to participants there, the dmarc(a)ietf.org mailing list is the primary venue for discussion of DMARC development-related topics at the moment (the list at dmarc.org has been inactive for months). Over the past few weeks a general consensus has developed that further technology should be developed, which we hope will be adopted by providers like AOL and Yahoo!, as well as by mailing lists and others suffering from draconian DMARC policies. To this end, a charter for an IETF working group has been proposed, discussed, and will be submitted to the IETF very soon. The proposed charter is here: http://trac.tools.ietf.org/wg/appsawg/trac/wiki/DMARC (I'm not sure if this is the original or how current it might be; only a few suggestions for changes were received.) Briefly, the DMARC protocol itself is considered "successful" as far as it goes, so the current protocol is proposed for independent publication by its current editors as an Informational RFC. (Ie, this is not part of the working group's function.) I think this is reasonable, as the DMARC Consortium can ignore any RFC they don't like. The specific products of the working group that are planned are a Best Current Practices RFC on implementation and deployment of DMARC tools, and new experimental or standards-track RFCs aimed at providing protocols for senders to designate authorized resenders (such as mailing lists). I don't know how soon the working group will be formed, but I suppose some discussion will take place while we're waiting for official word from the IETF. Mailing list discussion of the charter, as well as the concrete proposals received so far, can be found here: https://mailarchive.ietf.org/arch/search/?q=dmarc Not directly related to the chartering process, but perhaps of interest to Mailman-Developers, are the following documents. The BCP draft is here: http://tools.ietf.org/html/draft-crocker-dmarc-bcp Three proposals for third-party authorization: http://tools.ietf.org/html/draft-kucherawy-dkim-delegate http://tools.ietf.org/html/draft-levine-dkim-conditional http://tools.ietf.org/html/draft-otis-tpa-label (from simplest to most complex). Regards, Steve

1 0

Mailman-Developers July 2014