Entourage 2008 not connected till i send a new email

[bricktop44]

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: Exchange

I have a user who's email account is on exchange 2003, using entourage 2008. Whenever i close the entourage client...or log in during the morning the account will be "not connected" until i send a new email. It will not connect under any other circumstances. OWA log in works, and im positive that the exchange settings are correct. I have tried a new identity as well as setting the account up on a totally separate machine, same result. The funny thing is that the sync status bar (the blue and white barber pole at the bottom right) seems to be busy moving mail to sub folders, but still it says not connected until i send an email. The connection is fine for the rest of the day (as long as entourage is not closed out), this just happens in the morning at first log in.

any ideas??? its making me crazy.

Thanks,

brick

 

[William Smith [MVP]]

I have a user who's email account is on exchange 2003, using
entourage 2008. Whenever i close the entourage client...or log in
during the morning the account will be "not connected" until i send a
new email. It will not connect under any other circumstances. OWA log
in works, and im positive that the exchange settings are correct. I
have tried a new identity as well as setting the account up on a
totally separate machine, same result. The funny thing is that the
sync status bar (the blue and white barber pole at the bottom right)
seems to be busy moving mail to sub folders, but still it says not
connected until i send an email. The connection is fine for the rest
of the day (as long as entourage is not closed out), this just
happens in the morning at first log in.

Is your user possibly setting Entourage to Work Offline? Check under the
Entourage menu.

Hope this helps!

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[bricktop44]

yea, looked at that for sure. not the case here. Thanks though!

 

[bricktop44]

Ok i dont know why, but using our OWA address instead of the exchange server FQDN and this solved the issue. Is this common to use an OWA address i wonder?