Entourage and Exchange Server 2003

R

Radzi Ibrahim

Hi,

My company just upgraded the mail server to Exchange 2003 and no longer
support POP3 emails. Therefore I've started to try using Exchange in
Entourage but having intermittent problems. I have to remove the server from
entourage and re-define it before could be able to see receive and send
emails. It has been 2 days I been doing this.

Is there anyone who can point out where/what to configure in Entourage
and/or Exchange server?

LDAP works fine though.


Thanks in advance.


Radzi.
 
C

Corentin Cras-Méneur

Radzi Ibrahim said:
Hi,

My company just upgraded the mail server to Exchange 2003 and no longer
support POP3 emails. Therefore I've started to try using Exchange in
Entourage but having intermittent problems. I have to remove the server from
entourage and re-define it before could be able to see receive and send
emails. It has been 2 days I been doing this.
Click to expand...

There might something wrong in the database. Did you try rebuilding it
(press the alt key as you launch the application). I will re-download
all your messages, but it might be worth it.

Corentin
 
F

Frank

I have what I think may be a similar situation. Only my entourage does
send and receive message when I first start it up. Afterwards
Entourage says Exchange 2003 needs needs me to log in again and the
password (my exchange 2003 password) fails. I close out entourage and
restart it and the mail send/receive works initially. The next
send/receive asks for my password again and the loops continue.
 
C

Corentin Cras-Méneur

I have what I think may be a similar situation. Only my entourage does
send and receive message when I first start it up. Afterwards
Entourage says Exchange 2003 needs needs me to log in again and the
password (my exchange 2003 password) fails. I close out entourage and
restart it and the mail send/receive works initially. The next
send/receive asks for my password again and the loops continue.
Click to expand...

I've had that here when the server we have was outdated. They applied various
service releases that MS had made available for Exchange servers and the
problem went away. Any chance it could be the case for you too ?

Corentin
 
Top