Re: OT: protonmail mail body

[Stuart Henderson]

On 2017-07-20, Rupert Gallagher  wrote:
> If you make business in Europe, or with people in Europe, then you know about 
> legal compliance with the Commision's standards, and their pdf and p7m signed 
> attachments. Similar standards exist in other countries, and they use mime 
> parts. If your email client cannot read mime parts, you are out of business. 
> If your email server rejects mime messages, you are out of business.
> Sent from ProtonMail Mobile
>
> On Thu, Jul 20, 2017 at 10:22 AM, Paul de Weerd  wrote:
>
>> On Thu, Jul 20, 2017 at 02:46:02AM -0400, Rupert Gallagher wrote: | Out of 
>> curiosity, I just checked what all the fuss is about. It turns out that 
>> someone reads mail with a non-RFC compliant client, and thus fails to read 
>> mime parts. Screw it, update your client. | The other problem seemed to be 
>> with the list archive. It turns out that at least one archive has no problem 
>> at all (*). If other archives have mime problems, they can update themselves 
>> or just delete the mail. All of this while large parts of the world consider 
>> those sending such mails to be spam (after spammers abused trick this to 
>> evade anti-spam solutions), never to deliver them. Your base64-encoded mime 
>> parts are braindead, but nobody is really worried: those e-mails will simply 
>> be ignored by those that might otherwise have had useful replies. Just 
>> because something is a standard, doesn't mean everybody should do it. There 
>> are (very many) harmful standards (caused in large part by a lack of 
>> ax-murderers, I hear). Ch
 eers, Paul 'WEiRD' de Weerd -- 
>[<++>-]<+++.>+++[<-->-]<.>+++[<+ 
+++>-]<.>++[<>-]<+.--.[-] 
http://www.weirdnet.nl/

1. This is not a business list. 

2. I can read the words you write. But it's such a jumbled up mess
that it's not worth taking the time to read them.

People posting to a technical mailing list, particularly if they're
asking for assistance, are expected to follow the standards of that
list.

Re: OT: protonmail mail body

[Allan Streib]

Rupert Gallagher  writes:

> If you make business in Europe, or with people in Europe, then you
> know about legal compliance with the Commision's standards, and their
> pdf and p7m signed attachments. Similar standards exist in other
> countries, and they use mime parts. If your email client cannot read
> mime parts, you are out of business. If your email server rejects mime
> messages, you are out of business.

None of which changes the terms of use for this list, which are (from
the FAQ):

Plain text, 72 characters per line

ALlan

Re: OT: protonmail mail body

[Rupert Gallagher]

If you make business in Europe, or with people in Europe, then you know about 
legal compliance with the Commision's standards, and their pdf and p7m signed 
attachments. Similar standards exist in other countries, and they use mime 
parts. If your email client cannot read mime parts, you are out of business. If 
your email server rejects mime messages, you are out of business.
Sent from ProtonMail Mobile

On Thu, Jul 20, 2017 at 10:22 AM, Paul de Weerd  wrote:

> On Thu, Jul 20, 2017 at 02:46:02AM -0400, Rupert Gallagher wrote: | Out of 
> curiosity, I just checked what all the fuss is about. It turns out that 
> someone reads mail with a non-RFC compliant client, and thus fails to read 
> mime parts. Screw it, update your client. | The other problem seemed to be 
> with the list archive. It turns out that at least one archive has no problem 
> at all (*). If other archives have mime problems, they can update themselves 
> or just delete the mail. All of this while large parts of the world consider 
> those sending such mails to be spam (after spammers abused trick this to 
> evade anti-spam solutions), never to deliver them. Your base64-encoded mime 
> parts are braindead, but nobody is really worried: those e-mails will simply 
> be ignored by those that might otherwise have had useful replies. Just 
> because something is a standard, doesn't mean everybody should do it. There 
> are (very many) harmful standards (caused in large part by a lack of 
> ax-murderers, I hear). Cheers, Paul 'WEiRD' de Weerd -- 
> >[<++>-]<+++.>+++[<-->-]<.>+++[<+ 
> +++>-]<.>++[<>-]<+.--.[-] 
> http://www.weirdnet.nl/

Re: OT: protonmail mail body

[Paul de Weerd]

