Mailman 3 March 2005 - Mailman-Developers

PGP and Mailman
by Joost van Baal 22 Jul '05

22 Jul '05

Hi, I will write and publish a patch which integrates PGP signature validation and re-encryption of encrypted posts to mailman. Specs are: - A post will be distributed only if the PGP signature on the post is from one of the list members. - For sending encrypted email, a list member encrypts to the public key of the list. The post will be decrypted and re-encrypted to the public keys of all list members. (Later, the patch will handle RFC 2633 (S/MIME) messages too, next to RFC 2440 (OpenPGP)). I've taken a look at the NAH6 secure list patch #646989 at http://sourceforge.net/tracker/index.php?func=detail&aid=646989&group_id=10… and at Ben Laurie's patch #645297 at http://sourceforge.net/tracker/index.php?func=detail&aid=645297&group_id=10… , but I believe none of these completely implements the listed requirements (although these will help me implementing, of course). I am asking you to take a look at my plan for implementation. Am I on the right track? So, the plan: I think one way to implement it would be to add two modules to GLOBAL_PIPELINE: in front, before SpamDetect, there would be 'PGPCheck'. PGPCheck would check wether the message is encrypted, and, if so, make a temporary decrypted copy in order to verify with which key is was signed. If the message is unencrypted, it would check the signature. It would store this information in new properties of the Mailman Message object. A second new module in GLOBAL_PIPELINE would be 'PGPRecrypt', to be called after CookHeaders' and before 'ToDigest'. This would, if needed, decrypt the message and reencrypt it to all recipients, and would sign it. If for instance a list member erroneously signs a post with a wrong public key, and encrypts the message, this message should be handled carefully. I believe the Hold module should be adapted for this. A copy of the original encrypted message should be kept. The message should be decrypted, signed with the listkey, encrypted to the list moderator key, and sent for acknowledgement. If the moderator chooses to deny the message, the poster should get her original message back. (I guess.) For all PGP handling, I plan to use Frank J. Tobin's GnuPGInterface ( http://py-gnupg.sourceforge.net/ ). I plan to write the patch against current stable Mailman. Any insight to share on this? Thanks! Bye, Joost -- Joost van Baal http://abramowitz.uvt.nl/ Tilburg University j.e.vanbaal(a)uvt.nl The Netherlands

4 12

RE: [Mailman-Developers] Min requirements for running Mailman?
by John.Airey＠rnib.org.uk 31 May '05

31 May '05

