An administrator has a corrupt SMTP Virtual service. He has have moved all of the queued messages to an alternative location, but when he restarts the SMTP Virtual server, it reports 400 odd messages in the pre-processing queue and hogs the system resources. He has now disabled the default SMTP service and created a new one. The new SMTP Virtual Service is now processing all of the company’s mail without any issues.
The question is how can he now move the previously unsuccessful messages into the drop queue for the working SMTP virtual services. How can hetrack the possibility that one of the messages may be corrupt and stuffs up the new SMTP virtual service?
regards
trmbr
The question is how can he now move the previously unsuccessful messages into the drop queue for the working SMTP virtual services. How can hetrack the possibility that one of the messages may be corrupt and stuffs up the new SMTP virtual service?
regards
trmbr