I finally got set up with fidonet and all of my packets I am receiving from
my HUB are not tossing they where going to my C:\ drive folder. (I think I
have that corrected by uncommenting the bad packet line in my mailin.ini).
Here is a snippet of the log:
----------------- MUTIL v1.12 A46 2020/08/26 Fri, Jan 22 2021 (loglevel 3)
+ Jan 22 18:43:26 Startup using mailin.ini
- Jan 22 18:43:27 EXEC ImportEchoMail
- Jan 22 18:43:27 EXEC FileToss
+ Jan 22 18:43:27 Process: Toss FDN/TIC Files
+ Jan 22 18:43:27 Waiting for BUSY nodes
+ Jan 22 18:43:27 Scanning Hatches
+ Jan 22 18:43:27 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.03s
+ Jan 22 18:43:27 Process: Importing EchoMail
+ Jan 22 18:43:27 Waiting for BUSY nodes
! Jan 22 18:43:27 Import from c:\mystic\echomail\in\
+ Jan 22 18:43:27 Extracting c95bb9b8.fr0
- Jan 22 18:43:27 unzip -oqqjC "c:\mystic\echomail\in\c95bb9b8.fr0"
"*.pkt" -d c:\mystic\temputil\ 2>nul
+ Jan 22 18:43:27 Importing 0b60a400.pkt (1:154/10 to 1:120/457)
! Jan 22 18:43:27 Invalid PKT password
! Jan 22 18:43:27 Moving c:\mystic\temputil\0b60a400.pkt to \0b60a400.pkt
+ Jan 22 18:43:27 Importing 0b60a401.pkt (1:154/10 to 1:120/457)
! Jan 22 18:43:27 Invalid PKT password
! Jan 22 18:43:27 Moving c:\mystic\temputil\0b60a401.pkt to \0b60a401.pkt
+ Jan 22 18:43:27 Importing 0b60a40c.pkt (1:154/10 to 1:120/457)
! Jan 22 18:43:27 Invalid PKT password
! Jan 22 18:43:27 Moving c:\mystic\temputil\0b60a40c.pkt to \0b60a40c.pkt
+ Jan 22 18:43:27 Importing 0b60a51e.pkt (1:154/10 to 1:120/457)
! Jan 22 18:43:27 Invalid PKT password
Should I have my HUB just remove packet passwords?
Jeff

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

Found the problem, was using a packet password when i shouldn't have..
Proceed with your regularly scheduled program.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

On 23 Jan 2021 at 06:08a, Sparky pondered and said...

! Jan 22 18:43:27 Moving c:\mystic\temputil\0b60a401.pkt to \0b60a401.pkt + Jan 22 18:43:27 Importing 0b60a40c.pkt (1:154/10 to 1:120/457) ! Jan 22 18:43:27 Invalid PKT password
! Jan 22 18:43:27 Moving c:\mystic\temputil\0b60a40c.pkt to \0b60a40c.pkt + Jan 22 18:43:27 Importing 0b60a51e.pkt (1:154/10 to 1:120/457) ! Jan 22 18:43:27 Invalid PKT password
Should I have my HUB just remove packet passwords?
Jeff

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)

Couple of things.

There's a bug in this version of Mystic that caught me out.
If the packet is deemed BAD it should move it to a bad packet folder.
If you don't have that in your ini file then it is shifting them to your root directory! So look for them there and move them to where you want them to be. I'd suggest back into your inbound dir...

But before you do, yes, it's easiest to set your packet password as per the system that is sending those packets to you. Then Mystic will toss them in.

As for that ini switch here's what I added for my setup


[ImportEchoMail]

; If you want bad packets that cannot be imported moved to a directory
; then uncomment and set this value to an existing directory.

bad_packet = C:\bbs\mystic\echomail\in\bad

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 23 Jan 2021 at 06:08a, Sparky pondered and said...

! Jan 22 18:43:27 Moving c:\mystic\temputil\0b60a401.pkt to \0b60a401.pkt + Jan 22 18:43:27 Importing 0b60a40c.pkt (1:154/10 t 1:120/457) ! Jan 22 18:43:27 Invalid PKT password
! Jan 22 18:43:27 Moving c:\mystic\temputil\0b60a40c.pkt to \0b60a40c.pkt + Jan 22 18:43:27 Importing 0b60a51e.pkt (1:154/10 t 1:120/457) ! Jan 22 18:43:27 Invalid PKT password
Should I have my HUB just remove packet passwords?
Jeff

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)

Couple of things.

There's a bug in this version of Mystic that caught me out.
If the packet is deemed BAD it should move it to a bad packet folder.
If you don't have that in your ini file then it is shifting them to your root directory! So look for them there and move them to where you want them to be. I'd suggest back into your inbound dir...

But before you do, yes, it's easiest to set your packet password as per the system that is sending those packets to you. Then Mystic will toss them in.

Hi Avon, The problem turned out to be I thought the HUB I was calling was
using a packet password, they were not. Deleted the packet password tossed
the packets back in the "inbound" directory and everything tossed nicely.
Jeff

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

On 04 Feb 2021 at 03:37p, Sparky pondered and said...

Hi Avon, The problem turned out to be I thought the HUB I was calling was using a packet password, they were not. Deleted the packet password
tossed the packets back in the "inbound" directory and everything tossed nicely. Jeff

All good, glad you sorted it Sparky :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 23 Jan 2021, Sparky said the following...

I finally got set up with fidonet and all of my packets I am receiving from my HUB are not tossing they where going to my C:\ drive folder. (I think I have that corrected by uncommenting the bad packet line in my mailin.ini). Here is a snippet of the log:

1:120/457) ! Jan 22 18:43:27 Invalid PKT password

I think we already got this hashed out a week or more ago. But for the record, I don't set PKT passwords here unless specifically asked to do so. Otherwise, if you have any other issues, let me know and we'll get you fixed up asap.

Regards,
Nick

--- Mystic BBS v1.12 A47 2021/01/30 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 23 Jan 2021, Sparky said the following...

Found the problem, was using a packet password when i shouldn't have.. Proceed with your regularly scheduled program.

There I go reading/responding to messages in-line again. I wouldn't have needed to reply to the last one if I had read this one beforehand. ;)

Regards,
Nick

--- Mystic BBS v1.12 A47 2021/01/30 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

I think we already got this hashed out a week or more ago. But for the record, I don't set PKT passwords here unless specifically asked to do
so. Otherwise, if you have any other issues, let me know and we'll get
you fixed up asap.

Yes all fixed and working like a dream! Now if I can get some time to edit
and upload some ANSI files...

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Communicatin Connection 21:100/192 (21:1/192)

On 06 Feb 2021, Sparky said the following...

Yes all fixed and working like a dream! Now if I can get some time to
edit and upload some ANSI files...

It's reasons like this us sysops have said our systems are a work in progress, even if it's for 20+ years! ;)

Regards,
Nick

--- Mystic BBS v1.12 A47 2021/01/30 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 06 Feb 2021 at 11:36p, Accession pondered and said...

It's reasons like this us sysops have said our systems are a work in progress, even if it's for 20+ years! ;)

I totally agree :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)