securityforums
IS-IT--Management
What is the best to achieve good logging when allowing external clients to connect to an exchange 2000 server remotely via pop?
In exchange system manager within the protocols the logging for smtp and http (owa) can simply be set by doing properties on the virtual server and then enabling logging.
This provides good logging for smtp communication and owa including authentication, and the logging is configurable to say what is logged
This option does not appear under the virtual pop server, only timeout, authentication etc.
Obviously this is logged at perimeter firewall level but only gives incoming ip address, not extended information such as username, bytes sent / received etc. etc.
Is there any reason why this option is missing, or can anyone suggest a more granular means of logging on virtual pop servers
thanks
In exchange system manager within the protocols the logging for smtp and http (owa) can simply be set by doing properties on the virtual server and then enabling logging.
This provides good logging for smtp communication and owa including authentication, and the logging is configurable to say what is logged
This option does not appear under the virtual pop server, only timeout, authentication etc.
Obviously this is logged at perimeter firewall level but only gives incoming ip address, not extended information such as username, bytes sent / received etc. etc.
Is there any reason why this option is missing, or can anyone suggest a more granular means of logging on virtual pop servers
thanks
