Greetings All!

On one of my bbs's (mystic) I use hpt/binkd for the mailer. I have had points off of that system before in the past and set it up like any other downlink. I decided to try aftershock (android app) and while hpt packs mail for that point and I can pick it up from the phone, everything composed on the phone never makes it back to the echo's. So I tried a areafix message, it went to the bbs, bbs responded "your an unknown system" ??? So I figured (like maybe your are) this aftershock program must be the culprit. So on my laptop I setup a hpt/binkd/golded point, and I get the exact same behavior. I get no error messages in either hpt or binkd that I can find. There is no mail in unsecure dir or bad etc.

Would love some guesses!



----
Regards,


Rick Smith (Nitro)

... recipes..........The bumper stickers of BBSing
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

On one of my bbs's (mystic) I use hpt/binkd for the mailer.

So hpt is your tosser and binkd is your mailer and Mystic (mutil) is not being used?

I have had points off of that system before in the past and set it up like any other downlink. I decided to try aftershock (android app) and while hpt

packs mail for that point and I can pick it up from the phone, everything composed on the phone never makes it back to the echo's. So I tried a areafix message, it went to the bbs responded "your an unknown system" ???

This is your problem. Where do you see this "unknown system" message?

It must be coming from hpt?? Have a look at hpt's logs from the time the message is written and see why it's an unknown system.

So I figured (like maybe your are) this aftershock program must be the culprit.

I don't think so. I am using AfterShock with BBBS currently and it works as expected. When I first started using AfterShock I was running binkd and hpt and it worked for me with that setup also.

So on my laptop I setup a hpt/binkd/golded point, and I get the exact same behavior. I get no error messages in either hpt or binkd that I can find.

Your issue seems to originate on the boss side of it. Turn up your loglevel on hpt so it will (hopefully) give a clear indication of why it thinks this is an "unknown system".

Would love some guesses!

I couldn't even guess.. but I hope you can solve it. :)

----
Regards,

Rick Smith (Nitro)

... recipes..........The bumper stickers of BBSing

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Greetings Alan!

Monday April 24 2023 08:43, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'

On one of my bbs's (mystic) I use hpt/binkd for the mailer.

So hpt is your tosser and binkd is your mailer and Mystic (mutil) is
not being used?

Your issue seems to originate on the boss side of it. Turn up your loglevel on hpt so it will (hopefully) give a clear indication of why
it thinks this is an "unknown system".

its weird as I have run this point on this setup previously, I just went into my links file and uncommented out the point, it should work, unless I am forgetting something somewhere (which clearly must be). The logs are on full, so I will try to simulate it again..


----
Regards,


Rick Smith (Nitro)

... TAGLINE A BBS addict is hooked when: you consider BBSing better than chocolat
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Greetings Alan!

Monday April 24 2023 08:43, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'

On one of my bbs's (mystic) I use hpt/binkd for the mailer.

So hpt is your tosser and binkd is your mailer and Mystic (mutil) is
not being used?

so far I see only these errors

pkt: /mystic/tmp.in/64383eeb.tos No Link for 1:105/10.1, processing only Netmail

although I have the point in my links file

7 20:08:36 pkt: /mystic/echomail/in/64386143.tos [1:105/10.1]
A 20:08:36 pkt: /mystic/echomail/in/64386143.tos No Link for 1:105/10.1, processing only Netmail
8 20:08:37 areafix: Security violation from 1:105/10.1

Likely explains the "unknown system" However I do not know why this error is happening... I will post my links entry below.

Link Fido point
aka 1:105/10.1
ouraka 1:105/10
password ******
areafixpwd ******
pktpwd *******
EchoMailFlavour Hold
fileEchoFlavour Hold
NetMailFlavour Crash
packer Zip
LinkGrp F


----
Regards,


Rick Smith (Nitro)

... Taglines: the <real< reason for BBSing.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Hello Rick,

Monday April 24 2023, Rick Smith wrote to Alan Ianson:

