Version: 4.7 (using KDE 4.7.4) OS: Linux If i add a custom mime header (Configure-->composer-->headers), press "ok" and reopen the dialoge, the custom headers list is empty again. Reproducible: Always Steps to Reproduce: Add a custom mime header. Save and reopen the configure-dialogue. Actual Results: The before-added custom mime headers are lost. Expected Results: the custom mime headers are saved and used when sending e-mail. As it seems, the mime headers are stored in kmail2rc without a number/id. Example: [Mime #] name=User-Agent value=KMail If I add the header by hand including a number (#0) it shows up in the configure-dialogue and doesn't get lost and is correctly used when sending email. Example: [Mime #0] name=User-Agent value=KMail
Valid in master
Git commit 0cb01ec600fc2f96104318fdc25b2b80089c0183 by Montel Laurent. Committed on 12/01/2012 at 08:42. Pushed by mlaurent into branch 'master'. Fix Bug 290702 - Custom mime header fields are not stored FIXED-IN: 4.8.1 M +1 -1 kmail/configuredialog.cpp http://commits.kde.org/kdepim/0cb01ec600fc2f96104318fdc25b2b80089c0183
Git commit 515f27a306f59913e8af2eb886ba28c4b859600a by Montel Laurent. Committed on 12/01/2012 at 08:42. Pushed by mlaurent into branch 'KDE/4.8'. Fix Bug 290702 - Custom mime header fields are not stored FIXED-IN: 4.8.1 (cherry picked from commit 0cb01ec600fc2f96104318fdc25b2b80089c0183) M +1 -1 kmail/configuredialog.cpp http://commits.kde.org/kdepim/515f27a306f59913e8af2eb886ba28c4b859600a
Git commit 20ea4aa0d135a1a688016f7dc4052d743a4796f7 by Montel Laurent. Committed on 12/01/2012 at 08:42. Pushed by mlaurent into branch 'KDE/4.7'. Fix Bug 290702 - Custom mime header fields are not stored FIXED-IN: 4.8.1 (cherry picked from commit 0cb01ec600fc2f96104318fdc25b2b80089c0183) M +1 -1 kmail/configuredialog.cpp http://commits.kde.org/kdepim/20ea4aa0d135a1a688016f7dc4052d743a4796f7
Does "fixed-in: 4.8.1" mean that KDE 4.8.0 will be released containing the bug?
tagging happened yesterday, the will will likely be in 4.8.0 Please test and report
If tag was created yesterday so it will fix in 4.8.0. Regards