-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Aug 14, 2009, at 06:22 , Alec Mitchell wrote: > It would be very helpful to have these changes in Zope 2.12; > otherwise, Plone 4.0 will be stuck with our unmaintained > SecureMailHost product for yet another release in order to provide > equivalent functionality. Moving to a standard Zope MailHost would be > a big benefit for Plone, and all Zope users will benefit from the > ability to easily send properly formed non-ASCII messages. Andreas may be off on vacation already. IMHO this is a great example where code developed for Plone is pushed to the _correct_ place in the stack to benefit everyone. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkqFCBQACgkQRAx5nvEhZLKJvgCePef8P/XuCgCXV/kXr0KcD3KM HEcAn36wv8S5d2mWCk2/YUciJlVEW4oa =sRi9 -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
