Subj : Re: Issues with PING functionality
To   : Flavio Bessa
From : Alan Ianson
Date : Wed Apr 13 2022 18:52:46

>> I sent a couple, one routed that is still parked in my outbound until
>> picked up and another direct that is at your node now but may be in your
>> unprotected inbound.

> Thanks Alan, I can see from my logs here that two PING responses were sent
> towards 1:153/757. Please let me know if they were correctly received or
> ended up at your BAD echomail directory.

I have no netmail in my netmail area or any bad packets here.

However I see this in my logs..

This is the netmail I sent to ping @ 4:80/1 via 4:920/1.

220413 17:49 BMT: 1:153/757.0 -> 4:80/1.0, 139 bytes
220413 17:49 BMT: Alan Ianson -> Ping [Ping]
220413 17:49 Routing netmail to 4:80/1.0 via 4:920/1.0
220413 17:49 Creating new attach 23e7a7a1.pkt to 4:920/1.0

This packet was received from 1:320/219.

220413 18:06 Processing packet 569d17e6.pkt from 1:320/219.0, 250 bytes.
220413 18:06 BMT: 1:80/1.0 -> 1:153/757.0, 57 bytes
220413 18:06 BMT:  ->  []
220413 18:06 BMT: 1:80/1.0 -> 1:153/757.0, 57 bytes
220413 18:06 BMT:  ->  []

The From and subject are blank. I suspect this packet was grunged somehow but I don't have the packet to inspect.

Can you either set your mailer to reply directly or through 4:920/1 and we'll see if we get better results?

Let me know if you'd like me to try again.

--- BBBS/Li6 v4.10 Toy-6
 * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

.