|
|
原帖由 luke999 於 2010-2-19 09:32 發表 ![]()
小弟我於mdaemon設定了dkim
與
按照mdaemon knowledge設定dkim於dns server
然後dns server與dns client服務重新啟動
但寄信到gmail.看該信件原始檔案~得到其中一行為:
Authentication-Results: mx.googl ...
MDaemon supports both Sender Policy Framework (SPF) and Sender ID Framework (SIDF) to help verify sending servers and protect against spoofing and phishing, which are two common types of email forgery in which the sender of the message attempts to make the message appear to be coming from someone else.
Many domains publish MX records in the Domain Name System (DNS) to identify the locations permitted to receive mail for them, but this doesn't identify the locations allowed to send mail for them. SPF is a means whereby domains can also publish sender records to identify those locations authorized to send messages. By performing an SPF lookup on incoming messages, MDaemon can attempt to determine whether or not the sending server is permitted to deliver mail for the purported sending domain, and consequently determine whether or not the sender's address may have been forged or "spoofed". Sender ID is related to SPF, but it is more complex in order to more reliably determine the actual domain purported to have sent the message, and to reduce the likelihood of incorrect results.
Use the options on this tab to configure your server's SPF and Sender ID settings.
For more information on SPF, visit:
http://spf.pobox.com
For more information on Sender ID, visit:
http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx
------
Use this screen to configure MDaemon to verify DomainKeys Identified Mail (DKIM) and/or DomainKeys (DK) signatures in incoming remote messages. When this feature is enabled and an incoming message has been cryptographically signed, MDaemon will retrieve the public key from the DNS record of the domain taken from the signature and then use that key to test the message’s DKIM or DK signature to determine its validity.
If the signature passes the verification test, the message will continue on to the next step in the regular delivery process. Additionally, if the domain taken from the signature also appears on the Approved List, the message’s Spam Filter score will receive a beneficial adjustment.
If a message has no signature, or if the signature is invalid, MDaemon will retrieve the Author Domain Signing Practices (ADSP) record of the domain in the From header to determine whether or not all of that domain’s messages should be signed. If the ADSP record indicates that a valid signature is required and the public key indicates that the signer is not merely testing DKIM, the message will receive a "Fail" result and be treated accordingly—it can be rejected outright or accepted but have its Spam Filter score adjusted upward.
Finally, if a site's ADSP record uses a syntax unknown to MDaemon, if no record exists at all, or if the ADSP option located on the DKIM Options screen is disabled, then no punitive measures will be taken. The unsigned or invalidly signed message will be treated as if the domain signs only some of its messages.
For more on DKIM see: http://www.dkim.org/ |
本帖子中包含更多资源
您需要 登录 才可以下载或查看,没有帐号?会员注册
x
|