I've being trying to figure out why mu out going mail is not making it to the node with out any luck. Checked setting and can't seem to figure out what the problem is. Here is my mutil log:
----------------- MUTIL v1.12 A46 2020/08/26 Sun, Feb 14 2021 (loglevel 3)
+ Feb 14 11:10:36 Startup using MAIlout.ini
- Feb 14 11:10:36 EXEC ExportEchoMail
+ Feb 14 11:10:36 Process: Exporting EchoMail
+ Feb 14 11:10:36 Waiting for BUSY nodes
+ Feb 14 11:10:36 Scanning...
+ Feb 14 11:10:36 Resuming from 546 in fsx_gen
+ Feb 14 11:10:36 Resuming from 10 in netmail
+ Feb 14 11:10:36 Export NETMAIL #10 to 21:3/100@fsxnet
+ Feb 14 11:10:36 Export NETMAIL #11 to 21:3/100@fsxnet
- Feb 14 11:10:36 2 msgs from Netmail (fsxNet)
+ Feb 14 11:10:36 Resuming from 23 in fsx_bbs
+ Feb 14 11:10:36 Resuming from 113 in fsx_mys
+ Feb 14 11:10:36 Resuming from 130 in fsx_ads
+ Feb 14 11:10:36 Resuming from 1 in fsx_cry
+ Feb 14 11:10:36 Resuming from 465 in fsx_dat
+ Feb 14 11:10:36 Resuming from 11 in fsx_eng
+ Feb 14 11:10:36 Resuming from 3 in fsx_ham
+ Feb 14 11:10:36 Resuming from 61 in fsx_net
+ Feb 14 11:10:36 Resuming from 101 in fsx_tst
+ Feb 14 11:10:36 Resuming from 170 in fsx_sta
+ Feb 14 11:10:36 Resuming from 100 in sx_fil
+ Feb 14 11:10:36 Resuming from 460 in fsx_bot
+ Feb 14 11:10:36 Resuming from 41 in fsx_mag
- Feb 14 11:10:38 EXEC: zip -qj9 c:\mystic\echomail\out\primary\00000023.su1 c:\mystic\temputil\0895a03c.pkt 2>nul
+ Feb 14 11:10:38 Adding PKT to FLO (addr=21:3/100 pkt=c:\mystic\echomail\ou \primary\00000023.su1 flo=c:\mystic\echomail\out\primary\00030064.clo)
+ Feb 14 11:10:38 Results: 0 echo, 2 net, 0 skipped in 2.06s
+ Feb 14 11:10:38 Shutdown Normal (0)

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

On 14 Feb 2021, cozmo said the following...

I've being trying to figure out why mu out going mail is not making it
to the node with out any luck. Checked setting and can't seem to figure out what the problem is.

So this looks all ok, like everything is packed up & ready to go. What happens if you run fidopoll send or mis poll send?


Jay

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

This is what happens when I run fidopoll send:

FIDOPOLL Version 1.12 A46 2020/08/26

Polling ALL nodes...

---
Scanning 21:3/100
Queued 0 files (0 bytes) to 21:3/100

Polled 0 nodes

When I run mis poll send it runs so quick I saw this:
But nothing in the mis.log

Sending to all nodes

O Polled

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

On 14 Feb 2021, cozmo said the following...

When I run mis poll send it runs so quick I saw this:
But nothing in the mis.log

Active Yes
^^^^^^ ^^^
Description fsxNet Hub (Net 3)
SysOp Name Deon George
Address 21:3/100
Domain fsxnet
Session Type BinkP
Archive Type
Export Type Normal
^^^^^^^^^^^ ^^^^^^
Route Info 21:*
Direct Bypass No
Max PKT Size 512
Max ARC Size 2048
Use Filebox No
Filebox Dir
Crash Limiter 0


Do you have the node set to active & export type set to normal or crash?


BINKP Hostname fidohub.leenooks.net
IP Type IPV4
Server Type Normal
Password **********
Time Out 30
Block Size 16384
CRAM-MD5 Forced
Hide AKAs Yes


Jay

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

All my settings are all correct except Export Type was set to crash. I
changed it to normal but still not working.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

Re: Re: Mail out not making it to the node
By: cozmo to Warpslide on Sun Feb 14 2021 07:31 pm

All my settings are all correct except Export Type was set to crash. I changed it to normal but still not working.

Crash or normal should work OK.

I would double check you have both zip and unzip installed. If zip is missing this will happen.

Ttyl :-),
Al

... Misspelled? Impossible. My modem is error correcting.
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Here is my mutil.log I don't know what The "Unknown inbound file" is.
IO.SYS, MSDOS.SYS etc.

----------------- MUTIL v1.12 A46 2020/08/26 Mon, Feb
15 2021 (loglevel 3) + Feb 15 08:26:46 Startup using mailin.ini
- Feb 15 08:26:46 EXEC ImportEchoMail
+ Feb 15 08:26:46 Process: Importing EchoMail
+ Feb 15 08:26:46 Waiting for BUSY nodes
! Feb 15 08:26:46 Import from c:\mystic\echomail\in\
! Feb 15 08:26:46 Unknown inbound file bootmgr
! Feb 15 08:26:46 Unknown inbound file BOOTSECT.BAK
! Feb 15 08:26:46 Unknown inbound file DZERV
! Feb 15 08:26:46 Unknown inbound file FSXNET.Z36
! Feb 15 08:26:46 Unknown inbound file 13ajtlqu.tic
! Feb 15 08:26:46 Unknown inbound file 13ajtlrq.tic
! Feb 15 08:26:46 Unknown inbound file IO.SYS
! Feb 15 08:26:46 Unknown inbound file MSDOS.SYS
! Feb 15 08:26:46 Unknown inbound file FSXNET.z43
! Feb 15 08:26:46 Unknown inbound file 13at26aw.tic
! Feb 15 08:26:46 Unknown inbound file FSXNET.1.Z43
! Feb 15 08:26:46 Unknown inbound file 13b0159w.tic
+ Feb 15 08:26:46 Extracting 2a748403.tu0
- Feb 15 08:26:46 unzip -oqqjC "c:\mystic\echomail\in\2a748403.tu0" "*.pkt" d c:\mystic\temputil\ 2>nul
+ Feb 15 08:26:46 Importing 2A748421.PKT (21:3/100 to 21:3/135)
+ Feb 15 08:26:46 Import #597 to FSX_GEN
+ Feb 15 08:26:46 Import #598 to FSX_GEN
! Feb 15 08:26:46 Import from c:\mystic\echomail\in\unsecure\
+ Feb 15 08:26:46 Results: 2 echo, 0 net, 0 dupes, 0 tossed in 0.14s
+ Feb 15 08:26:46 Shutdown Normal (0)

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

