home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 48273 
 Rob Swindell (on Windows 11) to Git commit to main/sbbs/master 
 src/sbbs3/sbbsecho.c sbbsecho.h 
 10 Dec 25 16:04:02 
 
TZUTC: -0800
MSGID: 53696.syncprog@1:103/705 2da01232
PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0
TID: SBBSecho 3.32-Linux master/6bb344da2 Dec 08 2025 GCC 12.2.0
BBSID: VERT
CHRS: ASCII 1
FORMAT: flowed
https://gitlab.synchro.net/main/sbbs/-/commit/fe2d6930583d7961596c3e1c
Modified Files:
	src/sbbs3/sbbsecho.c sbbsecho.h
Log Message:
Don't write empty PATH: control line to exported echomail message

Points don't normally have any addresses to add to the PATH: line, so
(as was pointed out in the FIDOTEST echo), an empty PATH: line would be
included in exported echomail messages from points.

Although this isn't a violation of FTS-4, it is a violation of its proposed
successor: FSC-74:

  "Blank" path lines shall not be transmitted

And this caused a duplicate PATH: line to be added by FMail when processing
such messages.

This change also eliminates possibility of adding "\r\x01PATH:" not
followed by space (ASCII 32) character, which was also a violation of FSC-74.

I resisted the urge to clean-up this crufty bit of code here and made this
commit the minimal necessary change.
--- SBBSecho 3.32-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715
SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110
SEEN-BY: 229/134 206 317 400 426 428 470 700 705 240/1120 5832 263/1
SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124
SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35
PATH: 103/705 280/464 460/58 229/426


<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca