Sent folder doesn't synch

M

mrspeakers

If I send email from the Outlook web client, it synchs in my Entourage
Sent folder. However, if I send from Entourage, I have to empty my
cache to get the Sent folder to Sync. It's a real problem, as I have
constant need for Sent folder access.

This is the opposite of the Active Synch issue MSFT acknowledges. Any
know a fix? I'm using 11.3.4 on a MacBook Pro, 10.4.9.

Dan
 
W

William Smith

If I send email from the Outlook web client, it synchs in my Entourage
Sent folder. However, if I send from Entourage, I have to empty my
cache to get the Sent folder to Sync. It's a real problem, as I have
constant need for Sent folder access.

This is the opposite of the Active Synch issue MSFT acknowledges. Any
know a fix? I'm using 11.3.4 on a MacBook Pro, 10.4.9.
Click to expand...

Hi Dan!

If you're using your company's Outlook Web Access (OWA) address as your
Exchange Server address then verify with your Exchange administrator
that he has the latest updates and patches applied. I faced a similar
issue where Entourage would not sync sent items or any items created in
Entourage. I believe this was fixed with an update but I don't know for
sure.

If your Exchange Server is within your company's network then I suggest
using an internal server name of a backend server rather than the OWA
address.

Hope this helps! bill
 
W

William Smith

William,

Our server is interenal, and the OWA URL is simply https://owa.servername.com

Is that what you are refering to?
Click to expand...

Typically, the OWA address is an external address shared to the
Internet. An internal name is accessible only within a company network.

If you use an external address internally then you're essentially
leaving your company network to go to the Internet and then coming back
into your company network to get your mail. That can be a few extra
hops compared to connecting directly to a backend server.

Hope this helps! bill
 
M

mrspeakers

Typically, the OWA address is an external address shared to the
Internet. An internal name is accessible only within a company network.

If you use an external address internally then you're essentially
leaving your company network to go to the Internet and then coming back
into your company network to get your mail. That can be a few extra
hops compared to connecting directly to a backend server.

Hope this helps! bill
Click to expand...

Yes, this is it. So I didn't have to use VPN, I had switched from our
server name to our external email interface. That's what breaks it.
Wish MSFT would fix this, it's not great to have to choose between
slow access over VPN and regularly emptying the cache and doing a
refresh on Sent.
 
W

William Smith

Yes, this is it. So I didn't have to use VPN, I had switched from our
server name to our external email interface. That's what breaks it.
Wish MSFT would fix this, it's not great to have to choose between
slow access over VPN and regularly emptying the cache and doing a
refresh on Sent.
Click to expand...

You might also try creating a second identity. Use one internally and
the other externally. You'll still have to synchronize but only messages
that have changed that day.

Hope this helps! bill
 
Top