Subj : Re: BinkD To : Ingo Juergensmann From : Joacim Melin Date : Sun Aug 11 2019 11:43:39 IJ> Hello Dave! IJ> 11 Jul 18 19:08, you wrote to Frank Linhares: FL>>> I gave up as well. I now run BinkD on a Raspberry Pi and connect FL>>> it to my Amiga via a null modem cable. That and some scripting at FL>>> both ends make mail flow smoothly. DV>> I came up with a simple solution, since I run an emulator, I just DV>> setup a win32 version of binkd, set it to use amiga style outbound DV>> (aso) then used a path translation to translate amiga path -> windows DV>> path .. 2 lines and everything works great IJ> I'm looking for a similar solution: running the tosser on my Amiga IJ> behind binkd on Linux. IJ> But instead using some sftp/scp or whatever I'm thinking about using IJ> some NFS or SMB share between Amiga and Linux for inbound/outbound. IJ> Does anyone have experience with this kind of setup? Are there some IJ> pitfalls to expect? Here's how I do it, and it works really well. On a virtualized Linux machine (Ubuntu) I run Binkd and Crashmail II (check Github...). Binkd is the mailer and Crashmail II is the tosser. I handle all the mailing/storing/tossing stuff on that Linux machine and then offer that to the Amiga 2000 running my BBS via NFS. My BBS then has a scripts that imports and exports all messages in the MSG format from/to the Linux machine. Do note this: The Amiga (or at least my BBS software) read and wrote 16 bit values in the .MSG files in the big endian format which works fine with tossers running on the Amiga. Crashmail II on x86 and Linux uses the little endian format which caused outgoing mail never to be found by the tosser. The developer of my BBS software fixed this - I'm unure if this is an issue with all Amiga based software packages. The same problem arose when I tried to use the Crashmail tosser on the Amiga and then send the packages to the Linux machine where Binkd runs. (sorry for late reply, etc). --- NiKom v2.5.0 * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (39:160/242.0) .