I am having a problem with netmail.
Every time I send a netmail, I get a failed password error before the mail even goes out. When it goes out, everything works fine. I have spoken with Alan (my hub) and he can't explain it either. Anyone have any idea why this is happening? Any help is appreciated

Greg
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

This is what I am seeing:


JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 167772160 bytes

Reading script from C:\sbbs\exec\binkit.js
C:\sbbs\exec\binkit.js compiled in 0.00 seconds
BinkIT/2.41 invoked with options: -p
Attempting callout for 1:153/757, file: C:\sbbs\fido\outbound\009902f5.cut JSBinkP/4 callout to 1:153/757 started
Connecting to 1:153/757@fidonet at f757.n153.z1.binkp.net:24554
Peer version: BBBS/Li6 v4.10 Toy-7
BinkP got fatal error 'Invalid password' from remote: 1:153/757@fidonet,1:153/0@fidonet,21:4/106@fsxnet,25:25/31@metronet
Attempting poll for node 1:153/757@fidonet
JSBinkP/4 callout to 1:153/757@fidonet started
Connecting to 1:153/757@fidonet at f757.n153.z1.binkp.net:24554
Peer version: BBBS/Li6 v4.10 Toy-7
Authentication successful:
Sending file: C:\sbbs\fido\outbound\009902f5.cut (0.7KB)
Sent file: C:\sbbs\fido\outbound\009902f5.cut (0.7KB)
Deleted file: C:\sbbs\fido\outbound\009902f5.cut
C:\sbbs\exec\binkit.js executed in 5.47 seconds

Sorry, forgot to add this to the original message.
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

Re: failed password
By: Greg Meckel to All on Mon Mar 24 2025 07:27 pm

This is what I am seeing:

JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 167772160 bytes

Reading script from C:\sbbs\exec\binkit.js
C:\sbbs\exec\binkit.js compiled in 0.00 seconds
BinkIT/2.41 invoked with options: -p
Attempting callout for 1:153/757, file: C:\sbbs\fido\outbound\009902f5.cut JSBinkP/4 callout to 1:153/757 started
Connecting to 1:153/757@fidonet at f757.n153.z1.binkp.net:24554
Peer version: BBBS/Li6 v4.10 Toy-7
BinkP got fatal error 'Invalid password' from remote: 1:153/757@fidonet,1:153/0@fidonet,21:4/106@fsxnet,25:25/31@metronet

Do you multiple linked-addresses for this same linked-node (e.g. in sbbsecho.ini / echocfg)? If so, are they all using the same password?

BinkP has some funky stuff with passwords and identities when multiple addresses (AKAs) are used and it's possible that when you receive an inbound BinkP connection, a different password is being expected/used than when you make an outbound connection to the same linked-node. Double check your configuration.
--
digital man (rob)

Sling Blade quote #6:
Karl: he should've had a chance to grow up. He would had fun some time.
Norco, CA WX: 62.1°F, 70.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs

Re: failed password
By: Digital Man to Greg Meckel on Mon Mar 24 2025 09:26 pm

Re: failed password
By: Greg Meckel to All on Mon Mar 24 2025 07:27 pm

Do you multiple linked-addresses for this same linked-node (e.g. in sbbsecho.ini / echocfg)? If so, are they all using the same password?

BinkP has some funky stuff with passwords and identities when multiple addresses (AKAs) are used and it's possible that when you receive an inbound BinkP connection, a different password is being expected/used than when you make an outbound connection to the same linked-node. Double check your configuration.

I only have 1 linked node and only 1 linked address. Passwords are the same in sbbsecho.ini and echocfg.
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

I had the same problem Im my sbbsecho.ini file I removed the "@fidonet" in the nodes setup area. That fix the problem. Instead of [Node 1:229/426@fidonet] I changed my uplinks setting to [Node 1:229/426]
Worked after that.

RickV

--- Mystic BBS v1.12 A49 2023/01/28 (Windows/64)
* Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (1:154/110)

Re: failed password
By: Greg Meckel to Digital Man on Tue Mar 25 2025 07:19 am

Do you multiple linked-addresses for this same linked-node (e.g. in sbbsecho.ini / echocfg)? If so, are they all using the same password?

BinkP has some funky stuff with passwords and identities when multiple addresses (AKAs) are used and it's possible that when you receive an inbound BinkP connection, a different password is being expected/used than when you make an outbound connection to the same linked-node. Double check your configuration.

