On Sun, 12 Apr 2020 14:54:31 +0700, Robert Elz said: > That will be do that is one of the addresses is bad (and the receiving > MTA can work that out - which it once would have often done, and sadly these > days, amost never) then the message gets delivered to no-one, rather than
Well, the -snoop output was pretty clear that Google's inbound listener on port 587 gave back a 250 OK on both addresses: (tls-encrypted) => MAIL FROM:<valdis.kletni...@vt.edu> (tls-decrypted) <= 250 2.1.0 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => RCPT TO:<valdis.kletni...@gmail.com> (tls-decrypted) <= 250 2.1.5 OK o16sm4571323qki.110 - gsmtp (tls-encrypted) => RCPT TO:<val...@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.kletni...@vt.edu> (It then goes on to correctly send one copy to each destination) So if it was supposed to retry if one address was bad, it's even more broken than we thought....
pgpb2UD3AalNg.pgp
Description: PGP signature
