I have setup a second mystic board, I have everything configured exactly like the other one, but for some reason the echomail is not passing. When looking
at the first board it has the various passwords (such as packets) in lower case, but the new system will not let me do them in lower case. other than
that I see no difference in the way that I have them setup.

Rapid response is greatly appreciated so I can get this fixed ASAP.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

On 09/02/18, Lupine Furmen said the following...

When looking at the first board it has the various passwords (such as packets) in lower case, but the new system will not let me do them in lower case. other than that I see no difference in the way that I have them setup.

Not knowing much other then what I have done, I do know passwords for the networks have to be in CAPS.. At least that is how mine are.. Paul?? :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Not knowing much other then what I have done, I do know passwords for the networks have to be in CAPS.. At least that is how mine are.. Paul?? :)

A38 let you do lower case. A39 does not give the choice, EXCEPT for the
session password. The other three are forced upper case.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

Not knowing much other then what I have done, I do know passwords for networks have to be in CAPS.. At least that is how mine are.. Paul??

A38 let you do lower case. A39 does not give the choice, EXCEPT for the session password. The other three are forced upper case.

Ok, problem seems to be solved. Seems that for some reason windows was not properly loading the PATH variable so the new mystic setup was unable to run zip/unzip.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

On 09/02/18, Lupine Furmen pondered and said...

I have setup a second mystic board, I have everything configured exactly like the other one, but for some reason the echomail is not passing.
When looking at the first board it has the various passwords (such as

So firstly when you say not passing, can you post some logging (level 3
mutil) so show message export, toss and packing etc. from you system to the other system.. what addresses are each etc.

When looking at the first board it has the various passwords (such as packets) in lower case, but the new system will not let me do them in lower case. other than that I see no difference in the way that I have them setup.

Not sure if passwords are in fact the issue, it may be simply not exporting something to a system you think it should be.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 09/02/18, Bucko pondered and said...

Not knowing much other then what I have done, I do know passwords for the networks have to be in CAPS.. At least that is how mine are.. Paul?? :)

My advise is keep all passwords in CAPS and limit them to no more than 8 characters.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 09/02/18, Lupine Furmen pondered and said...

Ok, problem seems to be solved. Seems that for some reason windows was
not properly loading the PATH variable so the new mystic setup was
unable to run zip/unzip.

A good debug test is to set mystic to send uncompressed packets if you
suspect this :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 09-02-18 15:39, Lupine Furmen wrote to Bucko <=-

Not knowing much other then what I have done, I do know passwords for the networks have to be in CAPS.. At least that is how mine are.. Paul?? :)

A38 let you do lower case. A39 does not give the choice, EXCEPT for the session password. The other three are forced upper case.

That makes sense. The session password is case sensitive in the protocol specs, the other passwords are not, so forcing them to uppercase makes sense.


... Put on your seatbelt - I'm gonna try something new!
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)

So when are we going to see posts from your 'Cat here? :) LOL!
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: fsxNet: Omicron Theta * Southaven, MS * winserver.org (21:2/136)

So when are we going to see posts from your 'Cat here? :) LOL!

Which one? I have 4 at last count, occasionally gusting up to 6 depending on who all is over at the time.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

So when are we going to see posts from your 'Cat here? :) LOL!

Which one? I have 4 at last count, occasionally gusting up to 6 depending on who all is over at the time.

Was talking the Wildcat! :)
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: fsxNet: Omicron Theta * Southaven, MS * winserver.org (21:2/136)

Was talking the Wildcat! :)

I've never run a Wildcat! system.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

Was talking the Wildcat! :)

I've never run a Wildcat! system.

my bad. Was thinking that for some reason you did.
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: fsxNet: Omicron Theta * Southaven, MS * winserver.org (21:2/136)