ASP Mail Component

• Updated to include improvements in the Chilkat common underlying architecture.

9-JUL-2003

Fixed:

• The Body property, and the methods to get the plain-text body from multipart/report emails now work properly.

Modified:

• IMPORTANT An extra argument (HtmlEncode) was added to both the GetMbPlainTextBody and GetMbHeaderField methods. This argument controls whether the returned data is HTML encoded or not.

Added:

• HasHtmlBody method returns 1 if the email has an HTML body, and 0 if it does not.
• HasPlainTextBody method returns 1 if the email has a plain-text body, and 0 if it does not.
• IsMultipartReport returns 1 if the email is a multipart/report, which is the content-type for bounced email notifications. Chilkat will soon release a new product for handling bounced emails.

3-JUL-2003

Added:

• Added the ErrorLogHtml property to each object to allow the error information to be easily displayed on an HTML page.

27-JUN-2003

Fixed:

• When attachments are added, files are opened for file sharing as opposed to exclusive access.

Added:

• SendMime method for sending pre-constructed MIME emails intact.

18-JUN-2003

Fixed problems with sending Czech email.

13-JUN-2003

Added:

• SetCSP method.
• SetSigningCert method
• SetEncryptCert method

Fixed:

• SetHtmlBody
• Attachment filenames with non us-acsii names handled correctly.

2-JUN-2003

Added:

• GetAttachmentSize method.

28-MAY-2003

Fixed:

