From owner-freebsd-questions@FreeBSD.ORG Sat Feb 28 02:13:13 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 847A7947 for ; Sat, 28 Feb 2015 02:13:13 +0000 (UTC) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 437E8DD9 for ; Sat, 28 Feb 2015 02:13:13 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id t1S2Cfvr055994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 27 Feb 2015 18:12:42 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id t1S2Cf85055993; Fri, 27 Feb 2015 18:12:41 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA19788; Fri, 27 Feb 15 17:49:58 PST Date: Fri, 27 Feb 2015 17:49:55 -0800 From: perryh@pluto.rain.com (Perry Hutchison) To: guru@unixarea.de Subject: Re: sendmail && dhcp Message-Id: <54f11ec3.lqwMEiHv/6pQsPVF%perryh@pluto.rain.com> References: <20150226144245.GA1346@c720-r276659> <44bnkgsmcl.fsf@lowell-desk.lan> <20150226194012.GA2695@c720-r276659> <4461aoe96j.fsf@lowell-desk.lan> <20150226203154.GA2853@c720-r276659> <44k2z4ci8y.fsf@lowell-desk.lan> <54efe697.xdtSCVZsiZDqV7lP%perryh@pluto.rain.com> <20150227130145.GA3591@c720-r276659> <54f0dc41.NVD2hFGwt9XGczfB%perryh@pluto.rain.com> <20150227213834.GA2324@c720-r276659> In-Reply-To: <20150227213834.GA2324@c720-r276659> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions-local@be-well.ilk.org, freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2015 02:13:13 -0000 Matthias Apitz wrote: > El d??a Friday, February 27, 2015 a las 01:06:09PM -0800, Perry Hutchison escribi??: > > ... depending on how you have it configured, mutt may *currently* > > be running a sendmail process (via fork/exec) for each message you > > send, rather than using the local sendmail daemon. > > mutt uses sendmail (i.e. pipes the mail to something like >'sendmail -t -f ....) which queues the mail for further delivery ... Yep. mutt is invoking sendmail directly to queue the outgoing message. It's not using the daemon. > and this is what I want: queue all the answered mails until I open > the Wifi uplink and all answers are going out at once. I think, > this is only possible with a configured sendmail daemon and queue > runner. You do need sendmail configured (sendmail.cf set up appropriately), and you do need to run the queue when you're ready to transmit the outgoing messages, but you don't need the daemon. When the Wifi link comes up, instead of restarting a daemon, all that's needed is to run "sendmail -q" or "sendmail -qf". The advantage of the -qf form is that -- if I'm reading the manpage correctly -- it won't return until everything has been sent (at which point you can shut down the link, unless it's being used for something else -- like incoming messages). A sendmail daemon is useful in an always-connected system, to receive messages that someone pushes to it via SMTP or to retry queued transmissions periodically if the receiving system (or the path to it) was down on the first attempt. As the first responder was saying, it's really not all that useful on a system that is connected to the Internet only occasionally.