Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MBSE    |    The Linux/FreeBSD MBSE BBS Support Echo    |    2,445 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,647 of 2,445    |
|    Vince Coen to mark lewis    |
|    Filefind file limit    |
|    25 Oct 17 22:50:07    |
      Hello mark!              Wednesday October 25 2017 11:10, you wrote to me:              Thanks for that and I will increase my system limit if possible.              Vince                      > On 2017 Oct 25 14:36:30, you wrote to Andrew Leary:               AL>>> In the future, I can look at possibly splitting large replies        AL>>> into multiple messages.               VC>> In mbse there is a 60/64k message limit does this still apply in        VC>> fido land these days with internet comms used for most if not all        VC>> sysops ?               > there never was a limit on message size... what everyone has been        > seeing is arbitrary limits placed by ""lazy"" coders*... the tech        > standard states that message bodies are unbounded which means there is        > no limit set... this leaves plenty of room for expansion as technology        > grows... we can see this by this very 64k barrier... it used to be        > 32k... these days, memory is accessed differently and the barrier is        > much much larger... effectively, each system is limited by drive        > space*N where N is the number of copies of the message a system makes        > when processing the message... copies because of sending to other        > systems in a distribution system (eg: fidonet)...                      > * ""lazy"" coders: those who didn't implement some sort of disk-based        > overflow system so they could process messages too large to fit into        > the memory allocation scheme of the time... sure, the larger messages        > would be processed slower but they would be processed and passed on...        > no need for splitting... splitting should be done only when the        > messages are stored in a local message base that has arbitrary message        > size limits in place... split the message when initially stored...        > reassemble it into one when exporting it to other systems (eg: they        > rescanned the area)... the ^ASPLIT spec is perfect for this but some        > chose to use it at another point in the process...               > )\/(ark               > Always Mount a Scratch Monkey        > Do you manage your own servers? If you are not running an IDS/IPS yer        > doin' it wrong...        > ... The road to success is often under construction...                     Vince              --- Mageia Linux v5/Mbse v1.0.7.2/GoldED+/LNX 1.1.501-b20150715        * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca