On Sat, Apr 2, 2016 at 10:40 AM, Carl Byington wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On Sat, 2016-04-02 at 11:42 -0500, frnk...@iname.com wrote:
> > Anyone aware of email servers that take the approach that CloudFlare
> > has, which is not allow the lowest common denomina
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sat, 2016-04-02 at 11:42 -0500, frnk...@iname.com wrote:
> Anyone aware of email servers that take the approach that CloudFlare
> has, which is not allow the lowest common denominator or cleartext to
> be used if there's a better/more-secure ciphe
Gmail red open padlock composing message
On 31/03/16 17:38, Kirk MacDonald wrote:
> With thanks to Google for pushing the cause, I implemented STARTTLS
> functionality on my org’s MX (as well as outbound SMTP with
> opportunistic STARTTLS).
Firstly - well done for doing it. Everybody sho
Henson
Sent: Friday, April 01, 2016 12:07 PM
To: mailop@mailop.org
Subject: Re: [mailop] Gmail red open padlock composing message
http://blogs.technet.com/b/exchange/archive/2015/07/27/exchange-tls-amp-ssl-best-practices.aspx
Exchange 2003 is out of support.
Exchange 2007 support ends 4/11
ailop-boun...@mailop.org] On Behalf Of Franck Martin
> via mailop
> Sent: Friday, April 1, 2016 11:27 AM
> To: Kirk MacDonald
> Cc: mailop@mailop.org; Tim Bray
>
>
> Subject: Re: [mailop] Gmail red open padlock composing message
>
>
>
> RC4 is a conundrum, it is abou
, but my PCI
scanning vendor disagrees.
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Franck Martin via
mailop
Sent: Friday, April 1, 2016 11:27 AM
To: Kirk MacDonald
Cc: mailop@mailop.org; Tim Bray
Subject: Re: [mailop] Gmail red open padlock composing message
RC4 is a conundrum
future.
>
>
> -Original Message-
> From: Tim Bray [mailto:t...@kooky.org]
> Sent: Friday, April 01, 2016 5:58 AM
> To: Kirk MacDonald ; mailop@mailop.org
> Subject: Re: [mailop] Gmail red open padlock composing message
>
> On 31/03/16 17:38, Kirk MacDonald wrote:
[mailto:t...@kooky.org]
Sent: Friday, April 01, 2016 5:58 AM
To: Kirk MacDonald ; mailop@mailop.org
Subject: Re: [mailop] Gmail red open padlock composing message
On 31/03/16 17:38, Kirk MacDonald wrote:
> With thanks to Google for pushing the cause, I implemented STARTTLS
> functionality on my
Brandon,
Thank you for your efforts.
Kirk
From: Brandon Long [mailto:bl...@google.com]
Sent: Thursday, March 31, 2016 9:10 PM
To: Franck Martin
Cc: Kirk MacDonald ; mailop@mailop.org
Subject: Re: [mailop] Gmail red open padlock composing message
I've pinged the team to see what the upda
On 31/03/16 17:38, Kirk MacDonald wrote:
> With thanks to Google for pushing the cause, I implemented STARTTLS
> functionality on my org’s MX (as well as outbound SMTP with
> opportunistic STARTTLS).
Firstly - well done for doing it. Everybody should be enabling TLS.
Did you test the install?
I've pinged the team to see what the update is, but my guess is it's a
daily log processing job, so we have to actually send you mail to validate
it.
Looks like you enabled it between 5-6am PDT, not sure what their cut-off is
for percentage success or what, so it might be two days for your traffic
I wanted to add, make sure you have compatible ciphers, you may have
enabled STARTTLS but if you cannot negotiate a cypher, then the point is
moot ;)
A packet capture when STARTTLS is initiated will tell you what ciphers are
offered and which one is negotiated.
On Thu, Mar 31, 2016 at 12:03 PM, F
I guess, once they have positive data on your domain, they should update
the icon:
https://www.google.com/transparencyreport/saferemail/#search=eastlink.ca
On Thu, Mar 31, 2016 at 9:38 AM, Kirk MacDonald <
kirk.macdon...@corp.eastlink.ca> wrote:
> With thanks to Google for pushing the cause, I im
With thanks to Google for pushing the cause, I implemented STARTTLS
functionality on my org’s MX (as well as outbound SMTP with opportunistic
STARTTLS).
Does anyone have any insight into how long it might take Gmail to acknowledge
the STARTTLS availability when composing a new message to a doma
14 matches
Mail list logo
