Bug 344047

It's normal.
What is the problem ?

If it is by design then ok. Simply, looking in the draft helps to test the custom headers functionalilty.

Acutually I discovered that issue while making some custom changes in the code by adding the following functionalilty. I don't know if this can somehow be generalized.

I receive emails containing a specific header : "X-Apparently-To" formatted this way :
X-Apparently-To: my_email-extension@example.tdl; Wed, 11 Feb 2015 20:32:37 +0000
I use the email of this field because it is the message's recipient. Sometimes it is not in To: or Cc: (for example when in bcc)
I manage many email extensions and don't want to create an identity or alias for each of them.
I want to use that email when replying to the mail instead of my regular identities' mail. I use it to override the From & ReplyTo email of the reply.
Thus I modified the code so as to extract the email from the X-Apparently-To header, save it in the reply message. Thus I wanted to save it's value in the draft so that when reopening the draft, it is not lost and overwritten by the default identity email. I can send you a patch for that specific development in case you want to have a look at it and see whether this can be generalized or you have an idea to implement this

FYI : the X-Apparently-To is set on emails received on a yahoo account when using the disposable email address functionnality

Actually that could also be useful to people using the +extension of gmail accounts (mymail+alias1@gmail.com) but I'm not sure of the name of the header gmail adds to the incoming mail (probably Delivered-To: )

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Still present in KMail 5.2.3
(versions shipped with debian jessie (stable) : kdepim 16.04.3)
According to #c1 it is by design.
In the meantime I could find a workaround for my specific need.

Thanks for the update; changing status.

If developers decide that the issue is indeed as intended, they should close as WONTFIX.

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!