| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2148.1 | LinkWorks object should be created | UTROP1::kampenp.uto.dec.com::SCHIMMEL_B | | Fri Feb 28 1997 09:32 | 25 |
| Hi,
When LinkWorks (external mail) sends mail to someone (possibly outside
LinkWorks), always a copy of the data of the LinkWorks objects is made. The
file names used (for the copy) are: d<seq-nr>.<suffix>. The original file
names (as kept in LinkWorks) are even more funny (something like
00000000/00/01/02/AB). So the 2nd part of .-1 seems to make sense.
When LinkWorks external mail receives mail in MIME format, the MIME message
is decoded (of course only when using the external mail kit which supports
MIME) and information is prepared for LinkWorks so that LinkWorks will be
able to create LinkWorks objects. These LinkWorks objects will get names.
The name of an object is derived from information present in a MIME
sub-header (if any) or it is derived from the Subject (using sequence nr +
subject as name for the object) or some default rule if this rule cannot be
followed.
Given your remark in .-1 I don't see precisely what you are saying.
o Don't you get LinkWorks objects ?
o Do these LinkWorks objects have funny names ?
Please give an example when the explanation above doesn't give you enough
information.
Regards, Berd Schimmel
|
| 2148.2 | Names of attachements are incorect | BRADEC::bpc054.mil.brc.dec.com::takacs | | Fri Mar 14 1997 15:23 | 47 |
| Hi Berd,
sorry for delay, but I was not in. When I send attachement from LinkWork to
Exchange, in Exchange I get names of attached files like d0000001.bmp,
d0000002.xls. When I send message from Exchaneg to LinkWorks, I get names
of attachements Note, Document, Document, although in the MIME header there
are names of attached files. It looks very very strange. I post also MIME
header (first LNX file in the envelope).
From daemon Fri Mar 14 15:18:36 1997
Received: from demo1.mil.brc.dec.com by urpin.mil.brc.dec.com;
(5.65v3.2/1.1.8.2/28Jan97-0158PM)
id AA01469; Fri, 14 Mar 1997 15:18:35 +0100
Received: by demo1.mil.brc.dec.com with SMTP (Microsoft Exchange Server
Internet Mail Connector Version 4.0.993.5)
id <[email protected]>; Fri, 14 Mar 1997
15:17:10 +0100
Message-Id:
<c=US%a=_%p=Digital%[email protected]>
From: Roland Takacs <[email protected]>
To: 'roland na urpine' <[email protected]>
Subject: 222
Date: Fri, 14 Mar 1997 15:17:07 +0100
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version
4.0.993.5
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----
=_NextPart_000_01BC308A.C9514D60"
------ =_NextPart_000_01BC308A.C9514D60
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
------ =_NextPart_000_01BC308A.C9514D60
Content-Type: application/msword; name="AltaVista~Mail.doc"
Content-Transfer-Encoding: base64
------ =_NextPart_000_01BC308A.C9514D60
Content-Type: application/msword; name="AltaVista~Search.doc"
Content-Transfer-Encoding: base64
------ =_NextPart_000_01BC308A.C9514D60--
Thanks
Roland
|
| 2148.3 | Rules selecting Object Name (External Mail) | UTROP1::16.197.208.129::VISSER_J | Joop Visser @ UTO | Tue Apr 01 1997 11:11 | 40 |
| Answer from Berd,
Rules are followed from low to high. So when a name is
defined via rule 1, rule 2 (and higher) are not applicable.
1. When LinkWorks specific information is present (containing the name of an
object), the received LinkWorks will get this name.
2. When a MIME message is received, a body part header can contain
the "Content-Description" header line. When present, the information of
this header line is used as name for the LinkWorks object.
3. An option can be specified in the external mail configuration file in the
X400 block (so after "BEGIN X400") which activates another rule (ALSO for
MIME although it is in the X400 block !).
See option "ObjectName: Yes | No". When "Yes" is specified
and a Subject is present in the message (and no name for the LinkWorks
object is known yet), a name is generated consisting of:
[sequence-number] <Subject>
Example: "[1] subject text from AltaVista mail"
Sequence-number is increased for every body part.
4. If no name can be determined by the external mail component (using rules
1-3), the received objects are imported by LinkWorks and it generates a
default name (which is the name of the object class).
My first suggestion to you is to investigate if Exchange can add
"Content-Description" fields.
If not, then switch to using rule 3 (set option "ObjectNames: Yes"). We do
not intend to extend the above scheme with another rule (using filenames or
other pieces of information from the incoming mail message).
In your specific example it looks as if the filenames contain
some relevant information. And the subject is funny.
Use a more descriptive subject as in the example in rule 3 above.
Joop Visser
|