Mapi FAQ

This is because the mapi.dll is in the system32 subdirectory on NT 4.0. You can't move it to the system directory because in NT 4.0 it is just a shell that does some thunking into the Mapi32.dll. To correct the problem, the dll search path will have to be modified in the source code to include the system32 directory. The users that have the source will have to modify the search path, users that do not have the source code, will have to purchase
it to solve the problem. Top

Why does my application hang when I use the Logon method?

Logon works with Exchange on 95 , but not with MS Mail. Exchange Inbox and MsMail client handle logons differently. Exchange Inbox uses the username field as the profile. MsMail uses the username as the username. On some systems, this could hang the application if not handled. Top

Can the ISGMapi get the size of the message?

Sorry, but it is not possible with simple Mapi. Extended Mapi or OLE messaging is needed. Top

Can the ISGMapi get messages from a folder other than the InBox?

Sorry, but it is not possible with simple Mapi. Extended Mapi or OLE messaging is needed. Top

Does the IsgMapi component need a mail server?

Yes. IsgMapi needs a functioning MAPI compliant mail server. Two of the more common mail servers are MS Mail and Groupwise. Top

Will the IsgMapi component work with MS Exchange?

Yes, it will work with MS Exchange. It has been tested with the Exchange client & the Exchange server in Windows 95 & Windows NT. Top

Will the IsgMapi component work with MS OutLook?
Why do I get the error '' is not a valid integer when using the FormPacker with Outlook?

The ISGMapi component will work with MS Outlook, However the EFormPacker component will NOT work with Outlook. Microsoft has changed the EForm Mapi functions to return the OLE COM objects identifier rather than the Mapi message ID. Without the message ID the FormPacker can not function correctly. Top

Will the IsgMapi component work with MS Windows NT?

Yes, it will work with NT. It has been tested with the NT 3.51. If you are using the 16-bit version of the component, make sure that the MAPI.DLL file is in the \WINNT\SYSTEM directory. By default, it isn't there. The 32-bit version uses the MAPI32.DLL which is in the \WINNT\SYSTEM32 directory. Top

Will the IsgMapi component work with cc:Mail or other VIM systems?

Yes, But you will need a copy of the MAPIVIM.DLL file. You can download a copy of the DLL and some notes on how to use the file with the ISGMapi component. Top

I am using the eform template in version 1.0 and the data in the controls is not being sent. What am I doing wrong?

Every control has a tag property that needs to have a unique identifier in it. It uses this to package the information. This has been made easier with the new version 2.0 FormPackager component. You only have to double click on our component and you will be presented with a list of all the controls on the form. Check off the ones you want packaged and it will do the work for you. Top

Is it possible to determine whether a mail message has been sent with a receipt requested or is still unread?

Yes. After a mail message is read (using the ReadMail method), the MsgOptions property is set to contain this information. The following sample code gives an example of this.

var
    tStr : String;
begin
    with IsgMapi1 do
       while FindNext do
          begin
              ReadMail;
              tStr:=Originator+' '+Subject;
              if mmfReceiptRequested in MsgOptions then
                 tStr:=tStr+' RR';
              if mmfUnRead in MsgOptions then
                 tStr:=tStr+' Unread';
              MyListBox.Items.Add(tStr);
         end;
end;

Top

When the text from the NoteText property is displayed in a memo control, the text seems to format inappropriately. How is text formatted?

The text is placed into a TStringList so each line cannot be larger than 255 characters (due to Delphi 1.0 limitation). The text is therefore formatted so that CRLF breaks a line. If there are no CRLF breaks within
a 255 character segment, then the line is broken at the last space. If there isn't a space, then the line is arbitrarily broken at 255 characters. Depending on the width of your memo control this may be a good or bad number
(255 characters). If you need additional control, the following code will give you an example of one way to proceed. Remember that the Msg^.NoteText points to the null terminated string after the ReadMail and before the FreeMsgMem call.

if (Msg^.NoteText <>nil) <B>then
begin
    i:=0;
    while i < StrLen(Msg^.NoteText) do
    begin
       nLoc:=StrPos(Msg^.NoteText+i,#13#10);
       { Instead of using 255, use your own preference }
       if (nLoc=nil) or ((nLoc-Msg^.NoteText-i)>255) then
         begin
             j:=255;
             tLoc:=0;
             while (j>0) and (tLoc=0) do
                 begin
                    if Copy(StrPas(Msg^.NoteText+i+j),1,1)=' ' then
                       tLoc:=j+1;
                   Dec(j);
               end;
             if tLoc=0 then tLoc:=255;
             MyNoteText.Add(Copy(StrPas(Msg^.NoteText+i),1,tLoc));
             i:=i+tLoc;
          end
       else
         begin
            MyNoteText.Add(Copy(StrPas(Msg^.NoteText+i),1, nLoc-Msg^.NoteText-i));
            i:=i+(nLoc-Msg^.NoteText-i)+2;
        end;
    end;
end;

Top

I can't get the browser to find E-Forms. I'm using a Shared directory in Ms Mail, is this a problem?

Using a Shared directory in MS Mail is not a problem with the component as long as it has been configured properly. The E-Form Browser has a bug that will cause eforms stored in the shared.ini not to be displayed in
the browser. You must modify the MAIN.PAS file so that line number 114 looks like the following:
tStr:=tStr+'\shared.ini'; Top

When sending E-Forms, some machines on our network return a "File Access Denied" error. What is the cause?

The send routine creates a file 'EFPACK.DAT' which is saved to disk and then attached to the message. When using a network drive the component may attempt to store the file to a directory that has read-only access.
To avoid this problem, the directory containing the program should not be read-only (some Windows 95 and NT systems may still have random problems due to their choice of unqualified file locations). The solution to the problem is to qualify the path. The TFormPackage.SendBtnClicked(Sender:TObject) routine must be changed to include code to use a complete path. GetWindowsDirectory() or GetTempPath() can be very helpful. Contact customer support if you need assistance. Top

Can I use ISGMapi to Send a Fax?

With MS Exchange you can place an open square brace '[' at the beginning and a closed square brace ']' at the end of the address. Once these are added to the address and then this address is added to the RecipientsTo
property, the SendMail method can be called and ISGMapi will send the message. Exchange will see the message as a fax and route the message to a Fax Gateway.

Please Note: This has only been tested with Exchange running and configured with a fax gateway. This process has only been tested using these FaxServers: Exchange, ZetaFax and FaxMaker. Top

Why do I get the error "xx.dcu file not found" or "xx.pas file not found" when running or compiling my application in Delphi 3.0

The directory where you have installed the components is not listed in the Delphi 3.0 Library Search Path. If you select tools in the menu bar of Delphi 3.0 and then click on "Environment Options" Once you're in
the environment options window click the "Library" tab and add the path to your newly installed components to the Library path. Click OK when you are done and now your application will compile and run with out the 'file not found' error. Top

When I send mail with the MessageType property set to 'IPC.OMB' to a person using MS-Exchange or Group-Wise the MessageType is dropped. What is the cause?

The support of Simple Mapi is very weak by most vendors, as a result not all email clients will support all the functions of Simple Mapi. MS-Exchange & Group-wise do not support the MessageType property. Top

[ Home ] [ Up ]

Send mail to webmaster@didelot.com with questions or comments about this web site. Copyright © 2001 Infinity Software Group Last modified: October 23, 2001

Send mail to webmaster@didelot.com with questions or comments about this web site.
Copyright © 2001 Infinity Software Group
Last modified: October 23, 2001