So I got a user report that exmh was doing something weird with bcc:. I looked at the exmh code, which doesn't do anything special with bcc:, it just assumes that the underlying nmh will DTRT. So.. I go to test nmh. As tested, it had: From: "Valdis =?utf-8?Q?Kl=c4=93tnieks?=" <Valdis.Kletnieks@vt.edu> To: valdis.kletnieks@gmail.com bcc: valdis@vt.edu Fcc: +outbox Subject: Test of bcc: nmh -------- adsfasdf And I do a 'send -watch -snoop', and the relevant part of the transcript says: (tls-encrypted) => MAIL FROM:<Valdis.Kletnieks@vt.edu> (tls-decrypted) <= 250 2.1.0 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => RCPT TO:<valdis.kletnieks@gmail.com> (tls-decrypted) <= 250 2.1.5 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => RCPT TO:<valdis@vt.edu> (tls-decrypted) <= 250 2.1.5 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => RSET (tls-decrypted) <= 250 2.1.5 Flushed o16sm4571323qki.110 - gsmtp (tls-encrypted) => MAIL FROM:<Valdis.Kletnieks@vt.edu> (tls-decrypted) <= 250 2.1.0 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => RCPT TO:<valdis.kletnieks@gmail.com> (tls-decrypted) <= 250 2.1.5 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => DATA (tls-decrypted) <= 354 Go ahead o16sm4571323qki.110 - gsmtp (tls-encrypted) => . (tls-decrypted) <= 250 2.0.0 OK 1586650839 o16sm4571323qki.110 - gsmtp (tls-encrypted) => RSET (tls-decrypted) <= 250 2.1.5 Flushed o16sm4571323qki.110 - gsmtp (tls-encrypted) => MAIL FROM:<Valdis.Kletnieks@vt.edu> (tls-decrypted) <= 250 2.1.0 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => RCPT TO:<valdis@vt.edu> (tls-decrypted) <= 250 2.1.5 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => DATA (tls-decrypted) <= 354 Go ahead o16sm4571323qki.110 - gsmtp (tls-encrypted) => . (tls-decrypted) <= 250 2.0.0 OK 1586650840 o16sm4571323qki.110 - gsmtp (tls-encrypted) => QUIT (tls-decrypted) <= 221 2.0.0 closing connection o16sm4571323qki.110 - gsmtp which looks to me like it tried both destinations, got 250 back for them.. ... and then did an RSET and sent as two separate SMTP transactions. which had me going WTF?? (and it of course didn't help my mood that this doesn't match the reported problem behavior, which sounds like 'send' did a 'forw -mime', but the embedded message wasn't recognized as MIME message/822 and all the headers displayed in the body of the message, which of course confused all the non-expert recipients...)
pgpccia7yiK5w.pgp
Description: PGP signature