Your message dated Sun, 23 Oct 2011 12:15:47 +0000
with message-id <e1rhwxv-0004os...@franck.debian.org>
and subject line Bug#640496: Removed package(s) from unstable
has caused the Debian Bug report #640496,
regarding RM: whitelister -- ROM; unmaintained upstream, obsolete
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 ow...@bugs.debian.org
immediately.)


-- 
640496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libspf0
Version: 0.999-1.0.0-p3.dfsg-2
Severity: important

Hello,

It seems that libspf0 has a problem with validation of IPv6 addresses. I
discovered this problem with spfmilter, and I could reproduce it with
spfqtool. Here is the transcript of a test, with spfquery (libspf2) and
spfqtool (libspf0):
    % spfquery -i 2a01:e34:ee8f:150:201:c0ff:fe04:d58b -s 
foo...@listes.ortolo.eu
    pass                                                                        
    
    
    spfquery: domain of listes.ortolo.eu designates 
2a01:e34:ee8f:150:201:c0ff:fe04:d58b as permitted sender
    Received-SPF: pass (spfquery: domain of listes.ortolo.eu designates 
2a01:e34:ee8f:150:201:c0ff:fe04:d58b as permitted sender) 
client-ip=2a01:e34:ee8f:150:201:c0ff:fe04:d58b; 
envelope-from=foo...@listes.ortolo.eu;

    % spfqtool -h vanvogt.ortolo.eu -i 2a01:e34:ee8f:150:201:c0ff:fe04:d58b -s 
foo...@listes.ortolo.eu
    SPF short result:   fail                                                    
                         
    SPF verbose result: policy result: [fail] from rule [-all]
    RFC2822 header:     Received-SPF: fail (vanvogt.ortolo.eu: domain of 
foo...@listes.ortolo.eu does not designate 2a01:e34:ee8f:15 as permitted 
sender) receiver=vanvogt.ortolo.eu; client_ip=2a01:e34:ee8f:15; 
envelope-from=foo...@listes.ortolo.eu;

Here, spfquery is right and spfqtool is wrong, because:
    listes.ortolo.eu.   86400   IN  SPF     "v=spf1 +a:mx1.ortolo.eu 
+a:mx2.ortolo.eu -all"
    mx2.ortolo.eu.      86400   IN  AAAA    2a01:e34:ee8f:150:201:c0ff:fe04:d58b
(yes, the RFC for SPF defines the “a:” mechanism with A or AAAA lookups,
depending on the IP address family).

Regards,

-- 
Tanguy Ortolo

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.31.5-grsec-xxxx-grs-ipv6-32 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libspf0 depends on:
ii  libc6                         2.7-18     GNU C Library: Shared libraries

libspf0 recommends no packages.

libspf0 suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

whitelister |      0.8-5 | source
whitelister |   0.8-5+b1 | amd64, hurd-i386, i386, kfreebsd-amd64, 
kfreebsd-i386, powerpc, sparc

------------------- Reason -------------------
ROM; unmaintained upstream, obsolete
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close Bugs which have been reported against this package
automatically.  But please check all old bugs, if they where closed
correctly or should have been re-assign to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 640...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/640496

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)


--- End Message ---

Reply via email to