techwtr's profile

73 Messages

 • 

1.1K Points

Wednesday, May 21st, 2025

Gmail rejected email because it was not authenticated with either SPF or DKIM

Gmail today rejected an email sent from my Homestead-hosted email address with the following message shown below.  Since this authentication is handled entirely by Homestead, can you please correct the problem?

550-5.7.26 Your email has been blocked because the sender is unauthenticated.
   550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM.
   550-5.7.26
   550-5.7.26  Authentication results:
   550-5.7.26  DKIM = did not pass
   550-5.7.26  SPF [xxxxxx.org] with ip: [xx.xxx.xxx.xxx] = did not pass

This conversation is no longer open for comments or replies and is no longer visible to community members.

Oldest First
Selected Oldest First

111 Messages

 • 

1.6K Points

7 months ago

I'm personally sick of this problem.  Not being able to send or receive from customers is NOT GOOD.  This service is terrible and has been for a while.  Something needs done about it.

4 Messages

 • 

110 Points

We're having the same issue.  Can it be corrected or should we look for another web hosting company?

19 Messages

 • 

260 Points

7 months ago

I'm having the same issue.

19 Messages

 • 

428 Points

7 months ago

Yes, I'm experiencing the same problem. Can someone from Homestead please rectify the issue? 

111 Messages

 • 

1.6K Points

7 months ago

THIS IS GREAT.  EMAILS JUST KEEP COMING BACK.  FIX THIS, HOMESTEAD.

19 Messages

 • 

260 Points

Or at least let us know you're working on it!

111 Messages

 • 

1.6K Points

7 months ago

I'm over it.  It's a recurring problem and I have many messages that didn't go out or come in.  It's a terrible service.

8 Messages

 • 

200 Points

7 months ago

please correct this issue. So unprofessional for a business to have email issues like this. It seems homestead is 10 years behind everyone else. 

111 Messages

 • 

1.6K Points

7 months ago

I'm beyond over it.  The website software is terrible.  The email service, as you can see, is not great.  I'm actively looking around.

73 Messages

 • 

1.1K Points

7 months ago

This is still broken.  The DKIM error is gone, but the following error message now gets returned:

 550-5.7.26 The MAIL FROM domain [xxxxxx.org] has an SPF record with a hard fail
   550-5.7.26 policy (-all) but it fails to pass SPF checks with the ip:
   550-5.7.26 [65.254.254.64]. To best protect our users from spam and phishing,
   550-5.7.26 the message has been blocked. For instructions on setting up
   550-5.7.26 authentication, go to
   550 5.7.26  https://support.google.com/mail/answer/81126#authentication 6a1803df08f44-6f8b09b00a8si156731026d6.321 - gsmtp
Reporting-MTA: dns; walmailout06.yourhostingaccount.com

19 Messages

 • 

260 Points

7 months ago

Mine is working now.

111 Messages

 • 

1.6K Points

Mine is STILL not sending to gmail accounts.  Is ANYONE from tech support going to acknowledge or repair this?  Haven't seen a comment yet from them.

31 Messages

 • 

510 Points

@michael9953​ What did you do to get yours working? I am using MailChimp to send group emails out using our email domain through Homestead and all Gmail addresses are rejected. I found the so called fix on MailChimp to enter certain domain information is the CNAME of Homestead, but Homestead does not support doing that, so it will not save that information and says I need to set up a CloudFlare account.

31 Messages

 • 

510 Points

Thanks to the person that posted their tech support 800 #

Call their tech support at 1-800-710-1998 - I called and got right through to a tech and they said they have just found the fix for the problem. I send them one of my rejected Gmail emails and they will be going in and updated my DNS/Domain/Email records and that should fix the problem... they say. Truth will be after it takes affect and I am able to test it.

31 Messages

 • 

510 Points

5/24/25 Update - the tech emailed me about 2 hours after our phone call and said he had all of my domain updates in and populated and that it should now work. I tested sending an email to my own Gmail account and it went through with no errors.

111 Messages

 • 

1.6K Points

My point to all of my ranting is that I shouldn't have to call tech support for this.  They are making changes to settings, etc - things that I don't know what to do with.  Why can't they make some kind of global changes to this program?  For me to go a week without being about to get mails out, then having to call them to change things or change settings is not good.  Tech support is only available at certain hours and I'm sure probably not on a holiday.

73 Messages

 • 

1.1K Points

7 months ago

It's now working for me as well.

111 Messages

 • 

1.6K Points

Mine still does not work - my outgoings are bouncing back.  This is not acceptable.

73 Messages

 • 

1.1K Points

7 months ago

It's failing again:

   550-5.7.26 Your email has been blocked because the sender is unauthenticated.
   550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM.
   550-5.7.26
   550-5.7.26  Authentication results:
   550-5.7.26  DKIM = did not pass
   550-5.7.26  SPF [xxxxxx.org] with ip: [65.254.253.145] = did not pass

6 Messages

 • 

282 Points

7 months ago

I'm having this problem as well. Any option for resolving this without having to call in to customer support? I'm traveling abroad, so it's not that easy for me to do so. 

19 Messages

 • 

428 Points

7 months ago

I had the same issue everyone here is experiencing. If you can, I would highly suggest that you call their 1-800 number to tech support. I spoke with someone over the phone yesterday, and they had the email issue resolved in about 10 minutes. 

4 Messages

 • 

110 Points

6 months ago

We're having the same issue.  Can it be corrected or should we look for another web hosting company?  This is not an issue we can tolerate going on for any prolonged period of time.

111 Messages

 • 

1.6K Points

I hate having to call them after discovering that I've had days of emails not going out or coming in.  It's frustrating that this can't be somehow automatically be updated.