If the user has more than 1 mail account on the web, he needs to setup more than one access in Kmail2. So far, so good. For sending mails, Kmail2 is not able to set up a smtp account for, as example, each IMAP account. Moreover, Kmail2 is able to connect, for example, Identity A with IMAP-access B. But it is not able to connect this identity A and IMAP access B with the smtp-account, which belongs to IMAP-account B. This is, while Kmail2 could read the username and password of the smtp-account, which normally are the same as the username and password of the belonging IMAP-account. Because Kmail2 is not that smart, but the user thinks that it actually is, the user tries to send mails from Identity B, but the Mail will be sent via Identity A, or if the service provider on the web are different for Identity A and B, will not be sent, resulting in a failure message about "wrong password and username". This goes on and on, until the user realises, that he actually needs to connect the smtp-accounts manually to each identity. Reproducible: Always Steps to Reproduce: 1. set up 2 or more mail accesses 2. wonder why Kmail2 sends mails over the wrong paths 3. search and find a small option, hidden in the config, in the "advanced" Tab Actual Results: see description Expected Results: Kmail2 should connect smtp accounts automatically to identities, or at least ask the user or make him aware of this.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.