Your message dated Sun, 26 Jul 2009 11:14:13 +0200
with message-id <[email protected]>
and subject line Re: Bug#538361: libapache2-mod-spamhaus: cannot query RBL for 
specific return code
has caused the Debian Bug report #538361,
regarding libapache2-mod-spamhaus: cannot query RBL for specific return code
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
538361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538361
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libapache2-mod-spamhaus
Version: 0.7-1
Severity: important


Problem: sbl.spamhaus.org (which I would like to use) has been
deprecated, one should use zen.spamhaus.org instead. 

Unfortunately, I cannot use zen.spamhaus.org (or sbl-xbl.spamhaus.org)
in their entirety on a webserver, since lots and lots of dynamically
assigned IP spaces are contained in the three lists zen is made up
from (pbl, sbl, xbl). 

If one could do blocking based on the IP address returned by the RBL
lookup, such a distinction would be possible using this table:

http://www.spamhaus.org/faq/answers.lasso?section=DNSBL%20Usage#202

What do the 127.0.0.* Return Codes mean?
     
     Return Code      Source       Notes
     127.0.0.2        SBL          Spamhaus Maintained
     127.0.0.3        ---          reserved for future use
     127.0.0.4        XBL          CBL Detected Address
     127.0.0.5        XBL          NJABL Proxies (customized)
     127.0.0.6        XBL          reserved for future use
     127.0.0.7        XBL          reserved for future use
     127.0.0.8        XBL          reserved for future use
     127.0.0.9        ---          reserved for future use
     127.0.0.10       PBL          ISP Maintained
     127.0.0.11       PBL          Spamhaus Maintained
     


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30.1 (SMP w/4 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages libapache2-mod-spamhaus depends on:
ii  apache2.2-common              2.2.11-6   Apache HTTP Server common files
ii  libc6                         2.9-12     GNU C Library: Shared libraries

libapache2-mod-spamhaus recommends no packages.

libapache2-mod-spamhaus suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Ralf Hildebrandt ha scritto:

> Odd, on my webserver I'm getting:
> 
> $ host 176.123.222.94.sbl.spamhaus.org
> 176.123.222.94.sbl.spamhaus.org does not exist, try again
> 
> On my mailservers I'm getting:
> 
> # host 176.123.222.94.sbl.spamhaus.org
> 176.123.222.94.sbl.spamhaus.org does not exist, try again
> 


This doesn't mean sbl.spamhaus.org is not working, but it means that IP
94.222.123.176 isn't listed.

Try with 2.78.52.211.sbl.spamhaus.org for example.

Therefore I'm closing this bug, please reopen it if necessary.


Cheers,
Giuseppe.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to