I only have 1 linked node and only 1 linked address. Passwords are the same in sbbsecho.ini and echocfg.

And you only have one address in SCFG->Networks->FidoNet->System Addresses?

Another possibility is a mismatch between 3D and 4D/5D addresses (e.g. 1:2/3 and 1:2/3@fidonet are not the same address in all scenarios).
--
digital man (rob)

Steven Wright quote #6:
A conscience is what hurts when all your other parts feel so good.
Norco, CA WX: 79.6°F, 39.0% humidity, 11 mph W wind, 0.00 inches rain/24hrs

Re: Re: failed password
By: Richard Vonzel to Greg Meckel on Tue Mar 25 2025 11:56 am

I had the same problem Im my sbbsecho.ini file I removed the "@fidonet" in the nodes setup area. That fix the problem. Instead of [Node 1:229/426@fidonet] I changed my uplinks setting to [Node 1:229/426]
Worked after that.

RickV

Thanks Rick. I will try that and hope it works

Greg
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

Re: failed password
By: Digital Man to Greg Meckel on Tue Mar 25 2025 02:02 pm

Re: failed password
By: Greg Meckel to Digital Man on Tue Mar 25 2025 07:19 am

Do you multiple linked-addresses for this same linked-node (e.g. in sbbsecho.ini / echocfg)? If so, are they all using the same password?

BinkP has some funky stuff with passwords and identities when multiple addresses (AKAs) are used and it's possible that when you receive an inbound BinkP connection, a different password is being expected/used than when you make an outbound connection to the same linked-node. Double check your configuration.

I only have 1 linked node and only 1 linked address. Passwords are the same in sbbsecho.ini and echocfg.

And you only have one address in SCFG->Networks->FidoNet->System Addresses?

Another possibility is a mismatch between 3D and 4D/5D addresses (e.g. 1:2/3 and 1:2/3@fidonet are not the same address in all scenarios).

The only system address I have is my own system address 1:153/143
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

Re: Re: failed password
By: Greg Meckel to Richard Vonzel on Tue Mar 25 2025 04:00 pm

Re: Re: failed password
By: Richard Vonzel to Greg Meckel on Tue Mar 25 2025 11:56 am

I had the same problem Im my sbbsecho.ini file I removed the "@fidonet" in the nodes setup area. That fix the problem. Instead of [Node 1:229/426@fidonet] I changed my uplinks setting to [Node 1:229/426] Worked after that.

RickV

Thanks Rick. I will try that and hope it works

Greg

That did not work either but thanks anyway
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

Re: Re: failed password
By: Greg Meckel to Richard Vonzel on Tue Mar 25 2025 04:36 pm

Thanks Rick. I will try that and hope it works

Greg

That did not work either but thanks anyway

i'm no expert on this stuff but then again i have been connected to fidonet and other ftns with no issues. i would recommend checking your work and even ripping it all out and starting over. it's just a matter of getting the numbers right. make sure your feed is working correctly and after that if you have issues it's operator error.
---
■ Synchronet ■ ::: BBSES.info - free BBS services :::

That did not work either but thanks anyway

I am sorry if you already did so and I missed it, but could you post the
output from one of these failed connects?


* SLMR 2.1a * Pass the tequila, Manuel...
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Re: failed password
By: MRO to Greg Meckel on Wed Mar 26 2025 12:13 am

Re: Re: failed password
By: Greg Meckel to Richard Vonzel on Tue Mar 25 2025 04:36 pm

i'm no expert on this stuff but then again i have been connected to fidonet and other ftns with no issues. i would recommend checking your work and even ripping it all out and starting over. it's just a matter of getting the numbers right. make sure your feed is working correctly and after that if you have issues it's operator error.

I'm pretty sure it's probably operator error anyway. LOL
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

Re: Re: failed password
By: Greg Meckel to MRO on Wed Mar 26 2025 07:27 am

Re: Re: failed password
By: MRO to Greg Meckel on Wed Mar 26 2025 12:13 am

Re: Re: failed password
By: Greg Meckel to Richard Vonzel on Tue Mar 25 2025 04:36 pm

i'm no expert on this stuff but then again i have been connected to fidonet and other ftns with no issues. i would recommend checking your work and even ripping it all out and starting over. it's just a matter of getting the numbers right. make sure your feed is working correctly and after that if you have issues it's operator error.

I'm pretty sure it's probably operator error anyway. LOL

we all make mistakes. especially when we are rushing... or working on computers drunk!

