Mailman 3 June 2014 - Mailman-Developers

before next release: disable backscatter in default installation
by Jo Rhett Nov. 7, 2022

Nov. 7, 2022

Hi. There's a fairly simple problem here that needs to be addressed. And it's mostly a documentation/install problem. I'm hoping we can get this resolved before the next release. PROBLEM: Mailman comes out of the box ready to backscatter spam people. Yes, it's easy enough to fix. But because it comes stock this way, and is documented to install this way, most people install it to do this. Those of us who work in abuse departments are tired of hearing "well that's how Mailman … [View More]

21 168

Re: [Mailman-Developers] Disabling SELinux
by Stephen J. Turnbull July 1, 2014

July 1, 2014

Aurelien Bompard writes: > For your information, I have written a small SELinux module for Mailman3, > it's included in my Fedora RPM and works fine. In the future (when MM3 is > out), I'll ask for integration in the core policy. "Core policy" means at SELinux? Why not put it in a contrib directory in MM3, too? Why not now?

2 1

[CLI Project] Portioning Commands as Singular or Plural
by Stephen J. Turnbull June 30, 2014

June 30, 2014

Rajeev S writes: > The commands surely do become more intuitive and make more sense, > but this has a negative,the number of commands almost doubles. The number of instances of "class Command" or whatever it's called doesn't need to double, though. You could simply have the parser recognize the relevant plurals as equivalent to the corresponding singular forms. If you want to make life hard, you could do that but in addition in the parse constrain the command to number agreement (ie,… [View More]

1 0

[CLI Project] Portioning Commands as Singular or Plural
by Rajeev S June 30, 2014

June 30, 2014

Hi, A modification has been suggested for the Command line tools in an IRC discussion with Abhilash. It was suggested that, to make commands more intuitive, the commands be partitioned into singular and plural as per the scale of the action performed. For example, In the current scenario >>>./mmclient show user //Lists all users in the system >>> ./mmclient show user foo(a)bar.com //Describes the user foo(a)bar.com Usage after the suggested change >>>./… [View More]

1 0

[CLI Project] Support of filtering of objects in Command Shell
by Rajeev S June 29, 2014

June 29, 2014

Hi, Now the mid term evaluations are done, I would be building the command line shell, as planned. I would like to present how I would like to tackle the requirement at hand. As mentioned in my proposal and the most logical approach, all the common functionalities between the shell and the already built command line tools would use the same classes, the ones built for the command tools. As this is a command shell, I wish to give it a SQL like feel. However, The SQL commands SELECT, … [View More]INSERT INTO do not look nice in Mailman context, as we are dealing with objects and not tables. I would be using the object related terms like SHOW, CREATE etc for the respective actions. However, I would like to discuss about the support for the WHERE clause by the shell. The WHERE clause is not mentioned in my proposal, but I feel that this feature ought to be in the project. If the commands require to support a WHERE clause, as SQL does, For example, >>> show users where display_name = 'foo' and subscribed_list_ids contains = 'list(a)domain.org <mailto:%27list@domain.org>' The steps involved in processing a command with a WHERE clause would be 1.Parse the command 2.Filter the results from the database 3.Perform the action using the command line tool methods if possible else write a new procedure. For the Step 2, there are two approaches in hand: 1.Use the Storm library to query the database directly, as mailman core does. 2.Use the REST API By using the first approach, a good performance improvement is achieved, by leaving the data filtering to database engine. But this limits the usability of of the CLI to the system in which the mailman database exists, as the remote connections to DB servers are usually disabled. By using the second approach, the performance is bad, as it requires a normal python `for` loop that compares the the results one by one. However, this approach might be easier in case that the mailman installation be managed remotely, if its OK to enable the REST API to accept connections from remote machines.(I believe this is currently not supported/disabled by default.) By building the WHERE clause, its costlier to reuse the command line tools methods in many use cases, like delete, subscribe etc. Further, as I have already mentioned to Abhilash, it demands more time. I am not sure if that will fit into GSoC time frame. I am confident that I can make significant progress, but not sure if it can be 'completed'. Also, I am fine on completing it even after GSoC. So, the final question is, Should the CLI support filtering using the WHERE clause? Or should I proceed as per my proposal, building a basic Mailman shell and leave the rest to be completed in future? [View Less]

3 2

GSoC updates till midterm
by varun sharma June 24, 2014

June 24, 2014

Hi everyone, This will be my second update email to mm-dev after gsoc started, i'll be sending weekly summaries in the future. The ci-tool(please suggest some nice name) is almost finished, i need few more days to get it working on multiple projects under mailman suite. The following parts of ci-tool are working: ./ci-tool --pull project_name ./ci-tool --pull all ./ci-tool --test project_name ./ci-tool --test all ./ci-tool --try project_name The projects under the mailman suite are listed … [View More]

1 0

[CLI Project] Preference management commands added
by Rajeev S June 22, 2014

June 22, 2014

Hi, As promised, I have completed the preference related commands and pushed it as revision 60 [1]. The preferences form a new scope, along with user, domains and lists. There are 2 commands associated with the `preference` scope. 1.Show Preference ./mmclient show preference [scope] [scope_args] [key] That is, to view a preference of a list member ./mmclient show preference member --email a(a)b.com --list list(a)domain.org receive_own_postings 2. Update Preference Similar to … [View More]

1 0

Disabling SELinux
by Stephen J. Turnbull June 19, 2014

June 19, 2014

I thought I sent this but my MUA disagrees.... A user (one among many) writes: > Mark, > Good straw to grasp at. I thought SElinux had already been disabled but it > hadn't. It seems to be working now. Do we have better advice than just "disable SELinux" to offer? I ask because "solving" the DMARC "problem" seems to involve trust of Mediators (the technical RFC term for middlemen like Mailman) by Author Domains (RFC-ese for domains with DMARC policies about verifying From:). … [View More]

3 2

[CLI Project]Commands for adding Moderators and owners
by Rajeev S June 19, 2014

June 19, 2014

Hi, I have pushed r59 (In fact, 2 days before) which adds commands to perform the following actions - Add moderators ./mmclient add-moderator list list(a)domain.org --user a(a)b.com b(a)c.com d(a)e.com - Add owners ./mmclient add-owner list list(a)domain.org --user a(a)b.com b(a)c.com d(a)e.com - Remove Moderator ./mmclient remove-moderator list list(a)domain.org --user a(a)b.com b(a)c.com d(a)e.com - Remove Owner ./mmclient remove-owner list list(a)domain.org --… [View More]

1 0

Two more DMARC mitigations
by John Levine June 18, 2014

June 18, 2014

* Forwarding signature The IETF DMARC list is discussing a mutant weak DKIM signature from a sending system (e.g. Yahoo and AOL) that would survive forwarding, but contains a list of forwarding target domains. It's only considered valid if it's with a signature from the forwarding domain, i.e., the list. This is nice for list operators, since it requires nothing beyond not stripping the signature header, and signing on the way out. * Submit and sign When a user at a p=reject signs up for a … [View More]

7 23