We all have to make sacrifices.

They say the engagement ring should be two months of salary, so a single chip of DDR5 should do.

Thank you too. I’m glad I don’t have that incorrect factoid in my head now! :D

That’s the unfortunate reality. Google can force their will on the internet because they own around 35% of all email. And Microsoft owns another ~35%, so if the two decide to change how email works, it’s everyone else who has to conform.

Yep, you are right. So Gmail is following the spec, but still altering headers. So at least it’s not breaking the email, just breaking the authentication.

Atom is defined as such:

atext           =       ALPHA / DIGIT / ; Any character except controls,
                        "!" / "#" /     ;  SP, and specials.
                        "$" / "%" /     ;  Used for atoms
                        "&" / "'" /
                        "*" / "+" /
                        "-" / "/" /
                        "=" / "?" /
                        "^" / "_" /
                        "`" / "{" /
                        "|" / "}" /
                        "~"

atom            =       [CFWS] 1*atext [CFWS]

So since atom does not contain white space, there should be no white space. Only comments can separate 1*atom.

If they wanted to allow separating atoms by a space, it would be written:

atom *(SP atom)

Edit: wait, I’m wrong. CFWS includes white space. You’re right.

Folding white space is a different issue. It’s the atom / quoted-string part. That’s the standard form of a display name. Meaning if it’s more than one word (separated by white space), it should use the quoted string form. It does list obs-phrase as an alternative, but using obsolete syntax should be avoided when possible.

The section right below shows that it’s obsolete:

A.6.1. Obsolete addressing

   Note in the below example the lack of quotes around Joe Q. Public,
   the route that appears in the address for Mary Smith, the two commas
   that appear in the "To:" field, and the spaces that appear around the
   "." in the jdoe address.

----
From: Joe Q. Public <john.q.public@example.com>
To: Mary Smith <@machine.tld:mary@example.net>, , jdoe@test   . example
Date: Tue, 1 Jul 2003 10:52:37 +0200
Message-ID: <5678.21-Nov-1997@example.com>

Hi everyone.
----

And in the spec itself, that syntax is named as “obs-phrase”.

But yes, though obsolete, it is still legal syntax. So I guess I shouldn’t say it “does not conform to the standard”, but rather “just barely conforms to the standard”.

Lettre is following the spec, where if the display name contains a space, the modern way to encode it is to put quotes around it.

Quotes around the display name in a header certainly conforms to the standard (and in fact, the way Gmail rewrites it does not conform to the standard when it contains a space, but is the obsolete form), and I would expect any decent mail program to leave it alone. Then again, Gmail is not a decent mail program, and hasn’t been for a long time.

Edit: @[email protected] points out below that Gmail’s rewrite does follow the spec, so it is conforming to the standard when white space is in the display name. It’s only when there is a dot (.) that it would be using the obsolete form.

Yeah, I understand how the mail that Gmail receives is not necessarily the mail that the user sent (in regards to headers), and I understand Gmail can add headers (like auth results, spam scores, other sorts of records), but is Gmail really changing the “From” header or other headers included in the DKIM signature?? I would think that would be absolutely unacceptable.

Wait, so when you download what is supposed to be the original email from Gmail, it’s not actually the original? How is that ok?

Let me do it for you, kermie.

How dare you steal our technology! We stole it first!

VDO Ninja is really nice. My friend self hosts it, and it didn’t seem that hard.

There are plenty of easy to set up open source servers. I use a bunch of them. Here’s a few that come to mind:

• jellyseerr
• navidrome
• jswiki
• homeassistant
• docmost
• rustdesk

Those are all ones that only require three or fewer services in a Docker Compose stack. And the docker-compose.yml files are short and easy to understand.

There are plenty that are hard to set up, like:

• jellyfin
• nextcloud
• wordpress
• immich
• mastodon

I’ve installed all of these, and they were not as straightforward, but not too bad.

Matrix is the only one that has taken me more than a day. And I couldn’t even get everything working. Element Call still doesn’t work after trying to set it up for two days.

There is a lot of variance in how difficult these servers are to set up, but Matrix stands alone as the absolute hardest, most convoluted setup process I’ve ever experienced.

That’s legal… for now.

Because the performance gain was basically negligible. That was their explanation in the issue.

What appears to be the person behind the agent resubmitted the PR with a passive aggressive bullshit comment:

https://github.com/matplotlib/matplotlib/pull/31138#issuecomment-3890808045

Not to my knowledge.