> -----Original Message----- > From: mailman-developers-bounces+john.airey=rnib.org.uk(a)python.org > [mailto:mailman-developers-bounces+john.airey=rnib.org.uk@pyth > on.org]On > Behalf Of Tollef Fog Heen > Sent: Monday, 06 September 2004 16:47 > To: mailman-developers(a)python.org > Subject: Re: [Mailman-Developers] Min requirements for > running Mailman? > > > * Nigel Metheringham > > | I'd tend to take this as:- > | * Mailman is a bitch to package > > Not really. It's fairly well-behaved in my experience. It's a > semi-large web application with some requirements, but nothing > unreasonable. > > | * RH have packaged it for a while > | * RH found a good few of the gotchas in packaging Mailman > | * RH have subsequently learnt from their mistakes and recently > | have produced good packages. > | * Other distros may do better, or may yet have to > learn from their > | mistakes :-) > > Mailman has been in Debian since June 1998 (1.0b4), so we've been > working on it for a while as well. I think our packages are of good > quality (far from perfect, but making perfect packages is _a lot_ of > work. ;) > Just to throw my tuppence worth in... I've used mailman since Red Hat 7.2. I found that the version that came with Red Hat 9.0 wouldn't work for me (ie I couldn't upgrade to it) so I stuck with the 7.2 version (2.0.13) till the end of Red Hat 9 support. We are now running the 2.1.5 version that comes with Fedora but running it on Red Hat Enterprise Linux (RHEL). I did however have to recreate all the lists by hand in an overnight shift (what fun that was...) a few days before leaving the country (hence the rush). At that time I didn't know I could export the configuration (Doh!). Red Hat have taken some packages out of RHEL eg arpwatch and mysql-server (although this is in the "extras" channel) even though these are in the source RPM. Mailman is currently not included but might be being put back in to RHEL 4.0. I would like to hope so, as I find 2.1.5 far superior to 2.0.13. -- John Airey, BSc (Jt Hons), CNA, RHCE Internet systems support officer, ITCSD, Royal National Institute of the Blind, Bakewell Road, Peterborough PE2 6XU, Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 John.Airey(a)rnib.org.uk To truly believe in Evolution requires complete faith that life has no meaning. Fortunately there are billions of people who aren't that stupid. -- DISCLAIMER: NOTICE: The information contained in this email and any attachments is confidential and may be privileged. If you are not the intended recipient you should not use, disclose, distribute or copy any of the content of it or of any attachment; you are requested to notify the sender immediately of your receipt of the email and then to delete it and any attachments from your system. RNIB endeavours to ensure that emails and any attachments generated by its staff are free from viruses or other contaminants. However, it cannot accept any responsibility for any such which are transmitted. We therefore recommend you scan all attachments. Please note that the statements and views expressed in this email and any attachments are those of the author and do not necessarily represent those of RNIB. RNIB Registered Charity Number: 226227 Website: http://www.rnib.org.uk

6 11

qmail MTA hook
by Hatuka*nezumi 28 Mar '05

28 Mar '05

Hi Mailman folks. I wrote an MTA hook for qmail to automate creation/deletion of list aliases. This seems to work well on my environment (I tested this on FreeBSD 4.11-STABLE with qmail-1.03 and Mailman 2.1.5 installed from FreeBSD ports): http://sourceforge.net/tracker/index.php?func=detail&aid=1170429&group_id=1… The qmail-to-mailman.py script also detect newly-created lists automatically. But "accept and verify" approach by this script seems not to able to prevent/reduce generating unuseful bounces (so-called "backscatter mails") in its nature. My approach will make their reduction somewhat possible --- combined with a patch for qmail. For details, please read submitted attachment README.qmail. --- nezumi

1 0

Mailman 2.1.6 beta 5 released
by Tokio Kikuchi 23 Mar '05

23 Mar '05

Hi, Sorry for the delay of 2.1.6 but a serious bug was found in the previous beta releases. I put a final beta release before jumping up to the release candidate. The bug is related to 'Privacy -> SPAM filter -> header_filter_rules'. So, I want all of you, who have had brave souls to upgrade 2.1.6 beta and who use this feature, to upgrade again to 2.1.6 beta 5. The tarball is placed at http://mm.tkikuchi.net/mailman-2.1.6b5.tgz # Sorry but it looks like I have not access to the file releases on SF. -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

2 2

postfix deployment scenario needs to be supported
by Derrick Hudson 23 Mar '05

23 Mar '05

Hello! At work I have the following real-world postfix setup: mydomain = redoaksw.com mydestination = local.redoaksw.com # note that this domain doesn't exist virtual_mailbox_domains = redoaksw.com I installed mailman and created the list 'test1(a)redoaksw.com'. So far so good, however the "virtual-mailman" alias map mailman generates does not work. The problem is as follows : 1) the map contains entries such as test1(a)redoaksw.com test1 2) postfix converts "test1(a)redoaksw.com" to "test1" as it should, and then qualifies the address with $mydomain, test1(a)redoaksw.com. (note: this does not actually create a loop) 3) with the address test1(a)redoaksw.com, postfix hands the message to virtual(8) which looks in the virtual_mailbox_maps and correctly reports no such user The solution is simple -- change the map to: test1(a)redoaksw.com test1(a)local.redoaksw.com In this scenario, after the virtual_alias_map rewriting, postfix will hand the message to local(8) which will find the mailman command in $alias_maps. To this end I created the attached patch to mailman. It WorksForMe, but is not yet complete enough to include in the next release. I need some assistance in polishing it for inclusion. The core of the patch is simply to optionally fully-qualify the map value in _addvirtual() in Mailman/MTA/Postfix.py. The parts I need help with are : + What are good names for the parameters (in mm_cfg.py and the mail list object)? I'm not convinced you want to be stuck with the names in my patch forever :-). + How do you handle additional parameters on maillist objects? I noted that __getattr__ fails when the web interface tries to load the current value from a list created before the parameter was added. + Should the default value for 'local_domain' (as it is currently called in my patch) be '' or None? I would generally choose None, but that seems to not play well with the web interface (it shows "None" instead of nothing). + Do I need to do anything with any translation files with regards to the new list parameter? -D -- One OS to rule them all, one OS to find them, One OS to bring them all and in the darkness bind them, In the Land of Redmond, where the Shadows lie. www: http://dman13.dyndns.org/~dman/ jabber: dman(a)dman13.dyndns.org

1 0

Where to post RFEs ?
by MF 23 Mar '05

23 Mar '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I am new to this list. I am the admin of several mailman-based lists and I'd like to submit a RFE to be able to recover admin passwords (NOT subscriber passwords). I haven't seen this submitted as a bug or as an RFE in the Sourceforge site, and I see the RFEs there don't seem to be maintained/assigned. Where should I post this ? Thanks for any pointers :) Cheers, Fabian -----BEGIN PGP SIGNATURE----- iIcEARECAEcFAkJBr3xAGmh0dHA6Ly93d3cuZmFiaWFucm9kcmlndWV6LmNvbS9l bmNyeXB0aW9uL3RoYXd0ZV93b3QucGhwI3BvbGljeQAKCRB9RxNcWvKk1Q9AAJ9B 9i+3n+dMYy3ggIrAs8Mu2JO0EQCcDJUu/hbK/zyyugSqPKSfUkby21U= =gSdj -----END PGP SIGNATURE-----

