D
David Blaymires
Hi everyone,
Well, we found the answer to our problems. It has to do with URLSCAN which
is something that is applied when the IIS Lockdown Tool is run - in a
nutshell you can run the IIS Lockdown Tool to shut off potential security
issues on your Windows/Exchange/IIS 2000/2003 server. When our Windows 2000
Server with Exchange 2000 Server was installed in March 2003 our IT
Consultant ran the IIS Lockdown Tool using the default settings recommended
when running an Exchange 2000 server.
The result was it prevented emails with certain characters in the subject
from being delivered to Entourage 2004 clients. One of the articles
mentioned below indicates that this should/could also have impacted on us
when using Entourage X, but we did not find this to be the case. Email only
stopped being delivered when we were using Entourage 2004.
The default URLSCAN.ini file settings also prevents emails being opened in
Outlook Web Access on Mac and Windows - the email appears in the Inbox, but
when you click on it, you get an http 404 error - file not found.
There are a number of articles that will help your understanding and help
you correct the problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;326444
All about URLSCAN and what it does, and how to modify it.
http://support.microsoft.com/?kbid=823175
This is also a good article to read as it spells out the issue for Entourage
clients quite clearly.
We have been dealing with an Entourage person at MS (who also lurks here but
I must protect his identity!!!), and he provided the succinct answer. The
relevant snippet from his email follows:
I hope this helps you as much as it helped us. It also fixed the speed
issues it was painfully slow getting mail from the server, and
synchronising, but making this change to the URLSCAN.INI file has sped
things up so much that an email is delivered immediately!
I'd like to also take this opportunity to say a huge thank you to the person
at the Mac BU who persevered, went online to our server using a test account
we set up, researched it thoroughly, tried the same setup on a test server
at MS, came back with a possible solution that worked for him, and
encouraged us to try the same. It took about 7 weeks to find the solution
and prove it beyond reasonable doubt, but finally we have it. It makes a
huge difference to us, and based on some other emails we have had from
others, hopefully it will work for you.
Well, we found the answer to our problems. It has to do with URLSCAN which
is something that is applied when the IIS Lockdown Tool is run - in a
nutshell you can run the IIS Lockdown Tool to shut off potential security
issues on your Windows/Exchange/IIS 2000/2003 server. When our Windows 2000
Server with Exchange 2000 Server was installed in March 2003 our IT
Consultant ran the IIS Lockdown Tool using the default settings recommended
when running an Exchange 2000 server.
The result was it prevented emails with certain characters in the subject
from being delivered to Entourage 2004 clients. One of the articles
mentioned below indicates that this should/could also have impacted on us
when using Entourage X, but we did not find this to be the case. Email only
stopped being delivered when we were using Entourage 2004.
The default URLSCAN.ini file settings also prevents emails being opened in
Outlook Web Access on Mac and Windows - the email appears in the Inbox, but
when you click on it, you get an http 404 error - file not found.
There are a number of articles that will help your understanding and help
you correct the problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;326444
All about URLSCAN and what it does, and how to modify it.
http://support.microsoft.com/?kbid=823175
This is also a good article to read as it spells out the issue for Entourage
clients quite clearly.
We have been dealing with an Entourage person at MS (who also lurks here but
I must protect his identity!!!), and he provided the succinct answer. The
relevant snippet from his email follows:
I hope this helps you as much as it helped us. It also fixed the speed
issues it was painfully slow getting mail from the server, and
synchronising, but making this change to the URLSCAN.INI file has sped
things up so much that an email is delivered immediately!
I'd like to also take this opportunity to say a huge thank you to the person
at the Mac BU who persevered, went online to our server using a test account
we set up, researched it thoroughly, tried the same setup on a test server
at MS, came back with a possible solution that worked for him, and
encouraged us to try the same. It took about 7 weeks to find the solution
and prove it beyond reasonable doubt, but finally we have it. It makes a
huge difference to us, and based on some other emails we have had from
others, hopefully it will work for you.