Getting error Too many arguments in command .. in ${run} expansion
Just wondering what the limitations are and how to fix it. Would
eliminating spaces reduce the number of arguments or is it the length of
the strings?
Thanks in advance.
--
## List details at
On 2007-12-05 at 15:28 -0800, Marc Perkel wrote:
Getting error Too many arguments in command .. in ${run} expansion
Just wondering what the limitations are and how to fix it. Would
eliminating spaces reduce the number of arguments or is it the length of
the strings?
60 parameters.
Marc Perkel wrote:
Getting error Too many arguments in command .. in ${run} expansion
Just wondering what the limitations are and how to fix it. Would
eliminating spaces reduce the number of arguments or is it the length of
the strings?
A 5 second grep into the code sitting on your
On 2007-12-05 at 16:41 -0800, Marc Perkel wrote:
I guess one thing I don't understand is why Exim is counting the
parameters and not just passing the string as is.
Because that's how security holes happen. What if one of those strings
contained `cmd` substitution? etc etc.
Exim breaks up to
On Wed, 2007-12-05 at 15:28 -0800, Marc Perkel wrote:
Getting error Too many arguments in command .. in ${run} expansion
How about you give us some detail of what your ${run} expansion is?
Graeme
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at
The problem is that generally some of what I'm passing is fairly short
but sometimes people do unusual thing like have 100 name for reverse
lookups or spammers will pass something trying to make it too long. So
when that happens is when I get the error.
I guess one thing I don't understand is
Running dynastop and passing what is returned from ${lookup
dnsdb{defer_never,ptr=$sender_host_address}{$value}}
On some IPs like what returns when you run dig -x 67.69.14.226 it passes
too many parameters. I'm just wondering what the limitations are and
yes, perhaps it is a bug?
--
## List