3 2

Fwd: [SourceForge.net Release] m2f : m2f
by Tobias Eigen 23 Mar '05

23 Mar '05

Dear friends, I thought you might be interested in the fact that mail2forum, the hack that provides phpbb/list gatewaying, has released a new 'stable' version. Haven't tried it yet but will do so once I get back from the nonprofit technology conference in Chicago. Sorry to be missing all the Mailman visitors to DC - hope you have a productive and fruitful time at PyCon DC! Cheers, Tobias Begin forwarded message: > From: "SourceForge.net" <noreply(a)sourceforge.net> > Date: March 22, 2005 3:39:38 PM EST > To: noreply(a)sourceforge.net > Subject: [SourceForge.net Release] m2f : m2f > > Project: mail2forum (m2f) > Package: m2f > Date : 2005-03-22 16:39 > > Project "mail2forum" ('m2f') has released the new version of package > 'm2f'. > You can download it from SourceForge.net by following this link: > <https://sourceforge.net/project/showfiles.php? > group_id=68964&release_id=314792> > or browse Release Notes and ChangeLog by visiting this link: > <https://sourceforge.net/project/shownotes.php?release_id=314792>

1 0

EOL handling in Mailman
by Sylvain Beucler 20 Mar '05

20 Mar '05

Hi, I'm a Savane (gna.org/p/savane) developer, and we noticed that when we send mail with newlines in the \r\n format, Mailman converts them to \n\n. I would like to get your point on what we should do to fix the problem. I had a look at RFC 822; the EOL (end of line) description is not very clear, but it seems that the standard EOL convention is \r\n (CRLF). The issue can be fixed if I make Savane convert all \r\n to \n before to send the notifications, but I am not sure this is very compliant. Anyway I do think this is a bug in Mailman. What do you think we (Mailman and Savane) should do? I posted a detailed bug report at: http://sourceforge.net/tracker/index.php?func=detail&aid=1151439&group_id=1… +id=100103 for more information. The Savane bug report counterpart is at: https://gna.org/bugs/?func=detailitem&item_id=1980 -- Sylvain

5 8

Re: [Savane-dev] Re: [Mailman-Developers] EOL handling in Mailman
by Mark Sapiro 19 Mar '05

19 Mar '05

