[...]Did you get a response now?
No, and I tried it again with a crashmail to your system. Which also didn't get a response so far:
Did your system proces it? And where did it route the answer to?
I've looked in my Synchronet log file and found your call.
Also, just some seconds later, an outgoing call was initiated - and I guess, your answer was sent this way:
18:44:07 BINKP Remote addresses: 2:280/464@fidonet 39:39/0@amiganet 18:44:07 BINKP Receiving file: /sbbs/temp/07b0fd60.pkt (0.4KB)
18:44:07 BINKP Received file: /sbbs/temp/07b0fd60.pkt (0.4KB)
18:44:07 BINKP Non-secure session type: 'non-secure'
18:44:07 BINKP Moving '/sbbs/temp/07b0fd60.pkt' to '../fido/nonsecure/ 07b0fd60.pkt'.
18:44:11 DAILY Semaphore signaled for Timed Event: FIDOIN
18:44:11 FIDOIN Running native timed event: FIDOIN
18:44:11 FIDOIN Timed event: FIDOIN returned 0
18:44:15 DAILY Semaphore signaled for Timed Event: BINKOUT
18:44:15 BINKOUT Running timed event: BINKOUT
18:44:15 BINKOUT BinkIT/2.39 invoked with options:
18:44:15 BINKOUT Attempting callout for 2:240/5832@fidonet, file: /sbbs/ fido/outbound/00f016c8.out
18:44:15 BINKOUT JSBinkP/1.123 callout to 2:240/5832@fidonet started 18:44:15 BINKOUT Connecting to 2:240/5832@fidonet at bamberg-ot.de:24554
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 410 |
Nodes: | 16 (2 / 14) |
Uptime: | 78:58:50 |
Calls: | 8,578 |
Calls today: | 2 |
Files: | 13,225 |
Messages: | 5,932,144 |