I continue to run into a problem where Declude fails to get any response from
the ip4r blacklists, then SmarterMail catches the exact same spam using the
ip4r blacklists(spamcop, cbl, spamhaus, etc.). Declude support implied that
there was a problem with my DNS server. But both Declude and
. IMail Queue Monitoring, Declude Overflow Queue Monitoring, SURBL/URI
integration, MRTG Integration, and Log Parsers.
- Original Message -
From: Gary Steiner [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Saturday, September 03, 2005 11:09 AM
Subject: [Declude.JunkMail] ip4r
]) [EMAIL PROTECTED]
Sent: Saturday, September 03, 2005 11:21 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] ip4r blacklists
Gary,
Someone recently posted that they did not have the HOP x setting in their
global.cfg and what was happening is that the ip4r tests were
Parsers.
- Original Message -
From: Gary Steiner [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Saturday, September 03, 2005 6:45 PM
Subject: Re: [Declude.JunkMail] ip4r blacklists
1. I have a HOP 0 line in my global.cfg file.
2. Here's what I get:
nslookup 2.0.0.127
- Original Message -
From: Gary Steiner [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Saturday, September 03, 2005 6:45 PM
Subject: Re: [Declude.JunkMail] ip4r blacklists
1. I have a HOP 0 line in my global.cfg file.
2. Here's what I get:
nslookup 2.0.0.127
