| Title: | TeamLinks for Windows |
| Notice: | Kit and ECO locations: See replies to note 8. o note 8. |
| Moderator: | ORION::chayna.zko.dec.com::tamara::eppes AN |
| Created: | Mon Aug 28 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2238 |
| Total number of notes: | 9650 |
TeamLinks 2.7 Internet Mail UNIX 3.2c Customer has Internet Mail as their primary mail file cabinet on a Unix 3.2c system. Customer creates a mail message and adds two attachments from DOS. Attachment names are BILL.DOC and BILL.PPT. Sends to user. The recipient receives the message nad instead of retaining the name BILL.DOC and BILL.PPT they now have the names TL.DOC and TL.PPT. I tried here first with a POP3 server on a VAX 3100 WITH 6.2 VMS AND UCX 4.1. I noticed when I received the message, before decoding the attachment name was TL.DOC and TL.PPT but after decoding the attachments in the "decoded" message were named their original names. I tried to test here on our OSF server but ran into snags. Instead of waiting I talked with R.P. and he said to put this out here. If I understand the customer correctly, when they receive the message on their system - it has already been decoded. If this is the case then is there something they can configure at the server or the client end to force the original name to be restored once the message is decoded? Thanks in advance. Debbie Giannetti
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1966.1 | send to exchange lost original names | AIMTEC::GIANNETTI_D | Wed Jan 29 1997 15:58 | 6 | |
In testing further, if I send the message from my internet mail
(on my UCX 4.1 system) to my exchange account, the two documents
when received were already decoded but were in fact named TL.DOC
and TL.PPT and original names were lost there as well.
Debbie
| |||||
| 1966.2 | It's not an MS-DOS file anymore. | TAMARA::HOVEY | Thu Jan 30 1997 11:22 | 26 | |
When teaminks mime encodes a draft message, it is comming out of the filecabinet, not DOS so it does not have an MS-DOS name. When the MIME is created, teamlinks just uses "TL" as a stub; but it can fake up the extention using the fileformat tag to map to a dot three character extention. Thus an attachment documents file format tag "MS-DOS BATCH File" is mapped to "BAT" in tlformat.ini. If you look at the raw mime teamlinks creates, the Content-Type: line will have "name=tl.bat". When a document is imported into the filecabinet from MS-DOS, the 8.3 filename is the default display/subject name; but this is not used on the name= line since most of the time attachments come from the filecabinet where this text can be any subject line the user chose to type in. Although to the user the steps seem like they are in the same context (i.e. I create a mail message, attach a DOS document and MIME encode it); they really aren't and TeamLinks does not know it's an MS-dos file anymore are the time the MIMEing is done. As far as the MIME create is concerned, it's just a CFC document with attachments and the fact that one of the attachments was originally an MS-DOS file has been lost. The original MS-DOS filename is not stored in the CFC... because a unique name must be generated anyway when the file is fetched to the teamlinks staging directory. | |||||
| 1966.3 | reply | AIMTEC::GIANNETTI_D | Fri Feb 07 1997 10:48 | 6 | |
I relayed the message to the customer but he says all other
programs are able to do this despite the "file cabinet" issue
and he would like to suggest that we incorporate this as a
feature.
Debbie Giannetti
| |||||