Converting bayes DB to MySQL
I'm in the process of converting my Bayes DB setup from in users' home directories (since I'm setting up a separate SpamAssassin server, and accessing Bayes via NFS is causing insane amounts of I/O). After a bunch of fiddling, I have a MySQL server set up properly, tables created, and a spamassassin user set up so I can populate the database. I have 432 users, with about 1.6 GB of Bayes data to import (from sa-learn --backup). I started the import last Friday around 10am, and it's still running (Monday at 1pm), on user 379. My question is this: is this normal? I don't really have any SQL administration experience, so this is all very new to me. For what it's worth, I'm using InnoDB instead of MyISAM tables. smime.p7s Description: S/MIME Cryptographic Signature
Re: Converting bayes DB to MySQL
Michael Parker wrote: Dan Bongert wrote: I'm in the process of converting my Bayes DB setup from in users' home directories (since I'm setting up a separate SpamAssassin server, and accessing Bayes via NFS is causing insane amounts of I/O). After a bunch of fiddling, I have a MySQL server set up properly, tables created, and a spamassassin user set up so I can populate the database. I have 432 users, with about 1.6 GB of Bayes data to import (from sa-learn --backup). I started the import last Friday around 10am, and it's still running (Monday at 1pm), on user 379. My question is this: is this normal? I don't really have any SQL administration experience, so this is all very new to me. For what it's worth, I'm using InnoDB instead of MyISAM tables. Thats probably normal, import takes awhile with SQL since its a lot of inserts and updates. That's good--I was hoping this wouldn't be a performance issue once the system goes into production, though I guess we'll see about that. smime.p7s Description: S/MIME Cryptographic Signature
3.1 seems worse than 2.64?
I recently did an email server change/upgrade from Sendmail on FreeBSD (w/ Spamassassin 2.6.4) to Postfix on RHEL 3 (w/Spamassassin 3.1). On both systems, Spamassassin is called from user's .procmailrc files--not every user wants to be running SA (I'm not quite sure why). I wasn't able to convert people's Bayes databases from one system to the other--the Linux system didn't recognize them at all as valid DB files, so everyone had to start Bayes over from scratch. Here's my problem: the new SA doesn't work nearly as well as the old one. Some of my users are reporting 50% false negatives in their inbox in the morning, even after their Bayes autolearning has kicked in. We run a nightly learning script for them, and have been telling everyone to put any and all false negatives in the appropriate mailbox so that sa-learn can snag them. For my own experiences, I'm seeing a lot more spam that's being autolearned as ham--scores of 0.0 and even negative ones for things that to my eyes are very obviously spam. It's a pretty vanilla set up so far--are there any recommended optional rules sets or tweaks I haven't discovered for 3.1 yet? Unfortunately, I don't have any hard numbers comparing the set ups, just lots of complaints that the new version isn't as good. -- Dan Bongert [EMAIL PROTECTED] SSCC Unix System Administrator smime.p7s Description: S/MIME Cryptographic Signature
