Your message dated Sat, 3 Sep 2005 22:46:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line no response
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 9 Jul 2005 11:56:43 +0000
>From [EMAIL PROTECTED] Sat Jul 09 04:56:43 2005
Return-path: <[EMAIL PROTECTED]>
Received: from finch.datentrampelpfad.de [195.60.111.220] (Debian-exim)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DrDwp-0004rg-00; Sat, 09 Jul 2005 04:56:43 -0700
Received: from toje by finch.datentrampelpfad.de with local (Exim 4.52 #1
(Debian))
id 1DrDwh-0008Ff-P3; Sat, 09 Jul 2005 13:56:35 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="ISO-8859-15"
From: Torsten Jerzembeck <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: bogofilter-bdb: seems to be stuck in an endless loop
X-Mailer: reportbug 3.15
Date: Sat, 09 Jul 2005 13:56:35 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_01,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: bogofilter-bdb
Version: 0.95.2-1
Severity: grave
Justification: renders package unusable
After upgrading to the current unstable version of bogofilter-bdb,
bogofilter seems to get stuck in an endless loop on every operation
accessing the wordlist.db. This happens even with an nonexisting
wordlist.db, an new one is created in this case, but bogofilter gets
stuck anyway.
top output shows bogofilter consuming all available CPU, the memory
footprint doesn't seem to grow, however. From the outside it looks as if
bogofilter is stuck in an endless loop.
My /etc/bogofilter.cf is attached below.
Greetings from Münster,
=ToJe=
--------- by cutting here you might damage your screen surface ---------
/etc/bogofilter.cf:
# Comment lines MUST have their hash mark in the leftmost column.
# Comments can be added at the end of any line (after whitespace and a '#').
# Blank lines are allowed.
########### General Settings ########################################
#### BOGOFILTER_DIR
#
# directory for wordlists
#
#bogofilter_dir=~/.bogofilter
##bogofilter_dir=/var/spool/bogofilter
#### name/location of user config file
#
#user_config_file=~/.bogofilter.cf
##user_config_file=~/.bogofilterrc
##user_config_file=~/.bogofilter/config
#### TRANSACTIONS: enable/disable database transactions
#
# boolean indicating whether transactions
# should be enabled (yes) or disabled (no)
#
#db_transaction=no # default
##db_transaction=yes # (alternate)
#### WORDLIST: define additional word lists
#
# char type: 'r' (regular) or 'i' (ignore)
# char *name: name of list, e.g. "system", "user", "ignore"
# char *path: absolute path to file or
# file name (relative to bogofilter_dir)
# int order - once found, skip higher numbered lists
#
##wordlist i,ignore,~/ignorelist.db,1
##wordlist r,wordlist,~/wordlist.db,2
#### SPAM_HEADER_NAME
#
# used in reporting spamicity and
# in removing already existing headers
#
#spam_header_name=X-Bogosity
#### SPAM_SUBJECT_TAG
#
# tag added to "Subject: " line for identifying spam or unsure
# default is to add nothing.
#
##spam_subject_tag=***SPAM***
##unsure_subject_tag=???UNSURE???
#### STATS_IN_HEADER
#
# non-zero (default): put spamicity info in message header
# zero: put spamicity info in message body
# can use "bool" values of True, False, Yes, No, 1, or 0
#
#stats_in_header=Yes # default
##stats_in_header=No # (alternate)
#### DB_CACHESIZE
#
# non-zero: set this as DB cache size (in Mbytes)
# zero: use DB default cache size (.25 Mbyte in 4.0.14)
#
# note that Berkeley DB increases any buffer size below 500 MB
# by 25%!
# This helps most when doing massive changes to the data base that
# involve a lot of overwrites, such as registering mail boxes,
# whereas it is mostly a waste of memory for read-only
# applications such as scoring.
# WARNING: If you set this too large, bogofilter will fail.
#
#db_cachesize=0 # default
##db_cachesize=16 # (alternate)
#### DB_LOG_AUTOREMOVE
#
# boolean indicating whether auto-removing of
# logs should be enabled (yes) or disabled (no)
#
#db_log_autoremove=no # default
###db_log_autoremove=yes # (alternate)
#### TIMESTAMP
#
# enables or disables token timestamps
#
#timestamp=Yes
#### Format of spamicity output
#
# for two-state output the third entry is not needed and not used
#
#spamicity_tags = Spam, Ham, Unsure
#spamicity_formats = %0.6f, %0.6f, %0.6f
#
##spamicity_tags = Yes, No, Unsure
##spamicity_formats = %0.6f, %0.6f, %0.6f
#### Format of SPAM_HEADER
#
# formatting characters:
#
# h - spam_header_name, e.g. "X-Bogosity"
#
# c - classification, e.g. Yes/No, Spam/Ham/Unsure, +/-/?
#
# D - date, fixed ISO-8601 format for Universal Time ("GMT")
#
# e - spamicity as 'e' format
# f - spamicity as 'f' format
# g - spamicity as 'g' format
#
# A - IP address (from first Received: statement having one)
# Not guaranteed to be the originating address of the message.
# I - Message ID
# Q - Queue ID (from first id tag found in Received: headers)
#
# l - logging tag (from '-l' option)
#
# o - spam_cutoff, ex. cutoff=%o
#
# p - spamicity value
# d - if ham or unsure, the spamicity
# if spam, difference of spamicity from 1.0
#
# r - runtype
# w - word count
# m - message count
#
# u - username - this will either be the login from getlogin(),
# if that is empty, the pw_name obtained from
# the password database, or the user id
# prefixed by #, for instance, #1003
#
# v - version
#
# customizable messages:
#
# header_format - the "X-Bogosity" line that '-p' adds to
# the message header and '-v' outputs.
# terse_format - an abbreviated form of header_format;
# selected by command line option '-t'
# log_header_format - written to syslog by '-u' option
# when classifying messages.
# log_update_format - written to syslog by '-u' option
# when registering messages.
#
#
#header_format = %h: %c, tests=bogofilter, spamicity=%p, version=%v
#terse_format = %1.1c %f
#log_header_format = %h: %c, spamicity=%p, version=%v
#log_update_format = register-%r, %w words, %m messages
##log_header_format = %h: %c, spamicity=%f, ipaddr=%A, queueID=%Q, msgID=%I,
version=%v
#### TERSE
#
# if enabled, format the X-Bogosity using the 'terse_format' specificaton.
#
#terse=no # default
##terse=yes # (alternate)
########### Tokenizer Settings ######################################
#### BLOCK ON SUBNETS
#
# convert IPADDRs into a special token, url:1.2.3.4,
# and also return url:1.2.3, url:1.2, and url:1
# to allow identifying spammers by ip address / subnets.
#
#block_on_subnets=no
#### CHARSET handling
#
# specify default charset
#
#charset_default=us-ascii # default
charset_default=iso-8859-1 # (alternate)
##charset_default=cp866 # for Russian
#### REPLACE_NONASCII_CHARACTERS
#
# replace non-7bit chars with '?'
#
#replace_nonascii_characters=N # default
##replace_nonascii_characters=Y # (alternate)
#### UNICODE handling
#
# boolean indicating whether raw storage (no) or unicode (yes)
# is the default encoding for the wordlist
#
#unicode=yes # default
##unicode=no # (alternate)
########### Classification Constants Settings #######################
#
# See man page for a more detailled description of the parameters.
#### MINIMUM DEVIATION
#
# if token spamicity closer to EVEN_ODDS (0.5)
# than MIN_DEV, don't use the word in the
# spamicity calculation
#
#min_dev=0.375 # default
#### Robinson Constants
#
# floating point values for
# Robinson S and X coefficients.
#
#robs=0.0178 # default
#robx=0.52 # default
#### CUTOFF Values
#
# both ham_cutoff and spam_cutoff are allowed.
# setting ham_cutoff to a non-zero value will
# enable tri-state results (Spam/Ham/Unsure).
#
#ham_cutoff = 0.45 # default
#spam_cutoff= 0.99 # default
#
# for two-state classification:
#
##ham_cutoff = 0.00 # default
##spam_cutoff = 0.99 # default
#### Effective Size Factor Values
#
#ns_esf = 1.000 # default
#sp_esf = 1.000 # default
#### Auto-update threshold
#
# Skip autoupdating if the spamicity is within this value
# of 0.000000 (surely ham) or 1.000000 (surely spam).
#
## thresh_update=0.01 # (optional)
--------- by cutting here you might damage your screen surface ---------
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages bogofilter-bdb depends on:
ii bogofilter-common 0.95.2-1 a fast Bayesian spam filter (commo
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libdb4.3 4.3.28-2 Berkeley v4.3 Database Libraries [
ii libgsl0 1.6-2 GNU Scientific Library (GSL) -- li
bogofilter-bdb recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 317524-done) by bugs.debian.org; 4 Sep 2005 02:46:12 +0000
>From [EMAIL PROTECTED] Sat Sep 03 19:46:12 2005
Return-path: <[EMAIL PROTECTED]>
Received: from acolyte.scowler.net [216.254.112.45]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EBkWK-0001GL-00; Sat, 03 Sep 2005 19:46:12 -0700
Received: by acolyte.scowler.net (Postfix, from userid 1000)
id 838A470055; Sat, 3 Sep 2005 22:46:11 -0400 (EDT)
Date: Sat, 3 Sep 2005 22:46:11 -0400
From: Clint Adams <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: no response
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
Reopen this bug if you have additional information.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
