Donate: If you have found Mail_IMAP to be helpful in your project please express your appreciation by donating to my efforts through my Amazon wishlist.
Mail_IMAP provides a flexible API for connecting to and retrieving mail from mailboxes using the IMAP, POP3 or NNTP mail protocols. Connection to a mailbox is acheived through the c-client extension to PHP. Meaning installation of the c-client extension is required to use Mail_IMAP.
Mail_IMAP can be used to retrieve the contents of a mailbox, whereas it may serve as the backend for a webmail application or mailing list manager, or whatever you can imagine that requires connectivity to a mailbox.
Since Mail_IMAP is an abstracted object, it allows for complete customization of the UI for any application.
By default Mail_IMAP parses and retrieves information about multipart messages in a threaded fashion similar to MS Outlook, e.g. only top level attachments are retrieved initially, then when message part id and message id are passed to Mail_IMAP, it retrieves attachments and information relevant to that message part. Mail_IMAP::getParts() can be supplied an argument to turn off threading, whereas all parts are retrieved at once.
Mail_IMAP also, by default retrieves the alternative message parts of multipart messages. This is most useful for debugging applications that send out multipart mailers where both a text/html and alterntaive text/plain part are included. This can also be turned off by supplying an additional argument to Mail_IMAP::getParts().
Mail_IMAP always searches for a text/html part to display as the primary part. This can be reversed so that it always looks for a text/plain part initially by supplying the necessary arguments to Mail_IMAP::getParts(), and Mail_IMAP::getBody().
03/16/2013 - After an extremely long hiatus and some encouragement from Mail_IMAP users, I have resumed development of Mail_IMAP! I am currently preparing a brand new version with a revised API built for PHP5, and make to take advantage of what PHP5 has to offer. I will try to come up with a workable solution that keeps as much backward compatibility as possible, but I make no promises there.
The new project will be called hMailIMAP. It is built into my PHP framework Hot Toddy. Eventhough it will be built into Hot Toddy, I will release a stand-alone package, which will not require Hot Toddy.
The new package will NOT be posted to PEAR. It will also have no depenencies on PEAR packages. More news to come on that.
I have also posted some small revisions and bug fixes to the old Mail_IMAPv2, these revisions are NOT in the downloadable tgz package on PEAR and will NOT be posted to PEAR in the future. You can, however, download the new zip archive containing the revised Mail_IMAPv2 source code
Among the improvments: fixed decoding of message headers, including support for UTF-8. Added PHP5 support. Removed dependency on Net_URL and PEAR error stack.
Improvements to the old Mail_IMAPv2 script will terminate when hMailIMAP is completed and ready to go.
You are welcomed to contact me with bug reports (please be as detailed as possible). Please DO NOT contact me with support or how-to requests, I will not answer them, and do not have time to answer them. I have an extremely busy schedule, which is why I have been unable to develop Mail_IMAP for some eight years or so. You are also welcomed to email messages that Mail_IMAP is unable to parse the structure of, or properly decode to: email@example.com. Please include [Mail_IMAP] in the subject line.
This is changing, I'll post more about it when I have a product.
There are no comments posted at this time.
* All comments are moderated and are subject to approval.
Your comment will appear once it has been approved.
Posting multiple times will not expedite the approval process.
Comments are closed at this time.