| |
WQ6N > SYSOP 25.01.20 22:32z 33 Lines 1247 Bytes #999 (0) @ WW
BID : 89_WQ6N
Read: GUEST
Subj: Non-delivery Notifications and missing Flood Codes
Path: HB9ON<IW2OHX<IR1UAW<I0OJJ<I0OJJ<N6RME<AA6HF<KC6IKE<WQ6N
Sent: 200125/2146Z 89@WQ6N.#SCA.CA.USA.NOAM BPQ6.0.19
>From wq6n%wq6n.#sca.ca.usa.noam@i0ojj.ampr.org Sat Jan 25 23:32:36 2020
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0m.1) with SMTP
id AA97367 ; Sat, 25 Jan 2020 23:32:36 +0100
Message-Id: <89_WQ6N@i0ojj.bbs>
>From: wq6n@wq6n.#sca.ca.usa.noam
X-JNOS-User-Port: Telnet (i0ojj @ 44.134.32.240) -> Sending message
It has been my experience while troubleshooting B type (bulls) being changed to P type (personnel) due to flood codes being str
ipped during forwarding. The result is a string of Non-delivery Notifications that usually die off and get sent back to the sou
rce of the sender.
While troubleshooting, I had taken the time to change the mail back to B type with the correct flood codes. What a pain.
My test string was a JNOS and BPQ32 systems forwarding with AX25 and AXIP paths.
As for me, I finally found the source of the stripping of the flood codes, an apparent after effect of sending and receiving fo
rwarding BBS partners, with different FBB forwarding settings.
Once both sides of the forwarding processes are aligned (e.g. FBB 2 or F2B), the problem of the flood code stripping and Bull t
o Personnel type changes all goes away.
Hope this information will help others resolve forwarding conflict
Read previous mail | Read next mail
| |