On one of my bbs's (mystic) I use hpt/binkd for the mailer.

So hpt is your tosser and binkd is your mailer and Mystic (mutil)
is not being used?

so far I see only these errors

pkt: /mystic/tmp.in/64383eeb.tos No Link for 1:105/10.1, processing
only Netmail

although I have the point in my links file

7 20:08:36 pkt: /mystic/echomail/in/64386143.tos [1:105/10.1]
A 20:08:36 pkt: /mystic/echomail/in/64386143.tos No Link for
1:105/10.1, processing only Netmail
8 20:08:37 areafix: Security violation from 1:105/10.1

^^^^^^^^^^^^^^^^^^

Likely explains the "unknown system" However I do not know why this
error is happening... I will post my links entry below.

Link Fido point
aka 1:105/10.1
ouraka 1:105/10
password ******

^^^^^^^^^^^^^^^
Try to comment this out.

areafixpwd ******
pktpwd *******
EchoMailFlavour Hold
fileEchoFlavour Hold
NetMailFlavour Crash
packer Zip
LinkGrp F

----
Regards,

Rick Smith (Nitro)

... Taglines: the <real< reason for BBSing.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230221
* Origin: Moscow, Russia (2:5020/1042)

Greetings Michael!

Monday April 24 2023 23:30, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'
Hello Rick,

Monday April 24 2023, Rick Smith wrote to Alan Ianson:

On one of my bbs's (mystic) I use hpt/binkd for the mailer.

So hpt is your tosser and binkd is your mailer and Mystic
(mutil) is not being used?

so far I see only these errors

pkt: /mystic/tmp.in/64383eeb.tos No Link for 1:105/10.1,
processing only Netmail

although I have the point in my links file

7 20:08:36 pkt: /mystic/echomail/in/64386143.tos [1:105/10.1]
A 20:08:36 pkt: /mystic/echomail/in/64386143.tos No Link for
1:105/10.1, processing only Netmail
8 20:08:37 areafix: Security violation from 1:105/10.1

^^^^^^^^^^^^^^^^^^

Likely explains the "unknown system" However I do not know why
this error is happening... I will post my links entry below.

Link Fido point
aka 1:105/10.1
ouraka 1:105/10
password ******

^^^^^^^^^^^^^^^
Try to comment this out.

sadly this didnt help
----
Regards,


Rick Smith (Nitro)

... A job is nice, but it interferes with BBSing.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Hello Rick!

24 Apr 23, Rick Smith wrote to Alan Ianson:

although I have the point in my links file

A 20:08:36 pkt: /mystic/echomail/in/64386143.tos No Link for
1:105/10.1,

Remove/comment the link definition, see if log changes.
Rebuild the link config line per line.

Link Fido point

Are spaces allowed there?

Non-ASCII password? Sometimes there are charset mismatches.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Greetings Kai!

Wednesday April 26 2023 12:55, you wrote to me about an urgent matter!:

Hello Rick!

24 Apr 23, Rick Smith wrote to Alan Ianson:

although I have the point in my links file

A 20:08:36 pkt: /mystic/echomail/in/64386143.tos No Link for
1:105/10.1,

Remove/comment the link definition, see if log changes.
Rebuild the link config line per line.

Link Fido point

Are spaces allowed there?

I believe so yes, I just uncommented this area when I wanted to start using point again, it worked just as it is last year.

I found the packets that got renamed to .sec and put in unsecure folded so I ran pktinfo on them and here are the results..

PktInfo/lnx 1.9 2023-01-07

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

A 08:41:51 Invalid pkt version 0!
0069000a.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 46d19900.sec
PktInfo/lnx 1.9 2023-01-07

A 08:42:05 Invalid pkt version 325!
46d19900.sec: Corrupt packet



----
Regards,


Rick Smith (Nitro)

... There's a fine line between BBSing and beebling
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

I found the packets that got renamed to .sec and put in unsecure folded so I ran pktinfo on them and here are the results..

PktInfo/lnx 1.9 2023-01-07

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

