1. 12
  1.  

  2. 5

    This illustrates the difference between the “envelope” and the “message” and shows, for example, how SMTP handles BCC’d emails.

    (Also…what a wonderful, atavistic anachronism “BCC” is. When was the last time you used carbon paper for anything?)

    To BCC something, you put the recipients’ emails in the RCPT TO commands and something like undisclosed-recipients in the To header in the message headers.

    SMTP is such a wonderfully fun protocol to know and play with.

    1. 2

      When was the last time you used carbon paper for anything?

      Every time I write a cheque.

      Would this technique work nowadays? Mail servers seem to spam check the From header

      1. 2

        I would be surprised if it did work now because the author is putting an @gmail.com address in reply-to, which should get their mail rejected by both SPF and DKIM checks

    2. 2

      Hah! So like a D-mail from Steins;Gate.

      1. 1

        I remember doing this in the mid 90s, around when I was starting high school.

        It’s sad email is still around and is so widespread. I’d been hopeful DIME would be ready by now.

        1. 2

          From what I can see by a cursory googling, DIME was superseded by SOAP in the early 2000s. SOAP, of course, is Old and Busted(tm) now, so I guess someone is working on reinventing SMTP using JSON.

          1. 1

            By DIME I meant this DIME.

            1. 2

              They need to up their Google game, the first hit for “dime message format” is the ancient Microsoft proposal.

              1. 1

                I’m surprised that people are still using Google’s websearch.

                For me, every time I try to search something on it, I get a first page of results full of obvious scam or malware download sites.

                From that, I understand Google doesn’t care anymore.

                1. 3

                  Oh, they care… they just don’t care about you. Or anything that you or I care about.

          2. 2

            On TCP/IP networks, nothing will ever fully replace SMTP/POP email. Path dependence; network effects. Email is a prime, textbook-quality example of technological lock-in. But I concur, it is sad.

            1. 1

              DIME offers the end-to-end always-on encryption smtp/pop do not and will never, because plaintext is rooted into it.

              There’s some demand, or there should be, for these features. It could be seen as a legal/compliance requirement, too. And that would allow an smtp replacement to take off.