201024 20:30 Processing packet f94c5fd9.pkt from 1:396/45.0, 1070
bytes.
201024 20:30 BOGUS: Packet /home/bbbs/tmpin/f94c5fda.pkt is not for us (2:333/808.7) This clip above I believe is saying that your netmail to 2:333/808.7 was seen by bbbs as lacking proper "routing" verbs (or
whatever the heck <g>) BBBS is looking for to route to another node.
I also know part of the problem is that BBBS will not deliver mail to _point_ addresses (they are points, not nodes).
I have had to change my netmail routing to another node that doesn't exhibit this aberrant behaviour.
Any views on this?
I have had to change my netmail routing to another node that doesn't
exhibit this aberrant behaviour.
I haven't looked at the input .pkt so here is my guess.
Any views on this?
Was the packet addressed to 1:261/38? The packet header I mean. The messages within the packet could have been echomail or netmail
addressed to any node and those message will be forwarded on as
usual.
If that packet was addressed to 1:261/38 (the packet, not the
messages inside) the tosser there will likely act on it as needed.
The mail bundle was addressed to 261/38 for forwarding purposes. The packet would have been addressed to 2:333/808.7.
201024 20:30 Processing packet f94c5fd9.pkt from 1:396/45.0, 1070 bytes. 201024 20:30 BOGUS: Packet /home/bbbs/tmpin/f94c5fda.pkt is not for us (2:333/808.7)
If that packet was addressed to 1:261/38 (the packet, not the
messages inside) the tosser there will likely act on it as
needed.
If by packet you actually mean the mail bundle, then yes the affected bundles went to 1:261/38.
If by packet you actually mean the mail bundle, then yes the affected bundles went to 1:261/38.
A compressed mail bundle is a different thing, it may contain one
or more packets (*.pkt files). If you want any node to open a .pkt
file and toss it those packets need to be addressed to that node
even though the messages inside are destined for other nodes.
With all due respect, there's something wonky about that. Nobody
else's mail processor seems to have any problem appropriately
forwarding netmail. E.g., I now send all out-of-zone netmail to
1:229/426. He's using D'Bridge; messages going to Z2 are delivered promptly. Same format - message bundle addressed to 1:229/426
containing pkts bound for various Z2 addresses - all handled w/o problem... Or perhaps I don't properly understand what's inside
that outbound mail bundle.<?> I have never attempted to open one
and examine the contents as they're usually gone from the system in
very short order.
I will however, send netmail to one of my contacts in Z2, routed
through 229/426, but I will stop the BinkP server long enough to do
an exam of the message bundle.
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
=-=-=-=-=-=-=-=-=-=-=-2nd MESSAGE PKT=-=-=-=-=-=-=-=-=-=-=-=-=-
PKT INFO:
1/1 396/45 333/808 0000003a NETMAIL Type 2+ Maximus-CBCS v1.11 O=1:396/45 D=2:333/808
Please, when you have the opportunity, explain why BBBS's
tosser/packer has issues with this.
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 991 |
Nodes: | 10 (0 / 10) |
Uptime: | 00:28:14 |
Calls: | 12,940 |
Files: | 186,574 |
Messages: | 3,262,554 |