home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!bu.edu!olivea!sgigate!sgiblab!swrinde!zaphod.mps.ohio-state.edu!darwin.sura.net!paladin.american.edu!auvm!INNOSOFT.COM!DAN
- From: DAN@INNOSOFT.COM (Daniel C. Newman)
- Newsgroups: bit.listserv.pmdf-l
- Subject: RE: ccMail question
- Message-ID: <01GRAWIDBFSI8ZI0JR@YMIR.CLAREMONT.EDU>
- Date: 19 Nov 92 01:08:11 GMT
- Sender: PMDF Distribution List <PMDF-L@IRLEARN.BITNET>
- Lines: 19
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Errors-to: epmdf@YMIR.BITNET
- X-Envelope-to: PMDF-L@IRLEARN.BITNET
- X-VMS-To: IN%"MAC@gvg47.gvg.tek.com"
- X-VMS-Cc: IPMDF
- MIME-version: 1.0
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
-
- > We are seeing some of the messages that PMDF leaves for ccMail to deliver
- > that contain what looks like some form of line wrapping that uses the ``=''
- > as the continuation character. There message also appear to have hex
- > quoting for some characters like maybe =20 means a space and maybe =9 means
- > a tab. I know this is a marginal description of the problem. I will
- > enclose a part of one of these message at the end of this message. What is
- > going on? Any help greatly appreciated.
-
- You're seeing line wrapping which uses the quoted printable MIME encoding.
- The "=xx" means "ASCII character with hex value xx". You see some =20 at
- the end of lines because PMDF wrapped the line and was now afraid that if
- it left a naked space at the end of the line some other mailer would strip
- it away. The =9 are tabs.
-
- Send your PMDF.CNF to service@innosoft.com and some sort of indication as
- to how this message originally entered PMDF. It probably came in on some
- channel with a "linelength" keyword specified.
-
- Dan
-