Re: Imap Backend Propsal

>I've written my own webmail client with similar functions in the backend as >this class proposes, and as such, I'm highly interrested in it. >As you may or may not know, PHP's imap module can connect to IMAP, POP and >NNTP via the same functions. Even the data returned will be nearly >identical. There will be no need at all for a seperate Mail_POP3 class, >since the Mail_IMAP package will access it just as easily as it would with >IMAP. That said, I agree with Bertrand about the class name and function >names. I'd suggest calling it Mail_Message, since it deals with parsing and >reading of a message. Actually my entire package has been created testing on a POP3 account, I don't have access to an IMAP or NNTP mailbox. As far as what the name of the package is, I have considered Mail_Cclient but I think since the PHP functions are called imap_xxxx I'd stick with the Mail_IMAP name, eventhough it is misleading in that aspect. >Also, let me know if you could use any help with this, I've had enough >experience with the imap_* functions to know I don't wanna have to deal with >them ever again ;) They can certainly leave you red-faced and feeling abused! I think the biggest help at this point would be testing. I am only aware of one bug currently, and that has to do with how the default header pid is selected. I need to alter it to search parent parts for a header pid in certain situations. In multipart messages the functions always look for a text/html part to display, in finding a default top level part, it looks for a text/html part first and a text/plain part second. My question is, in multipart messages, is that text/html part always gauranteed to exist?!?! And in what situations will it not exist as a subpart in a multipart message. So that is a potential second bug, Perhaps I will use recursion to re-search the message for a text/plain part in the event that a text/html part was not found. Best Regards, Richard York