>>Harold J. Sibble wrote: >How many folks implement recipient filtering (block all mail from accounts >not in the AD) and the tar pit feature as per here >http://support.microsoft.com/kb/842851 >If not, why not? >And if not, what do you do instead? >>>>>>>>>>>----------------------------------------------->>>>>>>>>>>>>> Our e-Soft firewall is doing Recipient Filtering in front of EX2k3 and I'm looking into tar pitting at that device. Thus, filtering and tar pitting on Exchange is not enabled. Otherwise, anything to stick it to the spammers I'm all for... (no pun intended!) Every push of that [shift + delete] sequence makes me cringe and smile at the same time as I visualize my strong hands around the neck and squeezing the evil life breath out of some punk spam author... :) ~ Ralph -----Original Message----- From: Harondel J. Sibble [mailto:exchangelist@xxxxxxxxx] Sent: Thursday, January 12, 2006 9:33 PM To: [ExchangeList] Subject: [exchangelist] exchange, recipient filters and tar pit http://www.MSExchange.org/ How many folks implement recipient filtering (block all mail from accounts not in the AD) and the tar pit feature as per here http://support.microsoft.com/kb/842851 If not, why not? And if not, what do you do instead? -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@xxxxxxxxx (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: rhaney@xxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to info@xxxxxxxxxxxxxx