No New Mail Sound

[@home]

HI
I have Entourage 2008 installed on Leopard & while everything was ok with Entourage 2004....I am having a few issues with the 2008 as follows...

No new mail sound notification. Yet When I receive junk mail I get a notification sound..

When entourage has been left open the 'sent mail' sound notification no longer works

Has anyone else had these problems? If so how did you fix them.

Apart from these little annoyances, I'm loving the new Office 2008 for Mac

Cheers & have Fun

 

[Steve]

I'm in the same situation. No sound and when you go into the preferences section, you can't any changes to the sound portion of notification.

 

[Darren Wright]

When i open entourage i get the welcome sound, I then go to check my email I get the no new messages sound then i get no more sounds until i quit the app and start again. (Macbook Pro OS X 10.5.1) (works fine if i put 2004 back on) (using the standard microsoft sound set)

- I have check this on my mac pro running 10.4.11 and this seems ok
- Created a new user SAME PROBLEM?
- completely deleted all traces of office 2004 and 2008, preferences, fonts etc. SAME PROBLEM?

 

[Scott Willens]

I too have no notification sounds.

Any ideas what to do?

 

[Michael Jardine]

Same. I¹m getting a sound for Junk Mail only. My advice is to sit tight and
wait for the update. Otherwise if you must have sound, go back to Entourage
2004. Personally, I have switched to having the Entourage icon bounce in my
dock. That¹s enough for me.

 

[Guest]

Well it's no consolation I know but at least I'm not alone.

Have you guys been in touch with Microsoft about these problems?

I have via this site.

Hope they don't take forever to fix it.

Cheers

 

[Radio_Bill]

I have the same problem.

 

[Mark]

Has anyone had any feed back from Microsoft about when there gonna bring out an update for Office 2008 to address the bugs like the no sound on receipt of new mail?

Cheers

 

[Bocaboy]

I have the same problem. If you search this forum you'll see that MS
acknowledges this as a known problem and that it will be fixed in a
future update. Can you believe that something like this wasn't caught
in beta, especially after delaying the release for four months in
order to "get everything right.