[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference utrop1::linkworks_v3

Title:	LinkWorks V3.0 Notes Conference
Notice:	LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:	tacklr.apd.dec.com::TACK_Lm::TACK_L

Created:	Tue Jun 28 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2269
Total number of notes:	8338

2243.0. "MIME questions" by ATZIS3::au8034.aui.dec.com::Huschka () Wed May 21 1997 15:07

Hi,

two questions regarding LNX-MIME Integration

  - Is it possible to define a default EXTFORMATID (or CLASS) when receiving 
    a MIME Mail w�tch no corresponding <ext>,<content type> entry in mimetags.txt.
    For X400 Mails there is a "UnknownTag" option - Why not for MIME ??

  - Is there a way to decode the subject string (happens if subject contains
    e.g. Umlaute )

Thank's in advance for your response.

regards

Andreas Huschka

T.R Title User Personal
Name Date Lines

2243.1 UTROP1::utoschimmel1.uto.dec.com::SCHIMMEL_B Wed May 21 1997 16:26 15

T.R	Title	User	Personal Name	Date	Lines
2243.1		UTROP1::utoschimmel1.uto.dec.com::SCHIMMEL_B		`Wed May 21 1997 16:26`	15
	Andreas, When a non-defined content-type/sub-type is received in a MIME message (i.e., not defined in mimetags.txt), the content-type/sub-type is used as the format definition. Since this format definition is unknown to LinkWorks, you will get an event and a Note object is created. The alternative could have been to use the "UnknownTag: <something>" definition like is done for X.400. The consideration has been that this situation should not occur for the majority of the attachment types. Most of them are defined in mimetags.txt and certainly those which allow LinkWorks to create a suitable object class. With respect to the Subject: no encoding during send, no decoding during receive. Regards, Berd Schimmel

Andreas,

When a non-defined content-type/sub-type is received in a MIME message (i.e., 
not defined in mimetags.txt), the content-type/sub-type is used as the format 
definition.  Since this format definition is unknown to LinkWorks, you will 
get an event and a Note object is created.  The alternative could have been 
to use the "UnknownTag: <something>" definition like is done for X.400.  The 
consideration has been that this situation should not occur for the majority 
of the attachment types.  Most of them are defined in mimetags.txt and 
certainly those which allow LinkWorks to create a suitable object class.

With respect to the Subject: no encoding during send, no decoding during 
receive.

Regards, Berd Schimmel