# Mautic 7: Columba Edition is released **URL:** \ **Category:** Community Blog\ **Created:** [January 20, 2026, 7:25pm UTC](https://forum.mautic.org/t/mautic-7-columba-edition-is-released/37193 "2026-01-20T19:25:15Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\ **Post date:** [January 20, 2026, 7:25pm UTC](https://forum.mautic.org/t/mautic-7-columba-edition-is-released/37193/1 "2026-01-20T19:25:15Z")
Originally published at: [Mautic 7: Columba Edition is released - Mautic](https://mautic.org/blog/mautic-7-columba-edition-is-released) Today we’ve released Mautic 7.0: Columba Edition. It’s here. This is a full term release with a four-year support cycle – one year active, one year security, two years Extended Long Term Support. [Read more about our release strategy](https://mautic.org/blog/introducing-mautics-new-release-strategy-long-term-support-elts/). Check out the [full release notes](https://github.com/mautic/mautic/releases/tag/7.0.0). Here’s what matters. ![](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/5/580eaf6051434cb71ee97c466bc7be4687687d2f.png) ## Thank you It takes a village to ship a release. A huge thank you to everybody who contributed code, tested and reviewed contributions, created imagery, wrote content, managed social media, and updated documentation. Every contribution – code or no-code – helped get Mautic 7 over the line. The Mautic Community is the foundation of our progress. This release exists because of you. ## Marketer-facing changes ### Projects: Keep your campaigns organised As campaigns grow, organisation matters. Projects in Mautic 7 help teams manage all related resources under a single, logical structure. Group emails, landing pages, forms, and assets that belong together. Keep multi-channel initiatives aligned. Reduce duplication across campaigns. Projects give teams a shared structure without limiting flexibility. This means: - Different product lines? Projects have you covered. - Multiple organizational units? Projects have you covered. - Significantly differing seasonal campaign themes? You guessed it: Projects have you covered. ### Campaign import and export Columbia, aka Mautic 7, introduces the ability to import and export campaigns together with their related assets. Move complete campaign setups between environments without rebuilding them manually. Migrate from development to staging to production with confidence. Reuse proven campaign frameworks across teams or regions. An ideal step up for organisations of any scale. This feature was funded by the [NLNet Foundation](https://nlnet.nl/project/MauticPortability/). ### Smarter segment-based sending Segment emails can now adapt to audience growth in real time. Choose whether to continue sending to contacts as they enter a segment, or lock the audience to those present when sending begins. More control. Better predictability. Clearer intent for time-sensitive campaigns. ### Preview and scheduling improvements - **Text message previews** optimised for quick, on-the-go review - **Web notification previews** that make design validation simpler and more visual - **Email scheduling** now lives on the email detail page – easier to review, adjust, and launch without context switching Less guesswork before you publish. ## Developer-facing changes ### A modern API at /api/v2 API Platform brings a cleaner, more consistent interface – built for what’s next. - Autogenerated, interactive documentation – test and discover responses right in the docs - More consistent, discoverable endpoints - Better alignment with modern API standards - Stronger support for headless use cases, integrations, and custom applications A better foundation for building on Mautic. ### Infrastructure flexibility - **Database caching** can now be replaced with Redis or similar services, improving performance for larger installations - **Multiple mailer DSNs** can be defined for more flexible email infrastructure - **Project events** allow plugins and bundles to map their own entities into the Projects bundle ### Under the hood Mautic 7 brings support for Symfony 7.3 and PHP 8.4. We’ve updated many outdated dependencies and removed a vast amount of legacy code. The result: a cleaner, more modern core that’s easier to extend and maintain. For details on changes that may affect custom code, review the [UPGRADE-7.0.md file](https://github.com/mautic/mautic/blob/f8177794d63cfcd0f3987e0dcf6190c56efbdfbd/UPGRADE-7.0.md). ## Before you upgrade Mautic 7 includes changes that may affect your setup. Here’s what to check: **PHP version:**  Mautic 7 requires PHP 8.2 or higher. PHP 8.1 is no longer supported. **No more UI updates:**  We removed manual updates through the Mautic interface. Use Composer or download the release package directly. **What we removed:** - AMQP queue support - The API rate limiter (unmaintained library) - The “Identify visitor by tracking URL” configuration option Review the [UPGRADE-7.0.md file](https://github.com/mautic/mautic/blob/f8177794d63cfcd0f3987e0dcf6190c56efbdfbd/UPGRADE-7.0.md) for the full list of breaking changes before upgrading. ## Get started Ready to explore Mautic 7? - [Download Mautic 7.0](https://github.com/mautic/mautic/releases/tag/7.0.0) - [Read the full release notes](https://github.com/mautic/mautic/compare/6.0.3...7.0.0) **Questions? Join us on [Slack](https://mautic.org/slack/) in #mautic-7.** ---
**Author:** ![rabii](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rabii/32/13080_2.png) [@rabii](https://forum.mautic.org/u/rabii)\ **Post date:** [January 21, 2026, 4:23pm UTC](https://forum.mautic.org/t/mautic-7-columba-edition-is-released/37193/2 "2026-01-21T16:23:20Z")
> [@silavapi](#): > > **Multiple mailer DSNs** can be defined for more flexible email infrastructure First of all, congrats on the new release and thanks to all the amazing contributors - version 7 looks really good. How does this work - i couldn’t find any documentation on how to use multiple dsn. Certainly under Configuration \> Email Settings \> there is only one Email DSN. I assume this feature should allow a marketer to set multiple DSN whcih allow to use different providers / differents email domains to send emails ? Am i missing something here ? Thanks ---
**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\ **Post date:** [January 21, 2026, 4:37pm UTC](https://forum.mautic.org/t/mautic-7-columba-edition-is-released/37193/3 "2026-01-21T16:37:56Z")
Hey there, thanks for the positive comments and appreciation of the many contributors who have put work into this release! > [@rabii](#): > > How does this work - i couldn’t find any documentation on how to use multiple dsn. Certainly under Configuration \> Email Settings \> there is only one Email DSN. This is a code-level change to enable future plugin development which would enable this behaviour. If you review the PR related to it, you’ll find the info. There is no current implementation of it, so we haven’t got any demonstrable examples to use at this time and the developer was not able to help with documentation. > > > See https://symfony.com/doc/current/mailer.html#multiple-email-transports > > > |… Issue(s) addressed | Not sure if a separate issues need to be created > > > \## Description > > I'm developing plugin that should allow for multiple mailer transports and I would like to follow symfony's mechanism to do so. > https://symfony.com/doc/current/mailer.html#multiple-email-transports > > I can modify the configuration of the \`framework\` bundle by using a prepend in my own plugin/extension > https://symfony.com/doc/current/bundles/prepend\_extension.html > but I face an error from symfony that I can't define both \`transports\` and \`dsn\` for mailer. > My proposal is to change to the long form of defining the mailer configuration so extensions have the chance to add more transports. With the current definition it limits extensibility. > > > > \--- > \### 📋 Steps to test this PR: > Create a new plugin with the following \`DependencyInjection/MultiSMTPRoutingExtension.php\` file > \`\`\`php > \ > namespace MauticPlugin\\MultiSMTPRoutingBundle\\DependencyInjection; > > use Symfony\\Component\\Config\\FileLocator; > use Symfony\\Component\\DependencyInjection\\ContainerBuilder; > use Symfony\\Component\\DependencyInjection\\Extension\\Extension; > use Symfony\\Component\\DependencyInjection\\Extension\\PrependExtensionInterface; > use Symfony\\Component\\DependencyInjection\\Loader\\PhpFileLoader; > > class MultiSMTPRoutingExtension extends Extension implements PrependExtensionInterface > { > /\*\* > \* @param mixed\[\] $configs > \*/ > public function load(array $configs, ContainerBuilder $container): void > { > $loader = new PhpFileLoader($container, new FileLocator(\_\_DIR\_\_.'/../Config')); > $loader-\>load('services.php'); > } > > public function prepend(ContainerBuilder $container): void > { > $container-\>prependExtensionConfig('framework', \[ > 'mailer' =\> \[ > 'transports' =\> \[ > 'alternative' =\> 'smtp://mailpit:1025' > \], > \], > \]); > } > } > \`\`\` > With Mautic core without this PR it throws an error but with the change proposed it allows to have an additional \`alternative\` transport. We have a project which we’re hoping will be picked up, to enable multi-DSN use in the application: > **[Multiple email transport configuration for different purposes - Mautic...](https://community.mautic.org/processes/roadmap/f/43/results/16)** > > This proposal has been discussed on the Mautic forums at https://forum.mautic.org/t/ability-to-specify-different-email-gateways-to-use-for-different-purposes/10620(External link)The feature request has also been tracked in GitHub issue #3827 since... Currently there are third party commercial plugins that do part of this, but not the whole story (e.g. as far as I know they don’t fully take into account bounce notifications, replies, etc). We would like to bring such a capability into core (and so would many Mautic users!) ---
**Author:** ![rabii](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rabii/32/13080_2.png) [@rabii](https://forum.mautic.org/u/rabii)\ **Post date:** [January 21, 2026, 4:39pm UTC](https://forum.mautic.org/t/mautic-7-columba-edition-is-released/37193/4 "2026-01-21T16:39:42Z")
Thanks for the detailed reply 🙂 ---
**Author:** ![jonathandhn](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/jonathandhn/32/5737_2.png) [@jonathandhn](https://forum.mautic.org/u/jonathandhn)\ **Post date:** [January 30, 2026, 3:03pm UTC](https://forum.mautic.org/t/mautic-7-columba-edition-is-released/37193/5 "2026-01-30T15:03:55Z")
So the plot is to allow direct Mautic based control of what would have need a custom MTA relay host? Wonderful