We have a content filtering configuration to check emails for certain account numbers. It's working great the only bad thing is sometimes it finds what it thinks is account numbers in HTML or XML code. This is random but annoys several of our customers. Is there a way to fine tune the filter some how to prevent this from happening? What we've been doing as a work around is saving docs with out XML or sending emails in plain text.
I have done some more testing and this email sends fine in plain text. When I send it using HTML enable it gets flagged as having a SSN and encrypts the message. The issue seems to be in the HTML code. I doubt there is a way to tell Ironport when scanning the email exclude HTML and XML code. I've tried deleting each of the lines then sending the email to find out which ones are causing the encryption. It seems to be a combination of using the bullets with other formatting. I'm kind of stumped on this one. I'm not sure how to resolve this without telling the person to send the email in plain text.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...