Microsoft Exchange Integration Techniques
Those of you integrating the Piratefish with Microsoft Exchange know that delivery of spam to the users into the Junk boxes has been difficult to provide, and many of you have sought alternative methods such as delivery to a specific user, or quarantining.
While these methods work, they're not as optimal as many would like to see - ideally it'd be best to deliver the spam so that the users can access it - but automatically sort it into their junk boxes so that it doesn't get in their way. This way, if something is mis-categorized as spam, they'll still be able to hunt for it in the junk box.
Exchange 2003 sp2 has a feature called the "Intelligent Message Filter" or IMF for short. The IMF isn't easy to use or program, and it doesn't provide the controls or even the gui needed for something to be easily implemented or utilized - however, there is hope. The IMF can be taught to trust and read headers written by the Piratefish (or any spam filter for that matter) using some tips and techniques I've linked to on the Piratefish support page found here.
By combining some custom headers from the Piratefish with some XML filtering in the IMF, your SCL's (Spam Confidence Level) can be influenced by the Piratefish, and the Exchange server can do it's job more effectively than ever, working with the Piratefish to achieve a low cost spam free mailbox!
While these methods work, they're not as optimal as many would like to see - ideally it'd be best to deliver the spam so that the users can access it - but automatically sort it into their junk boxes so that it doesn't get in their way. This way, if something is mis-categorized as spam, they'll still be able to hunt for it in the junk box.
Exchange 2003 sp2 has a feature called the "Intelligent Message Filter" or IMF for short. The IMF isn't easy to use or program, and it doesn't provide the controls or even the gui needed for something to be easily implemented or utilized - however, there is hope. The IMF can be taught to trust and read headers written by the Piratefish (or any spam filter for that matter) using some tips and techniques I've linked to on the Piratefish support page found here.
By combining some custom headers from the Piratefish with some XML filtering in the IMF, your SCL's (Spam Confidence Level) can be influenced by the Piratefish, and the Exchange server can do it's job more effectively than ever, working with the Piratefish to achieve a low cost spam free mailbox!
Comments