[exim-dev] [Bug 2912] cutthrough delivery gets canceled on unexpected (non 2xx) SMTP response

2023-04-16 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2912

Jeremy Harris  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |WONTFIX

--- Comment #5 from Jeremy Harris  ---
Lacking further info, closing.

-- 
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 Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2912] cutthrough delivery gets canceled on unexpected (non 2xx) SMTP response

2023-04-05 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2912

--- Comment #3 from Thomas Mechtersheimer  ---
(In reply to Jeremy Harris from comment #2)
> Changing the message does not show up in the testsuite.
> 
> I'm interested if you saw the meesage in "normal" output?  Debug?
> Or is this purely from code-inspection?

This showed up in debug output as:
 cutthrough shutdown (target timeout on read) 

Unfortunately I didn't keep the full debug log files.

I've patched my local copy to wrap the cancel_cutthrough_connection call in
cutthrough_response with "if(errno != 0)" (without any negative side effects),
so I cannot easily reproduce this situation...

I'm trying to replace an old completely queue-less mail forwarding system with
exim; so using cutthrough whenever possible would be my prime goal.

-- 
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 Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2912] cutthrough delivery gets canceled on unexpected (non 2xx) SMTP response

2023-04-05 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2912

--- Comment #4 from Jeremy Harris  ---
Possibly exim is not the right tool for you, if you want no store-and-forward.
Something close to a pure proxy would be better, though I'm unclear how
complex your routing needs are.

Nor, indeed, why email can't be store-and-forward.

-- 
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 Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2912] cutthrough delivery gets canceled on unexpected (non 2xx) SMTP response

2023-04-02 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2912

--- Comment #2 from Jeremy Harris  ---
Changing the message does not show up in the testsuite.

I'm interested if you saw the meesage in "normal" output?  Debug?
Or is this purely from code-inspection?

-- 
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 Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2912] cutthrough delivery gets canceled on unexpected (non 2xx) SMTP response

2023-04-02 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2912

Jeremy Harris  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|unalloca...@exim.org|jgh146...@wizmail.org

--- Comment #1 from Jeremy Harris  ---
It's reasonable to fix the message.

I'm less happy about trying to continue using the onward conn after an
unexpected response; always dropping back to the traditional store
processing path keeps things simple.

-- 
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 Exim 
details at http://www.exim.org/ ##