Received: from mn3.swip.net by westsound.com with SMTP
	id AA4110 ; Fri, 03 May 96 11:52:52 PST
Received: by mn3.swip.net with UUCP (8.6.8/2.01)
	id UAA28711; Fri, 3 May 1996 20:51:12 +0200
Received: by wsd.wline.se (WtrGate+ 0.90.p10 beta sn 61438)
          via UUCP; Fri, 03 May 96 20:30:20 GMT+1
          for John.Mudge@f111.ptmudge.westsound.com
Date: Fri, 03 May 96 19:38:48 GMT+1
From: ramon@wsd.wline.se (Ramon van der Winkel)
Message-ID: <wgcid$2$g200$h111$i15$j18a98e11@wsd.wline.se>
In-Reply-To: <wgcid$wgmid$24$3cwgcid$241$24g352$24h111$24kfidonet$24j3e0654db$kp
To: John.Mudge@f111.ptmudge.westsound.com
Subject: Buglet?
Organization: Waterline Software Development, Sweden


John Mudge wrote in a message to Ramon van der Winkel:

 JM> The process worked smoothly...except the resulting outgoing
 JM> message was 77K. Within WTRCONF I though I had set maximum
 JM> message size to 64K....but I am guessing that setting that
 JM> size only has an effect on incoming mail.  Should outgoing
 JM> file attach sizes be limited also just in case the other end
 JM> cannot handle large ones or are we btter off the way it
 JM> seems to be working now?

You mean that it encoded an attached a file to somebody in FTN style? And
that message was bigger than 77Kb?

Why did it encode an attached file for an FTN style user? It shouldn't do
that.

Mails can be as big as you want them: no limit there.

The encoding stuff is not related to the code that exports a message to a
certain user and then splits it.

The biggest problem left is when importing: before the file is extracted,
the number of split parts is calculated... I have to fix this soon.

Ramon

-- 
============================================================
Ramon van der Winkel  WaterLine Software Development, Sweden
ramon@wsd.wline.se                 postmaster@admin.wline.se

Home of WaterGate! Mail to info@wsd.wline.se for information
============================================================
