| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2031.1 | XMR issue? | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Thu Mar 06 1997 16:45 | 19 |
| Erich,
No idea. What mail client is receiving it? DAT is a file extension
used for WordPerfect Merge Data files, not normal documents. Is
there any chance this is really a merge file?
What would they expect a WP 5.* attachment to look like? Perhaps
"Attach.wp"? WP 5.* didn't really have a default a file extension.
By convention, they used WP and DOC (like MS Word). WP standardized
on the WPD extension later when WP 6.0 came out. All the newer WP
apps are setup for the WPD file type.
This would be something you would have to bring up with the XMR
and MAILbus 400 folks. Maybe they have something you can configure
to give the attachments the extensions you want.
Bob
|
| 2031.2 | Still missingall the info | ZUR01::ASHG | Grahame Ash @RLE | Fri Mar 07 1997 10:00 | 21 |
| >This would be something you would have to bring up with the XMR
>and MAILbus 400 folks. Maybe they have something you can configure
>to give the attachments the extensions you want.
XMR and MB400 are X400-based products - and X.400 has no concept of filenames
and extensions. All they can carry are "tags", which are mapped between the
various systems e.g. XMR maps an Object-Identifier to a Message Router
Bodypart + a string (Format, Tag, whatever). It's then up to the mail servers
(Mailworks, ALL-IN-1) to translate between the tags and the file extensions.
(The exception to this is if the File Transfer Bodypart is used - but you need
something like Exchange or Lotus Message Switch to generate these. But these
filenames can not be carried through XMR and MR)
I'm still not sure what the exact path of the message is - so far we have:
TL Client (which?) - MW-VMS - MR - XMR - MB400-MTA - ??? - Wordperfect?
Or not?
grahame
|
| 2031.3 | Please draw me a picture! | ZUR01::ASHG | Grahame Ash @RLE | Fri Mar 07 1997 10:15 | 17 |
| Ah, I've just been back to Note 3079 in the mailbus_400 conference, where this
saga started. And Lotus Message Switch is involved.
Erich,
Please describe the path the message is taking when it fails. So far, you've
just given a list of products, and it's not always clear how they're
connected.
For instance, if WP connects to the LMS, which sends to the MB400 MTA, then
the MTA will (if you have set up the Content Information correctly in the
directory) use the File Transfer Bodypart Mapping Table to map the file
extension (if it's present) to an object identifier. This identifier is then
mapped by XMR to a DECBODY7 bodypart + Tag. This Tag is then mapped by
Mailworks (I think) back to a filename.
grahame
|
| 2031.4 | FTB Mapping Table ! | OSITEL::rtont2.rto.dec.com::rtoms1::schaefere | SI-Office | Mon Mar 10 1997 06:47 | 18 |
| Hi
thanks for the inputs so far. I think the
File Transfer Bodypart Mapping Table to map the file
extension (if it's present) to an object identifier is exactly what
I have to look at. Indeed we use File Transfer Body part and
the route is
Teamlinks V 2.5 with WordPerfect V 5.2 on the same PC,
WP is attached to a mail,
mail is send via MW/VMS to MR -> XMR -> MTA -> Lotus LMS ->
a gateway -> MS Mail
and the attachment arrives at "attach.dat"
The same applies for the reverse route.
regards, Erich
|