• The SetAttachmentFilename method broke in the v5.0.0 release, and has been fixed.
• On some email clients, HTML emails having file attachments did not display perfectly. This only occured when adding related images, body parts, and file attachments in certain orders. (Chilkat Mail relieves you from the burden of manually structuring y our multipart MIME message and does all the work so you don't have to be a MIME expert.)

22-MAY-2003

Fixed:

• If a hash algorithm for signing is not explicitly specified, and this is usually the case, Chilkat was by default selecting the 1st hash algorithm returned by the Cryptographic Service Provider. Instead, it first looks for SHA-1, then MD2, then MD5, ... and when it runs out of well-known algorithms, it will simply choose the first one offered by the CSP. This will ensure that your signed emails use the same hash algorithm if one is not explicitly set via the ChilkatCSP object.
• Similar to Outlook, Chilkat includes any intermediate certificates in the certificate chain to the root authority (except the root itself). It was possible for Chilkat to choose expired certs before, but not anymore.
• If the FromName property is set *after* the FromAddr property, it was getting ignored. This is now fixed.

21-MAY-2003

Fixed:

• The v5.0.0 version caused AddFileAttachment to break in some instances and on some systems such that the file was attached but empty. This only occured on some Win98 and WinME systems. It is now fixed.
• The Message-ID header field is now regenerated during a send. With some SMTP servers, when the same email object is reused, the fact that multiple messages had the same ID caused mail non-delivery problems. This problem did not occur when separate email objects were used because each email object had its own unique message-id.

9-MAY-2003

Added a ConnectTimeout property to ChilkatMailMan. The default ConnectTimeout is 5 seconds.

25-APR-2003

Added the intelligence to automatically handle non-usascii characters passed to the following methods/properties without first calling QEncodeString or BEncodeString.

• AddCC
• AddTo
• AddDataAttachment
• AddFileAttachment
• AddFileAttachment2
• Body
• From
• FromName
• ReplyTo
• Subject

The preferred way of passing a string with non-usascii characters is to use QEncodeString like this:

email.Body = QEncodeString("string with non-ascii chars","charset_name")

(Where charset_name is something like shift-jis, iso-8859-1, big5, etc.)

In this version (5.0.4) Chilkat Mail will automatically detect non-usascii input and automatically Q-encode it to utf-8. If the non-usascii characters entirely fall within the bounds of iso-8859-1, then iso-8859-1 is used instead of utf-8.

For example, this code will automatically Q-encode the subject to iso-8859-1.

email.Subject = "Here are some accented chars - ŕ é"

14-APR-2003

Minor fixes:

• AddTo did not work correctly if the first argument was a zero-length string.
• Better parsing of dates in email headers, especially if a malformed date string is encountered.

7-APR-2003

Fixed minor memory leaks.

1-APR-2003

Major upgrade that vastly improves international email capabilities. Version 5.0.0 additions are clearly marked in the documentation pages:

• WebMailMan
• WebEmail
• WebBundle

Also fixed with this version:

• Email Date property returned the wrong times.
• Saving emails to XML is improved such that safeguards are now in place to prevent binary data from creeping into XML files.

6-MAR-2003

Added:

7-FEB-2003

Changes:

• Certificates for intermediate certification authorities are now included in the detached signature that is created when sending signed email. This allows the recipient (receiving email client) to reconstruct the chain-of-trust to the root CA, especially if those intermediate certificates are not already installed on the recipient's computer. Note that the root CA certificate is never included in the signature.

3-FEB-2003

Fixes:

• Methods such as CopyMail, GetAllHeaders, etc. will now work with older POP3 servers that do not support the UIDL command.
• The BCC list is now saved to XML in the SaveXml method. When loading XML, the BCC list is restored.

New Methods / Properties:

The following new methods allow attachments and HTML-related images and other items to be attached directly from memory, as opposed to having a file source.

• WebEmail.AddDataAttachment - Add an attachment directly from a memory buffer.
• WebEmail.AddRelatedData - Add an HTML-related item directly from a memory buffer.

The following property and method allow access to emails that are attached to an email. (These are "message/rfc822" content-type subparts.) One way of generating such an email is to forward an email "as an attachment" from an email client such as Yahoo! Mail online.

• WebEmail.NumAttachedMessages - The number of attached email messages.
• WebEmail.GetAttachedMessage(index) - Returns a ChilkatEmail object representing the attached mail message.

31-JAN-2003

The MailMan.SendQ method accessed the registry in read/write mode to determine the queue directory, and this has been changed to access it in read-only mode.

29-JAN-2003

Fixed a problem that can sometimes occur (infrequently) when B-encoding email header fields.

21-JAN-2003

Updated to keep versions in sync with Chilkat Mail.

7-JAN-2003

Added methods to assist in using multibyte character encodings such as utf-8, shift-JIS, euc-kr, iso-2022-jp, big5, gb2312, etc. These methods allow you to set email body and header fields without ever needing to convert to Unicode. Here is a summary:

(Property)
MbPlainTextBody As Variant read/write

This property allows the email body (or plain-text body in a multipart/alternative email) to be accessed or set directly from multibyte (non-Unicode) character data.

(Property)
MbHtmlBody As Variant read/write

This property allows the email HTML body to be accessed or set directly from multibyte (non-Unicode) character data.

(Method)
MbEncode (mbString As Variant, charset As String) As String

Encodes a multibyte string using "Q" or "B" encoding such that the returned Unicode string can be used to set any of the email's header fields, such as the Subject.

Click HERE for an example showing how to pass utf-8 data from an HTML form to an ASP page that sends the utf-8 form data in an email.

16-DEC-2002

• Added the SendQ method for sending emails through the Chilkat smtpQ service.

12-DEC-2002

• Updated to keep versions in sync with Chilkat Mail.

7-DEC-2002

• Updated to accept "Lite" unlock codes to unlock basic functionality.

3-DEC-2002

• Fixed a problem with using replacement patterns in HTML email.

2-DEC-2002

• Fixed a problem with the DropAttachments method where images in HTML emails were being dropped as well.
• Fixed a problem with adding attachments to HTML emails. This problem caused the email to not display properly in some email clients. Specifically, Yahoo Mail, Hotmail, and other online mail Web interfaces. Chilkat Mail now properly constructs the email such that file attachments are properly recognized as such, and HTML related image and style sheet "attachments" are recognized as part of the HTML body proper.

18-NOV-2002

• Fixed version reporting problem.

11-NOV-2002

• Added the ReadTimeout property: the maximum number of seconds to wait for new data to arrive from the POP3 server. A value of 0 (the default) sets the timeout to infinity. Setting a reasonable timeout value will prevent your application from hanging if the POP3 server stops responding.

8-NOV-2002

• Overwhelming popular adoption of Chilkat WebMail has created email communications and support burdens that force us to charge a small amount for using this previously free component. Our intent is to keep the price as low as possible. Current users can continue to use version 3.2.4, but must purchase a license to upgrade to 4.0.0 and beyond.

18-OCT-2002

• Updated because of improvements in the shared underlying Chilkat common architecture relating to improved error reporting in some situations.

11-OCT-2002

• Updated because of charset conversion fixes in the underlying Chilkat common architecture.

9-OCT-2002

• AddRelatedContent did not recognize uppercase file extensions for the purpose of setting MIME content types.

28-SEP-2002

• Updated because of XML fixes in the underlying Chilkat common architecture. (See http://www.chilkatsoft.com/ChilkatXmlRef.asp)

23-SEP-2002

• The Chilkat Charset component is no longer needed for character conversions. Chilkat Mail will do the conversions without any external help.
• Additional information is now added to the error log when reporting NTLM authentication failures.

18-SEP-2002

• The "Received" header field is no longer parsed. The only effect is that when an email is saved as XML, the attribute/value name pairs will not be present, and the entire content will appear between <received> and </received> tags

10-SEP-2002

Fixes:

• Q-Encoding vs. B-Encoding for non-ascii emails: Japanese and other non-western languages will use B-Encoding for header fields rather than Q-Encoding. Western languages still use Q-Encoding.
• The "Received" header fields were not properly re-saved and re-loaded to XML. This has been fixed.
• Calling AddPlainTextAlternativeBody after an HTML body was already present caused the HTML body to not be encoded as quoted-printable. This has been fixed -- the email will be properly constructed regardless of the order of method calls.
• Filters did not work for the email body. This has been fixed.
• iso-2022-jp charsets should now work correctly.

28-AUG-2002

Fixes:

• SetCSP now works for emails that are both signed AND encrypted.
• Problems regarding SetReplacePattern in HTML emails have been resolved.
• DeleteBundle became broken in version 2.9.6, and is now fixed.

26-AUG-2002

Fixes:

• 128-bit RC2 and 3DES algorithms will now work when using other Cryptographic Service Providers via the SetCSP method.
• The X-UIDL field is assured of being present in all emails or headers downloaded from POP3 servers.
• SendEmail returned 1 (total success) in cases where bad emails existed. It now returns 0 as it should.

22-AUG-2002

Version 2.9.6 introduced a problem where the POP3 connection was not closed. This was an intentional feature provided in the caching mechanism -- to try to keep a POP3 connection alive between calls, but apparently it caused problems with some POP3 servers (not all of them). Until this is fully understood, the POP3 connection is closed and re-opened with each method call -- thus backing-out this optimization that was introduced in v2.9.6.

20-AUG-2002

Updated to include fixes that are common with Chilkat Mail. Chilkat WebMail is built on the same engine, but the COM housing is different and specialized for ASP. The version numbers of Web Mail and Chilkat Mail will be kept almost in sync to reflect this.

8-JULY-2002

Initial version adapted from Chilkat Mail v2.9.2