Hi,

yesterday I published the first release candidate of TurboMail 3.0. As the status 'release candidate' implies this release *should* be stable enough to be used by normal users.

TurboMail 3.0b2 got quite some testing by various users and we found some
interesting bugs during the process. Now we need even more real-world testing to get a rock-solid final release!

I uploaded the files to http://www.schwarz.eu/opensource/misc/2009/turbomail/
until Alice can put them on the TurboMail webspace.

Changes since beta2:
- 'mail.smtp.count' was renamed to 'mail.smtp.max_messages_per_connection' to
  reflect the semantics better, default was lowered to 1 to prevent log
  warnings about disconnects
- 'mail.tries' was renamed to 'mail.message.nr_retries'
- Reworked UTF8qp extension which is now only necessary for backwards
  compatibility. We have a separate, less intrusive 'UTF8qp' charset which can
  be used for quoted printable encoding without the extension.
- SMTPTransport always sends ehlo (report with patch by akalias)
- SMTPTransport is more robust in case of connection drops (reported+initial
  patch by Ethan Frey)
- Fixed a couple of bugs in the Pylons adapter (reported+diagnosed by little
  wiki)
- Configuration option for message encoding is now 'mail.message.encoding'
  (was 'message.encoding') to provide a consistent naming (reported by Domen
  Kožar)
- HTML documentation is included in the release tarballs


Roadmap to 3.0:
- Give that release candidate 2-3 weeks of field testing
- release new versions if serious bugs are found
- write release notes for 3.0
- Remove all pointers to the old svn in trac
- Rework trac pages so that they reflect the current status
- Find a way to push updated docs to the website.

fs


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to