[Prev][Next][Index][Thread]
Changes since last version of comp.mail.mime FAQ
-
Subject: Changes since last version of comp.mail.mime FAQ
-
From: mime-faq@ics.uci.edu (MIME FAQ maintainer)
-
Date: Mon, 8 Jan 1996 07:38:43 GMT
-
Followup-To: comp.mail.mime
-
Newsgroups: comp.mail.mime
-
Organization: Irvine Compiler Corp., Irvine, California, USA
-
Reply-To: mime-faq@ics.uci.edu (MIME FAQ maintainer)
-
Sender: usenet@irvine.com (News Administration)
This posting consists of diffs between the MIME FAQ for September,
1995 and the most recently posted version for January, 1996.
[ Part 0 ]
No changes.
[ Part I ]
*** - Mon Jan 1 15:53:34 1996
--- mime1 Mon Jan 1 15:51:40 1996
***************
*** 13,28 ****
Archive-Name: mail/mime-faq/part1
! Version: $Id: mime1,v 3.14 1995/09/03 06:14:01 jsweet Rel $
Posting-Frequency: monthly
- --
==========================================================
comp.mail.mime frequently asked questions list (FAQ) (1/3)
==========================================================
Part 1: Answers to Frequently Asked Questions about MIME
- ~~~~~~
--
Overview
--- 13,26 ----
Archive-Name: mail/mime-faq/part1
! Version: $Id: mime1,v 3.14 1995/09/03 06:14:01 jsweet Rel jsweet $
Posting-Frequency: monthly
==========================================================
comp.mail.mime frequently asked questions list (FAQ) (1/3)
==========================================================
Part 1: Answers to Frequently Asked Questions about MIME
--
Overview
***************
*** 41,73 ****
marked with '+'.
Contents
! ~~~~~~~~
Part 1: Answers to Frequently Asked Questions about MIME (this file)
========================================================
1) Introduction
1.1) Authorship
1.2) Conventions
! ! 1.3) Where can I get the comp.mail.mime FAQ?
2) What is MIME?
2.1) Introduction
2.2) MIME features that may or may not be present
! 2.3) Help! I got a message in MIME format--how do I decode it?
! ! 2.4) Further information
2.5) MIME glossary
! 2.6) Newsgroups and mailing lists
3) Miscellaneous questions
3.1) What can I use to display MIME messages?
3.2) What's "text/enriched"?
! 3.3) What about security issues?
3.4) So, does MIME introduce any new security problems?
! 3.5) What about a group 3 facsimile encoding?
3.6) Should I always use external body parts to save space?
3.7) What mail servers can I reference?
3.8) Can I interwork between MIME and X.400?
3.9) Why does MIME define base64 instead of using uuencode?
3.10) How can I use uuencode with MIME?
4) MIME information available from the Internet
4.1) Anonymous FTP
--- 39,73 ----
marked with '+'.
Contents
! --------
Part 1: Answers to Frequently Asked Questions about MIME (this file)
========================================================
1) Introduction
1.1) Authorship
1.2) Conventions
! 1.3) Where can I get the comp.mail.mime FAQ?
2) What is MIME?
2.1) Introduction
2.2) MIME features that may or may not be present
! ! 2.3) Help! I got a message in MIME format--how do I decode it?
! 2.4) Further information
2.5) MIME glossary
! ! 2.6) Newsgroups and mailing lists
3) Miscellaneous questions
3.1) What can I use to display MIME messages?
3.2) What's "text/enriched"?
! ! 3.3) What about security issues?
3.4) So, does MIME introduce any new security problems?
! ! 3.5) What about a group 3 facsimile encoding?
3.6) Should I always use external body parts to save space?
3.7) What mail servers can I reference?
3.8) Can I interwork between MIME and X.400?
3.9) Why does MIME define base64 instead of using uuencode?
3.10) How can I use uuencode with MIME?
+ + 3.11) Does Microsoft Mail support MIME?
+ + 3.12) Can I do MIME on a (pick one) PC/Macintosh/Envoy/Whatever?
4) MIME information available from the Internet
4.1) Anonymous FTP
***************
*** 78,84 ****
5) Published books and articles
6) MIME based relays for commercial mail services
! 6.1) Large national or international providers
6.1.1) ATTMAIL
6.1.2) CompuServe
6.1.3) RadioMail
--- 78,84 ----
5) Published books and articles
6) MIME based relays for commercial mail services
! ! 6.1) Large national or international providers
6.1.1) ATTMAIL
6.1.2) CompuServe
6.1.3) RadioMail
***************
*** 86,100 ****
Part 2: MIME products (posted separately)
=====================
! 7) Freely available MIME packages
! ! 7.1) Libraries and Patches
! ! 7.2) Conversion tools and extension packages
! 7.3) Mail user agents and transport systems
! 8) Commercial MIME packages
9) Packages for MIME in USENET
! 9.1) Introduction
9.2) News readers and transports with MIME support
Part 3: Advanced topics (posted separately)
--- 86,100 ----
Part 2: MIME products (posted separately)
=====================
! ! 7) Freely available MIME packages
! 7.1) Libraries and Patches
! 7.2) Conversion tools and extension packages
! 7.3) Mail user agents and transport systems
! 8) Commercial MIME packages
9) Packages for MIME in USENET
! ! 9.1) Introduction
9.2) News readers and transports with MIME support
Part 3: Advanced topics (posted separately)
***************
*** 101,109 ****
=======================
10) Information
! 10.1) MIME-relevant RFCs and other standards
! ! 10.2) MIME types
! 10.2.1) List of registered MIME types
! 10.2.2) List of known unregistered MIME types
10.3) Internet Engineering Task Force (IETF) working groups
11) Developers' FAQs
--- 101,109 ----
=======================
10) Information
! 10.1) MIME-relevant RFCs and other standards
! 10.2) MIME types
! 10.2.1) List of registered MIME types
! ! 10.2.2) List of known unregistered MIME types
10.3) Internet Engineering Task Force (IETF) working groups
11) Developers' FAQs
***************
*** 115,121 ****
11.6) Why doesn't MIME include a mechanism for compression?
11.7) What's this Content-Disposition header?
! ! 12) Acknowledgements
13) Permissions
--
--- 115,121 ----
11.6) Why doesn't MIME include a mechanism for compression?
11.7) What's this Content-Disposition header?
! 12) Acknowledgements
13) Permissions
--
***************
*** 209,217 ****
original document, the MIME FAQ maintainer probably can't fix it
directly.
! In particular, RFC references in the Ohio State version may still
point to pages saying "they've been moved". This is beyond the
! control of the MIME FAQ maintainer.
- If you are reading this FAQ via some fixed medium such as hardcopy
--- 209,217 ----
original document, the MIME FAQ maintainer probably can't fix it
directly.
! ***In particular, RFC references in the Ohio State version may still
point to pages saying "they've been moved". This is beyond the
! control of the MIME FAQ maintainer.***
- If you are reading this FAQ via some fixed medium such as hardcopy
***************
*** 219,227 ****
instead.
! There is also a "meta-FAQ", posted monthly, that attempts to help with
! any special problems that you may have with reading MIME messages,
! such as this one.
--
--- 219,227 ----
instead.
! There is also a Part 0, the "Meta-FAQ", posted monthly, that attempts
! to help with any special problems that you may have with reading MIME
! messages, such as this one.
--
***************
*** 246,252 ****
- other messages (reliably encapsulated)
- tar files
- PostScript
! - FTPable file pointers
- other stuff
MIME supports not only several pre-defined types of non-textual
--- 246,252 ----
- other messages (reliably encapsulated)
- tar files
- PostScript
! - pointers to FTPable files
- other stuff
MIME supports not only several pre-defined types of non-textual
***************
*** 347,354 ****
decoding a MIME message, some of which are enumerated in part 2
of this FAQ.
! --------------------------------
2.4) Further information
A nice overview of the MIME specification by Mark Grand is available
--- 347,393 ----
decoding a MIME message, some of which are enumerated in part 2
of this FAQ.
! If you receive some content type that your mail user agent can't
! already handle, then you'll have to modify your global or personal
! mail system configuration to deal with it--if you can. It's not
! always possible, short of spending a year of your life to write the
! required programs. But look in the MIME FAQ to see if someone already
! has a tool or product that will decode the content type that you're
! attempting to handle. (Also check the MIME Meta-FAQ, go
! treasure-hunting on the net, and so on.)
!
! Here your faithful MIME FAQ maintainer feels the need to rant a bit on
! the subject of poor MIME usage and concomitant MIME decoding problems.
+ MIME capability doesn't automatically confer interoperability with the
+ rest of the world. Any random data can be mapped into MIME one way or
+ another, but some consideration needs to be given to the target
+ audiences.
+
+ Still, as Einar Stefferud likes to point out, "'Can' implies 'shall.'"
+ Platform or application-specific MIME data formats inevitably leak out
+ to the rest of the world, prompting instant FAQs: "Huh? Now how do I
+ make my mail reader handle _this_? And why was it sent to me?"
+
+ For creators of MIME messages, here are some preventive suggestions:
+
+ - Know how your attachments are going to be sent. Bear in mind
+ that what's reasonable for another Macintosh/Windows/Envoy/Whatever
+ recipient isn't necessarily reasonable for the rest of the world.
+ For example, sending that Microsoft Word document as an attachment
+ might not work out as well as you think it should.
+
+ - Be somewhat conservative about content types when sending to
+ mailing lists or other public forums, or consider using
+ multipart/alternative.
+
+ - Watch charset selections and content transfer encodings.
+ For example, some commonly used character sets on Apple Macintosh
+ computers use eight bits, not the standard seven bits, and also
+ contain a few non-standard glyphs.
+
+ --------------------------------
+
2.4) Further information
A nice overview of the MIME specification by Mark Grand is available
***************
*** 399,407 ****
part a piece of a MIME message containing some data type
PBM an image format
PEM Privacy Enhanced Mail
PostScript a popular page description language
RFC request for comments; proposed or standard Internet protocols
! SMTP Simple Mail Transport Protocol - RFC 821
text/enriched simple text markup language for MIME - RFC 1563
text/simplemail another (even simpler?) text markup language
URL WWW uniform resource locator; access-method://host/path
--- 438,447 ----
part a piece of a MIME message containing some data type
PBM an image format
PEM Privacy Enhanced Mail
+ PGP Pretty Good Privacy
PostScript a popular page description language
RFC request for comments; proposed or standard Internet protocols
! SMTP Simple Mail Transfer Protocol - RFC 821
text/enriched simple text markup language for MIME - RFC 1563
text/simplemail another (even simpler?) text markup language
URL WWW uniform resource locator; access-method://host/path
***************
*** 439,445 ****
a message body containing, e.g. "send info-mime-uk 08-1993".
! - The archive ftp://ftp.ora.com/pub/usenet/comp.mail.mime stores
articles in three formats: by subject, by article number, and by
month. See the README file for more information.
--- 479,485 ----
a message body containing, e.g. "send info-mime-uk 08-1993".
! - The archive ftp://ftp.ncd.com/pub/usenet/comp.mail.mime stores
articles in three formats: by subject, by article number, and by
month. See the README file for more information.
***************
*** 500,520 ****
Both users and administrators should be aware that ordinary Internet
and UUCP e-mail is not secure. No authentication, confidentiality, or
data integrity properties are provided in SMTP, RFC 822, or MIME.
! Persons desiring any or all of those security properties in their e-mail
! should look into the use of Privacy-Enhanced Mail (PEM). At least one
! no-cost implementation of PEM is available in the US and Canada.
! There are also a number of implementations being developed in Europe
! (hopefully these will not suffer the same restrictions on export).
! PEM will (eventually) be integrated with MIME. See
! draft-ietf-pem-mime-03.txt
! for the latest work on this.
!
! A system providing similar functionality to PEM implementations is
! PGP. PGP is an implementation, not a specification, and it does not
! carry the blessing of the IETF, or any other body. It is, however,
available at no cost throughout the world (although its status with
respect to certain US patents is dubious). Caveat emptor.
--- 540,563 ----
Both users and administrators should be aware that ordinary Internet
and UUCP e-mail is not secure. No authentication, confidentiality, or
data integrity properties are provided in SMTP, RFC 822, or MIME.
! Persons desiring any or all of those security properties in their
! e-mail should look into the use of Privacy-Enhanced Mail (PEM). Other
! forms of e-mail security, such as PGP (Pretty Good Privacy), are also
! available.
! At least one no-cost implementation of PEM is available in the US and
! Canada. There are also a number of implementations being developed in
! Europe (hopefully these will not suffer the same restrictions on
! export).
! See also the following RFCs:
! RFC 1421 through RFC 1424 - PEM
! RFC 1847 - Security Multiparts for MIME
! RFC 1848 - MIME Object Security Services
! A system providing similar functionality to PEM implementations is PGP
! PGP is an implementation, not a specification, and it does not carry
! the blessing of the IETF, or any other body. It is, however,
available at no cost throughout the world (although its status with
respect to certain US patents is dubious). Caveat emptor.
***************
*** 534,539 ****
--- 577,598 ----
contains, among other useful information, an unflinching report
on how PGP came to be.
+ [ Michael Elkins <elkins@aero.org> 18-Dec-1995 ]
+
+ If you are interested in joining the discussion of issues on a standard
+ for use of PGP to encrypt/sign Internet e-mail messages using MIME, you
+ may be interested in this list. I highly encourage everyone who is
+ working on incorporating PGP into a mail client to join, even if you
+ don't participate in the discussion, since it will be the best source of
+ information about the developing proposed standard.
+
+ To join the list, send mail to
+ pgp-mime-request@lists.uchicago.edu
+ with a subject of "subscribe".
+
+ Submissions should be sent to
+ pgp-mime@lists.uchicago.edu
+
{ This section needs additional information, URLs, etc. }
--------------------------------
***************
*** 564,579 ****
3.5) What about a group 3 facsimile encoding?
! It is rumored that there was an attempt to include G3 FAX in the
! original MIME specification, but that it was impossible for the
! authors of the MIME specification to gain a consensus on how to encode
! the data. So G3 FAX has been left for a future MIME implementation.
! But you can always define your own body part.
! Here are some snippets relevant to MIME and FAX.
! The MIME-MHS documents define a G3Fax body part that is conformant
! with the X.400 G3Fax definition.
[ Stuart Lynne <sl@wimsey.com> 30-Dec-1992 ]
--- 623,638 ----
3.5) What about a group 3 facsimile encoding?
! There is an X.400-conformant G3 facsimile type for MIME, "image/g3fax".
! The specifications are in the MIME-MHS documents.
! { What current commercial and non-commercial software packages implement
! viewers or generators for the image/g3fax content type per se, as opposed
! to fax image rendering for other MIME content types? And which of these
! interoperate with the remote printing experimental domain "TPC.INT"? }
! The early MIME specification did not include a G3 facsimile type, but
! there were some efforts along these lines anyway:
[ Stuart Lynne <sl@wimsey.com> 30-Dec-1992 ]
***************
*** 598,605 ****
multipart facilities, and so forth. PMDF-FAX was developed with MIME
in mind from the outset.
! --------------------------------
!
3.6) Should I always use external body parts to save space?
Not necessarily. In many cases, for example, at the ends of UUCP
--- 657,666 ----
multipart facilities, and so forth. PMDF-FAX was developed with MIME
in mind from the outset.
! See also: news:comp.mail.misc - "FAQ: How can I send a fax from the Internet?"
!
! --------------------------------
!
3.6) Should I always use external body parts to save space?
Not necessarily. In many cases, for example, at the ends of UUCP
***************
*** 710,715 ****
--- 771,794 ----
could be useful.
--
+ 3.11) Does Microsoft Mail support MIME?
+
+ [ Ned Freed <ned@sigurd.innosoft.com> 30-Nov-1995 ]
+
+ Microsoft Mail doesn't provide MIME support. Microsoft Exchange may,
+ although it isn't clear what form this support will take.
+
+ There is a variety of solutions available from various third parties.
+ I'd recommend that you peruse the MIME FAQ for this list -- it should
+ suggest several starting points.
+ --
+
+ 3.12) Can I do MIME on a (pick one) PC/Macintosh/Envoy/Whatever?
+
+ See section 2.3.
+
+ --
+
4) MIME information available from the Internet
-----------------------------------------------
***************
*** 805,812 ****
sought out, according to preference.
One chapter of the book is devoted to MIME.
-
- Articles and Papers
[ Daniel Glazman <Daniel.Glazman@der.edf.fr> 27-Oct-94 ]
--- 884,891 ----
sought out, according to preference.
One chapter of the book is devoted to MIME.
+
- Articles and Papers
[ Daniel Glazman <Daniel.Glazman@der.edf.fr> 27-Oct-94 ]
***************
*** 830,845 ****
6.1) Large national or international providers
! { Lots missing here. Anyone got any info these, or any others? }
! { America On-line }
! { Dialog }
! { Genie }
! { MCI Mail }
! { Sprintmail }
!
! --------------------------------
!
6.1.1) ATTMAIL
[ Steve <atthelp@attmail.com> 30-Dec-1992 ]
--- 909,921 ----
6.1) Large national or international providers
! { There's lots missing here, and this information is aging. If anyone
! has updated information about any of the various mail service providers
! listed here, or any others, then send 'em to the MIME FAQ Maintainer
! address <mime-faq@ics.uci.edu>. }
! --------------------------------
!
6.1.1) ATTMAIL
[ Steve <atthelp@attmail.com> 30-Dec-1992 ]
***************
*** 898,911 ****
to support them.
! { Should coordinate this with the global e-mail list that is posted to }
! { comp.mail.misc. }
!
! --------------------------------
!
6.2) Local and regional providers
{ Any info? Should coordinate this with e.g. the PDIAL list. }
--
End of Part 1
--- 974,985 ----
to support them.
! --------------------------------
!
6.2) Local and regional providers
{ Any info? Should coordinate this with e.g. the PDIAL list. }
+
--
End of Part 1
[ Part II ]
*** - Mon Jan 1 15:53:35 1996
--- mime2 Mon Jan 1 15:55:09 1996
***************
*** 13,19 ****
Archive-Name: mail/mime-faq/part2
! Version: $Id: mime2,v 3.14 1995/09/03 06:14:01 jsweet Rel $
Posting-Frequency: monthly
--- 13,19 ----
Archive-Name: mail/mime-faq/part2
! Version: $Id: mime2,v 3.14 1995/09/03 06:14:01 jsweet Rel jsweet $
Posting-Frequency: monthly
***************
*** 51,58 ****
are discussed in section 9, although many of the packages in this
section also deal with USENET news.
! --------------------------------
7.1) Libraries and Patches
Name: c-client
--- 51,74 ----
are discussed in section 9, although many of the packages in this
section also deal with USENET news.
! Information for this section about MIME-capable software packages may
! be contributed by anyone, including the maintainers of the software.
! The FAQ maintainers look with favor on brief entries that are provided
! in the existing entry format, but it's fair simply to offer
! corrections or updated information. Notifications of obsolete or
! non-working URLs are also appreciated. Send new or updated entries to
! "mime-faq@ics.uci.edu"; posting to comp.mail.mime isn't necessarily
! sufficient.
!
! Readers should bear in mind that files whose names contain version
! numbers are often out of date by the time that you try to find them,
! so you may need to poke around in the parent directories to locate the
! latest versions.
+ See also: news:comp.mail.misc - "UNIX Email Software Survey FAQ"
+
+ --------------------------------
+
7.1) Libraries and Patches
Name: c-client
***************
*** 1007,1012 ****
--- 1023,1044 ----
For more information, see http://www.cac.washington.edu/pine/
+ Name: PP
+ Product: MTA
+ Platform: UNIX
+ Where: ftp://ftp.uninett.no
+ Author:
+ Contact:
+ Comments:
+
+ PP is an X.400/SMTP mailer and gateway. The last non-commercial
+ version was PP 6.0 (ca. 1992), which is still available for
+ downloading from some Internet sites; one is listed above. PP has
+ since been folded into a commercial software suite from the ISODE
+ Consortium; see the entry for "ISODE Consortium MTA", in section 8,
+ below.
+
+
Name: Tkmailto
Product: MUA
Platform: UNIX
***************
*** 1025,1030 ****
--- 1057,1083 ----
8) Commercial MIME software packages
------------------------------------
+ Information for this section about commercial MIME-capable software
+ packages may be contributed by anyone, including the firms offering
+ the packages. The FAQ maintainers look with favor on _brief_ entries,
+ preferably as non-hypeful as possible, that are provided in the
+ existing entry format, but it's fair simply to offer corrections,
+ updated information, or unbiased consumer-oriented comments. Send new
+ or updated entries to the address "mime-faq@ics.uci.edu"; posting to
+ comp.mail.mime isn't necessarily sufficient.
+
+ This section is getting unwieldy, so all entries for commercial
+ products may be subject to being edited down to shorter summaries of
+ any available concrete information, along with contact information and
+ any relevant URLs.
+
+ Readers should bear in mind that files whose names contain version
+ numbers are often out of date by the time that you try to find them,
+ so you may need to poke around in the parent directories to locate the
+ latest versions.
+
+ --------------------------------
+
Name: Echelon
Product: MUA
Platform: NEXTSTEP
***************
*** 1186,1198 ****
Name: Internet Exchange for cc:Mail
Product: cc:Mail to SMTP/MIME Internet Mail Gateway
! Platform: MS-Windows
! Contact: sales@ima.com
! Phone: +1 415 871 4045
! Author: International Messaging Associates
! Comments:
! [ Tim Kehres <kehres@ima.com> 08-Dec-1993 ]
For cc:Mail users, Internet Exchange is the gateway of choice to
provide standardized full multimedia connectivity between cc:Mail
--- 1239,1252 ----
Name: Internet Exchange for cc:Mail
Product: cc:Mail to SMTP/MIME Internet Mail Gateway
! Platform: MS-Windows, Windows for Workgroups, Windows 95, Windows NT
! Contact: info@ima.com
! Phone: +852 2649-0135
! Fax: +852 2648-5913
! Author: International Messaging Associates Ltd
! Comments: Updated information available at http://www.ima.com
! [ Tim Kehres <kehres@ima.com> 08-Nov-1995 ]
For cc:Mail users, Internet Exchange is the gateway of choice to
provide standardized full multimedia connectivity between cc:Mail
***************
*** 1201,1227 ****
the Internet as well as connecting your own internal network to your
cc:Mail community.
! Internet Exchange for cc:Mail is the first SMTP to cc:Mail gateway
! that suports the full MIME Internet standard for exchanging rich
! media multipart messages. This means that your cc:Mail users can
! now exchange any attachment types with Internet based mail systems.
! By using the MIME standard, Internet Exchange for cc:Mail users
! will be assured future compatibility with other MIME compliant mail
! gateways.
To simplify administration and management, the Internet Exchange
! System Manager runs under Windows 3.1. On screen buttons provide
! administration access into the gateway operations. Managers can
! easily view and modify all gateway activity. Message routing is
! accomplished using any combination of host tables,Domain Name System
! (DNS) lookup, and default mail host routing.
Name: InterOFFICE
Product: Multiplatform MTA and gateway for most email systems
Platform: UNIX, OS/2, VAX/VMS, Tandem NonStop, NeXTSTEP, HP 3000, AS/400,
VM/370, Wang VS
Contact: info@bsw.com
Phone: +1 617 482 9898
Author: The Boston Software Works, Inc.
Comments:
--- 1255,1359 ----
the Internet as well as connecting your own internal network to your
cc:Mail community.
! Internet Exchange for cc:Mail Version 1.0 was the first SMTP to
! cc:Mail gateway that supported the full MIME Internet standard.
! This capability provided cc:Mail users with the ability to exchange
! any attachment types with Internet-based email systems.
+ Version 1.1 of Internet Exchange adds to these capabilities by
+ giving Macintosh and PC cc:Mail users the ability to transparently
+ exchange files across platforms. Internet Exchange now supports
+ all Apple Macintosh file handling standards including MacMIME,
+ AppleSingle, AppleDouble, and BinHex as well as MIME and UUENCODE
+ for PC's and UNIX.
+
+ Internet Exchange gives administrators complete flexibility with
+ address translations. Instead of forcing a fixed conversion format
+ between cc:Mail user names and Internet addresses, the user names
+ found in the cc:Mail post office directory are first grouped into
+ three parts: one first name, zero or more middle names, and one
+ last name. The administrator can combine them in an almost infinite
+ number of ways for the desired address translation between cc:Mail
+ user names and their Internet counterparts. This automation of
+ the address translation rules results in significant manpower
+ savings versus manually maintaining address translation tables.
+
+ Internet Exchange allows for the storage of information about
+ destination, or peer-based capabilities. These capabilities
+ include attachment types that can be decoded on the remote side,
+ as well as permissions related to the sending and receiving of
+ messages to the remote machine or domain. Internet Exchange
+ consults the peer database prior to sending messages to first
+ obtain permission to send messages to the destination, and then
+ to determine the appropriate attachment types and encoding
+ methods that can be successfully received by the remote system.
+
To simplify administration and management, the Internet Exchange
! System Manager runs under several Microsoft Windows based operating
! systems. On screen buttons provide rapid access to all the gateway
! operations which allow administrators to view and modify all gateway
! activity. Message routing is accomplished using any combination of
! host tables,Domain Name System (DNS) lookup, and default mail host
! routing.
+ Name: Internet Mail Center
+ Product: gateway
+ Platform: Microsoft Windows
+ Author: U.S. Computer
+ Contact: sales@usc.com
+ Phone: +1 408 446-0387
+ Fax: +1 408 446-1013
+
+ [ Will Estes <westes@usc.com> 15-Dec-1995 ]
+
+ Internet Mail Center is a complete solution for connecting
+ cc:Mail and Lotus Notes mail networks to the Internet, or
+ to a corporate TCP/IP protocol backbone network, using the
+ Simple Mail Transfer Protocol (SMTP). Using Internet
+ Mail Center, your mail users will be able to
+ communicate with other SMTP RFC-822-compliant mail systems
+ such as UNIX sendmail, IBM PROFs, and PC-based SMTP networks.
+
+ Designed from scratch to run under Microsoft Windows 3.1, and
+ with a Microsoft Windows/NT 3.51 version that runs as a true NT
+ service due out shortly, Internet Mail Center is a secure,
+ cost-effective solution for small and large companies that want
+ to connect to Internet using industry-standard operating systems.
+ Internet Mail Center supports cc:Mail, Notes, and stand-alone
+ SMTP mail server applications.
+
+ Internet Mail Center offers full support for the Multipurpose
+ Internet Mail Extensions (MIME) standard, which allows for
+ transport of 8-bit binary content over the Internet. With
+ MIME, your cc:Mail and Notes users can attach binary files
+ using the native cc:Mail and Notes user interfaces, without
+ the need for any additional steps to decode or prepare messages
+ bound for the Internet. Messages are sent and received using
+ the standard interfaces for file attachments, seamlessly, and
+ easily.
+
+ Internet Mail Center was designed for large heterogeneous
+ network environments with many concurrent senders and receivers
+ of mail. On simple '486-class hardware, Internet Mail Center
+ supports more than 60 concurrent SMTP transactions.
+
+ Internet Mail Center performs many of the same functions that
+ UNIX sendmail does, allowing a system administrator to rewrite
+ user and host addresses for incoming and outgoing mail.
+
+ For More Information Contact:
+
+ U.S. Computer
+ [ contact information above ]
+
+
Name: InterOFFICE
Product: Multiplatform MTA and gateway for most email systems
Platform: UNIX, OS/2, VAX/VMS, Tandem NonStop, NeXTSTEP, HP 3000, AS/400,
VM/370, Wang VS
Contact: info@bsw.com
+ Contact: Kevin McCarthy <kpm@bsw.com>
Phone: +1 617 482 9898
Author: The Boston Software Works, Inc.
Comments:
***************
*** 1287,1292 ****
--- 1419,1490 ----
Austin, TX 78758-7631
+ Name: ISODE Consortium MTA
+ Product: MTA
+ Platform: UNIX
+ Contact: ic-info@isode.com
+ Where: http://www.isode.com/
+
+ [Steve Kille <S.Kille@isode.com> 26-Oct-1995]
+
+ The ISODE Consortium MTA is an X.400 and SMTP mailer, and a gateway
+ between these, so you can communicate with "both worlds". This
+ product is based on the older public domain PP MTA.
+
+ The Messaging products in the latest Isode Consortium Release
+ (3.0) include:
+
+ o MESSAGE TRANSFER AGENT (MTA). The MTA is designed for high
+ performance and operational robustness in a multi-protocol
+ environment. It supports X.400 (1984, 1988, 1992),
+ Internet Mail (SMTP/MIME), and X.400/MIME mapping according
+ to RFC 1327. There are extensive management features
+ including SNMP monitoring according to MADMAN (RFC 1566)
+ X.500 based routing according to the IETF MHS-DS specifications
+ (RFC 1801), authorisation, content conversion, and flexible
+ configuration.
+
+ o MESSAGE STORE. Provides multi-protocol access, using X.400
+ P3 and P7 and the Lightweight Message Access Protocol (LMAP)
+ which supports X.400 and Internet Messages. Integrated with the
+ MTA using P3 or co-resident access. Configuration uses
+ X.500, based on MHS-DS.
+
+ o MESSAGE AND DIRECTORY INTEGRATION APIs. Provision of X/Open
+ OSI integration APIs (MT, XDS and OM) and APIs for
+ integration using lightweight access protocols (LMAP, LDAP).
+
+ o X.509 SECURITY LIBRARIES. A suite of libraries providing
+ range of cryptographic algorithms (MD5, SHA, RSA, DSA) and
+ tools to form the basis of a Certification Authority based on
+ X.509(93) version 3 certificates.
+
+ o A TCL/TK-BASED CONFIGURATION GUI. This will be provided to
+ configure of MTAs and Message Stores. The configuration data is
+ held in the X.500 Directory.
+
+ o DOCUMENTATION. Administrator and Programmer manuals,
+ provided in Postscript and Frame (revisable) format.
+
+ The ISODE Consortium is a leading supplier of source technology for
+ open messaging, directory and security services. The primary focus is
+ on server technology, which includes management tools and integration
+ APIs. The ISODE Consortium has led long term activities to promote
+ open standards and has specified and promoted new standards where none
+ previously existed.
+
+ The ISODE Consortium makes its product available through membership,
+ which helps it to maintain its technology lead through commercial and
+ research partnership. The membership approach allows service
+ providers, OEMs, systems-integrators, government departments and
+ research organisations to avoid re-inventing non-differentiating core
+ technology.
+
+ The ISODE Consortium product is a source release. Binary Products
+ based on the technology are available from commercial vendors who are
+ members of the ISODE Consortium.
+
+
Name: Mail 3.3
Product: MUA
Platform: NEXTSTEP
***************
*** 1424,1429 ****
--- 1622,1649 ----
(look in the CD Extras folder).
+ Name: Marcel Lite
+ Product: MUA
+ Platform: Acorn RISCOS
+ Contact: ANT Sales <sales@ant.co.uk>
+ Phone: +44 1223 567808
+ Where: http://www.ant.co.uk/
+ Author:
+ Comments:
+
+ [ Nick Smith <nas@ant.co.uk> 17-Nov-1995 ]
+
+ Marcel Lite is a MUA for Acorn RISCOS that can decode, display and
+ compose mail with MIME, uuencode and btoa attachments. Mail can be off
+ local disc, or from an IMAP server over a TCP/IP stream.
+
+ It also operates threading news reading, reading from a local spool or
+ from an NNTP server.
+
+ Details including a datasheet and screenshots are available from:
+ http://www.ant.co.uk/
+
+
Name: Mi'Mail
Product: MUA
Platform: MS Windows 3.x
***************
*** 1640,1676 ****
Claremont, CA 91711
- Name: PP
- Product: MTA
- Platform: UNIX
- Contact: ic-info@isode.com (commercial version)
-
- [ "Harald T. Alvestrand" <Harald.T.Alvestrand@uninett.no> 22-Aug-1994 ]
-
- PP is an X.400 and SMTP mailer, and a gateway between these, so
- you can communicate with "both worlds".
-
- The latest and greatest version is the ISODE Consortium release,
- IC-R1, but this is no longer free. However, it is not expensive,
- either. The ISODE Consortium offers the source code to all
- Consortium members, and gives the right to sell products based on
- the code to commercial members.
-
- The PP included in Isode Consortium Release 1 (IC-R1) includes:
-
- - Conformance tested X.400/84, running over most stacks you care
- to name
- - X.400/88
- - X.400 (84 and 88) to SMTP gateways (RFC 1327 compliant)
- - SMTP, DECNET and UUCP support
- - P3File (Retix-like) message submission and delivery
- - Routing using X.500 (experimental)
- - MIME gatewaying support (MIME-MHS/HARPOON compliant)
- - SNMP monitoring
- - X.500 and file based distribution lists
- - Fax gateway supporting Panasonic, Fujitsu and Class 2 fax modems
-
-
Name: SecureMail
Product: MUA
Platform: AIX 3.2.5, SunOS 4.1, HP-UX 10.0, Open Desktop 3.0
--- 1860,1865 ----
***************
*** 1697,1705 ****
- Support for multi-media (MIME) attachments.
! SecureWare, Inc.
! 2957 Clairmont Road, Ste. 200
! Atlanta, GA 30329
Name: SMTPLINK 2.1
--- 1886,1894 ----
- Support for multi-media (MIME) attachments.
! SecureWare, Inc.
! 2957 Clairmont Road, Ste. 200
! Atlanta, GA 30329
Name: SMTPLINK 2.1
***************
*** 1837,1844 ****
Name: Z-Mail
Product: MUA
Platform: Unix
! Contact: info@z-code.com
! Author: Z-Code Software Corporation
Comments:
[ Carlyn M. Lowery <lowery@zen.z-code.com> 29-May-1993 ]
--- 2026,2035 ----
Name: Z-Mail
Product: MUA
Platform: Unix
! Contact: info@z-code.ncd.com
! Contact: http://www.ncd.com/
! Contact: ftp://ftp.ncd.com (downloadable demo version)
! Author: NCD Software Corp.
Comments:
[ Carlyn M. Lowery <lowery@zen.z-code.com> 29-May-1993 ]
***************
*** 1864,1886 ****
and transparently to the user. Z-Mail understands MIME-format
documents and is also compatible with Sun's multimedia Mailtool.
! Mac, MS-DOS, and MS-Windows versions, as well as native MIME
! support, are planned for this summer.
!
! For more information on Z-Mail, contact:
! Z-Code Software Corp.
! 4340 Redwood Hwy., Suite B-50
! San Rafael, CA 94903
! tel: (415) 499-8649
! fax: (415) 479-0448
! e-mail: info@z-code.com
!
! Also, you can anonymous-ftp a demo copy of Z-Mail from
! ftp://ora.com/pub/z-code/zmail/2.1/
! (The file you want is named zm.XXX.tar.Z, where XXX is
! your type of machine.) You'll need to call us after you do so we
! can send you an activation key.
--
9) MIME and USENET news
--- 2055,2065 ----
and transparently to the user. Z-Mail understands MIME-format
documents and is also compatible with Sun's multimedia Mailtool.
! [ Scott Hetherington <scott@z-code.ncd.com> 26-Oct-1995 ]
+ We have released several versions of Z-Mail for Windows and Z-Mail
+ for Macintosh (both MIME compliant).
+
--
9) MIME and USENET news
***************
*** 1894,1899 ****
--- 2073,2092 ----
A number of the mail user agents and tools discussed in section 7 also
handle USENET news.
+
+ Information for this section about MIME-capable USENET news software
+ packages may be contributed by anyone. The FAQ maintainers look with
+ favor on brief entries that are provided in the existing entry format,
+ but it's fair simply to offer corrections or updated information.
+ Send new or updated entries to the address "mime-faq@ics.uci.edu";
+ posting to comp.mail.mime isn't necessarily sufficient.
+
+ Readers should bear in mind that files whose names contain version
+ numbers are often out of date by the time that you try to find them,
+ so you may need to poke around in the parent directories to locate the
+ latest versions.
+
+ See also: news:comp.mail.misc - "FAQ: pointer to alt.usenet.offline-reader FAQs"
--------------------------------
[ Part III ]
*** - Mon Jan 1 15:53:35 1996
--- mime3 Mon Jan 1 14:38:16 1996
***************
*** 13,19 ****
Archive-Name: mail/mime-faq/part3
! Version: $Id: mime3,v 3.14 1995/09/03 06:14:01 jsweet Rel $
Posting-Frequency: monthly
--- 13,19 ----
Archive-Name: mail/mime-faq/part3
! Version: $Id: mime3,v 3.14 1995/09/03 06:14:01 jsweet Rel jsweet $
Posting-Frequency: monthly
***************
*** 88,93 ****
--- 88,100 ----
IAB standards or standards-track RFCs
+ RFC 1870 SMTP Service Extension for Message Size Declaration
+ RFC 1869 SMTP Service Extensions
+ RFC 1866 Hypertext Markup Language - 2.0
+ RFC 1864 The Content-MD5 Header Field
+ RFC 1848 MIME Object Security Services
+ RFC 1847 Security Multiparts for MIME: Multipart/Signed and
+ Multipart/Encrypted
RFC 1767 MIME Encapsulation of EDI Objects
RFC 1740 MIME Encapsulation of Macintosh files - MacMIME
RFC 1734 POP3 AUTHentication command
***************
*** 95,104 ****
RFC 1730 Internet Message Access Protocol - Version 4
RFC 1725 Post Office Protocol - Version 3
RFC 1700 Assigned Numbers { Way more than the title implies. }
- RFC 1653 SMTP Service Extension for Message Size Declaration
RFC 1652 SMTP Service Extension for 8bit-MIMEtransport
- RFC 1651 SMTP Service Extensions
- RFC 1544 The Content-MD5 Header Field
RFC 1502 X.400 Use of Extended Character Sets
RFC 1496 Rules for Downgrading Messages from X.400(88) to X.400(84)
when MIME Content-Types are Present in the Messages
--- 102,108 ----
***************
*** 113,123 ****
Other RFCs (Informational, Experimental, or Historical)
RFC 1838 Use of the X.500 Directory to support mapping between
X.400 and RFC 822 Addresses
RFC 1830 SMTP Service Extensions for Transmission of Large
and Binary MIME Messages
- RFC 1820 Multimedia E-mail (MIME) User Agent Checklist
RFC 1815 Character Sets ISO-10646 and ISO-10646-J-1
RFC 1806 Communicating Presentation Information in
Internet Messages: The Content-Disposition Header
--- 117,131 ----
Other RFCs (Informational, Experimental, or Historical)
+ RFC 1874 SGML Media Types
+ RFC 1873 Message/External-Body Content-ID Access Type
+ RFC 1872 The MIME Multipart/Related Content-type
+ RFC 1867 Form-based File Upload in HTML
+ RFC 1844 Multimedia E-mail (MIME) User Agent checklist
RFC 1838 Use of the X.500 Directory to support mapping between
X.400 and RFC 822 Addresses
RFC 1830 SMTP Service Extensions for Transmission of Large
and Binary MIME Messages
RFC 1815 Character Sets ISO-10646 and ISO-10646-J-1
RFC 1806 Communicating Presentation Information in
Internet Messages: The Content-Disposition Header
***************
*** 175,181 ****
and MIME/X.400 mapping tables.
A list of URLs follows for documents relevant to various media types.
! The media types are taken from the June, 1995 version of the
aforementioned media-types file, but the URLs below aren't necessarily
representative of the latest list of registered types. In general,
each <type> has a directory whose name has this form:
--- 183,189 ----
and MIME/X.400 mapping tables.
A list of URLs follows for documents relevant to various media types.
! The media types are taken from the December, 1995 version of the
aforementioned media-types file, but the URLs below aren't necessarily
representative of the latest list of registered types. In general,
each <type> has a directory whose name has this form:
***************
*** 211,219 ****
--- 219,229 ----
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/remote-printing
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/riscos
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/rtf
+ ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/sgml
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/slate
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/wita
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/wordperfect5.1
+ ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/x400-bp
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/application/zip
Audio types:
***************
*** 222,230 ****
--- 232,243 ----
Image types:
+ ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/image/cgm
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/image/jpeg
+ ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/image/g3fax
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/image/gif
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/image/ief
+ ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/image/naplps
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/image/tiff
Message types:
***************
*** 239,247 ****
--- 252,262 ----
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/multipart/alternative
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/multipart/appledouble
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/multipart/digest
+ ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/multipart/form-data
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/multipart/header-set
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/multipart/mixed
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/multipart/parallel
+ ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/multipart/related
Text types:
***************
*** 248,253 ****
--- 263,269 ----
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/text/enriched
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/text/plain
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/text/richtext
+ ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/text/sgml
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/text/tab-separated-values
Video types:
***************
*** 281,286 ****
--- 297,303 ----
LOCAL-FILE directly retrievable file
MAIL-SERVER request to a mail-based archive server
TFTP trivial file transfer protocol (RFC 1350)
+ content-id Message/External-Body Content-ID Access Type (RFC 1873)
Content transfer encodings:
***************
*** 331,336 ****
--- 348,354 ----
Application types:
+ application/pgp PGP
application/x-aiff Z-Mail: AIFF audio data
application/x-bcpio MHonArc: bcpio data
application/x-bitmap Z-Mail: X11 bitmaps
***************
*** 386,392 ****
Image types:
- image/g3fax X.400 mapping to/from g3-facsimile [RFC 1494]
image/x-cmu-raster MHonArc: CMU raster data
image/x-fits FITS files (see part 2 for an xv patch)
image/x-macpict TCP/Connect II, Iride: Macintosh PICT
--- 404,409 ----
***************
*** 415,421 ****
Text types:
! text/html MHonArc: WWW HTML
text/unknown Worldtalk
text/x-html MHonArc: WWW HTML
text/x-setext MHonArc: setext
--- 432,438 ----
Text types:
! text/html MHonArc: WWW HTML (See also RFC 1866)
text/unknown Worldtalk
text/x-html MHonArc: WWW HTML
text/x-setext MHonArc: setext
***************
*** 530,536 ****
Here are two sources:
! ftp://thumper.bellcore.com/pub/nsb/samples/
http://www-dsed.llnl.gov/documents/tests/email.html
Here're more sources:
--- 547,553 ----
Here are two sources:
! ftp://ftp.bellcore.com/pub/nsb/samples/
http://www-dsed.llnl.gov/documents/tests/email.html
Here're more sources:
[ End ]