Hello all. I am baffled on this one. I am currently running the latest pre-alpha however was having this same issue with the previous version. I have three FTN's configured.. Two of which are working great.

However this third one is having an issue. I am able to poll, send/receive the hub. But when I receive and it tries to process, poll gives me the following error:

+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156

This I do not understand, as it is clearly configured under the echomail nodes.

Any help would be greatly appreciated!

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156

This I do not understand, as it is clearly configured under the echomail nodes.

It seems there is a small error in the message text there which I've just fixed up.

That error means that you have a password set in your entry for 46:1/156 but the PKT file itself did not have the password you configured.

(Or it means you have no active configuration for 46:1/156 but you've already mentinoned that you do).

In the next build it will properly report "PKT password does not match password set for 46:1/156".

... What was the best thing before sliced bread?

--- Mystic BBS v1.12 A47 2021/08/17 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On Saturday, August 21, 2021 at 10:20:30 AM UTC-5, g00r00 wrote:

+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156

This I do not understand, as it is clearly configured under the echomail nodes.

It seems there is a small error in the message text there which I've just fixed
up.

That error means that you have a password set in your entry for 46:1/156 but the PKT file itself did not have the password you configured.

(Or it means you have no active configuration for 46:1/156 but you've already
mentinoned that you do).

In the next build it will properly report "PKT password does not match password
set for 46:1/156".

... What was the best thing before sliced bread?

Thank you for the reply, g00r00! I woke up to an email from the hub operator that he normally doesn't setup a PKT password unless asked. Funny, it was on the application. Anyhow, rant off.. ;) It is working as expected now, and thank you for all your
hard work! Now to go finish reading the whatsnew file.. so many updates! WOO!

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156

I think it's saying that you don't have any configuration for 46:1/156 in your node list. What is 46:1/156? your node or the hub node?

... My tagline could eat your tagline for breakfast
--- Mystic BBS v1.12 A47 2021/08/10 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (2:250/5)

On Monday, August 23, 2021 at 9:20:21 AM UTC-5, Christian Sacks wrote:

+ Aug 21 06:16:08 Importing 5691629c.pkt (46:1/156 to 46:10/196)
! Aug 21 06:16:08 PKT Password found but no configuration for 46:1/156

I think it's saying that you don't have any configuration for 46:1/156 in your
node list. What is 46:1/156? your node or the hub node?

... My tagline could eat your tagline for breakfast

It ended up being that I had a PKT password set, but the hub did not. All good now =)

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)