Thus spake Dennis T Cheung <[EMAIL PROTECTED]>, circa 1/15/2003 10:36 PM: > First, it is unfair and inaccurate to link the vulnerability of some > Microsoft products to all Microsoft products. [...] It's like saying > Mail.app can't be trusted because Apple has had a history of needing > to release Security Updates to patch MacOS X [...] Would that be fair > or accurate?
It would be fair, though inaccurate. I'm sure many of the same programmers worked on both. That's why an attack on the MacBU -- if it had happened -- would have been both unfair and inaccurate. As I understand it, you function like a separate company inside Microsoft. A better company. That said, I thought your reply was a little over the top, and the reply to your reply was written in anger. After rule #1 (see below) I'd add rule #2, "When in doubt, save your message as a draft and re-read it the next day before sending. E-mail in haste, repent at leisure." > Thirdly, I stand behind my advice that attachments shouldn't be opened > without verification and the read the warning dialogs in Entourage. I don't > see how anyone could oppose such a simple piece of advice. This is just common sense and you're right to point it out. Macs are far less likely that PCs to have a problem with attachments, but Mac OS X is still a bit of an unknown to most of us and there could be a Windows scale security problem that has yet to be uncovered. So this is good advice. It does not require you to call the sender to confirm, of course. Just know what kind of file it is and open in the proper application. The big problem with Windows is that a document can *look* like a JPEG, but when you double click it, it runs like a program. Boom, you've just handed complete control of your PC to a program from the net! I doubt this can happen in Mac OS X but I can't guarantee it. So if it looks like a Word file, don't double click it. Save it to disk, switch to Word, and open the file via File>Open. And make sure Word will warn you if the file contains macros! If you're still in doubt, call the sender. They'll understand your paranoia. > Finally, I'll use the cheap excuse that that my original message was > enclosed in <rant></rant> tags and it should've been treated as such. :) That's standard internet procedure. Never get frothed up over something *labeled* as a rant. :-> > Although it may not be evident from my ramblings, security really is a focus > at the Entourage team. As proof, I'd like to cite that Entourage [...] was > -the- first e-mail client on the Mac to warn the customer if an AppleScript > tried to send e-mail through it Well done! I didn't know that. I repeat my earlier wish that the Entourage team should pay the Outlook team a little visit with baseball bats... > In closing, I'd like to say that I wish I had just said that I'm 99% sure > that none of the symptoms reported on this list so far look like a known > virus* for Entourage. I agree. I suspect disk corruption of some sort and would suggest rebooting from a Tech Tool CD to check. I would also investigate the possibility that the problem lies outside Entourage, since the item appears to be correct in the "Sent" folder. The problem seems to lie either in the SMTP server or in Entourage communicating with it. > *First customer to respond to me with the name of the one known Entourage > virus [...] wins a set of Office X for Mac stickers. That was too easy, so I won't be the first.... :-> peter -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
