Mailing List Archive

[Bug 2630] $readsocket bug
https://bugs.exim.org/show_bug.cgi?id=2630

Yehor Lite <eg.sh.rab@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Exim 4.95 |Exim 4.94

--
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/ ##
[Bug 2630] $readsocket bug [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2630

Jeremy Harris <jgh146exb@wizmail.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Exim 4.94 |Exim 4.95

--
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/ ##
[Bug 2630] $readsocket bug [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2630

Yehor Lite <eg.sh.rab@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Priority|medium |critical

--- Comment #1 from Yehor Lite <eg.sh.rab@gmail.com> ---
At this point, the behavior using the fourth argument is no longer consistent
with the documentation.
According to the documentation, as in earlier versions of Exim (<4.94),
the fourth argument was used to replace new lines in the readsocket response,
while in Exim 4.94 there are 2 options for its operation, if {} is empty, all
new lines will remain unchanged, and the second option, for any character in
{*}, all new lines will be removed from the answer.

--
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/ ##
[Bug 2630] $readsocket bug [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2630

Jeremy Harris <jgh146exb@wizmail.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unallocated@exim.org |jgh146exb@wizmail.org
Priority|critical |medium

--- Comment #2 from Jeremy Harris <jgh146exb@wizmail.org> ---
Can't duplicate the "any character" portion of comment 1, but whitespace chars
(including spaces and newlines) are indeed broken. The utility of asking to
replace a newline with a newline is dubious.

--
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/ ##
[Bug 2630] $readsocket bug [ In reply to ]
https://bugs.exim.org/show_bug.cgi?id=2630

Git Commit <git@exim.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |git@exim.org

--- Comment #3 from Git Commit <git@exim.org> ---
Git commit:
https://git.exim.org/exim.git/commitdiff/7f83b348ccf4cd815e9758ab9ca1012e66324e9d

commit 7f83b348ccf4cd815e9758ab9ca1012e66324e9d
Author: Jeremy Harris <jgh146exb@wizmail.org>
AuthorDate: Fri Aug 14 13:09:53 2020 +0100
Commit: Jeremy Harris <jgh146exb@wizmail.org>
CommitDate: Fri Aug 14 14:10:06 2020 +0100

fix ${readsocket } eol-replacement. bug 2630
----
doc/doc-txt/ChangeLog | 4 ++++
src/src/expand.c | 11 +++++++----
src/src/functions.h | 2 +-
src/src/lookups/readsock.c | 6 ++++--
src/src/macros.h | 6 ++++--
src/src/readconf.c | 4 ++--
src/src/string.c | 30 +++++++++++++++++++-----------
test/scripts/0000-Basic/0373 | 28 +++++++++++++++++++++++++++-
test/stdout/0373 | 38 ++++++++++++++++++++++++++++++++++++++
9 files changed, 106 insertions(+), 23 deletions(-)

--
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/ ##