Differences between version 3 and predecessor to the previous major change of ContentScanner.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 3 | Last edited on Thursday, June 3, 2004 6:05:21 am | by TylerAkins | Revert |
Older page: | version 2 | Last edited on Wednesday, April 14, 2004 5:34:25 am | by AristotlePagaltzis | Revert |
@@ -1,3 +1,3 @@
-While the term is very generic, "ContentScanner" usually refers to tools that integrate with an [MTA] and scan [Email] on-the-fly as it arrives or goes out. They can be configured to react to [Email] in any number of ways depending on headers, body text, attachment types or filenames, and so on. The most common use is to
to hook anti-[Virus] and anti-[Spam] tools into the mail sending and delivery process, but they can also drive (selective or not) automated archiving or backup tools, gather statistics, or do just about anything you can think of. Depending on configuration and how they integrate with the [MTA] of choice they may be able to scan only locally-sent or -received [Email] or also messages being relayed.
+While the term is very generic, "ContentScanner" usually refers to tools that integrate with an [MTA] and scan [Email] on-the-fly as it arrives or goes out. They can be configured to react to [Email] in any number of ways depending on headers, body text, attachment types or filenames, and so on. The most common use is to hook anti-[Virus] and anti-[Spam] tools into the mail sending and delivery process, but they can also drive (selective or not) automated archiving or backup tools, gather statistics, or do just about anything you can think of. Depending on configuration and how they integrate with the [MTA] of choice they may be able to scan only locally-sent or -received [Email] or also messages being relayed.
For examples, see MailScanner and QmailScanner.