From owner-freebsd-hackers Mon Dec 18 10:28:23 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 18 10:28:20 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mothra.ecs.csus.edu (unknown [130.86.76.220]) by hub.freebsd.org (Postfix) with ESMTP id ED73F37B400; Mon, 18 Dec 2000 10:28:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mothra.ecs.csus.edu (8.11.1/8.11.1) with ESMTP id eBIJs6X48953; Mon, 18 Dec 2000 11:54:06 -0800 (PST) (envelope-from joseph@randomnetworks.com) Date: Mon, 18 Dec 2000 11:54:05 -0800 (PST) From: Joseph Scott X-Sender: scottj@mothra.ecs.csus.edu To: Vivek Khera Cc: Joseph Scott , Dan Langille , freebsd-hackers@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: processing incoming mail messages (FreshPorts 2) In-Reply-To: <14910.20578.512135.887887@onceler.kciLink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Dec 2000, Vivek Khera wrote: # >>>>> "JSF" == Joseph Scott writes: # # JSF> If you don't want to process a message the instant it comes in # JSF> (via feeding it to a perl script or what ever) you'll need to setup some # JSF> sort of queue, then have a cron job come through and process the # JSF> queue. # # Or, you could use a mailer system that does it for you. You can # configure postfix to deliver at most N messages to a specific local # destination at once, the rest getting queued in the local mail spool. # If you set this limit to 1, you'd avoid the need for any additional # file locking as well. How does postfix determine that a message has been delivered though? From reading Dan's first message, my though was the problem was doing the processing of the commit, all the db stuff, which would happen after the perl script had already accepted delivery of the message. *********************************************************** * Joseph Scott The Office Of Water Programs * * joseph@randomnetworks.com joseph.scott@owp.csus.edu * *********************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message