Junk email not available if not in cached exch mode

[Andrea]

We recently switched office environments to Windows 2003
Terminal Server, Exchange 2002, and Outlook 2003. Our
users are trying to get thier junk email feature set up,
but they get this error:
"The Junk e-mail filter is not available for your
Microsoft Exchange Server e-mail account because you are
working online. To enable the Junk E-mail filter for this
account, switch to Cached Exchange Mode."

When our technician switches the user to Cached Exchange
Mode, the change never keeps and the checkbox to enable
this feature reverts back to being unchecked.

Cached Exchange Mode is new to our technical team, but if
it's a problem in the terminal server environment and not
because they don't have something set up correctly on the
server, we would like to know. If it is supposed to work,
then could you guide me to where I need to look on the
server for a correct setup.

If you need more detailed information, just let me know.
Thanks so much,
Andrea Kalli

 

[Ben M. Schorr, MVP-OneNote]

I actually answered this in the Exchange.clients group but for the benefit
of all....you can't use Cached mode with Outlook in a Terminal Services
environment. Since the junk filters rely upon cached mode...


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

 

[Guest]

So - what is being done about this? This is a SIGNIFICANT deterrent to using BOTH Outlook 2003 *AND* Terminal Server. Why doesn't "exchange cache mode" work in a Terminal Server environment - Not everyone uses TS across slow network connections - we are using it in-house as a means of extending the useful life of our older equipment..

Not having Junk Email capability in Terminal Server means that we have to find an alternate solution - when one already exists...sure would appreciate any logic behind this..

Also - Not that it matters directly for this discussion, but what is the relationship between junk email and "cached exchange mode"? Is Microsoft looking towards selling another product down the road that ties these two together? I have seen the list of compatible applications that the junk mail capability is compatible with - and Outlook in the "online mode" is not one of them - again, what gives?

 

[Diane Poremsky [MVP]]

Outlooks junk filter is client side - and as such, needs a client side
message store. This can be cached exchange or a pst for non-exchange users.
They are working on a server side filter for Exchange 2003 and I don't
expect it will be available for older versions.

www.slipstick.com/problems/noost.htm
http://support.microsoft.com/support/kb/articles/q277/7/80.asp - this is for
ol2000 but it should work with 2003. Be sure to use the correct reg path -
11.0, not 9.0.


Personally, I would suggest a junk filter on your SMTP server - get rid of
most of the junk before it hits your users inboxes.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)


Search for answers: http://groups.google.com
Most recent posts to the Outlook newsgroups:
http://groups.google.com/groups?as_ugroup=microsoft.public.outlook.*&num=30

 

[Guest]

But *again* why doesn't it work in TS - which emulates the environment of a local desktop in most every other aspect - in Outlook - except offline folders...for those of us on fast connections and a lot of disk space on our servers, it would be nice to have this as an option you could toggle on/off - rather than it not being an option at all...

Agree wholeheartedly about the server-based solution - but that puts the server in charge of determining what is/isn't spam for the entire organization. In most environments, that probably works pretty well but in a law firm, we *often* get emails that contain matters that most spam filters would incorrectly flag...

And on that same note, just because one person says it isn't spam doesn't mean that everyone feels that way - not sure how those using server-based solutions are handling it - some people actually like the junk...with a server based solution, you have the more "authoritarian" approach to spam handling...