Is Google planning on updating the certificate for smtp.gmail.com port
465? I noticed that it's expiring today which could cause a lot of
issues with email clients sending email today and tommorow.
> Is Google planning on updating the certificate for smtp.gmail.com port
> 465? I noticed that it's expiring today which could cause a lot of
> issues with email clients sending email today and tommorow.
> > Is Google planning on updating the certificate for smtp.gmail.com port
> > 465? I noticed that it's expiring today which could cause a lot of
> > issues with email clients sending email today and tommorow.
I've never seen someone go this close to the wire with renewing a
certificate. I already see a couple more messages with people getting
the error.. Google better get on their game on this one. especially
for large corps that use Google Apps for email!
Of course, trying to contact them is like trying to contact the
president..
> It's also impacting IMAP clients sending via port # 587
> EB
> On Jul 29, 1:01 pm, Hatfinch wrote:
> > On Jul 29, 1:54 pm, bvstone wrote:
> > > Is Google planning on updating the certificate for smtp.gmail.com port
> > > 465? I noticed that it's expiring today which could cause a lot of
> > > issues with email clients sending email today and tommorow.
> > Is Google planning on updating the certificate forsmtp.gmail.com port
> > 465? I noticed that it's expiring today which could cause a lot of
> > issues with email clients sending email today and tommorow.
Good timing with the possible attack on DNS servers out this week. I
makes you worry that maybe your connecting to a fake server via a DNS
redirection hack. I had to run several test against my office DNS
servers to verify they were patched and working correctly as well as
my ISP's DNS servers. Then I could allow people to send messages and
ignore the warning.
> Good timing with the possible attack on DNS servers out this week. I
> makes you worry that maybe your connecting to a fake server via a DNS
> redirection hack. I had to run several test against my office DNS
> servers to verify they were patched and working correctly as well as
> my ISP's DNS servers. Then I could allow people to send messages and
> ignore the warning.