Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 47957  |
|  Rob Swindell (on ChromeOS) to Git commit to main/sbbs/master  |
|  src/sbbs3/echocfg.c rechocfg.c sbbsecho.  |
|  31 Oct 25 20:24:54  |
 TZUTC: -0700 MSGID: 53392.syncprog@1:103/705 2d6b8416 PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0 TID: SBBSecho 3.30-Linux master/96091c55c Oct 31 2025 GCC 12.2.0 BBSID: VERT CHRS: ASCII 1 FORMAT: flowed https://gitlab.synchro.net/main/sbbs/-/commit/8c70994e75d4ba6960faca58 Modified Files: src/sbbs3/echocfg.c rechocfg.c sbbsecho.c sbbsecho.h Log Message: Support SBBSecho robots that use .msg files directly Each configured robot now has a "Uses MSG File" option (defaults to false) and if set to true, either the initial .msg file will be retained or if imported from a packet will be exported to .msg format, thus skipping the "mail base" phase. Make the default robot attributes value 0x20 (In-transit) since that prevent repeated imports and exports of the same mail message. I think this addresses issue #1001 With the robot attributes set to 0, I would've expected a .msg-using robot to still work (before this change) via the path: .pkt->mail base->.msg or even .msg->mail base->.msg. But now we don't need the mail base phase. Increase SBBSecho version to 3.31 --- SBBSecho 3.30-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 10/0 1 102/401 103/1 705 105/81 106/201 124/5016 128/187 SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 610 700 810 226/30 SEEN-BY: 227/114 229/110 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 >> ]