Send, receive, edit, sign/verify and encrypt/decrypt email messages in any .NET application or service. 
Product Release History
The following is a list of public releases for all components shipped with PowerTCP Mail for .NET (Latest Release 2018-09-24)
PowerTCP Mail for .NET
Current Version:    Released: 2018-09-24
  • Various improvements made in handling malformed mail messages and message headers.    Released: 2018-08-02
Product fixes in this release:
  • An issue where RFC822 parts may not be decoded correctly when their encoding type is Quoted-Printable has been fixed.  (1049)    Released: 2018-04-04
  • Added support for .NET Standard 2.0 and .NET Core 2.0
  • New .NET Core 2.0 sample projects, referencing the Dart.Mail.Standard dll
  • Updated trial license operation for use on .NET Standard-compatible platforms
    • Details regarding trial operation for Dart.Mail.Standard.dll can be found in the Licensing and Trial Operation topic in the included help documentation
Product fixes in this release:
  • Resolved an issue where some attachment filenames were not properly decoded.  (1025)
  • Resolved an issue where the component would use the systems native end of line sequence instead of CRLF.  (1026)
  • Resolved an issue where in line links to web resources in HTML emails could cause an exception be thrown if the URL began with capital letters, ex: HTTP instead of http.  (1035)    Released: 2017-03-08
  • Visual Studio 2017 compatibility.    Released: 2017-02-01
Product fixes in this release:
  • An issue where spaces were incorrectly removed when only a portion of header text was Q-encoded was resolved.  (958)
  • An issue where attachments names were not parsed out correctly when the attachment part headers contained both a name and filename parameter has been resolved.  (964)
  • Some servers do not support the reciept of the EHLO command after authentication. EHLO will no longer be sent after authentication has occurred.  (983)
  • An issue where FETCH responses containing parentheses within quoted strings were not being parsed correctly has been resolved and the responses will now be correctly parsed.  (984)
  • An issue where IMAP Mailbox name encodings could be persisted between separate IMAP sessions has been resolved. Now all encodings revert to their default state when a new connection is attampted.  (989)
  • An issue where LIST responses were noit correctly parsed if NIL was in the heieracrhy separator place was resolved.  (990)    Released: 2016-07-19
Product fixes in this release:
  • An issue that could result in a null reference exception being thrown while retreiving email headers from a POP server was resolved.  (915)    Released: 2016-06-01
Product fixes in this release:
  • Mailbox heirarchy delimiters that are an escaped qouted string character (ex: "\\") will now be decoded and parsed correctly.  (901)    Released: 2016-04-15
  • Improved decoding of email messages with nonconformant MIME boundaries.
  • Improved samples to display HTML parts with charset headers that are not parsed correctly by the WebBrowser control.    Released: 2016-04-07
  • XOAUTH2 authentication support for Imap, Smtp, and Pop has been added.
  • MailMessage.ReplyInline and MailMessage.ReplyAllInline methods have been added which will prepend a reply to the original message text.
  • Imap.GetAllMailboxes has been added so that a flat list of mailboxes can be retrieved.
  • Imap.Select has been added to provide support for selecting mailboxes using an absolute path.
  • Support for UTF8=Accept and UTF8=Only server advertised 8-bit capabilities. Its use can be controlled with the ImapSession.AutoUtf8 property.
  • Support for RFC3030 (Chunking and Binary mime) and RFC6152 (8-bit Mime) for Smtp has been added.
  • Support for Xtext encoding as specified in RFC 3461 has been added.
  • Developer Note:
    In order to provide more concise groupings for server settings the Smtp and Imap controls now use SmtpSession and ImapSession to store settings instead of the previously shared MailSession.
Product fixes in this release:
  • If PunyCode decoding fails for any reason the original encoded header will be preserved.  (661)
  • Instances where some multi-line QP encoded subject headers would fail to decode correctly have been addressed.  (666)
  • An issue where some SMIME messages with a content-type of application/pkcs7-mime would fail to decode has been corrected.  (679)
  • When an email message is added as an attachment the content-type is now correctly set to application/octet-stream.  (711)
  • In issue where MailMessage.ReplyAll could incorrectly populate recipient data has been addressed.  (717)
  • An error in handling extended parameters as described in RFC2231 was addressed.  (826)    Released: 2015-04-01
  • The Bcc header will now be included when a message is saved to disk and when loaded from disk.
  • Functional Change:
    In order to make email message data available if a signature fails validation, MailMessage.SecureDecode() no longer automatically validates SMIME signatures. Signatures can now be validated using the returned SignerInfoCollection, ex:
    System.Security.Cryptography.Pkcs.SignerInfoCollection signatories = mailMessage1.SecureDecode();
    foreach (System.Security.Cryptography.Pkcs.SignerInfo signator in signatories)
Product fixes in this release:
  • Parts with a Content-Disposition of 'inline' but a Content-Type of 'multipart' will now be parsed as a Multipart, not a Resource.  (620)
  • MIME emails with UUEncoded attachments will now be decoded regardless of the presence or absence of the begin and end affixes, and encoding now includes the begin and end affixes.  (622)
  • Encoded word email addresses containing ";" will now be decoded correctly.  (633)
  • Email decoding will now succeed when the Bcc field is populated with an invalid email address.  (634)
  • When using Smtp, if Auto authentication is chosen and no user name and password are provided then authentication will default to 'None'.  (637)
  • Emails with RFC822 attachments that contain an attachment will no longer throw an IOException when Dispose is called.  (638)    Released: 2014-09-29
Product fixes in this release:
  • Calling MailMessage.Clear() will result in the message being initialized to a MIME message.  (499)
  • If there is a content disposition header present in a mail part then a resource or attachment part will always be added regardless of content type.  (511)
  • UUencoded attachments will now be encoded with a grave character instead of a space.  (519)
  • Mail message header values that use quoted printable encoding now decode correctly.  (545, 549)    Released: 2014-04-11
  • The MailMessage.IsMime property has been added to indicate and control the use of Mime encoding for the current message. Messages that are not Mime encoded will now retain their original encoding.
  • Support for decoding headers encoded with the extensions described in RFC 2231 "Parameter value and encoded word extensions" has been added.
  • The FAST and FULL fetch macros defined in RFC3501 have been added to the ImapMessageInfo enumeration.
  • SmtpResults.Recipients has been changed from a list of EmailAddress objects to list of Recipient objects in order to include a SmtpResponse property that will contain the response of the sending server for each successful send.
Product fixes in this release:
  • When calling MailMessage.ForwardAsAttachment all temporary files will now be created in directory specified by Attachment.Directory instead of the system temporary directory.  (359)
  • Malformed parts with no content-encoding would result in a null part being added to the MailMessage object, these parts will now add a text/plain part.  (395)
  • Imap flags for messages residing on a Gmail server now update correctly when messages are fetched.  (396)
  • An issue where unsolicted server responses could interrupt email message processing has been addressed.  (397)
  • Email parts without a specified content type containing are created as text/plain parts per RFC 2046.  (401)
  • Subject and Comment fields containing the semicolon (;) character will now be parsed correctly.  (419)
  • MailBox.Add now returns void. After the message has been added a NOOP can be performed to update the mailbox state.  (434)
  • Sender and ReplyTo are now parsed out if present when fetching an email's envelope with IMAP.  (450)
  • Imap.Seen will default to true when fetching a message with ImapInfo.Message or ImapInfo.Text and not specifying peek. Previously messages flagged as seen on the server would be flagged as unseen to the component.  (454)    Released: 2013-12-17
  • Added the Attachment.Directory static property which indicates where temporary files will be stored for emails after decoding.
Product fixes in this release:
  • Trial notifications have been revamped to be more friendly with service based projects.  (TFS294)
  • Dispose was added to message and protocol objects so that temporary files will be deleted when dispose is called for those objects. Please see the documentation for details.  (TFS329)    Released: 2013-10-02
Product fixes in this release:
  • Improved message cloning when malformed file attachment headers are present.  (TFS277)
  • Resolved an issue with Part.EncodingMap that could cause a race condition in multi-threaded applications.  (TFS292)
  • Improved the message object representation of mail messages that are attachments when only the structure of the parent email is retrieved with Imap.  (TFS299a)
  • Improved support for the legacy RFC822 attachment format.  (TFS299b)
  • Improved parsing of Imap email structure to provide access to parts of an email that is attached to the parent email.  (TFS300a)
  • Resolved an issue with retrieving the same attachment part repeatedly.  (TFS300b)
  • Resolved an issue where filtering for multipart message parts would return no parts.  (TFS301)
  • Resolved a segmentation issue that could occur while decoding quoted printable messages.  (TFS313)    Released: 2013-08-02
  • Addition of the MessagePart object provides support for in place decoding of message parts of content-type message/rfc822 which allows for any attachments or resources of that part to be promoted up to their respective top-level collections.
  • PowerTCP Mail for .NET is operational with Mono 2.10.9 or greater with the exception of NTLM and GSSAPI authentication.
Product fixes in this release:
  • If a charset is not present in the message or part headers but is detected in the HTML body, the charset in the HTML body will be used to decode the content of that part.  (TFS 214)
  • Support for split-line word-encoding added.  (TFS 217)
  • Mail messages received as an attachment to another mail message will now be decoded in place.  (TFS 255)
  • Allow decoding to succeed if there is a missing terminating "--" in the closing boundary demarcation of a multipart MIME encoded mail message.  (TFS 265)
  • Accommodated for System.Net.Mime.ContentDisposition producing incorrectly encoded Date/Time headers.  (TFS 268)
  • Resolved ImapMessage.Info not always updating correctly when returning to a previously selected mailbox.  (TFS 269)    Released: 2013-04-12
  • Dart Communications is pleased to announce the release of PowerTCP Mail for .NET 4.0.

    Some of the exciting new features include:

    • Model-View-Controller design uses fewer resources, is more flexible, and produces code that is easier to maintain
    • Improved use of .NET Features including generics and IPv6
    • Robust IMAPv4. POP3 and SMTP support
    • Improved thread-safe design
    • SSL support for secure communications
    • Added NTLM and GSSAPI, supporting single sign-on
    • Improved support for internationalized e-mail addresses and domains when in .NET 4.0+
    • Support for DNS resolution of internationalized domain names
    • Simplified MailMessage object, making it easier to use
    • Support for S/MIME encrypted and signed e-mails
    • Support for Windows applications, services and ASP.NET web applications
    • Many sample projects for C#, VB.NET, including ASP.NET
    • Comprehensive MS Help 2.0 and Help Viewer 1.0 integrated documentation
    • Stand-alone and online documentation also provided
    • NET Framework Client Profile compatible
    • 64-bit OS support

    Learn more about PowerTCP Mail for .NET 4.0 and download a Free Trial >
    Learn more about PowerTCP 4 technology improvements and upcoming product plans >
    PowerTCP 4.0 Mail for .NET Upgrade Guide >

    No more Async methods
    Previous versions of PowerTCP and PowerSNMP implemented an event-driven model for asynchronous use. In addition to a synchronous method, each operation had an asynchronous "BeginXXX" method and corresponding "EndXXX" event. For example, to receive data asynchronously using the Tcp component, the developer called BeginReceive and waited for the EndReceive event to fire with data. In the meantime, other code was free to execute.

    In the new design, asynchronous methods are no longer needed. Instead, the developer uses one or more synchronous methods (for example, "Receive") within function, and then passes a delegate referring to this function to the component's Start method. The Start method then executes the function a worker thread.

    Marshaling data back to the UI thread
    It is sometimes necessary to pass information from a worker thread to an element on the UI thread. The new design includes Marshal functions to simplify this operation. Each Marshal overload corresponds to an event handler that executes on the UI thread and provides access to data passed by the Marshal method.

    No more "pseudo-blocking"
    Methods in the new design are now true-blocking calls. In previous versions, methods were "pseudo-blocking," meaning that UI events could be processed while the call blocked. With the new design, the UI thread is blocked if a method is called from within the UI thread. The Start method should therefore be used in UI environments so normal UI processing is preserved.

    Use of IPEndPoints
    Many methods in the new design include overloads that take IPEndPoint parameters to facilitate IPv6 use. A new IPEndPoint derived class provides several overloads for easy IPEndPoint creation, including automatic hostname resolution.    Released: 2011-01-05
Product fixes in this release:
  • A login error introduced in version was addressed. "An address incompatible with the requested protocol was used" error would occur under certain conditions if the mail server supported IPv6.  (5374)    Released: 2010-10-21
  • PowerTCP Mail for .NET has been updated with VS 2010 integration.
  • PowerTCP Mail for .NET now supports .NET Framework 4 Client Profile.
Product fixes in this release:
  • Fixed Smtp.Authentication failures when the server supported options other than what the property was set to.  (5133)
  • Fixed index out of range exception when examining Attachments collection for messages with nested attachments.  (5146)
  • Fixed SMTP authentication problem for servers that would send more options after explicitly negotiating a secure connection.  (5194)
  • Fixed Stack overflow exception that would occur when constructing MessageStreams from some file streams.  (5224)
  • MessageStream can now decode messages using CP1252 encoding type.  (5251, 5318)
  • Fixed ArgumentOutOfRange exception when referencing some attachments in a MessageStream.  (5333)
  • Provide better error message for invalid "Search 0" response provided by SmarterMail v7.  (5343)    Released: 2009-06-29
  • A UsePipelining property has been added to the Smtp component, permitting users to choose whether or not to use PIPELINING when the server supports it.
  • Added a MimeAttachmentStream.ContentId property.
Product fixes in this release:
  • Fixed problems with some Smtp servers when PIPELINING was used with Explicit security.  (4069)
  • The MessageStream property now has a default value (MessagePriority.Normal), instead of being null.  (4723)
  • Fixed an issue with decoding headers that span multiple lines.  (4724)
  • When Imap Gets are performed with the UID option, ImapMessage.Uid is now populated.  (4726)
  • An encoding exception that would only appear in Japanese Operating Systems has been fixed.  (4758)
  • The PopLoginMethod.Apop option now works correctly.  (4762)
  • The IsMime property now works correctly.  (4774)
  • The Logout method will always timeout now if no response is received from the server.  (4781)
  • Under certain circumstances the Pop component Timeout would incorrectly be twice the value specified.  (4864)
  • The NotSeen Imap Search Criterion now works.  (4883)
  • The Content-Type and Date headers are no longer cleared when a message is encrypted or signed for S/MIME.  (4887)
  • Setting the Content-Type on the message level now correctly affects the appropriate parts of the message.  (4889)
  • The Imap component now uses the manually set Security value for Implicitly secure connections, instead of always using TLS.  (4894)
  • Certificates for wildcard domains such as * are now supported.  (4917)
  • Connecting asynchronously with Imap after trying to connect asynchronously to a non-existent server no longer causes an error.  (4935)
  • A BeginLogin overload was defaulting to the Implicit security port instead of 110.  (4937)
  • A problem with Imap and Implicit security was addressed.  (4938)
  • The Content-Type of a part can now be set after the part has been added to a message.  (4942)
  • Fixed a stack overflow exception caused by certain non-standard messages.  (4973)
  • Fixed an issue with Smtp using Explicit security and authentication.  (4977)
  • Fixed a problem with fetching some message BODYSTRUCTUREs with Imap.  (4989)
  • Corrected condition in which messages could have two FROM headers.  (5084)
  • Fixed a Quoted-Printable problem when multiple Smtp components were used on multi-processor machines.  (5091)    Released: 2008-04-08
  • If a message is sent with no From header or Smtp.MailFrom, the component looks for a Sender header to use as the From address.
  • There is a new DeliveryStatusNotification.Enabled property which can be set to false to prevent DSN extensions, even when the server supports them.
Product fixes in this release:
  • An Imap compatibility problem with Domino server has been addressed.  (4506)
  • The MessageStream no longer inserts a line into the headers of a 0 part message.  (4573, 4651)
  • S/MIME is now fully functional on 64 bit machines.  (4579)
  • A message truncation problem as been addressed.  (4637)
  • Friendly names that include '@' are now parsed correctly.  (4650)
  • The MessageStream now correctly decodes long filenames of messages created by Thunderbird.  (4688)    Released: 2008-01-30
Product fixes in this release:
  • Addressed problem with Smtp component where initialization would fail if default DNS servers were not found on the system.    Released: 2007-10-03
Product fixes in this release:
  • Header encoding issue introduced in resolved. In previous build, subject was incorrectly defaulting to UTF-8.  (4520)
  • Corrected condition that caused message corruption between creating, loading and storing.  (4525)    Released: 2007-09-13
  • Added SMIME messaging capabilities
  • Merged secure functionality from old Secure Mail for .NET product into current Mail for .NET product.
  • Optional use of stream-level encryption (SSL2, SSL3, PCT or TLS)
  • Client-side and server-side authentication
  • Options for both implicit and explicit security modes
Product fixes in this release:
  • Fixed issue that caused an attachment to be corrupt if the message did not contain an end boundary  (3855)
  • IMAP no longer puts quotes around parameters used in the Search method, unless they are strings  (4065)
  • Handles of files added using MessageStream.Attachments.Add are now properly closed when MessageStream.Clear is called  (4066)
  • SMTP now sends another EHLO message after performing the STARTTLS command to switch to secure mode  (4069)
  • Modified web samples to eliminate 'potentially dangerous Request.Form value' errors  (4070)
  • Corrected 'Outside range of Int32' error that occured when server gave large UidValidity values  (4206)
  • Addressed various issues related to UTF-8 and ISO-2022JP charsets   (4298, 4297)
  • SMTP now properly switches to secure mode before sending user/pass on servers that require authentication  (4364)
  • Fixed issue with forwarding messages as inline parts  (4459)
  • Fixed problem with the auto-construction of HTML messages  (4461)    Released: 2006-08-21
  • Mail for .NET now supports 64 bit environments.
Product fixes in this release:
  • Addressed an issue where the MessageStream HTML file constructor did not produce Quoted-Printable parts  (2993)
  • Addressed incorrect handling of CC addresses  (3003)
  • Fixed a problem with Smtp.Send when the "quick" overload was used  (3067)
  • MessageStream - decode msg w/ bad Subject  (3280)
  • Base 64 decoding is now more flexible when encoded data is slightly off  (3327)
  • Addressed a problem with decoding attachment filenames  (3535)
  • Addressed a problem with encoding Japanese HTML  (3547, 3606)
  • The Pop component will now login successfully if there is a message greater than 2 GBs in size  (3617)
  • Fixed a problem with GMT Offset when the Tool is used in VS.NET 2005  (3629)    Released: 2005-11-01
Product fixes in this release:
  • No major changes to DLL. This DLL was rebuilt and included in the 2.1.3 kit that fixed VS2005 problems    Released: 2005-08-03
Product fixes in this release:
  • Corrected GPF that occurred in Windows 98 when we attempted to get the machine name
  • Fixed error that occurred if a message subject contained the phrase 'UID:'
  • No longer fire Trace event twice for each POP command
  • Now use default charset if it is unclear what to use
  • Fixed several MailAddress parsing issues
  • Corrected condition that cause 'iso-2022-jp' to be incorrectly used
  • Fixed several Multi-Byte encoding issues
  • Corrected issue that caused attachments to download slowly    Released: 2005-02-01
