| 3:40 am on Oct 17, 2009 (gmt 0)|
The SPF site has tools, overviews and wizards to help generate an SPF for your site:
| 9:31 pm on Oct 17, 2009 (gmt 0)|
Consider the decision carefully and do a web search on the pros and cons.
If you are having lots of problems with email, then it might be worth considering (but it still might not be worth doing - there are drawbacks), but if you aren't having problems now, it is possible for an SPF record to do more harm than good, so it it probably not a good preventive measure.
I'm sorry I can't provide specifics. I've forgotten everything I learned while looking into this a couple of years ago, but my decision was not to use it unless I had a severe problem that it was intended to address, and maybe not to use it even then.
Two things I recall (hope they're correct): a) SPF only works if the recipient mail server checks it, and few do, b) (this one could be seriously outdated): Hotmail uses some sort of nonstandard use of SPF that can cause it to block mail that has a valid SPF, when the same email would have gotten through if it had no SPF at all.
| 12:53 am on Oct 18, 2009 (gmt 0)|
|it is possible for an SPF record to do more harm than good |
You'll need to back up a statement like that with some facts. Sounds like FUD to me.
An SPF failure on an incoming mail might be incorporated into some mail filters (and that's what you want it to do), but I've never heard of mail being blocked because of a valid SPF.
| 1:08 pm on Oct 18, 2009 (gmt 0)|
My intent was to encourage the OP to do a web search on pros and cons before making a website configuration change such as that, and to provide in my additional comments some potential keywords to help with finding out if there are any possible drawbacks.
Two authoritative places where that web search could start are at:
| 5:45 am on Oct 19, 2009 (gmt 0)|
maybe this helpful information posted by phranque in this post can also be of use for you.
| 1:24 pm on Oct 19, 2009 (gmt 0)|
Thanks everybody for the feedback.