File: intro.html

package info (click to toggle)
emil 2.1.0-beta9-9
  • links: PTS
  • area: main
  • in suites: potato
  • size: 1,152 kB
  • ctags: 587
  • sloc: ansic: 10,369; yacc: 412; makefile: 326; sh: 172
file content (62 lines) | stat: -rw-r--r-- 2,701 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
<HEAD>
<TITLE>EMIL version 2 TUTORIAL</TITLE>
</HEAD>
<BODY>

                                             
<H1>TUTORIAL FOR EMIL VERSION 2.1
</H1>
<EM>Written by Martin Wendel, ITS, Uppsala university.
Martin.Wendel@its.uu.se
</EM>
<HR>
<A HREF=why.html><IMG ALIGN=MIDDLE SRC=arrow_right3.gif></A><A HREF=main.html><IMG ALIGN=MIDDLE SRC=arrow_up2.gif></A>
<BODY>
<H2>INTRODUCTION</H2>
<P>Message transport is one of the major uses of the Internet today. Although the 
mechanisms of transport itself may vary, the format of what is being transported 
varies even more. Emil is a tool that gives the opportunity to bridge these format 
variations. Emil does not deal with how messages are sent, therefore the transport 
mechanisms are left out in favour of the message format in the rest of this 
document.
<P>RFC822 is a common base that defines the format of an Internet Message.
 Unfortunately this does not mean that all Mail User Agents (MUA's) conforming to 
RFC822 will interoperate satisfactory. Messages may very well be incompatible 
while still conforming to RFC822 <A HREF="rfc822.html">[RFC822]</A>. RFC822 is just a common base and does not address 
compatibility of the data being sent, MIME 
<A HREF="rfc1521.html">[RFC1521]</A>and
<A HREF="rfc1522.html">[RFC1522]</A> is an effort to do just that. 
While RFC822 defines the format of the message itself, MIME
 defines the format of the contents of the message (Internet messages not conforming 
with MIME typically has a fairly unstructured content). Until MIME is widely 
used these incompatibilities will remain. The intermediate cure for this is the tool Emil.
<P>Emil acts as a filter tool and transforms messages between message formats. It can act as 
a manual filter or it can be used by a Mail Transfer Agent (MTA) like sendmail. It is often 
argued that MTA's should only alter messages when they act as gateways between 
heterogeneous networks. I argue that a MTA may very well transform a message 
when passing it between heterogeneous logical communities (or networks) of MUA's. 
These two arguments are really analogous. 
<P>Using Emil, heterogeneous MUA networks can act as homogenous. This works both 
ways; A single user can make the rest of the world act homogenous looking from his/her MUA.

<hr size="4" noshade>
<ADDRESS>
<table WIDTH="95%">
<td>
March 1996<p>
<B>ITS Uppsala university</B><BR>
Box 887<BR>
751 08 Uppsala<BR>
SWEDEN<P>
</td>
<td ALIGN="right" VALIGN="middle">
<a href="mailto:Martin.Wendel@its.uu.se">Martin Wendel</a>
</td>
<td ALIGN="left" VALIGN="middle">
<a href="mailto:Martin.Wendel@its.uu.se">
<IMG border="0" SRC="binpobox.gif" ALT="E-Mail: "></a>
</td>
</table>
</ADDRESS>
</body>
</html>