Extended MAPI has been a long requested enhancement for PowerBuilder.
In PowerBuilder 12.6 Extended MAPI was implemented with the interface unchanged. This means that existing PowerBuilder applications will continue to work without modifying the Powerscript source code. Most mail object related functions and properties are identical to Simple MAPI with only a few changes that are described below.
PB 12.6 Extended MAPI changes to the Mailsession object:
(1) functionmailReadMessage( messageid, mailmessage, readoption, mark )
For the readoption argument, valuemailBodyAsFile!is not supported for Extended MAPI. It will work asmailEntireMessage!If used in powerscript code.
(2) function mailResolveRecipient( recipient {, allowupdates } )
The optional argumentallowupdatesis always false for Extended MAPI.
(3) function mailRecipientDetails( mailrecipient {, allowupdates } )
The optional argumentallowupdates is always true for Extended MAPI.
PB 12.6 Extended MAPI changesto the mailFileDescriptionobject
(1 (1) FileTypeProperty
OnlymailAttach!is supported for Extended MAPI, it will assume this value if you specify one other value (mailOLE! ormailOLEStatic! ).
If the Windows operating system being used does not support Extended MAPI, PowerBuilder 12.6 will use the legacy Simple MAPI.
64-bit PowerBuilder mail applications can only work with 64-bit Windows MAPI. 32-bit PowerBuilder applications can only work with 32-bit Windows MAPI.
Known Issues
CR 780378 – PB 12.6 GA through EBF 24160 (build 4035)
Regression when mail is sent from PB 12.6, a copy of the mail sent is not placed in the senders Outlook folder. A fix is not yet available in a product release. This will be updated with EBF details once the CR is fixed.