- From: ONIME EHIMIKA OHIREIME <onime@ictp.trieste.it>
- Date: Thu, 26 Aug 1999 10:45:17 +0200 (MET DST)
- To: "Lena [Kiev.Ukraine]" <lena@ganimed.freenet.viaduk.net>
- cc: www-email-discuss@w3.org
Well, I was thinking of cleaning up the mailer section of www4mail.... I will look into this... At least on www4mail@wm.ictp.trieste.it, it should now be sending single lines between (Attachment headers & Attachment body). Thanks Clement Onime On Wed, 25 Aug 1999, Lena [Kiev.Ukraine] wrote: > > On Tue, 24 Aug 1999, Dietmar P. Schindler wrote: > > > > today I received the base64 encoded GIF file > > > > > > http://195.82.89.133/magazin/templates/main_p/gewinnspiel/winner_mitmach.gif > > > > > > that neither netscape nor xv could display (of course after decoding). I > > > looked into it and saw an extra CR/LF pair at the beginning of the file > > > before the characters GIF with which it should actually begin. > > > Could www4mail have incorrectly inserted the CR/LF? > > www4mail inserts one extra CR/LF pair (or single CR or LF - my mailer > conceals such details from me) at very beginning of body of each letter. > If the letter contains text, HTML or uuencoded file then it's not problem. > But if the letter contains base64-encoded file then some mailers/decoders > in some circumstances may transfer this empty line to decoded file. > One of my stand-alone base64 decoders sees only empty line and creates > empty output file, ignoring base64-encoded file following the empty line. > Look to "document source" of a letter from www4mail with a base64-encoded > binary file, you'll see two empty lines between header and body instead > of one. >
Received on Thursday, 26 August 1999 04:50:49 UTC