Arjan, I don't think it makes practical sense to scan OWA traffic for virus as it is usually encrypted SSL. However, if you are worried about email viruses, then you should implement an Exchange specific antivirus software in your front end and back end servers. We use McAfe Groupshiled 5.2, and has been very successful. HTH. Regards, Raj Periyasamy Systems Administrator MCSE(Messaging), CCNA -----Original Message----- From: AHendriks@xxxxxx [mailto:AHendriks@xxxxxx] Sent: Wednesday, May 04, 2005 6:46 AM To: [ISAserver.org Discussion List] Subject: [isalist] OWA Publishing http://www.ISAserver.org I wanted to use a ISA 2004 server for publishing OWA, but i need some kind of virus scanning, i'm using TrendMicro IWSS for http trafic on an other server, which service needs to listen for traffic, the iwss service, or the isa service ? If the isa service need to listen, the traffic need to go through the iwss service, and after that to the front-end servers. Can someone explains me how to make it possible, if it is possible, or mayby some other solution. Regards, Arjan ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: raj.periyasamy@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx