Mailman 3 March 2015 - Mailman-Developers

[GSoC] Introduction - A Dashboard for Admins/Owners/Moderators
by Anuj Bansal 07 Mar '15

07 Mar '15

Hi all, I'm Anuj, a computer science undergraduate at Birla Institute of Technology and Science, Pilani. I'm interested in the project "Dashboard for Admins/Owners/Moderators". I've already downloaded and setup my development environment with the help of instructions given on [1]. I know Python and HTML and have been working on it from last 1 year. I'm also quite familiar with Django framework and have made some projects using it. Last semester I made a Django project which is currently been used by my institute [2]. I'd like to contribute to Mailman and hence, would like ideas for patches / code samples which I could write like supporting modules which may be required for the project or some other bug fixes. Thanks and regards, Anuj Bansal [1] - http://gnu-mailman.readthedocs.org/en/latest/src/mailman/docs/WebUIin5.html [2] - http://www.bits-pilani.ac.in:12383/

1 0

Re: [Mailman-Developers] Setting my web-server to run mailman
by Mark Sapiro 07 Mar '15

07 Mar '15

On 03/06/2015 11:47 PM, Rakesh Verma wrote: > I can't get past the Step 5 in the installation tutorial: > http://www.gnu.org/software/mailman/mailman-install/node10.html > I am fairly very new to mailman. > Any possible help for kind of me? If you are doing this for GSoC, you should be working with Mailman 3. See <http://docs.list.org>. If you really want to install Mailman 2.1, please describe exactly what the problem is. "I can't get past the Step 5" does not tell us how to help you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: [Mailman-Developers] Anatomy of list ids does not keep with that of urls causes some REST end points to return 404 always
by Richard Damon 07 Mar '15

07 Mar '15

On 3/7/15 5:27 AM, Ankush Sharma wrote: > Hello everyone, > > I want to discuss a serious issue regarding mailman architecture in context > with bug #1429366 <https://bugs.launchpad.net/mailman/+bug/1429366>. > The *hash(#) > *is a valid character as far as the local part of the email addresses is > concerned as per the email RFCs. So, as the mailing list addresses are > email addresses too, we can use # in the list names too. And, in context > with mailman it works well. We can create a list with list_id > *sam#hashed.host.org > <http://hashed.host.org>* for the address *sam#hashed(a)host.org > <hashed(a)host.org> *. This works fine. But it makes the *list_id *to contain > the hash character and therefore the REST endpoint for retrieving list wise > info becomes invalid, i.e : > > *<api-root>/lists/sam#hashed.host.org <http://hashed.host.org>* > > Because in an URL the stuff after # is treated as *document starting point* > i.e an id identifier or something of a dom element. This is not a valid > PATH for the server. Therefore the *falcon wsgi request object* does not > contain information of that and the *req.path* simply returns *sam* as the > *list_id* ( http://bazaar.launchpad.net/~mailman-coders/mailman/3.0/view/head:/src/mail… > ) giving a 404 because there is no any list with list id *sam*. > The mailman client works fine, it sends a GET to > *<api-root>lists/sam#hashed.host.org > <http://hashed.host.org>. * > > This causes the REST end points which needs *list_id* to return 404 or in > worse we can have a list_id clash between ids* sam#XXXXX* and *sam*. > Further more if the list_id starts with a # character then the server finds > list_id to be *empty string* and therefore we get a KEY ERROR because > *fqdn_listname > *is not set too. The bug highly effects postorius too. The lists index > template at */postorius/lists/ *cannot be rendered as it uses the former > REST endpoint and again a 404 is given. And, until we delete this list from > the database, we can't do anything except of getting a 404 and KEY ERROR > each time. > As far as security is concerned, if an another user created a public list > using a hash character, then public list indexing would also fail. > > *Possible fixes:* > 1. Put a constraint over the use of this kind of characters, but it's like > falling back. > 2. Do not derive list ids directly from the list addresses, use some kind > of hashing or encoding technique to generate list_ids. Need to change a lot > in architecture; :( . > 3. Use obscure techniques to retain the hash part as discussed here > http://stackoverflow.com/questions/317760/how-to-get-url-hash-from-server-s… > . > > I think this is quite a serious issue in mailman architecture; i.e > obtaining list_ids directly from list addresses. I have been trying to fix > this bug using some obscure techniques. But as it is related to mailman > architecture, I thought it should be worthy to discuss on the mailing list > first. > > Thanks, > Ankush Sharma > github.com/black-perl > The simple, and standard complient, solution would seem to be to define that special characters get URL encoded as needed (and decoded on the receiving end. It should be standard procedure that ANY routine building a URL would use URL encoding on the pieces unless it is positive that it is not needed. (URL encoding is replacing the problem chars with %nn where nn is the hex value of the character, this now makes % a problem char so it is sent as part of the URL as %25) -- Richard Damon

