From: Bryan_Cardoza@Novell.COM (Bryan Cardoza)
Subject: NetWire by E-Mail
Followup-To: poster
Organization: Novell, Inc.
Date: Mon, 4 Jan 1993 22:12:22 GMT


Hi.

I've gotten permission from Novell's Tech. Support group to publish
this.  Hope it doesn't offend anybodies sensibilities....


--
Bryan Cardoza                        Internet:  Bryan_Cardoza@Novell.COM
NetWare Systems Group             NetWare MHS:  BRYAN@NOVELL
Novell, Inc.                            Voice:  +1-801-568-8653
Sandy, UT                                 FAX:  +1-801-568-8866


------------------------------------------------------------------------


		    Welcome to the Novell NetWire
		    Internet E-Mail Archive Server
			   at ns.Novell.COM


Introduction
------------

In order to serve our customers better, the portions of the NetWire
archives that we are able to offer through FTP and Gopher are now being
offered on a trial basis through a mail-server.

This service is provided on an experimental and unsupported basis in
order to determine interest.


Request Format
--------------

Mail-server requests should be sent to "mail-server@ns.Novell.COM."

Requests to the mail-server are taken from the body of the message.
Commands are prefaced with the "begin" command and closed with the
"end" command.

For example, if your message body contained the following:

	begin
	encoding base64
	send netwire/01/forum.zip
	end

The mail-server would respond by mailing you the forum.zip file from
netwire/01 encoded using the MIME "base64" encoding.

Responses from the mail-server are formatted according to the MIME
specifications (RFC1341).  All messages are of the "Multipart/Mixed"
content type with the first part being a run log of the mail-server and
subsequent parts being the requested text files (first) and non-text
files (last).

The default encoding for non-text files uses the UNIX uuencode(1)
command (Content-Transfer-Encoding: x-uue) for compatibility with
systems that may not have access to a MIME compliant user agent.  Users
with access to a MIME user agent (e.g. your favorite mailer with
metamail support) should probably select "base64" encoding.

When the message body exceeds (approximately) 2500 lines, the message
is split into multiple parts using the MIME "Message/Partial" content
type.  MIME-compliant mail user agents will be able to automatically
reconstruct these fragmented messages.


Command Summary
---------------

The mail-server supports the following commands:

begin           Start accepting commands.  All lines between "begin"
		and "end" are expected to be mail-server commands.

encoding <type> Set transfer encoding for non-text files to <type>.
		Currently supported types are "base64" which is
		specified by MIME and "x-uue" for UNIX uuencode
		encoding.  The default is "x-uue."

end             Stop accepting commands.

help            Send the help file.  This may also be retrieved by
		issuing "send mail-server/help" to the mail-server.
		The help file is also automatically sent when some
		errors are encountered.

index           Send the index file.  This may also be retrieved by
		issuing "send mail-server/index" to the mail-server.

path <addresss>	Set the return address for the mail reply to the address
		specified.

send <file>     Send the specified file.  File names must have either
		"mail-server/" or "netwire/" at the beginning.  Leading
		"/" characters will be stripped, and ".." or empty path
		components will be reduced.


Where to Make Comments
----------------------

Send trouble reports to Bryan_Cardoza@Novell.COM.

If you would like to see this become a permanent service, send your
request to Scott_Christensen@Novell.COM or contact your customer
service representative or account manager.



Last Update: 12/10/92 11:25:12

Newsgroups: comp.sys.novell