From owner-freebsd-isp@FreeBSD.ORG Mon Jul 26 20:12:03 2004 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B639C16A4CE for ; Mon, 26 Jul 2004 20:12:03 +0000 (GMT) Received: from mail.wintek.com (mail.wintek.com [199.233.104.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5703643D1F for ; Mon, 26 Jul 2004 20:12:03 +0000 (GMT) (envelope-from rjk@wintek.com) Received: from [172.28.1.248] (rjk.wintek.com [206.230.2.248]) i6QKC1fU045058 for ; Mon, 26 Jul 2004 15:12:01 -0500 (EST) (envelope-from rjk@wintek.com) Message-ID: <41056580.3050007@wintek.com> Date: Mon, 26 Jul 2004 15:11:44 -0500 From: Richard Kuhns User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040628 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-isp@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.4 required=7.0 tests=RCVD_IN_ORBS,USER_AGENT_MOZILLA_UA,X_ACCEPT_LANG version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Question about virus/spam filtering for customers with mail servers X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 20:12:03 -0000 I'm hoping someone will be willing to share a better way to handle this. We offer virus/spam filtering for customers with their own mail servers. We're currently implementing this by configuring the customer's firewall to only accept smtp connections from our servers (all running sendmail under FreeBSD 4), and the customer's MX records point to their server first and our server(s) second and third. In most cases this works just fine -- attempts by a mail server to deliver mail directly to the customer fail, the mail server tries the secondary MX site (us), we accept and filter the message and deliver it to the customer (or not). Sometimes, though, there's a very long delay for messages to be delivered - up to several days. In each case I've been able to track down, it's been a Microsoft Exchange 2000 server that has issues with sending messages to the secondary mail server. Does anyone have a good way we could use to list our server as the primary, and then forward the messages? I've been going through the bat book, but the indexing leaves a little to be desired and I haven't found anything that looks applicable yet. Any suggestions would be greatly appreciated. Thanks in advance... - Rich -- Richard Kuhns Wintek Corporation E-mail: rjk@wintek.com 427 N 6th Street Tel: +1 (765) 742-8428 Lafayette, IN 47901-1126 Fax: +1 (765) 742-0646 United States of America