1 0

Re: [Mailman-Developers] Discussion about Mailman plugins(GSOC 2015)
by Stephen J. Turnbull 07 Mar '15

07 Mar '15

Please keep traffic on-list, unless it's security-related or truly personal. Replying to list. Prakash kumar writes: > > What does a "plugin" give that improves on this process? > > The only problem that I find is, we need to implement a framework for > loading, unloading and communication of plugins. We have such a framework already, and since the only person who will be using it is the site admin (see below), I really don't see why the command-line-based download-copy-configure process is excessively burdensome. > Loading and unloading plugins are better than going to code and making > changes for every requirement. Somebody has to write the code. Once it's written, you just copy the module into place, and no code needs to be written. > It will also help new developers to write plugins without actually > understanding the complex coding of mailman. I can't imagine an interesting plugin that requires no understanding of Mailman internals. Theming web interfaces, sure, but that's not part of Mailman core anymore, that would for Postorius or HyperKitty or some other application. What kind of thing are you thinking about? Is it really appropriate for a mailing list (vs a blog or web forum)? > I think it will be better if we can give the users What users? See next comments. > ability to load and unload plugins without touching the source code We already have that, for values of "user" == site admin. With a prewritten plugin (handler or rule), the only Python you need to know is the syntax of Python lists and strings, and maybe not even that. > means from the web ui like in wordpress. I think this is very unlikely to happen. No sane site admin would enable such a feature in Mailman as currently implemented, because once you have a Python module, you have access to pretty much everything inside of Mailman. For example, you could write a plugin that looks for private or no-archive lists, saves a month of posts to disk, and then spews the lot to Twitter (after checking the language and spewing to Weibo instead for Chinese). The only thing I can think of would be nice to have, maybe the site admin could install the handlers/rules manually as now, but add a feature to Postorius to allow manipulation of the pipeline from the web UI so that handlers or rules could be enabled selectively for individual lists. Again I'm not sure that a sane site admin would allow this from the web UI, because manipulating the pipeline or rules can have a large impact on performance and correctness of behavior. If a poorly ordered pipeline caused a list to go rogue, that could affect the reputation of the whole site.

2 1

Anatomy of list ids does not keep with that of urls causes some REST end points to return 404 always
by Ankush Sharma 07 Mar '15

07 Mar '15

Hello everyone, I want to discuss a serious issue regarding mailman architecture in context with bug #1429366 <https://bugs.launchpad.net/mailman/+bug/1429366>. The *hash(#) *is a valid character as far as the local part of the email addresses is concerned as per the email RFCs. So, as the mailing list addresses are email addresses too, we can use # in the list names too. And, in context with mailman it works well. We can create a list with list_id *sam#hashed.host.org <http://hashed.host.org>* for the address *sam#hashed(a)host.org <hashed(a)host.org> *. This works fine. But it makes the *list_id *to contain the hash character and therefore the REST endpoint for retrieving list wise info becomes invalid, i.e : *<api-root>/lists/sam#hashed.host.org <http://hashed.host.org>* Because in an URL the stuff after # is treated as *document starting point* i.e an id identifier or something of a dom element. This is not a valid PATH for the server. Therefore the *falcon wsgi request object* does not contain information of that and the *req.path* simply returns *sam* as the *list_id* ( http://bazaar.launchpad.net/~mailman-coders/mailman/3.0/view/head:/src/mail… ) giving a 404 because there is no any list with list id *sam*. The mailman client works fine, it sends a GET to *<api-root>lists/sam#hashed.host.org <http://hashed.host.org>. * This causes the REST end points which needs *list_id* to return 404 or in worse we can have a list_id clash between ids* sam#XXXXX* and *sam*. Further more if the list_id starts with a # character then the server finds list_id to be *empty string* and therefore we get a KEY ERROR because *fqdn_listname *is not set too. The bug highly effects postorius too. The lists index template at */postorius/lists/ *cannot be rendered as it uses the former REST endpoint and again a 404 is given. And, until we delete this list from the database, we can't do anything except of getting a 404 and KEY ERROR each time. As far as security is concerned, if an another user created a public list using a hash character, then public list indexing would also fail. *Possible fixes:* 1. Put a constraint over the use of this kind of characters, but it's like falling back. 2. Do not derive list ids directly from the list addresses, use some kind of hashing or encoding technique to generate list_ids. Need to change a lot in architecture; :( . 3. Use obscure techniques to retain the hash part as discussed here http://stackoverflow.com/questions/317760/how-to-get-url-hash-from-server-s… . I think this is quite a serious issue in mailman architecture; i.e obtaining list_ids directly from list addresses. I have been trying to fix this bug using some obscure techniques. But as it is related to mailman architecture, I thought it should be worthy to discuss on the mailing list first. Thanks, Ankush Sharma github.com/black-perl

