Mea Culpa! Well one of those silly innocuous changes in 3.2.0.119 that I didn't even think worth mentioning turned out to be a show-stopper that missed the boat. Sender addresses were being truncated to just their local addresses. Nasty -- and I don't quite know how I missed it! It's also been reported that there are at least some systems which still don't have some basic POSIX typedefs that Smail now uses (e.g. SCO OSR5) and unfortunately my naive attempt to deal with such inadequacies didn't work. However the likely fix for this problem will no doubt cause repercussions for other kinds of systems so I want to do a lot more careful testing before I hack in a quick fix for this emergency release. I may be able to make a test patch available in the next couple of days, so watch this spot for further news. A full ChangeLog of all CVS commit messages since the 3.2.0.119 release is included in the distribution for your entertainment and amazement. :-) The best way to find out just the user-visible changes in this or any other release might be to read the CHANGES file from the version you're using now and then read the new CHANGES file and see what's different (an actual "diff", even with '-b', may not work very well because of paragraph re-formatting, but it may give you a head start on where to actually read for the differences). Before installing the new version in a production system you should also first dump the full run-time configuration from and compare that to your existing installation's configuration. (i.e. save the output from "src/smail -v -bP all" and visually compare that to the same output from the existing installation -- if you want to use "diff" you may have to edit one or the other and re-sort both to give them the same format and ordering) If you're upgrading a pre-3.2.0.116 installation you may want to flush your input queue and clean out your error queue before installing. This is because the per-message log format changed in the previous release. The old format won't break anything, though bounce messages from any eventually undeliverable old messages may not include all the right details. As always be very careful to test the new release in your environment before committing to it! Once again this release has been very carefully and extensively tested in a variety of busy environments. It is expected that with only minor fixes and portability adjustments it will very soon become the next new full official release (which will be known as 3.3). However more testing and experience in different environments is always welcome, so if you can possibly install and use this beta release and report your results then that will help us make an even better official release. One thing's for certain, the release process is getting easier (see the mkRelease.sh script), and of course it's always less arduous the less there is that has changed since the last release, so provided there's new code to release, releases of some sort will hopefully be more frequent in the future. Note for users of pkgsrc/ports/openpkg style systems: There's a pkgsrc module for the latest available here: ftp://ftp.weird.com/pub/local/smail/smail-pkgsrc.shar ftp://ftp.planix.com/pub/Smail/smail-pkgsrc.shar It will be udated to include any critical bug fix patches if and when necessary -- i.e. before a proper release including the same fixes is available. Watch the smail3-users list for notices about such updates. As always the ToDo and PROJECTS files list an ever-growing number of things that various people think should be worked on. Patches that eliminate items from these files are always welcome! If you would like to work on any of the bigger projects just send a note to the developers at and let us know so we can help co-ordinate. See the README and the file Smail3-devel for more information. If you need help with configuration issues, or you'd like to discuss some feature or bug, etc., please subscribe to the Smail-3 User's Mailing list . To subscribe to this list send your request to . Note I do not have any direct connection with this list, other than the fact that I maintain the software discussed on it. See the README file for more information. Remember to use the "smailbug" utility to submit patches, change requests, bug reports and other stuff that needs to be recorded so it won't get lost or forgotten! (There's now a symlink installed in the smail_bin_dir to make it easier to access this script, and of course there's a manual page for it too.) For further information please visit the Smail world-wide web page: