Messaging Access SDK Release Notes

Messaging Access SDK Release Notes

C Version
This file was last updated on August 28, 1998.



Thank you for choosing Netscape Messaging Access SDK 3.51. These release notes contain known problems and other important information about the product. Please read these notes before using the SDK.

What's in the Messaging Access SDK? You can find the latest feature list at this URL.

For installation instructions: See the Read Me file.

For the latest documentation: See the Messaging Access SDK Guide, which is available on Netscape DevEdge Online.

[Top]


Bugs fixed in this release

The Messaging Access SDK release 3.51 includes fixes to the following bugs:

242755:   POP3 API gets parser error for retrieve with servers that do not return an octet count.
312512:   SMTP API adds an extra space at the end of mailFrom and RcptTo commands,
                which is not acceptable to some of the servers.
313521:   SMTP API does not quote the addresses.
312637:   MIME parser should handle lines larger than 512 bytes.
313545:   mime_decodeHeaderString() should handle unencoded and multiple encoded strings
                with intermixed unencoded text. Several array bounds conditions with this method fixed.
[Top]


Known problems with this release

This section describes known problems or bugs in this release. [Top

The C multithreaded examples have not been certified for the AIX or IRIX platforms.

[Top]

Documentation Errata

  • POP3 Servers and Octet Count
  • mime_multiPart_getPart function
  • mime_message_getBody function
  • [Top

    POP3 Servers and Octet Count

    pop3Sink_t.retrieveStart: The definition of the in_octetCount parameter of the retrieveStart callback (in the pop3Sink_t structure), should contain this note:
    Some POP3 servers do not return an octet count with RETR response. For these servers retrieveStart callback returns an octet count of zero (0).
    [Top]

    mime_multiPart_getPart function

    In the mime_multiPart_getPart function, the name of the in_pContentType parameter should be out_pContentType, as follows:
    int mime_multiPart_getPart (mime_multiPart_t * in_pMultiPart, 
                    int  in_index, 
                    mime_content_type * out_pContentType, 
                    void **out_ppTheBodyPart)
    [Top]

    mime_message_getBody function

    In the mime_message_getBody function, the name of the in_pContentType parameter should be out_pContentType, as follows:
     
    int mime_message_getBody (mime_message_t  * in_pMessage,
                    mime_content_type  * out_pContentType,
            void  ** out_ppTheBody)
    [Top]
     Last Updated: August 28, 1998 
    Copyright © 1997 and 1998 Netscape Communications Corporation All Rights Reserved.