On Thu, Jul 20, 2017 at 02:46:02AM -0400, Rupert Gallagher wrote:
| Out of curiosity, I just checked what all the fuss is about. It turns out 
that someone reads mail with a non-RFC compliant client, and thus fails to read 
mime parts. Screw it, update your client.
| The other problem seemed to be with the list archive. It turns out that at 
least one archive has no problem at all (*). If other archives have mime 
problems, they can update themselves or just delete the mail.

All of this while large parts of the world consider those sending such
mails to be spam (after spammers abused trick this to evade anti-spam
solutions), never to deliver them.

Your base64-encoded mime parts are braindead, but nobody is really
worried: those e-mails will simply be ignored by those that might
otherwise have had useful replies.  Just because something is a
standard, doesn't mean everybody should do it.  There are (very many)
harmful standards (caused in large part by a lack of ax-murderers, I
hear).

Cheers,

Paul 'WEiRD' de Weerd

-- 
>[<++>-]<+++.>+++[<-->-]<.>+++[<+
+++>-]<.>++[<>-]<+.--.[-]
 http://www.weirdnet.nl/ 

Re: OT: protonmail mail body

[Rupert Gallagher]

Out of curiosity, I just checked what all the fuss is about. It turns out that 
someone reads mail with a non-RFC compliant client, and thus fails to read mime 
parts. Screw it, update your client.
The other problem seemed to be with the list archive. It turns out that at 
least one archive has no problem at all (*). If other archives have mime 
problems, they can update themselves or just delete the mail.
http://openbsd-archive.7691.n7.nabble.com/OT-protonmail-mail-body-td322547.html
Sent from ProtonMail Mobile

On Thu, Jul 13, 2017 at 2:39 PM, Bryan Steele  wrote:

> On Wed, Jul 12, 2017 at 10:09:11AM +0200, Alarig Le Lay wrote: > Hello, > > 
> It's just Base64 Content-Transfer-Encoding, and it's part of rfc2045. > 
> https://tools.ietf.org/html/rfc2045#section-6.8 > > So, the problem is on 
> marc.info side. Moreover, it's working on > mutt and on mail-archive: > 
> https://www.mail-archive.com/misc@openbsd.org/msg154853.html > > -- > alarig 
> The mailing lists have very simple rules, messages should be in English, 
> plain/text and generally not be MIME. Attachments should be avoided and sent 
> inline, unless accepted by the list. https://www.openbsd.org/mail.html 
> "ProtonMail" does not meet these requirements, by defalt. It's not just 
> marc.info archives, I suspect anyone using mail(1) is ignoring all of your 
> mails. -Bryan.

Re: OT: protonmail mail body

[jungle Boogie]

On 18 July 2017 at 09:29, Eric Johnson  wrote:
>
> On Wed, 12 Jul 2017, Mihai Popescu wrote:
>
>> Hello,
>>
>> I preffer to keep it calm, but some people on the list are using
>> protonmail and their mails are impossible to read directly on the
>> list. I think they are destroying the list, maybe they should turn
>> that feature off. Here is what I see reading on marc.info:
>>
>> TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp
>> bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv
>> YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+
>> IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg
>> bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv
>> d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh
>> bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t
>> YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg
>> YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl
>> IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg
>> Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD
>> bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl
>> ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN
>> VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh
>> dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw==
>
> My primary e-mail address is on protonmail.  For testing purposes, I have
> sent e-mail from my protonmail account to a number of other accounts and
> have never had any problem reading the messages.  For example, on this
> account I use pine (alpine) to handle my e-mail and have never had a
> problem.
>

Oh, I get it! You can decode base64 in your head and read messages that way.
Dang, that's impressive. I know a couple people who know ASCII by
memory, but never anyone who can read base64.

> Eric
>



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info

Re: OT: protonmail mail body

[Theo de Raadt]

> As things stand, ProtonMail is not a suitable client for writing to this
> mailing list.
> 
> Your messages are nearly unreadable.

Maybe it should be blocked.  Then the users there can tell them to fix it.

Would have no downside for me.

Re: OT: protonmail mail body

[Theo de Raadt]

