This probably isn't the best place to post this, but we're seeing a
certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
certificate. Hope someone from Google is watching and can alert
someone to renew or replace the cert.
> This probably isn't the best place to post this, but we're seeing a
> certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> certificate. Hope someone from Google is watching and can alert
> someone to renew or replace the cert.
> This probably isn't the best place to post this, but we're seeing a
> certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> certificate. Hope someone from Google is watching and can alert
> someone to renew or replace the cert.
> This probably isn't the best place to post this, but we're seeing a
> certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> certificate. Hope someone from Google is watching and can alert
> someone to renew or replace the cert.
> Well, that certainly explains all the errors people have been
> receiving. =)
> On Jul 29, 12:55 pm, Bret <bret91...@gmail.com> wrote:
> > This probably isn't the best place to post this, but we're seeing a
> > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > certificate. Hope someone from Google is watching and can alert
> > someone to renew or replace the cert.
> I just got off the phone with a Google rep. They;re working on it.
> Their backup SMTP option is smtp.googlemail.com. It works fine for
> me.
> On Jul 29, 12:59 pm, askrenes <askre...@gmail.com> wrote:
> > Well, that certainly explains all the errors people have been
> > receiving. =)
> > On Jul 29, 12:55 pm, Bret <bret91...@gmail.com> wrote:
> > > This probably isn't the best place to post this, but we're seeing a
> > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > certificate. Hope someone from Google is watching and can alert
> > > someone to renew or replace the cert.
Yes, this is a known issue and we should have a resolution in the next
hour. In the meantime, using the alternate server listed here in this
thread is a good option.
We apologize for any inconvenience this may have caused.
- Mark
On Jul 29, 11:17 am, brianmcallester <brianmcalles...@gmail.com>
wrote:
> > > > This probably isn't the best place to post this, but we're seeing a
> > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > certificate. Hope someone from Google is watching and can alert
> > > > someone to renew or replace the cert.
> Yes, this is a known issue and we should have a resolution in the next
> hour. In the meantime, using the alternate server listed here in this
> thread is a good option.
> We apologize for any inconvenience this may have caused.
> - Mark
> On Jul 29, 11:17 am, brianmcallester <brianmcalles...@gmail.com>
> wrote:
> > Same issue here -- thanks for the smtp.googlemail.com option, we'll
> > give that a whirl.
> > On Jul 29, 2:14 pm, askrenes <askre...@gmail.com> wrote:
> > > I just got off the phone with a Google rep. They;re working on it.
> > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > me.
> > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > certificate. Hope someone from Google is watching and can alert
> > > > > someone to renew or replace the cert.
> Yes, this is a known issue and we should have a resolution in the next
> hour. In the meantime, using the alternate server listed here in this
> thread is a good option.
> We apologize for any inconvenience this may have caused.
> - Mark
> On Jul 29, 11:17 am, brianmcallester <brianmcalles...@gmail.com>
> wrote:
> > Same issue here -- thanks for the smtp.googlemail.com option, we'll
> > give that a whirl.
> > On Jul 29, 2:14 pm, askrenes <askre...@gmail.com> wrote:
> > > I just got off the phone with a Google rep. They;re working on it.
> > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > me.
> > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > certificate. Hope someone from Google is watching and can alert
> > > > > someone to renew or replace the cert.
> <advisor.m...@google.com> wrote:
> > Hi Everyone,
> > Yes, this is a known issue and we should have a resolution in the next
> > hour. In the meantime, using the alternate server listed here in this
> > thread is a good option.
> > We apologize for any inconvenience this may have caused.
> > > > I just got off the phone with a Google rep. They;re working on it.
> > > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > > me.
> > > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > > certificate. Hope someone from Google is watching and can alert
> > > > > > someone to renew or replace the cert.
> <advisor.m...@google.com> wrote:
> > Hi Everyone,
> > Yes, this is a known issue and we should have a resolution in the next
> > hour. In the meantime, using the alternate server listed here in this
> > thread is a good option.
> > We apologize for any inconvenience this may have caused.
> > > > I just got off the phone with a Google rep. They;re working on it.
> > > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > > me.
> > > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > > certificate. Hope someone from Google is watching and can alert
> > > > > > someone to renew or replace the cert.
> Help! My email has not been working for a week and that
> smtp.googlemail.com thing is not working for me.
> Help me.
> On Jul 29, 4:16 pm, Google Apps Advisor Mark <advisor.m...@google.com>
> wrote:
> > This issue is now resolved.
> > Thanks for everyone's patience.
> > - Mark
> > On Jul 29, 11:23 am, Google Apps Advisor Mark
> > <advisor.m...@google.com> wrote:
> > > Hi Everyone,
> > > Yes, this is a known issue and we should have a resolution in the next
> > > hour. In the meantime, using the alternate server listed here in this
> > > thread is a good option.
> > > We apologize for any inconvenience this may have caused.
> > > > > I just got off the phone with a Google rep. They;re working on it.
> > > > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > > > me.
> > > > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > > > certificate. Hope someone from Google is watching and can alert
> > > > > > > someone to renew or replace the cert.
> Help! My email has not been working for a week and that
> smtp.googlemail.com thing is not working for me.
> Help me.
> On Jul 29, 4:16 pm, Google Apps Advisor Mark <advisor.m...@google.com>
> wrote:
> > This issue is now resolved.
> > Thanks for everyone's patience.
> > - Mark
> > On Jul 29, 11:23 am, Google Apps Advisor Mark
> > <advisor.m...@google.com> wrote:
> > > Hi Everyone,
> > > Yes, this is a known issue and we should have a resolution in the next
> > > hour. In the meantime, using the alternate server listed here in this
> > > thread is a good option.
> > > We apologize for any inconvenience this may have caused.
> > > > > I just got off the phone with a Google rep. They;re working on it.
> > > > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > > > me.
> > > > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > > > certificate. Hope someone from Google is watching and can alert
> > > > > > > someone to renew or replace the cert.
I have no idea what any of that means. All I know is that my email no
longer works; I receive about 50% of the messages that are sent to my
account and I have made no changes to my account. What is going on
and why won't Google fix the problem? I receive error messages that
say my domain name has permanent fatal errors and the messages bounce
back to the sender.
I have lost valuable data in email messages due to this problem, and
even though I am only a Standard member, I am frustrated that I can't
report a bug (except on this random forum) and that I can't get anyone
to address the issues. I have consistently enjoyed Google's products
and supported them, but I think this is a major, major flaw. No user
support? No bug reporting? For a bug that was created by Google?
Wow.
On Jul 30, 3:44 pm, cyocom <camey.yo...@gmail.com> wrote:
> > > > Yes, this is a known issue and we should have a resolution in the next
> > > > hour. In the meantime, using the alternate server listed here in this
> > > > thread is a good option.
> > > > We apologize for any inconvenience this may have caused.
> > > > > > I just got off the phone with a Google rep. They;re working on it.
> > > > > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > > > > me.
> > > > > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > > > > certificate. Hope someone from Google is watching and can alert
> > > > > > > > someone to renew or replace the cert.
However, you mention that you're not receiving all your mail and
senders are receiving bounce messages. That sounds like a separate
issue unrelated to the IMAP issue. If you're still experiencing
problems, please provide your domain name so the group can assist. I
suspect there might be something wrong with your MX records, you can
check your MX records in Section 4 at http://www.google.com/support/a/bin/answer.py?hl=en&answer=33352.
If it's joshuataton.com (looking at your profile's email address) then
everything does check out with your MX records so we'd want to look
deeper.
We appreciate your honest feedback, and the group here can help
resolve your issue ASAP.
- Mark
On Jul 31, 7:35 am, JOSH <administra...@joshuataton.com> wrote:
> I have no idea what any of that means. All I know is that my email no
> longer works; I receive about 50% of the messages that are sent to my
> account and I have made no changes to my account. What is going on
> and why won't Google fix the problem? I receive error messages that
> say my domain name has permanent fatal errors and the messages bounce
> back to the sender.
> I have lost valuable data in email messages due to this problem, and
> even though I am only a Standard member, I am frustrated that I can't
> report a bug (except on this random forum) and that I can't get anyone
> to address the issues. I have consistently enjoyed Google's products
> and supported them, but I think this is a major, major flaw. No user
> support? No bug reporting? For a bug that was created by Google?
> Wow.
> On Jul 30, 3:44 pm, cyocom <camey.yo...@gmail.com> wrote:
> > Try using smtp.gmail.com on port 465 or 587 for SSL. Elliot from the
> > Google Apps team helped out with this.
> > On Jul 30, 3:30 pm, WarriorKnight <lisaki...@gmail.com> wrote:
> > > Help! My email has not been working for a week and that
> > > smtp.googlemail.com thing is not working for me.
> > > Help me.
> > > On Jul 29, 4:16 pm, Google Apps Advisor Mark <advisor.m...@google.com>
> > > wrote:
> > > > This issue is now resolved.
> > > > Thanks for everyone's patience.
> > > > - Mark
> > > > On Jul 29, 11:23 am, Google Apps Advisor Mark
> > > > > Yes, this is a known issue and we should have a resolution in the next
> > > > > hour. In the meantime, using the alternate server listed here in this
> > > > > thread is a good option.
> > > > > We apologize for any inconvenience this may have caused.
> > > > > > > I just got off the phone with a Google rep. They;re working on it.
> > > > > > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > > > > > me.
> > > > > > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > > > > > certificate. Hope someone from Google is watching and can alert
> > > > > > > > > someone to renew or replace the cert.
Thanks, Mark. From reading the Google Groups pages, though, I am FAR
from the only person experiencing this problem. My MX settings are
not the problem, since I purchased the domain name from Google (and
yes I checked them as instructed). I have not changed any settings on
my account whatsoever and the problem started happening suddenly.
Other users are experiencing the same problems and it appears possibly
related to Enom and possibly related to AOL.
If Google had a bug-reporting feature, we could report it, it could
get logged into a database and action could be taken. But, instead,
we have to reply on futile posts on this forum! Very frustrating.
Once again, this is a problem that MANY apps users appear to suddenly
be having within the last week or two. It does appear connected to
AOL at least that is how I am trying to send/receive emails to my
domain name account and they are still not working as of last night.
About 40-50% of the messages go through and the others bounce. Size
of the emails seems to have nothing to do with it, nor does
attachments / no attachments.
On Aug 4, 11:00 am, Google Apps Advisor Mark <advisor.m...@google.com>
wrote:
> However, you mention that you're not receiving all your mail and
> senders are receiving bounce messages. That sounds like a separate
> issue unrelated to the IMAP issue. If you're still experiencing
> problems, please provide your domain name so the group can assist. I
> suspect there might be something wrong with your MX records, you can
> check your MX records in Section 4 athttp://www.google.com/support/a/bin/answer.py?hl=en&answer=33352.
> If it's joshuataton.com (looking at your profile's email address) then
> everything does check out with your MX records so we'd want to look
> deeper.
> We appreciate your honest feedback, and the group here can help
> resolve your issue ASAP.
> - Mark
> On Jul 31, 7:35 am, JOSH <administra...@joshuataton.com> wrote:
> > I have no idea what any of that means. All I know is that my email no
> > longer works; I receive about 50% of the messages that are sent to my
> > account and I have made no changes to my account. What is going on
> > and why won't Google fix the problem? I receive error messages that
> > say my domain name has permanent fatal errors and the messages bounce
> > back to the sender.
> > I have lost valuable data in email messages due to this problem, and
> > even though I am only a Standard member, I am frustrated that I can't
> > report a bug (except on this random forum) and that I can't get anyone
> > to address the issues. I have consistently enjoyed Google's products
> > and supported them, but I think this is a major, major flaw. No user
> > support? No bug reporting? For a bug that was created by Google?
> > Wow.
> > On Jul 30, 3:44 pm, cyocom <camey.yo...@gmail.com> wrote:
> > > Try using smtp.gmail.com on port 465 or 587 for SSL. Elliot from the
> > > Google Apps team helped out with this.
> > > > > > Yes, this is a known issue and we should have a resolution in the next
> > > > > > hour. In the meantime, using the alternate server listed here in this
> > > > > > thread is a good option.
> > > > > > We apologize for any inconvenience this may have caused.
> > > > > > > > I just got off the phone with a Google rep. They;re working on it.
> > > > > > > > Their backup SMTP option is smtp.googlemail.com. It works fine for
> > > > > > > > me.
> > > > > > > > > > This probably isn't the best place to post this, but we're seeing a
> > > > > > > > > > certificate expiration (7/29/2008 8:xx a.m.) on smtp.gmail.com's SSL
> > > > > > > > > > certificate. Hope someone from Google is watching and can alert
> > > > > > > > > > someone to renew or replace the cert.
> > > > > > > > > > Thanks!- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -