Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 48759  |
|  Rob Swindell (on Windows 11) to Git commit to main/sbbs/master  |
|  src/sbbs3/mailsrvr.cpp  |
|  17 Jan 26 04:11:26  |
 TZUTC: -0800 MSGID: 54191.syncprog@1:103/705 2dd1861d PID: Synchronet 3.21b-Linux master/177a369d2 Jan 04 2026 GCC 12.2.0 TID: SBBSecho 3.34-Linux master/e6acb3269 Jan 17 2026 GCC 12.2.0 BBSID: VERT CHRS: UTF-8 4 FORMAT: flowed https://gitlab.synchro.net/main/sbbs/-/commit/c5daf067bae2f7666c4ccfc2 Modified Files: src/sbbs3/mailsrvr.cpp Log Message: Strip ctrl chars "B" mime-encoded words in incoming message header fields Per RFC2047: "Only printable and white space character data should be encoded using this scheme." Apparently TikTok doesn't follow that advice. Here's one example: 68% #614159 (1741720) TikTok Header field contains control characters ... Subject 6C 69 76 6B 61 70 73 7A 6F 6F 20 70 6F 73 74 65 64 3A 20 4D 75 66 66 69 6E 20 73 61 69 64 20 0A 4E 6F 20 74 68 61 6E 6B 73 F0 9F AB A0 Which expands to: "livkapszoo posted: Muffin said No thanks🫠" This could do weird things when the message is viewed (depending on the viewer) and triggers the chksmb error: Control Characters in Header Fields (!): 1 --- SBBSecho 3.34-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 10/0 1 102/401 103/705 105/81 106/201 124/5016 128/187 129/14 SEEN-BY: 153/7715 154/110 214/22 218/0 1 215 700 810 226/30 227/114 SEEN-BY: 229/110 134 206 317 400 426 428 470 700 705 266/512 280/464 SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280 SEEN-BY: 712/848 902/26 5075/35 PATH: 103/705 218/700 229/426 |
[ << oldest | < older | list | newer > | newest >> ]