How to reject the attachment which exceed filesize limit in Exchange Server 2007 before it gets received by the HT server
Hi All,
Is there any way to change the precedence of email sending attachment validation ?
because at the moment, a user sent 80 MB email attachment and he got the Forefront error of false positive rather than the "polite" Exchange Server NDR.
any help would be appreciated.
Thanks.
Error Message:From: ForefrontServerSecurity@ExServer.com [mailto:ForefrontServerSecurity@ExServer.com]Sent: Wednesday, 13 May 2009 11:37 AMTo: Joe AdamsCc: mail-adminSubject: Microsoft Forefront Security for Exchange Server detected a virusMicrosoft Forefront Security for Exchange Server has detected a virus.Virus name: "Exceedingly compressed size"File name: "CES_Client_542.zip"State: RemovedSubject Line: "FW: CES Client 5.4.2"Sender: "Joe Adams"Location: "Itree Software/Exchange Administrative Group (FYDIBOHF23SPDLT)/ExServer (Realtime Scan Job\Joe Adams\Outbox)"Name MaxMessageSize---- --------------Send Connector 20000KB Name MaxMessageSize---- --------------Receive Connector 20000KB
You can configure max send and receive size globally to reject messages above that size.
Configure attacment filtering, if you want to filter on the type of file.
ok, so in this case the AV take precedence over the filesize.
i think it's a bit of waste of CPU resource checking the file attachment which was supposed to be rejected at the HT level before continuing to the Forefront layer.
but thanks anyway for the reply.
But, you wouldn't want hub trasnport server to go through checking all virus messages.
0
Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Configure attacment filtering, if you want to filter on the type of file.
http://technet.microsoft.com/en-us/library/aa997139.aspx
AV scans the email first and then it goes through all the AntiSpam agents in a Hub Transport Server.