Well its always a bad idea in general security terms to run processes when you have no need to use them; why open yourself up to the potential of an exploit in something you don't have to use when you can just close it down and forget the risk?
Why risk forgetting you need to apply a patch for it because "We don't use that here so we don't need to worry about it" (case in point would be those MSDE 2000 installs that got hit by slammer whose users didn't worry because they didn't use SQL Server 2000). Having it running when you don't use it is just more ways for things to go wrong -- for example a user connects to it while "playing" and downloads mail via pop, which deltes it from the server, and then complains they've lost their email. Why waste the server's resources on a process you don't expect to use. Robert Moir MSMVP IT Systems Engineer Luton Sixth Form College Ciderspace: An online 3D virtual reality environment for tramps. Ciderspace Cafe: A park Bench. > -----Original Message----- > From: Tony Hlabse [mailto:[EMAIL PROTECTED]] > Sent: 05 February 2003 15:10 > To: Exchange Discussions > Subject: POP3 bad? > > > Are they any reasons to disable POP3 for use by users on a E2K setup? > Security or any other? Customer would like to shut it off but > needs reasons > why POP3 should be shutdown. > > > > > > > _________________________________________________________________ > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. > http://join.msn.com/?page=features/virus > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]