A report on my findings thus far: I set up a pristine test environment to try and replicate the problem that Karl has been having. I have been able to setup a system running exim with the same configuration that Karl has, plugged into delivering mail through bogofilter, using the same bogofilter configuration as Karl. To setup the bogofilter databases, I fed approximately 2,000 ham messages and approximately 6,000 spam messages into bogofilter, creating database files in /etc/bogofilter with the same permissions as Exim.
I then proceeded to send test mails. In the beginning bogofilter failed after about 20 messages due to database corruption. This was because the /etc/bogofilter directory was not set to have the correct ownership and permissions as was needed. After confirming with Karl how he had his setup, I changed it in the test scenario and restarted the tests. I ran tests that simulated mail delivery of approximately 1200 messages an hour (approximately 20/minute) for over 24 hours with no failures, I delivered approximately 35,000 messages with no problems at all. This is with exim 4.34-10 and bogofilter 0.93.5-1. It certainly seems that with a fresh installation of these versions everything works as expected. I am now going to try the same suite of tests with version 0.93.3 and then attempt to upgrade to 0.93.5-1 as this is where Karl seemed to have a problem, moving from 0.93.3 to 0.93.5. I need to somehow track down an older version of the .deb. micah On Thu, 10 Feb 2005, Clint Adams wrote: > > >Can you provide the configuration you use with exim to plug bogofilter > > >in? I am particularly interested because version 4.34-10 of exim > > >depends on libdb3 and exim 4.44-2 depends on libdb4.2 so I am curious > > >to know if exim uses libdb to interface with bogofilter in any way. > > > > > >micah > > > > I can use libdb - but I'm not using any db lists. > > That's an interesting question; maybe you should try the exim in > project/experimental, which is linked against libdb4.2. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
