Interviewed by CNN on 30/08/2012 07:10, Interges told the world: > Making a new install, all has gone fine. Seems that Symantec has been testing > the file that I sended to them, and now I can install the update. > > Thank your for a nonexistent technical support. Bye. >
(...sigh...) Well, it was fixed by the people who made the mistake in the first place. You are obviously frustrated about the problems you had, and that's understandable. But you assign blame in the wrong direction. You seemed to argue in a previous message that the SM team should have tested the build against Norton, since it's one of the largest antivirus vendors around. Well, that's not really realistic. SM can't do it. Mozilla can't do it. *Google* can't do it. *Microsoft* can't do it. Even SYMANTEC ITSELF can't release software and guarantee it won't be hit by a "false positive" from Norton. Why? Because it's a moving target. Antivirus vendors release updated signature files very often -- every few hours in most cases. At any time a new signature can mistakenly start detecting some innocent piece of software as a "dangerous virus." The antivirus vendors depend on user feedback to track those cases. This time you were the unfortunate victim. It happens. Life goes on. It happened to me in the past -- my antivirus suddenly started complaining about the new version of some Nirsoft tools it never had problems with previously. I did the "submit false positive" dance and they eventually fixed it. Did I blame Nir Sofer? No, he is powerless to control this. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my Intellivision. * Added by TagZilla 0.7a1 running on Seamonkey 2.12 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