1 0

Re: [Mailman-Developers] Mailman installation error: GSOC 2015
by Rajiv Sharma 07 Mar '15

07 Mar '15

Sorry abhilash, next time I will make sure I include the stack trace along with the commands. Yes, setuptools.py is installed in my virtual environment and I specified the python3.4 path with the -p argument while creating the virtual env to install mailman. Turns out my virtualenv had setuptools for python 2.7 and hence I was getting module already installed message on running apt-get or pip install. The solution to this is either: Sudo apt-get install python3-setuptools Or: Sudo pip install setuptools-3.4.py (or something similar mentioning the version of setup tools) Hope this helps others. Thank you Rajiv Sharma

1 0

Correcting the user_task.html template
by prakhar joshi 07 Mar '15

07 Mar '15

hi, I have been working on the bug https://bugs.launchpad.net/postorius/+bug/1409050 for that I need to ask where are the user_tasks stored so that I can call then while rendering the templates. Thank You!! IRC Name :- _pjoshi Prakhar Joshi DA-IICT,Gandhinagar

1 0

Setting my web-server to run mailman
by Rakesh Verma 07 Mar '15

07 Mar '15

I can't get past the Step 5 in the installation tutorial: http://www.gnu.org/software/mailman/mailman-install/node10.html I am fairly very new to mailman. Any possible help for kind of me?

1 0

Re: [Mailman-Developers] Mailman installation error: GSOC 2015
by NILMADHAB MONDAL 07 Mar '15

07 Mar '15

I am struck in same error... No module named setuptools.py On Sat, Mar 7, 2015 at 11:03 AM, Abhilash Raj <raj.abhilash1(a)gmail.com> wrote: > Hi Rajiv, > > On 6 March 2015 at 16:10, Rajiv Sharma <rajiv.tilakraj.sharma(a)gmail.com> > wrote: > > Hi > > > > I am Rajiv Sharma, pursuing bachelor of IT engineering at SPIT India. I > am > > interested in contributing to the Mailman project in any way I can. I > have > > subscribed to the mailing list and am currently reviewing the mailman > idea > > page for ideas suiting my skill set. I have 2 years experience of > > programming in python and java and have dabbled with JavaScript and C# to > > some extent. > > > > Currently I am trying to install mailman referring to ( > > https://fedorahosted.org/hyperkitty/wiki/DevelopmentSetupGuide). While > > trying to run setup.py in the virtualenv configured with python3.4 (the > > minimum required for mailman) I get the following error: > > No module named setuptools.py > > I checked and its already installed. What am I missing here? Any help > would > > be greatly appreciated. > > Did you check if setuptools is installed in your virtualenv? How did > you create the > virtualenv for python3.4? > > Whenever you refer to any error, its better than you mentioned the > whole traceback > alone with the command that you executed. > > -- > thanks, > Abhilash Raj > _______________________________________________ > 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/nilmadhab1994%40… > > Security Policy: http://wiki.list.org/x/QIA9 > -- Regards, Nil madhab Mondal Web team Head, Kshitij Technology Students Gymkhana Indian Institute of Technology, Kharagpur

1 0

Re: [Mailman-Developers] Mailman installation error: GSOC 2015
by Abhilash Raj 06 Mar '15

06 Mar '15

Hi Rajiv, On 6 March 2015 at 16:10, Rajiv Sharma <rajiv.tilakraj.sharma(a)gmail.com> wrote: > Hi > > I am Rajiv Sharma, pursuing bachelor of IT engineering at SPIT India. I am > interested in contributing to the Mailman project in any way I can. I have > subscribed to the mailing list and am currently reviewing the mailman idea > page for ideas suiting my skill set. I have 2 years experience of > programming in python and java and have dabbled with JavaScript and C# to > some extent. > > Currently I am trying to install mailman referring to ( > https://fedorahosted.org/hyperkitty/wiki/DevelopmentSetupGuide). While > trying to run setup.py in the virtualenv configured with python3.4 (the > minimum required for mailman) I get the following error: > No module named setuptools.py > I checked and its already installed. What am I missing here? Any help would > be greatly appreciated. Did you check if setuptools is installed in your virtualenv? How did you create the virtualenv for python3.4? Whenever you refer to any error, its better than you mentioned the whole traceback alone with the command that you executed. -- thanks, Abhilash Raj

1 0