Offline Documentation
As of today, you can download the whole Swiftmailer documentation for easy offline reading. Get the gorgeous PDF document for your laptop and get the great EPUB file for your tablet or your phone.
As of today, you can download the whole Swiftmailer documentation for easy offline reading. Get the gorgeous PDF document for your laptop and get the great EPUB file for your tablet or your phone.
Swiftmailer 4.1.6 has been released. It makes serialized messages much smaller, which is great when you store messages in a spool.
Swiftmailer 4.1.5 has just been released.
This release contains some bug fixes. The full changelog is available here: https://raw.github.com/swiftmailer/swiftmailer/master/CHANGES
Install it as usual:
Swiftmailer 4.1.4 has just been released.
This release contains a fix for an annoying bug when you want to send many emails with attachements. It also contains a new MemorySpool class. This new class is used by Symfony 2.1 to allow sending emails after the page has been sent to the user.
The full changelog is available here: https://raw.github.com/swiftmailer/swiftmailer/master/CHANGES
Install it as usual:
Swiftmailer 4.1.3 has just been released. This release contains bug and documentation fixes.
Using Swiftmailer with TLS now works as expected (thanks to the STARTTLS addition).
The full changelog is available here: https://raw.github.com/swiftmailer/swiftmailer/master/CHANGES
Install it as usual:
Swiftmailer 4.1.2 has just been released. This release contains bug and documentation fixes. The full changelog is available here: https://raw.github.com/swiftmailer/swiftmailer/master/CHANGES
Install it as usual:
As of today, Swiftmailer is using Github to manage issues.
All opened tickets in the old system (Lighthouse) have been migrated to Github. The new ticket contain the reference to the original ticket, the original date, and the original reporter:
https://github.com/swiftmailer/swiftmailer/issues
As we were already using Github for our repositories, using Github for tickets is a natural fit and will give everyone a better experience and a better integration.
Even if the Lighthouse system will remain open, don’t create new tickets there (as far as I can see, there is no way to “lock” Lighthouse in a read-only state).
The website and the documentation have also been updated to reflect this change.
With the upcoming release of Swiftmailer 4.1.0, I’ve changed the way the Git repository is managed. The master branch becomes the main development branch where new features are added (right now, it is equivalent to the 4.1 branch, but it is where new features will be added for the 4.2 version). The 4.0 branch is a new branch to manage the maintenance of the 4.0 version and 4.1 remains the maintenance branch for the 4.1 version.
I’ve just released the first release candidate for Swiftmailer 4.1.
This new version of Swiftmailer has several new features:
You can install this new version as usual: