Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Re: LISTSERV Line Monitor
From:
Turgut Kalfaoglu <TURGUT@TREARN>
Reply To:
Revised LISTSERV forum <LSTSRV-L@CEARN>
Date:
Wed, 21 Feb 90 16:51:56 TUR
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
 
Ferhat: No, gateways have a tendancy to corrupt the binary files - such
files need to be encoded with a special method which reduces the
binary range of these files (so that for example, instead of using ASCII
0->255, it uses only '0'->'F', like the HEX option)..
 
UUENCODE does this, it 'stretches' each 3-byte piece into four, and
XXENCODE is similar, except XXENCODE uses another character set which
is at some newer implementations, is given up front - so that even if
all the (let's say) '@' characters in the file get changed to something
else, the receiving side can figure this out from the 'ruler' on top
of the file.. HEX is more brute-force, and results in a larger file,
and it turns each byte into two hex bytes.. (Encoders for VM are
available from LISTSERV@TREARN, decoders from TRICKLE@TREARN!)
Regards, -turgut
 

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV