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.

 LE> Also, as I know from sad experience, some of the software that 
 LE> can't handle large messages does so based on number of *lines*, 
 LE> not size. For example, one mail import program would silently 
 LE> truncated inbound email at line 100, no matter how small the 
 LE> message was (sent a test message consisting of 1 to 200, each 
 LE> on a seperate line. It got chopped). 

 LE> So it might be a thought to add a "maxlines" command to limit 
 LE> the max number of lines.

I too have fiddled with that setting,  but ran into trouble anyway...

Thing is,  the trouble wasn't in my setup here,  nor in GIGO,  but upstream a
couple of links,  where they'd decided that 100k was a maximum email size.  And
there doesn't appear to be anything I can do about it.

I used to watch as Eudora Light pulled in email and,  when it got something
bigger than about 64k or so,  it would split it up.  Why?  Beats the heck out
of me...