Your message dated Wed, 01 Nov 2006 23:17:32 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362913: fixed in spamassassin 3.1.7-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: spamassassin
Version: 3.1.0a-0volatile2
Severity: normal
Hello,
running the attached message through spamassassin triggers
DATE_IN_FUTURE_06_12:
-----------------------------------------------------
[EMAIL PROTECTED]:/tmp$ cat ~/.spamassassin/user_prefs
use_bayes 0
use_auto_whitelist 0
bayes_auto_learn 0
report_safe 1
[EMAIL PROTECTED]:/tmp$ nice spamassassin --siteconfigpath=/tmp/empty -t -x -L
< /tmp/testspamass.stripped.correcttime
[...]
Content analysis details: (1.7 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.7 DATE_IN_FUTURE_06_12 Date: is 6 to 12 hours after Received: date
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines
-----------------------------------------------------
Afaict this is caused by the Resent-Date: header that the bts software
is adding:
-----------------------------------------------------
[EMAIL PROTECTED]:/tmp$ grep -v '^Resent-Date: Sun, 16 Apr 2006 02:48:08 -0700'
< /tmp/testspamass.stripped.correcttime | nice spamassassin
--siteconfigpath=/tmp/empty -t -x -L
[...]
pts rule name description
---- ---------------------- --------------------------------------------------
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines
-----------------------------------------------------
I think it is ok for spohr to add this header, and the time/date seems
to be correct too, it sorts like it should:
Date header (Sun, 16 Apr 2006 11:44:47 +0200)
local Received (Sun, 16 Apr 2006 11:44:47 +0200)
smarthost Received (Sun, 16 Apr 2006 09:45:01 +0000)
spohr accepted Received (Sun, 16 Apr 2006 02:45:07 -0700)
internal spohr Received headers (16 Apr 2006 09:45:07 +0000)
internal spohr Received headers (Sun, 16 Apr 2006 09:48:08 UTC)
Resent-Date: Sun, 16 Apr 2006 09:48:08 UTC
spohr re-fed into exim (Sun, 16 Apr 2006 02:48:08 -0700)
received by haydn (Sun, 16 Apr 2006 09:58:50 +0000)
fed from mailman to exim (Sun, 16 Apr 2006 09:58:59 +0000)
received by master (Sun, 16 Apr 2006 04:59:01 -0500)
thanks, cu andreas
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-k7
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Versions of packages spamassassin depends on:
ii debconf 1.4.30.13 Debian configuration management sy
pn libdigest-sha1-perl Not found.
ii libhtml-parser-perl 3.45-2 A collection of modules that parse
ii perl [libstorable-perl] 5.8.4-8sarge3 Larry Wall's Practical Extraction
pn spamc Not found.
--
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken. (c) Jasper Ffforde
testspamass.stripped.correcttime.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.1.7-1
We believe that the bug you reported is fixed in the latest version of
spamassassin, which is due to be installed in the Debian FTP archive:
spamassassin_3.1.7-1.diff.gz
to pool/main/s/spamassassin/spamassassin_3.1.7-1.diff.gz
spamassassin_3.1.7-1.dsc
to pool/main/s/spamassassin/spamassassin_3.1.7-1.dsc
spamassassin_3.1.7-1_all.deb
to pool/main/s/spamassassin/spamassassin_3.1.7-1_all.deb
spamassassin_3.1.7.orig.tar.gz
to pool/main/s/spamassassin/spamassassin_3.1.7.orig.tar.gz
spamc_3.1.7-1_i386.deb
to pool/main/s/spamassassin/spamc_3.1.7-1_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Duncan Findlay <[EMAIL PROTECTED]> (supplier of updated spamassassin package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 2 Nov 2006 01:43:42 -0500
Source: spamassassin
Binary: spamassassin spamc
Architecture: source all i386
Version: 3.1.7-1
Distribution: unstable
Urgency: low
Maintainer: Duncan Findlay <[EMAIL PROTECTED]>
Changed-By: Duncan Findlay <[EMAIL PROTECTED]>
Description:
spamassassin - Perl-based spam filter using text analysis
spamc - Client for SpamAssassin spam filtering daemon
Closes: 362913 367365 373914 374377 385450 396600
Changes:
spamassassin (3.1.7-1) unstable; urgency=low
.
* New upstream release (Closes: #385450, #396600)
- Fixes handling of PGP/MIME messages (Closes: #367365)
- Fixes URIDNSBL warning of invalid bitwise or (Closes: #373914)
- Fix date handling bug (Closes: #362913)
.
* Fix README.Debian now that libnet-dns-perl isn't a dependency anymore
(Closes: #374377)
Files:
1eacbe963688e9ceedf3e556075200c9 738 mail optional spamassassin_3.1.7-1.dsc
4b342c63949d47f3ce56b3fc1c8881c1 1168183 mail optional
spamassassin_3.1.7.orig.tar.gz
a5206bface2de2ad520b012289a12c6e 28061 mail optional
spamassassin_3.1.7-1.diff.gz
9aced3ccd0d7432d511e2910a7df7a59 972932 mail optional
spamassassin_3.1.7-1_all.deb
f2afc9cf91f50bed7ce2bf1ada0fb140 75044 mail optional spamc_3.1.7-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFSZPzqjUzNGvmnNARAgHUAJ9eAm3p+RIOsrEGOV/+A9wvUyKeSQCeKX/p
z3+kzpPftKZ1tS7e4aww32s=
=uLOl
-----END PGP SIGNATURE-----
--- End Message ---
