* This is the modus mailing list * We saw the same problem here and the issue is that there is no direct correlation between the configurable settings of the pre SCA modus and what we have now. In our case I opened the registry backup and searched by domain for all the settings that did not follow the server defaults, analyzed them and set them up accordingly. The best Vircom could do would be to have a utility during the upgrade that outlined each account and domain that differed from the server defaults and what the setting were so the installed could make the appropriate adjustments.
There is an important note to this however. During the beta, a number of us were a bit taken back with the idea of running the server defaults on the extreme level. Experience shows us that is the best thing to do with the new engine. There is almost no way to compare the way the new engine works compared to the old. If you drop back to the strong or normal level the porn spam gets through and some family pictures still get quarantined. It doesn't have so much to do with what it is as how it is represented in the message that apparently triggers the SCA. Our customers appreciate it. The handful of customers bummed about not being able to get a picture of their granddaughter without any accompanying text usually understand that sort of message is the prime porn method of delivery. That is what the quarantine report and whitelist are their to solve. Mark Thornton San Marcos Internet, Inc 512-393-5300 ----- Original Message ----- From: "Micha�l Gaudette" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 19, 2003 8:42 AM Subject: [Modus] Warning to those upgrading to 3.0 regarding Anti-Spam settings * This is the modus mailing list * Hi, We've heard about that in the past but nobody in Beta had been able to put it's finger on it. The information given on this mailing list now should help us correct it for the next Release version. We will be trying to reproduce it here (sounds easy from what I hear) and will let you know. Regards, ------------------------------------- Micha�l Gaudette, P.Eng., M.B.A. Product Manager Vircom Inc. [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Willis - MIS Sent: Wednesday, November 19, 2003 12:44 AM To: [EMAIL PROTECTED] Subject: [Modus] Warning to those upgrading to 3.0 regarding Anti-Spam settings * This is the modus mailing list * Yikes guess I will be putting off the upgrade until this is resolved. With over 800 domains and 6000+ users, many with settings different than the domain, and many domains that override the server default, this will be a real problem and can not afford to take a chance Vircom: Please comment on this Jeff ----- Original Message ----- From: "Darryl Dunkin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 18, 2003 20:58 Subject: [Modus] Warning to those upgrading to 3.0 regarding Anti-Spam settings * This is the modus mailing list * This was also my issue with it (as I just upgraded today). It makes getting upgrades past the bigwigs a little more difficult when you don't have all day to handle an upgrade like this, unforseen consequences are accounted for, but not on this scale. Results should be predictable. At least one-click release kept working, end users can get whiney if you change things like this on them. -Darryl -----Original Message----- From: Jon Benson [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 20:26 To: Modus (E-mail) Cc: Vircom Support (E-mail); [EMAIL PROTECTED] Subject: [Modus] Warning to those upgrading to 3.0 regarding Anti-Spam settings Importance: High * This is the modus mailing list * Hi all, I just discovered that the upgrade not only set the server wide default for Anti-Spam from Disabled to Extreme, which I could cope with due to watching this list, but it overrode all domain level settings to be Extereme as well!! It appears to have done this as instead of using the existing key values they've added another key (DomainMailboxesSieveLevel) which now controls all settings and if it doesn't exist it defaults to Extreme. IMHO it should default to Normal and as part of the upgrade should have chosen the least agressive of the existing levels. NOTE: Even worse, this did NOT effect the sieve behavior so it's possible that some domains have gone from Disabled/Delete to Extreme/Delete as a consequence of the upgrade and are having legitimate email deleted. :( It would be nice if changes of this nature were CLEARLY documented with a rather large warning in the upgrade notes. Oh well, I know what I'm working on fixing with the rest of my day. Regards, Jon Benson Mail/DNS/Linux Administrator OzHosting.com ** 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. ** 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. ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line.
