Re: New Mail/Mime.php class

Rudi Benkoviè wrote: > > > Then the only thing you need to do is choose your prefered transport > > method (already implemented mail, sendmail and smtp). For ex: > Why not rather use PEAR's already existant transport methods (mail(), sendmail > and SMTP) - they are much faster and reliable than these (I have tried both, I > know)... Perhaps I was not clear enough, I wanted to say: "choose you prefered PEAR transport method" :) > > If noone suggests changes/missing points, I'll commit so. IMHO in Pear > > we can't have a complete Mail folder without a mime mail manager. Also > > if somebody can point me to some good code that do the reverse > > action (get the files back from a mime mail) I'll be very glad. > > <ad> > My little webmail <http://jawmail.sourceforge.net/> has > such class - pass the > message id and imap stream, and the class will do the other stuff... imho it > wouldn't be a problem to move some other functions to this class and package it > into PEAR... > just a suggestion :) > </ad> Umm, I didn't think on imap functions. I see now that some functions like imap_fetchstructure() and imap_fetchbody() do quite clean this task. Perhaps there is no need to implement it as a PEAR class. What do you think about that? Do you find any advantage to have a front-end to theese functions? > BTW, I'm doing a PEAR class for sending SMSes via various methods of transport - > URLs, mail gateways... I hope that it'll be finished soon (perhaps even this > week?) > If anyone would like to pass some data for their GSM companies, please mail 'em > to me... I only have those for Slovenia, since I live here :) > Sorry I can't help you much here. Tomas V.V.Cox