MSGID: 1:396/45.0 f9b78000
REPLY: 1:396/45.0 f9b68c30
CHRS: IBMPC 2
Hello Alan.
<>
ML> With all due respect, there's something wonky about that. Nobody
ML> else's mail processor seems to have any problem appropriately
ML> forwarding netmail. E.g., I now send all out-of-zone netmail to
ML> 1:229/426. He's using D'Bridge; messages going to Z2 are delivered
ML> promptly. Same format - message bundle addressed to 1:229/426
ML> containing pkts bound for various Z2 addresses - all handled w/o
ML> problem... Or perhaps I don't properly understand what's inside
ML> that outbound mail bundle.> I have never attempted to open one
ML> and examine the contents as they're usually gone from the system in
ML> very short order.
ML> I will however, send netmail to one of my contacts in Z2, routed
ML> through 229/426, but I will stop the BinkP server long enough to do
ML> an exam of the message bundle.
I have 2 examples of the outbound message bundle contents. The bundle was
addressed to 1:229/426 for forwarding. Here's the contents of the bundle
containing 2 separate netmails for 2 separate Z2 addresses as seen by InspectA:
-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
=-=-=-=-Message content:
From: Marc Lewis 396/45 29 Oct 20 20:18:46
To: August Abolins 333/808
Subj: 2nd Test Size: 246b Stat: Pvt
Ofs: 58b-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
xTOPT 7
xMSGID: 1:396/45.0 f9b69dc1
xINTL 2:333/808 1:396/45
xCHRS: IBMPC 2
=-=-=-=-=-=-=-=-=-=-=-1st MESSAGE PKT=-=-=-=-=-=-=-=-=-=-=-=-=-
PKT INFO:
1/1 396/45 221/360 0000003a NETMAIL
Type 2+ Maximus-CBCS v1.11 O=1:396/45 D=2:221/360
=-=-=-=-Message content:
From: Marc Lewis 396/45 29 Oct 20 20:17:02
To: August Abolins 221/360
Subj: Test message Size: 243b Stat:
Pvt
Ofs: 58b-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
xMSGID: 1:396/45.0 f9b69dc0
xINTL 2:221/360 1:396/45
xCHRS: IBMPC 2
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
As you can see, although the message bundle is addressed to 1:229/426, the two
packets contained therein are addressed to their respective Z2 addresses.
Both these pkts will be delivered w/o problem by the forwarding node
(229/426). It's always worked like this in the past, even before 1:261/38 was
my feed - - years ago.
Please, when you have the opportunity, explain why BBBS's tosser/packer has
issues with this.
Best regards,
Marc
--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)
SEEN-BY: 1/123 19/25 33 90/1 103/705 106/633 987 120/340 123/131 124/5014
SEEN-BY: 124/5016 129/305 130/803 154/10 203/0 221/0 226/30 227/114
SEEN-BY: 229/101 424 426 452 550 664 1016 240/1120 2100 5138 5411
SEEN-BY: 240/5832 5853 249/206 317 261/38 280/464 5003 292/854 8125
SEEN-BY: 317/3 320/219 322/757 342/200 387/25 396/45 423/120 712/848
SEEN-BY: 770/1 2452/250 2454/119
PATH: 396/45 280/464 240/5832 229/426
|