Product fixes in this release:
  • Fixed issues where some public events where incorrectly obfuscated  (1748)
  • Fixed issues with email address parsing  (1748, 2163, 2720, 1956, 2330)
  • Fixed problem with 8 bit characters in commands. Example: "USER niño"  (1810)
  • Fixed many encoding/decoding/boundary issues  (1855, 1885, 1911, 1918, 1913, 2566, 1748, 2821, 2491, 2473, 2386, 2583, 2682, 2696, 2596, 2334, 2879, 2170, 1913, 2654, 2540, 2435, 2520, 2437, 2313, 2425)
  • Fixed problem where Mailbox.BeginRefresh and Mailboxes.BeginRefresh share the EndRefresh event  (1871)
  • Fixed problem where a Message's length was always reported as 0 after logging in  (1876)
  • Fixed issues with IMAP Append  (1885)
  • Fixed problem where Headers were being altered unnecessarliy  (1895)
  • Fixed licensing issues with MessageStream  (1904)
  • Fixed parsing problems when adding addresses. No longer get exception if address is invalid in existing message  (1956, 1993)
  • Fixed stack overflow issues in certain conditions  (1979, 2044, 2585)
  • Fixed problem with encoding in Mailbox names  (2101)
  • Fixed licensing issues with 3rd party components  (2146)
  • IMAP Mailbox.FirstUnseen now set to 0 if there are no messages  (2148)
  • Fixed problem intrepreting multi-line replies  (2311)
  • Removed messagebox that would pop-up during unhandled exception in events  (2332)
  • Stopped adding unecessary CRLFs in some parts  (2384)
  • Fixed issue where a crash occurred if a parenthesis is in quoted text (such as an encoded friendly name) during a BodyStructure Fetch  (2426)
  • Fixed crash when "literals" appeared in replies to STATUS command  (2462)
  • Fixed crash when "literals" appeared in message during FETCH  (2571)
  • Implemented DoEvents in IMAP  (2587)
  • Fixed issues with HTML messages  (2610, 1994, 2002, 1998, 2824, 2811)
  • Fixed various memory leaks  (2671, 2632)
  • Commands are no longer case sensitive. Example: Flags = FLAGS = flags  (2680, 2681)
  • Fixed issue with left over temp files  (2723)
  • Fixed issue where incorrect size was sent with non-Mime messages  (2741)
  • Eliminated many "Index out of bounds" and "length cannot be zero" errors when loading messages  (2875, 2604, 2932, 2971)
  • Some properties that previous had to be set to "" can now be set to null or nothing  (2957)    Released: 2003-07-28
  • This update for PowerTCP Mail for .NET focused on enhancing support for international character sets, especially for IMAP and support for non-standard header implementations. Our goal has always been to extend compatibility as wide as possible, even if that means going beyond RFC specifications. Also, this release addresses a number of minor issues that have been reported by users and a few alterations based on user feedback since the release of the previous version. If you have any specific questions concerning a particular issue, feel free to contact us and include the reference number next to the issue. Please note that this release coincides with our initial release of PowerTCP Secure Mail for .NET, which includes all the capabilities of PowerTCP Mail for .NET, plus support for SSL encryption/decryption and certificate authentication/management
Product fixes in this release:
  • Fixed a problem with attachments using international characters  (1517)
  • Added a specific exception for a bad UID when using AutoUID in POP  (1548)
  • Adjusted the licensing exception to be more informative  (1562)
  • Adjusted how Smtp responds to 5xx Response messages  (1567)
  • Added SynchronizationObject property to all components for proper multi-threaded marshalling  (1573)
  • Moved the PopEventHandler to the proper Dart.PowerTCP.Mail namespace  (1601)
  • From header no longer altered when encoded  (1602)
  • Fixed bad underscore handling with Norwegian characters  (1667)
  • Adjusted Login operation to expect capabilities with the login confirmation  (1670)
  • Adjusted error handling when a network interuption occurs  (1674)
  • Adjusted the LIST command for Exchange compatibility  (1677)
  • Adjusted the operation of CREATE command for better compatibility  (1711)
  • Added support for Mod-UTF7 encoding/decoding  (1723, 1746)
  • The ConnectedChange event now properly fires when the server aborts  (1724)
  • Adjusted how Mailbox.Refresh operates  (1738)
  • Fixed improper decoding of subject lines when more than 2 lines  (1749)
  • Adjusted incorrect usage of Shift-Jis when iso-2022-jp was specified  (1756)
  • Fixed a problem with MailAddresses.Verify  (1759)
  • Message Part headers not properly encoded when using international characters  (1760)
  • Adjusted Base64 decoding of message parts  (1763)
  • Made some Imap adjustments to support the Gordano server  (1765)
  • Fixed a problem when sending a FETCH command with a BODYSTRUCT parameter and getting rfc822 attachments  (1778)
  • Modified EventArgs for Pop.EndLogin and Pop.EndLogout to provide more error information  (1791)
  • Added the ability to specify Localport and LocalAddress for Imap  (1795)
  • Adjusted error messages in Imap for bad host and bad local host  (1795)
  • Added state parameter to Pop.BeginLogin  (1796)
  • Header decoding now supports multiple character sets for a single header  (1803)
  • Adjusted Base64 algorithm  (1803, 1807)
  • Adjusted parser that handles HTML messages  (1805)
  • Fixed a problem interpreting non-ASCII characters  (1807)
  • Fixed a problem that prevented files from getting deleted when added to a MessageStream  (1807)
  • Adjusted some of the error messages in Smtp  (1818)
  • No longer leave a NIL value during a FETCH when header item is missing  (1822)
  • Altered base64 to handle 1 byte attachment encoding properly  (1823)
  • Adjusted MessageStream Date header  (1826)
  • Adjusted operation of Smtp.Progress due to occassional report of erronous Message.Length  (1830)
  • Header lines are now properly ordered and folded  (1831, 1892)
  • Changed default behavior of international character sets  (1832)
  • MessageStream no longer adds an extra line when encoding  (1835)
  • No longer add an extra line when sending an Smtp message under certain conditions  (1836)
  • Progress event is now raised once before any transfer starts in Pop  (1837)
  • Now properly decode header values during a FETCH  (1838)
  • Fixed date problems when appending a message to a mailbox  (1838)
  • Fixed Smtp.AutoSize property  (1852)
  • Adjusted DoEvents operation in Pop  (1861)
  • Removed Last property from Pop, based on RFC change  (1862)
  • Adjusted the operation of the TCP connection during Smtp usage  (1863)
  • Adjusted the timeout operation of Imap.Login  (1868)
  • AutoPurge now only purges when CurrentMailbox is altered or before a Logout  (1869)
  • Message Forms no longer leave temp files  (1870)
  • A List no longer returns an empty array when unsubscribed  (1878)
  • Mailbox.Get and Mailbox.EndGet now return correct number of messages  (1880)
  • Can now attach Read-Only files  (1882)
  • Files added to MessageStream no longer locked  (1884)
  • Altered how CRLFs are encoded using Quoted-Printable  (1887)
  • MessageStream(Stream) constructor no longer adds an extra line  (1890)
  • Failed Examine commands no longer lock further Examine commands  (1894)
  • Mime header filenames now retain their original encoding state when loaded into a MessageStream and then saved  (1906)    Released: 2003-01-24
  • The second version of PowerTCP Mail for .NET adds an Imap component for comprehensive communications with an IMAP server. Based on the most recent revision to RFC 2060 on October of 2002, the Imap component is designed to enable a local representation of a remote IMAP server in a hierarchical structure, enabling the ability to easily represent the IMAP structure in a TreeView. Plus, the new Imap component includes full Idle support, advanced search capabilities, extensive Event notification with over 28 Events, and the ability to access individual message parts even when conducting bulk transfers
