Unless you are a spam generator (in which case, please go jump into a wood chipper), you want to do everything you can to help stop the spam onslaught.
IN TXT "v=spf1 mx ~all"
IN TXT "v=spf1 mx a:mymailserver.example.com ~all"
Received-SPF: pass (google.com: domain of email@example.com designates 126.96.36.199 as permitted sender)
Some MTAs already support SPF natively, and almost all other current MTAs have patches or software plugins that provide SPF support. In fact, Ubuntu’s 7.04 release (Feisty Fawn) has announced support for their Postfix package. Have I mentioned yet that I like Ubuntu? 🙂 With luck, they will back port it into their LTS distribution … maybe.
If your MTA doesn’t already support SPF, there are a number of methods to stuff it in … I suggest to just start Googling around.
For Postfix on a non-7.04 Ubuntu server, check out this link. The worst part is getting all of the prereq perl modules in place.
If you want to skip all of this work, but want to keep your own mail server, feel free to contact us at info at officepcsupport.com — we can do the pre-filtering of anti-spam/anti-virus for you and then relay the mail to your server. We also do POP/IMAP/Webmail services for offsite email storage if that’s what you would prefer.
With luck, if more and more domains, servers, and relays implement SPF, at least the faked originator spam will loose ground, so put on your SPF already, will ya!?!