Re: status of Mail_mime?
| From: | Alexey Borzov | Date: | Tue, 30 Dec 2008 23:49:29 +0000 |
| Subject: | Re: status of Mail_mime? | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev php.pear.qa |
| Request: | Send a blank email to pear-dev+get-51369@lists.php.net to get a copy of this message | ||
Hi,
Walter Hop wrote:
[in reply to daniel.oconnor@gmail.com, 27-12-2008] *nudge* Cipri, Walter! If we don't hear from either of you by Jan 4th, we're probably going to push ahead and do this release - so let us know if that's not ok! I have the week off, so I can fix some things during this week. Cipri is on a long vacation and probably won't be available. I will be on IRC in the coming days, but I'm not always looking at the screen, so please send me a mail and we can sort out the priorities. Releasing around jan 4th sounds good to me. I haven't built a release before, so some assistance with this would be very much appreciated.The release will be pretty useless if it doesn't contain a fix for bug #11238: http://pear.php.net/bugs/bug.php?id=11238 I spent a bit of time researching said bug and the fix will not be an easy one, unfortunately. Essentially we'll need to add logic to parse "structured" headers from RFC 822. It won't need to be as complex as that in Mail_RFC822 class, but we'll need to split the header value into lexical parts, as described in section 3.1.4 of said RFC and then encode (or not) these parts separately. All the patches proposed so far do not follow this approach and thus fail to comply to RFC 2047 (its section 5, in particular).