I set up a G Suite account for an organization's domain that I owned back when that was a free service. I'm effectively grandfathered in now for life; now Google refers to it as a "legacy G Suite account." For all intents and purposes it's just a regular G Suite account; I just don't get billed for it but I also get no support from Google.

Recently I noticed that my email address was no longer getting any emails. If I log into that account and send a message to myself, that is the only thing that works. Trying to email in from any other account at all results in a bounce back with this message:

530 SMTP authentication is required.

I have no idea how to troubleshoot this, frankly. This email address has worked for the longest time and this is only a recent result. I definitely haven't been fiddling with any settings so I'm not sure what change occurred on Google's end that would have brought this about. Any ideas on how to fix this, so I can start receiving email again?

  • Please read SMTP error reference Commented Aug 21, 2019 at 22:30
  • 1
    @Rubén that reference is not helpful. It redirects to a troubleshooting article titled "I can't sign into my email client." But that is not the problem. I can sign in just fine. The problem is that my account is not receiving email. That 530 error message is what gets sent in the bounce back from "Mail Delivery Subsystem" to the sender.
    – soapergem
    Commented Aug 28, 2019 at 2:33
  • 1
    How do you go that article? The error 530 Authentication Required points to "Use IMAP to check Gmail on other email clients". Anyway to check that your G Suite email and DNS are OK try toolbox.googleapps.com/apps/main Commented Aug 28, 2019 at 2:52
  • The link goes to the #cantsignin anchor on that page which is titled "I can't sign into my email client." I see that if you scroll all the way to the top the title is actually "Use IMAP to check Gmail on other email clients." But either way it misses the mark... I can clearly see the bounceback messages being delivered to every other address that tries to send to this account. Whether I check it directly in the browser or with Outlook/Thunderbird/etc doesn't change that. I am looking into the DNS records however... I did have to migrate the site's "A" records recently.
    – soapergem
    Commented Aug 28, 2019 at 3:15
  • 1
    It's not possible to cancel a bounty. Ref. webapps.stackexchange.com/help/bounty (P.D. just in "very rare" cases a bounty could be cancelled like when a bounty is offered to prevent the closing of a very bad question; I'm not sure if a diamond moderador could do this directly ) Commented Aug 28, 2019 at 16:35

2 Answers 2


The problem was the DNS records. Recently I had to migrate my hosting provider for the domain, I thought I was just updating "A" records but apparently all the MX records vanished along with DKIM entries, SPF, etc. I ran this tool to find out what was missing. Then I had to wait 12 hours or so for things to propagate, but now it seems to be working again.


The G Suite Administrator Help Center include a lot of information that could help us to troubleshoot many problems, specially those related to the email service.

In cases like this, delivery problems after changing DNS records, the help article that could be the best reference is Troubleshoot MX records. It includes instructions for the following steps, among other things:

  1. Step 1: waiting 72 hours after making DNS records changes,
  2. Step 2: Check the DNS records
    • Check the MX records that are applied to your primary domain
    • Check your MX records using an MX lookup tool
    • Check your DNS configuration with the Check MX tool
  3. Step 3: Add or remove the @ sign

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.