| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 949.1 | Do you REALLY want filenames? | ZUR01::ASHG | Grahame Ash @RLE | Fri Mar 21 1997 11:09 | 31 |
| >I've got a customer who wants their filenames preserved when sending
>attached files from All-In-1 to Exchange. The files go through MB400
>on a VAX and then MB400 on Unix.
I'm afraid this requirement doesn't make much sense to me. An attached file in
ALL-IN-1 (note product name) will have a filename of something like:
OA$SHARE367:ZX12FG3GH.WPL (OK, perhaps also .DOC). ALL-IN-1 and the MR
environment have never supported transmission of filenames.
I would guess that the customer is worried that the datatype and format of the
files may be lost. Both XMR and the MTA have mapping policies which:
- XMR maps between ALL-IN-1 FORMAT, MR Bodypart -> X.400 Object Identifier
- MTA maps the Object Identifier to a FTBP, which can include a file
extension.
i.e. you can send from ALL-IN-1 to Exchange without loss of USEFUL information
- I don't consider the original filename to be useful. (Of course, if the
customer does, a customisation to the ALL-IN-1 system could include the
filenames of all attachments - perhaps as another bodypart, perhaps "hidden"
in the message e.g. in the Subject field).
So, if you are transmitting a file type known to XMR, and have configured the
MB400 MTA to convert the Externally Defined Bodyparts to FTBP, and it doesn't
work, it seems likely that you have a problem with a particular bodypart type.
Please see the MB400 Tuning and Problem Solving Guide, Chapter 11, for
information on mapping between Externally Defined and FTBP.
grahame
|
| 949.2 | Good Points | NETRIX::"SilvaM@mail.dec.com" | Marc Silva | Fri Mar 21 1997 17:31 | 21 |
| grahame,
Thanks for the reply.
I must confess, I really don't know All-In-1 at all and have
been dealing with this customer by phone. They claim to have been
told by Microsoft and others that filename preservation was possible
and was being done at several other companies.
I spent several hours with chapter 11, in particular Table 11-1, open
in bookreader yesterday along with reading in the Notes Conference.
I finally came to the conclusion that I either had a piece missing or
this just didn't work.
They told me they would download a file from their PC disk to All-In-1
and send it. However, they cannot at that point tell me that All-In-1
knows the filename in order to send it along with the attachment. Is
this where the breakdown begins?
Marc
[Posted by WWW Notes gateway]
|
| 949.3 | Still need a problem statement | ZUR01::ASHG | Grahame Ash @RLE | Fri Mar 21 1997 17:57 | 18 |
| Marc,
I haven't really got anything to add to .1, I'm afraid. I must admit I'm
beginning to wish I was paid according to the number of Notes I've read which
say "my customer told me that Microsoft said it was possible to . . .". Sigh.
The important question is: What is not working?
If you are only hearing that "the filename is not being kept", then say "True,
so what?"
If they say "the document can not be recognised at the receiving system", then
we have a real problem, and there is some info in .1 to help you understand
how the important info is transferred.
It's difficult to suggest anything else without knowing what the problem is.
grahame
|
| 949.4 | One Final Question | NETRIX::"SilvaM@mail.dec.com" | Marc Silva | Fri Mar 21 1997 18:28 | 9 |
| The problem is the DOS filename is not being kept (i.e., a Word document
created on the PC and named letter.doc). Is the upload of this document
to All-In-1 where the filename is lost? Or is it lost between there and
MB400?
Question is: Where is the filename letter.doc lost?
Marc
[Posted by WWW Notes gateway]
|
| 949.5 | Message Router ? | tunsrv2-tunnel.imc.das.dec.com::foster | Stan Foster - foster@mail.dec.com | Sun Mar 23 1997 00:59 | 8 |
| The filename probably gets lost entering Message Router. The bodypart
type will be preserved but not the file name. Thats why you see
attachments leaving our PMDF gateways tagged as winword.doc - we know
what the file types is and can map it to the corresponding MIME type
but the original file name is long gone by this time.
If you were going ALL-IN-1/X.400 directly the FTBP15 may work better
and preserver the filename
|
| 949.6 | Sorry, FTBP15 not supported | IOSG::WRENI | | Tue Apr 01 1997 20:20 | 17 |
|
>> If you were going ALL-IN-1/X.400 directly the FTBP15 may work better
>> and preserver the filename
V3.2 with X.400 doesn't support the File Transfer Body Part used by
default by MS-Exchange. You have to make sure Mailbus 400 is correctly
configured to ensure that FTBP15 bodyparts are correctly converted as
messages are transfered between Exchange and ALL-IN-1 users.
However the intention seems to be preservation of the PC filename rather
than the I<mumble> filename used within ALL-IN-1. This information is
lost on 'download' to ALL-IN-1; if you're using TeamLinks and attach a
DOS file to a message then the attachment's subject is defaulted to the
DOS filename. So the filename is carried in the Subject as suggested in
a previous reply.
Ian
|