Ok, here's a new one.
I have a customer that was running their own web server. They did a server upgrade recently and accidentally left their SMTP relay wide open by not reconnecting their server through their firewall.
They've fixed the problem but are now stuck with so many files in their inetpub/mailroot/queue and inetpub/mailroot/badmail folders that explorer literally hangs when you browse to those directories. They want to clear those directories out before they restart the SMTP service.
I've got remote desktop access to their server and I've tried deleting the files via a command prompt and using the "del" command. It's been running for about an hour without finishing.
I've got no idea how many files are in the directories but it's a lot. I tried a dir command and let it run for several minutes before killing the command with a ^X.
I'm wondering if anyone has any ideas for clearing out these directories? Remember that they are on my client's production web server. I can't really install anything on it. BTW, it's running Windows Server 2003.
Any suggestions?
I have a customer that was running their own web server. They did a server upgrade recently and accidentally left their SMTP relay wide open by not reconnecting their server through their firewall.
They've fixed the problem but are now stuck with so many files in their inetpub/mailroot/queue and inetpub/mailroot/badmail folders that explorer literally hangs when you browse to those directories. They want to clear those directories out before they restart the SMTP service.
I've got remote desktop access to their server and I've tried deleting the files via a command prompt and using the "del" command. It's been running for about an hour without finishing.
I've got no idea how many files are in the directories but it's a lot. I tried a dir command and let it run for several minutes before killing the command with a ^X.
I'm wondering if anyone has any ideas for clearing out these directories? Remember that they are on my client's production web server. I can't really install anything on it. BTW, it's running Windows Server 2003.
Any suggestions?
Comment