https://bugs.exim.org/show_bug.cgi?id=2250
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #19 from
https://bugs.exim.org/show_bug.cgi?id=2250
Jeremy Harris changed:
What|Removed |Added
Assignee|ni...@exim.org |jgh146...@wizmail.org
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #17 from David Carter ---
(In reply to David Carter from comment #16)
> (In reply to David Carter from comment #14)
>
> > I will start bisection with DKIM disabled.
>
> 4a5cbaff2f9addfc9b4375a97ec6669bf18ee4db (Tue Sep 19
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #16 from David Carter ---
(In reply to David Carter from comment #14)
> I will start bisection with DKIM disabled.
4a5cbaff2f9addfc9b4375a97ec6669bf18ee4db (Tue Sep 19 21:57:30 2017 +0100)
has the problem. That predates
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #15 from David Carter ---
(In reply to David Carter from comment #13)
> That patch doesn't apply cleanly to "80a47a2c96". It looks like quite a long
> has changed since then, so I'm going to need some help applying the same
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #14 from David Carter ---
(In reply to David Carter from comment #13)
> (In reply to David Carter from comment #12)
>
> > I am currently running ae06ddc47aa43bb5e2dcbe2643e41649d1947a9d (latest
> > available commit from
On 09/03/18 13:25, admin--- via Exim-dev wrote:
> That patch doesn't apply cleanly to "80a47a2c96". It looks like quite a long
> has changed since then, so I'm going to need some help applying the same fix
> to
> intermediate versions.
80a47a2c96 was 2006; you're only looking for problems
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #13 from David Carter ---
(In reply to David Carter from comment #12)
> I am currently running ae06ddc47aa43bb5e2dcbe2643e41649d1947a9d (latest
> available commit from origin/exim-4_90+fixes), and that still has the
>
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #12 from David Carter ---
(In reply to David Carter from comment #8)
> > I suggest modifying Exim so that it doesn't return 5xx on NULL characters.
> > Return 4xx instead so that it will retry? That way you can collect more
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #11 from Jeremy Harris ---
I don't think there were any real howlers in that sequence.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at
admin--- via Exim-dev (Do 08 Mär 2018 14:24:47 CET):
> https://bugs.exim.org/show_bug.cgi?id=2250
>
> --- Comment #10 from David Carter ---
> I guess I will need to try bisection with the 4xy suggestion to minimise
> fallout.
>
> Any obvious points between
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #10 from David Carter ---
I guess I will need to try bisection with the 4xy suggestion to minimise
fallout.
Any obvious points between 4.89.1 and 4.90.1 that I need to avoid as they
introduce nasty bugs?
--
You are
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #9 from Jeremy Harris ---
Depends whether the bug is deterministic for that recipient string.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #8 from David Carter ---
> I suggest modifying Exim so that it doesn't return 5xx on NULL characters.
> Return 4xx instead so that it will retry? That way you can collect more
> instances of the issue without dropping
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #7 from Simon Arlott ---
(In reply to David Carter from comment #4)
> > I assume that a bisect isn't viable?
>
> It would be awkward. I would be willing to try a couple of subdivisions to
> try and narrow
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #6 from David Carter ---
> It's a puzzler.
The fact that I only seem to see these errors for messages from lists.cam.ac.uk
is curious.
Actually, no: If I search my logs for the last 28 days I _do_ find some
examples
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #5 from Graeme Fowler ---
So in the "only the receiving end has changed", I'm not seeing anything on my
MX servers which are mirroring the behaviour you're seeing.
I *am* seeing occasional "??EHLO somename" commands,
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #4 from David Carter ---
> I assume that a bisect isn't viable?
It would be awkward. I would be willing to try a couple of subdivisions to try
and narrow things down.
However I think that I would want to wait a couple of
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #3 from Jeremy Harris ---
Scanning the commit log between 4.89.1 and 4.90.1 isn't flagging anything to
me. I assume that a bisect isn't viable?
--
You are receiving this mail because:
You are on the CC list for the
https://bugs.exim.org/show_bug.cgi?id=2250
--- Comment #2 from David Carter ---
> I can see a steady stream of 'NULL character' error messages
> which appear to relate to remote hosts attempting to talk gibberish
> (TLS perhaps?) on port 25
Yes, we still see this now that I
https://bugs.exim.org/show_bug.cgi?id=2250
Graeme Fowler changed:
What|Removed |Added
CC||gra...@graemef.net
---
21 matches
Mail list logo