Return-Path: Received: from mail.greenbuilder.com ([205.238.129.197] verified) by mail.stalker.com (CommuniGate Pro SMTP 4.2.5) with SMTP id 30560455 for SIMS@mail.stalker.com; Mon, 18 Oct 2004 01:51:46 -0700 Received-SPF: none receiver=mail.stalker.com; client-ip=205.238.129.197; envelope-from=billc_lists@greenbuilder.com Received: from [192.168.33.201] (HELO [192.168.0.2]) by mail.greenbuilder.com (Stalker SMTP Server 1.8b9d14) with ESMTP id S.0012209526 for ; Mon, 18 Oct 2004 03:34:43 -0500 Mime-Version: 1.0 X-Sender: billc_lists@mail.greenbuilder.com Message-Id: In-Reply-To: References: Date: Mon, 18 Oct 2004 03:33:28 -0500 To: "SIMS Discussions" From: billc_lists@greenbuilder.com Subject: verify return paths Content-Type: text/plain; charset="us-ascii" ; format="flowed" Hi remaining SIMS users, I'm curious... where in the order of things does "verify return paths" get executed? I'm apparently getting some problems with it in combination with ASSP. When ASSP gets a bogus return path, SIMS sees it as coming from the ASSP address (ASSP's IP is in the client hosts list) I'm considering turning it off for a bit and seeing if that helps ASSP keep from clogging up when bogus return paths come through, which I think is currently the case. If it comes into play before the RBLs, I figure that the RBLs will still catch the majority of the junk... -- Bill Christensen Green Building Professionals Directory: Sustainable Building Calendar: Green Real Estate: Straw Bale Registry: Books/videos/software: