From owner-freebsd-ports@FreeBSD.ORG Wed Feb 6 11:45:21 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 A7A6216A47C for ; Wed, 6 Feb 2008 11:45:21 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from mk-outboundfilter-2.mail.uk.tiscali.com (mk-outboundfilter-2.mail.uk.tiscali.com [212.74.114.38]) by mx1.freebsd.org (Postfix) with ESMTP id 2350A13C4EC for ; Wed, 6 Feb 2008 11:45:20 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) X-Trace: 1334956/mk-outboundfilter-2.mail.uk.tiscali.com/PIPEX/$MX-ACCEPTED/pipex-infrastructure/62.241.163.7 X-SBRS: None X-RemoteIP: 62.241.163.7 X-IP-MAIL-FROM: xfb52@dial.pipex.com X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAMklqUc+8aMH/2dsb2JhbACSBZt4 X-IP-Direction: IN Received: from blaster.systems.pipex.net ([62.241.163.7]) by smtp.pipex.tiscali.co.uk with ESMTP; 06 Feb 2008 11:15:35 +0000 Received: from [192.168.23.2] (62-31-10-181.cable.ubr05.edin.blueyonder.co.uk [62.31.10.181]) by blaster.systems.pipex.net (Postfix) with ESMTP id 2AB55E00005A; Wed, 6 Feb 2008 11:15:34 +0000 (GMT) Message-ID: <47A996D2.9000801@dial.pipex.com> Date: Wed, 06 Feb 2008 11:15:30 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-ports References: <20080204141316.76512pfm25is8i68@intranet.encontacto.net> <20080204220126.GA25963@eos.sc1.parodius.com> <20080205095440.94936n0t6ybjhyas@intranet.encontacto.net> <20080205190404.GA62881@eos.sc1.parodius.com> In-Reply-To: <20080205190404.GA62881@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 06 Feb 2008 11:45:21 -0000 Jeremy Chadwick wrote: >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 > > Obviously, I can't tell you if this particular entry has legitimate reasons or not. However, I think you mentioned in an earlier message that you didn't believe that a delay of the magnitude of 19 hours ought to be possible. From a competent mail service, one would hope not, but some months ago I found myself completely unable to send messages to most FreeBSD mailing lists and debugged this with sterling help from postmaster@. My email provider could wait *days* before retrying an email which was greylisted. It took four days for a message to arrive in test@ and the mail logs clearly showed them failing to retry at any kind of acceptable interval. For the record, this was my broadband provider blueyonder.co.uk - now owned by Virgin - who were *no help whatsoever*. Luckily, I have kept up a dial-in provider as well and always used my email address from them; they provide an authenticated SMTP gateway, so I'm not disenfranchised any longer :-) (They've recently been taken over by Tiscali, so I hope that their previous standard of service keeps up). Just a data point for the archives. Great obspamd write-up too! --Alex