Product fixes in this release:
  • Fixed support for Smartquotes in MessageStream
  • Localized Pop, Smtp, and Imap Editor Forms
  • Reworded certain Exception messages for clarity
  • Fixed an array index problem with MessageStream.Store
  • Fixed a problem with Y-encoded multi-part files
  • Adjusted Y-encoding parser for greater compatibility
  • Fixed a stack overflow with MessageStream reading a specific type of message
  • Added an Imap component
  • Fixed a problem with Japanese attachments
  • Added support for more unusual types of Content-Ids    Released: 2002-11-25
  • This release of PowerTCP Mail for .NET adds the option of using the documentation with the older Help 1.3 engine (chm file). As some of you are developing with only the Framework and not using Visual Studio .NET, this version will help you gain access to the documentation in an easy to use manner. Also, we have compatibility tested this release against the most recent beta of Visual Studio .NET 2003
Product fixes in this release:
  • Aysnchronous operations now return an IAsynchResult object rather than a void
  • Smtp.Timeout now defaults to 30000
  • Fixed Trace that was broken in previous release    Released: 2002-11-01
Product fixes in this release:
  • Fixed a licensing error in the PopEditor Form
  • Fixed invalid code page error for MessageStream when code page is not recognized    Released: 2002-10-23
Product fixes in this release:
  • Fixed UUDecode error
  • Fixed minor Message decoding error    Released: 2002-09-13
Product fixes in this release:
  • Protocol error no longer listed as part of the FTP component
  • Unsupported characters in the header are now replaced with default
  • Licensing update in MessageStream
  • Charset header now read properly
  • Added a clearer error message for license exception
  • With absence of Content-Transfer-Encoding we no longer assume quoted printable
  • Added space to RCPT header for Exchange 2000 compatibility
  • MailAddresses RemoveDuplicates no longer throws exception when used
  • Fixed Y-encoding compatibility problem
  • No remove illegal characters when found in filenames