Subj : Re: Not a valid PKT
To   : Paul Hayton
From : Tim Woodland
Date : Tue Jan 17 2023 07:04 pm

On Thursday, December 15, 2022 at 10:20:13 PM UTC-5, Paul Hayton wrote:
> On 15 Dec 2022 at 06:00p, Nicholas Boel pondered and said... 
> 
> NB> TW> 12 00:15:18 Cannot find arctype for 71211085.12.mo0; skipping 
> NB> 
> NB> "arctype" would lead me to believe you don't have zip/unzip installed or 
> NB> setup correctly in Mystic's configuration? 
> 
> yep I think you're on the right path with this one Nick. 
> 
> this one is I think because the system has had to rename the zipped packet and 
> you have a filename.morename.extn when it should be filename.extn 
> 
> suggest rename this one to 71211085.mo0 (assuming sysop does not have one there 
> with the same name in their inbound dir already) then try to re-run the import, 
> but also check you have zip and unzip installed. 
> 
> Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' 
> avon[at]bbs.nz | bbs.nz | fsxnet.nz
Update:  I did have zip/unzip installed and was able to verify that it would run from the command line as the sysop user. Also, renaming did not help.  

I am running Mystic A48 on Linux Mint 20.3 Cinnamon v 5.2.7.  The problem is due to the Mystic folder/file permission settings.  When I change the owner and group of the Mystic directories and files to my sysop user/group, I have to run mis as sudo for 
it to allow IP connectivity.  Then when running mutil, the zip extraction does not work nor does it recognize the pkt files, even if I manually extract them.  I tried then setting the mystic application executable files with root as the owner along with 
the echomail directory and files.  This did not work either no change in log errors.  

Finally, I recursively changed the owner of the Mystic directory and files to root leaving the sysop group unchanged.  This worked, no errors.  I now am trying to determine what the correct permission settings for the directories and folders should be so 
that I can run Mystic as the sysop user as the owner and group so that root is not exposed.  Is there a way to give the sysop user permissions to the ethernet ports so Mystic can use the IP ports when running as the sysop user?

Gandalf

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

.