| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: fmail not packing crash-netmail? |
Hi mark, On 03 Dec 13 11:08, mark lewis wrote to Tom De Puysseleyr: about: "fmail not packing crash-netmail?": TDP>> Does binkd support unpacked messages? I would assume it doesn't TDP>> care which type file is specified in the .flo file, it just TDP>> transfers it to the other side. If that's the case, then the TDP>> reason would be within fmail... ml> yes, binkd does and you are right in that it doesn't care what's in the ml> files... raw PKTs in BSO format have an ?UT extension... CUT are crash, ml> DUT are direct, i think FUT is normal non-crash non-direct but would have ml> to dig out the documentation from the original binkleyterm... when these ml> ?UT files are sent to the remote, they are renamed in transmission to at ml> least have an extension of PKT so the other side will recognize them... ml> on the local BSO side, they could also be named PKT but then a ?LO file is ml> required to point to them for transmission... That looks about right... ;) The full specification is here: http://ftsc.org/docs/fsp-1034.001 (If anyone is interested) Wilfred. --- FMail-W32-1.66* Origin: point{at}work (2:280/464.112) SEEN-BY: 19/33 75 34/999 90/1 116/18 123/500 128/2 187 135/364 140/1 218/700 SEEN-BY: 222/2 226/0 160 230/150 249/303 250/306 261/38 100 266/185 1413 SEEN-BY: 267/155 280/1027 292/907 908 311/2 320/119 322/762 340/400 393/68 SEEN-BY: 396/45 633/260 267 712/848 800/432 801/161 189 5030/1256 @PATH: 280/464 292/854 140/1 261/38 633/260 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.