Bug 341941

Summary:	Reply from the same address the message was sent to
Product:	[Applications] kmail2	Reporter:	Sudhir Khanger <sudhir>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REPORTED ---
Severity:	wishlist	CC:	KDE, robert
Priority:	NOR
Version:	4.14.2
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Sudhir Khanger 2014-12-16 12:30:50 UTC

I have multiple SMTP accounts setup but email are always replied with the default smtp account. I have to manually change that for each email I send. Instead of a single default smtp account it makes more sense that account-1 sends email through it's own smtp account not system default. Someone sends you email to bill@gmail.com and you reply through melinda@gmail.com because that's what has been set as system default is not the best choice.

Reproducible: Always

Steps to Reproduce:
1. Setup a few smtp account
2. set one as default
3. all emails are sent from default account

Actual Results:  
emails are always sent from same default account

Expected Results:  
different email account should be using their own smtp accounts.

Comment 1 Robert Riemann 2024-06-01 13:26:58 UTC

I think we should distinguish between two slightly different situations:

2) few non-changing recipients (cake of the bug reporter)

Create separate identities for each email address and configure the appropriate SMTP sender. Kmail switch to the respective identity when replying to mails. Furthermore, the identity chooser can also be enabled in the composer view, so that users get an easy drop-down selection field to overwrite the identity on a case-by-case (here email) basis.

2) many non-stable recipients due to the use of sub addressing, e.g. myname+onlineshop1@host.com or mycompany+client1@host.com

Here, it is likely not feasible to setup identities for each sub address. Note that there is no common standard for sub addresses. Sometimes it is "+", sometimes it is "-". Hence, detection is non-trivial.

As (1) solves the issue of the bug reporter and (2) is somewhat different, I suggest to either close this bug report as solved or change the title to be explicit that this bug report covers now rather (2).