Mathieu Roy wrote: >Mark Sapiro <msapiro(a)value.net> tapota : >> >> How does Savane inject its messages into the internet mail transport >> system? If it is sending via SMTP, then it MUST send line terminators >> as <CRLF> (or \r\n). > >I do not remember the specifics exactly but Sylvain wrote previously >"we noticed that when we send mail with newlines in the \r\n format, >Mailman converts them to \n\n.". So I assume Savane is sending >newlines in the \r\n format. > > >> If this results in doubling, then the receiving SMTP server is non >> compliant. If it is sending messages via some non SMTP intermediary, >> then it needs to format the messages as expected by the >> intermediary. >> >> Does Savane perhaps pipe outgoing messages directly to the Mailman >> wrapper in the same way that an incoming MTA might do? If so, this is >> _not_ an SMTP transfer and end of line sequences should be those of >> the platform, i.e just \n for Unix. > > >It uses the default mail() function provided by PHP, which would send >the mail via the locally available SMTP server -- maybe through a pipe >but still there's an SMTP server between Savane and mailman. > >The main reason why we have the feeling that the bug comes from >mailman is the fact that only mails redistributed by mailman >mailing-list have this problem -- not copies sent directly to users or >mailing-list managed by other list managers. > >Savane and the SMTP server itself are completely unaffected by this >problem when mailman is not involved. I certainly understand why you would think this given your observations, but I have never seen this problem from Mailman, nor have I seen any report of it other than yours, so I'm inclined to be more skeptical. Here's a suggestion for a test. Presumably, your current MTA that delivers to Mailman has aliases (or equivalents) to hand off incomming mail to Mailman. In particular, the posting address for listname has something like listname(a)example.com: "|/usr/local/mailman/mail/mailman post listname" The path to mailman/mail/mailman may be different, but assuming there is an alias like this, you could change it temporarily to something like listname(a)example.com: "|tee somefile|/usr/local/mailman/mail/mailman post listname" i.e. you could capture a copy in somefile of the incoming message as delivered to Mailman. Then, by comparing this copy both to what you're sending and to what Mailman sends, you should be able to pinpoint where the problem is. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Can you donate a public subversion repository for Pycon sprints?
by Barry Warsaw 18 Mar '05

18 Mar '05

I'm wondering if anybody out there can donate a Subversion repository for use at the upcoming Pycon sprint next week (actually, starting Saturday). I had a machine that I was going to use for this, but it lost its disk over the weekend, and it doesn't look like I'm going to be able to get it back online in time. :( Ideally, someone who will be coming to the sprint would be able to donate a repository, since we'll need to set up access control once we're there and we know who's going to be participating. It will be tough to coordinate this if you're not at the sprint, but if you're willing to be accessible via IM or IRC, we might be able to work around that. I'd like for us to have a separate repository, not tainted by other projects or code. Access can be by http or ssh+svn, whichever you prefer (although the latter requires us to coordinate pubkeys, so that's less desirable). I would send you a dump file of my private repository, and then you'd send me a dump file when the sprints are all done. This will not be the permanent subversion repository for Mailman3. For the long term, we'll either host at SourceForge when they make Subversion available, or I'll host it at my site after I get my machine back online. We just need something we can use for the week of Pycon. If you think you can help out, please respond to me directly. Thanks! -Barry

2 3

list-owner address spam
by Bob Puff＠NLE 17 Mar '05

17 Mar '05

Hi Gang, I've got a list where the <listname>-owner address is getting directly spammed. Any ideas on how to combat this? I don't suppose I can just change it to owner-<listname> and still have mailman pass along admin requests, huh? Bob

2 1

Mailman 3 Sprint at Pycon2005
by Barry Warsaw 17 Mar '05

17 Mar '05

Just a reminder that we're going to do a Mailman 3 sprint again this year at Pycon2005, which starts Saturday. I plan on being there all four sprint days (Sat-Tues) and I hope you will be able to join us. For the meager information on the MM3 sprint see: http://www.python.org/moin/Mailman3Sprint Please sign up on this page if you plan on coming. Remember that the sprint days at Pycon are free; for more information on the conference in general see: http://www.pycon.org I plan on logging into the #mailman channel on irc.freenode.net so if you can't make it and have questions, we'll try to discuss things there, although we might be too busy to pay much attention to irc. I should have more information about the Subversion repository for MM3 later today. -Barry

