Hello everybody!

After checking a couple of times this morning, I am getting some of my uplink packets tossed to badpkt folder, after I opened one of the pkts, this is one of the headers.

è _ & * *y*Davidy PASS♥ ♥ @ @ ♥ ♥ *AB8D* å *y* 20 Oct 24 08:00:30 All Northern Realms NYPost Daily Horoscope AREA:HOROSCOPE
NYPost Daily Horoscope for Sunday, October 20, 2024*

I didn't see any tarce of these bad pkts on the logs, not the messages tossed to my duplicates echo area, Mystic or mutil mailin process don't give me mucho of a clue.

Any advice you guys could provide where to look?.

Gracias.

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)

Re: Getting packets sent to badpkt folder and no log
By: David Gonzalez to All on Mon Nov 11 2024 01:46 pm

Howdy,

After checking a couple of times this morning, I am getting some of my uplink packets tossed to badpkt folder, after I opened one of the pkts, this is one of the headers.

Your tosser's log file should tell you why it put the packet's contents in the badpkts folder. Posting it here will not be enough to determine why your tosser made the decision it did.

BTW: Dont post raw packets, most terminals cannot show the non-printable content and it causes wierd message rendering - eg: beeps. If you want some body to review the headers, post a hex dump.


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

Hello deon!

12 Nov 24 08:32, you wrote to me:

Oh boy

Re: Getting packets sent to badpkt folder and no log
By: David Gonzalez to All on Mon Nov 11 2024 01:46 pm

Howdy,

After checking a couple of times this morning, I am getting some of
my uplink packets tossed to badpkt folder, after I opened one of
the pkts, this is one of the headers.

Your tosser's log file should tell you why it put the packet's
contents in the badpkts folder. Posting it here will not be enough to determine why your tosser made the decision it did.

BTW: Dont post raw packets, most terminals cannot show the
non-printable content and it causes wierd message rendering - eg:
beeps. If you want some body to review the headers, post a hex dump.

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

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)