From owner-freebsd-ports@FreeBSD.ORG Tue Feb 5 19:04:04 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40E4816A41A for ; Tue, 5 Feb 2008 19:04:04 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 26BF213C4D9 for ; Tue, 5 Feb 2008 19:04:04 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 146291CC031; Tue, 5 Feb 2008 11:04:04 -0800 (PST) Date: Tue, 5 Feb 2008 11:04:04 -0800 From: Jeremy Chadwick To: eculp Message-ID: <20080205190404.GA62881@eos.sc1.parodius.com> References: <20080204141316.76512pfm25is8i68@intranet.encontacto.net> <20080204220126.GA25963@eos.sc1.parodius.com> <20080205095440.94936n0t6ybjhyas@intranet.encontacto.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080205095440.94936n0t6ybjhyas@intranet.encontacto.net> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-ports Subject: Re: Do SpamAssassin spamd and Obspamd play nicely together? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 19:04:04 -0000 On Tue, Feb 05, 2008 at 09:54:40AM -0600, eculp wrote: > Quoting Jeremy Chadwick : >> http://jdc.parodius.com/freebsd/openbsd-spamd.txt > > Sorry, but I have one other question. Are you still using obspamd on the > machines you set up when you wrote the above link? Your reasons on why or > why not would be greatly appreciated. No, we're not. The main reason we reverted back to postgrey was because OpenBSD spamd cannot add an SMTP header to mails detailing how long the mail was delayed for. postgrey, since it's a postfix policy service, adds an X-Greylist header to mails allowing users to see just how long the greylisting delay was. This feature has come in handy for tracking down greylisting problems. An example header: X-Greylist: delayed 360 seconds by postgrey-1.30 at mx01.sc1.parodius.com; Mon, 04 Feb 2008 21:02:35 PST Here's an example of one which I should probably track down in our SMTP logs to see if the delay was caused by something other than redelivery time on the remote SMTP server: X-Greylist: delayed 16000 seconds by postgrey-1.30 at mx01.sc1.parodius.com; Mon, 07 Jan 2008 10:33:09 PST I would love to try OpenBSD spamd again, but it's not a policy service service like postgrey is -- OpenBSD spamd has absolutely no way of inserting any data into delivered mail, because it's implemented with pf(4) and is not a policy service. It's quite possible to make a piece of software that would act as a policy service for postfix which could get details of greylisted mails and when they were actually delivered by OpenBSD spamd. Just thinking about it makes me consider writing it. :-) Would be quite useful... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |