Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: phranque
Had a look here [postmaster.msn.com...] and one of the few things it suggests in installing SPF on your DNS server.
I had wanted to put this on anyway since it makes sense, but I wonder how much effect will it have when it comes to the bigger email providers; gmail hotmail etcetera.?
So much depends on word recognition, that a 'bad' name is going to bite you in the bum in so many ways. Forever.
Just as a 'good' name can make a small but significant difference, so a 'bad' name can give you a slight - but oh so significant disadvantage compared to your competitors.
Take a long view, see the big picture. Do what has to be done.
An SPF helps to insure the information is coming from where it says it is, but if your NAME is causing the redflag, then you are still going to have problems.
Hence the answers above yours that you chose to ignore.
Whatever, I don't have time to jump through further AOL hoops, so I have informed the membership that we cannot handle AOL, have deleted all AOL entries in the data base, and barred further AOL applications - suggesting something like hotmail (which still works fine, along with all other mail handlers). I relalise this is no solution for a commercial organization, though.
So in short, a SPF is no guarantee of even the most innocent newsletters being barred.
As long as the "bad" name is being identified from the address or a link rather than from textual content then you may be advised to spend a few pennies on a clean name which simply redirects.
I had big problems originally sending through my own ISP's email but now route it through the company that maanges the domain with few regular problems.