Re: [Pharo-project] Issue 3509 in pharo: Multi-part MIME support for MailMessage

2011-01-19 Thread pharo
Updates: Status: Closed Comment #3 on issue 3509 by marcus.d...@gmail.com: Multi-part MIME support for MailMessage http://code.google.com/p/pharo/issues/detail?id=3509 13002

Re: [Pharo-project] Issue 3509 in pharo: Multi-part MIME support for MailMessage

2011-01-19 Thread Norbert Hartl
I'm not sure but I think there was a discussion about Zinc http components and how it will be integrated into pharo. What is the status on this? Seeing the issue report below I think there should be made some decision. Zinc has quite some good mime multipart support. No need to double efforts.

Re: [Pharo-project] Issue 3509 in pharo: Multi-part MIME support for MailMessage

2011-01-19 Thread Marcus Denker
On Jan 19, 2011, at 5:01 PM, Norbert Hartl wrote: I'm not sure but I think there was a discussion about Zinc http components and how it will be integrated into pharo. What is the status on this? Seeing the issue report below I think there should be made some decision. Zinc has quite

[Pharo-project] Issue 3509 in pharo: Multi-part MIME support for MailMessage

2011-01-06 Thread pharo
Status: New Owner: New issue 3509 by tony.fleig: Multi-part MIME support for MailMessage http://code.google.com/p/pharo/issues/detail?id=3509 I have added multi-part MIME support to MailMessage. The package will be in PharoInbox as soon as I finish labeling the slice with the issue

Re: [Pharo-project] Issue 3509 in pharo: Multi-part MIME support for MailMessage

2011-01-06 Thread pharo
Comment #1 on issue 3509 by tony.fleig: Multi-part MIME support for MailMessage http://code.google.com/p/pharo/issues/detail?id=3509 Published to PharoInbox.

Re: [Pharo-project] Issue 3509 in pharo: Multi-part MIME support for MailMessage

2011-01-06 Thread pharo
Updates: Status: Fixed Labels: Milestone-1.3 Comment #2 on issue 3509 by marianopeck: Multi-part MIME support for MailMessage http://code.google.com/p/pharo/issues/detail?id=3509 excellent. thanks! I tag it as milestone 1.3 since only important bugs are integrated in 1.2