From owner-freebsd-questions@FreeBSD.ORG Mon Mar 2 19:05:13 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BDECBB4 for ; Mon, 2 Mar 2015 19:05:13 +0000 (UTC) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D58F61C for ; Mon, 2 Mar 2015 19:05:13 +0000 (UTC) Received: from [89.204.137.235] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1YSVeK-00016T-3M for freebsd-questions@freebsd.org; Mon, 02 Mar 2015 20:05:04 +0100 Received: from localhost.my.domain (c720-r276659 [127.0.0.1]) by localhost.unixarea.de (8.14.9/8.14.9) with ESMTP id t22J4q14001296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 2 Mar 2015 20:04:53 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.9/8.14.9/Submit) id t22J4oQt001295 for freebsd-questions@freebsd.org; Mon, 2 Mar 2015 20:04:50 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Mon, 2 Mar 2015 20:04:50 +0100 From: Matthias Apitz To: freebsd-questions@freebsd.org Subject: Re: sendmail && dhcp Message-ID: <20150302190450.GA1263@c720-r276659> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , freebsd-questions@freebsd.org 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> <1350745400.96918844.1425317480900.JavaMail.zimbra@logitravel.com> <448uff9s5s.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <448uff9s5s.fsf@be-well.ilk.org> X-Operating-System: FreeBSD 11.0-CURRENT r269739 (i386) User-Agent: Mutt/1.5.23 (2014-03-12) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.137.235 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: Mon, 02 Mar 2015 19:05:13 -0000 El día Monday, March 02, 2015 a las 01:21:35PM -0500, Lowell Gilbert escribió: > Raimund Sacherer writes: > > > sorry to barge in so late, but I do not like to have sendmail or any > > daemon which can listen on 25 running on my systems when it is not > > necessary, therefore I use DMA. > > > > It doesn't run a deamon, rather when you send mail it stows them in a > > queue. Now the queue get's worked on, but when there is no internet > > connection it should queue the mail (never tried it without internet > > connectivity though). > > > > You can then fire up your link and use dma -q (see man page) to send the queued email ... The inbound direction is: ISP--(imaps)--fetchmail--(smtp)-->sendmail(localhost:25) --> procmail-->mbox...mutt The outbound is: mutt--(sendmail)--> queue and after link-up and 'sendmail -q' all mails are send out queue--(sendmail)--(smtp/TLS)--> ISP MX I think, this scenario is pretty much fine and LISTEN is only on localhost:25; it requires only DNS working correctly in the moment of receivin and sending; This is what I asked for: how to ensure that DNS+sendmail is fine after link-up on any interface (wlan0, tun6, ...) matthias -- Matthias Apitz, guru@unixarea.de, http://www.unixarea.de/ +49-170-4527211 La referencia de la Duma a la anexión de la RDA, en este caso al contrario con la Crimlía sin referéndum, no solamente tiene gracia sino da en el blanco.- Marinos Yannikos @MarinosYannikos en un blog de RTdeutsch.