Date: Tue, 05 Feb 2008 14:26:17 -0600 From: eculp <eculp@encontacto.net> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Do SpamAssassin spamd and Obspamd play nicely together? Message-ID: <20080205142617.19694x2f6n88li0w@intranet.encontacto.net> In-Reply-To: <20080205190404.GA62881@eos.sc1.parodius.com> References: <20080204141316.76512pfm25is8i68@intranet.encontacto.net> <20080204220126.GA25963@eos.sc1.parodius.com> <20080205095440.94936n0t6ybjhyas@intranet.encontacto.net> <20080205190404.GA62881@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Jeremy Chadwick <koitsu@freebsd.org>: > On Tue, Feb 05, 2008 at 09:54:40AM -0600, eculp wrote: >> Quoting Jeremy Chadwick <koitsu@freebsd.org>: >>> 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 o= r >> 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 =20 > 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 =20 > 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... It would be very nice to have and useful information. Especially now =20 that I am impatiently watching my tables grow and waiting for emails =20 that I have seeded from many other sources, I am far from comfortable =20 with pfspamd but seeing that I have received almost no spam since I =20 started the test, is currently compensating. I would give postgray a =20 try but don't have a server running postfix right now and don't have a =20 lot of time and for now am going to set up pfspamd on all unless I =20 find some major issue. Thanks again for all the useful information. ed > > -- > | 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 | > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080205142617.19694x2f6n88li0w>