Good evening!

I had noticed that I appeared not to be receiving my FSX mail on this node.
Got to poking around and could not find anything odd here, at first.
Polled and picked up some mail and noticed this:

MagiMail 1.0 started successfully!
Tossing files in /home/bbs/u/MagickaBBS/ftn/in...

Unarchiving /home/bbs/u/MagickaBBS/ftn/in/0000ffde.tu0 using ZIP

Archive: /home/bbs/u/MagickaBBS/ftn/in/0000ffde.tu0
inflating: mystfsx-net4/echomail/out/temp/f93ffb1d.pkt

Unarchiving /home/bbs/u/MagickaBBS/ftn/in/0000ffde.tu1 using ZIP

Archive: /home/bbs/u/MagickaBBS/ftn/in/0000ffde.tu1
inflating: mystfsx-net4/echomail/out/temp/f948211f.pkt

Unarchiving /home/bbs/u/MagickaBBS/ftn/in/0000ffde.tu2 using ZIP

Archive: /home/bbs/u/MagickaBBS/ftn/in/0000ffde.tu2
inflating: mystfsx-net4/echomail/out/temp/f9505f1f.pkt

Total -> Read messages: 0 Written messages: 0
Imported -> Imported messages: 0 Routed netmails: 0
Bad -> Bad messages: 0 Duplicate messages: 0

Scanning for orphan files
Scanning for old packets
Scanning for new files to pack
MagiMail end

So, then I checked my /tmp directory and found a directory had been
created called /mystfsx-net4/echomail/out/temp/ . It was full of PKT files that I just moved over into my inbound and was able to toss.

I think something on your end is adding the path to the PKT files on your system to the bundles, which is causing them not to toss on this end.
Maybe this only causes issues with magimail, but I suspect that is a zip setting you probably want to turn off for making FTN bundles.

I will also check and see if I can tell magimail to ignore any path info
when unzipping files.

Thanks!
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Hello Black,

I had noticed that I appeared not to be receiving my FSX mail on this node. Got to poking around and could not find anything odd here, at
first. Polled and picked up some mail and noticed this:

MagiMail 1.0 started successfully!
Tossing files in /home/bbs/u/MagickaBBS/ftn/in...

I have also seen this here. I have 0000fffa.mo0 that says this when I unzip it with the -l option..

Archive: 0000fffa.mo0
Length Date Time Name
--------- ---------- ----- ----
1432 2019-12-16 11:12 mystfsx-net4/echomail/out/temp/f7d77106.pkt --------- -------
1432 1 file

I can't unzip it. When I try I get this..

inflating f7d77106.pkt
error: invalid compressed data to inflate
error: invalid zip file with overlapped components (possible zip bomb)

I don't know what that means and that is the only error I have encountered with
mail from 4/100. I got that yesterday. It's not a concern, I just hope whatever is in that pkt was addressed to me and someone is waiting on a reply..
:)

Just FYI.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 17 Dec 2019, Blue White said the following...

I think something on your end is adding the path to the PKT files on your system to the bundles, which is causing them not to toss on this end. Maybe this only causes issues with magimail, but I suspect that is a zip setting you probably want to turn off for making FTN bundles.

I think I found it in the config file. I had a typo in the zip command that
was allowing the directory names to be stored.

There are some files already archived in your outbound, but any new ones
should process OK on your end. :)

Sorry about that.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 17 Dec 2019, Al said the following...

I don't know what that means and that is the only error I have
encountered with mail from 4/100. I got that yesterday. It's not a concern, I just hope whatever is in that pkt was addressed to me and someone is waiting on a reply.. :)

It might be the same issue, with having the directories listed in the zip
file. Let me know if you have any issues with the newer archives.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 17 Dec 2019 at 07:01p, Black Panther pondered and said...

I think I found it in the config file. I had a typo in the zip command that was allowing the directory names to be stored.

Yipes... I'd better check my settings also.

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

So, then I checked my /tmp directory and found a directory had been created called /mystfsx-net4/echomail/out/temp/ . It was full of PKT

Its not unusual for packet archives to contain a path structure, but its usually up to the decompression to ingnore that and put them where you expect them to go. Usually just a switch setting ...

Spec


*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: Scrawled in haste at The Lower Planes (21:3/101)

Black Panther wrote to Blue White <=-

I think I found it in the config file. I had a typo in the zip command that was allowing the directory names to be stored.

There are some files already archived in your outbound, but any new
ones should process OK on your end. :)

Sorry about that.

No worries. I was able to add a '-j' to my unzip command and that caused
them all to toss just fine. Thanks!



... Tell me, is something eluding you, Sunshine?
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)