Difference between revisions of "Common reasons for false positives"
(Created page with '=What are the common reasons for false positives?= By default, all policies will be enforced at a domain level. This provides the maximum level of protection for a domain name. …') |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
By default, all policies will be enforced at a domain level. This provides the maximum level of protection for a domain name. However, this level of protection may interfere with certain legitimate emails also. | By default, all policies will be enforced at a domain level. This provides the maximum level of protection for a domain name. However, this level of protection may interfere with certain legitimate emails also. | ||
| − | The following | + | The following are details of some common causes of false positives and the associated policies which will require exception rules. |
| − | + | * '''Newsletters''' | |
HTML is poorly written; too many images; off-site images; attempts to track receiving of email. | HTML is poorly written; too many images; off-site images; attempts to track receiving of email. | ||
| − | + | * '''Automated emails from financial and payroll packages''' | |
Attachments can not be scanned; attachments have double extensions E.g. .rpt.pdf | Attachments can not be scanned; attachments have double extensions E.g. .rpt.pdf | ||
| − | + | * '''Tickets and reservation confirmations''' | |
Off-site images; attempts to track receiving of email | Off-site images; attempts to track receiving of email | ||
| − | + | * '''Encrypted attachments''' | |
Can not be scanned for security risks | Can not be scanned for security risks | ||
| − | + | * '''Drawings from architectural and graphics packages''' | |
attachments have double extensions E.g. .rpt.pdf | attachments have double extensions E.g. .rpt.pdf | ||
| − | + | * '''Content from on-line auction and trading sites''' | |
HTML is poorly written; HTML contains methods for relaying data back to an external site; attempts to track receiving of email | HTML is poorly written; HTML contains methods for relaying data back to an external site; attempts to track receiving of email | ||
[[Category:MailWall]] | [[Category:MailWall]] | ||
Latest revision as of 17:33, 16 February 2012
What are the common reasons for false positives?
By default, all policies will be enforced at a domain level. This provides the maximum level of protection for a domain name. However, this level of protection may interfere with certain legitimate emails also.
The following are details of some common causes of false positives and the associated policies which will require exception rules.
- Newsletters
HTML is poorly written; too many images; off-site images; attempts to track receiving of email.
- Automated emails from financial and payroll packages
Attachments can not be scanned; attachments have double extensions E.g. .rpt.pdf
- Tickets and reservation confirmations
Off-site images; attempts to track receiving of email
- Encrypted attachments
Can not be scanned for security risks
- Drawings from architectural and graphics packages
attachments have double extensions E.g. .rpt.pdf
- Content from on-line auction and trading sites
HTML is poorly written; HTML contains methods for relaying data back to an external site; attempts to track receiving of email