Hello.
Faced an error in the work of the readsocket .
${readsocket{<name>}{<request>}{<options>}{<eol string>}{<fail
string>}}
The problem arises when using the fourth argument ({<eol string>}) .
It forcibly removes all "\n" from the string it receives when
requested.
In theory, everyone who uses memcached should have encountered this
error.
Example:
${readsocket{inet:MEMCACHED_HOST:MEMCACHED_PORT}{get
$acl_c_memcache_key\r\n}{5s}{\n}}
In version 4.93 and lowest, this request will return:
"VALUE 123.123.123.123 0 21\r\ntest@???\r\nEND\r\n"
In version 4.94:
"VALUE 123.123.123.123 0 21\rtest@???\rEND\r"
Without "{\n}" argument, this request will return:
"VALUE 123.123.123.123 0 21\r\ntest@???\r\nEND\r\n"
The current version of exim is:
# exim --version
Exim version 4.94 #1 (FreeBSD 11.2) built 27-Jul-2020 15:46:45
Has anyone encountered this error?
Are there already existing solutions to it?
Virus-free. [1]
www.avg.com
References
Visible links
1.
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient
Hidden links:
3.
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient
4.
file://localhost/tmp/tmpAsRkUw.html#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2
