How to delete files on .MAPIMail

Question

Given some files (or shell file files), how can I call the .MAPIMail extension .MAPIMail registered shells with them?

---

Question

I have some files on the computer:

• C:\Users\ian\AppData\Local\Temp\Contoso_Invoice_141174.pdf
• C:\Users\ian\AppData\Local\Temp\Contoso_Invoice_141173.pdf
• C:\Users\ian\AppData\Local\Temp\Contoso_Invoice_141171.pdf

What I want to do is the software equivalent by dropping them to a registered .MAPIMail handler:

The Sent to Mail Recipient parameter is actually a registered .MAPIMail extension:

What type of file is registered in the system:

 HKEY_CLASSES_ROOT\.mapimail 

How to call drop on ephermeral .MAPIMail file?

Can't you just look in the registry?

Now, I can be a poor developer and spellunk registry, the default value .MAPIMail value:

 CLSID\{9E56BE60-C50F-11CF-9A2C-00A0C90A90CE} 

Extract clsid {9E56BE60-C50F-11CF-9A2C-00A0C90A90CE} and confirm that the class is registered:

 HKEY_CLASSES_ROOT\CLSID\{9E56BE60-C50F-11CF-9A2C-00A0C90A90CE} (default) = Desktop Shortcut \InProcServer32 (default) = %SystemRoot%\System32\sendmail.dll 

And use CoCreateInstance to create this COM object:

 IUnknown unk = CreateComObject("{9E56BE60-C50F-11CF-9A2C-00A0C90A90CE}"); 

And then I ended up in an undocumented, unsupported world where I don’t know what interface I should QueryInterface for, and which methods to call in which order.

So, we have left shell programming

I would like, most likely, something related to the shell (pseudocode):

 IShellFolder desktop; OleCheck(SHGetDesktopFolder(out desktop)); List<pidl> pidls = new List<pidl>(); ULONG chEaten = 0; ULONG dwAttributes = 0; PIDL pidl; foreach (String filename in Files) do { OleCheck(desktop.ParseDisplayName(0, nil, filename, out chEaten, out pidl, ref dwAttributes)); pidls.Add(pidl); } //Get the shell folder of the temp folder IShellFolder tempShellFolder; desktop.ParseDisplayName(0, nil, GetTemporaryPath, out chEaten, out pidl, ref dwAttributes)); desktop.BindToObject(pidl, nil, IShellFolder, tempShellFolder); //i have no idea what i've been doing; just throwing reasonable looking code together //nobody will actually ever read this IDontCare context; tempShellFolder.GetUIObjectOf(0, pidls.Count, pidls, IDontCareAnymore, nil, ref context); 

Except for all this code, it depends on the availability of the context menu. I don’t have. No one says .MAPIMail should be in any Send to context.

I asked how to drop files in a .MAPIMail file.

And my god.

Why not just use MAPI?

Since no MAPI client is installed when you are a 32-bit application running on a 64-bit version of Windows with 64-bit Office installed. Therefore, I need to accomplish what the user can already do.

Answer 1

Although he does not answer my question, Raymond indicated that this is a stupid question. No one in their right mind should send mail to recipients. But I was desperate!

Turns out I'm not completely stuck. Despite the fact that 64-bit Outlook (MAPI provider) out of 32-bit applications (or vice versa) has a nightmare with bit, there is one way out.

If I use only MapiSendMail and other MAPI functions , it is safe to cross the 32-bit / 64-bit barrier. From Creating MAPI Applications on 32-bit and 64-bit Platforms :

32-bit MAPI application and 64-bit Outlook

32-bit MAPI applications are not supported for running on a computer installed with 64-bit version of Outlook and 64-bit Windows. The application developer must update and rebuild the application as a 64-bit application for the 64-bit platform. This is because the 32-bit application cannot load the 64-bit Msmapi32.dll file. There are a small number of API changes that application developers must implement to successfully create code for a 64-bit environment. MAPI header files have been updated with these changes to support the 64-bit platform. You can load these header files in Outlook 2010: MAPI header files . Developers can use the same set of MAPI header files to create 32-bit and 64-bit MAPI applications.

