Re: [Framework-Team] Re: [Zope-dev] MailHost Improvements
-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- ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: MailHost Improvements
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 15, 2009, at 19:03 , Alec Mitchell wrote: There's one additional significant change to Zope behavior here that I forgot to mention. The current implementation sets the python default email transfer and header encoding for 'utf-8' messages to 'quoted-printable', it normally defaults to 'base64'. This is essentially a cosmetic change and makes reading and debugging email messages much more straightforward. It also makes encoded mail less likely to be caught by SPAM filters (some of which dislike base64 mail on principle). At present this change causes one test in CMFDefault to fail, which I'm happy to fix. But it's also not a problem to just remove the line that sets the new 'utf-8' encoding, though I think it dpes have some important advantages. I'm not an expert, but if quoted-printable is better practice then it should be used and the CMF test should be changed accordingly. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkqHAXIACgkQRAx5nvEhZLKBTQCfcHjWwaRkbRsDo57+bdK2hbsZ CkgAmwcsUFuH0rXBVvimieyeA+XBJ4aG =NHxE -END PGP SIGNATURE- ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/27/10 10:03 , Raphael Ritz wrote: David Glick wrote: [..] If I recall, the main risks are that the migration may take a long time, and that the admin may not have properly configured blob-storage in their buildout. The migration itself is pretty well-tested, at least under Plone 3 -- Groundwire has migrated dozens of sites to use blobs. There may be some other concern I am forgetting? The only other concern I recall is the potential breakage of backup routines. If someone just rsyncs/copies Data.fs via cron (or the like) it will miss the binary data after the upgrade. As someone who wears two hats (developer and admin) I can see both sides. However, my admin side is always upset about potentially unknown upgrade consequences. As a compromise I would suggest an upgrade experience where the user gets something pushed into their face about admin changes that may need to happen before they push the button. As long as people are made *very* aware of the change *and* they have the opportunity to stop the upgrade at that moment to prepare their systems it would be OK. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkv+KoIACgkQRAx5nvEhZLJltwCgjVLlv38kJA2kCGqxAoktB5Rz xvwAnR6zvhyhjmkH2rfAZrNgNYlvheuT =YhoW -END PGP SIGNATURE- ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
