Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages When attaching a text file to a mail, KMail changes the newline encoding to Unix format (line feed only instead of carriage return/line feed pair for Windows). Expected is that files are leaved untouched when attaching them to a mail. How to reproduce: open a new mail, select "attach file". Select a file with known Windows cr/lf encoding and attach it to the mail. The file gets attached, and the "size" attribute right then shows a different size due to the removed cr chars. Right-clicking the attachment and selecting "open" will open the file with Kate, "extras->newline" will show "Unix" instead of "Windows/Dos".
What encoding do you use for the attached file before sending it? One you have attached a file in composer, use right click over the attachment list in the composer window and select the encoding you want for the attached file. Reading in rfc 1521 The difference between "8bit" (or any other conceivable bit-width token) and the "binary" token is that "binary" does not require adherence to any limits on line length or to the SMTP CRLF semantics, while the bit-width tokens do require such adherence. If the body contains data in any bit-width other than 7-bit, the appropriate bit-width Content-Transfer-Encoding token must be used (e.g., "8bit" for unencoded 8 bit wide data). If the body contains binary data, the "binary" Content-Transfer-Encoding token must be used
Is there a way to set the default encoding?
Kmail2 editor does not comply with RfC 822 and uses only "lf" instead of "cr-lf" at the end of a line. Especially in quoted-printable and MIME Extensions See: RfC 822, 2045 Point 2.10. Lines
Reassigning to Kmail2
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.