Bug 2506 - eols get converted
Summary: eols get converted
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Plugins/Privacy/PGP (show other bugs)
Version: other
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
: 2588 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-09-27 13:52 UTC by Lars
Modified: 2012-01-27 08:11 UTC (History)
1 user (show)

See Also:


Attachments

Description Lars 2011-09-27 13:52:10 UTC
When I attach a LaTeX file to an email and send it encrypted with PGP MIME, the LF eols get converted to CR+LF. I think this happens during the creation of the email and not when saving the attachment. 
Interestingly, it seems that the conversion can be circumvented by removing the filename suffix ".tex".
Comment 1 mike 2012-01-22 16:35:47 UTC
I can reproduce this, too. Please fix.
Comment 2 Paul 2012-01-22 17:18:23 UTC
what is the problem?
Comment 3 mike 2012-01-24 19:16:10 UTC
What is yours?

Claws-mail should not cause an attached file to change from sender to receiver.

Steps to reproduce:
1) Type a TeX file, e.g.: gedit test.tex
2) cp test.tex text
3) Start claws-mail and compose a new email
4) Attach the files "text" and "test.tex"
5) Send the email encrypted with PGP/MIME to yourself
6) Receive email and save the attached files
7) Check the filesize of the newly saved files: ls -l text test.tex
8) Be surprised that "test.tex" is couple of bytes larger than "text" because the eols got converted
Comment 4 Paul 2012-01-24 20:05:16 UTC
This is correct for PGP/MIME'ed msgs.
See http://www.ietf.org/rfc/rfc3156.txt
Comment 5 mike 2012-01-24 21:36:09 UTC
The only reference to <cr> i saw under the linked file was concerning signed messages but i am not talking about signed messages. However i do expect it to work with signed messages, too. neither did i find anything about handling files with different name suffixes differently.

i don't care what creative interpretation of this RFC you can come up with -- for endusers it only matters that sending an encrypted (TeX-)file should not alter the received file without warning. thunderbird(+enigmail) does manage that. doesn't matter if they do it by better understanding the rfcs or less caring about the rfc, their endresult is better.
Comment 6 Paul 2012-01-27 07:59:06 UTC
*** Bug 2588 has been marked as a duplicate of this bug. ***
Comment 7 Colin Leroy 2012-01-27 08:11:41 UTC
If your text files should be treated as binary, it's enough to set their mime-type to application/octet-stream.

Note You need to log in before you can comment on or make changes to this bug.