If you're sending on behalf of "<user>@<myowndomain>.com" from a new IP address that isn’t part of Google Workspace’s infrastructure, you’ll need to manually add that IP address to your domain’s SPF record. Otherwise, Google (and other receivers) may reject or flag the message as unauthorised.
For example, if you're also sending e-mail from IP address 198.51.100.25, you should update the SPF record to look something like this:
"v=spf1 ip4:198.51.100.25 include:_spf.google.com ~all"
Alternatively, instead of specifying an IP address directly, you can use a domain name that resolves to the correct IP (via an A or CNAME record), such as "mailsender.myowndomain.com". In that case, your SPF record might look like this:
"v=spf1 a:mailsender.myowndomain.com include:_spf.google.com ~all"
Make sure not to duplicate it, just update the existing one accordingly. Also, depending on the TTL (Time To Live in seconds) of the DNS TXT record, it may take some time before changes propagate across DNS resolvers. .
That's a great explanation of how this works -- thank you.
I have been using my regular google email account username and password for all ROS e-mail configurations and it works perfectly. The problems just very recently started and only at 1 or 2 sites.
Are you saying that we have the option of (1) updating or adding another SPF record for where emails will be sent from, or (2) using an app password?
