Sender ID is Microsoft's proposed e-mail sender
authentication protocol designed to protect against
domain spoofing and
phishing exploits. The Sender ID Framework, as Microsoft calls it, comprises three separate specifications: Sender Policy Framework (
SPF
), Caller ID for e-mail, and Submitter Optimization. Briefly, here's how it works: The Domain Name System (
DNS) maintains SPF records for domains. When an e-mail message is received by the inbound
mail server, the server looks up the sending domain's published DNS record and determines whether the sending server's
IP address matches the one on record. If the record matches, the e-mail is authenticated and delivered to the recipient; otherwise, the message is either discarded or returned to the sender as bounce e-mail.
Domain spoofing is often used to make recipients think that a fraudulent message comes from a legitimate source; the sender is likely to be phishing (pronounced fishing) for information that will give them access to the recipient's resources, such as credit card numbers, user names, and passwords. These messages often purport to come from well-known companies; AOL, BestBuy, MSN, PayPal, and Yahoo have all been imitated. When the attacker pretends to represent a well-known company, the exploit is sometimes called a brand spoof.
This was last updated in September 2004
Dig Deeper
-
As Exchange organizations look to Office 365, questions arise about mobile device support in the cloud. Exchange Online may have the features your enterprise wants and needs.
-
With so many users accessing Exchange mail remotely, IT pros have to make mobile device management a priority. Should you use Exchange Server or Mobile Device Manager?
-
The number of mobile users grows by the day, so it helps to understand how to manage ActiveSync from the command line. Here are the four most important EMS commands in Exchange 2010 SP1.
-
People who read this also read...
-
Resources from around the Web