Our local ISP uses Barracuda's excellent filtering and sends a daily email if there are emails the filter isn't sure about per my setting.
MS must have a similar filtering application that's sitting somewhere adjacent to Outlook.com... but I have yet to find a link or...
Is there a way to view our account's spam filter page?
Mark
It's Microsoft's confusing of names, Office comes with the Outlook program/installed E-Mail client while Outlook.com is an Online/Webmail application used in Browsers. Outlook.com has been slowly replacing Hotmail.com, I have an account in both but they both go to Outlook – free personal email and calendar from Microsoft.
On a general level I've understood what you've said.
We've used the OL desktop client I'd guess from its inception, initially POP3 and local .pst files.
Then we moved to an ISP providing a web, email sync server using Kerio Connect, an Exchange generic.
Connie, needing another syncing server account, ended up using an Outlook.com account.
(There was an in between, marginally successful move to Gmail then back to I think Outlook.com) Also, as you mentioned and I've forgotten the timing and details, her MS server back end migrated to an Exchange format).
But through all this my original question remains.
Our Kerio Connect addresses are filtered by the ISP's Kerio associated Barracuda filter which is plainly accessible to us. And we'll not infrequently find an email trapped that shouldn't be and add the address to the filter's trusted list or the reverse.
However, Connie does not have that ability with her Outlook.com server account that must have somewhere a similar filter.
Keeping in mind that we have always accessed any mail server syncing or otherwise through our desktop Outlook client. The desktop Outlook client's local filter is marginal at best.
So where is MS' filter for their Outlook.com syncing email servers for Outlook.com email accounts?
Hi there
Not sure about this but I get the feeling that "If we told you --we'd have to kill you" !!!!!
If the SPAM filter algorithms from the Email Server were were publically available then anybody doing even "SPAM 101" would be able to bypass and it would be a Spammers paradise.
Locally of course you can add extra filters but I doubt whether Ms will give you their algorithm. If legitimate stuff is going straight to your SPAM folder then the only solution is to contact your email service provider and see if they can remove whatever is causing emails from that address to be treated as SPAM.
Smaller less well know providers might make their list available but Ms being a global company -- all sorts of cans of worms would be opened up if they made THEIR list available.
Don't forget also that some of these smaller providers might be buying services from someone higher up the chain and you won't have access to their list so even if you can alter your providers list it won't necessarily fix the problem.
Cheers
jimbo
Here's what sparked the question.
My wife uses the Outlook.com email address/server as an account on her local desktop OL specifically for the nonprofit she works for as a volunteer part time bookkeeper. She was dealing with the offshore support person for Mercury Payment Systems. He send a credential reset to the Outlook.com account and the email didn't arrive. She then gave him the Kerio account and the email arrived. It was fairly clear to me MS' Outlook.com server's filter ate the offshore email.
Given the offshore support person's command of the English language was somewhere between marginal and non-existent, any troubleshooting from his end was zilch.
When she described the condition to me, it seemed fairly clear that MS ate the email. And this was not the only time she's experienced the problem with MS' servers.
No way that anyone's filter will always block bad and allow good absent client, periodic intervention.
I'm not sure I agree with the spam 101 thinking for one reason. Barracuda has built their company and reputation on excellent hardware/software based filters for ISP's and businesses. And Barracuda has allowed for client access absent breaches that I'm aware of.
Quote