On Thu, Sep 09, 2004 at 09:30:46PM +0800, JM Ibanez wrote: > I believe that the issue was with MSFT's Caller-ID and not SPF. > Correct me if I'm wrong, but SPF + Caller-ID = IETF-sponsored > soon-to-be-standard-if-only-MS-would-play-nice Sender ID for anti > spam/anti-phishing.
SPF == Caller-ID as of now, thanks to Meng Wong. They made a deal with the devil, and look where it's getting us. If you use SPF classic, unmixed with any Microsoft stuff then you probably won't have anby issues with MS... -- dido Te capiam, cuniculus sceleste! -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie