Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem with spamassassin

0 views
Skip to first unread message

Vittorio

unread,
May 26, 2003, 8:30:24 AM5/26/03
to
As an absolute beginner with spamassassin, I check my mail by means of
procmail and spamd (started at boot time). In a nutshell it seems all to work but....

1) Procmail warns that:
"procmail: Skipped ". All servers run spamd(1) so users should"
What steps should I take?

2) the console is flooded by the following warning:

"Cannot open bays_path $HOME/.spamassassin/bayes R/W: file exists" AND
"Cannot open bayes_path $HOME/.spamassassin/bayes R/O: Inappropriate
ioctl for device"

What does it mean and what should I do?

Ciao
Vittorio


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

ooboob

unread,
May 26, 2003, 3:05:29 PM5/26/03
to
On Mon, 26 May 2003 14:30:24 +0200, Vittorio <vde...@supereva.it>
wrote:

> 2) the console is flooded by the following warning:

> "Cannot open bays_path $HOME/.spamassassin/bayes R/W: file exists" AND
> "Cannot open bayes_path $HOME/.spamassassin/bayes R/O: Inappropriate
> ioctl for device"

Most likely you apt-get upgraded, and your version of perl and/or
libdb were upgraded. Thus the problem is that spamassassin's Bayes
databases were created with an older version of perl and/or libdb, and
now you have a newer version that can't read them.

I have yet to figure out a way to save all that hard work that went
into the thousands of messages I separated and scanned. >:(

oob

ooboob

unread,
May 27, 2003, 10:52:26 AM5/27/03
to
> "Cannot open bays_path $HOME/.spamassassin/bayes R/W: file exists"
> AND "Cannot open bayes_path $HOME/.spamassassin/bayes R/O:
> Inappropriate ioctl for device"

I found a solution.

First check the files you have by running "file" against them.
bayes_seen and bayes_toks are probably gonna be:

% file bayes_*
bayes_seen: Berkeley DB (Hash, version 5, native byte-order)
bayes_toks: Berkeley DB (Hash, version 5, native byte-order)

Then apt-get install db4.1-util and run db4.1_upgrade on both of those
files. Check them again with "file" and you should see:

% file bayes_*
bayes_seen: Berkeley DB (Hash, version 7, native byte-order)
bayes_toks: Berkeley DB (Hash, version 7, native byte-order)

This should fix everything. :-)

paul lesiak

unread,
Jun 12, 2003, 8:04:09 PM6/12/03
to
ooboob <o...@oob.oob> wrote in message news:<0ku6dv88sgph3l8jr...@4ax.com>...

>
> I found a solution.
>
> First check the files you have by running "file" against them.
> bayes_seen and bayes_toks are probably gonna be:
>
> % file bayes_*
> bayes_seen: Berkeley DB (Hash, version 5, native byte-order)
> bayes_toks: Berkeley DB (Hash, version 5, native byte-order)
>
> Then apt-get install db4.1-util and run db4.1_upgrade on both of those
> files. Check them again with "file" and you should see:
>
> % file bayes_*
> bayes_seen: Berkeley DB (Hash, version 7, native byte-order)
> bayes_toks: Berkeley DB (Hash, version 7, native byte-order)
>
> This should fix everything. :-)

I tried this and it worked perfectly. Thank you for that quick and easy fix!

0 new messages