tedivm/fetch
Fetch is a PHP library for reading email and attachments via IMAP and POP. Connect to a mail server, authenticate, list messages, and access subjects, bodies, and attachments with a simple API (requires the PHP IMAP extension).
Full Changelog: https://github.com/tedious/Fetch/compare/v0.7.1...v0.7.2
This release contains a variety of bug fixes, optimizations, and some new helper functions to east common operations.
This update has a lot of bug fixes and optimizations, particularly around character encoding, that have been submitted by over a dozen contributors. This release also contains two new functions- listMailboxes and getOrderedMessages.
This release fixes some issues with the test suite when running through vagrant (the biggest being bugs with the automatic creation and resetting of the staging suite). It also enhances how Fetch handles certain types of encoding.
This update has no changes to Fetch itself, but does have an affect on it's test suite. The purpose of this update is to remove the Dovecot email setup out of the main package and into it's own development package. This will reduce the size of the production install of Fetch while also allowing other libraries to take advantage of the Dovecot/Vagrant/Travis email setup code.
With this latest release comes a whole new test suite, bringing the code coverage of the product from almost none to over 90%!
This update represents a new life for Fetch. Previously it had been very difficult to manage external contributions, as testing was a mostly manually process. With new technology like Vagrant and Travis-CI things have become a lot easier. The new test suite sets up an actual IMAP server and populates it with preprepared emails.
This is the first of many new updates, as Fetch will be getting a reworked API as well as some additional features. This update is backwards compatible with previous versions in order to provide a fully tested baseline.
Primarily bug fixes.
Adds BCC support (for reading through sent mail folders).
Bug fixes from PR #17.
How can I help you explore Laravel packages today?