1 0

Re: [Mailman-Developers] Two patches for site-wide configuration
by J C Lawrence 16 Mar '05

16 Mar '05

On Wed, 16 Mar 2005 13:36:41 +0000 Matthew Newton <mcn4(a)leicester.ac.uk> wrote: I've not reviewd the patches and so am reacting to their descriptions only. > Lets the site administrator stop list owners from changing certain > configuration options. Example is to stop the list owner making > someone else the owner. +1 (this is also useful to me) > Gives a hook into the add member routines that allow the subscribers > address to be changed before it is added to the list. This could be > dangerous if used incorrectly, but is needed for sites that have two > "identical" domain names, such as "leicester.ac.uk" and "le.ac.uk". +1 as a hidden hook. -0 as an exposed feature. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Two patches for site-wide configuration
by Matthew Newton 16 Mar '05

16 Mar '05

Hi! I've written two small patches for Mailman that add the following functionality: site_hide_list_options.patch, sourceforge number 1164457 Lets the site administrator stop list owners from changing certain configuration options. Example is to stop the list owner making someone else the owner. transform_address_hook.patch, sourceforge number 1164464 Gives a hook into the add member routines that allow the subscribers address to be changed before it is added to the list. This could be dangerous if used incorrectly, but is needed for sites that have two "identical" domain names, such as "leicester.ac.uk" and "le.ac.uk". Any comments on these patches would be most appreciated! Is there a better way of doing these things, or are there any improvements that could be made to the patches? Patches apply to 2.1.5. Thanks! Matthew -- Matthew Newton <mcn4(a)le.ac.uk> UNIX and e-mail Systems Administrator, Network Support Section, Computer Centre, University of Leicester, Leicester LE1 7RH, United Kingdom

1 0

bug in ListAdmin._UpdateRecords in 2.1.5 - 2.1.6b4?
by Zoran Dzelajlija 15 Mar '05

15 Mar '05

