protector 1.00.11

protector scans e-mail attachments in order to identify those that could (by nature of their type) contain viruses or other undesirable content, and replaces them with a warning message. Protector is designed to be used on a unix mail gateway server MS Windows clients by way of a POP3 service. Typically, protector blocks DOS or Windows executables, DLLS etc Files with double extensions like "picture.gif.exe" Visual basic (VB) scripts Word documents that contain macros unrecognised file types ... etc ...

Protector is NOT a virus scanner in the traditional sense: It does NOT scan attachments for virus signatures, but blocks or edits attachments that could contain viruses. So *.exe, *.vba etc attachments dont get through. This means that you dont have to keep protector up to date to stay protected against the growing tide of new viruses and worms.

Protector does not work by blocking listed types, but by blocking a set of listed types.

The logic employed by protector to determine the file types contained in attachments is based on a modified version of the "file" command, and a number of type-specific validation programs - it does not rely on the actual name of the file, or the "content-type" declared in the attachment header. It also looks inside ZIP, TAR and other archive formats, and checks the files contained in them.

Some types of files are allowed through only under certain conditions. The main example being that MS Word documents are blocked if they contain ANY macros, but allowed through otherwise.

Protector grew out of a need to protect a small network that I manage in my spare time from the dangers of e-mail borne viruses and trojans. A number of installations exist round the world and feed back from users has allowed me to improve the system - in terms of reliability, performance, ease of use and the breadth of file types "allowed through". Development is still underway, and a new release will be available shortly that allows a far larger set of file types through, allows scripts to be removed from attachments (eg: JavaScript can be removed from HTML files), and is significantly easier to tailor.

Constructive critisism is warmly invited