Does this contain a fix for declude aborting with the error message that has
the 0xc142 and then a click ok to terminate the application ?
If not is there a work around ?
Avolve Support
Get High Speed Internet - Go Wireless !
http://www.avolvewireless.net
-- Original Message
My desktop IP was erroneously listed on CBL. It seems that declude is
checking autheticated users sending mail for CBL and according to CBL this
is wrong. SEE below
Here is the header showing what went on with the actual Ips removed to
proect the innocent (ME). But it sure seems that my
Doug,
IP's should not be in CBL unless they were found sending E-mail to a
spam trap, and seemed to be residential in nature or lacked reverse DNS
entries. So the primary issue that I see is that your IP was found to
have sent E-mail to a spam trap. CBL allows for removal without
Doug, you're probably scoring on multiple hops by setting your HOPHIGH
in global.cfg ...
If you don't want RBLs to score on multiple hops, just comment out that
HOPHIGH line.
Alternatively, rename your CBL test to CBL-DYNA (don't forget to change
the global.cfg definition plus the action line
Andrew,
Just to clear up any confusion, this message was sent by Doug through
his own SmarterMail/Declude server, so his IP was the connecting hop and
the DYNA/hop limiting tricks won't have an effect here.
I think it might be valuable if people resisted the temptation of
removing IP's from
That's a good point, Matt.
I glossed over analyzing the hops, but wouldn't Declude skip running any
test with DYNA in the name if the message was received via AUTH? I
remember that you wrote a Master's Thesis on this over in the
Declude.Support mailing list.
Naturally, this would only count
I was hoping that someone would correct my mistakes on this instead of
me needing to do another famous reply to my own post :)
In this case you are correct, but there is a little problem in the
details. Adding DUL, DYNA or DUHL to the name of any dnsbl test in
Declude will result in not only
- Original Message -
From: Matt
So it would be possibly useful in this case, but again, solving the
issue that created the CBL listing is the most direct route, and less
dependencyon any particular test by adding something like Sniffer
and reducing weights on such things I think is
