ERROR: is not a file: "/var/lib/tumgreyspf/config/client_address/1/2/3/4", mode=040755

[mdik]

Hi,

I did some whitelisting by putting files named "default" with the content "CHECKERS = " in pathes representing the ip addresses of the delivering mail servers like e.g. /var/lib/tumgreyspf/config/client_address/1/2/3/default for a range of 256 IPs.

Now, these seem to work fine, but for a server with a single IP address, thus resulting in a path like /var/lib/tumgreyspf/config/client_address/1/2/3/4/default. This results in the error message (taken from /var/log/mail.log) given in the subject, though. tumgreyspf seems to want "4" to be the file which is "default" in the other cases.

Is this behaviour intended?

Sincerely,

Malte

[linsomniac]

It is. 4 should be a file, that overrides the values in a default file if it exists. The final IP octet is a file with the values, not a directory. On Nov 24, 2014 6:07 AM, "mdik" [email protected] wrote:

Hi,

I did some whitelisting by putting files named "default" with the content "CHECKERS = " in pathes representing the ip addresses of the delivering mail servers like e.g. /var/lib/tumgreyspf/config/client_address/1/2/3/default for a range of 256 IPs.

Now, these seem to work fine, but for a server with a single IP address, thus resulting in a path like /var/lib/tumgreyspf/config/client_address/1/2/3/4/default. This results in the error message (taken from /var/log/mail.log) given in the subject, though. tumgreyspf seems to want "4" to be the file which is "default" in the other cases.

Is this behaviour intended?

Sincerely,

Malte

— Reply to this email directly or view it on GitHub https://github.com/linsomniac/tumgreyspf/issues/4.