| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 28 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 50:01:50 |
| Calls: | 422 |
| Files: | 1,024 |
| Messages: | 90,494 |
Hi Martin,
On 2024-10-29 21:14:06, I wrote to you:
orI need someone from Zone 1 who isn't a point to send me a netmail. O MK>>> course, everyone who volunteered previously was outside zone 1
a point, both of which I've never had working routing from my Feed MK>>> (Zone1, Net340).
You know you can send messages to 'PING' and get an automated response
on systems that support this (see the PING flag in the nodelist). There
is one in your region: 1:134/0
And it works (somewhat). I tested it and got a response within 8minutes from
1:134/100. So maybe better use that node number... ;-)
The response from 1:134/0 (aka 1:134/101) took a bit longer, about 40 minutes, and was delivered here by crashmail. So not so useful for you if you want routed mail send to you.
The response from 1:134/0 (aka 1:134/101) took a bit longer, about 40
minutes, and was delivered here by crashmail. So not so useful for
you if you want routed mail send to you.
Never received a PING response.
The important thing is why. Binkd is sending echomail and so is fastecho. One of them isn't sending netmail routed. I sent a netmail directly to lord time and it worked. Routed to Sean Dennis worked.
I need someone from Zone 1 who isn't a point to send me a netmail.
I sent you a direct netmail a short time ago.
It is likely to arrive in your unprotected inbound.
Of course, everyone who volunteered previously was outside zone 1 or a point, both of which I've never had working routing from my Feed (Zone1, Net340).
A netmail is simply a netmail message.
It makes no difference if the message came from another zone or point, a message addressed to your node should be forwarded either directly or
routed to your node.
Routed mail can get lost however, and there isn't a good way to know
where, why or how it failed.
Hi Martin,Yeah, I put "PING" in To: Subject: and Body.
On 2024-10-29 20:39:00, you wrote to me:
40The response from 1:134/0 (aka 1:134/101) took a bit longer, about
minutes, and was delivered here by crashmail. So not so useful for
you if you want routed mail send to you.
Never received a PING response.
If you are doing it correct ("PING" in the To: field), 1:134/100 should respond. And make sure there is some text in the message it self, because some systems delete empty messages...
I'll check again when I've got some time to do this in real-time, but theThe important thing is why. Binkd is sending echomail and so isfastecho.
One of them isn't sending netmail routed. I sent a netmail directly tolord
time and it worked. Routed to Sean Dennis worked.
If you take a look in your logs and/or in some of your directories, you may find error messages or "lost" packets laying around. That would
tell you it is on your end and not with your hub or somewhere
along the way.
A while back when we were testing, I got the FSX netmail you sent me, which would have routed through different system(s) than your FIDO netmail.
The important thing is why. Binkd is sending echomail and so isfastecho.
One of them isn't sending netmail routed. I sent a netmail directly tolord
time and it worked. Routed to Sean Dennis worked.
If you take a look in your logs and/or in some of your directories, you may find error messages or "lost" packets laying around. That would
tell you it is on your end and not with your hub or somewhere
along the way.
A while back when we were testing, I got the FSX netmail you sent me, which would have routed through different system(s) than your FIDO netmail.
Never received a PING response.
If you are doing it correct ("PING" in the To: field), 1:134/100 should
respond. And make sure there is some text in the message it self, because
some systems delete empty messages...
Yeah, I put "PING" in To: Subject: and Body.
Hi Martin,
On 2024-10-30 11:34:00, you wrote to me:
Never received a PING response.
shouldIf you are doing it correct ("PING" in the To: field), 1:134/100
respond. And make sure there is some text in the message it self, because
some systems delete empty messages...
Yeah, I put "PING" in To: Subject: and Body.
Then you will have to check your logs if it went out the door, and if so check with your uplink if it got forwarded... It is really simple! ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523 * Origin: FMail development
HQ (2:280/464)
My messages just recently went out; I needed a -p argument with my
packing command.
Ok, instead of "fastecho pack" I need "fastecho pack -p" and it seemed to go out. We'll see if people get these now.
Ok, instead of "fastecho pack" I need "fastecho pack -p" and it seemedto go
out. We'll see if people get these now.
Good luck. Hopefully you have it figured out now!