From owner-freebsd-current Tue Jan 12 19:31:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01217 for freebsd-current-outgoing; Tue, 12 Jan 1999 19:31:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhub.ainet.com (mailhub.ainet.com [204.30.40.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01202 for ; Tue, 12 Jan 1999 19:31:06 -0800 (PST) (envelope-from jmscott@ainet.com) Received: from shell.ainet.com (jmscott@shell.ainet.com [204.30.40.108]) by mailhub.ainet.com (8.9.1/8.9.1) with SMTP id TAA20327; Tue, 12 Jan 1999 19:30:31 -0800 (PST) Received: from localhost by shell.ainet.com (4.1/SMI-4.1) id AA18416; for current@FreeBSD.ORG; Tue, 12 Jan 99 19:32:48 PST Date: Tue, 12 Jan 1999 19:32:47 -0800 (PST) From: "Joseph M. Scott" To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: defaults changed in sendmail.cf In-Reply-To: <199901121353.VAA66059@spinner.netplex.com.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quick comments/questions. On Tue, 12 Jan 1999, Peter Wemm wrote: > 1: I turned on the relay_based_on_MX feature. This is intended to ease the > transition from the "default relay" to "relay denied" in 8.9.x. Note that > this DOES NOT expose anybody to spam risk, although it does mean that > sendmail will automatically perform a fallback relay function without > explicitly being enabled. For example; if "foo.com" lists "xyz.bar.com" in > their fallback MX list, then xyz.bar.com will happily relay mail TO foo.com > (and only TO them, not FROM them). If foo.com did this without bar.com's > permission and xyz.bar.com relayed spam to foo.com, then foo.com is getting > what they deserve and has no right to complain (and they can fix it by > repairing their MX configuration). I'll have to go back and check, but I this type setting can still allow anyone with control of their dns to relay mail through a system. If spam.com adds norelay.com to their mx list then spam.com can relay off of norelay.com. This is just quickly off of what I remember when reading about these options when they first came out. If I'm totally wrong ( which is not totally out of the question by any means :-) please let me know. Also, even if what I just stated is true, I do think, like you said, it is a good transition step. > 2: I turned on the Mime header overflow checking. This is a runtime cost > since sendmail scans the body when it passes through the system. Fair enough. > 3: I turned on a few more (optional) tables. Nothing happens unless the > .db files are created, but the rules are present. This means that the > default sendmail.cf will be a lot more useful without needing rebuilding > in as many cases. I hope this represents a better medium capability > sendmail.cf file. Of course it can still be tuned for specific purposes. Which ones where turned on? > > 4: some default paths are different, in line with Eric's plans to move > everthing to /etc/mail for the next release. I take it that the previous items in /etc/mail have been removed then? ( I thought I'd read something about them at least been renamed or something ) * Joseph M. Scott * jmscott@ainet.com * American InfoMetrics * Modesto, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message