On 16/04/18 03:44, Phil Pennock wrote:
While double-checking logs after an MTA update, I saw something from
Gmail which is ... bemusing.  I'm wondering if there's any consensus on
how this should be handled in a manner which scales, given that Gmail
don't publish DANE records?

2018-04-16 01:14:55 [95041] 1f7sjN-000Oiu-7W
    => <censored>@gmail.com
    R=outbound_signed T=remote_dksign
    H=gmail-smtp-in.l.google.com []:25
    X=TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256 CV=no
    DN="/OU=No SNI provided; please fix your client./CN=invalid2.invalid"
    K C="250 2.0.0 OK q15si10692445edd.343 - gsmtp" QT=1s DT=0s

I don't get this, I get the usual stuff:
2018-04-16 09:29:10.848 [8077] 1f7yZR-0000PJ-ML
S=7618 H=gmail-smtp-in.l.google.com []:25 I=[]:3554 X=TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256 CV=yes DN="/C=US/ST=California/L=Mountain View/O=Google Inc/CN=mx.google.com" K C="250 2.0.0 OK p91si8786056edp.99 - gsmtp" QT=9s DT=0.885s

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

mailop mailing list

Reply via email to