Re: send bcc: wierdness?

[Robert Elz]

    Date:        Sun, 12 Apr 2020 05:17:19 -0400
    From:        "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <address@hidden>
    Message-ID:  <423943.1586683039@turing-police>

  | Well, the -snoop output was pretty clear that Google's inbound
  | listener on port 587 gave back a 250 OK on both addresses:

Yes, so both were OK, which means it is OK to transmit the message.

That needed to be done in two different SMTP transactions, to avoid
revealing the bcc user's address to the other user (nmkh doesn't
know they're both you).

  | it's even more broken than we thought....

Not broken at all, it is doing exactly what it was supposed to do.
It's just that doing the Rcpt To pre-check these days is mostly
a waste of time, as everyone simply says OK to every syntactically
correct address they're handed (and of course, nmh/MH would never pass
on a syntatically invalid address).

kre