+ Oct 22 07:01:57 Process: Importing EchoMail
+ Oct 22 07:01:57 Waiting for BUSY nodes
! Oct 22 07:01:57 Import from /home/xxxx/mystic/echomail/in/
+ Oct 22 07:01:57 Extracting 4FE35279.SA0
- Oct 22 07:01:57 unzip -oqqjC
"/home/xxxx/mystic/echomail/in/4FE35279.SA0" "*.pkt" -d /home/xxxx/mystic/temputil/
! Oct 22 07:01:57 Unable to extract bundle; skipping
+ Oct 22 07:01:57 Extracting 4FE35279.TU2
- Oct 22 07:01:57 unzip -oqqjC
"/home/xxxx/mystic/echomail/in/4FE35279.TU2" "*.pkt" -d /home/xxxx/mystic/temputil/
+ Oct 22 07:01:57 Importing 90F59CFC.PKT (954:895/1 to 954:895/29)
+ Oct 22 07:01:57 Shutdown Corrupted memory (216)

I noticed there wasn't any new echomail msgs in a while and I found this li'l stinker.. deleted 90F59CFC.PKT and back to good, but why would this happen?

|08__ _ _ ____ |02_ _ |10___ _ _ |02____ |08_ _ _ ___
|08| \| | |__\ |02|--| |10 | \/ |02|--| |08|__| |___ |

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Nightvault (21:3/112)

Hello fang-castro,

I noticed there wasn't any new echomail msgs in a while and I found
this li'l stinker.. deleted 90F59CFC.PKT and back to good, but why
would this happen?

Sounds like a stinky packet. Do you still have that packet to inspect?\
Ttyl :-),
Al

... If you don't think women are explosive, drop one!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

why

would this happen?

@fc
It happens due to bugs in the software, ie, not failing gracefully.

Sounds like a stinky packet. Do you still have that packet to
inspect?\

@al
Hopefully, but it sounds like he deleted it.

@fc
If you didn't delete it, you could try sending it to james so he can find
the bug in mystic that the dodgy packet is triggering.

Also, I wouldn't mind taking a look at the packet too as I've been
battling similar problems in my software, would be good to test against.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.27-dev (Windows/x64)
* Origin: The Grinning Cat >^.^< (21:1/182.1)

On 23 Oct 2021, Al said the following...

Sounds like a stinky packet. Do you still have that packet to inspect?\
Ttyl :-),
Al

I do. I've never inspected a packet; sounds devious. What can we find in it?

|08__ _ _ ____ |02_ _ |10___ _ _ |02____ |08_ _ _ ___
|08| \| | |__\ |02|--| |10 | \/ |02|--| |08|__| |___ |

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Nightvault (21:3/112)

Hello fang-castro,

Sounds like a stinky packet. Do you still have that packet to
inspect?

I do. I've never inspected a packet; sounds devious. What can we find
in it?

If we are lucky we can find and solve the issue. We don't want tossers just quitting like that.

If you can make that packet available on the web of ftp site I'll have a look and see if I can see any issues with it.

Probably a good idea to get that packet to g00r00 as well see he can see what is happening.

Ttyl :-),
Al

... AAAAA - American Association Against Acronym Abuse
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.3)

Sounds like a stinky packet. Do you still have that packet to
inspect?

I do. I've never inspected a packet; sounds devious. What can we find in it?

If we are lucky we can find and solve the issue. We don't want tossers just quitting like that.

If you can make that packet available on the web of ftp site I'll have a look and see if I can see any issues with it.

i don't have any net presence besides the BBS. the login is quick w/full
access if you want to DL it from the file area 'network' i just added w/the packet. nightvault.fsxnet.nz:2323

if you don't want to spend the time i'm feeling adventurous, i'll try and
setup a html/ftp point to get it from this evening.

=)
fc

|08__ _ _ ____ |02_ _ |10___ _ _ |02____ |08_ _ _ ___
|08| \| | |__\ |02|--| |10 | \/ |02|--| |08|__| |___ |

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Nightvault (21:3/112)

i don't have any net presence besides the BBS. the login is quick w/full access if you want to DL it from the file area 'network' i just added w/the packet. nightvault.fsxnet.nz:2323

I just tried to download it, but it said i don't have access?

Andrew

... Error 3032 - Recursion error. See error 3032.

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I just tried to download it, but it said i don't have access?

