We have a website hosted on Windows 2008 (SP2), running iis 7.0
One of the pages on our website, when submitted, will send an informational email to info@mywebdomain.com. The email is sent to the localhost smtp server on the same server that the website runs on. This had been working until December 10th and now it always fails.
As best I can tell, it looks like I need to remove mywebdomain.com from the smtp server’s domain block list. However, I cannot figure out how to do that. I got as far as figuring out that the smtp server running under iis 7.0 is actually configured via the iis 6.0 manager. I expanded “local computer”, right-clicked “SMTP Virtual Server #1” (the only one in the list) and selected Properties. I didn’t see anything in any of the tabs which looked like it could be used to unblock a domain.
Any help would be greatly appreciated!!! Details below:
mywebdomain - substituted to keep this posting hopefully anonymous; but this domain is hosted on our server and is available on the internet
mwd3.mwd.local - again substituted for anonymity; but this is effectively localhost
From: postmaster@mwd3.mwd.local
To: webadmin@mywebdomain.com
Date: Mon, 10 Dec 2012 11:29:29 -0600
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="9B095B5ADSN=_01CDCE88DCFE2F9B00000001mwd3.mwd.local"
X-DSNContext: 7ce717b1 - 1196 - 00000002 - 00000000
Message-ID: <f69aZbLAX00000001@mwd3.mwd.local>
Subject: Delivery Status Notification (Failure)
This is a MIME-formatted message.
Portions of this message may be unreadable without a MIME-capable mail program.
--9B095B5ADSN=_01CDCE88DCFE2F9B00000001mwd3.mwd.local
Content-Type: text/plain; charset=unicode-1-1-utf-7
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
info@mywebdomain.com
--9B095B5ADSN=_01CDCE88DCFE2F9B00000001mwd3.mwd.local
Content-Type: message/delivery-status
Reporting-MTA: dns;mwd3.mwd.local
Received-From-MTA: dns;mwd3.mwd.local
Arrival-Date: Mon, 10 Dec 2012 11:29:25 -0600
Final-Recipient: rfc822;info@mywebdomain.com
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;551 Mailhost is on domain's block list (Mode: normal)
--9B095B5ADSN=_01CDCE88DCFE2F9B00000001mwd3.mwd.local
Content-Type: message/rfc822
Received: from mwd3.mwd.local ([127.0.0.1]) by mwd3.mwd.local with Microsoft SMTPSVC(7.0.6002.18222);
Mon, 10 Dec 2012 11:29:25 -0600
From: <webadmin@mywebdomain.com>
To: info@mywebdomain.com
Subject: Consumer Q & A
Date: Mon, 10 Dec 2012 11:29:25 -0600
Message-ID: <20121210-11292530-342c@mwd3.mwd.local>
MIME-Version: 1.0
Return-Path: webadmin@mywebdomain.com
X-OriginalArrivalTime: 10 Dec 2012 17:29:25.0305 (UTC) FILETIME=[E6549290:01CDD6FB]
The following information was submitted at 12/10/2012 11:29:25 AM from Consumer Q&A.
Body of the email
Gregg,
Thanks for your comment. I marked it as adding something useful to the post, since it wasn’t an answer.
It took me a while to figure out how to get an SMTP transcript.
For others reading this post, here is how I did it. Adapt it to your own situation. I was able to stop/start the Virtual SMTP Server because the client gave me permission since it wasn’t accomplishing the purpose it was setup for anyway.
Again, note that IIS 6 is used to administer the SMTP server even when you’re running IIS 7.
I found instructions in the Help menu to enable logging:
I set my logging destination to a new folder just to be sure it wouldn’t get mixed up with other logging.
I turned on every option in the Advanced tab. Then I stopped and started the virtual server.
I sent an email using one of the website features which hadn’t been working (Request Info)
When I tried to view the log, it said it was in use. So I stopped the Virtual SMTP Server, copied the contents of the log, and then started the Virtual SMTP Server again.
Effectively what I discovered is that the client was using mxlogic.net for spam filtering. He regularly contacts them when spam gets through their service. I suspect when he contacted them on December 10th they blocked his address instead of the offending spammer. But that is just speculation.
They acknowledged that his IP address was in a blocked IP range. They fixed it within a few minutes and the problem is now resolved.
You can see below in the transcript that the first OutboundConnectionResponse is initiating a conversation with an mxlogic.net server. The last line is a closing of the transmission channel with the mxlogic.net server. In between you can see a couple of messages stating, “551+Mailhost+is+on+domain’s+block+list”