JF> Leonard Erickson wrote in a message to Jason Fesler:

 LE> Got a question. I commented out the "SPLIT 15000" line, as our 
 LE> tosser can handle anything we are going to get (if it ever 
 LE> chokes, the author will rewrite it so it won't. He believes 
 LE> "text unbounded" means what it says). 

 LE> Trouble is, GIGO seems to be splitting messages *anyway*. Since 
 LE> we aren't feeding anybody else, we'd kinda like to not have 
 LE> this happen. I *could* put in something like "SPLIT 16711680" 
 LE> (max message size our messagebase format allows) but that'd be 
 LE> kinda silly.

 JF> Alas, there's a default SPLIT value if you don't set one 
 JF> yourself. 

Me,  I didn't comment that line out,  I just added an extra zero on the end...



 JF> Go ahead and set it to the max message size you wish to honor. 
 JF> I'd set it to the same as your MAX_USENETBUF.

I'll have to look at that...

 JF> What tosser is that?  It's a work of art to handle true 
 JF> unbounded text, considering the current state of fidonet :-).

I'm doing pretty well with Squish here.  Running the 386+ version,  I can
handle some *really big* messages.  The limit,  in fact,  is upstream from me
on the usenet side of things,  set at 100k by the commercial provider two steps
up the line from me.

 JF> Having half the info at the beginning of the message is cool, 
 JF> but having half at the end *sucks*..

:-)