Hi All,
I would like to put my mailparse ("As seen on zend.com weekly summary")
extension into CVS; shall I just check it into php4/ext?
> wc *.c *.h README *.m4 *.in
805 2374 21660 mailparse.c
1191 3096 25926 rfc2045.c
78 217 1578 rfc2045_base64encode.c
129 289 2885 rfc2045acchk.c
108 255 2096 rfc2045acprep.c
118 267 2215 rfc2045appendurl.c
301 828 6343 rfc2045cdecode.c
42 113 912 rfc2045decode.c
50 125 996 rfc2045find.c
61 121 1119 rfc2045mkboundary.c
460 1141 9385 rfc2045rewrite.c
117 277 2528 rfc2045tryboundary.c
542 1487 10700 rfc2047.c
110 210 1899 rfc2047u.c
722 1635 13411 rfc822.c
102 222 1853 rfc822_getaddr.c
95 208 1640 rfc822_getaddrs.c
84 210 2748 php_mailparse.h
208 739 5652 rfc2045.h
81 265 1926 rfc2047.h
167 705 5039 rfc822.h
79 390 2917 README
26 132 958 config.m4
16 46 537 Makefile.in
5692 15352 126923 total
Any comments for/against this?
It's based on maildrop, and I am cleaning out some cruft that does not
apply to PHP, so I expect the code size to reduce.
It allows you to parse MIME mail (something that a lot of people are doing
with PHP) in a resource efficient manner - streaming through files rather
loading the whole thing into memory (something you don't want to do with
100 users opening messages with 2MB attachments).
I plan to add support for creating MIME mail (a bit like the
imap_mail_compose() function, but with no dependencies on c-client), and
provide an integrated "mail_compose" function that can also handle S/MIME
signatures (via openssl extension).
I know Jani was interested in seeing this get into CVS, and I have had 84
downloads since the weekly summary was published (week31).
--Wez.
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]