Pa provo kete mo
Welcome to GoDaddy Community! Thanks for your post.
This is usually caused by not having an SPF record for your domain (or having the wrong one). SPF records are a type of DNS record that lets receiving mail servers know whether or not the sender is using the proper mail server. If you're using Workspace Email, the proper SPF record to have is:
v=spf1 mx include:secureserver.net -all
You would want to add this as a TXT record when managing your DNS. If you're domain is hosted with us, you can see
this article for more information about managing your DNS settings.
------------
ose kjo
------------
This is a new security feature Google has just introduced to Gmail, which is why you haven't seen this before. More about that new feature here:
https://gmail.googleblog.com/2016/02/making-email-safer-for-you-posted-by.html
The big problem with e-mail has always been that it's very easy to forge a sender address - it doesn't even require any technical knowledge. Spammers have abused this trick by using random sender addresses or addresses collected from spamlists that look like they're trustworthy. Worse is of course if criminals start sending messages that look like they're coming from your bank for example.
Luckily, there are some techniques to prevent this and most e-mail services and companies already use these. They allow receiving e-mail servers to check if the message is likely to really come from this sender by checking if the e-mail server that is used is the right one (SPF) and if the message is preferably digitally signed (DKIM).
So you'll see this warning for some senders whose providers or companies haven't yet been implementing these techniques. This prevents Google from verifying wether these messages really came from this particular sender and Google decided to notify you starting last month about that. It doesn't mean the message is
unsafe, it just means you might be a bit more careful especially if it's a sensitive e-mail. Some comments asked why you can't whitelist certain addresses, but that wouldn't work in this case: you see this warning because Gmail isn't certain that this message from ja...@ example.com really came from ja...@ example.com, so we can't just say 'trust all e-mails from ja...@ example.com' since we don't know if that's the actual sender.
As companies and providers adopt the verification techniques you should start seeing these warnings less often. Google could of course have waited until everybody adopted these authentication techniques but with all major e-mail providers on board I guess this was their way of giving the others a little push to start working, so we can all have safer e-mail.
