The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
I've just recreated this by writing to a MS Outlook account from one of my Freeola domain accounts.
When viewing the email via MS webmail it shows:
This sender failed our fraud detection checks and may not be who they appear to be.
Looking around it looks like this might be due to SPF checks?
A report on a Freeola domain shows: "The DNS record type 99 (SPF) has been deprecated".
EDIT: I only see the 'fraud detection' error when using standard email, EmailPro comes through clean.
The 'deprecated' comment is still there so that might be a red-herring.
There's a previous related email tech talk here.
Can anything be done to improve this?
I thought I would start a forum thread rather than use a Support Ticket as others are seeing this so being able to read about the issue may help.
[s]Hmmm...[/s]
I've just recreated this by writing to a MS Outlook account from one of my Freeola domain accounts.
When viewing the email via MS webmail it shows:
This sender failed our fraud detection checks and may not be who they appear to be.
Looking around it looks like this might be due to SPF checks?
A report on a Freeola domain shows: "The DNS record type 99 (SPF) has been deprecated".
EDIT: I only see the 'fraud detection' error when using standard email, EmailPro comes through clean.
The 'deprecated' comment is still there so that might be a red-herring.
There's a previous related email tech talk here.
Can anything be done to improve this?
I thought I would start a forum thread rather than use a Support Ticket as others are seeing this so being able to read about the issue may help.
[s]Hmmm...[/s]
EmailPro:
v=spf1 a:emailpro.xxxxxxxx.com include:spf.freeolamail.net ~all
Standard email:
v=spf1 ~all
The Freeola comments mention:
All Freeola domain names will already have SPF records set up for our SMTP servers (smtp.freeola.net and smtp-auth.freeola.net).
v=spf1 a:smtp-auth.freeola.net ~all
I'm out of my depth here, but obviously there are some differences. Can Freeola update all standard email SPF records en-mass to improve things or do customers need to update their own individual records?
Thanks.
[s]Hmmm...[/s]
Please let me know when this has been done and I'll check the Microsoft warning has gone.
As you mention, it looks like this might be for older domains. I've just run an SPF report on a domain registered in the last few weeks and that looks much healthier.
Thanks.
[s]Hmmm...[/s]
I'm no longer seeing:
This sender failed our fraud detection checks and may not be who they appear to be.
- when reading Freeola email via Microsoft webmail.This can only be a good thing!
[s]Hmmm...[/s]
UPDATE:
Looking at Gmail before and after the SPF records were updated I can see that they are also 'passing authentication' now.
Authentication-Results: mx.google.com;
spf=softfail (google.com: domain of transitioning [email protected] does not designate '*Freeola IP*' as permitted sender) [email protected]
This now shows as:
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of [email protected] designates '*Freeola IP*' as permitted sender) [email protected]
More good news!