ml>> while true, it only put a ceiling on the maximum message
 ml>> size able to be processed... if the code had been written
 ml>> properly, it'd likely still be able to be used today with
 ml>> larger limits... indeed, it may even be that fidonet would
 ml>> have already been carrying encoded pictures and such like
 ml>> internet email does... i remember several FTSC proposals for
 ml>> new PKT types that used "containers" and allowed for just
 ml>> such traffic...

 MT> Yep...that's exactly what I'm afraid of.  That's also why I
 MT> only bump my "Buffers" statement up to "Large" during
 MT> newsgroup-only processing runs.  The "too large" error in the
 MT> logs helps identify who needs to be added to SQTool's kill
 MT> filter. ;)

 MT> Maybe it's time for Squish to get a keep-by-size parameter
 MT> added to keep-by-days and keep-by-qty. :)

sadly, i don't understand the fight against being able to carry
multimedia... i can't even begin to count the number of arguments and
disagreements that would never have taken place if a picture of something
had been able to be sent rather than interpretive words being used that got
interpreted the wrong way around at the other end...

newsgroups and stuff like that are a bit different... especially these
days... but that's not what i'm looking at...

i also don't understand how one can filter, block or kill based on a bogus
name... no one in their right mind would dare to try to block spam based on
the From: name... at least not anyone who has tried it and learned what the
definitive definition of bogus is :wink:  especially when importing
newsgroups...

heck, i'd even like to be able to use xfaces in fidonet... hummm... there's
an idea :wink:

)\/(ark