On 28/02/07, Peter Farmer <[EMAIL PROTECTED]> wrote: > I've run exim_checkaccess over the whole list and found a few more as well. > The actually server is running 4.65, but I've also tested on 4.66. > > Should I open a bug? >
Hmm... can you try the IPs in question in a totally new file, don't copy/paste... I'm suspecting odd characters in your file which might be upsetting things. That error is generated when Exim detects an oddly-constructed IP address or mask, with the following comment: /* The pattern is not an IP address. A common error that people make is to omit one component of an IPv4 address, either by accident, or believing that, for example, 1.2.3/24 is the same as 1.2.3.0/24, or 1.2.3 is the same as 1.2.3.0, which it isn't. (Those applications that do accept 1.2.3 as an IP address interpret it as 1.2.0.3 because the final component becomes 16-bit - this is an ancient specification.) To aid in debugging these cases, we give a specific error if the pattern contains only digits and dots or contains a slash preceded only by digits and dots (a slash at the start indicates a file name and of course slashes may be present in lookups, but not preceded only by digits and dots). */ The code looks to do what it says on the tin. But then again.... Peter -- Peter Bowyer Email: [EMAIL PROTECTED] -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
