| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2172.1 | | AIMTEC::ZANIEWSKI_D | Add Jean to the list of deserters! | Tue May 06 1997 09:41 | 11 |
| Hi Debbie,
I'd don't have any answers, but lots of questions. What is the
server being used for this TeamLinks user? Are they using Message
Router/MRX, MAILbus 400 or something else like PMDF? Is this a
body or an attachment? What is the gateway that converts to MIME?
Since it makes it most of the time, this may point to a gateway
conversion that isn't happy with something in the document format.
Dave Zaniewski
|
| 2172.2 | some questions | TAMARA::qwert.zko.dec.com::ANONYMOUS% | John McClung, 381-2774 | Tue May 06 1997 10:22 | 62 |
| Debbie,
A bunch of questions:
1. What is the primary file cabinet in TL (Internet Mail?)
2. Can you reproduce the problem?
3. What exactly is the problem - when is "doesn't work", what is wrong? I'm
guessing that the attachment in Exchange is not displayed with the Excel bitmap,
and launching/viewing it does not launch Excel or view Excel properly? What
happens when he launches/views the problem attachment?
4. What version of Excel was the file created with?
5. What is the TL format tag value for the Excel attachment?
6. What version of Windows?
7. Why did he modify TLFORMAT.INI? When he tried it with the original
TLFORMAT.INI, what was the problem?
8. Can he/you try sending the exact same Excel attachment from TL to his/your TL
internet mail address also? When the message is received using TLPOP3 is the
attachment tagged properly? Every time?
9. If any other email POP3 client is available (Netscape), does it receive the
message properly every time?
10. Of the 20 identical messages he sends, I'm assuming that the 20 Outbox
copies are all identical? These contain the MIME that is sent. If these are
identical, then it doesn't make sense that Exchange would decode some properly,
and some not.
11. Could you please copy the problem Excel file and a copy of his TLFORMAT.INI
to XANADU::?
12. What version of Exchange (client and server) is he running?
That's all I can think of for now - should keep you busy a while :-)
John
>Customer has TeamLinks 2.7 eco1. He is trying to
>send Excel spreadsheet to Microsoft Exchange account.
>He has attempted to add the MIMEContentType string to
>tlformat.ini and the strange thing is it works sometimes,
>sometimes it doesn't.
>
>If he chooses the same spreadsheet and sends 20 times,
>15 may be successful, 5 are not.
>
>Help!
>
>The string he is using in TLFORMAT.INI is below:
>
>MIMEContentType=application/vnd.ms-excel; name="TL.xls"; type=%%peg%%
>
>Any ideas?
>
>Debbie Giannetti
|
| 2172.3 | Here's what I DO have! | ALFSS2::GIANNETTI_D | | Tue May 06 1997 14:57 | 86 |
| reply: Questions:
1. What is the primary file cabinet in TL (Internet Mail)?
A. MailWorks for VMS v1.3a-1
2. Can you reproduce the problem?
3. What exactly is the problem - when is "doesn't work",
what is wrong? I'm guessing that the attachment in
Exchange is not displayed with Excel bitmap, and
launching/viewing it does not launch Excel or view
Excel properly? What happens when he launches/views
the problem attachment?
A. If he sends encoded the recipient receives an ******.ATT
file, which is a valid/functional file, however, he
must file save/as ******.xls in order to use on
system as an Excel file.
If he sends MIME - same thing *******.ATT file
same scenario as above
If he UUENCODES - it sometimes comes across with
garbage text, unusable format
Intermittently it comes across as an *******.XLS
but the ******* has been changed from the original
filename to encrypted
4. What version of Excel was the file created with?
A. Excel 5.0
5. What is the TL format tag value for the Excel
attachment?
A. Cust is using XLS5 (has automatic format detection
turned off)
6. What version of Windows?
A. Windows 95 (no plus pak) and Windows 3.1
7. Why did he modify TLFORMAT.INI? When he tried it with
the original TLFORMAT.INI, what was the problem?
A. He had the problems listed above with number 3
using the original TLFORMAT.INI, he modified in
an effort to change behavior and results
8. Can he/you try sending the exact same Excel attachment
from TL to his/your TL internet mail address also?
When the message is received using TLPOP3 is the
attachment tagged properly? Every time?
A. Waiting
9. If any other email POP3 client is available (Netscape),
does it receive the message properly, every time?
A. Have not tried anything with POP3 (he does not
have a POP3 server at his site)
10. Of the 20 identical messages he sends, I'm assuming that
the 20 OUTBOX copies are all identical? These contain
the MIME that is sent. If these are not identical, then
it doesn't make sense that Exchange would decode some
properly, and some not.
A. Has not checked this but will check for me
11. Would you please copy the problem Excel file and a copy of
the customer's TLFORMAT.INI to XANADU::?
A. Waiting
12. What version of Exchange (client and server) is he running?
A. Server 4.0 with service pak3 mostly (some not up to svc pak3)
Client 4.0
|
| 2172.4 | maybe a gateway conversion problem? | TAMARA::qwert.zko.dec.com::McClung | John McClung, 381-2774 | Wed May 07 1997 14:50 | 36 |
| Debbie,
As Dave asked in .2, what (if any) gateway is on his system to handle the MIME
encoding when sending to the internet? The fact that sometimes (usually?) the
message is received properly indicates something wrong outside of TeamLinks (the
gateway conversion software on the VMS/MailWorks system, or something on the
Exchange server, ...?).
What address does he type into the To: field? Something like
[email protected]@internet? I've tested this here by using TL with MailWorks to send
to my Exchange account like this:
To: [email protected]@internet
The received message with the Excel 5 attachment is received fine. The
attachment is named EXCEL.XLS, and double clicking it invokes Excel on it.
When using MailWorks or ALL-IN-1 to send to the internet, it's best to have a
gateway setup to handle the MIME encoding. Our system has PMDF. When this is the
case, you should NOT have TeamLinks do any (MIME or UU) encoding on send. If you
do, it will result in the message being encoded twice, which will prevent the
receiving end from decoding it properly.
Assuming this user's system does have something like PMDF installed on it, tell
him not to have TeamLinks do any encoding, and that changing TLFORMAT.INI as he
did will have no effect, since it's only used when TeamLinks does the encoding.
There MAY be some changed needed in the gateway conversion options which would
help.
I have seen this xyz.ATT problem before on messages received by Exchange. It was
caused by PMDF not tagging the attachments properly when doing the MIME
encoding. As you said, saving it to a file with the proper file extension
resulted in a launchable/viewable file - the trick is you need to know it's type
and extension.
John
|
| 2172.5 | PMDF gateway was the prob | ALFSS2::GIANNETTI_D | | Thu May 08 1997 12:57 | 3 |
| Thanks guys it was the PMDF mapping table needed changing.
Debbie Giannetti
|