Hello. I have been trying to migrate from 2.0.13 to 2.1.5 a few lists at a time, and run 2.0 and 2.1 in parallel. We have a lot of pending requests around, and we would not like to lose them. Luckily, it looks like almost everything is handled in bin/update, although some things require special attention, like pending_subscriptions.db (haven't tried yet, but it looks like it should be enough to copy it over to the Mailman 2.1 installation each time a list is migrated, and run bin/update or the relevant portion thereof). Most other stuff is done on a per-list basis, like held messages. class ListAdmin has an sort-of-private function _UpdateRecords, used in bin/update to upgrade from 2.0-style request.db which holds the held messages metadata. It writes the entries to the new database like this: if op == SUBSCRIPTION: [munge...] # Here's the new layout self.__db[id] = when, addr, fullname, passwd, digest, lang However, other code uses it like: type, data = self.__db[id] Seems like the correct way should be something like self.__db[id] = TYPE, (when, addr, fullname, passwd, digest, lang) I'v made a script to mv files and directories from 2.0 to 2.1 installation, fix the aliases, and do stuff withlist, _UpdateRecords() among other. After this, some of the migrated lists would have munged requests without a request type. AFAICT this would happen on a regular 2.0.x -> 2.1.5 upgrade with bin/update too. So here's a patch for 2.1.5 which includes crude heuristics to guess the forgotten request type, it can be used in withlist to fix the damage, or in bin/update. I'm not sure if this is adequate to put in the main tree. It applies to 2.1.6b4 too, but I've not tested yet if it works. Should I file a bug report at sourceforge? Regards, Zoran Index: ListAdmin.py =================================================================== RCS file: /var/lib/cvs/mailman-conf/ListAdmin.py,v retrieving revision 1.1 retrieving revision 1.3 diff -u -r1.1 -r1.3 --- ListAdmin.py 7 Sep 2004 02:48:50 -0000 1.1 +++ ListAdmin.py 7 Sep 2004 03:33:17 -0000 1.3 @@ -530,7 +530,19 @@ except IOError, e: if e.errno <> errno.ENOENT: raise self.__db = {} - for id, (op, info) in self.__db.items(): + for id, rest in self.__db.items(): + if len(rest) == 2: + op, info = rest + # repair junk from 2.1.5 + elif len(rest) == 6: + op = SUBSCRIPTION + if len(rest[5]) > 10 and rest[2] != '': + op = HELDMSG + self.__db[id] = op, rest + continue + else: + assert len(rest) == 2, 'Found broken database' + continue if op == SUBSCRIPTION: if len(info) == 4: # pre-2.1a2 compatibility @@ -545,7 +557,7 @@ assert len(info) == 6, 'Unknown subscription record layout' continue # Here's the new layout - self.__db[id] = when, addr, fullname, passwd, digest, lang + self.__db[id] = op, (when, addr, fullname, passwd, digest, lang) elif op == HELDMSG: if len(info) == 5: when, sender, subject, reason, text = info @@ -554,7 +566,7 @@ assert len(info) == 6, 'Unknown held msg record layout' continue # Here's the new layout - self.__db[id] = when, sender, subject, reason, text, msgdata + self.__db[id] = op, (when, sender, subject, reason, text, msgdata) # All done self.__closedb()

1 0

middleware requirements contribution
by John-Paul Robinson 11 Mar '05

11 Mar '05

Hello Mailman Developers, Some of you may be aware of an Internet2 sponsored and NSF funded effort to improve the integration of popular open source mailing list software with emerging middleware technologies for identity management and authorization. http://middleware.internet2.edu/mlist The mlist working group of Internet2 has been gathering information related to mailing list software needs of higher education and working on integration scenarios for mailing list software related to these needs. As part of this effort, we have put together much of the knowledge we have gathered over the past year into a how-to guide for mailing list developers. http://webapp.lab.ac.uab.edu/wiki/mlist/index.php/HomePage Our initial version of this guide has been put together over the past few weeks in the hopes that it is useful to the Mailman developers in light of the upcoming Mailman developer sprint at PyCon2005. We hope that it will contribute positively to the development requirements of the next major release of Mailman. As I mentioned, this is our initial version of the document. We have put it online as a wiki in order to solicit feedback on the utility of the information and to allow people to easily contribute to this discussion. Please let us know if you find this information useful or if there are areas you feel should be improved. Our goal is to provide requirements guidance to mailing list system developers to help promote the changing needs of the higher education community. We feel that these same requirements represent the future needs of many organizations that use Mailman and that by addressing the general requirements Mailman will continue to be a popular and adaptable part of future mailing list systems. Thanks for your time and let me know if you have any questions or requests. Thanks, ~jpr

1 0

Appropriate text for private archive login
by Mark Sapiro 11 Mar '05

11 Mar '05

Much of the template templates/en/private.html is based on (copied from) the template templates/en/admlogin.html. Thus, the language about cookies is not appropriate for this function. I have submitted a patch with suggested changes to the english template at https://sourceforge.net/tracker/index.php?func=detail&aid=1161505&group_id=… -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

XHTML Compliant Web UI 2.1.6b4 Patch
by Bryan Carbonnell 09 Mar '05

09 Mar '05

I have just uploaded a patch that will make the web UI for MM 2.1.6b4 XHTML 1 strict compliant. Well, the start of a patch. Currently only the listinfo pages are xhtml 1 compliant and some minor CSS formating ability. As time goes by, I'm going to update the patch to include more of the UI pages. Since this is my first atempt at something like this I thought I'd post it incrementally in case anyone finds something terrible wrong with what I'm doing :) It it patch 1160353 in the Sourceforge Mailman patch repository. http://sourceforge.net/tracker/index.php?func=detail&aid=1160353&group _id=103&atid=300103 If anyone has any feedback on it, I'd love to hear it. -- Bryan Carbonnell - carbonnb(a)sympatico.ca "When they put 'unknown' at the end of a quote, that means they probably don't know how to spell 'anonymous'." ~Author Unknown

1 0

Fwd: <incom> Design for Civil Society / Technology and Social Action
by Tobias Eigen 07 Mar '05

07 Mar '05

Hi all, The link below might be of interest in the context of usability discussions we've been having. Best wishes, Tobias Begin forwarded message: > From: Maja van der Velden <maja(a)xs4all.nl> > Date: March 4, 2005 10:11:01 AM EST > To: Maja van der Velden <maja(a)xs4all.nl> > Cc: Subject: <incom> Design for Civil Society / Technology and Social > Action > > FYI, some work I am participating in: > > A special issue of Interacting with Computers - Volume 17, Issue 1, > Pages 1-120 (January 2005) - on Design for Civil Society, edited by > Steve Walker and Andy Dearden, is available full text online as a > complementary issue. Yu can read the articles online, download them or > send them in pdf format. > > A follow-up on this is a project called Technology and Social Action > (see http://www.technologyandsocialaction.org ): "a project to foster > dialogue and collaboration between activists in social movements, > voluntary and community organisations and technology designers. We are > committed to supporting communities of practice exploring effective > ways of using technology to support social action, and of ensuring > that technological innovation responds to social priorities. > > Greetings, Maja > > The (very unhandy) link to the Design for Civil Society issue is: > http://www.sciencedirect.com/science? > _ob=IssueURL&_tockey=%23TOC%235644%232005%23999829998%23549345%23FLA%23 > Volume_17,_Issue_1,_Pages_1 > -120_(January_2005)%2BMDesign_for_Civil_Society%2BMEdited_by_S._Walker_ > and_A._Dearden&_auth=y&view=c&_acct=C000050221&_version=1&_urlVersion=0 > &_userid=10&md5=59c069dfff5e2e729975cf03dfead78b > > It has the following articles: > > 1. Inside Front Cover > Page CO2 > > 2. Designing for civil society • EDITORIAL > Pages 1-8 > Steve Walker and Andy Dearden > > 3. Participating in civil society: the case of networked communities > • ARTICLE > Pages 9-33 > Andrea Kavanaugh, John M. Carroll, Mary Beth Rosson, Debbie D. Reese > and Than T. Zin > > 4. Net neighbours: adapting HCI methods to cross the digital divide • > ARTICLE > Pages 35-56 > Mark Blythe and Andrew Monk > > 5. Fairtrade.com versus Fairtrade.org—how Fairtrade organisations use > the Internet • ARTICLE > Pages 57-83 > Dorothea Kleine > > 6. Online design for bilingual civil society: a Welsh perspective • > ARTICLE > Pages 85-104 > Daniel Cunliffe and Dilwyn Roberts-Young > > 7. Programming for cognitive justice: Towards an ethical framework for > democratic code • ARTICLE > Pages 105-120 > Maja van der Velden > > > Maja van der Velden > Oslo, Norway > http://www.globalagenda.org > http://blogger.xs4all.nl/ > maja_______________________________________________ > incom-l mailing list > incom-l(a)incommunicado.info > http://mail.kein.org/mailman/listinfo/incom-l > -- Tobias Eigen Executive Director Kabissa - Space for Change in Africa http://www.kabissa.org * Kabissa's vision is for a socially, economically, politically, and environmentally vibrant Africa, supported by a strong network of effective civil society organizations. *

1 0

Re: [Mailman-Developers] Postfix.py extension for virtual_domain management
by clif 06 Mar '05

06 Mar '05

Hi Mike, I've also wished mailman handled Virtual lists better. PostfixVirtual.py Works great, and I also tried removeing the name change restriction in General.py: vi /usr/lib/mailman/Mailman/Gui/General.py /real_name # Lets try this just for fun... if property == 'real_name_NOT' and \ I did some quick testing and found most of the obvious references to com.foo.test became test without any problems. Though the URLs and some other text still refers to it by the "correct" name. Anyway you mentioned in your post that you had customized mailman in other ways. Do you feel like publishing them as well? Thanks, Clif

2 3

Suggestion on Spam
by Rui Correia 05 Mar '05

05 Mar '05

Hi All Would it be feasible to create a feature that would automate a search for a pre-agreed phrase set by list owner typed on each individual email posted to a list? An email would then begin with the pre-agreed phrase, eg: "We all love red wine", which Mailman would have been programmed to recognise. A "reply to" post would be exempt from such. Anyone initiating a new string and forgetting to include the key-phrase would receive an auto-response notification to resend including key-phrase. This would in most cases replace the "your posting is being held for approval", as most lists have open posting for their members. It would be a matter of days before everybody got used to including the key-phrase in their postings - to make life easier, members can even include it in their signature. Rui ________________________________________________ Rui Correia Advocacy, Media and Language Consultant 36 Finch St, Ontdekkers Park, Roodepoort, Johannesburg, South Africa Tel/ Fax (+27-11) 766-4336 Cell (+27) (0) 83-368-1214

4 3

Hashing member passwords in config.pck
by Barry Warsaw 05 Mar '05

05 Mar '05

I think CAN-2005-0202 gives us the opportunity to finally implement what we have long considered an embarrassing exposure in Mailman's config.pck databases. Member passwords are kept in this database in the clear. The obvious fix is to hash member passwords and keep only the hash in the database. We haven't changed this before now for two reasons: 1. We would have to regenerate all member passwords, which is an administrative burden. We might also need to implement checks to see if the passwords were cleartext or hashed and do the password comparison accordingly. 2. This breaks all password reminders. To fully address CAN-2005-0202 we're recommending sites regenerate their member passwords anyway, so this gives us an opening to fix this properly. And we have a better internal password generator now too. As for #2, well, I think most people hate those password reminders anyway, and we've decided that they are going away for MM3. I don't think many people would shed too many tears if we killed off monthly password reminders for 2.1.6. Doing that would also eliminate the requirement for the site list, since its primary purpose is to function as the sender of the reminder messages. To do this for 2.1.6, we'd have to change the "Email My Password To Me" feature in the options page and in the member login page. These would have to become a "create a new password for me" feature. Also, crontab.in should not call mailpasswds anymore, or that script should turn into a simple "here's the lists you are on" reminder, without the password information in it. This will require i18n updates too. The downside to doing this now is that it's more coding work for 2.1.6 and I'd like to get the new version out asap. Still, this seems like an opportunity that we shouldn't lightly dismiss. What do you all think? Is anybody willing to take a crack at a patch for this? -Barry

28 91

Mailman 2.1.6b4
by Barry Warsaw 04 Mar '05

04 Mar '05

Okay, I've pushed the 2.1.6b4 tarball out to SourceForge (now that file uploads are working again ;). I will likely be off-line until Tuesday. -Barry

4 3

Re: [Mailman-Developers] PGP and Mailman
by J C Lawrence 02 Mar '05

02 Mar '05

On Wed, 2 Mar 2005 12:37:41 +0100 Brad Knowles <brad(a)stop.mail-abuse.org> wrote: > True. A session key would be encrypted to each key id, so the key ids > would be visible. However, subscriber information is not too hard to > get from Mailman even when it's supposedly limited to being available > only to the admin, so I think there may be bigger fish to fry > elsewhere. There's also the difference between using a key for a list subscription which is publicly distributed on key servers, and a special-purpose key that you don't otherwise distribute and use for smaller more privacy critical cases. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

[Mailman-Developers] Using an external system to generate passwords, etc..
by Mark Tilden 01 Mar '05

01 Mar '05

I'm wondering if anybody has integrated Mailman's user name/password system with external systems that generate the user names and passwords. I've searched the archives and found a few references to using MySQL or LDAP, but nothing concrete enough to tell if it's actually implemented somewhere. My goal is to integrate Mailman and it's admin pages into a larger site that already has a system of creating user names and passwords (using email addresses as user names). I run several smaller Mailman lists, and we're trying to integrate one of these lists with the existing site. If anybody has any pointers, I'd appreciate it. I've been running Mailman for a couple of years, but haven't dug deeply into the code (and hope to avoid having to...). Thanks! Mark

2 1