On 30 Jun 2013, at 06:05 , Wietse Venema wie...@porcupine.org wrote:
LuKreme:
When reject_unknown_client_hostname triggers on an NXDOMAIN it
returns a 550 error, which is great. When it triggers because there
is no PTR record, it returns a 450 error, which is also great?
except.
That is
On 7/1/2013 5:05 PM, LuKreme wrote:
On 30 Jun 2013, at 06:05 , Wietse Venema wie...@porcupine.org wrote:
LuKreme:
When reject_unknown_client_hostname triggers on an NXDOMAIN it
returns a 550 error, which is great. When it triggers because there
is no PTR record, it returns a 450 error,
When reject_unknown_client_hostname triggers on an NXDOMAIN it returns a 550
error, which is great. When it triggers because there is no PTR record, it
returns a 450 error, which is also great… except.
What I see is servers that connect hundreds of times, getting 450 errors and
ignoring them
On 2013-06-30 LuKreme wrote:
When reject_unknown_client_hostname triggers on an NXDOMAIN it returns
a 550 error, which is great. When it triggers because there is no PTR
record, it returns a 450 error, which is also great… except.
What I see is servers that connect hundreds of times, getting
LuKreme:
When reject_unknown_client_hostname triggers on an NXDOMAIN it
returns a 550 error, which is great. When it triggers because there
is no PTR record, it returns a 450 error, which is also great?
except.
That is incorrect. The 450 code is for errors where lookup
failed (no result
On 6/30/2013 3:12 AM, LuKreme wrote:
When reject_unknown_client_hostname triggers on an NXDOMAIN it returns a 550
error, which is great. When it triggers because there is no PTR record, it
returns a 450 error, which is also great… except.
What you're seeing is the PTR lookup fails with a
On 6/30/2013 3:12 AM, LuKreme wrote:
When reject_unknown_client_hostname triggers on an NXDOMAIN it returns a 550
error, which is great. When it triggers because there is no PTR record, it
returns a 450 error, which is also great… except.
What I see is servers that connect hundreds of