> I can reproduce the problem. bogofilter 0.94.13-1 did not have this > bug. > > Like for the original submitter, it does not seem to depend on the db > - fails with both existing, and newly created one (removed > ~/.bogofilter) - and it also does not seem to depend on the message > either: > > --8<--- > $ echo foo | bogofilter -c /etc/bogofilter.cf~ -vvxdi > probing "/home/elho/.bogofilter" and "wordlist.db" for > environment...T_ENABLED > open_lockfile: open(/home/elho/.bogofilter/lockfile-p) succeeded, fd > #3 > db_env_create: 0x807318c > DB_ENV->set_cachesize(4) > DB_ENV->set_lg_max(1048576) > DB_ENV->open(home=/home/elho/.bogofilter) > db_version: Header version 4.3, library version 4.3 > [pid 8598] DB->open(db=0x8073f48, file=wordlist.db, database=NIL, > type=1, flags=0x1000010=DB_RDONLY DB_AUTO_COMMIT , mode=0664) -> 0 > Successful return: 0 > DB->get_byteswapped: false > DB->fd: 5 > DB->stat success, pagesize: 4096 > converting iso-8859-1 # (alternate) to UTF-8 > Conversion from 'iso-8859-1 # (alternate)' to 'UTF-8' is > not supported. > --8<--- > > At this point bogofilter sits in an infinite loop using up all > available CPU time. > > The only difference of /etc/bogofilter.cf~ to the default config is > the charset_default=iso-8859-1 setting.
Does it work fine if you remove the trailing spaces and comment from the config line? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
