Exchange Folders not displaying

  • Thread starter Erle S. Bridgewater
  • Start date
E

Erle S. Bridgewater

Imported all my accounts, etc into test drive 2004. Everything seems to work
ok; even exchange seems to check the mail ok. However, no inbox, no other
boxes showing up, except ³public folders² and frankly no folders below that
showing up either. Perhaps something simple that has already been addressed
here but I can¹t find any thread with these issues. As of now Test Drive
2004 is a failure.

I¹m running Max X 10.3.3
Entourage X works fine except Contacts won¹t sync (which was why I was
trying 2004)
Sent using the Microsoft Entourage 2004 for Mac Test Drive.
 
B

Bob B

I¹m having the same problem. I didn¹t see a reply on this one. Could someone
help me (us) out? Thanks...
 
D

Diane Ross

Imported all my accounts, etc into test drive 2004. Everything seems to work
ok; even exchange seems to check the mail ok. However, no inbox, no other
boxes showing up, except ³public folders² and frankly no folders below that
showing up either. Perhaps something simple that has already been addressed
here but I can¹t find any thread with these issues. As of now Test Drive 2004
is a failure.
Click to expand...


I¹m not an exchange user, but try doing a refresh. There is an exchange
support section that might help with your questions.

Exchange Support <http://www.entourage.mvps.org/exchange/index.html>
 
C

Corentin Cras-Méneur [MVP]

Forgot to add... Try option-command-L. It does an (undocumented) "special"
IMAP refresh.
Click to expand...

Doesn't work for Exchange in Entourage 2004 since Exchange now uses DAV for
mail :-\
I usually quit and relaunch but you can "switch identity" and reselect your
own account to force Entourage to resync.

Corentin
 
B

Brett Belcastro

I can't get my account to connect. It works fine in X, but not 2004. What is
the deal???
 
C

Corentin Cras-Méneur [MVP]

I can't get my account to connect. It works fine in X, but not 2004. What is
the deal???
Click to expand...

Is webmail active on the server you entered as your Exchange server ??


Corentin
 
V

Vaughn R. Hamilton

Doesn't work for Exchange in Entourage 2004 since Exchange now uses DAV for
mail :-\
I usually quit and relaunch but you can "switch identity" and reselect your
own account to force Entourage to resync.
Click to expand...

I just started using Entourage 2004 yesterday and I suspected that they had
changed it to WebDAV when I found certain messages would not show up in my
Exchange Inbox. Any message with an illegal character in the subject line
(like a period or an ampersand) won't be displayed in the Inbox -- it's like
the message doesn't even exist!

Outlook Web Access has a similar limitation, but at least with OWA you can
see that the message is in your Inbox you just can't display the message.
Does anyone know if this issue will be addressed or even *can* be addressed
given the switch from straight IMAP to WebDAV? We're using Exchange 2000 --
does 2003 offer some kind of work around?

I really like Entourage 2004, so I'd like to deploy it throughout our
various Prepress/Art Departments but I'd probably get in trouble for doing
so with a known issue like this.

Thanks in advance for any help!
 
V

Vaughn R. Hamilton

I noticed that Entourage 2004 is using WebDAV instead of plain old IMAP for
message transfers. As a result, I found that certain folders would not
synchronise, and certain email messages simply would not show up in my
display even though I knew they were on the server. The problem messages
and folders were those that had prohibited characters in the folder name or
email subject. These characters were such as an ampersand, a percent sign,
a period at the end of the line, and so on.

I first noticed this behaviour with Outlook Web Access, so I recognised it
immediately in Entourage 2004 as related to the common Web services being
used on the Exchange 2000 server for both purposes. I finally found the
cause and resolution to the problem and wanted to share it here in case
anyone else is experiencing this.

The IIS Lockdown tool was previously run on our Exchange 2000 server system.
Left in its default lockdown state, it is designed to prevent illegal code
execution by prohibiting the processing of certain characters in certain URL
contexts. Since this server is not serving any other web based resources
than Outlook Web Access (and since I'm the Network Administrator who should
have known this already) I made the modifications on the server to allow for
these otherwise prohibited characters to be processed. This cleared up the
problem described above.

The full explanation of this is found in the Microsoft Knowledge Base
Article #309677 entitled " XADM: Known Issues and Fine Tuning When You Use
the IIS Lockdown Wizard in an Exchange 2000 Environment."

<http://support.microsoft.com/default.aspx?scid=kb;EN-US;309677>

If I've overlooked anything here I'd appreciate being corrected.

I hope this is of help to someone else out there.
 
Top