Your message dated Tue, 2 Aug 2005 15:35:02 -0400
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #317524,
regarding bogofilter-bdb: seems to be stuck in an endless loop
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(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 317524-forwarded) by bugs.debian.org; 2 Aug 2005 19:35:03 +0000
>From [EMAIL PROTECTED] Tue Aug 02 12:35:03 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 1E02XX-0004DM-00; Tue, 02 Aug 2005 12:35:03 -0700
Received: by acolyte.scowler.net (Postfix, from userid 1000)
id 4232B70055; Tue, 2 Aug 2005 15:35:02 -0400 (EDT)
Date: Tue, 2 Aug 2005 15:35:02 -0400
From: Clint Adams <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED],
Torsten Jerzembeck <[EMAIL PROTECTED]>
Subject: Re: Bug#317524: bogofilter-bdb: seems to be stuck in an endless loop
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL
PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
> >Okay. What if you comment out the charset_default line in your config?
>
> When I do this, bogofilter doesn't end up in the endless loop anymore
> and seems to work as it should.
[Additional information at http://bugs.debian.org/317524 ]
There is apparently a problem if charset_default is set to iso-8859-1 .
I have not attempted to reproduce this yet.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
