| Helen,
The customer has responded to your questions:
Thanks for all your help. Aisha
> I spoke with the customer again and she gave me the actual scenario
> of the problem.
>
> The customer is using the (simple) MAPI.DLL file that is in the TL2.7
> kit. She copies the file into the window/system directory. She runs
> a product called Saratoga to create a message. She clicks on SEND
> within Saratoga and is then prompted to log into her TL Filecabinet
> by entering her Username and Password. When the message is sent
> it goes through the TL message system. (Mailworks is her Mailserver)
> The user then opens TL and attempts to read the message. This is when
> the users sees boxes for character returns as mentioned in note 1827.
Does a TeamLinks create message window ever appear in this
scenario?
CUSTOMER: NO.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If not then they are sending the message without a TeamLinks
UI. In this case they can send the TeamLinks MAPI dll the cover memo
text in one of 2 forms; either it is passed as a string parameter to
the call and the MAPI dll creates a temporary file from that string
and sends it, or it sends a file of it's own in which case we just
use that file as is.
CUSTOMER: I believe it is passed as a string parameter to the call and the MAPI
dll creates a temporary file from that string and sends it. When recieving the
message in Teamlinks, all carriage returns look like boxes and the next line is
attached to the top line. A carriage return is forced by the size of my
Teamlinks Read Message Window.
Example:
Refer to the following bullet item:[][]Item no. 1[]Item no. 2[]Item no. 3[]Item
no 4[]Item no. 5[][]
* Note: [] detnotes a square and is suppost to be a carriage return.
When using Microsofts MAPI, the message is created in Saratoga, selecting the
send button causes Microsofts Mail logon to appear as well and the message is
sent after logon. When reading in Teamlinks, all carriage returns are fine.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'm not really sure why the wierd characters are
appearing, but would be very helpful is to have the actual message. We
could probably figure out what the characters are and in turn why
they are showing up.
CUSTOMER: The wierd characters are boxes that are suppose to be carriage
returns.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> She is concerned that the TL Mapi.dll driver is much different than
> the ms/mail Mapi.dll driver and needs this to be addressed offically
> somehow.
Well the Microsoft MAPI dll is different. I believe it is a full
MAPI implementation, not a Simple MAPI implementation, but I don't
believe that is the issue. The TeamLinks Simple MAPI dll is written
to a standard API. There may be differences between the two, but it
does follow the API.
CUSTOMER: I am not concerned that Microsofts MAPI is different then Teamlinks
other then Teamlins MAPI doesn't work well and Microsoft MAPI does. Microsoft
does not have a full MAPI out yet either. They have 16 and 32bit MAPI files.
Thank you for addressing this issue.
Lynn St.Denis/Sr. Systems Engineer
|
|
Aisha,
Thanks for posting the information. It would have been helpful to
have the actual file, but it doesn't look like that's going to happen.
I have seen something similar when using Lotus WordPro, so hopefully we
can reproduce it here and try and fix it.
And not that this matters in this particular issue, but Microsoft
does have full MAPI. Having 16 and 32 bit MAPI files have nothing
to do with that. The only reason I even mentioned it is that there
are other problems caused by the fact that our MAPI.DLL is a Simple
MAPI implementation and Microsoft's is a FULL MAPI implementation.
.....helen
|
|
Well, I looked into this whole issue a little more and
I don't believe it is a Simple MAPI problem at all. When
someone calls the Simple MAPI call to SendMail, they send
the text. We take it as is and send it along. That's the
correct thing to do. The calling application in this case
is sending those funny carriage returns.
What is probably the difference in this case is viewing the
message. I did some testing around this with another application
that had similar symptoms and could see the boxes when viewing
the message with V2.7 of TeamLinks. For the next version we
are using a different viewer and the boxes no longer appear.
So, I believe this problem will be resolved with the next version
of TeamLinks.
......helen
|