It sounds like all hope is lost. But on Windows 7 there is:

Exception: MAPISendMail

However, one function call among all Simple MAPI and MAPI elements, MAPISendMail , will succeed in Windows-32-bit-on-Windows-64-bit (WOW64) or Windows-64-bit-on-Windows-32-bit (WOW32) and will not result in the warning above. This WOW64 script is applicable only to Windows 7. Figure 2 shows the WOW64 script in which a 32-bit MAPI application calls MAPISendMail on a computer installed with 64-bit Windows 7. In this case, the MAPI library makes a COM call to launch 64-bit Fixmapi applications. The Fixmapi application implicitly references the MAPI library, which routes the function call to the Windows MAPI stub, which, in turn, redirects the call to Outlook MAPI, allowing the MAPISendMail function to be successfully completed.

So, as a Delphi Jedi user, their simple email sending features will not work (because they use too much MAPI). So I had to create my own:

 procedure MapiSimpleSendMail(slFiles: TStrings; ToEmailAddress: string=''; ToName: string=''); var mapiMessage: TMapiMessage; flags: LongWord; // senderName: AnsiString; // senderEmailAddress: AnsiString; emailSubject: AnsiString; emailBody: AnsiString; // sender: TMapiRecipDesc; recipients: packed array of TMapiRecipDesc; attachments: packed array of TMapiFileDesc; i: Integer; hr: Cardinal; es: string; const MAPI_E_UNICODE_NOT_SUPPORTED = 27; //Windows 8. The MAPI_FORCE_UNICODE flag is specified and Unicode is not supported. begin ZeroMemory(@mapiMessage, SizeOf(mapiMessage)); { senderName := ''; senderEmailAddress := ''; ZeroMemory(@sender, sizeof(sender)); sender.ulRecipClass := MAPI_ORIG; //MAPI_TO, MAPI_CC, MAPI_BCC, MAPI_ORIG sender.lpszName := PAnsiChar(senderName); sender.lpszAddress := PAnsiChar(senderEmailAddress);} mapiMessage.lpOriginator := nil; //PMapiRecipDesc; { Originator descriptor } if ToEmailAddress <> '' then begin SetLength(recipients, 1); recipients[0].ulRecipClass := MAPI_TO; recipients[0].lpszName := LPSTR(ToName); recipients[0].lpszAddress := LPSTR(ToEmailAddress); mapiMessage.lpRecips := @recipients[0]; //A value of NULL means that there are no recipients. Additionally, when this member is NULL, the nRecipCount member must be zero. mapiMessage.nRecipCount := 1; end else begin mapiMessage.lpRecips := nil; //A value of NULL means that there are no recipients. Additionally, when this member is NULL, the nRecipCount member must be zero. mapiMessage.nRecipCount := 0; end; mapiMessage.lpszMessageType := nil; if slFiles.Count > 0 then begin emailSubject := 'Emailing: '; emailBody := ' '+#13#10+ //Yes, the shell really does create a blank mail with a leading line of ten spaces 'Your message is ready to be sent with the following file or link attachments:'+#13#10; SetLength(attachments, slFiles.Count); for i := 0 to slFiles.Count-1 do begin attachments[i].ulReserved := 0; // Cardinal; { Reserved for future use (must be 0) } attachments[i].flFlags := 0; // Cardinal; { Flags } attachments[i].nPosition := $FFFFFFFF; //Cardinal; { character in text to be replaced by attachment } attachments[i].lpszPathName := PAnsiChar(slFiles[i]); { Full path name of attachment file } attachments[i].lpszFileName := nil; // LPSTR; { Original file name (optional) } attachments[i].lpFileType := nil; // Pointer; { Attachment file type (can be lpMapiFileTagExt) } if i > 0 then emailSubject := emailSubject+', '; emailSubject := emailSubject+ExtractFileName(slFiles[i]); emailBody := emailBody+#13#10+ ExtractFileName(slFiles[i]); end; emailBody := emailBody+#13#10+ #13#10+ #13#10+ 'Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.'; mapiMessage.lpFiles := @attachments[0]; mapiMessage.nFileCount := slFiles.Count; end else begin emailSubject := ''; emailBody := ''; mapiMessage.lpFiles := nil; mapiMessage.nFileCount := 0; end; { Subject Emailing: 4388_888871544_MVM_10.tmp, amt3.log, swtag.log, wct845C.tmp, ~vs1830.sql Body <-- ten spaces Your message is ready to be sent with the following file or link attachments: 4388_888871544_MVM_10.tmp amt3.log swtag.log wct845C.tmp ~vs1830.sql Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled. } mapiMessage.lpszSubject := PAnsiChar(emailSubject); mapiMessage.lpszNoteText := PAnsiChar(emailBody); flags := MAPI_DIALOG; hr := Mapi.MapiSendMail(0, 0, mapiMessage, flags, 0); case hr of SUCCESS_SUCCESS: {nop}; //The call succeeded and the message was sent. MAPI_E_AMBIGUOUS_RECIPIENT: begin //es := 'A recipient matched more than one of the recipient descriptor structures and MAPI_DIALOG was not set. No message was sent.'; raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_AMBIGUOUS_RECIPIENT', SysErrorMessage(hr)]); end; MAPI_E_ATTACHMENT_NOT_FOUND: begin //The specified attachment was not found. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_ATTACHMENT_NOT_FOUND', SysErrorMessage(hr)]); end; MAPI_E_ATTACHMENT_OPEN_FAILURE: begin //The specified attachment could not be opened. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_ATTACHMENT_OPEN_FAILURE', SysErrorMessage(hr)]); end; MAPI_E_BAD_RECIPTYPE: begin //The type of a recipient was not MAPI_TO, MAPI_CC, or MAPI_BCC. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_BAD_RECIPTYPE', SysErrorMessage(hr)]); end; MAPI_E_FAILURE: begin //One or more unspecified errors occurred. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_FAILURE', SysErrorMessage(hr)]); end; MAPI_E_INSUFFICIENT_MEMORY: begin //There was insufficient memory to proceed. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_INSUFFICIENT_MEMORY', SysErrorMessage(hr)]); end; MAPI_E_INVALID_RECIPS: begin //One or more recipients were invalid or did not resolve to any address. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_INVALID_RECIPS', SysErrorMessage(hr)]); end; MAPI_E_LOGIN_FAILURE: begin //There was no default logon, and the user failed to log on successfully when the logon dialog box was displayed. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_LOGIN_FAILURE', SysErrorMessage(hr)]); end; MAPI_E_TEXT_TOO_LARGE: begin //The text in the message was too large. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_TEXT_TOO_LARGE', SysErrorMessage(hr)]); end; MAPI_E_TOO_MANY_FILES: begin //There were too many file attachments. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_TOO_MANY_FILES', SysErrorMessage(hr)]); end; MAPI_E_TOO_MANY_RECIPIENTS: begin //There were too many recipients. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_TOO_MANY_RECIPIENTS', SysErrorMessage(hr)]); end; MAPI_E_UNICODE_NOT_SUPPORTED: begin //The MAPI_FORCE_UNICODE flag is specified and Unicode is not supported. //Note This value can be returned by MAPISendMailW only. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_UNICODE_NOT_SUPPORTED', SysErrorMessage(hr)]); end; MAPI_E_UNKNOWN_RECIPIENT: begin //A recipient did not appear in the address list. No message was sent. raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_UNKNOWN_RECIPIENT', SysErrorMessage(hr)]); end; MAPI_E_USER_ABORT: begin es := 'The user canceled one of the dialog boxes. No message was sent.'; raise Exception.CreateFmt('Error %s sending e-mail message: %s', ['MAPI_E_USER_ABORT', es]); end; else raise Exception.CreateFmt('Error %d sending e-mail message: %s', [hr, SysErrorMessage(hr)]); end; end; 

Note Any code issued in a public domain. No attribution required.