Subj : sbbsecho not importing netmail
To   : Digital Man
From : deon
Date : Fri Feb 18 2022 21:39:35

  Re: sbbsecho not importing netmail
  By: Digital Man to deon on Thu Feb 17 2022 11:38 pm

 >  > I have a test setup of SBBS - compiled master/70898b5bb. It's configured as 21:3/999.
 >
 > Sorry, I don't memorize the git SHAs, so not sure what version that is/was. :-)

https://gitlab.synchro.net/main/sbbs/-/commit/70898b5bb

(2 weeks ago).

 >  > Sending a netmail from it to 21:2/116 works well.
 >  > Sending a netmail from 21:2/116 to 21:3/999 results in this:
 >  > 2022-02-18 16:11:59 Importing /opt/sbbs/fido/inbound/0a452fa6.pkt (Type 2e, 0.4KB) from 21:3/2744 to 21:3/999

 > Where does 21:3/2744 come in? You didn't mention that address in your intro.

OK, 2/116 -> 3/1 -> 3/2744 -> 3/999 is the path of netmail. (The other direction is the reverse).

 >  > Why would it not recognise 21:3/999 as itself, and its trying to forward it on to 21:0/0?
 >
 > Well, 21:0/0 isn't a local address on your system, so naturally it'll be packed up to be sent on... somewhere.
 >
 > Now 21:0/0 does sound like a bad packet. Use a tool pktdump to inspect the packet more closely.
 >
 > Are you running the latest and greatest SBBSecho on both systems?

I was wondering about the bad packet - and it's my next check. But sending netmail in the reverse direction works OK. (2/116 is quite old master/8f79438d2, which according to https://gitlab.synchro.net/main/sbbs/-/commit/8f79438d2 9 months ago).

I was discounting a bad packet, given the "Importing" line - but I guess that is the packet header, not the message header?

I'll explore the packet in detail and double check it's not bad (it's possible that it is...)


....лоеп

---
 ю Synchronet ю Alterant | an SBBS in Docker on Pi!
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.