When the email doesn't go through
How email travels from your desktop in Brooklyn to your friend's iPad in Toronto or even to your co-worker's laptop, two cubicles away is not something that you probably spend too much time thinking about - unless you happen to be the system administrator or your in-box throws out a 'undeliverable mail' message.
I was wearing the 'sysadmin' hat for this particular company assignment and ended up learning something new while resolving an unusual undeliverable email problem.
......As is usual in these posts, the name of the various parties including the company names have been changed to protect guilty and innocent alike.
Monday Morning Mail Madness
I had come into the office early to finish up documentation on the migration and decomisioning of the last two Windows 2000 domain controllers over the weekend and the completion of this assignment. Stefan, the VP of Sales, knocked on the door and asked if I could give him a hand with a problem that he was having in sending an email. Stefan is a nice guy and actually pretty good with technology so I figured it was probably a real problem. I asked him to give me about 30 minutes to finish up what I was working on and then I would come over to his office.
When I sat down with Stefan it turned out that he was having trouble sending email to a new client JohnnyCEO@bigcmailsrvr.com and that the emails that he had sent out three days before were now being returned to his in-box by the company Exchange server with a non-delivery report (NDR) saying:
Your message did not reach some or all of the intended recipients. Subject: New Order confirmation Sent: 4/29/2010 4:37 PM The following recipient(s) could not be reached: JohnnyCEO on 5/01/2010 8:09 AM This message was rejected due to the current administrative policy by the destination server. Please retry at a later time. If that fails, contact your system administrator.
Determine the scope of the problem: SMTP email test
Back at my desk, I brought up my trusty SMTP email test client [*]
in order to narrow the scope of the problem. If my test client worked then the problem would be within our company system and probably within the Exchange server since my client test would only bypass the Exchange server but not the rest of the infrastructure (like switch, firewalls and ISP).
The SMTP to SMTP (BMAIL.EXE) TEST C:appscomm>bmail -s bigcmailsrvr.com -t JohnnyCEO@bigcmailsrvr.com -f email@example.com -b "test to see if email makes it to you. Reply if you get it please.!" -a " domain to domain email test" -d Command Line SMTP Emailer V1.07 Copyright(C) 2002-2004 Craig.Peacock@beyondlogic.org Opening connection to bigcmailsrvr.com [126.96.36.199] on port 25 Socket Closed
Is it possible that the client company is filtering and rejecting the email from our company, and if so why?
Next post: Did the company land on an email (RBL) block list (again)?