Re: Proposal for new p

Olivier Hill wrote:

Richard York wrote:

I beleive Mail_MIME already includes this functionality. If so, why would your package be helpful? Does it take another approach? If so how is your approach different? If the functionality you're proposing doesn't already exist in Mail_MIME, could it be integrated? These are questions you'll have to answer to determine if your package has a place in PEAR. If you think it still merits a new package, a link to the source code would also be helpful.

It seems I forgot to look at the Mail_MIME source file until the end. I've looked in Mail and Mail_RFC822, but not Mail_MIME. The only thing that differs is the approach then. Because encoding headers via RFC2047 doesn't require a MIME message. This is why I didn't look into Mail_MIME before posting (sorry). So actually, if you don't want to send a (even single-part) MIME message, you cannot use Mail_MIME to encode the headers. I'm sorry if I'm mistaken. I have added an accent in the title for those who want to see what RFC2047 encoding looks like. Olivier

Perhaps this should go into a different package then and Mail_MIME should be altered to use it. Of course, I don't see the problem if using Mail_MIME for a single-part message. It's basically just a system to help in creating of an (even single-part) e-mail message. -- paperCrane <Justin Patrin>