> On Wed, 12 Jul 2017, Mihai Popescu wrote:
> 
> > Hello,
> >
> > I preffer to keep it calm, but some people on the list are using
> > protonmail and their mails are impossible to read directly on the
> > list. I think they are destroying the list, maybe they should turn
> > that feature off. Here is what I see reading on marc.info:
> >
> > TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp
> > bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv
> > YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+
> > IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg
> > bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv
> > d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh
> > bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t
> > YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg
> > YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl
> > IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg
> > Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD
> > bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl
> > ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN
> > VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh
> > dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw==
> 
> My primary e-mail address is on protonmail.  For testing purposes, I have
> sent e-mail from my protonmail account to a number of other accounts and
> have never had any problem reading the messages.  For example, on this
> account I use pine (alpine) to handle my e-mail and have never had a
> problem.

If I see a mail which isn't plain text, I delete it.

If that means something doesn't get handled, bummer.

Re: OT: protonmail mail body

[Eric Johnson]

On Wed, 12 Jul 2017, Mihai Popescu wrote:

> Hello,
>
> I preffer to keep it calm, but some people on the list are using
> protonmail and their mails are impossible to read directly on the
> list. I think they are destroying the list, maybe they should turn
> that feature off. Here is what I see reading on marc.info:
>
> TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp
> bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv
> YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+
> IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg
> bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv
> d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh
> bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t
> YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg
> YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl
> IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg
> Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD
> bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl
> ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN
> VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh
> dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw==

My primary e-mail address is on protonmail.  For testing purposes, I have
sent e-mail from my protonmail account to a number of other accounts and
have never had any problem reading the messages.  For example, on this
account I use pine (alpine) to handle my e-mail and have never had a
problem.

Eric

Re: OT: protonmail mail body

[Bryan Steele]

On Wed, Jul 12, 2017 at 10:09:11AM +0200, Alarig Le Lay wrote:
> Hello,
> 
> It's just Base64 Content-Transfer-Encoding, and it's part of rfc2045.
> https://tools.ietf.org/html/rfc2045#section-6.8
> 
> So, the problem is on marc.info side. Moreover, it's working on
> mutt and on mail-archive:
> https://www.mail-archive.com/misc@openbsd.org/msg154853.html
> 
> -- 
> alarig

The mailing lists have very simple rules, messages should be in English,
plain/text and generally not be MIME. Attachments should be avoided and
sent inline, unless accepted by the list.

https://www.openbsd.org/mail.html

"ProtonMail" does not meet these requirements, by defalt. It's not just
marc.info archives, I suspect anyone using mail(1) is ignoring all of
your mails.

-Bryan.

Re: OT: protonmail mail body

[jungle Boogie]

On 12 July 2017 at 00:37, Mihai Popescu  wrote:
> Hello,
>
> I preffer to keep it calm, but some people on the list are using
> protonmail and their mails are impossible to read directly on the
> list. I think they are destroying the list, maybe they should turn
> that feature off. Here is what I see reading on marc.info:
>

I agree.
I was trying to read this list on the links browser last weekend and I
had to skip over many messages because of the base64 encoding issues.

Good to know about mail-archive. I'll have to see how that looks on
links, though.

Thanks!

Re: OT: protonmail mail body

[Stuart Henderson]

On 2017-07-12, Rupert Gallagher  wrote:
> I top post deliberately, out of sympathy. When you will be as old as I am, 
> you will find that scrolling a long thread to read a reply it pains your 
> hand. So, to avoid top posting, you have to scroll twice: to read, and to 
> write. I people top post by default, it would make things easier to everybody.
> On wrapping, protonmail does it by iself, and is a real problem. There is no 
> user setting to solve this problem. It is a bug.
> Sent from ProtonMail Mobile

As things stand, ProtonMail is not a suitable client for writing to this
mailing list.

Your messages are nearly unreadable.

Re: OT: protonmail mail body

[Kamil Cholewiński]

On Wed, 12 Jul 2017, Rupert Gallagher  wrote:
> I top post deliberately, out of sympathy. When you will be as old as I
> am, you will find that scrolling a long thread to read a reply it
> pains your hand. So, to avoid top posting, you have to scroll twice:
> to read, and to write. I people top post by default, it would make
> things easier to everybody.

My MUA does this:

> [ 8 more citation lines. Click/Enter to show. ]

Problem solved.

Re: OT: protonmail mail body

[Rupert Gallagher]

