home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 15232 
 Tim Woodland to Paul Hayton 
 Re: Not a valid PKT 
 17 Jan 23 19:04:42 
 
INTL 3:770/1 3:770/3
REPLYADDR tlwoodland@gmail.com
REPLYTO 3:770/3.0 UUCP
MSGID: <4bc20e2e-5533-41c9-8042-6858f8c26443n@googlegroups.com> 07a2d412
REPLY: 3:770/100.0 f6a40b97
PID: SoupGate-Win32 v1.05
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)
SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 123/120 131
SEEN-BY: 129/305 153/7715 154/10 218/700 840 220/70 226/17 30 100
SEEN-BY: 227/114 229/110 111 112 113 114 206 275 307 317 400 424 426
SEEN-BY: 229/428 452 470 550 664 700 250/5 8 266/512 267/800 282/1038
SEEN-BY: 292/854 298/25 305/2 3 317/3 320/219 322/757 342/200 396/45
SEEN-BY: 460/58 633/280 712/848 770/1 3 100 340 772/210 220 230
PATH: 770/3 1 317/3 229/426


<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca