This update provides the Junk E-mail Filter in Microsoft Office Outlook 2003 with a more current definition of which e-mail messages should be considered junk e-mail. This update was released in July 2006.
The time now is
1:45:25 PM
ET.
Any comment problems?
E-mail us
#1 By
2960 (68.101.39.180)
at
7/13/2006 9:43:39 AM
I have to say, though I'm not a fan of non-learning Spam systems, this one has been doing a damned fine job lately.
It catches nearly everything that my (deplorable) cable companies filters miss (Cox).
TL
#2 By
8556 (12.217.111.92)
at
7/13/2006 10:13:49 AM
Larry: I have not been a fan of Outlook as it was slow and cumbersome. Outlook 2003 is a great program and includes an incredibly accurate anti-spam filter. It has been excellent from day one and is getting better.
Too bad the filter isn't used on Hotmail, which has the worst anti-spam filter availbale. Typical Microsoft, both good and bad stuff is provided.
#3 By
3653 (68.52.143.149)
at
7/13/2006 7:57:16 PM
agreed TL. I have used my work email address for over 10 years, which means I get a crazy amout of spam. The Outlook junk email filter catches ~150 junk emails per day for me... but still leaving me with ~10 per day. I'm quite happy with it. The price is right too.
#4 By
23275 (68.17.42.38)
at
7/13/2006 11:08:59 PM
Using OL 2003 as a client to EXCH 2K3 with the intelligent message screener and you'll have zero SPAM of any kind and no false positives. It really does work. Run it using an RPC/HTTPS connection and you can use E2K3 as though you are on your LAN from any network and any location [precious few networks block the default SSL TCP Port]. It is the best messaging combination in the market and so very stable.
#5 By
3653 (68.52.143.149)
at
7/14/2006 3:41:50 AM
good point lketchum. I neglected to say that we are using EXCH 2K, so no intelligent message filter on the server.
#6 By
2960 (68.101.39.180)
at
7/17/2006 12:21:42 PM
#4,
Since I work from a home office, that's how I connect to the exchange server as well.
Yup - that is the best way - we've been doing it since Aug 2004 and it is so awesome.
Prior to that we did it via forced encryption over TCP - using ISA Server 2000 and secure RPC publishing of Exchange via ISA - problem was that while safe, one could not assure that all networks could make an out-bound request for TCP port 139.
So RPC over HTTP(S) on default SSL 443 was/is the answer.
We were still so very glad to be able to offer [safely] secure RPC publishing of Exchange 2000/2003 via ISA Server - it was so rare back then.
Also, when we first did it RPC over HTTP(S) was tough to do - now its is a few clicks - kind of took the pleasure out of being skilled enough to do it.
#8 By
4240821 (213.139.195.162)
at
10/27/2023 12:50:26 AM