From owner-freebsd-current Sat Jan 18 20: 4: 1 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64AF437B401 for ; Sat, 18 Jan 2003 20:03:59 -0800 (PST) Received: from durendal.skynet.be (durendal.skynet.be [195.238.3.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id E202743F1E for ; Sat, 18 Jan 2003 20:03:57 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.2] (ip-26.shub-internet.org [194.78.144.26] (may be forged)) by durendal.skynet.be (8.11.6/8.11.6/Skynet-OUT-2.20) with ESMTP id h0J43hk27686; Sun, 19 Jan 2003 05:03:43 +0100 (MET) (envelope-from ) Mime-Version: 1.0 X-Sender: bs663385@pop.skynet.be Message-Id: In-Reply-To: <00db01c2bf57$37d96810$0245a8c0@KutuluWare> References: <001a01c2bf05$e44ba6a0$0245a8c0@KutuluWare> <200301182028.h0IKShjU092671@khavrinen.lcs.mit.edu> <00db01c2bf57$37d96810$0245a8c0@KutuluWare> X-Grok: +++ath X-WebTV-Stationery: Standard; BGColor=black; TextColor=black Reply-By: Wed, 1 Jan 1984 12:34:56 +0100 Date: Sun, 19 Jan 2003 05:03:32 +0100 To: "Kutulu" From: Brad Knowles Subject: Re: postfix equiv. of sendmail's -bH? Cc: "Garrett Wollman" , Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 8:08 PM -0500 2003/01/18, Kutulu wrote: > I was just concerned that some useful task that used to occur nightly may > now not be occurring, and if so, what I could do to make it occur again. I > didn't see anything to even indicate that postfix has a host status cache, > meaning the option is pretty pointless either way. I was just wondering if > anyone who had run postfix longer than me knew for sure :) I think the closest that postfix has for the sendmail "host status" feature is the fast_flush_domains parameter, but this is normally only used for those domains that you will be acting as a backup MX/relay host and only works in conjunction with the ETRN command. With sendmail, IIRC you can use the host status information both for domains that you act as a backup MX for, as well as for domains that you do a lot of e-mail with. Therefore, they don't quite serve the same function. The fast_flush_domains feature is something Wietse added after several people (myself included) complained that there was no easy way to do the equivalent of a "sendmail -qRdomain.com", either from the command-line or via the ETRN command. Instead, he used to just flush the entire queue. Imagine you're an ISP running a backup MX for tens of thousands or hundreds of thousands of clients, and you see an average of 5-10 ETRN commands per second. Then think about trying to flush the entire queue each time you get an ETRN. Of course, postfix has built-in methods of restricting the number of SMTP clients that can be attempting to deliver mail to any given user or domain, so it has less of a need for something like a HostStatusDirectory. My understanding is that the fast_flush_domains stuff works through having the system log data related to the $relay_domains parameter in a certain way so that you can keep track of which file/message is bound for which recipient domain(s), and so that you can then figure out which files need to be flushed when you get an ETRN. I don't think there's a way to flush this feature in postfix, short of stopping and starting the service. However, I'll have to check the latest source code to be sure. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message