_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 4VkHbK6lTrz4S5b for ; Tue, 21 May 2024 14:57:17 +0000 (UTC) (envelope-from fquest@paz.bz) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of fquest@paz.bz designates 23.235.65.100 as permitted sender) smtp.mailfrom=fquest@paz.bz Received: from 254-68-235-23.gwaiicomm.com ([23.235.68.254] helo=[10.10.10.9]) by emailh.ca with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s9QvM-000IIH-3z; Tue, 21 May 2024 07:57:08 -0700 Message-ID: <8703f043-3703-4535-8ae3-9d552d9e79d6@paz.bz> Date: Tue, 21 May 2024 07:57:08 -0700 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: FBSD 14.0 / exim 4,97.1 - exim SIGSEGV To: questions@freebsd.org Content-Language: en-US From: Jim Pazarena Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: / X-Spamd-Result: default: False [-0.21 / 15.00]; THREAD_HIJACKING_FROM_INJECTOR(2.00)[]; FAKE_REPLY(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; NEURAL_HAM_SHORT(-0.93)[-0.928]; R_SPF_ALLOW(-0.20)[+ip4:23.235.65.64/26]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:852, ipnet:23.235.64.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[paz.bz]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4VkHbK6lTrz4S5b On 2024-05-21 3:05 AM, Odhiambo Washington wrote: > > > On Sun, May 19, 2024 at 7:24 PM tetrosalame > wrote: > > Il 19/05/2024 16:46, Jim Pazarena ha scritto: > > I upgraded both of the captioned versions at the same time, so it > is not > > clear to me which is causing this issue.. however, since upgrading, > > often but without any discernible cycle or frequency, exim refuses > > incoming connections, and logs the following: > > > > 2024-05-19 07:21:00 SIGSEGV (fault address: 0xffffffffffffff70) > > 2024-05-19 07:21:00 SIGSEGV (maybe attempt to write to immutable > memory) > > Maybe exim is violating some policy? > What does sysctl kern.elf${your_arch}.allow_wx say? > > FreeBSD14 features some pretty memory protections: see mitigations(7). > Bye, > f > > > I am running the same version of Exim on the same version of FreeBSD (on > two different servers, no custom kernel) and I haven't seen these symptoms. > If anything, here is the output of what you asked: > > `` > wash@gw:~$ sysctl -a | grep allow_wx > kern.elf32.allow_wx: 1 > kern.elf64.allow_wx: 1 > ``` > > But I did not configure these. > > > -- > Best regards, > Odhiambo WASHINGTON, My sending server is SSL outbound capable (if SSL has anything to do with this - which seems unlikely). However the sending server remains at FBSD 13.2p11, Exim 4.94.2 The smtp server sends to both direct via ethernet (public IP) connected servers plus a couple of local email accounts which use fetchmail The chassis which it sends these emails to are all 14.0p6. and exim 4.97.1. My results for the "allow_wx" also were '1'. I changed these to '0' and email wouldn't flow at all. So, I am in the throws of re-loading two chassis to FreeBSD 13.3p1 If this resolves email sending and eliminates the SIGSEGV, I will have a more firm grasp of the issue. I hear you ... you have not experienced these symptoms. I compile exim myself. Perhaps I have some odd 'Local/Makefile' settings. -- Jim Pazarena fquest@paz.bz Haida Gwaii - British Columbia - Canada