Released: Aug 18, 2021

10.0.1282.1986 での更新項目

機能

• Added assemblies for Microsoft .NET 6.0 Preview 7 to the base installation. To build applications using .NET 6.0 you will need install the Microsoft Visual Studio 2022 Preview.
• Added support for several more Microsoft Windows code page character sets and updated the parser to internally convert them into Unicode. This affects both the contents of message and encoded header values which used these code pages. This change was made to improve messages imported from older mail clients. Windows code pages should not be used when composing new messages.
• Created new installers and Windows Installer (MSI) packages which no longer use InstallShield. The new installers provide an improved installation experience and provide support for silent installation and a streamlined update process.
• Examples have been added for the Visual Studio 2022 Preview and Library Edition examples have been updated to use the v143 toolset. Note some examples use Microsoft Foundation Classes (MFC) which should be installed for the current toolset.
• Minor updates to the HTML Help documentation and a README.md file has been included which provides information about the installer.

不具合の修正

• Corrected an issue where the InternetMail component would not disconnect correctly from an IMAP server under some circumstances.
• Corrected an issue where the GetText method or HttpGetText function in the HTTP client components and library would not return an error if an invalid resource was specified.
• If the HttpClient Connect method or HttpConnect function is called using an HTTPS URL instead of a hostname, and the default port number is specified, it will automatically switch to using a secure port (443) instead of returning an error.
• The HTTP server components and libraries will no longer override custom values for the Cache-Control, Content-Type and Server response headers. This will enable the application to provide its own values unique to that client session. A default Pragma response header will only be used with HTTP/1.0 client sessions.
• Corrected an issue where setting the Passive property to false in the FtpClient component would not force the client to use active mode file transfers.
• Corrected an issue where the value of the ActivePorts property in the FileTransfer .NET class would be ignored when establishing a new FTP connection and revert to using the default port range.
• The ComposeMessage method in the InternetMail and MailMessage component, and the MimeComposeMessage function in the MIME library will use Unicode (UTF-8) instead of the ISO 8859-1 character set with HTML formatted text.
• Corrected an issue where the ComposeMessage method in the InternetMail and MailMessage .NET components could fail with an error indicating invalid encoding was used. An additional check is made to ensure the correct encoding is always selected with the default UTF-8 character set.
• Corrected an issue when composing a new message with HTML text using the ComposeMessage method or the MimeComposeMessage function where the HTML contents would not be encoded even though the Content-Transfer-Encoding header would specify quoted-printable encoding. This could cause mail clients to display the HTML contents incorrectly.
• Corrected an issue where the Attachment property of the InternetMail and MailMessage components, and the MimeGetAttachedFileName function, could return "Unknown" as the file name even though a valid file name has been specified for the attachment.
• Corrected an issue where the AttachData method for the InternetMail and MailMessage components, and the MimeAttachData function, would return an error indicating a message header was invalid, although the same data could be written to a file and attached to the message using the AttachFile method.
• The MIME parser will defer decoding quoted-printable or base64 encoded text until the application requests the contents of the encoded text, rather than always decoding the text as the message is being parsed. This optimization should improve performance when importing large messages.
• Corrected an issue with the SocketWrench .NET class which could cause a unmanaged memory leak when a large number of class instances were created.
• Corrected an issue with all components and libraries which could prevent the process heap from being destroyed if the Uninitialize method or function was explicitly called by the application. This could result in memory fragmentation and a potential memory leak if the component was repeatedly initialized and uninitialized.
• If you have previously installed SocketTools with a serial number, installing an update will no longer require you to re-enter your serial number under some circumstances.
• Launching the License Manager utility directly from the default installation folder, rather than using the shortcut, will automatically detect the correct SocketTools edition rather than selecting another edition which was previously installed with an evaluation license.
• Uninstalling SocketTools will no longer display error messages about being unable to unregister or remove 64-bit ActiveX components.
• Updated the licensing for all ActiveX controls to resolve an issue where using CreateObject could fail if the application or script references the control on a system which does not have a development license installed.