VC> tearlines and origin lines and even message body lines have artificial VC> limits placed on them because folks got used to 80x25 terminals... they VC> look very funny when viewed on terminals with larger widths...
*SBBS* has a bug, I just noticed the last two emails I have "quoted" it is putting the incorrect initials ... VC should be ML... :-/
Anyway, would it be worth implementing a Kludge for flowed - when found 0d is ignored and paragraphs get formatted by the reader? This is how JAMNNTPd works - in my NNTP server code I dropped flowed since it was really messing up BBS_ADS and a couple other echos. I thinking adding ^aFORMAT: flowed^m would help in the cases that people can handle >80 columns.
That would make ^aCOLS: 80^m make a little more sence ;) Ozz --- SBBSecho 2.12-Win32 * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)