This is a problem. I just joined this area from my own AfterShock setup so I'll post a message from there is a few minutes and we'll see if it makes the trip.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

This is a problem. I just joined this area from my own AfterShock setup so I'll post a message from there is a few minutes and we'll see if it makes the trip.

This is just a reply to test AfterShock.

Ttyl :-),
Al

--- AfterShock/Android 1.7.4
* Origin: The Rusty Point - Penticton, BC Canada (1:153/757.1)

I found the packets that got renamed to .sec and put in unsecure folded so I ran pktinfo on them and here are the results..

PktInfo/lnx 1.9 2023-01-07

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

I don't see that here. Here is what pktinfo says about a packet created at my point..

alan [ ~ ]$ pktinfo -h 64495166.pkt PktInfo/lnx 1.9 2023-02-24

Packet header ============================================================================== Filename : 64495166.pkt
OrigAddr : 1:153/757.1
DestAddr : 1:153/757.0
AuxNet : 0
CapWord : 0x0001
DateCreation : Wed 2023-04-26 10:29:26
Password : "SECRET"
ProdCode : 1bff
ProdVersion : 0.1

Message header ------------------------------------------------------------------------------ From : "Alan Ianson"
To : "All"
Subject : "Test post"
DateTime : "26 Apr 23 09:29:20"
Attr : 0x0008 -> Sent
OrigAddr : 153/757
DestAddr : 153/757

Can you examine one of those packets before you toss it?

Hopefully you'll get a similar result.

I'm not sure what is causing your bad packets, but that is the cause of your issue.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

26 Apr 2023 08:42, you wrote to Kai Richter:

I found the packets that got renamed to .sec and put in unsecure
folded so I ran pktinfo on them and here are the results..

PktInfo/lnx 1.9 2023-01-07

[...]

A 08:42:05 Invalid pkt version 325!
46d19900.sec: Corrupt packet

Could it be that those are not .PKT's, but zipfiles? AfterShock sends echomail in compressed bundles.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Greetings Alan!

Wednesday April 26 2023 09:46, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'

I found the packets that got renamed to .sec and put in unsecure
folded so I ran pktinfo on them and here are the results..

PktInfo/lnx 1.9 2023-01-07

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

I don't see that here. Here is what pktinfo says about a packet
created at my point..

This is so bizarre I have run points of this setup in the past with these exact cfgs, I just commented them out when I stopped using the point. Is it possible that updated or changed code in todays hpt/binkd have broke this somehow? I did move the BBS to a different server about three months ago so I did a fresh build of hpt/binkd. I set up binkd/hpt on my linux laptop and I get the same problems that I have with aftershock so it is for sure my mystic bbs setup that is causing the issue.


----
Regards,


Rick Smith (Nitro)

... BBSing is like sex, except for not wanting to get off.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Hello Alan!

Wednesday April 26 2023 09:46, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'

I found the packets that got renamed to .sec and put in unsecure
folded so I ran pktinfo on them and here are the results..

PktInfo/lnx 1.9 2023-01-07

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

I don't see that here. Here is what pktinfo says about a packet

Now I have no idea, I tried a new point on synchronet and I get the same behavior...

Regards,

Rick

... I love BBSing: All the social dynamics of pre-school!
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

I would check that that 0069000a.sec is a plain packet and not a compressed mail bundle as Carlos suggested. If it is a mail bundle you may need to decompress it.

I don't see that here. Here is what pktinfo says about a packet

Now I have no idea, I tried a new point on synchronet and I get the same behavior...

I would suggest that you grab fresh husky source from github and rebuild just to be sure your husky tools are up to date.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan!

Saturday April 29 2023 18:28, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

I would check that that 0069000a.sec is a plain packet and not a compressed mail bundle as Carlos suggested. If it is a mail bundle you
may need to decompress it.

I don't see that here. Here is what pktinfo says about a packet

Now I have no idea, I tried a new point on synchronet and I get the
same behavior...

I would suggest that you grab fresh husky source from github and
rebuild just to be sure your husky tools are up to date.

I think that it is something to do with archivers perhaps? On the mystic system I unzipped all the .sec files and they were indeed pkt's and hpt tossed them just fine. On the synchronet test it renames them to .bad and I am unable to unarchive those to test.

Regards,

Rick

... Recipes: the bumper stickers of BBSing.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

I think that it is something to do with archivers perhaps? On the mystic system I unzipped all the .sec files and they were indeed pkt's and hpt tossed them just fine.

Good, I saw your test messages in the aftershock area.

It may be your archiver setup that is causing the issue so have a look at that.

On the synchronet test it renames them to .bad and I am unable to unarchive those to test.

Those might be plain packets already, so check the log and see if there is a different issue with those. A missing or unexpected password perhaps.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan!

Sunday April 30 2023 08:19, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'

I think that it is something to do with archivers perhaps? On the
mystic system I unzipped all the .sec files and they were indeed
pkt's and hpt tossed them just fine.

Good, I saw your test messages in the aftershock area.

It may be your archiver setup that is causing the issue so have a look
at that.

On the synchronet test it renames them to .bad and I am unable to
unarchive those to test.

Those might be plain packets already, so check the log and see if
there is a different issue with those. A missing or unexpected
password perhaps.

ok aftershock is working on the sbbs bbs, so the culprit must be my mystic/hpt/binkd setup..

Regards,

Rick

... BBSing is irrelevent. You will be..A8,1^**7 NO CARRIER
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

ok aftershock is working on the sbbs bbs, so the culprit must be my mystic/hpt/binkd setup..

I think so yes.

Don't lose sight of the actual problem. Why are those packets not tossed as expected?

Hopefully the logs will tell you enough to figure out what you need to do.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Re: point system
By: Rick Smith to Alan Ianson on Sun Apr 30 2023 07:57 am

Hello Alan!

Saturday April 29 2023 18:28, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'

A 08:41:35 Invalid pkt version 272!
47e8bc00.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
PktInfo/lnx 1.9 2023-01-07

I would check that that 0069000a.sec is a plain packet and not a compressed mail bundle as Carlos suggested. If it is a mail bundle you may need to decompress it.

I don't see that here. Here is what pktinfo says about a packet

Now I have no idea, I tried a new point on synchronet and I get the
same behavior...

I would suggest that you grab fresh husky source from github and rebuild just to be sure your husky tools are up to date.

I think that it is something to do with archivers perhaps? On the mystic system I unzipped all the .sec files and they were indeed pkt's and hpt tossed them just fine. On the synchronet test it renames them to .bad and I am unable to unarchive those to test.

If you're able to unzip the file, then it's not a packet, it's a bundle (which will usually contain one or more packets).

The latest builds of SBBSecho can include the *reason* a packet is bad when renaming it (configured in echocfg). Or you can just search the sbbsecho.log for "Bad packet detected" and the log lines before that msg will say *why* the packet file was considered bad.
--
digital man (rob)

This Is Spinal Tap quote #41:
Ian Faith: It says "Memphis show cancelled due to lack of advertising funds." Norco, CA WX: 61.2°F, 86.0% humidity, 8 mph ESE wind, 0.00 inches rain/24hrs

Greetings Alan!

Sunday April 30 2023 10:18, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'

ok aftershock is working on the sbbs bbs, so the culprit must be my
mystic/hpt/binkd setup..

I think so yes.

Don't lose sight of the actual problem. Why are those packets not
tossed as expected?

The laptop setup is back pointing at mystic setup to try and sort this out.. I sent a netmail to areafix from laptop point which is also hpt/binkd/golded, on the mystic system in binkd log I see the netmail received it all looks normal with this exception;

? 30 Apr 18:00:41 [12766] unexpected password digest from the remote

However there is nothing in the hpt log indicating it ever tossed or processed the netmail. I am trying to find where the the packet went.



----
Regards,


Rick Smith (Nitro)

... You know you're hooked when: you consider BBSing better than chocolate
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Greetings Rob!

Sunday April 30 2023 11:05, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'
Re: point system
By: Rick Smith to Alan Ianson on Sun Apr 30 2023 07:57 am

Hello Alan!

Saturday April 29 2023 18:28, you wrote to me:

The latest builds of SBBSecho can include the *reason* a packet is bad when renaming it (configured in echocfg). Or you can just search the sbbsecho.log for "Bad packet detected" and the log lines before that
msg will say *why* the packet file was considered bad.

Thanks DM I was able to sort it out on SBBS and that point is now working as expected, oddly the system (hpt/binkd) I am way more familiar with I cannot get working.. I am sure it is something I am just overlooking.


----
Regards,


Rick Smith (Nitro)

... BBSing is a terminal disease and I have the ANSI strain.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Don't lose sight of the actual problem. Why are those packets not
tossed as expected?

The laptop setup is back pointing at mystic setup to try and sort this out.. sent a netmail to areafix from laptop point which is also hpt/binkd/golded, on the mystic system in binkd log I see the netmail received it all looks normal with this exception;

? 30 Apr 18:00:41 [12766] unexpected password digest from the remote

I think that is a password error in binkd. That would explain why the packets/bundles are renamed to .sec since the session is insecure.

However there is nothing in the hpt log indicating it ever tossed or processed the netmail. I am trying to find where the the packet went.

If I am right (I might not be) that happened when binkd received the file so check your binkd log. Session passwords are case sensitive so "password", "Password" and "PassWord" are all different. Be sure the same password is being used at both ends of the link.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Greetings Alan!

Sunday April 30 2023 11:22, you wrote to me about an urgent matter!:

* Forwarded from area 'FIDOSOFT.HUSKY'

Don't lose sight of the actual problem. Why are those packets not
tossed as expected?

The laptop setup is back pointing at mystic setup to try and sort
this out.. sent a netmail to areafix from laptop point which is also
hpt/binkd/golded, on the mystic system in binkd log I see the
netmail received it all looks normal with this exception;

? 30 Apr 18:00:41 [12766] unexpected password digest from the remote

I think that is a password error in binkd. That would explain why the packets/bundles are renamed to .sec since the session is insecure.

However there is nothing in the hpt log indicating it ever tossed or
processed the netmail. I am trying to find where the the packet
went.

If I am right (I might not be) that happened when binkd received the
file so check your binkd log. Session passwords are case sensitive so "password", "Password" and "PassWord" are all different. Be sure the
same password is being used at both ends of the link.

All passwords match, this is getting more weird tho... If I poll the mystic system from point I can deliver mail which I just found is in the bad area of golded stating I was not active for that area ( I checked my point is active in that area) if I poll the point from mystic machine it delivers mail normally and it gets tossed and auto adds areas not in fidoconfig etc? This is a real head scratcher...


----
Regards,


Rick Smith (Nitro)

... TAGLINE A bad day BBSing is better than a good day at school!
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

? 30 Apr 18:00:41 [12766] unexpected password digest from the remote

I think that is a password error in binkd. That would explain why the
packets/bundles are renamed to .sec since the session is insecure.

However there is nothing in the hpt log indicating it ever tossed or
processed the netmail. I am trying to find where the the packet
went.

If I am right (I might not be) that happened when binkd received the
file so check your binkd log. Session passwords are case sensitive so
"password", "Password" and "PassWord" are all different. Be sure the
same password is being used at both ends of the link.

All passwords match, this is getting more weird tho...

If that is so you need to figure out why you are getting the message "unexpected password digest from remote".

If I poll the mystic system from point I can deliver mail which I just found is in the bad area of golded stating I was not active for that area ( I checked my point is active i that area) if I poll the point from mystic machine it delivers mail normally and it gets tossed and auto adds areas not in fidoconfig etc?

Maybe the area is set to export to your point but your point is not setup with the area yet?

This is a real head scratcher...

Agreed.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)