I tried to use the mailread.mpx script it is something that would find to
be very useful.. I tired with and and without including the
username/password switches.. but either way, it logs in and then immediately exits without showing any output from the MI command. However, some of the other scripts return output.. the usage.mpx script for example works as expected.

I am sorry to ask so many questions. I'm starting to feel like I'm being annoying since I'm not seeing others post about such issues. Is the Win32 build more stable? Not that it matters.. since I wouldn't consider running Windows anyway..

Thanks,

Fat Rastus

--- Mystic BBS v1.12 A29 (Linux)
* Origin: CombatNet Support BBS (46:1/107.2)

I am sorry to ask so many questions. I'm starting to feel like I'm being annoying since I'm not seeing others post about such issues. Is the
Win32 build more stable? Not that it matters.. since I wouldn't consider running Windows anyway..

Are you passing the command line correctly? Its difficult to help you if you're not posting any other detail besides "it doesn't work".

sudo ./mystic -ug00r00 -pasdf -xmailread
sudo ./mystic -ujoe_smith -pasdf -xmailread

^^ I just tested those with a stock install and it worked for me. Its been there for half a decade and no one has ever mentioned an issue with it to my knowledge. Usually this is a sign of a user error...

If you get the wrong user name or password, or you give the wrong filename (do not use file extensions for example) then it will do exactly what you're describing.

I don't find the questions annoying. Most of them are already addressed in other support areas or the documentation, but the documentation isn't well arranged at the moment and I realize you aren't in the primary support area, so its all good. :)

You are implying that Mystic is unstable though, without backing that up. What I *do* find frustrating is when someone makes frequent user errors, does not read documentation, and then makes bold statements like calling Mystic unstable while using the unstable builds.

I am not saying you definitely fall into that category, but the -UPACK and the script above may be a sign of jumping to conclusions before asking questions. The way MIS works with SUDO is also discussed in the second and third sentences of the installation guide for MIS, so the fact you didn't know how it works means you didn't even read any of it, for example.

What is unstable in A29 (an unstable build) so it can be addressed? Please at least do that if you're going to imply Mystic is unstable.

--- Mystic BBS v1.12 A29 (Windows)
* Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)

On 07/16/16, Fat Rastus said the following...

I am sorry to ask so many questions. I'm starting to feel like I'm being annoying since I'm not seeing others post about such issues. Is the
Win32 build more stable? Not that it matters.. since I wouldn't consider running Windows anyway..

It's not annoying at all.. :) When I first setup Mystic I was in here
everyday for the longest time with questions..

If I see questions I can answer I will.. but I still see a lot of questions that I don't have answers for.. so I hope someone else does.. :)

Ttyl :-),
Al

--- Mystic BBS v1.12 A29 (Linux)
* Origin: The Rusty MailBox - Penticton, BC Canada (46:1/161)

On 07/17/16, g00r00 said the following...

Are you passing the command line correctly? Its difficult to help you if you're not posting any other detail besides "it doesn't work".
sudo ./mystic -ug00r00 -pasdf -xmailread

I was using the full path to both mystic and to the script. My bad.. but
I've been *unix for so long that doing so has become second nature to me.

I don't find the questions annoying. Most of them are already addressed in other support areas or the documentation, but the documentation isn't well arranged at the moment and I realize you aren't in the primary support area, so its all good. :)

Primary support area? Is there a better place to find information? I don't like asking questions that have already been answered. I read the mystic.txt and parse through the whatsnew files going back to 1.05. I am subscribed to this echo and to the fidonet mystic support echo.. agoranet seems to be preferred by many here?

Thanks,

Fat Rastus

--- Mystic BBS v1.12 A29 (Linux)
* Origin: CombatNet Support BBS (46:1/107.2)

On 07/17/16, g00r00 said the following...

I am sorry to ask so many questions. I'm starting to feel like I'm b annoying since I'm not seeing others post about such issues. Is the Win32 build more stable? Not that it matters.. since I wouldn't consi running Windows anyway..

Are you passing the command line correctly? Its difficult to help you if you're not posting any other detail besides "it doesn't work".

sudo ./mystic -ug00r00 -pasdf -xmailread
sudo ./mystic -ujoe_smith -pasdf -xmailread

^^ I just tested those with a stock install and it worked for me. Its been there for half a decade and no one has ever mentioned an issue with it to my knowledge. Usually this is a sign of a user error...

Didn't you change things in 112a3?

+ When passing -X to execute MPL from command line, Mystic will now longer
replace _ with spaces in the filenames. Instead it is expected that you
use quotations around the argument if it has spaces.

So maybe the argument is the problem? Is there a passed argument that isn't parsed correctly?

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A29 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (46:1/116)

Are you passing the command line correctly? Its difficult to help you if you're not posting any other detail besides "it doesn't work".

The problem, my error, was that I was trying to run it from a bash script
that resided in another directory. I had changed to the /mystic directory in the script but for some reason the path must not have been picked up??? I
added the mysticbbs variable to my environment and it's working... And it was ok to use the full path to the mpx file after I added the variable.


Sorry if my question sounded like a critisim.. it was not meant to be that way.. I am still working on my communication skills... strokes really suck and

--- Mystic BBS v1.12 A29 (Linux)
* Origin: CombatNet Support BBS (46:1/107.2)

working... And it was ok to use the full path to the mpx file after I added the variable.

Yep the full path is okay, but not file extension if I recall correctly - Mystic always forces MPL executables to be ".MPX" files.

Maybe I can improve the logging a little more in that area so it gives a
better idea of what is happening when it just logs you out like that.

Sorry if my question sounded like a critisim.. it was not meant to be
that way.. I am still working on my communication skills... strokes really suck and

No worries man. I am sorry to hear of your troubles. I wasn't aware of that.

--- Mystic BBS v1.12 A30 (Windows)
* Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)

On 07/17/16, Fat Rastus said the following...

Are you passing the command line correctly? Its difficult to help you you're not posting any other detail besides "it doesn't work".

The problem, my error, was that I was trying to run it from a bash script that resided in another directory. I had changed to the /mystic
directory in the script but for some reason the path must not have been picked up??? I added the mysticbbs variable to my environment and it's working... And it was ok to use the full path to the mpx file after I added the variable.

You may need to build the command line like this:
# ./mystic -Ualias -Ppassword -X/path/to/mpl/mplfile

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A29 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (46:1/116)