Re: Imap Backend Propsal
| From: | Cipriano Groenendal | Date: | Mon, 02 Feb 2004 16:03:20 +0000 |
| Subject: | Re: Imap Backend Propsal | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-25426@lists.php.net to get a copy of this message | ||
> > I'd disagree there. What I could gather about Mail_Box is that it's
trying
> > to provide a wrapper aruond different sorts of sources for mail, be it a
POP
> > / IMAP server, a local file, a directory with mails, etc. Wolfram's
> > Mail_Message OTOH seems to be used more for reading and generating
messages,
> > which is already provided by other packages (Mail, Mail_Mime, etc). I
think
> > that Richy's Mail_IMAP(For lack of a better name) compliments the Mail
and
> > Mail_MIME packages nicely. COmbine all three, and you have a full
fledged
> > emailing app (Mail to send, Mail_MIME to make, and Mail_IMAP to read
> > messages). I havn't had the time to try out Mail_IMAP yet, but from what
I
> > saw, all it missed was the ability to pass an already existing IMAP
> > connection to it.
> > My request for being able to pass a .eml file to it wouldn't work I just
> > realized 'cause you couldn't run the imap_*() functions on that.
>
> That's true, you'd have to use something like the mailparse extension.
> So what structure do you guys suggest for that package ?
>
> Looks like we will end up with Mail_Imap and that's it ?
> Personally, I don't have a problem with it.
Well, right now I'm not at all involved with any project, I'm just jumping
out of the lurking corner to yell
Ooh! ooh! I want that! ;-)
My personal opinion on all of this however is this:
* Add Richard's Mail_IMAP package as Mail_Message, Mail_Reader, or something
similar.
* Take an already established connection, or establish a connection to a
mailserver.
* Fetching a list of a certain (IMAP/POP/NNTP) folder.
* Fetching a part(Attachment, Plain/HTML, Plain/TEXT) of a message.
* Fetching a certain attachment.
* Handle errors/notices from Mail Server.
* Handle folder listings that might exist on the remote server.
Most of these are already in the Mail_IMAP package according to the quick
glance I gave it. Any that don't exist yet, I'd be happy to help implement
in the Mail_IMAP package.
Having these all of these options allows one to create an entire mail
package easily.
* Mail_mail to send mail.
* Mail_MIME to create mail
* Mail_IMAP to read/access mail.
Just my $14.95 by now.
Cipri