Messaging Gateway

Hi,

Can anyone guide me to configure rules for allowing mails with unscannable attachments from a particular external domain to be delivered normally. We have the default policy to quarantine unscannable attachments in Symantec Mail Security appliance with version 9.0.
 

Thanks..

Raj.

You will need to create a policy group for the internal e-mail address that needs the "unscannable" mail.  Then set up a 2nd unscannable content rule that says deliver normally and apply this rule to the policy group that you created. 

I don't believe that you can create the rules using the external domain address.

Correct, policy groups work for  local recipients or local senders.  They don't apply to external domains.

Dam.. I was just trying to set this up...  that is a real short coming of SBG ..

Our other product you can configure password protected zip files from/to specific addresses to be allowed . 

As an example we block all password protected zip files, however from our external provider who looks after the compand pay, and our internal pay officer they can send to/from password protected emails... but no one else can to our pay officer.

dam... finding more reasons to move to trial Sophos

I think u can add exception in which rules you have specified the Scan the attachment .

Ex: Source is External Domain Which You dont wanted to scan and destination is your internal Domain or your domain.

Not able to find the above You can try with Creating seperate rule above that rule where you have current rule for Attachment scan

I don't think the attachment scan rule will work.  Because "encrypted attachment" is considered a Virus rule which rules before any  Content rules.  So the verdict has already happened.  You might try created an "incident" for this problem.

I think you can make a rule based on email content by creating a list of allowed emails and use that list in the "From" option so that if the email contains the addresses listed in the "From" part of the email, you can set a rule to let it through.

Also edit the virus policy to allow files of such type to pass through. Maybe use Tru-type and file extension and if possible, the filename if it contains company specific keywords. I'm guessing that important encrypted files like these follow a naming convention.