I top post deliberately, out of sympathy. When you will be as old as I am, you 
will find that scrolling a long thread to read a reply it pains your hand. So, 
to avoid top posting, you have to scroll twice: to read, and to write. I people 
top post by default, it would make things easier to everybody.
On wrapping, protonmail does it by iself, and is a real problem. There is no 
user setting to solve this problem. It is a bug.
Sent from ProtonMail Mobile

On Wed, Jul 12, 2017 at 11:30 AM, Theo Buehler  wrote:

> On Wed, Jul 12, 2017 at 04:54:24AM -0400, Rupert Gallagher wrote: > +1 
> Alright, the base64 transfer encoding thing is in the RFC... However, nowhere 
> does the RFC specify that you should top-post and strip all the newlines: > 
> On Wed, Jul 12, 2017 at 10:09 AM, Alarig Le Lay wrote: > > > On mer. 12 juil. 
> 10:37:59 2017, Mihai Popescu wrote: > Hello, > > I preffer to keep it calm, 
> but some people on the list are using > protonmail and their mails are 
> impossible to read directly on the > list. I think they are destroying the 
> list, maybe they should turn > that feature off. Here is what I see reading 
> on marc.info: > > 
> TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp > 
> bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv > 
> YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+ > 
> IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg > 
> bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv > 
> d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh > 
> bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t > 
> YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg > 
> YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl > 
> IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg > 
> Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD > 
> bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl > 
> ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN > 
> VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh > 
> dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw== Hello, It’s just 
> Base64 Content-Transfer-Encoding, and it’s part of rfc2045. 
> https://tools.ietf.org/html/rfc2045#section-6.8 So, the problem is on 
> marc.info side. Moreover, it’s working on mutt and on mail-archive: 
> https://www.mail-archive.com/misc@openbsd.org/msg154853.html -- alarig 
> @swordarmor.fr>

Re: OT: protonmail mail body

[Mihai Popescu]

On Wed, Jul 12, 2017 at 11:53 AM, Rupert Gallagher  wrote:
> Can you read me?
>
> Sent from ProtonMail Mobile

Yes, I can read what you wrote, but on Gmail only. I didn't know that
there is a RFC for this, I thought there is a feature offered by
protonmail. Bytheway, they look interesting to me.
The decoding part falls on marc.info then.

Thank you and I'm sorry for this.

Re: OT: protonmail mail body

[Theo Buehler]

On Wed, Jul 12, 2017 at 04:54:24AM -0400, Rupert Gallagher wrote:
> +1

Alright, the base64 transfer encoding thing is in the RFC...

However, nowhere does the RFC specify that you should top-post and strip
all the newlines:

> On Wed, Jul 12, 2017 at 10:09 AM, Alarig Le Lay  wrote:
> 
> > On mer. 12 juil. 10:37:59 2017, Mihai Popescu wrote: > Hello, > > I preffer 
> > to keep it calm, but some people on the list are using > protonmail and 
> > their mails are impossible to read directly on the > list. I think they are 
> > destroying the list, maybe they should turn > that feature off. Here is 
> > what I see reading on marc.info: > > 
> > TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp > 
> > bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv > 
> > YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+ > 
> > IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg > 
> > bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv > 
> > d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh > 
> > bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t > 
> > YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg > 
> > YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl > 
> > IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg > 
> > Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD > 
> > bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl > 
> > ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN > 
> > VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh > 
> > dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw== Hello, It’s 
> > just Base64 Content-Transfer-Encoding, and it’s part of rfc2045. 
> > https://tools.ietf.org/html/rfc2045#section-6.8 So, the problem is on 
> > marc.info side. Moreover, it’s working on mutt and on mail-archive: 
> > https://www.mail-archive.com/misc@openbsd.org/msg154853.html -- alarig

Re: OT: protonmail mail body

[Rupert Gallagher]

+1

On Wed, Jul 12, 2017 at 10:09 AM, Alarig Le Lay  wrote:

