Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This release primarily brings bug fixes. It also includes a huge number of unit tests, making it (hopefully) one of the most stable releases of Mailhandler to date.
The biggest change in this release is that "default commands" are now configured per-Source rather than per-Importer. If you had configured any default commands in an Importer attached to a Source content type, those commands will automatically be moved to the Source nodes.
This release primarily brings bug fixes. It also includes a huge number of unit tests, making it (hopefully) one of the most stable releases of Mailhandler to date.
The biggest change in this release is that "default commands" are now configured per-Source rather than per-Importer. If you had configured any default commands in an Importer attached to a Source content type, those commands will automatically be moved to the Source nodes.
From now on, the HTML body of an email will be imported by default (if available), even if you previously selected to import the plain text body. If you want to import the plain text body, you will need to update your importers to use the appropriate mapping source. Please see http://drupal.org/node/1368580#comment-5390890 for more info.
From now on, the HTML body of an email will be imported by default (if available), even if you previously selected to import the plain text body. If you want to import the plain text body, you will need to update your importers to use the appropriate mapping source. Please see http://drupal.org/node/1368580#comment-5390890 for more info.
#1363484: Error on import related to get_mime_type() makes this release unusable for most users. Sorry! Please wait for 6.x-2.2, which will come out shortly. I'm adding more tests to prevent this sort of problem in the future.
Please note that the labels for 'POP' and 'IMAP' on the mailbox creation screen are reversed- this will be fixed in the next release. It's advised that you do not create any mailboxes using this release, and instead wait for the next release.
Please note that the labels for 'POP' and 'IMAP' on the mailbox creation screen are reversed- this will be fixed in the next release. It's advised that you do not create any mailboxes using this release, and instead wait for the next release.
There is an error when running update.php- please wait for alpha6 and skip this release. If you are installing mailhandler for the first time, however, it is okay to use this release.
The mailbox schema has changed slightly- the 'mail' field now holds and alphanumeric version of the email address, and the actual email address is stored in the extended settings. Note that the version jump from alpha3 to alpha5 is simply to keep Mail Comment and Mailhandler releases in lockstep.
You must run update.php if upgrading from a previous release. This is because the mailbox schema has changed slightly- the 'mail' field now holds and alphanumeric version of the email address, and the actual email address is stored in the extended settings. Note that the version jump from alpha3 to alpha5 is simply to keep Mail Comment and Mailhandler releases in lockstep.
An upgrade path now exists from Mailhandler 6.x-1.x to 6.x-2.x. Please make sure you have all dependencies of Mailhandler 6.x-2.x installed, then run update.php, which will upgrade your existing mailboxes to the 2.x format and create corresponding Feeds importers and input formats.
Initial release of 7.x-2.x- note that this release is strictly for testing and not for use on production sites. There is no upgrade path from 7.x-1.x. The purpose of this release is to iron out critical bugs and stabilize the schema/architecture of the module before an upgrade path is written.
Initial release of 6.x-2.x- note that this release is strictly for testing and not for use on production sites. There is no upgrade path from 6.x-1.x. The purpose of this release is to iron out critical bugs and stabilize the schema/architecture of the module before an upgrade path is written.
Note: This release is just a placeholder to attach issues for now. There is no real Drupal 7 code in this package. Avoid downloading it untill the code transition has been done.
Fix a major issue in the last release of not checking whether a module exists during execution of a plugin. See 6.x-1.9 release for other release notes.
This is a bug fix, refactor, and feature release. The main feature introduced is the pluggable authentication system which allows for other modules to create authentication plugins for mailhandler in order to handle whether a message should be allowed or denied based on a strategy implemented by each plugin. Bug fixes and refactoring are many and listed below: