|
|
User Controls
|
New User
|
Login
|
Edit/View My Profile
|
|
|
|
ActiveMac
|
Articles
|
Forums
|
Links
|
News
|
News Search
|
Reviews
|
|
|
|
News Centers
|
Windows/Microsoft
|
DVD
|
ActiveHardware
|
Xbox
|
MaINTosh
|
News Search
|
|
|
|
ANet Chats
|
The Lobby
|
Special Events Room
|
Developer's Lounge
|
XBox Chat
|
|
|
|
FAQ's
|
Windows 98/98 SE
|
Windows 2000
|
Windows Me
|
Windows "Whistler" XP
|
Windows CE
|
Internet Explorer 6
|
Internet Explorer 5
|
Xbox
|
DirectX
|
DVD's
|
|
|
|
TopTechTips
|
Registry Tips
|
Windows 95/98
|
Windows 2000
|
Internet Explorer 4
|
Internet Explorer 5
|
Windows NT Tips
|
Program Tips
|
Easter Eggs
|
Hardware
|
DVD
|
|
|
|
Latest Reviews
|
Applications
|
Microsoft Windows XP Professional
|
Norton SystemWorks 2002
|
|
Hardware
|
Intel Personal Audio Player
3000
|
Microsoft Wireless IntelliMouse
Explorer
|
|
|
|
Site News/Info
|
About This Site
|
Affiliates
|
ANet Forums
|
Contact Us
|
Default Home Page
|
Link To Us
|
Links
|
Member Pages
|
Site Search
|
Awards
|
|
|
|
Credits
©1997/2004, Active Network. All
Rights Reserved.
Layout & Design by
Designer Dream. Content
written by the Active Network team. Please click
here for full terms of
use and restrictions or read our
Privacy Statement.
|
|
|
|
|
|
|
|
Time:
04:30 EST/09:30 GMT | News Source:
ZDNet |
Posted By: Alex Harris |
My main mail client is Outlook 2002. This is no corporate mandate; it's just me here. I've had lots of problems with Outlook over the years and on occasion I've tried to change to another program, but I've always come back. There's just no other program that does all the key things it does. Why not?
We've talked this question over here at Tech Update: Why has the software industry not produced a plug-in replacement for Microsoft Outlook? Few products, even other Microsoft products, get as much bad press as Outlook. Personally I think most of the criticism of Outlook is overstated, but that's not what's important. There's a market opportunity here.
The real key, especially in the corporate market, is to produce a client that supports Microsoft Exchange and is interoperable with Outlook for supporting e-mail, calendaring, and some other groupware features.
Instead, the software industry seems more taken with the notion of replacing Exchange and leaving Outlook in place. Oracle has their Collaboration Suite and Bynari makes a number of server products that support Outlook clients.
|
|
#1 By
6859 (204.71.100.215)
at
8/29/2002 9:01:09 AM
|
This is exactly the reason (IMO) that OSS has failed. There is a real market out there for a true Outlook replacement, but there isn't. Heck, they (the OSS/WINE/Emulator people) can't even get Outlook in CW mode to operate on their systems, so it shouldn't be a surprise, but that's key. If they had a real replacement for Outlook, perhaps, just perhaps, corporate desktop use of Linux would grow.
This post was edited by Cthulhu on Thursday, August 29, 2002 at 09:01.
|
#2 By
135 (209.180.28.6)
at
8/29/2002 10:11:56 AM
|
I'm going to go out on a limb here, but I rather suspect that not one person currently running Outlook 2002 in it's minimal default configuration has passed on a virus. Klez or otherwise.
|
#3 By
6253 (12.237.219.240)
at
8/29/2002 11:00:26 AM
|
sodablue is right. Part of the problem is that people are unwilling to update. Even if you're still on Outlook 2000, there are free patches to provide the functional equivalent of 2002's security features. But heck, lots of people on 2002 go out of their way to disable or bypass 2002's protections, so the other part of the problem is that the vocal minority of customers are blaming Microsoft's code for security holes while the silent majority is going around creating the real security holes.
A few months ago, I ran into a user who received an exe file attachment. Outlook 2000 SP2 prevented her from getting to it. While she was fighting with Outlook, the person whose name appeared in the "From" field of that message came over to her desk, looked at the message, and told her that he did not send it. At that point, you would think that she would delete the message and move on. Nope. She went around until she found a machine with Outlook 97 which let her get to the attachment, but antivirus software on that machine stopped her from launching it or saving it. So she disabled the antivirus software and finally managed to launch the exe attachment. The saddest part is that the machine it clobbered wasn't even her own.
The Ximian Connector is really ridiculous, because it uses OWA to talk to Exchange 2000. Hello? If you already have OWA with Exchange 2000 (and you always "have" OWA whenever you have Exchange 2000 unless you disable or block access to it), then you already have a good equivalent to Outlook which can be accessed by any capable browser.
Some features of OWA (such as being able to drag and drop messages into the folder treeview) don't work as smoothly if your browser isn't IE 5.5 or higher. You can still perform all the essential functions with any HTML 3.2 compatible browser. It just might take a few extra clicks when compared to drag and drop.
What Ximian is doing is saying that, rather than implement a browser for Linux which matches IE's capabilities, their Connector will treat OWA as a web service by connecting to it as if the connector were IE, then parsing or "scraping" the content and re-rendering it within their Evolution client. Evolution can then provide the drag and drop type stuff. That stuff is then translated back into http get/post messages to be sent back to OWA.
For this, Ximian wants $69 per user. OK, $58 with volume discounts. That's $58-69 more than using OWA directly with your choice of free browsers on Linux. Either way, you're going through OWA, so there's nothing you will ever be able to do through the Evolution Connector that you can't do through OWA alone, and the Connector will never perform faster or more securely than OWA alone. All you get for $58-69 is a more fluid GUI "feel" on Linux.
If that's what you want, for $78 per user, Microsoft will sell you a Terminal Services CAL which you can use with an RDP client for Linux. So for $9-20 more, you get real Outlook 2002 on a Linux desktop. (Exchange 2000 CALs include a free license for Outlook 2002 even if you don't have Office, or even if you use an older version of the other Office apps. You have to have the Exchange CAL in order to have a mailbox, so the cost of the Exchange CAL is equal for Outlook vs. Evolution.) Another way of looking at it is that you could save $9-20 per user, as long as you're willing to go with an immature product which could waste $20 worth of a non-Linuxhead's productivity in a single day.
|
#4 By
4209 (64.175.184.131)
at
8/29/2002 11:20:38 AM
|
I would have had that user fired for disabling the AV software and then putting a virus on a company PC. She does not deserve to own or use a PC if she is that stupid.
|
#5 By
1190 (63.28.229.195)
at
8/29/2002 11:24:09 AM
|
I really hate Outlook. I hate the ugly VB interface, bloated, unintuitive layout. What really galls me is that it hasn't changed since Office 97. More features have been added, but the design has remained the same, right down to the old 256 color icons. Microsoft's MacBU has developed a really well designed product called Entourage. I would give anything if Microsoft would adapt some of the GUI elements from this product into Outlook. Or even port it to Windows altogether (not a likely scenario).
Microsoft has developed some of the best, and worst, software I have ever used. Outlook falls into the latter category.
|
#6 By
135 (209.180.28.6)
at
8/29/2002 1:13:45 PM
|
hmmm - "And if you have the AV software updated, why install the security patch or Outlook 2002 to block attachments when you can run your email client in the restriced zone?"
That's a simple answer...
Because nearly all the major worm/virus outbreaks have been the result of programs the antivirus vendors do not yet have signatures for. ILoveYou comes to mind, but the main one I can think of is Nimda. When Nimda hit in the morning, we didn't have an anti-virus signature for it from McAfee until about 11pm that night.
So it is important to not only block attachments and scripting, but also have antivirus software so you cover a variety of bases.
The attachments that Outlook 2000 SR2 and 2002 block, users have no business sending anyway. I mean .exe, .bat, .vbs, etc files. Any user who is sending something like that and knows they need to do it is going to be knowledgeable enough to put them in a .zip file.
|
#7 By
135 (209.180.28.6)
at
8/29/2002 2:57:44 PM
|
hmmm - The security patch for Outlook 2000 and 2002 also blocks COM automation of the Outlook email engine.
I don't believe the small amount of functionality you lose(i.e. ability to send .exe attachments) is worth anything, much less worth the substantial increase in risk you incur. So if you don't have the security patch in place, and/or allow .exe attachments you will have users who open the attachments and run them. Since the virus definitions have not been released, you won't catch it that way either. Even though you cannot execute them, users will still save them to disk and then execute them. The best answer is simply strip the emails of such attachments.
While I understand what you are saying, I do think the security update from Microsoft was one of their best moves, and anybody who does not implement it fully is being extremely foolish.
|
#8 By
2960 (156.80.64.120)
at
8/29/2002 4:23:07 PM
|
Outlook 2002 is a decent email client. Can't beat PST storage for ease of management.
However, it has one problem that kills it in many corporations, and that's poor (nearly non-existent) LDAP support.
If you can even get it to work right (and in most cases you can't) it's SO slow that no one would ever use it.
It is my understanding that MS had so little interest in the LDAP Module in Outlook 2002 that it was farmed out and wasn't even written by MS.
TL
|
#9 By
1845 (12.254.162.111)
at
8/29/2002 8:23:11 PM
|
As a programmer who has used Outlooks COM object to send emails, I'm furious that its been blocked. Well, not blocked, I suppose, but that a message box with a several second wait was added. There are plenty of legitimate reasons for sending email directly from an application. I'm bothered that Microsoft hindered this. I'm more bothered that there doesn't seem to be a way to disable it. Go ahead and ship with lock down mentality, but allow your users to unlock if the default doesn't meet their needs.
|
#10 By
135 (209.180.28.6)
at
8/30/2002 12:28:36 PM
|
BobSmith - I have wondered about this myself. I had a project in mind which would do COM automation of Outlook, but I would want to get around this blocking to.
I've been told that you can do this somewhat by installing a component directly into Outlook as an add-in. Not sure what that would do or how it works, or if it helps, but...
|
|
|
|
|