> On mer. 12 juil. 10:37:59 2017, Mihai Popescu wrote: > Hello, > > I preffer 
> to keep it calm, but some people on the list are using > protonmail and their 
> mails are impossible to read directly on the > list. I think they are 
> destroying the list, maybe they should turn > that feature off. Here is what 
> I see reading on marc.info: > > 
> TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp > 
> bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv > 
> YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+ > 
> IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg > 
> bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv > 
> d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh > 
> bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t > 
> YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg > 
> YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl > 
> IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg > 
> Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD > 
> bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl > 
> ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN > 
> VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh > 
> dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw== Hello, It’s just 
> Base64 Content-Transfer-Encoding, and it’s part of rfc2045. 
> https://tools.ietf.org/html/rfc2045#section-6.8 So, the problem is on 
> marc.info side. Moreover, it’s working on mutt and on mail-archive: 
> https://www.mail-archive.com/misc@openbsd.org/msg154853.html -- alarig

Re: OT: protonmail mail body

[Rupert Gallagher]

Can you read me?
Sent from ProtonMail Mobile

On Wed, Jul 12, 2017 at 9:37 AM, Mihai Popescu  wrote:

> Hello, I preffer to keep it calm, but some people on the list are using 
> protonmail and their mails are impossible to read directly on the list. I 
> think they are destroying the list, maybe they should turn that feature off. 
> Here is what I see reading on marc.info: 
> TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp 
> bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv 
> YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+ 
> IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg 
> bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv 
> d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh 
> bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t 
> YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg 
> YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl 
> IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg 
> Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD 
> bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl 
> ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN 
> VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh 
> dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw==

Re: OT: protonmail mail body

[Alarig Le Lay]

On mer. 12 juil. 10:37:59 2017, Mihai Popescu wrote:
> Hello,
> 
> I preffer to keep it calm, but some people on the list are using
> protonmail and their mails are impossible to read directly on the
> list. I think they are destroying the list, maybe they should turn
> that feature off. Here is what I see reading on marc.info:
> 
> TmV2ZXIgaGVhcmQgb2YgVk5DPwpTZW50IGZyb20gUHJvdG9uTWFpbCBNb2Jp
> bGUKCk9uIFR1ZSwgSnVsIDExLCAyMDE3IGF0IDg6MzkgUE0sIE5pZWxzIEtv
> YnNjaMOkdHpraSA8bmllbHNAa29ic2NoYWV0emtpLm5ldD4gd3JvdGU6Cgo+
> IEhpLCBJIGFtIHBvbmRlcmluZyB0byBpbnN0YWxsIE9wZW5CU0Qgb24gbXkg
> bWFpbiBtYWNoaW5lLiBCdXQgSSBqdXN0IGZvdW5kIGEgcG9zc2libGUgc2hv
> d3N0b3BwZXI6IGZhbWlseSByZW1vdGUgc3VwcG9ydCBSaWdodCBub3cgSSBh
> bSB1c2luZyBUZWFtdmlld2VyIHRvIGNvbm5lY3QgZnJvbSBteSBMaW51eC1t
> YWNoaW5lIHRvIHRoZSBmYW1pbHktTWFjLiBOb3cgSSBhbSBzZWFyY2hpbmcg
> YSBzaW1pbGFyIGVhc3kgd2F5IHRvIGRvIHRoYXQgZnJvbSBhIHBvc3NpYmxl
> IE9wZW5CU0QtbWFjaGluZS4gSXMgdGhlcmUgYW55IHNvZnR3YXJlIHRoYXQg
> Y291bGQgZG8gdGhhdD8gQXNraW5nIHRoZW0gZm9yIHRoZWlyIElQIG9yIGlD
> bG91ZC1ob3N0bmFtZSB3b3VsZCBhbHJlYWR5IGJlIHRvbyBjb21wbGljYXRl
> ZC4gV2hhdCBhcmUgeW91IHVzaW5nIGluIHN1Y2ggY2FzZXM/IElzIGEgUUVN
> VS1WTSBwZXJmb3JtYW50IGVub3VnaCBmb3Igc3VjaCBhIHRoaW5nIChJIGhh
> dmUgYSBUaGlua3BhZCBUNDYwIHdpdGggYSBTa3lsYWtlLWk1KSBOaWVscw==

Hello,

It’s just Base64 Content-Transfer-Encoding, and it’s part of rfc2045.
https://tools.ietf.org/html/rfc2045#section-6.8

So, the problem is on marc.info side. Moreover, it’s working on
mutt and on mail-archive:
https://www.mail-archive.com/misc@openbsd.org/msg154853.html

-- 
alarig


signature.asc
Description: PGP signature