Wilfred,

03 Dec 13 10:18, you wrote to me:

 TDP>> I am still having some questions about this. In my batch-file
 TDP>> that's executed after I write netmail, I use the above command.
 TDP>> When I write a normal (routed) netmail and pack it like that, it
 TDP>> creates a .flo file for the destination instead of following the
 TDP>> packing rules in fsetup. Is it supposed to do that?

 WV> For regular routed netmail you first have do a "normal" pack:

 WV> c:\fd\Fmail\FMailW32.exe pack

 WV> This leaves the netmails with crash status alone. You could have this
 WV> followed by the line with /C in your automatic batch files. I have a
 WV> seperate batch file for crashing netmails, that I only use manual, as
 WV> I don't often send crash netmails...

Ok, weird but I guess it'll work. I have only one batchfile, that's
automatically executed when golded exits. It knows the difference between
echomail and netmail but not between normal netmail and crashmail. So I'll
run both commands.


 WV> 4.4       Pack

 WV> [...] Packing messages is not required (but sometimes
 WV> useful) in e.g. a FrontDoor environment. It _is_ required in a
 WV> Binkley/PoP environment.
Does binkd support unpacked messages? I would assume it doesn't care which
type file is specified in the .flo file, it just transfers it to the other
side. If that's the case, then the reason would be within fmail...

 WV> So if you want to send your crash netmails unpacked, unfortunately you
 WV> have to use something else than FMail. Or do some processing after
 WV> FMail creates such a packed packet.
I don't feel like converting everything to another tool, so maybe the
second option would be easier. When I have a lot of time someday, ....




Groetjes,
Tom

--- GoldED+/W32-MINGW 1.1.5-b20130111