 |
 |
 |
 |
 |
|||
|
|
|
|
|||||||||||||
 |
|
|
|
|
|
|
|
 |
 |
|
Home >> Sender ID Framework: Fighting Deceptive Tactics Used By Spammers |
||||||||||
|
||||||||||
|
|
Sender ID Framework: Fighting Deceptive Tactics Used By Spammers By Jonathan Coupal Nothing causes more annoyance and frustration for IT professionals and users alike than the hordes of unwanted e-mail received daily. Much of this spam uses domain spoofing to forge the sender's address and fraudulently deceive intended recipients into believing that the e-mail was sent from a trusted site or domain. Such phony messages are particularly insidious because they are not easily filtered; users are forced to examine the messages and are often deceived into responding. What is Sender ID Framework?: Sender ID Framework (SIDF) checks the address of the server sending the e-mail against a list of servers that the domain owner or e-mail recipient allows to send e-mail. This comparison is performed by the Internet Service Provider (ISP) or by the recipient's mail server before the e- mail is delivered. If the sender's ID is validated, the e-mail is sent. If the ID is not validated, the message may be refused by the receiving server or flagged or sorted into a separate folder for the user. This technology, which will not be patented by Microsoft, incorporates Microsoft's own Purported Responsible Address (PRA), also known as Caller ID, as well as Sender Policy Framework (SPF), developed by Meng Wong of Pobox.com, and a third specification called Submitter Optimization. Benefits: With SIDF, an organization's domain and brand integrity will be protected against spoofing by validating the origin of e-mail. SIDF will also serve as a foundation for the reliable use of domain names in accreditation, reputation systems, and safe lists. There are already several major players currently use SPF to protect their e-mail systems, including AOL, Symantec, GNU, W3C, Google, and SAP.SIDF will be backward compatible with systems that already implement and use SPF. How it Works: In order for an organization to implement SIDF for its e-mail system, the organization (email sender) first publishes the IP addresses of outbound e-mail servers in DNS via a SPF record. This is done by systems administrators with little or no hard costs or technical overhead. If e-mail forwarding or e-mail intermediaries are involved, outbound e-mail servers will require software to identify their own domains. When messages are sent, receivers must determine which domain(s)to check-typically either the "purported responsible domain" from the message body or the "envelope from" domain. Receivers then query DNS for the outbound e-mail servers of the chosen domain and perform the domain-spoofing test. This requires software for inbound e-mail gateway servers, as well as optional client software to display the results of the domain checking. A match of the sender's domain with an SPF record means that the domain was not spoofed or forged. The e-mail will then be forwarded onto additional filters for other spam. A failed match means a spoofed domain and a rejected e-mail. Summary: SIDF targets one of the most pernicious forms of spam-the fraudulent use of legitimate and reputable domains to deceive e-mail recipients. Although not a comprehensive solution to spam, SIDF is surely an important first step towards cleaning up the current e-mail system. View our Technical Services covering the following areas:
|
|
 |
| |
