Sender ID focuses on one of the most common and deceitful practices used by spammers: domain spoofing. The term domain spoofing refers to the use of someone else domain name when sending a message. Domain spoofing is part of the larger problem of spoofing, which is the practice of forging a senders address on e-mail messages. Domain spoofing can also be used by malicious individuals in phishing scams, which try to lure consumers into disclosing sensitive personal information by pretending the e-mail is from a trusted source, such as a consumers bank. Disclosure of such information could lead to identity theft and other online consumer fraud.
Sender ID: Its an e-mail authentication protocol that verifies the origin of the e-mail and prevents forged mail from entering an organization. In essence, Spamjadoo using Sender ID framework asks a question – Has this e-mail message been spoofed If the answer is Yes, it has been spoofed, the Spamjadoo rejects the message immediately. If the answer is ? No, we can confirm the senders authenticity,? the message is assigned a SPF status and gets accepted for further checking by Spamjadoo.
So how does Sender ID work Sender ID functionality relies, in part, on an algorithm that is implemented in the Sender ID filter detects the purported responsible address (PRA). PRA is the e-mail address of the entity that is most recently responsible for injecting a message into the e-mail system. The Sender ID filter determines the actual e-mail domain by locating the first definition of the following RFC2822 message headers in this order:
If none of these headers is found, the Sender ID filter uses the STMP RFC 2821 MAIL FROM value.
Based on the evaluation of the Sender ID record, every message is handeled at SMTP process itself and appropriate responce is being sent to the sender.
The Sender ID status reflects the results of the Sender ID filtering process. The Sender ID status can be one of the following:
None validation status