[Mailman-Developers] (no subject)
Hi all, While i create new list with mailman rest api i receive this error, sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Traceback (most recent call last): File /usr/lib/python2.7/wsgiref/handlers.py, line 85, in run self.result = application(self.environ, self.start_response) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/database/transaction.py, line 60, in wrapper rtn = function(*args, **kws) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/rest/wsgiapp.py, line 59, in __call__ environ, start_response) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/app.py, line 18, in __call__ response = self.get_response(request, resource_or_response) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/app.py, line 65, in get_response resource_or_response = resource_or_response(request) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/resource.py, line 212, in __call__ return _dispatch(request, match, lambda r: callable(self, r)) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/resource.py, line 243, in _dispatch response = func(request) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/resource.py, line 212, in lambda return _dispatch(request, match, lambda r: callable(self, r)) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/rest/lists.py, line 203, in create mlist = create_list(**validator(request)) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/app/lifecycle.py, line 84, in create_list call_name(config.mta.incoming).create(mlist) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/mta/postfix.py, line 73, in create self.regenerate() File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/mta/postfix.py, line 108, in regenerate raise RuntimeError(NL.join(errors)) RuntimeError: command failure: /usr/sbin/postmap /home/kevin/var/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /home/kevin/var/data/postfix_domains, 127, Key has expired sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Traceback (most recent call last): File /usr/lib/python2.7/wsgiref/handlers.py, line 85, in run self.result = application(self.environ, self.start_response) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/database/transaction.py, line 60, in wrapper rtn = function(*args, **kws) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/rest/wsgiapp.py, line 59, in __call__ environ, start_response) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/app.py, line 18, in __call__ response = self.get_response(request, resource_or_response) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/app.py, line 65, in get_response resource_or_response = resource_or_response(request) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/resource.py, line 212, in __call__ return _dispatch(request, match, lambda r: callable(self, r)) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/resource.py, line 243, in _dispatch response = func(request) File /usr/local/lib/python2.7/dist-packages/restish-0.12.1-py2.7.egg/restish/resource.py, line 212, in lambda return _dispatch(request, match, lambda r: callable(self, r)) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/rest/lists.py, line 203, in create mlist = create_list(**validator(request)) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/app/lifecycle.py, line 84, in create_list call_name(config.mta.incoming).create(mlist) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/mta/postfix.py, line 73, in create self.regenerate() File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/mta/postfix.py, line 108, in regenerate raise RuntimeError(NL.join(errors)) RuntimeError: command failure: /usr/sbin/postmap /home/kevin/var/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /home/kevin/var/data/postfix_domains, 127, Key has expired sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Traceback (most recent call last): File /usr/lib/python2.7/wsgiref/handlers.py, line 85, in run self.result = application(self.environ, self.start_response) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/database/transaction.py, line 60, in wrapper rtn = function(*args, **kws) File /usr/local/lib/python2.7/dist-packages/mailman-3.0.0b3-py2.7.egg/mailman/rest/wsgiapp.py, line 59,
Re: [Mailman-Developers] (no subject)
On Thu, 6 Feb 2014, Kevin Ratnasekera wrote: While i create new list with mailman rest api i receive this error, sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Looks like Mailman is expecting to find a Postfix installation in the standard place. Are you using Postfix as your mail transport agent? If so, where is your postmap executable installed? If not, have you configured Mailman for the MTA you *are* using? Geoff. ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] (no subject)
On Feb 06, 2014, at 01:49 PM, Geoff Shang wrote: On Thu, 6 Feb 2014, Kevin Ratnasekera wrote: While i create new list with mailman rest api i receive this error, sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Looks like Mailman is expecting to find a Postfix installation in the standard place. Are you using Postfix as your mail transport agent? If so, where is your postmap executable installed? If not, have you configured Mailman for the MTA you *are* using? If you're using Postfix but the postmap executable is in a different location, add a postfix.cfg file containing this to your etc directory: [postfix] postmap_command: /path/to/postmap Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] (no subject)
Thanks all got it fixed :) regards Kevin On Thu, Feb 6, 2014 at 8:12 PM, Barry Warsaw ba...@list.org wrote: On Feb 06, 2014, at 01:49 PM, Geoff Shang wrote: On Thu, 6 Feb 2014, Kevin Ratnasekera wrote: While i create new list with mailman rest api i receive this error, sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Looks like Mailman is expecting to find a Postfix installation in the standard place. Are you using Postfix as your mail transport agent? If so, where is your postmap executable installed? If not, have you configured Mailman for the MTA you *are* using? If you're using Postfix but the postmap executable is in a different location, add a postfix.cfg file containing this to your etc directory: [postfix] postmap_command: /path/to/postmap Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@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/djkevincr1989%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@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
[Mailman-Developers] Updating the template HTML and including CSS?
Hi everyone, I have a little itch with Mailman and would like to know the best way to scratch it for everyone. I've looked into the current bzr version and the templates are still very old HTML, using hard-coded styles and, in some places, incorrect markup and unclosed tags (I can dig some examples up if necessary.) I can't come up with a proper reason to keep using outdated HTML, but I'm happy to be corrected if there is a specific reason to keep it so. I've also found an attempt to bring the markup up to date in this bug report with an attached patch from 4 years ago; https://bugs.launchpad.net/mailman/+bug/398030 However, the patch is pretty large and incorporating it into the codebase would be non-trivial (plus it's certainly outdated), so I understand why it's been sitting there forgotten. I'd like to take up the task of reviewing the patch and create a branch where changes would be properly documented in commit logs, following the Mailman development guidelines, so that it could be easily merged into the main branch. I would only like to ask the Mailman devs if this would be a desirable goal, since it only makes sense for me to work on this if there's openness for this to be included in the main branch. I've searched for previous instances of this discussion, so please excuse me if I missed any existing efforts on this front, and would appreciate any kind of pointers with regards to updating HTML and including CSS in Mailman templates. Thank you! :r ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] GSoC 2014 ideas list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, some project suggestions for this year's GSoC: 1. A continuous integration tool for the Mailman suite. Mailman 3 is based on 4 different packages which are developed somewhat independently: The Mailman core, Postorius, Hyperkitty and mailman.client. It's not always guaranteed that these components still play nicely with each other after a new commit. It would be very useful to have some mechanism that runs a series of tests to make sure everything's not fundamentally breaking. This could be everything from a command line based tool to a full-fledged integration into something like Jenkins. 2. A responsive ui for Postorius In 2014 a web ui should be equally usable on a desktop computer as on a phone. Nowadays the CSS mechanisms needed to use the same HTML for different devices are pretty well supported across browsers. I'd love to be able to use Postorius (and Hyperkitty!) on my phone without constant zooming. 3. Various Python 3 ports The goal for the Mailman core is to support Python 3 in the near future, so Postorius/Hyperkitty/mailman.client might be ported as well (probably supporting both 2.6+ *and* 3.3+ in order to not frustrate folks who use additional Django apps that haven't been ported yet). Not sure if this should be one single GSoC project or one for each package... 4. Postorius: Improve the test suite Currently Postorius' test suite consists mostly of unit-tests, using nose as the test runner. The test coverage could definitely be improved. It might also be nice to add some doctests as a developer resource. This project could also feature some interface/navigation testing, using Selenium, casperJS or similar. In addition to these there are a number of project ideas that didn't get picked last year: http://wiki.list.org/display/DEV/Google+Summer+of+Code+2013#GoogleSummerofCode2013-ProjectIdeas My personal favourites: - - Migration Scripts from MM 2.1 to MM 3 - - Design interface themes for specific types of list - - Enhance List Style Capabilities - - Full anonymization (obfuscating sender addresses) - - No-logging mode - - Log monitor Any comments or (even better) more ideas? I am planning to complete the ideas page by the end of the week (probably over the weekend), so I can submit our GSoC application on Monday or Tuesday... Of course we can theoretically add more after the deadline, but since the ideas page is the most important ingredient of the application, it would be *a lot* better if we had all projects on it before Friday 14. Cheers Florian On 01/09/2014 08:28 AM, Terri Oda wrote: I've had prospective Google Summer of Code students emailing me since, uh, September or so... so I guess it's time to talk ideas! I've set up a wiki page, as usual: http://wiki.list.org/display/DEV/Google+Summer+of+Code+2014 But let's start with here: what small projects would you like to see us sponsor this year? I think we'll need to be more selective about the final list, but let's start with some brainstorming! ___ Mailman-Developers mailing list Mailman-Developers@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/flo.fuchs%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS89A5AAoJEEceGbPdavl7kYAIAJFnVk3GwHVOJ1/xEQQogGd7 ted1MsA4QoDPPcqEDASN0SxpsYFIFLPHpPA9J58783pQN0bQ85iQphd3GyE5Ihg9 LLlJgkrmSyS2u5dX70RSSfN2r56wZ81aqVygWVPZA+xoNOnxossJqe1aK5rPrxnH xIyKtIfsn80Yi876SCB81sAN2kYS7A6NXJ7kF+krpMRW+c5rkkrnLSRPcH0PMIhs P423f+Q0IVTM+8+vK2MYdmCOCWc01ZrvNGbIBl4Q9t0kBtQ/3hHfjYlpaiSq1x6n InTbkgiX0Sd6lq5at3GyK/Ud5WC58OnTQEXm2qjkPHNGJPqF31hYKc97CChIveY= =1amL -END PGP SIGNATURE- ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] GSoC 2014 ideas list
On 01/09/2014 02:28 AM, Terri Oda wrote: I've had prospective Google Summer of Code students emailing me since, uh, September or so... so I guess it's time to talk ideas! I've set up a wiki page, as usual: http://wiki.list.org/display/DEV/Google+Summer+of+Code+2014 But let's start with here: what small projects would you like to see us sponsor this year? I think we'll need to be more selective about the final list, but let's start with some brainstorming! Do you know if Summer of Code students can do interaction design / UX stuff? Because I'd be willing to mentor for that. ~m ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] Updating the template HTML and including CSS?
On 02/06/2014 04:18 AM, Ricardo Lafuente wrote: I've also found an attempt to bring the markup up to date in this bug report with an attached patch from 4 years ago; https://bugs.launchpad.net/mailman/+bug/398030 However, the patch is pretty large and incorporating it into the codebase would be non-trivial (plus it's certainly outdated), so I understand why it's been sitting there forgotten. I'd like to take up the task of reviewing the patch and create a branch where changes would be properly documented in commit logs, following the Mailman development guidelines, so that it could be easily merged into the main branch. I would only like to ask the Mailman devs if this would be a desirable goal, since it only makes sense for me to work on this if there's openness for this to be included in the main branch. The main development focus for Mailman is Mailman 3/Postorius/Hyperkitty. Postorius is a totally new web UI for Mailman. Mailman 2.1 is at the end of its life cycle, although I continue to provide support, fix bugs and even implement new things. The main obstacles to merging the branch you propose is i18n considerations and impacts on existing users. I confess, I haven't really looked at the patch at https://bugs.launchpad.net/mailman/+bug/398030, but if it can be implemented with full i18n support and transparently to existing users/lists, I would certainly consider merging it. However, keep in mind that anything that works to extend the life of Mailman 2.1 is contrary to our goal of getting everyone on Mailman 3 as soon as possible. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] GSoC 2014 ideas list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/06/2014 07:22 PM, Máirín Duffy wrote: Do you know if Summer of Code students can do interaction design / UX stuff? Because I'd be willing to mentor for that. Oh, that would be great! I'm not a 100% sure about the exact criteria. I vaguely remember a discussion on the GSoC mentors list about CSS which eventually turned into an argument about Turing completeness and what constitutes real programming. So I don't know if a pure design/CSS project would qualify. But I think any UX work on Postorius/Hyperkitty will involve at least a little bit of Django and/or JavaScript work. I'll scan the mentors list archives if I can find something - or ask that question again, just to be on the save side. Florian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS89zRAAoJEEceGbPdavl7vrAH/0rru3C6TtS5RP66h3onx6te v+9ODFthhH4X4igbElIaI5THa2p8W9d3ukabN9JtvUPhdSSCzWxCn4JsFNJhhqa7 nxQ36cTeR/QPXs49MBBMVTtQPXN7vAC11OgIgOLmkYRrI0hFOQnOOliXflYy7ho6 RSxzHPpsUw48ASYryODfWOSBE1F0yk+fc4p4fWoQZsvGnR56U3y7PV39FLJdWAvq vdXTqHzX/rzHJyd1njfLO36SFQ0p+rDQNHZXrQJ/Ul5r3le2m1yrxD65WIjn1HAb frFD4V8RI+CHAP+PSbpJ3E8hBi5/CUVUKqnoZD9ShZ948wpQEIxYRIzXKUImPcE= =auR2 -END PGP SIGNATURE- ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] GSoC 2014 ideas list
Le 06/02/14 19:22, Máirín Duffy a écrit : On 01/09/2014 02:28 AM, Terri Oda wrote: I've had prospective Google Summer of Code students emailing me since, uh, September or so... so I guess it's time to talk ideas! I've set up a wiki page, as usual: http://wiki.list.org/display/DEV/Google+Summer+of+Code+2014 But let's start with here: what small projects would you like to see us sponsor this year? I think we'll need to be more selective about the final list, but let's start with some brainstorming! Do you know if Summer of Code students can do interaction design / UX stuff? Because I'd be willing to mentor for that. And what about this idea (already posted i think) about : - plug-in support for hyperkitty ( for plugs to other tools like redmine, etherpad, poll systems, and as an opening for semantic integration (index/search) ) ~m ___ Mailman-Developers mailing list Mailman-Developers@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/nicolas%40karageuzian.com Security Policy: http://wiki.list.org/x/QIA9 signature.asc Description: OpenPGP digital signature ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] GSoC 2014 ideas list
On Feb 06, 2014, at 07:11 PM, Florian Fuchs wrote: 1. A continuous integration tool for the Mailman suite. Very much +1. I like the development model where we have a gatekeeper against merges to the trunk better than post-merge buildbot-style validations. That way, we know that only merges that pass the test suite will land on trunk, so it should always be releaseable. The downside to that is that the gatekeeper is usually one exact setup (e.g. a specific version of the OS, a specific choice for backend database, a specific Python version, etc.) buildbots/jenkins, etc. then augment that to make sure that we haven't regressed on supporting PostgreSQL, MySQL, PythonX.Y, etc. 2. A responsive ui for Postorius Very much +1. Another thought would be to support an app that you could install on Android or iOS (or Ubuntu Touch? :) to more directly control a Postorius server. 3. Various Python 3 ports Very much +1. More on this later. 4. Postorius: Improve the test suite +1 - - Migration Scripts from MM 2.1 to MM 3 abompard has a merge proposal that I've been slowly working through here. - - Design interface themes for specific types of list Styles, yes, this would be nice and very doable for GSoC. - - Enhance List Style Capabilities - - Full anonymization (obfuscating sender addresses) - - No-logging mode - - Log monitor Any comments or (even better) more ideas? I am planning to complete the ideas page by the end of the week (probably over the weekend), so I can submit our GSoC application on Monday or Tuesday... Of course we can theoretically add more after the deadline, but since the ideas page is the most important ingredient of the application, it would be *a lot* better if we had all projects on it before Friday 14. Thanks for doing this Florian and to Terri for getting the ball rolling. -Barry signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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
Re: [Mailman-Developers] GSoC 2014 ideas list
Hi, Máirín! Good to see you here! Máirín Duffy writes: Do you know if Summer of Code students can do interaction design / UX stuff? Because I'd be willing to mentor for that. I'm not sure what you mean by design. Something like graphic design via CSS alone doesn't fly. It has to come with an implementation that is aimed to be of high enough quality to be integrated. If the project misses implementation quality by end of summer, nobody's going to complain if we pass the student based on reasonable effort and significant progress. But what Google is paying for is the time and effort spent on designing and writing code to implement processes, not the UX design. Eg, doing CSS work that makes a screen pretty and easy to hide uninteresting information and changes simple text fields to more structured widgets (eg for date input) is out. Writing JavaScript that sanity-checks user input is OK. If what you mean is the kind of stuff that is involved in Postorius and Shanu Salunke's Mailman Interface (a GSoC project for Systers last year), yes, that passes muster. ___ Mailman-Developers mailing list Mailman-Developers@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