oops! i had s25 instead of s20 for the file area... sorry!

|08__ _ _ ____ |02_ _ |10___ _ _ |02____ |08_ _ _ ___
|08| \| | |__\ |02|--| |10 | \/ |02|--| |08|__| |___ |

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Nightvault (21:3/112)

oops! i had s25 instead of s20 for the file area... sorry!

Thanks, got it now :D

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.27-dev (Windows/x64)
* Origin: The Grinning Cat >^.^< (21:1/182.1)

Hello fang-castro,

If you can make that packet available on the web of ftp site I'll
have a look and see if I can see any issues with it.

i don't have any net presence besides the BBS. the login is quick
w/full access if you want to DL it from the file area 'network' i just added w/the packet. nightvault.fsxnet.nz:2323

I'll come by and grab it in a minute or two..

Ttyl :-),
Al

... There is never time to do it right, but there's always time to do it over --- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.3)

Hello fang-castro,

I'll come by and grab it in a minute or two..

pktinfo tells me that the fromusername field is empty so the message header is wrong. It is a corrupt packet.

It would be better if mutil just dropped the packet, renamed it to bad or something instead of holding up your mail processing.

I would send the packet to g00r00 so he can see what is happening and give it some thought.

Ttyl :-),
Al

... Don't worry, I'm go*ng t* b*ckup t*d*µ!&%#~%
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello fang-castro,

pktinfo tells me that the fromusername field is empty so the message header is wrong. It is a corrupt packet.

pktdump says the packet is corrupt because of the datetime field.

Either way, that packet is stinky!

Ttyl :-),
Al

... Oh no, not another learning experience!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

pktinfo tells me that the fromusername field is empty so the message

where do i get pktinfo and pktdump? =)

|08__ _ _ ____ |02_ _ |10___ _ _ |02____ |08_ _ _ ___
|08| \| | |__\ |02|--| |10 | \/ |02|--| |08|__| |___ |

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Nightvault (21:3/112)

pktinfo tells me that the fromusername field is empty so the message
header is wrong. It is a corrupt packet.

It looks like the packet was written correctly, then re-written over two
bytes off.

the Packet header ends 02 00 which should be (00 00) then is followed by
02 00 which is the start of the packed message header. Then each field is
also offset by 2 bytes...

It looks like it's to David Smit? (I guess david smith) so the TO field
should look like

David Smith<NULL>

but instead looks like

DaDavid Smit

The from looks like

DaDaryl Stou

When it should be

Daryl Stout<NULL>

And so on...

So while mystic should discard that packet as you say, more concerning is whatever the hub is running causing packets like that?

The message is FROM a synchronet system, but I suspect it's not
synchronet to blame but whatever is in between.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.27-dev (Windows/x64)
* Origin: The Grinning Cat >^.^< (21:1/182.1)

Hello fang-castro,

where do i get pktinfo and pktdump? =)

pktinfo is part of the husky project. It probably needs a husky configuration to run.

pktdump is part of Synchronet. There is a windows build available for download from Vertrauen.

You can grab my copy here..

http://trmb.synchro.net

It relies on glibc-2.33.

Ttyl :-),
Al

... I'm not dead. I'm electroencephelographically challenged.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello fang-castro,

You can grab my copy here..

http://trmb.synchro.net

I forgot the good part..

http://trmb.synchro.net/pktdump

I am running slackware-current here so it is very up to date and it may not run on other OSs that don't include glibc-2.33.

Ttyl :-),
Al

... If love is blind, why is Lingerie so popular?
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello apam,

pktinfo tells me that the fromusername field is empty so the
message header is wrong. It is a corrupt packet.

It looks like the packet was written correctly, then re-written over
two bytes off.

Yep, stuff does happen sometimes.. :)

So while mystic should discard that packet as you say,

Yes, just put it aside or something..

more concerning is whatever the hub is running causing packets like
that?

Yes, packets like that will not do anyone or any tosser any good.

The message is FROM a synchronet system, but I suspect it's not
synchronet to blame but whatever is in between.

I doubt it too. I toss packets to and from Synchronet all day. I've never had any issues with a Synchronet produced packet.

Ttyl :-),
Al

... Everybody lies, but it doesn't matter, cuz nobody listens
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello Al,

http://trmb.synchro.net/pktdump

There is also pktview. It is a perl script. I run it like this..

perl /path/to/pktview <90F59CFC.PKT

Don't forget the "<" before the packet name. It's old but still useful.

http://trmb.synchro.net/pktview

Ttyl :-),
Al

... A sense of humour is the difference between ambition and achievement
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Yes, packets like that will not do anyone or any tosser any good.

Hehe yep, it's an interesting puzzle though. I think the hobby net bbs is
a Wildcat board, so I guess one can't load up the source and see whats
going on. I don't even know who you'd go to to report a wildcat bug.

When I ran that packet through postie, it decided it was an empty netmail
and threw it away, probably not the best way to go either lol

I doubt it too. I toss packets to and from Synchronet all day. I've
never had any issues with a Synchronet produced packet.

Yeah, if it were a synchronet bug I would imagine it would be picked up
pretty quickly too, being so many of them around.

Oh well, I was hoping the packet was one similar to what has been
crashing postie lately, but it was not.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.27-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

Hello fang-castro,

You can grab my copy here..

Thanks for everything!

=)
fc

|08__ _ _ ____ |02_ _ |10___ _ _ |02____ |08_ _ _ ___
|08| \| | |__\ |02|--| |10 | \/ |02|--| |08|__| |___ |

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Nightvault (21:3/112)

You can grab my copy here..

http://trmb.synchro.net/pktdump

Hey thanks for this. Hope you don't mind that I grabbed it as well.

I have a separate problem of my own where Mystic is choking on a packet and it ran fine on my Ubuntu system.

Opening ./9FC80759.PKT
./9FC80759.PKT Packet Type 2+ (prod: 0111, rev: 3.0) from 954:895/1 to 954:895/31
./9FC80759.PKT 00003A Corrupted Message Header (DateTime)

I preserved this and posted it to the Fidonet Mystic echo, where hopefully a more graceful failure can be included in a future version.

--- Mystic BBS v1.12 A47 2021/09/24 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

I preserved this and posted it to the Fidonet Mystic echo, where
hopefully a more graceful failure can be included in a future version.

Interestingly, it's similar to the packet fang castro posted, both posted
by daryl stout, both on hobbynet and both have the off by 2 bytes thing
in the message header.

There appears to be only one line in the PATH: 895/7 (daryl's node) is he
the hub for you two on hobby net?

Strange.

Andrew

--
|03Andrew Pamment |08(|11apam|08)
|13Happy|10Land |14v2.0|08!|07


--- Talisman v0.27-dev (Linux/x86_64)
* Origin: HappyLand v2.0 - telnet://happylandbbs.com:11892/ (21:1/182)

There appears to be only one line in the PATH: 895/7 (daryl's node) is he the hub for you two on hobby net?

For me, Michael Dippel / hobbylinebbs.com is my hub. (954:895/1).

--- Mystic BBS v1.12 A47 2021/09/24 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

On 23 Oct 2021, fang-castro said the following...

I noticed there wasn't any new echomail msgs in a while and I found this li'l stinker.. deleted 90F59CFC.PKT and back to good, but why would this happen?

I had something similar from Hobbynet come through here:

----------------- MUTIL v1.12 A47 2021/09/29 Tue, Oct 19 2021 (loglevel 2)
+ Oct 19 19:06:18 Startup using mailin.ini
+ Oct 19 19:06:18 Process: Toss FDN/TIC Files
+ Oct 19 19:06:18 Waiting for BUSY nodes
+ Oct 19 19:06:18 Scanning Hatches
+ Oct 19 19:06:18 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.01s
+ Oct 19 19:06:18 Process: Importing EchoMail
+ Oct 19 19:06:18 Waiting for BUSY nodes
+ Oct 19 19:06:19 Extracting 512A62CA.TU1
+ Oct 19 19:06:19 Importing 90F59CDD.PKT (954:895/1 to 954:895/27)
+ Oct 19 19:06:19 Shutdown Corrupted memory (216)


(Thanks Al for the pktview program)

pi@bbs:/tmp $ perl ./pktview < ./90F59CDD.PKT
Version:2+
From: 954:895/1.0 20/10/2021 19: 3:35
To : 954:895/27.0
Prodcode : 273 (3.0)
Password : `' ----------------------------------------------------------------------------- Warning: Bad field(s) length (too long)
[ snip ]
To : , 895/27
Subj: --Loc--------------------------------------------------------------------[]--


If anyone wants a copy of 512A62CA.TU1:

https://drive.google.com/file/d/1OUXGp6XSj9LZUUv9VhTrzfd9GW1aljUw/


Jay

... When your work speaks for itself, don`t interrupt.

--- Mystic BBS v1.12 A47 2021/09/29 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

pktinfo tells me that the fromusername field is empty so the message header is wrong. It is a corrupt packet.

I would suggest that fix the tosser so if that happens it defaults to ALL.
---

Legends of Yesteryear (FIDO 1:123/256) - telnet: furmenservices.net:23322

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Legends of Yesteryear (furmenservices.net:23322) (21:4/102)

Hello DustCouncil,

http://trmb.synchro.net/pktdump

Hey thanks for this. Hope you don't mind that I grabbed it as well.

No problem. Those were all put together by different folks so sysops could get a better idea of what is causing problems.

I have a separate problem of my own where Mystic is choking on a
packet and it ran fine on my Ubuntu system.

Opening ./9FC80759.PKT
./9FC80759.PKT Packet Type 2+ (prod: 0111, rev: 3.0) from 954:895/1 to 954:895/31 ./9FC80759.PKT 00003A Corrupted Message Header (DateTime)

That looks like the same issue that fang-castro was seeing, maybe the same message. Something is bad about those packets.. it may or may not be the date.

I preserved this and posted it to the Fidonet Mystic echo, where
hopefully a more graceful failure can be included in a future version.

That would be a good thing. Should send a copy to the original node also so they know something is up. Something will need to be adjusted there also.

Ttyl :-),
Al

... Love is grand. Divorce is fifty grand
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello Geri,

pktinfo tells me that the fromusername field is empty so the
message header is wrong. It is a corrupt packet.

I would suggest that fix the tosser so if that happens it defaults to
ALL.

Every tosser in use would need to be updated to do that and I don't think that will happen.

Packets are not very forgiving. They are mostly message text but they are binary files and all those bits & bytes must be correct or the show is off.

The best solution is to create those packets correctly in the first place or they will fail downstream differently for different tossers.

Ttyl :-),
Al

