[exim-dev] [Bug 2273] Queue runners race with cutthrough delivery

2018-05-16 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2273 Jeremy Harris changed: What|Removed |Added Resolution|--- |FIXED

[exim-dev] [Bug 2273] Queue runners race with cutthrough delivery

2018-05-10 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2273 --- Comment #6 from Tim Stewart --- While testing this fix, I also found bug 2275. I still believe this bug is legitimate and the fix is correct. -- You are receiving this mail because: You are on the CC list for the bug. --

[exim-dev] [Bug 2273] Queue runners race with cutthrough delivery

2018-05-07 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2273 --- Comment #5 from Tim Stewart --- I did the sleep() test after getting your patch and all looks well. I also appreciate the extra return value checks. I will deploy this to a few of our servers and do some heavier testing.

[exim-dev] [Bug 2273] Queue runners race with cutthrough delivery

2018-05-05 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2273 --- Comment #4 from Jeremy Harris --- I don't think the solution was wrong, but I wanted to keep open the possibility of dealing more fully with an error from the fclose(), so I complexified it somewhat. If it's possible to do

[exim-dev] [Bug 2273] Queue runners race with cutthrough delivery

2018-05-05 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2273 Git Commit changed: What|Removed |Added CC||g...@exim.org --- Comment #3 from

[exim-dev] [Bug 2273] Queue runners race with cutthrough delivery

2018-05-05 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2273 Jeremy Harris changed: What|Removed |Added Status|NEW |ASSIGNED

[exim-dev] [Bug 2273] Queue runners race with cutthrough delivery

2018-05-04 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2273 --- Comment #1 from Tim Stewart --- Maybe this bug is related to bug 1322? -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev