> So what’s happened here? Well, whoever collected these emails first converted from CRLF (i.e., “Windows” line ending coding) to “NL” (i.e., “Unix” line ending coding). This is pretty normal if you want to deal with email. But you then have one byte fewer: I think there is a second possible conclusion, which is that the transformation happened historically. Everyone assumes these emails are an exact dump from Gmail,…
What's up with all those equals signs anyway?
21–30 of 200 posts
Re: What's up with all those equals signs anyway?
#22Earlier quoted context omitted.
I haven't seen them other than in the submission - but if the length matches up it may be that they were processed from raw email, the RFC defines a length to wrap at. Edit: yes I think that's most likely what it is (and it's SHOULD 78ch; MUST 998ch) - I was forgetting that it also specifies the CRLF usage, it's not (necessarily) related to Windows at all here as described in TFA. Here it is in my 'notmuch-more' emai…
> it's not (necessarily) related to Windows at all here as described in TFA. The article doesn't claim that it's Windows related. The article is very clear in explaining that the spec requires =CRLF (3 characters), then mentions (in passing) that CRLF is the typical line ending on Windows, then speculates that someone replaced the two characters CRLF with a one character new line, as on Unix or other OSs.
Re: What's up with all those equals signs anyway?
#23TLDR "=\r\n" was converted to "=\n"
Re: What's up with all those equals signs anyway?
#24Back in those days optical scanners were still used.
Re: What's up with all those equals signs anyway?
#25> We see that that’s a quite a long line. Mail servers don’t like that Why do mail server care about how long a line is? Why don't they just let the client reading the mail worry about wrapping the lines?
I suspect this is relevant because Quoted Printable was only a useful encoding for MIME types like text and HTML (the human readable email body), not binary (eg. Attachments, images, videos). Mail servers (if they want) can effectively treat the binary types as an opaque blob, while the text types can be read for more efficient transfer of message listings to the client.
Re: What's up with all those equals signs anyway?
#26Re: What's up with all those equals signs anyway?
#27Rock dots? You mean diacritics? Yeah someone invented them: the ancient Greeks, idiöt.
Re: What's up with all those equals signs anyway?
#28On a side note: There are actually products marketed as kosher bacon (it's usually beef or turkey). And secular Jews frequently make jokes like this about our kosher bros who aren't allowed to eat the real stuff for some dumb reason like it has too many toes.
Re: What's up with all those equals signs anyway?
#29> We see that that’s a quite a long line. Mail servers don’t like that Why do mail server care about how long a line is? Why don't they just let the client reading the mail worry about wrapping the lines?
Re: What's up with all those equals signs anyway?
#30Rock dots? You mean diacritics? Yeah someone invented them: the ancient Greeks, idiöt.