RE: message filtering

  • From: "Mark Fugatt" <mark@xxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 19 Nov 2002 21:52:27 -0500

Its around the 700 - 1000 mark is I remember correctly, I would recommend
looking at Block and Tackle from www.turbogeeks.com, its not that expensive
and is very effective and also the Open Relay blocker from www.vamsoft.com

Mark Fugatt
Pentech Office Solutions Inc
www.4mcts.com
www.exchangetrainer.com
Tel:  585 586 3890
Fax: 585 249 0316
Cell: 585 576 4750
Visit www.msexchange.org for valuable information about Microsoft Exchange


  -----Original Message-----
  From: SP Exadmin [mailto:sperops@xxxxxxxxx]
  Sent: Tuesday, November 19, 2002 9:47 PM
  To: [ExchangeList]
  Subject: [exchangelist] message filtering


  http://www.MSExchange.org/
  Hi,

  One effective way of controlling spams without 3rd party wares is to
include the domain name of the spam originator in the Exchange Message
Filtering box. Can anyone tell me how big can this list grow in order that
Exchange would still able to filter messages properly? I don't want to come
into a situations where the list gets too large and the filtering no longer
effective. Thanks.

  Rudi





----------------------------------------------------------------------------
--
  Do you Yahoo!?
  Yahoo! Web Hosting - Let the expert host your
site ------------------------------------------------------ List Archives:
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange
Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ:
http://www.msexchange.org/pages/larticle.asp?type=FAQ ----------------------
-------------------------------- ISA Server Resource Site:
http://www.isaserver.org Windows Security Resource Site:
http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com ----------------------------------------------------
-- You are currently subscribed to this MSExchange.org Discussion List as:
mark@xxxxxxxxx To unsubscribe send a blank email to
$subst('Email.Unsub')

Other related posts: