Inbound messages are being processed properly at Mystic level. Only outbound messages are not being recognized at Frontdoor level.
I ended up using like a file spool option to hold messages for outgoing traffic to nodes just like yours. This takes away any issues around sending other instructions / file attaches etc. to Frontdoor in order to get it to send files.
If you have a look back at info posted by JoHo at the time I was setting up then you should find what you're looking for. I'll try and dig up some further info in the coming days when I get some time :)
Inbound Echomail: c:\fd\secfiles
Outbound Echomail: c:\fd\files
I remember my old Squish cfg had both of these as inbound and imported
the unsecured Files directory with a "no-echomail" switch so I'd get incoming netmail from unknown nodes but no spurious echomail. For
outbound mail Squish dumped packets in FD's Packets directory, which it recognized and automatically transmitted to the host during the morning mail hour.
did not recognize the file, but probably I'll have to configure it in
such a way that FD focus on send files and don't care about netmail.
This is the way to go. From memory it's because FD is looking for
netmail is MSG format and Mystic does not deliver that. So I opted to
set fileboxes up for outgoing nodes, and use Mystic in 'directory' mode
to fidpoll packets to that outgoing spool directory for each given
node... hope that helps
Just did that and it worked fine! :) I was going through the documentation, but I can't access the STQ, it states that there is no queue available, so I did send the files manually. I will keep looking into the docs to create the filemasks correctly, but at least is working now. :)
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 60 |
Nodes: | 4 (0 / 4) |
Uptime: | 14:50:20 |
Calls: | 516 |
Files: | 6,995 |
D/L today: |
1 files (12K bytes) |
Messages: | 288,946 |