Installation

How Queueing Works in DevMailer
Messages that DevMailer is unable to send are preserved in the queue directory if your configuration has a valid queue directory. Refer to the QueueDirectory property for more information on this procedure. If you do not specify one, queuing defaults to C:\TEMP.

If the message does not contain any errors, but the mail server refuses the message or DevMailer is not able to connect to the mail server, the message is saved in the queue directory with extension .QDM.

DevMailer will automatically attempt to flush any queued messages once a successful connection to a mail server is established. Or you may refer to to the FlushQueue() method to force the aforementioned.

Message file format: *.QDM

The top of the queued file contains a message header generated by DevMailer that contains information about the sender, recipient(s), subject, and other fields. This information may have originally come from the message header in the original input file, from parameters specified on the command-line, or from defaults specified in the configuration functions in DevMailer. In most cases, the message header is generated from a combination of all these.

In general, unless there was an error in the message header itself, each generated header file will have at least the following four fields:


To: recipient@somedomain.com
From: support@geocel.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

There will likely be other optional fields, such as ‘Subject:’, 'CC:', and ‘BCC:’ also present in the generated file, as well as header fields that are ignored by DevMailer but were present in the original input file’s message header.

All standard SMTP headers may be used and will function according to the SMTP standards dictated in RFC #822.

The only non-standard header recognized by DevMailer (and handled internally) is 'ATTACH: filename.ext'. Any queued messages with file attachments will include this in the header text. Note that attachments in DevMailer are unlimited, and each attachment will be listed line by line.

Note that these headers need not be in any particular order.

The next section of the of queued file is the message body (text) itself. This is seperated by a blank line between the message header and the message body. The following is a simple example:

 
To: recipient@somedomain.com
From: support@geocel.com
CC: archive@somedomain.com
Subject: Test Message
ATTACH: D:\DIRECTORY\FILE.TXT

This is a the body of the message.

How Logging Works in DevMailer
DevMailer is equipped with advanced logging abilities. This will allow you to diagnose any SMTP problems, as well as any DevMailer usage problems.

DevMailer supports 5 different logging levels. Setting the property LogLevel = 0 will disable it totally. Setting LogLevel = 1 will log any error related messages. In contract, LogLevel = 4 provides an exhaustive log of everything DevMailer does. DevMailer documents every step it takes, and makes a note of server responses to each step.

If a Fatal error occurs, DevMailer writes to the LogFile using the current settings. Additionally, DevMailer writes to the NT Event Log. Sorry, but since Windows95 and Windows98 do not have an Event Log, this feature cannot be supported on these platforms.

Sample Log File:

 
[355] DevMailer v1.0b engine started on Thursday, April 29, 1999 21:50:31.
[355] DevMailer v1.0b for WIN32 (95/98/NT) (211 evaluation uses left)
[355] Visit http://www.geocel.com/ for registration information
[355] Connected to mailhost.geocel.com...
[355] Message successfully sent to mail server.
[355] DevMailer v1.0b engine shuting down.

Sample Verbose Log File:

 
[585] DevMailer v1.0 engine started on Monday, May 03, 1999 00:41:00.
[585] DevMailer v1.0 for WIN32 (95/98/NT) (209 evaluation uses left)
[585] Visit http://www.geocel.com/ for registration information
[585] Attempting connection to mailhost.geocel.com [25]
[585] Connected to mailhost.geocel.com...
[585] SERVER:
220 lithium.geocel.com ESMTP Sendmail 8.8.8/8.8.8; Mon, 3 May 1999 00:40:39 -0500 (CDT)


[585] CLIENT:
HELO smeg


[585] SERVER:
250 lithium.geocel.com Hello xx.xx.com [208.24.xx.xx] (may be forged), pleased to meet you


[585] CLIENT:
MAIL FROM:


[585] SERVER:
250 ... Sender ok


[585] CLIENT:
RCPT TO:


[585] Error receiving RCPT response: 22
[585] Error adding TO recipient: rrrrr@geocel.com
[585] CLIENT:
RCPT TO:


[585] SERVER:
250 ... Recipient ok


[585] BCC: benc@geocel.com
[585] CLIENT:
DATA


[585] SERVER:
354 Enter mail, end with "." on a line by itself


[585] CLIENT:
X-Mailer: DevMailer v1.0 (http://www.geocel.com/dm/) (DEMO)

Date: Mon, 03 May 1999 00:41:01 Central Daylight Time

From: DevMailer Example 

To: Doomed 

Subject: DevMailer Demonstration

MIME-Version: 1.0

Content-type: multipart/mixed; boundary="#DM1187299376#"




[585] CLIENT:


--#DM1187299376#

Content-Type: text/plain; charset=us-ascii

Content-Transfer-Encoding: quoted-printable




[585] CLIENT: Message body suppressed.
[585] CLIENT:


--#DM1187299376#--
[585] CLIENT:


.


[585] SERVER:
250 AAA05917 Message accepted for delivery