I was working with a co-worker the other day trying to see what our emails looked like when they were sent from a webpage. We had some formatting issues and wanted to see the actual message on the server right after it was generated. The problem, we couldn't capture it fast enough on the server.
I realized one small trick, turn just the SMTP service off that comes with IIS. Messages queue up in the local pickup folder. After you turn the service on, the messages are delivered as normal. This works both for troubleshooting webpages generated with classic asp, asp.net or a 3rd party script. Here is an example of what I did.
An update. I double checked this and ran into some workarounds in regards to .NET testing.
A few assumptions
1) This will fail if you have your SMTP Serivce not configured to accept email locally. You'll get a 'refused message'.
2) The code needs to run on the same server
3) For .NET 1.1 and 2.0 websites, you are using the System.Web.Mail (1.1 namespace) code sample. I could not get a webpage with System.Net.Mail namespace to work.
Stop the service.
Generate a message
Look in the pickup folder
Poof! The message is still there. Your webpage will still work. I get a lot of questions in the newsgroups asking where are my messages or what do my messages look like. You can review the email headers in Notepad while it remains in the pickup folder. If you have several messages in the folder, just use the Search feature to look inside files for your message.
Here are the headers from the sample email.
X-Receiver: [email protected]
X-Sender: [email protected]
Thread-Topic: Sending email with CDO
From: <[email protected]>
To: <[email protected]>
Subject: Sending email with CDO
Date: Fri, 6 Apr 2023 05:17:10 -0400
Message-ID: <[email protected]>
X-Mailer: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
This is a message.
Here is the ASP code used to generate the message.
response.write "Email was sent at " & Now()
Hope that helps in your SMTP troubleshooting.