The error DENIED_RDNS_RESOLVE means spamdyke found an rDNS name, but the name
it found doesn't forward-resolve to an IP address (any IP address). So even
though compxroads.com has an IP, m1.compxroads.com does not, so spamdyke
rejected it.
-- Sam Clippinger
On Mar 24, 2015, at 4:03 PM, Den
DENIED_RDNS_RESOLVE is produced by the "reject-unresolvable-rdns" filter. If
you disable that option in your configuration file, that filter will stop
blocking connections.
http://spamdyke.org/documentation/README.html#RDNS
Enabling or disabling filters for specific servers, senders or
Great, so if spamdyke could not resolve ip, triger a 'try again later..' ?
perfect.
Sam Clippinger <[EMAIL PROTECTED]> ha escrito:
> Actually, DENIED_RDNS_RESOLVE means that spamdyke found a reverse DNS
> name, but that name doesn't resolve to an IP address. However, because
> this error can
Actually, DENIED_RDNS_RESOLVE means that spamdyke found a reverse DNS
name, but that name doesn't resolve to an IP address. However, because
this error can be triggered by temporary DNS problems
(slow/unreachable/down servers), spamdyke always issues a "temporary"
rejection code in this situat
thanks folks :D
Arthur Girardi <[EMAIL PROTECTED]> ha escrito:
> Not likely, since in the first error spamdyke did get a non-existant reply.
>
> To me it looks like hotmail just put yet another new server up, and
> configured the reverse for it a little too late.
>
> Arthur
>
> Citando [EMAIL PRO
Not likely, since in the first error spamdyke did get a non-existant reply.
To me it looks like hotmail just put yet another new server up, and
configured the reverse for it a little too late.
Arthur
Citando [EMAIL PROTECTED]:
> Then... this must be caused for a timeout trying to resolve ?
>
Looks like a temporarily problem, the RDNS can be found now:
# host -r 65.55.111.96
96.111.55.65.in-addr.arpa domain name pointer
blu0-omc2-s21.blu0.hotmail.com.
David Stiller schrieb:
> I think spamdyke doesn't find the origin_ip listed in the mx's of
> hotmail.com:
>
> # dig mx hotmail.com
Yes could be a case, or the reverse DNS entry was not created
at that moment by dynamically created outbound mail servers.
Your server could not look up the rdns of the IP at
Nov 10 09:32:33, so it was yesterday. It can be a nameserver
refreshing issue, updating DNS entries 24hrs. Normally pointer
Then... this must be caused for a timeout trying to resolve ?
David Stiller <[EMAIL PROTECTED]> ha escrito:
> Looks like a temporarily problem, the RDNS can be found now:
>
> # host -r 65.55.111.96
> 96.111.55.65.in-addr.arpa domain name pointer
> blu0-omc2-s21.blu0.hotmail.com.
>
>
> David Stil
Yes but, isn't needed to be listed as mx.
Is a outbound mail server, not an mx.
And, error must be related MX nor RDNS issue. isn't it ?
David Stiller <[EMAIL PROTECTED]> ha escrito:
> I think spamdyke doesn't find the origin_ip listed in the mx's of
> hotmail.com:
>
> # dig mx hotmail.com | g
I think spamdyke doesn't find the origin_ip listed in the mx's of
hotmail.com:
# dig mx hotmail.com | grep "65.55.111.96"
# host -r 65.55.111.96
96.111.55.65.in-addr.arpa has no PTR record
[EMAIL PROTECTED] schrieb:
> Hi
>
>
> spamdyke is blocking emails like this:
>
> Nov 10 09:32:33 mail spam
Using your configuration file, spamdyke is running two rDNS tests on
incoming connections. First, it checks if the remote host has an rDNS
name at all. If it does not, spamdyke will log DENIED_RDNS_MISSING.
Then, it checks if the rDNS name resolves to an IP address. If it does
not, spamdyke
[EMAIL PROTECTED] schrieb:
> Hi
>
>
>
>> David
>>
> I had use [EMAIL PROTECTED] for example of mail, is not real mail.
>
Yes, thats why i didn't use a dig on that and said "i guess".
>
>> Peter
>>
> I check same too, 53-255-112-92.pool.ukrtel.net don't resolve to A
> entry. But
I guess 92.112.255.53 is not listed as a valid MX for mail.com
in the "from:"-field?
[EMAIL PROTECTED] schrieb:
> Hi guys.
>
>
> I'm fascianted with spamdyke, but i found issues like this
>
> Oct 28 13:15:11 myshost spamdyke[28940]: DENIED_RDNS_RESOLVE from:
> [EMAIL PROTECTED] to: [EMAIL PROTEC
Hi!
I think it means that the R-DNS is not resolveable:
[EMAIL PROTECTED]:~$ ping 53-255-112-92.pool.ukrtel.net
ping: unknown host 53-255-112-92.pool.ukrtel.net
[EMAIL PROTECTED]:~$ dig +trace 53-255-112-92.pool.ukrtel.net
; <<>> DiG 9.5.0-P2 <<>> +trace 53-255-112-92.pool.ukrtel.net
;; global op
15 matches
Mail list logo
