Since we are on this.
I would like to provide support for both turbomail 2 and turbomail 3. And
since there are differences in both configuration and API, is there a way of
getting the version of the installed turbomail package?

Thanks,
Alex Marinescu

On Mon, Jun 22, 2009 at 3:00 AM, Jorge Vargas <[email protected]>wrote:

>
> On Tue, Jun 16, 2009 at 3:10 AM, Felix Schwarz<[email protected]>
> wrote:
> > 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.
> >
> Hello Felix, awesome work on this extension. I just love all the
> features you guys pumped into it. Great work!
>
> I just wanted to point out that Alex from GSOC is on the last bits of
> tgext.registration which uses turbomail for it's confirmation emails,
> and I'm sure we'll give this a really nice 'real world' test with
> that.
>
> > fs
> >
> >
> >
>
> >
>


-- 
Alexandru Marinescu

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to