The source View for an email tries to be smart and wants to make the mail vaild to the contentTransferEncoding header. If you have a non valid mail (content is not in the right contentTransferEncoding), this this looks freaky and makes it hard to locate any kind of bug. One example of the wrong source view interface you find at bug https://bugs.kde.org/289728. Reproducible: Always Steps to Reproduce: 1. use a non valid mail (ContentTransferEncoding doesn't match with content) [see attchment]. 2. open this mail with View Source in kmail. Actual Results: Source view shows the mail like this: Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" BEGINPGPMESSAGEVersionGnuPGv1411GNU/LinuxhQEMA5XFb/XflcUEAQf8DgQ4PWfOI7Q9WRw nN/V9qu7fIJRlK7sqb9DKF/PlaNy8ZfTf/TNG5MJ+yokeX0nXkRBCPdVBLVLRnfuUam2xK3kC1LV 6ORPRWBJcTyj27pKejXemSenPb0H1dXZwqNvf3g/wYRKbgU+6R2zQVlb8dvwoP48S3pOFSYfrmr4 xXSwvJ+xcgQ6u8ul27tZ7HhdSwlYrV7HF5aPFQZL00zqZ1Pxth0qss8aaW8aOAnjssncW2ipN6u8 dtVMMdr+AWPPI15Tyatvo6m7O532FTkz1+keIwGf0eFZsbYbriMY44ff5YKNnM7GMULXOC61bGuw aF51Rapy2IT4suLMvlaCt0dJIAaw2qCWbCKz7agF2WaGvhcuQJmmcTQ9DmrlDvXY4NUUHM/1Ga/j euZUIK5TtDch5eECh0tBOhwEjJPNZcRg22ZvhOdUfzj/HAzFD8ENDPGPMESSAGEACg== Expected Results: Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" -----BEGIN PGP MESSAGE----- Version: GnuPG v2.0.19 (GNU/Linux) hQIOA2EOZthMz4KpEAgA6MjhMzsjgDQlmAXB39JgvoAE0v2+1qN7hztb8rSMVrkD GRislUNIedEW8htmiC1dOrm8GxOhuUTlcVeQhpz17uIFng377ZLbpER7FUma3hv9 ....
Created attachment 77719 [details] a non valid mail This is one non valid mail, where you can see this behavour, if you display the content of this mail vis the Source View Dialog in kmail.
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.