Out of the box on Neon, I cannot add an Exchange Web Services (EWS) outbound email account to take full advantage of Akonadi's new EWS functionality in KMail. Note that setting up a 'Receiving' EWS Email Account works fine. This is because the 'Sending' account dialog in KMail needs the kmailtransport-akonadi plugin in order to list Akonadi-provided outbound mail transports. This plugin is contained in the kmailtransport-akonadi package, and the kmailtransport-akonadi package is not depended on by kmail, so is not installed by default. Installing the kmailtransport-akonadi package manually resolves the issue. Please make kmail depend on kmailtransport-akonadi to ensure a nice out-of-the-box experience for Neon end users.
I had the same problem, installing the plugin fixes it successfully. KDE neon git stable branch.
Can you please let me know where to get the plugin for this?
(In reply to Benjamin Buch from comment #1) > I had the same problem, installing the plugin fixes it successfully. > > KDE neon git stable branch. Can you please let me know where to get the plugin?
If you use KDE neon as Linux distribution it is in your package manager without any additions ;-) Install it with: sudo apt install kmailtransport-akonadi
This issue is still present.
I'm using kmail2 5.16.3 (20.12.3) (on Manjaro) and as far as I can tell, this bug is no longer reproducible.
This is a KDE Neon-specific packaging issue so the status of this on Manjaro Linux is unfortunately not relevant. However, currently the Neon kmail package has kmailtransport-akonadi as a 'Recommends' soft dependency which should cause it to be installed under most circumstances. I still think this is wrong: if EWS support is installed at all, kmailtransport-akonadi should be a hard dependency. If install-recommends is off - which is quite easy to do and some apt frontends do by default - then it's possible to set up an EWS receiving account after a fresh KMail install, but not a sending one. This is confusing behaviour that no end-user would expect.
I don't think you're supposed to submit distro-specific packaging bugs to bugs.kde.org, but rather to your distro's bug tracker.