Exchange is retarded
I'm writing a mail-filtering script in perl and while testing just sending all e-mail to myself. Made a typo and exchange - which is our *main* mail server, sadly - returned this error..
did not reach the following recipient(s):
c=US;a= ;p=TIXX;o=SYRACUSE;dda:SMTP=krapszo@tickets.com; on Tue, 9 Dec 2003
13:42:31 -0800
The recipient name is not recognized
The MTS-ID of the original message is: c=us;a=
;p=tixx;l=SYRS-MAIL0312092142YSQZTSW0
MSEXCH:IMS:TIXX:SYRACUSE:SYRS-MAIL 0 (000C05A6) Unknown Recipient
My first thought at seeing this mess was "Good lord, what the hell is my script doing to the headers (I am modifying them)!
Took a second eye to notice that I misspelled my own bloody name and this is exchange's way of saying "Unknown Recipient". If you squint real hard you'll notice that message at the end of the pile of cryptic, useless (to me) information.
That is just hideous and disgusting.
Comments
"Exhange is retarded"
Why, yes. Yes it is. Glad you finally noticed. :-)
Posted by: Jeremy Zawodny | December 9, 2003 07:40 PM
Somebody said I would believe it when I saw it, and seeing from that... (...)
Jeremy says it all as always.
Posted by: david | December 9, 2003 11:00 PM
While generally I would agree, that error message is actually very helpful if something other than a typo occurs. It gives you all the information that a sysadmin needs to know to find out which server and part of the Exchange configuration was responsible for the error.
Of course, it's pretty much impossible for anyone else to understand...
Posted by: Ryan Gregg | December 10, 2003 01:45 AM
Hmmm... that would only be a win if it was much more likely that something went wrong internally with exchange than if a user were to make a typo.
hmm...
Posted by: Matt | December 10, 2003 01:51 PM
[E]mail
[X]tra
[C]rap
[H]aving
[A]mbiguous
[N]asty
[G]ruesome
[E]rrors
Posted by: Brian | December 10, 2003 03:49 PM
And my magic 8 ball said "Outlook not so good". Damn it's good.
Sorry, got nuttin' today :)
Posted by: Arcterex | December 11, 2003 12:33 PM
I've also noticed that sending a message with a duplicate message id to an exchange server tends to get lost in exchange. Most frustrating when testing!
Posted by: Jeff Macdonald | December 12, 2003 03:50 PM