i have use this mf-examples and have a half success for sending email via MS Exchange of MF Groupwise.

Only if i define one ore more attachment, i become following error message " 114 Attempt to Access item beyond bounds of Memory" bei this command:

call WINAPI MAPISendMail   using by value     Mapihandle  
                                 by value     0 size 4    
                                 by reference mapimsgstruct
                                 by value     0 size 4    
                                 by value     0 size 4    
                                 returning ws-retcode     
end-call                                                  

the program allow to define 10 attachments, but crashes by using only 1 attachment.

Without attachment the mail will be send correctly.

Have everywhere found a solution on this?

I will join the netxmapi.zip, also found on mf forum

I haven't used MAPI myself, but I'll try to take a look at this later today. It may be fairly straightforward to diagnose under the system debugger.

I don't have access to a Groupwise account but I tested this sample with Outlook and I can send attachments just fine.

I am also using the latest version of Net Express which is 5.1.

The MAPI Example was written back in 1998. I compiled and ran it using Net Express 5.1 which is the only version of NX still supported by Micro Focus. The MAPI example uses the Windows Messaging API and it should work with any email client that supports MAPI. It is not specific to Outlook. I tested with Outlook because this is the email client that I use. My test proves that the program, when compiled under the current NX 5.1 product works fine and I can send an attachment without error.

There is nothing within Net Express itself that supports any of this. The program is simply calling a Windows API. It should work for Groupwise just like it works for Outlook.

If it doesn't then it may be a problem with the older version of Net Express that you are using or it may be a problem with the setup of your Groupwise. You may want to run procmon on your system to trace the Windows events that are occurring to see what it is happening when the error occurs.