From nobody Tue Dec 12 20:46:28 2023 X-Original-To: questions@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 4SqVyq011tz53DSN for ; Tue, 12 Dec 2023 20:46:43 +0000 (UTC) (envelope-from darcy@druid.net) Received: from mail.vex.net (mail.vex.net [98.158.132.68]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SqVyp1L4Vz3Dsg for ; Tue, 12 Dec 2023 20:46:42 +0000 (UTC) (envelope-from darcy@druid.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of darcy@druid.net designates 98.158.132.68 as permitted sender) smtp.mailfrom=darcy@druid.net; dmarc=pass (policy=reject) header.from=druid.net Received: from [192.168.215.109] (unknown [98.186.196.172]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: darcy) by mail.vex.net (Postfix) with ESMTPSA id 777A33F220 for ; Tue, 12 Dec 2023 15:46:30 -0500 (EST) Message-ID: Date: Tue, 12 Dec 2023 14:46:28 -0600 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Sendmail on 14-RELEASE Content-Language: en-US To: questions@freebsd.org References: <20231212160938.470C67E25858@ary.qy> From: D'Arcy Cain In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [1.54 / 15.00]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_SPAM_MEDIUM(0.98)[0.984]; DMARC_POLICY_ALLOW(-0.50)[druid.net,reject]; NEURAL_SPAM_SHORT(0.35)[0.346]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ASN(0.00)[asn:19842, ipnet:98.158.132.0/24, country:CA]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4SqVyp1L4Vz3Dsg X-Spamd-Bar: + On 2023-12-12 13:18, Aryeh Friedman wrote: > I would completely disagree that the machine I was asking about does > not use email at all except during manual and automatic testing of a > web app it is the main test/development machine it is for. Without > something that can *SEND* mail it is impossible to test this > functionality. Since this is a IoT medical app (remote cardiac > monitoring) the email's are potentially life critical since they do > stuff like tell the doctor when you have a "concerning arrhythmia" or > informing the patient that their monitor is offline (or damaged in > someway or another)... we use email also as txt gateway for the same > purpose. Whoa! If it is that critical don't use email to text. Set up direct texting. You don't want to add an extra point of failure. -- D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. IM: darcy@Vex.Net, VoIP: sip:darcy@druid.net