-=> Quoting Jason Fesler to Leonard Erickson <=-

 JF> Alas, there's a default SPLIT value if you don't set one yourself.
 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 go back and change it. I just set it to 16000000. :-)

 JF> What tosser is that?  It's a work of art to handle true unbounded
 JF> text, considering the current state of fidonet  :-).  Having half
 JF> the info at the beginning of the message is cool, but having half
 JF> at the end *sucks*..

Jmail, Jason Steck is the author. It's also now *the* mail
tosser/scanner for QuickBBS (replaces QEcho, mailtoss and mailscan). 
 
 LE> Also, as I know from sad experience, some of the software
 LE> that can't handle large messages does so based on number of
 LE> *lines*, not size. For example, one mail import program
 LE> would silently truncated inbound email at line 100, no
 LE> matter how small the message was (sent a test message
 LE> consisting of 1 to 200, each on a seperate line. It got
 LE> chopped). 

 JF> Blech!

Agreed, but the results of *not* having it are fairly major.
 
 LE> So it might be a thought to add a "maxlines" command to
 LE> limit the max number of lines.

 JF> I'll keep it in mind, but no promises.  I've never been asked for
 JF> this one before at all, and the amount of overhead is not small.
 JF> Currently, GIGO doesnm't try and parse lines (other than headers) -
 JF> it's just one big buffer. 

I'd just scan for EOLs in the buffer, and keep a count until I got
close to the limit. then I'd worry about "parsing" the buffer. Of
course, if the buffer is at all large, you get nailed immediately
anyway. :-(


... DOS 6.0 - A $49 confirmation that you need REAL utilities