From owner-freebsd-isp Fri Aug 23 12:07:53 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA27244 for isp-outgoing; Fri, 23 Aug 1996 12:07:53 -0700 (PDT) Received: from host.igs.net (rene@host.igs.net [206.248.16.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA27230 for ; Fri, 23 Aug 1996 12:07:47 -0700 (PDT) Received: (from rene@localhost) by host.igs.net (8.7.4/8.6.12) id PAA29249; Fri, 23 Aug 1996 15:10:35 -0400 (EDT) Date: Fri, 23 Aug 1996 15:10:33 -0400 (EDT) From: Rene Kahle To: freebsd-isp@FreeBSD.org Subject: Re: mail storage In-Reply-To: <199608231810.LAA15125@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Attempting to use frequent runs of the queue is not a good way to solve > this problem, it is non-predictable. > > Better off to have sendmail sort mail destined to them into a seperate > /var/spool/mqueue.${DOMAIN}, then fire up a: > > sendmail -q -oQ/var/spool/mqueue.${DOMAIN} > > This is a non-trivial thing to set up, and there are bits and pieces of > it described in the BAT book, look in the sections on fault tolerent and > holding someones mail for them until they come back on line. An easier, but less elegant, way to do it is to issue a command like: sendmail -qRdomain.com & after starting PPP to make sendmail force the queue for domain.com at that time. -- Rene