REF: 為什麼有時人家寄給我們的信，退信是在對方的SMTP Server 產生?

-

 

 

下段說明為什麼有時人家寄給我們的信，退信是在對方的SMTP Server 產生，FYI

Example:
您沒有權限傳送給此收件者。如需協助，請連絡您的系統管理員。

            <eastech.net #5.7.1 smtp;550 5.7.1 Your message was refused by Microsoft Exchange Intelligent Message Filter, please re-check your message subject and content.>

SMTP Event

clip_image001

就反垃圾郵件代理程式而言，其首要考量並非郵件內容的有效性，而是據以識別及拒絕有效垃圾郵件的標準。越快拒絕已確認為垃圾郵件的郵件，組織所付出的成本就越低。

所有在 OnEndOfData SMTP 事件之前觸發的 SMTP 事件，都不需要接收 SMTP 主機產生未傳遞回條 (NDR)。不會產生 NDR 的原因是，在 OnEndOfData SMTP 事件觸發之前，並不會傳遞完整的郵件內容。因此，郵件的最終傳遞仍由傳送 SMTP 主機負責。若傳遞至接收 SMTP 主機的郵件在 OnEndOfData SMTP 事件之前即已失敗，傳送 SMTP 主機即必須產生 NDR 給郵件的寄件者。在 OnEndOfData SMTP 事件觸發後，接收 SMTP 主機即已接受完整的郵件內容。也就是說，SMTP 主機此時必須負責順利傳遞郵件，以及產生並傳送 NDR 給郵件的寄件者。因此，反垃圾郵件代理程式務必在 OnEndOfData SMTP 事件觸發前對 SMTP 事件進行登錄，以降低接收 SMTP 主機儲存郵件內容並對郵件寄件者產生 NDR 的可能性。

 

Blog Extended Reading

More Information & Reference

 

image

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more