I used to have ssh windows open for several servers and i'd be going so fast that i'd make the change on the wrong server.
---
■ Synchronet ■ ::: BBSES.info - free BBS services :::

Re: Re: failed password
By: MRO to Greg Meckel on Wed Mar 26 2025 01:17 pm

Re: Re: failed password
By: Greg Meckel to MRO on Wed Mar 26 2025 07:27 am

Re: Re: failed password
By: MRO to Greg Meckel on Wed Mar 26 2025 12:13 am

Re: Re: failed password
By: Greg Meckel to Richard Vonzel on Tue Mar 25 2025 04:36 pm

I'm pretty sure it's probably operator error anyway. LOL

we all make mistakes. especially when we are rushing... or working on computers drunk!

I used to have ssh windows open for several servers and i'd be going so fast that i'd make the change on the wrong server.

Well, I haven't been rushing and I quit drinking 29 years ago, so I'm pretty sure it wasn't that.
--- SBBSecho 3.23-Win32
* Origin: Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net (1:153/143)

From Newsgroup: alt.bbs.synchronet

+ User FidoNet address: 1:396/4
From: "Greg Meckel" <greg.meckel@THEICECA.remove-odc-this>

To: MRO
Re: Re: failed password
By: MRO to Greg Meckel on Wed Mar 26 2025 12:13 am

Re: Re: failed password
By: Greg Meckel to Richard Vonzel on Tue Mar 25 2025 04:36 pm

i'm no expert on this stuff but then again i have been connected to fidonet and other ftns with no issues. i would recommend checking your work and even ripping it all out and starting over. it's just a matter of getting the numbers right. make sure your feed is working correctly and after that if you have issues it's operator error.

I'm pretty sure it's probably operator error anyway. LOL
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net
--- Synchronet 3.20e-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ The FidoNet News Gate (Huntsville, AL - USA) +
+ The views of this user are strictly his or her own. + +++++++++++++++++++++++++++++++++++++++++++++++++++++++

---
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

--- Synchronet 3.20e-Linux NewsLink 1.2

Re: Re: failed password
By: Dumas Walker to GREG MECKEL on Wed Mar 26 2025 08:38 am

That did not work either but thanks anyway

I am sorry if you already did so and I missed it, but could you post the output from one of these failed connects?

* SLMR 2.1a * Pass the tequila, Manuel...

See message 1094

The connect eventually works, but not until after it throws the invalid password error
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

That did not work either but thanks anyway

I am sorry if you already did so and I missed it, but could you post the output from one of these failed connects?

See message 1094

The connect eventually works, but not until after it throws the invalid password error

IIRC, I get invalid password errors from some connections when there is no
mail to send or receive. I also see inbound connections where that
happens. I have a node that, for whatever reason, calls twice -- one right after the other. The first one works like normal but, because the node
just picked up their mail, the second one shows an invalid password error.

Not sure what causes that but as long as the mail is moving I usually
ignore it.


* SLMR 2.1a * "Mmmmmmmm.....doughnuts."
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Re: failed password
By: Dumas Walker to GREG MECKEL on Thu Mar 27 2025 09:01 am

happens. I have a node that, for whatever reason, calls twice -- one right after the other. The first one works like normal but, because the node
just picked up their mail, the second one shows an invalid password error.

Not sure what causes that but as long as the mail is moving I usually
ignore it.

you could ALWAYS tell the guy.
---
■ Synchronet ■ ::: BBSES.info - free BBS services :::

I still have not gotten the problem with the failed password fixed, but at least I am not having the error messages pop up every time I log in to the BBS
Thanks to everyone for your help.

Greg
---
■ Synchronet ■ Ice Castle BBS, Anchorage, AK - ice-castle-bbs.net

Re: failed password
By: Greg Meckel to All on Thu Mar 27 2025 10:18 am

I still have not gotten the problem with the failed password fixed, but at least I am not having the error messages pop up every time I log in to the BBS Thanks to everyone for your help.

Greg

talk to your feed and see if there's an issue on his end.
maybe he has more info from HIS logs.
---
■ Synchronet ■ ::: BBSES.info - free BBS services :::

happens. I have a node that, for whatever reason, calls twice -- one right
after the other. The first one works like normal but, because the node just picked up their mail, the second one shows an invalid password error.

Not sure what causes that but as long as the mail is moving I usually ignore it.

you could ALWAYS tell the guy.

Pretty sure I did. I have not checked lately so it may not even be
happening any more.


* SLMR 2.1a * ....we came in?
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP