Hey slacker,

I know you are creating packets and writing your own message tosser.

Wanted to let you know that I found some unprocessed packets from you on clrghouz. They werent processed because the packets were not addressed to clrghouz.

IE: The packet contained a netmail to another system (it appears to be addressed correctly), but the packet itself wasnt addressed to clrghouz, it was also addressed to that other system. So by definition it should have been sent direct.

If you want clrghouz to route it, the packet should have been addressed to clrghouz (with your packet password).

Here it is:

Packet Type : 2+ (App\Classes\FTN\Packet\FSC48)
From : 21:3/193.0@fsxnet to 21:2/150.0@fsxnet
Dated : 2024-11-18 22:29:34 (1731929374) [+11:00]
Password : xxxxxx (SET)
Messages : 1
Tosser : 0 (Unknown) version 28.0 (ff)
Capabilities: 0000000000000001
Has Errors : No
Messages : 1

- TYPE : App\Models\Netmail
- Date : 2024-11-19 03:29:34 (+00:00)
- Errors : No
- Flags : private
- Cost : 0
- From : slacker (21:3/193.0@fsxnet)
- To : slacker (21:2/150.0@fsxnet)
- Subject: Re: Testing



...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: Packets
By: slacker to deon on Wed Nov 20 2024 07:59 pm

Howdy,

Oh! Thank you for this info! I've been scratching my head as to why I'm able to receive but for some reason couldn't get anything to go out even though there were no errors returned.

I will set up a netmail bounce message, that should give you this insight - so hopefully you realise sooner while mail is not flowing.


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Wanted to let you know that I found some unprocessed packets from you on c lrghouz. They werent processed because the packets were not addressed to c lrghouz.

IE: The packet contained a netmail to another system (it appears to be add ressed correctly), but the packet itself wasnt addressed to clrghouz, it w
as also addressed to that other system. So by definition it should have be
en sent direct.

If you want clrghouz to route it, the packet should have been addressed to
clrghouz (with your packet password).

Oh! Thank you for this info! I've been scratching my head as to why I'm able to receive but for some reason couldn't get anything to go out even though there were no errors returned.

I'll try a few more tests with the (hopefully) correct addressing.

--- NE BBS v0.68 (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

I will set up a netmail bounce message, that should give you this insight
- so hopefully you realise sooner while mail is not flowing.

Awesome! Thanks!

Btw, my test netmail message I sent earlier was successfully sent out after fixing the 'To' of the packet.


KLUDGES:
INTL 21:2/150 21:3/193
TID: NE BBS TOSSER 0.04 (linux; x64)
PATH:
3/193
RECEIVED:
2024-11-21 07:35:29 via 21:3/193.0@fsxnet pkt d9cd736e
SENT:
2024-11-21 13:00:42 via 21:2/100.0@fsxnet pkt 00001011

Thanks again for all the help figuring this out.

--- NE BBS v0.68 (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)