From owner-freebsd-current Sun Apr 23 10:30:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02858 for current-outgoing; Sun, 23 Apr 1995 10:30:03 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id KAA02827 for ; Sun, 23 Apr 1995 10:29:38 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA02574; Sun, 23 Apr 1995 19:29:01 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA09357 for current@freebsd.org; Sun, 23 Apr 1995 19:29:00 +0200 Received: (from j@localhost) by jette.heep.sax.de (8.6.8/8.6.9) id SAA01420 for current@freebsd.org; Sun, 23 Apr 1995 18:38:35 +0200 From: J Wunsch Message-Id: <199504231638.SAA01420@jette.heep.sax.de> Subject: Re: dumb Q. on sendmail To: current@FreeBSD.org Date: Sun, 23 Apr 1995 18:38:32 +0200 (MET DST) Reply-To: current@FreeBSD.org In-Reply-To: <9504212320.AA13507@brasil.moneng.mei.com> from "Joe Greco" at Apr 21, 95 06:20:53 pm Reply-To: joerg_wunsch@uriah.heep.sax.de X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1613 Sender: current-owner@FreeBSD.org Precedence: bulk > Actually, what you *might* want to do is to pass off all your mail to your > ISP, and have their machines deal with it. All you really need to do is > look at Sendmail's examples for "smarthost" delivery, where the local > Sendmail mostly disregards DNS/etc. This is the fix that will probably > serve you best. But the smarthost would not prevent you from the following: While you're actually connected to the net, it's highly probable that there will be several outgoing messages from freefall (e.g.) just within that time. Since freefall can reach your system directly, it will use this link instead of any less-preferrable MX. As the result, while you can upload your batched mails quickly to your smarthost, you'll still have to wait until all _incoming_ SMTP connections will be closed again. This can take forever, since there will be many new connections opened while the existing ones are serviced. If you break the line, the connection will timeout and the mail bounce (since the sender found your system reachable for some time, and hence didn't fall back to an MX). Why can't you use UUCP for this? It _is_ already batched, and you can run it separately as well as ``in background'' via TCP while your IP connection is up. Your provider must be the best MX for your machine, while the machine itself is not mentioned as an MX for itself. This way, sending smtp's should never use the A record directly (some old mailers do however). Your provider could then use a mailertable to decide where outgoing uucp connections will be fed to. The above is what i'm using regularly here. J"org