GWClient utility is in the BackOffice Resource Kit, Second Edition on the TechNet September 1999 CD-ROM (According to Q250051) Ricki -----Ursprüngliche Nachricht----- Von: Hotchkiss, Peter [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 17. August 2001 14:55 An: MS-Exchange Admin Issues Betreff: RE: .Exchange IS and IMC stop 10x a day Maybe off base here. There is a tool called gwclient that allows you to get into the "bad" folder and the queues to remove offending messages. I think it is in the support directory of the Exchange cd. It's been a couple of years since I used it with assistance from MS Support. Pete Hotchkiss -----Original Message----- From: Matthew Western [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 16, 2001 9:59 PM To: MS-Exchange Admin Issues Subject: RE: .Exchange IS and IMC stop 10x a day typical microsnot.... they all do things differently. what we did was indeed deleting the IMC and recreating it... well not quite, but restarting the IMC with all the files renamed fixed the problem... my question is, where can i get this tool that logs into the IMC mailbox and removes the message? how can one hope that it won't happen again? last question. when will someone write program that sends mis formed messages to exchange servers and thus crashes the server??? dorks.... anybody want to mail me that IMC tool referred here, pls? thanks [EMAIL PROTECTED] M -----Original Message----- From: Don Ely [mailto:[EMAIL PROTECTED]] Sent: Friday, 17 August 2001 9:27 AM To: MS-Exchange Admin Issues Subject: RE: .Exchange IS and IMC stop 10x a day It's not that someone has figured out how to send misformatted messages so much as sometimes messages just get malformed mail headers that in turn wind up crashing the IS. The fix PSS gave you is a strange one though. I can't remember (GAWD, I HATE IT WHEN I CAN'T REMEMBER THINGS) the tools they gave me to fix the problem off hand, but the fix they gave you doesn't sound right. Their utilities they gave me actually allowed me to login to the IMC like a mailbox and remove the offending message, restart the IS and IMC and all was well. Took about 5 minutes to fix the problem. With the fix you got, you might was well have deleted and recreated the IMC... List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm CONFIDENTIALITY NOTICE: This electronic mail transmission is intended only for the use of the individual or entity to which it is addressed and may contain confidential information belonging to the sender which is protected by the attorney-client privilege. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this transmission in error, please notify the sender immediately by e-mail and delete the original message. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
