From nobody Mon Dec 05 15:42:29 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NQnr22fKbz4k0tL for ; Mon, 5 Dec 2022 15:42:58 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NQnr10JCnz3plb for ; Mon, 5 Dec 2022 15:42:56 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=washington.edu (policy=none) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.16.1/8.16.1) with ESMTPS id 2B5FgTua011480 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 5 Dec 2022 07:42:29 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.16.1/8.16.1/Submit) id 2B5FgTqb011479 for freebsd-current@freebsd.org; Mon, 5 Dec 2022 07:42:29 -0800 (PST) (envelope-from sgk) Date: Mon, 5 Dec 2022 07:42:29 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Subject: The dma mess Message-ID: Reply-To: sgk@troutmask.apl.washington.edu List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_SOFTFAIL(0.10)[washington.edu : No valid SPF, No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu] X-Rspamd-Queue-Id: 4NQnr10JCnz3plb X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N If one has not seen Mike Karel's email, here's the URL. https://lists.freebsd.org/archives/dev-commits-src-main/2022-December/011300.html The upshot is 1) No entry in src/UPDATING about dma replacing sendmail, and thereby breaking a function system on upgrade. 2) Having sendmail_enable="YES" in /etc/rc.conf no longer works after an upgrade, because dma replaces /etc/mail/mailer.conf. sendmail appears to start, but exits immediately. One needs to go through a serious of git commits to find out about this easter egg. 3) It seems that now one must also add sendmail_submit_enable="YES" sendmail_msp_queue_enable="YES" sendmail_outbound_enable="YES" to rc.conf to recover a functioning sendmail. When I upgrade the system next month, will dma remove the ability to use sendmail without unfixing whatever damage it does? POLA? -- Steve