Your message dated Tue, 22 May 2007 21:47:07 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#290927: fixed in spamassassin 3.2.0-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.0.2-1
Severity: normal

The ALL_TRUSTED rule is firing on much of the spam coming in to my
server.  This has a -3.3 score assigned by default.

Here's an example set of headers (including the spamassassin report) for
a spam message:

Return-path: <[EMAIL PROTECTED]>
Envelope-to: [EMAIL PROTECTED],
 [EMAIL PROTECTED]
Received: from [61.52.78.187] (helo=64.26.176.14)
    by pyloric.projectile.ca with smtp (Exim 4.34)
    id 1CqZBF-0001JN-Hv; Mon, 17 Jan 2005 10:52:57 -0500
from: "Jeffry Thornton" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Chaep n sceure
Date: Mon, 17 Jan 2005 18:50:27 +0300
MIME-Version: 1.0
Content-Type: multipart/related;
    boundary="----81278193136110956"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTvBtvuTKhRDcWvRGOd7oYCKcKsmg==
X-Broken-Reverse-DNS: no host name found for IP address 61.52.78.187
X-Spam-Projectile: (************) 12.9, autolearn=no
    1.7 SARE_RECV_IP_061052    Spam passed through possible spammer
relay
    1.7 SARE_MSGID_EMPTY       Message ID is empty, or just spaces
    -3.3 ALL_TRUSTED            Did not pass through any untrusted hosts
    0.0 HTML_MESSAGE           BODY: HTML included in message
    0.1 MPART_ALT_DIFF         BODY: HTML and text parts are different
    1.9 BAYES_99               BODY: Bayesian spam probability is 99 to
100%
    [score: 1.0000]
    0.0 HTML_90_100            BODY: Message is 90% to 100% HTML
    2.0 RCVD_IN_SORBS_DUL      RBL: SORBS: sent directly from dynamic IP
address
    [61.52.78.187 listed in dnsbl.sorbs.net]
    1.5 URIBL_WS_SURBL         Contains an URL listed in the WS SURBL
blocklist
    [URIs: amuralokastu.com]
    3.2 URIBL_OB_SURBL         Contains an URL listed in the OB SURBL
blocklist
    [URIs: amuralokastu.com]
    4.3 URIBL_SC_SURBL         Contains an URL listed in the SC SURBL
blocklist
    [URIs: amuralokastu.com]

It looks like this is related to spamassassin bug #3949:
http://bugzilla.spamassassin.org/show_bug.cgi?id=3949

If it is, that implies that spamassassin isn't parsing the Received
header correctly -- I'm running exim4-daemon-heavy 4.34-10 from Sarge.

Anyway, at the very least, I think you should maybe score ALL_TRUSTED
down to 0 until upstream fixees 3949.

- Marc
                                                                            

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)

Versions of packages spamassassin depends on:
ii  debconf                       1.4.30.11  Debian configuration management sy
ii  libdigest-sha1-perl           2.10-1     NIST SHA-1 message digest algorith
ii  libhtml-parser-perl           3.36-1     A collection of modules that parse
ii  perl [libstorable-perl]       5.8.4-5    Larry Wall's Practical Extraction 
ii  spamc                         3.0.2-1    Client for SpamAssassin spam filte

-- debconf information:
  spamassassin/upgrade/2.40:
  spamassassin/upgrade/2.40w:
  spamassassin/upgrade/cancel: Continue
  spamassassin/upgrade/2.42m: No
  spamassassin/upgrade/2.42u: No


--- End Message ---
--- Begin Message ---
Source: spamassassin
Source-Version: 3.2.0-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.2.0-1.diff.gz
  to pool/main/s/spamassassin/spamassassin_3.2.0-1.diff.gz
spamassassin_3.2.0-1.dsc
  to pool/main/s/spamassassin/spamassassin_3.2.0-1.dsc
spamassassin_3.2.0-1_all.deb
  to pool/main/s/spamassassin/spamassassin_3.2.0-1_all.deb
spamassassin_3.2.0.orig.tar.gz
  to pool/main/s/spamassassin/spamassassin_3.2.0.orig.tar.gz
spamc_3.2.0-1_i386.deb
  to pool/main/s/spamassassin/spamc_3.2.0-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: Mon, 21 May 2007 10:08:17 -0400
Source: spamassassin
Binary: spamassassin spamc
Architecture: source all i386
Version: 3.2.0-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: 290927 312263 319478 333882 336236 337617 341055 357696 367635 374432 
374435 374714 376610 391655 394939 395872 396500 400435 400437 402572 408472 
411022 413978 422692
Changes: 
 spamassassin (3.2.0-1) unstable; urgency=low
 .
   * New upstream release (Closes: #422692, #411022)
     - New plugin and script "sa-compile" should greatly improve
     performance if enabled (Closes: #394939)
     - Fix ordering of lines in sa-update generated files (Closes: #413978)
     - Fix parsing of Exim received headers (Closes: #357696)
     - Stop requiring Crypt::OpenSSL::Bignum with DKIM (Closes: #400437)
     - Better handling of trusted_networks (Closes: #290927)
     - More robust prefork mechanism for spamd (multiple bugs fixed)
     (Closes: #336236, #396500, #341055)
     - Better handling of Unicode (Closes: #333882)
     - Different rules, scores (Closes: #337617)
     - Doesn't flag certain PGP/MIME messages as empty (Closes: #367635)
     - sa-learn man-page now looks okay in 80 columns (Closes: #312263)
   * Put 65_debian.cf in /etc/spamassassin instead of
     /usr/share/spamassassin/ (Closes: #376610)
   * Recommend libsys-syslog-perl, gnupg (Closes: #395872, #402572, #374435)
   * Depend on libsys-hostname-perl (libnet-dns-perl needs it?) (Closes: 
#400435)  * Suggest libmail-dkim-perl (Closes: #391655)
   * Change the init script to properly restart spamd (would fail if it had
     been previously HUP'd)
   * Install daily cronjob that will automatically update to the newest
     rules (off by default, enable in /etc/default/spamassassin) (Closes: 
#374432)
   * Make sa-update's prerequisites Depends instead of Recommends. (Closes:
     #408472)
   * Stop pointing to the README for mail stream integration help in 
README.Debian (Closes:
     #374714)
   * Remove reference to libnet-dns-perl now that it's required in 
README.Debian (Closes: #319478)
Files: 
 af944e5b9a1f1964b80ae328a4b86aaf 738 mail optional spamassassin_3.2.0-1.dsc
 aed988bb6cf463afc868a64d4cd771a3 1290995 mail optional 
spamassassin_3.2.0.orig.tar.gz
 b374453fb93c893679444f554f58ac76 29145 mail optional 
spamassassin_3.2.0-1.diff.gz
 77eabd50bd26d689b3e76add43607c60 1157488 mail optional 
spamassassin_3.2.0-1_all.deb
 dfcf744f86863a07c04f40869168d9aa 163896 mail optional spamc_3.2.0-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGU1lPqjUzNGvmnNARAjEaAKDT7/WHQlQTZK8K2nUppQiqpjbXugCgjggs
ZqIwMGl03iqXMwAv6mEDb/o=
=W664
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to