KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q104298: PC MAPI: MAPISaveMail Function Resets Originator to Caller

Article: Q104298
Product(s): Microsoft Mail For PC Networks
Version(s): WINDOWS:3.0,3.0b
Operating System(s): 
Keyword(s): 
Last Modified: 09-NOV-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Mail for Windows, versions 3.0, 3.0b 
-------------------------------------------------------------------------------

SYMPTOMS
========

When you save a message using the Microsoft Visual Basic for Windows
MAPISaveMail function, the Originator parameter of the message is set to the
Mail user who logged on.

CAUSE
=====

The Microsoft Visual Basic MAPIMessage structure does not contain an Originator
field like the C equivalent message structure does. Therefore, the actual
originator cannot be saved--instead, the logon user information is saved in this
field (when it is read by MAPIReadMail). The C MAPISaveMail function correctly
preserves the originator field because it is in the C MAPIMessage structure.

STATUS
======

Microsoft has confirmed this to be a problem in versions 3.0 and 3.0b of
Microsoft Mail for Windows. This problem was corrected in version 3.2 of
Microsoft Mail for Windows.

Additional query words: 3.00 3.00b

======================================================================
Keywords          :  
Technology        : kbMailSearch kbZNotKeyword3 kbMail300 kbMail300b
Version           : WINDOWS:3.0,3.0b

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.