* This is the modus mailing list * We ran into some problems, but we upgraded from 1.4 to 3, so I don't know if this will apply to you. One thing we ran into is that the ScanSieve column has been overloaded with additional values. Instead of just 1 and 0, it stores 0 through 4 (I believe). Also, the ScanSieveLevel column is currently ignored (confirmed with Vircom tech support).
In regards to the former, we've been running the extended database format since it was introduced in VOPMail. At that time, we were running it against SQL Server 6.5 and had to make up our own scripts. Ever since then, when we have to add columns, we go off of the manual and release notes. However, the manual does not list SQL Server datatypes. Instead, it says things like "Number" with "values of 0 and 1". We interpreted that to mean a BIT field. However, looking at the scripts on the Vircom site, they almost always use INTEGER datatypes. At some point, Vircom overloaded the ScanSieve column. Since it didn't require a change to their scripts, I don't think they really announced the change. We certainly didn't notice it. What we noticed is that we were having problems changing mailbox settings programmatically and that the console didn't seem to reflect the underlying database. Anyway, Vircom tech support figured out what we had done wrong. So, a word of caution: I would check your datatypes against the latest scripts, not the manual. Ben Rogers http://www.c4.net v.508.240.0051 f.508.240.0057 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WMOL Admin Sent: Thursday, December 11, 2003 7:27 PM To: [EMAIL PROTECTED] Subject: [Modus] (FROM VIRCOM) Two important Announcements * This is the modus mailing list * So, we went to v3 today on our production server from the latest v2 with the SpamAssassin wrapper running. I must have something setup wrong here with it because we are seeing huge amounts of spam get past without SA running. We are using the extended database, anyone else who upgraded with extended DB know of any gotchas I may have missed? TIA, Scot ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line. ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line.
