If the server is saying your client connection is verify=FAIL/NO, I would imagine that means either you have a client certificate that doesn't verify, or you don't have a client certificate the remote server is being pedantic about it.
Brandon On Wed, Apr 13, 2016 at 2:56 PM, Robert Guthrie <rguth...@gmail.com> wrote: > Hello List, > > I wonder if someone could tell me about the verify=FAIL messages I'm > seeing in email headers sent from my SMTP's. > > Received: from loomio.io (errbit.loomio.org [45.55.128.240]) > by smtp.loomio.io (Haraka/2.8.0-alpha.7) with ESMTPSA id > 632790F7-CF56-4481-ACBA-2CBACE7EB8BB.1 > envelope-from <err...@loomio.io> (authenticated bits=0) > (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 *verify=FAIL*); > Wed, 13 Apr 2016 21:05:59 +0000 > > > If I'm seeing this, is there something I can or should do to resolve this? > Sometimes I see verify=NO also. > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
