On 27/07/2020 20:08, George via Exim-users wrote:
> I was able to find a solution for outgoing emails to have this but not the
> other way around.
Think carefully on the distinction between incoming/outgoing
as applied to the system, versus as applied to exim.
Messages come in to exim (from SMTP
On 27/07/2020 19:45, Jamie Barnes via Exim-users wrote:> I've been avoiding
check_local_user (since it tries to chdir into home directories that the exim
user has no access to), so I don't think I have access to $local_part_data (as
nothing populates it).
Not so. Any lookup done by a
Hi,
I have cPanel with Exim 4.93-5 on CentOS 7
I want to implement a solution where all incoming emails from remote
domains will have a disclaimer message appended to the body of the email.
I was able to find a solution for outgoing emails to have this but not the
other way around. Below is the
Hi all;
Firstly, just to note that I understand the purpose of tainting data, and
appreciate any improvements to security within Exim.
That said, I was already aware of the potential for bad variable data being
exposed to the server, and was removing non-alphanumeric characters from
Hello.
Faced an error in the work of the readsocket .
${readsocket{}{}{}{}{}}
The problem arises when using the fourth argument ({}) .
It forcibly removes all "\n" from the string it receives when
requested.
In theory, everyone who uses memcached should have encountered
