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)
Hi,
I have pushed r68 that adds the export to CSV feature to the mailman
command line tools.
Usage
./mmclient show user -v --csv path/to/file.csv
./mmclient show list -v --csv path/to/file.csv
./mmclient show domain -v --csv path/to/file.csv
The r68 further adds the support for white spaces in object names. The
corresponding regular
expression has been modified in all parsers.
>>> create user with `email` = `a(a)b.com` and `display_name` = `Foo
Bar` and `password` = `abcde`
http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision…
On Jul 29, 2014, at 10:13 AM, Aurelien Bompard wrote:
>I'm interested in helping port MM3 to SQLAlchemy, I've had some experience
>with it in the past. But first I'll add some tests to my patch, then I'll
>port KittyStore to SQLAlchemy, so I'll make less mistakes porting MM3, which
>is a significantly bigger piece.
Sounds great. Help is greatly appreciated! I have an unfinished branch
somewhere which I'll try to resurrect if there's anything useful there. I
think this will be a deep change, especially since there are ties to the
testing infrastructure, so it might be best to collaborate on it. I'm quite
happy of course to do that with you!
>Do you think we can release MM3 with Storm? Should we wait for the SQLAlchemy
>port? It's not in the TODO list on
>http://wiki.list.org/display/DEV/Mailman+3.0
I'm becoming increasingly concerned about our dependence on Storm, and not
just because of the lack of Python 3 support[*]. While I like the simple and
transparent model, I think the problems we're having with both SQLite and
PostgreSQL point to the need to switch. If we don't have a reliable database
layer, how can we possibly release?
Opinions very much welcome. If there's consensus that the switch is needed,
I'll add it to the wiki page above and start spending time on it.
Cheers,
-Barry
[*] Don't worry, porting Mailman to Python 3 is *not* on the table for 3.0.
Hi Aurélien,
You might then also be interested to follow the bug I submitted for this purpose:
Bug #1343137 “listarchiver table missing from postgresql schema” : Bugs : GNU Mailman
Bug #1343137 “listarchiver table missing from postgresql...
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 i...
View on bugs.launchpad.net Preview by Yahoo
On Friday, July 18, 2014 10:28 AM, Aurelien Bompard <aurelien(a)bompard.org> wrote:
Got hit by that too, I just created a merge request with the missing file :
https://code.launchpad.net/~abompard/mailman/pgsql_upgrade/+merge/227289
Could anyone have a quick look at this?
Aurélien
Hi,
In Mailman3 it would be nice to be able to add moderators to a mailing list from the command line using the mailman command. Currently I can only see the possibility to add new members to a mailing list, or did I miss something here?
Regards
ML
Hi,
I am testing the two following list config parameters:
default_nonmember_action
default_member_action
and actually the following options do not work: Reject (with notification) and Discard (no notification)
It looks like currently only the hold for moderator and accept options are working. Is it possible that these two are not ready yet in the beta4 version of mailman?
Furthermore the approval mail to the moderator contains in its body as reason XXX:
Reason: XXX
I guess this also needs adapting.
Let me know if I should open a bug for this.
Regards
ML
Cheers Rajeev!
On Monday, July 28, 2014 8:44 AM, Rajeev S <rajeevs1992(a)gmail.com> wrote:
Hi,
On Sun, Jul 27, 2014 at 4:29 PM, ML mail <mlnospam(a)yahoo.com.dmarc.invalid> wrote:
Yes, I guess something like a "-m" option would be good to specify that the e-mails being added with the "-a" option are moderators. Right now I have switched to using the REST API as it has all features I need, great work btw!
>
>
>
>On Saturday, July 26, 2014 12:20 AM, Barry Warsaw <barry(a)list.org> wrote:
>
>
>
>On Jul 24, 2014, at 02:03 PM, 'ML mail' via barry wrote:
>
>
>>In Mailman3 it would be nice to be able to add moderators to a mailing list
>>from the command line using the mailman command. Currently I can only see the
>>possibility to add new members to a mailing list, or did I miss something
>>here?
>
>You're not missing anything. The CLI for adding members isn't fantastic - you
>have to provide a file with one member per line. The way to extend this would
>be to be able to specify the members' role when adding them. I haven't
>thought of an elegant way to do this via the CLI, especially when multiple
>members can be added. Once a good interface is designed, it would be pretty
>easy to write the code to do it.
>
>
The CLI I built as part of GSoC 2014 supports the above features
http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli
It is based on the REST API.
To Add moderators you can do
./mmclient add-moderator list list(a)domain.org --user a(a)b.com b(a)c.com ...
Similarly to add owners do
./mmclient add-owner list list(a)domain.org --user a(a)b.com b(a)c.com
To add normal members
./mmclient subscribe user user1(a)bar.com user2(a)bar.com --list list(a)domain.org
You might want to install the PLY library [https://pypi.python.org/pypi/ply/3.4] to test the CLI fully.
Hi,
As mentioned, I have pushed r67, that comprises of the improved command
parsing system using Lex and YACC, for the Mailman shell.
The PLY module is used for the purpose.
Every command has a parser script associated with it, under the
`client/parsers/` directory. The parser is imported and used by each command
independently. The parser returns the necessary arguments as a hash
table, which can be easily used by the command execution
procedure.
The change of command parsing method to PLY now handles both command
validation and parsing/processing, which was
previously done in independent command processing steps. The r67 also
improves the environment variable management.
http://bazaar.launchpad.net/~rajeevs1992/mailman.client/mailmancli/revision…
Hello,
I am trying to find out all possible REST API parameters but can't find any documentation listing them all. For example I want to create a new mailing list using the following REST API URL:
http://localhost:8001/3.0/list
in the documentation I could only find the "fqdn_listname" parameter but there must definitely be more possible parameters such as one for the description, etc. Where can I find a list of these parameters?
Regards
ML
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.
