Summary: | Cannot add EWS outbound transport in KMail | ||
---|---|---|---|
Product: | [KDE Neon] neon | Reporter: | James Young <marmarama> |
Component: | general | Assignee: | Neon Bugs <neon-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | benni.buch, hujq, jr, krissn, neon-bugs, nick.berg3, nortexoid, sitter, tonymt00, victor |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
James Young
2017-12-19 14:30:15 UTC
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. |