| QUOTE |
The SMTP service in IIS is completely directory based. The SMTP installation creates the following directory structure in the \inetpub\mailroot directory: BADMAIL—This directory stores messages that the SMTP service can't deliver. Look here first when you're debugging problems related to the structural format of the mail messages. DROP—This directory holds all mail for your SMTP service. Each file in this directory represents one email message. Unfortunately, you can't determine the name and address of the sender and receiver from the structure of the filename. PICKUP—As soon as a mail message goes into this directory, the SMTP service picks it up and either delivers it to the Drop directory or sends it to the SMTP service for the destination domain. QUEUE— If the SMTP service can't deliver a message immediately because of a network problem or other connectivity problem, the message queues in the Queue directory. The SMTP service holds the message for a configurable length of time, then tries to retransmit it a configurable number of times. ROUTE, SORTTEMP, and MAILBOX—The SMTP service uses these directories to sort and rearrange outgoing messages so that it can make their delivery more efficient. If several messages are going to the same remote host, IIS tries to send them all by using a single connection instead of transmitting each one individually by reconnecting multiple times. You can use Notepad to create a properly formatted email message, then copy the message to the Pickup directory. As soon as the message is in the Pickup directory, the IIS SMTP service tries to deliver it. Adding this feature to your Web applications makes sending mail as easy as creating a text file and copying it to the \mailroot\pickup directory. To create a file for the \mailroot\pickup directory that the IIS SMTP service will deliver, use this format: x-sender: TimHuck@InterKnowlogy.com x-receiver: WoodyP@InterKnowlogy.com From: TimHuck@InterKnowlogy.com To: WoodyP@InterKnowlogy.com Subject: Test Email This is a test. This is the body of the message. Don't forget to insert a blank line between the header and the message text. |
Just decided to create a workaround for this. But I have no free resources at the moment, so if you urgently need an out of the box solution for your project, you should switch to IIS (Ouch that hurts ...). Maybe you come back later, when my Pickup Manager is available ...
