dburniston
MIS
I have an Exchange 5.0 server that used to have POP3 enabled and working.
I disabled the protocol for the site due to open relay issues. Now I have a Spam Filter that handles the internet mail and sends the good mail to the Exchagne server. It needs POP3 so users can view and release false positives. Since the Exchange server doesn't see the internet now, the relay issue isn't a problem.
I re-enabled the protocol on the server. When I try to connect by telnet or client I get connected to the server, I can enter a username and password, but I get "A required privilege is not held by client" error.
The only reference I can find on the internet say that I need to give the Exchange service account "act as part of the operating system" privileges, but it already has that. I've tried removing the privilege and re-adding it, but I get the same error.
I've checked the services to make sure I have the correct Exchange Service account for Internet Messaging.
Any suggestions how I proceed to get the POP3 working again (upgrading to a newer Exchange server isn't an option!)?
Thanks,
...Dave
I disabled the protocol for the site due to open relay issues. Now I have a Spam Filter that handles the internet mail and sends the good mail to the Exchagne server. It needs POP3 so users can view and release false positives. Since the Exchange server doesn't see the internet now, the relay issue isn't a problem.
I re-enabled the protocol on the server. When I try to connect by telnet or client I get connected to the server, I can enter a username and password, but I get "A required privilege is not held by client" error.
The only reference I can find on the internet say that I need to give the Exchange service account "act as part of the operating system" privileges, but it already has that. I've tried removing the privilege and re-adding it, but I get the same error.
I've checked the services to make sure I have the correct Exchange Service account for Internet Messaging.
Any suggestions how I proceed to get the POP3 working again (upgrading to a newer Exchange server isn't an option!)?
Thanks,
...Dave