Ed_P Posted September 24, 2004 Share Posted September 24, 2004 SPF is only to stop joe-jobbing and spoofing. It is NOT a replacement for other forms of spam checking.Oh. I was going by the thread's title. Thanks for clearing things up for me, yet again. You guys should really RTFWS. Trust me there isn't anything you guys have thought of that we haven't covered."WS"? "we"!? Isn't Scot and Fred and other newsletter authors against blacklists of any kind? Quote Link to comment Share on other sites More sharing options...
nlinecomputers Posted September 24, 2004 Share Posted September 24, 2004 RTFWSRead the fine web site.Yes many people oppose blacklists. I don't like them if they aren't well run. If you check the links above you find there are whitelists as well so newsletters can use them to get through. I personally don't get much spam that gets through. Spamassassin uses bayean filters and blacklists to check mail. The new version even cross checks links IN the email to know spam websites. Quote Link to comment Share on other sites More sharing options...
Freddy Posted September 24, 2004 Share Posted September 24, 2004 A little interesting reading:- http://www.neowin.net/comments.php?id=2380...ry=main#comment <http://www.neowin.net/comments.php?id=23803&category=main> 02 Sep 2004 "Apache (has) written an open letter to the IETF regarding the Sender ID proposal. Sender ID is a technology designed to reduce spam on the internet. Although well designed and a technology that could do a serious amount towards reducing spam, the proposal is tied up with patent problems. Who’s the prime culprit? Your favourite vendor, Microsoft. "The current Microsoft Royalty-Free Sender ID Patent License Agreement terms are a barrier to any ASF project which wants to implement Sender ID. We believe the current license is generally incompatible with open source, contrary to the practice of open Internet standards, and specifically incompatible with the Apache License 2.0. Therefore, we will not implement or deploy Sender ID under the current license terms." The decision lays out the position for not just Apache, but SpamAssassin and JAMES. SpamAssassin is a major tool for server administrators attempting to stop spam, and is deployed worldwide. The Apache decision highlights the view of the majority of the Open Source community. Although Microsoft (is) offering the technology "royalty free", the way they have constructed the license makes it impossible to fuse Sender ID with open source / license technologies..." - <http://apache.org/foundation/docs/sender-id-position.html> IETF Disbands Anti-Spam Working Group - <http://www.techweb.com/article/printableArticle.jhtml?articleID=47902431&site_section=700028> September 23, 2004 "The Internet Engineering Task Force has disbanded its working group tackling spam, saying it was deadlocked, in part, over troubles related to Microsoft Corp.'s Sender ID proposal. The decision, announced in an e-mail this week to the MADRID group by co-area director Ted Hardie, left in limbo industry efforts to develop a single standard for authenticating senders of e-mail, a process that would make it more difficult for spammers to disguise the origin of their inbox-clogging, annoying messages...the group has failed to reach a consensus on one anti-spam technology, blaming the logjam, in part, "by the need to evaluate IPR (intellectual property rights) and licensing related to at least one proposal," an apparent reference to Sender ID...With so much disagreement over the technology needed to beat back spam, it appears the industry is headed for fragmentation, rather than a single standard..." Quote Link to comment Share on other sites More sharing options...
Marsden11 Posted September 24, 2004 Share Posted September 24, 2004 It's all moot for the time being... Quote Link to comment Share on other sites More sharing options...
nlinecomputers Posted September 24, 2004 Share Posted September 24, 2004 What is? SPF? SPF != SenderID. SPF was to be included as part of SenderID along with what Microsoft called "CallerID" but SPF's portition is technically seperate and the standard is open source. SPF is already used in Apache's SpamAssassin, in Sendmail, in Postfix and many other MTAs and POP/IMAP servers. Only one that isn't using it, offically, is Exchange. But there are 3rd party hacks to address that. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.