From owner-freebsd-ports@freebsd.org Mon Dec 21 20:19:47 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4CA874C3738 for ; Mon, 21 Dec 2020 20:19:47 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D09mx4hcCz4Vy1 for ; Mon, 21 Dec 2020 20:19:45 +0000 (UTC) (envelope-from ronald-lists@klop.ws) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=klop.ws; s=mail; h=In-Reply-To:Message-ID:From:Content-Transfer-Encoding:MIME-Version: Date:References:Subject:To:Content-Type:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=YaQx8FoepHrCbZ4w4iW1yGP7J2EhCqkor6xuRQly4Ck=; b=PBzXEtu1jv9Z4BVZFcsOmjX6LF gDKInOerTDMQ6FXewB8GEs+zhn0UwM/BBe9gm24AexOGaTUqmR7N1C0nbbdBeCdKYXHGzRvkNZH1B ZsciJnO204sYG4ak6MHOCycG/P6mGb/kPj1C+CEVjhkdoumSyeTMEL6HWabCpags14QA=; Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-ports@freebsd.org, "Dan Mahoney (Gushi)" Subject: Re: DMA -- difference between base and port? References: <27a72fde-d96c-25e6-ff62-85767da510b7@prime.gushi.org> Date: Mon, 21 Dec 2020 21:19:39 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <27a72fde-d96c-25e6-ff62-85767da510b7@prime.gushi.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.greenhost.nl X-Spam-Level: / X-Spam-Score: -0.4 X-Spam-Status: No, score=-0.4 required=5.0 tests=ALL_TRUSTED, BAYES_50, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF autolearn=disabled version=3.4.2 X-Scan-Signature: 66f4fda096222dd2b2010deb1ce817c5 X-Rspamd-Queue-Id: 4D09mx4hcCz4Vy1 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=mail header.b=PBzXEtu1; dmarc=pass (policy=none) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 195.190.28.88 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-2.50 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[195.190.28.88:from]; R_DKIM_ALLOW(-0.20)[klop.ws:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[195.190.28.88:from]; R_SPF_ALLOW(-0.20)[+ip4:195.190.28.64/27]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[195.190.28.88:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[195.190.28.88:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:47172, ipnet:195.190.28.0/24, country:NL]; MID_RHS_NOT_FQDN(0.50)[]; MAILMAN_DEST(0.00)[freebsd-ports] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2020 20:19:47 -0000 On Mon, 21 Dec 2020 12:12:02 +0100, Dan Mahoney (Gushi) wrote: > Hey there, > > At the day job we've been using mail/dma port for a number of years now, > and the rollout and config of files in /usr/local/etc/dma is part of our > deploy process. > > It only recently occurred to us that there was a "dma" in base since > probably 11.0 (whomever wrote the release notes missed that -- and the > manpage doesn't mention when it was added to FreeBSD). > > We notice that the "newaliases" function in /etc/mail/mailer.conf is > missing from the port version -- which means if you're using ports dma, > you probably want to set newaliases to something like /usr/bin/true (dma > doesn't use an aliases db, so there's no need to rebuild one, as > newaliases would). Again. something we noticed in our deployment > process with puppet. > > I can't find a feature-by-feature comparison for what one would install > the port for (other than inertia, like we have). > > There's no "version" command that I can find in DMA. (tried -h, -?, -v > --version, -V). > > Does "our" DMA track the Dragonfly version (like the base sendmail or > openssl track world) or is it completely forked and unlikely to > incorporate changes? This would be useful in feature comparison. > > Is it worth mentioning this in the pkg-message for mail/dma? > > -Dan > On 13-CURRENT I have: # more /usr/src/contrib/dma/VERSION v0.11 But the version nr doesn't tell the whole story. There are some code syncs after 0.11. https://github.com/freebsd/freebsd/commits/master/contrib/dma There is a PR to upgrade base to 0.13 already. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244630 Would love to see a sync with even newer code. I made a fix upstream myself. Regards, Ronald.