Just to be sure, disable POP access for your account and see if continues to happen.
Also maybe check mailbox management (although I'm pretty sure it's store based and not
user based).
-Original Message-
From: Don Graham [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 31, 2002 12:35 P
Your RUS is probably configured to use your "first" server which doesn't exists so it
doesn't run. Make sure it's pointing to your "new" server.
-Original Message-
From: Nick Combellack [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 29, 2002 11:54 AM
To: MS-Exchange Admin Issues
Subject:
Is there any events Log warnings. I ran into an issue with one user whose mailbox
wasn't created on the server and I had to create it on another server and move it to
the main one. There were events saying something to the effect of "couldn't create
mailbox" when an attempt to access or send
obert
-Original Message-----
From: Carey, Greg [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 11, 2002 11:29 AM
To: MS-Exchange Admin Issues
Subject: RE: OWA
We ran into that after checkpoint required that we put in an anti-nimda
rule into the firewall (even though the requests were blocked
n Issues
Subject: RE: OWA
Does it pop up with the internal service error as well? Twice?
-Original Message-----
From: Carey, Greg [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 11, 2002 12:29 PM
To: MS-Exchange Admin Issues
Subject: RE: OWA
We ran into that after checkpoint required that we
We ran into that after checkpoint required that we put in an anti-nimda
rule into the firewall (even though the requests were blocked by other
rules). We were having an issue with a cvp server and they wouldn't
even look at it without us having that rule.
Basically OWA uses calls that trigger th
