From owner-freebsd-arch@freebsd.org Thu Dec 7 10:10:10 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08C58E82600 for ; Thu, 7 Dec 2017 10:10:10 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E2CC800A9 for ; Thu, 7 Dec 2017 10:10:09 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id l141so12025253wmg.1 for ; Thu, 07 Dec 2017 02:10:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=htqv6FFQTin5uWjLQRdBg8dA01SENi6QMuB8eBEw1rQ=; b=PbrPU67Womc7cqxAHD2fgHfTQKLjXzKzFHEWr2wqcwHvvxhEoigaAcT2cq7RjnGi+F datAfU/5BJqp5y1KZKGptUT1F6NfXkZygNoID1J44qL4H2SXOHD1kxGGQ1pj7EGwqVJC zVZBAk050YzL+GLsitjX0pa1IhvSuBLbvdKHNX1lgYS3fXeUUetDQJt37CwVgwkiW2Ed 0zsGDhaXL+Re+9LrlCFVGb9A4iyTxCjkiXhW5/BBn9DoF5o0pE/T1MLX2AAczRa4nwuX gR3rCUn/RgPIpDJk7APXa9iPd3qKtvNFy4/bXgb/IVxOtbZMcy1ejXhyJmaJ9NxBVBou lnRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=htqv6FFQTin5uWjLQRdBg8dA01SENi6QMuB8eBEw1rQ=; b=INuyBl62TSGQqOPUaG0Y1Zv9zRFr3qT0SkGxrkBJls4ydDFMhPQUfwAUIr7ka6KCTL OcHzTyggrh1Zcr+9lwTnRgfMNyhVG2hOHWUOevGtPDiSy0XdMkO/BTxdwgDen+jjA0zT 4zLrp7j5oYtAToibvHT38n5n+1xmhJCGauAVl1cx+LCIMM+9H4Q8B8zVd78/t1WmVsmu 8P6DjF4TsXpAL/SC3lXgmuaU2QRkVYJSBeZ1kx0TgzCv9z0bb4L8ObvYVwOJmsmgbq01 F/iNcRUR7X/G63FgUiowll/H6L1MMS0eKjh/L99youBRfrxW763sIMHfsZrYENXvDK1t YHjA== X-Gm-Message-State: AJaThX7FissL1MpDIQa21j6QQV/Tg4Ah0NUyNsF5YYHI+2/WKy9nbD3h dm5PI74tcNJwQo1j+IKDRbSGfw== X-Google-Smtp-Source: AGs4zMb0oHvEPq0C34LK0zm4aCgCQdTXguPeoYfzanvuGY742TYvqKh7enx/hn/epHUAY2e8WKPI/g== X-Received: by 10.80.187.99 with SMTP id y90mr44293635ede.154.1512641407788; Thu, 07 Dec 2017 02:10:07 -0800 (PST) Received: from [131.169.227.244] (laptop_mheinze.desy.de. [131.169.227.244]) by smtp.gmail.com with ESMTPSA id g45sm2285504eda.88.2017.12.07.02.10.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Dec 2017 02:10:07 -0800 (PST) Subject: Re: RFC: Sendmail deprecation ? To: freebsd-arch@freebsd.org References: <20171206223341.iz3vj4zz2igqczy7@ivaldir.net> From: Vitaly Magerya Message-ID: Date: Thu, 7 Dec 2017 11:08:40 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171206223341.iz3vj4zz2igqczy7@ivaldir.net> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2017 10:10:10 -0000 On 12/06/2017 11:33 PM, Baptiste Daroussin wrote: > Hi all, > > I would like to propose the deprecation then removal of sendmail in base. > > Deprecation will happen in the form of FreeBSD 12.0 being built WITHOUT_SENDMAIL > by default > > removal would happen in FreeBSD 13.0 > > [...] > > If noone express a strong opinion by then, I will turn sendmail option off by > december 15th. While I mildly welcome the replacement of sendmail with dma in base, what I really want to thank Baptiste and everyone involved for is the proper organization of this change: first a clear transition path (sendmail->dma), then a build knob to test the switch, then an advance announcement with a period for discussion, then a deprecation in the next major release, and then a complete removal after one major release. This is how it should be done. Thanks, Baptiste. It seems that too often we take this procedure for granted.