Outlook 2003 - Problems with "do not deliver before" feature

Hi,

We have recently upgraded from Windows 2000 with MS Office 97 to Windows XP SP2 with MS Office 2003. They are currently on an Exchange 5.5 Server back end.

Previously within Outlook, users could create emails and schedule them for delivery at a time of their choosing, normally when they are not in the office. Since upgrading to MS Office 2003, the email only sends if the user is logged in and has MS Outlook 2003 open at the time the email is scheduled to be sent. This clearly defeats the object of the function and is impractical in our environment.

I've looked reasonably extensively on the web and the best info I have is that this feature is "buggy" with Outlook 2003 due to a change in the way the message is transported from Outlook 97.

Does anyone have a definite answer as to whether there is a tried and tested solution to fixing this, or whether I have to accept the current situation and potentially look at a 3rd party solution or roll back to Outlook 97.

Many thanks.
MikeDGallagherAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David LeeCommented:
Greetings, MikeDGallagher.

See this Microsoft KB article: http://support.microsoft.com/kb/918824
It's a "Catch-22" situation.  If you're running in cached mode, which Microsoft recommends, then this feature doesn't work right.  If running in online mode, which Microsoft does not recommend, then it will work, but you run the risk of having other problems.

Cheers!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MikeDGallagherAuthor Commented:
BlueDevilFan,

I should have mentioned on the first post, as we are still on an Exchange 5.5 back end, the users are not in cached exchange mode but are still experiencing the problem. It is a bit intermittent, but fails far far more than it succeeds.

Any other ideas?

Many thanks again.
0
David LeeCommented:
Actually you did mention that, but it I don't believe it makes any difference.  Cached mode works with 5.5 too, or at least according to what I've read (e.g. http://office.microsoft.com/en-us/assistance/HA011402591033.aspx)
0
MikeDGallagherAuthor Commented:
Thanks,

I'm now looking in the area of, although we are not using Cached Exchanged Mode, whether it is still using OST files and disabling these. If you think of anything else, feel free to let me know.

Thanks a lot.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.