From mailman-developers@python.org Thu Mar 7 23:14:02 2002 From: mailman-developers@python.org (Barry A. Warsaw) Date: Thu, 7 Mar 2002 18:14:02 -0500 Subject: [Mailman-Announce] forwarded message from Lisa M. Opus Goldstein Message-ID: <15495.62522.11772.833283@anthem.wooz.org> --3/tf6c9+MU Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit Here's a great way to help with Mailman even if you don't fancy yourself a hacker. Documentation, as always, lags far behind. I'd be happy to work with someone (or perhaps a group of someones), on the technical side, but a good technical writer I'm not. -Barry --3/tf6c9+MU Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Return-Path: Delivered-To: barry@mail.wooz.org Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164]) by mail.wooz.org (Postfix) with ESMTP id 71AB4D35F2 for ; Thu, 7 Mar 2002 17:59:49 -0500 (EST) Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16j6os-00076p-00; Thu, 07 Mar 2002 17:57:06 -0500 Received: from opus by fencepost.gnu.org with local (Exim 3.33 #1 (Debian)) id 16j6OU-0004ML-00; Thu, 07 Mar 2002 17:29:50 -0500 Message-ID: <20020307222950.GH21338@gnu.org> User-Agent: Mutt/1.3.25i Errors-To: gnu-prog-admin@gnu.org Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: GNU Maintainers Announcement List List-Unsubscribe: , List-Archive: From: "Lisa M. Opus Goldstein" Sender: gnu-prog-admin@gnu.org To: gnu-prog@gnu.org Subject: Publishing GNU Documentation Date: Thu, 7 Mar 2002 17:29:50 -0500 X-BeenThere: gnu-prog@gnu.org X-Mailman-Version: 2.0.5 X-Followup-Discussion-To: gnu-prog-discuss@gnu.org Dear Maintainers, I am looking for maintainers to work with me to develop their program's documentation for publication by the Free Software Foundation's publishing department, the GNU Press. As most of you probably know, the Free Software Foundation publishes physical documentation for a few major programs; we have been doing this since we were founded in 1985. Sales of these books are an important source of income for the FSF. It helps pay for our machines, our staff, and by extension helps keep the entire GNU Project going. Accordingly, I was hired to increase the number of titles that the FSF prints and to increase their distribution range. I have created the publishing name "GNU Press", a logo, and redesigned the general appearance of the manual covers. Newer versions of Texinfo now allow inclusion of images, charts, and pictures, so I am hoping to beef up future documentation with such visuals. I am now looking for documentation to publish, and am very interested in actively working with maintainers to develop their documentation for publication by us. Smaller programs' documentation can be bundled with related programs into one book; I would also be very interested in working with some maintainers to help me develop these collections. Additionally, I would like to increase the percentage of documentation that are tutorials rather than simply reference manuals. I believe that teaching people how to use free software is very important, and want to emphasize this through which books I select for publication. If you are interested in participating in any of these projects, or if you have any ideas or suggestions, please contact me. I look forward to hearing from people. Best Regards, Lisa M. Goldstein opus@gnu.org Business Manager Tel 617-542-5942 Ext. 15 Free Software Foundation Fax 617-542-2652 _______________________________________________ GNU Maintainers Announcement List gnu-prog@gnu.org http://mail.gnu.org/mailman/listinfo/gnu-prog --3/tf6c9+MU-- From mailman-developers@python.org Sun Mar 17 05:50:07 2002 From: mailman-developers@python.org (Barry A. Warsaw) Date: Sun, 17 Mar 2002 00:50:07 -0500 Subject: [Mailman-Announce] RELEASED Mailman 2.1 beta 1 Message-ID: <15508.11919.910981.756175@anthem.wooz.org> I've released Mailman 2.1 beta 1; see below for a list of changes since version 2.1 alpha 4. There have been tons of bug fixes, several new languages, and lots of new features. We're finally in feature freeze for Mailman 2.1, although I reserve the right to classify an essential missing feature as a bug . I'd like to get 2.1 final out soon, and I think it's only fair that we eat our own dogfood before offering it to others, so I'll soon be transfering the mailman-* lists to the new version. Please report all bugs to SourceForge. Discussions about version 2.1 are preferred on mailman-developers. I'd also like to announce the mailman-docs@python.org mailing, which indeed is running under 2.1b1. This list will help coordinate the Mailman documentation effort, so if you'd like to contribute please join that list. This is a great way to help us out, even if you aren't into hacking the code. Enjoy, -Barry -------------------- snip snip -------------------- 2.1 beta 1 (16-Mar-2002) In addition to the usual bug fixes, performance improvements, and GUI changes, here are the highlights: - MIME and other message handling o More robustness against badly MIME encapsulated messages: if a MessageParseError is raised during the initial parse, the message can either be discarded or saved in qfiles/bad, depending on the value of the new configuration variable QRUNNER_SAVE_BAD_MESSAGES. o There is a new per-user option that can be used to avoid receipt of extra copies, when a member of the list is also explicitly CC'd. o Always add an RFC 2822 Date: header if missing, since not all MTAs insert one automatically. o The Sender: and Errors-To: headers are no longer added to outgoing messages. o Headers and footers are always added by concatenation, if the message is not MIME and if the list's charset is a superset of us-ascii. - List administration o An `invitation' feature has been added. This is selectable as a radio button on the mass subscribe page. When selected, users are invited to join instead of immediately joined, i.e. they get a confirmation message. o You can now enable and disable list owner notifications for disabled-due-to-bouncing and removal-due-to-bouncing actions. The site config variables DEFAULT_BOUNCE_NOTIFY_OWNER_ON_DISABLE and DEFAULT_BOUNCE_NOTIFY_OWNER_ON_REMOVAL control the default behavior. o List owners can now decide whether they receive unrecognized bounce messages or not (i.e. messages that the bounce processor doesn't recognize). Site admins can set the default value for this flag with the config variable DEFAULT_BOUNCE_UNRECOGNIZED_GOES_TO_LIST_OWNER. o The admindb summary page gives the option of clearing the moderation flag of members who are on quarantined. o The action to take when a moderated member posts to a list is now configurable. The message can either be held, rejected (bounced), or discarded. If the message is rejected, a rejection notice string can be given. o In the General admin page, you can now set the default value for five per-user flags: concealing the user's email address, acknowledging posts sent by the user, copy suppression, not-me-too selection, and the default digest type. Site admins can set the default bit field with the new DEFAULT_NEW_MEMBER_OPTIONS variable. o A new "Emergency brake" feature for turning on moderation of all list postings. This is useful for when flamewars break out, and the list needs a cooling off period. Messages containing an Approved: header with the list owner password are still allowed through, as are messages approved through the admindb interface. o When a moderated message is approved for the list, add an X-Mailman-Approved-At: header which contains the timestamp of the approval action (changed from X-Moderated: with a different format). o Lists can now be converted to using a less error prone mechanism for variable substitution syntax in headers and footers. Instead of %(var)s strings, you'd use $var strings. You must use "bin/withlist -r convert" to enable this. o When moderating held messages, the header text box and the message excerpt text box are now both read-only. o You can't delete the site list through the web. o When creating new lists through the web, you have the option of setting the "default member moderation" flag. - Security and privacy o New feature: banned subscription addresses. Privacy options/subscription rules now have an additional list box which can contain addresses or regular expressions. Subscription requests from any matching address are automatically rejected. o Membership tests which compare message headers against list rosters are now more robust. They now check, by default these header in order: From:, unixfrom, Reply-To:, Sender:. If any match, then the membership test succeeds. o ALLOW_SITE_ADMIN_COOKIES is a new configuration variable which says whether to allow AuthSiteAdmin cookies or not. Normally, when a list administrator logs into a list with the site password, they are issued a cookie that only allows them to do administration for this one list. By setting ALLOW_SITE_ADMIN_COOKIES to 1, the user only needs to authenticate to one list with the site password, and they can administer any mailing list. I'm not sure this feature is wise, so the default value for ALLOW_SITE_ADMIN_COOKIES is 0. o Marc MERLIN's new recipes for secure Linuxes have been updated. o DEFAULT_PRIVATE_ROSTER now defaults to 1. o Passwords are no longer included in the confirmation pages. - Internationalization o With the approval of Tamito KAJIYAMA, the Japanese codes for Python are now included automatically, so you don't need to download and install these separate. It is installed in a Mailman-specific place so it won't affect your larger Python installation. o The configure script will produce a warning if the Chinese codes are not installed. This is not a fatal error. o Russian templates and catalogs have been added. o Finnish templates and catalogs have been added. - Scripts and utilities o New program bin/unshunt to safely move shunted messages back into the appropriate processing queue. o New program bin/inject for sending a plaintext message into the incoming queue from the command line. o New cron script cron/disabled for periodically culling the disabled membership. o bin/list_members has grown some new command line switches for filtering on different criteria (digest mode, disable mode, etc.) o bin/remove_members has grown the --fromall switch. o You can now do a bin/rmlist -a to remove an archive even after the list has been deleted. o bin/update removes the $prefix/Mailman/pythonlib directory. o bin/withlist grows a --all/-a flag so the --run/-r option can be applied to all the mailing lists. Also, interactive mode is now the default if -r isn't used. You don't need to run this script as "python -i bin/withlist" anymore. o There is a new script contrib/majordomo2mailman.pl which should ease the transition from Majordomo to Mailman. - MTA integration o Postfix integration has been made much more robust, but now you have to set POSTFIX_ALIAS_CMD and POSTFIX_MAP_CMD to point to the postalias and postmap commands respectively. o VERP-ish delivery has been made much more efficient by eliminating extra disk copies of messages for each recipient of a VERP delivery. It has also been made more robust in the face of failures during chunk delivery. This required a rewrite of SMTPDirect.py and one casualty of that rewrite was the experimental threaded delivery. It is no longer supported (but /might/ be resurrected if there's enough demand -- or a contributed patch :). o A new site config variable SMTP_MAX_SESSIONS_PER_CONNECTION specifies how many consecutive SMTP sessions will be conducted down the same socket connection. Some MTAs have a limit on this. o Support for VERP-ing confirmation messages. These are less error prone since the Subject: header doesn't need to be retained, and they allow a more user friendly (and i18n'd) Subject: header. VERP_CONFIRM_FORMAT, VERP_CONFIRM_REGEXP, and VERP_CONFIRMATIONS control this feature (only supported for invitation confirmations currently, but will be expanded to the other confirmations). o Several new list-centric addresses have been added: -subscribe and -unsubscribe are synonyms for -join and -leave, respectively. Also -confirm has been added to support VERP'd confirmations. - Archiver o There's now a default page for the Pipermail archive link for when no messages have yet been posted to the list. o Just the mere presence of an X-No-Archive: is enough to inhibit archiving for this message; the value of the header is now ignored. - Configuring, building, installing o Mailman now has a new favicon, donated by Terry Oda. Not all web pages are linked to the favicon yet though. o The add-on email package is now distributed and installed automatically, so you don't need to do this. It is installed in a Mailman-specific place so it won't affect your larger Python installation. o The default value of VERP_REGEXP has changed. o New site configuration variables BADQUEUE_DIR and QRUNNER_SAVE_BAD_MESSAGES which describe where to save messages which are not properly MIME encoded. o configure should be more POSIX-ly conformant. o The Mailman/pythonlib directory has been removed, but a new $prefix/pythonlib directory has been added. o Regression tests are now installed. o The second argument to add_virtual() calls in mm_cfg.py are now optional. o DEFAULT_FIRST_STRIP_REPLY_TO now defaults to 0. o Site administrators can edit the Mailman/Site.py file to customize some filesystem layout policies.