Thanks for the remote hands. I have committed the upstream fix developed
in parallel to the ports tree.
I am very pleased to report that Theo's patch here fixed the problem for me,
packagees produced with the patch applied on a fresh ports tree checkout
produced valid exim 4.98p0 packages that receive incoming DKIM signed
messages without complaint.
Thank you, Sir!
I owe you at least a beverage of
On Sun, Aug 18, 2024 at 02:07:43PM +0200, Peter N. M. Hansteen wrote:
> After upgrading my mail server to the latest snapshot, exim consistently
> crashes on incoming TLS, making it unable to receive among other
> openbsd.org mail.
pdkim.c:671:12: warning: call to undeclared function 'strchrnul';
On 8/19/24 7:26 PM, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
That's indeed quite odd if connecting with openssl s_client works.
I really think you should try out asking exim devs.
reported as https://bugs.exim.org/show_bug.cgi?id=3108
I will
> On 19 Aug 2024, at 23:34, Kirill A. Korinsky wrote:
>
> On Mon, 19 Aug 2024 21:13:57 +0200,
> "Peter N. M. Hansteen" wrote:
>>
>> I did a bit of that and it looks if I read this correctly that the pain point
>> is in the DKIM handling, collection of bts at
>> https://nxdomain.no/~peter/exi
On Mon, 19 Aug 2024 21:13:57 +0200,
"Peter N. M. Hansteen" wrote:
>
> I did a bit of that and it looks if I read this correctly that the pain point
> is in the DKIM handling, collection of bts at
> https://nxdomain.no/~peter/exim-gdb-traces.txt
>
I wonder if this issue can be introduced by
htt
On Mon, Aug 19, 2024 at 03:13:40PM +0100, Stuart Henderson wrote:
> On 2024/08/19 15:26, Theo Buehler wrote:
> > On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
> > >
> > >
> > > On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
> > > >
> > > > So quite odd, the whole thi
On Mon, Aug 19, 2024 at 03:26:27PM +0200, Theo Buehler wrote:
> On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
> >
> >
> > On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
> > >
> > > So quite odd, the whole thing.
> > >
> >
> > That's indeed quite odd if connecting w
On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
> That's indeed quite odd if connecting with openssl s_client works.
> I really think you should try out asking exim devs.
reported as https://bugs.exim.org/show_bug.cgi?id=3108
I will go after stack traces, would you be able to dig o
On 8/19/24 4:13 PM, Stuart Henderson wrote:
(If it _does_ stay, perhaps it should switch to using gnutls).
I am not sure this is a good idea. In the past I had quite a lot of
issues when built with gnutls. This was under linux and lots of time
ago, but this might still bring some issues th
On 2024/08/19 15:26, Theo Buehler wrote:
> On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
> >
> >
> > On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
> > >
> > > So quite odd, the whole thing.
> > >
> >
> > That's indeed quite odd if connecting with openssl s_client
On 8/19/24 3:26 PM, Theo Buehler wrote:
On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
So quite odd, the whole thing.
That's indeed quite odd if connecting with openssl s_client works.
I really think you should t
On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
>
>
> On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
> >
> > So quite odd, the whole thing.
> >
>
> That's indeed quite odd if connecting with openssl s_client works.
> I really think you should try out asking exim devs
On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
So quite odd, the whole thing.
That's indeed quite odd if connecting with openssl s_client works.
I really think you should try out asking exim devs.
smime.p7s
Description: S/MIME Cryptographic Signature
> On 19 Aug 2024, at 11:53, Renaud Allard wrote:
>
> Is 134.209.237.226 the IP you tested your "s_client" from? Because I can't
> see any "error handling TLS incoming connection" from that IP. Besides, the
> SSL connection worked in your former mail.
>
No, the digitalocean address is someth
On 8/19/24 11:45 AM, Peter N. M. Hansteen wrote:
And the log has the same errors as before -
2024-08-19 11:41:30 1sfytD-8rO-2Mur Completed
2024-08-19 11:42:17 1sfyu1-Eqn-0YUe SIGSEGV (fault address:
0xc126c7df)
2024-08-19 11:42:17 1sfyu1-Eqn-0YUe SIGSEGV (maybe
And the log has the same errors as before -
2024-08-19 11:41:30 1sfytD-8rO-2Mur Completed
2024-08-19 11:42:17 1sfyu1-Eqn-0YUe SIGSEGV (fault address:
0xc126c7df)
2024-08-19 11:42:17 1sfyu1-Eqn-0YUe SIGSEGV (maybe attempt to write to
immutable memory)
2024-08-19 1
On Mon, Aug 19, 2024 at 11:33:14AM +0200, Renaud Allard wrote:
> > so I reinstalled the locally built older one for now
>
> It would have surprised me if it was rfc1413 requests, but that was
> something to test.
>
> Does it also do the same error if you just connect with "openssl s_client
> -sta
On Mon, Aug 19, 2024 at 11:33:14AM +0200, Renaud Allard wrote:
> > so I reinstalled the locally built older one for now
>
> It would have surprised me if it was rfc1413 requests, but that was
> something to test.
>
> Does it also do the same error if you just connect with "openssl s_client
> -sta
On 8/19/24 11:16 AM, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 11:11:40AM +0200, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 10:54:00AM +0200, Renaud Allard wrote:
Your configuration looks indeed very simple without anything unusual.
I added your tls_require_ciphers as this
On Mon, Aug 19, 2024 at 11:11:40AM +0200, Peter N. M. Hansteen wrote:
> On Mon, Aug 19, 2024 at 10:54:00AM +0200, Renaud Allard wrote:
> > Your configuration looks indeed very simple without anything unusual.
> > I added your tls_require_ciphers as this is the only thing that is really
> > differen
On Mon, Aug 19, 2024 at 10:54:00AM +0200, Renaud Allard wrote:
> Your configuration looks indeed very simple without anything unusual.
> I added your tls_require_ciphers as this is the only thing that is really
> different from my test server at connection time, but I still couldn't
> reproduce the
On 8/19/24 10:12 AM, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 10:05:01AM +0200, Renaud Allard wrote:
There are no secrets in my config, so I can give you a copy if that helps
at all.
Well, if you have no secrets inside that configuration, it might help if I
can see/try it.
sure
On 8/19/24 10:02 AM, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 09:17:03AM +0200, Renaud Allard wrote:
I still cannot reproduce this on latest snapshot from today and package from
repo.
OpenBSD current.arnor.org 7.6 GENERIC.MP#265 amd64
I have noticed that the same kind of error has
On Mon, Aug 19, 2024 at 09:17:03AM +0200, Renaud Allard wrote:
> I still cannot reproduce this on latest snapshot from today and package from
> repo.
> OpenBSD current.arnor.org 7.6 GENERIC.MP#265 amd64
>
> I have noticed that the same kind of error has already been seen in other
> versions of exi
On 8/19/24 8:46 AM, Renaud Allard wrote:
On 8/18/24 4:58 PM, Peter N. M. Hansteen wrote:
On Sun, Aug 18, 2024 at 01:57:11PM +0100, Stuart Henderson wrote:
Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
('cvs up -D 2024/07/29' in mail/exim) to see whether it was the up
On 8/18/24 4:58 PM, Peter N. M. Hansteen wrote:
On Sun, Aug 18, 2024 at 01:57:11PM +0100, Stuart Henderson wrote:
Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
('cvs up -D 2024/07/29' in mail/exim) to see whether it was the update
or something else causing it?
downgra
On Sun, Aug 18, 2024 at 01:57:11PM +0100, Stuart Henderson wrote:
> Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
> ('cvs up -D 2024/07/29' in mail/exim) to see whether it was the update
> or something else causing it?
downgrading to exim 4.97.1 has tls mail flowing again,
On Sun, Aug 18, 2024 at 03:07:15PM +0200, Theo Buehler wrote:
> kernel that you built yourself? It looks like something was in snaps
> but that diff seems to have been pulled. There haven't been recent
> changes in libssl or libcrypto that would explain this change of
> behavior.
Running with a ke
On Sun, Aug 18, 2024 at 03:29:25PM +0200, Peter N. M. Hansteen wrote:
> If it doesn't, the next step is of course a locally built exim 4.91.1.
make that locally built 4.97.1 but I guess it was obvious.
Also, looking at the FAQ's recipe for building kernels, I assume a
common beginner mistake woul
On Sun, Aug 18, 2024 at 01:57:11PM +0100, Stuart Henderson wrote:
>
> Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
> ('cvs up -D 2024/07/29' in mail/exim) to see whether it was the update
> or something else causing it?
It's 4.98, all of the freshest flavors here :)
Anyw
On Sun, Aug 18, 2024 at 03:07:15PM +0200, Theo Buehler wrote:
> >> 2024-08-18 13:20:39 1sfdxf-6KQ-0Em4 SIGSEGV (fault address:
> >> 0x5e2f61b7)
> >> 2024-08-18 13:20:39 1sfdxf-6KQ-0Em4 SIGSEGV (maybe attempt to
> >> write to immutable memory)
>
> These strings aren't in a current
On Sun, Aug 18, 2024 at 01:58:31PM +0100, Stuart Henderson wrote:
> On 2024/08/18 13:57, Stuart Henderson wrote:
> > Original message didn't show up.
>
> Ah it showed up now.
>
> : >Fix:
> : To be determined. Likely abi mismatch between exim and libressl
>
> that's unlikely.
yes.
>> 20
On 2024/08/18 13:57, Stuart Henderson wrote:
> Original message didn't show up.
Ah it showed up now.
: >Fix:
: To be determined. Likely abi mismatch between exim and libressl
that's unlikely.
> Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
> ('cvs up -D 2024/07/2
Original message didn't show up.
Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
('cvs up -D 2024/07/29' in mail/exim) to see whether it was the update
or something else causing it?
On 2024/08/18 14:14, Peter N. M. Hansteen wrote:
> And I should add, the data in the report i
It looks like the original report got eaten somewhere or at least has
not yet reached the marc.info archive, so I am putting the sendbug -P
output with my explanatory comments at
https://nxdomain.no/~peter/sendbug-p-skapet_exim_20240818.txt
All the best,
Peter
--
Peter N. M. Hansteen, member of
And I should add, the data in the report is from after I did another
sysupgrade -s followed by pkg_add -vurm and observing that the problem
had not gone away.
I assume and hope there is some relatively obvious fix for this. I look
forward to reading my backlog of openbsd.org mail :)
All the best
37 matches
Mail list logo