... Alpo is 99 cents per can -- that's almost 7 dog dollars!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

pktinfo tells me that the fromusername field is empty so the
message header is wrong. It is a corrupt packet.

I would suggest that fix the tosser so if that happens it defaults to ALL.

Every tosser in use would need to be updated to do that and I don't
think that will happen.

No, especially since the pktinfo isn't exactly right, the packet is corrupt, that was just the first thing it tripped up on (the fromusername wasn't null terminated) even if you changed from to ALL, it would then have tripped up on the to field being empty, the subject being empty and the entire message being empty because of no null termination between from, to and subject.

A tosser shouldn't attempt to fix a packet, the other tosser shouldn't create dodgy packets.

I think in this instance, mystic tosser needs to be fixed to not segfault on a dodgy packet, and Platnium Xpress or whatever hobby net is using needs to be fixed to not create dodgy packets in the first place.

Andrew

... The only place I want data loss is on my credit card!

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hello apam,

No, especially since the pktinfo isn't exactly right, the packet is corrupt, that was just the first thing it tripped up on (the
fromusername wasn't null terminated) even if you changed from to ALL,
it would then have tripped up on the to field being empty, the subject being empty and the entire message being empty because of no null termination between from, to and subject.

Absolutely. If tossers were trying to fix errors we'd be in a hellofa mess.

A tosser shouldn't attempt to fix a packet, the other tosser shouldn't create dodgy packets.

Yep, a bad packet will trip everyone up all down the line.

I think in this instance, mystic tosser needs to be fixed to not
segfault on a dodgy packet, and Platnium Xpress or whatever hobby net
is using needs to be fixed to not create dodgy packets in the first
place.

Looking at the product code it looks like newsgate may have created that packet, but I have no way to know for sure.

I have no links running Platinum Xpress, never did that I recall so I don't know how well it does or doesn't work. Hopefully they can find a way to get those bad packets out of the flow.

Ttyl :-),
Al

... SHIN: A device for finding furniture in the dark!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Just an update: g00r00 snarfed the bad ones, and will have it fixed in the next version so that at least it doesn't crash on it (he replied on FidoNet).

I will see if I can take up the packet format with its origin when I get a moment.

--- Mystic BBS v1.12 A47 2021/09/24 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)