Re: Re: Mail out not making it to the node
By: cozmo to Al on Mon Feb 15 2021 08:55 am

Here is my mutil.log I don't know what The "Unknown inbound file" is. IO.SYS, MSDOS.SYS etc.

That is odd. Can you see where those files are coming from in your mis.log?

Ttyl :-),
Al

... To err is human, to really screw up it takes a computer!
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

I have no idea where that is coming from. Here is a snipit from mis.log.
I'm banging my head on trying to figure it out.
Must be some setting in one of the .ini files that I'm missing.

+ 2021.02.15 06:55:08 BINKP > Connect on slot 1/3 (122.199.47.98)
+ 2021.02.15 06:55:08 BINKP 1-HostName Unknown
+ 2021.02.15 06:55:08 BINKP 1-System Alterant MailHub
+ 2021.02.15 06:55:08 BINKP 1-SysOp Deon George
+ 2021.02.15 06:55:08 BINKP 1-Location Parkdale, VIC AU
+ 2021.02.15 06:55:08 BINKP 1-Mailer binkd/1.1a-111/Linux binkp/1.1
+ 2021.02.15 06:55:09 BINKP 1-Queued 0 files for 21:3/100@fsxnet
+ 2021.02.15 06:55:09 BINKP 1-Receiving: 2a610604.mo0 (2,006 bytes)
+ 2021.02.15 06:55:09 BINKP 1-Session ended (0 sent, 1 rcvd, 0 skip)

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

Re: Re: Mail out not making it to the node
By: cozmo to Al on Mon Feb 15 2021 11:44 am

I have no idea where that is coming from. Here is a snipit from mis.log. I'm banging my head on trying to figure it out.
Must be some setting in one of the .ini files that I'm missing.

+ 2021.02.15 06:55:09 BINKP 1-Receiving: 2a610604.mo0 (2,006 bytes)

That one came from the Alterant mail hub. that's a mail bundle, that's what you want.

The MSDOS.SYS and IO.SYS look like files from the DOS OS. They shouldn't be in your inbound so they are getting there by mistake, somehow.

If you search your mis.log for those filenames you may be able to find out where they are coming from.

Could they have been copied there by mistake? It's mysterious.

Ttyl :-),
Al

... Freedom of the press is limited to those who have one.
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Can't find any mention of those DOS files in mis.log - Those files are not in the echomail\in folder. Although I somehow had "Directory" set for
Session Type about a week ago and those files got moved into the echomail\in folder but I had moved them out and are no longer in the folder. I then
changed Session to BinkP. So I don't know why they're still showing in the mutil.log file. Frustrating to say the least!

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

On 15 Feb 2021, Al said the following...

The MSDOS.SYS and IO.SYS look like files from the DOS OS. They shouldn't be in your inbound so they are getting there by mistake, somehow.

If you search your mis.log for those filenames you may be able to find
out where they are coming from.

Could they have been copied there by mistake? It's mysterious.

I think he mistakenly had this node set to directory tossing at one point which may have copied/movied those folders from the root.


Jay

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Would it possible to email your mutil.ini, mail.in and mail.out files to me?
I would like to scan over them to see if I have all the settings correct. I've edited those files so much that I think I might have screwed them up.

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

Re: Re: Mail out not making it to the node
By: Warpslide to Al on Mon Feb 15 2021 01:09 pm

I think he mistakenly had this node set to directory tossing at one point which may have copied/movied those folders from the root.

Yep, that could be. I've seen a few odds and ends in my inbound over the years. Sometimes I did that myself.. ;)

Ttyl :-),
Al

... 24 hours in a day, 24 beers in a case. Coincidence?
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 15 Feb 2021, Al said the following...

Yep, that could be. I've seen a few odds and ends in my inbound over the years.

Hopefully nothing *too* incriminating... ;)


Jay

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Re: Re: Mail out not making it to the node
By: Warpslide to Al on Tue Feb 16 2021 02:42 pm

Yep, that could be. I've seen a few odds and ends in my inbound over
the years.

Hopefully nothing *too* incriminating... ;)

A couple of them gave me a good laugh.. ;)

Ttyl :-),
Al

... And if one bad cluster should accidentally fail...
--- SBBSecho 3.12-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 14 Feb 2021 at 05:42p, Warpslide pondered and said...

BINKP Hostname fidohub.leenooks.net
IP Type IPV4
Server Type Normal
Password **********
Time Out 30
Block Size 16384
CRAM-MD5 Forced
Hide AKAs Yes

Just by way of feedback I suggest set CRAM-MD5 to Yes instead of Forced. This allows some wiggle room when the handshake is taking place. The session will still try to reach a MD5 handshake but not fail if the remote end says no. By having 'forced' at your end you potentially may end up having problems connecting to some remote systems that can't honor your request.

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