Implement imap client

[frederikbosch]

• [x] Finish reading message from client
• [x] Finish decent request/response API
• [x] Completely cover the IMAP spec
• [x] Add tests
• [x] Add ClientFactory with fromString method
• [x] Add ImapTransport

IMAP spec.

• [x] CAPABILITY
• [x] NOOP
• [x] LOGOUT
• [x] STARTTLS
• [x] AUTHENTICATE
• [x] LOGIN
• [x] SELECT
• [x] EXAMINE
• [x] CREATE
• [x] DELETE
• [x] RENAME
• [x] SUBSCRIBE
• [x] UNSUBSCRIBE
• [x] LIST
• [x] LSUB
• [x] STATUS
• [x] APPEND
• [x] CHECK
• [x] CLOSE
• [x] EXPUNGE
• [x] SEARCH
• [x] FETCH
• [x] STORE
• [x] COPY
• [x] UID

[frederikbosch]

Today I finished successfully fetching messages from the imap server using a decent API that should be ready for extending it to the full RFC spec. At least that is what I am thinking considering my current knowledge of IMAP v4rev1.

[frederikbosch]

One should consider that the current API could be wrapped in the future in an easy to use generic mail account/mailbox API. That might look like this.

$account = new ImapAccount (ClientFactory::fromString('imap://user:pass@host'));
$mailbox = $account->select('INBOX');
$messages = $mailbox->fetch(1, 5); // fetch first 5 messages
foreach ($messages as $message) {}

The above, however, is the next level of abstraction. First we need to implement the specifics of the IMAP protocol.

[frederikbosch]

Almost done covering the complete IMAP spec. I think I will leave the coverage as it is now. Focus now on getting this completely tested and adding the ClientFactory.

[frederikbosch]

IMAP protocol has 100% spec (from request perspective) and 100% test coverage now. Only a client factory left.