Mail is going to you, but it's not routing to anyone else. If it is a config issue on my end, I hope I can track this bugger down...

IREx shows:

log.txt:* 01:44:29 (732) Sent to 618:300/1: 127A13E0.MO0 (1284 bytes)

Fastecho shows:

FASTECHO.LOG:+ 02 Sep 01:44:24 FSTE Created FileAttach to 618:300/1 (012C0001.CLO)

I don't know where else to look... Its got to be a problem with irex or fastecho.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

Shurato wrote to Rick Smith <=-

I don't know where else to look... Its got to be a problem with irex
or fastecho.

I suspect it's FE that doesn't have its routing table correct. You should
have it set for all mail, including netmail since you cannot crashmail in
IRex (IRex requires you to use a V7+ nodelist which you have told me you do
not have) right now.

Double-check your FE setup and make sure all Micronet mail is routed to
Rick.

-- Sean

... Laugh and the world laughs with you...fart and you stand alone.
--- MultiMail/Linux
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

Shurato wrote to Rick Smith <=-

I don't know where else to look... Its got to be a problem with irex or fastecho.

I suspect it's FE that doesn't have its routing table correct. You should have it set for all mail, including netmail since you cannot crashmail in IRex (IRex requires you to use a V7+ nodelist which you have told me you do not have) right now.

Double-check your FE setup and make sure all Micronet mail is routed to Rick.

I have 618:* routing to 618:300/1. He's getting direct mail; I'm not sure where this stuff is routing to. I changed some settings and will send again.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

Shurato wrote to Rick Smith <=-

I don't know where else to look... Its got to be a problem with irex or fastecho.

I suspect it's FE that doesn't have its routing table correct. You should have it set for all mail, including netmail since you cannot crashmail in IRex (IRex requires you to use a V7+ nodelist which you have told me you do not have) right now.

Double-check your FE setup and make sure all Micronet mail is routed to Rick.

I've got 618:* routing to 618:300/1, and arcmail set to none. Previously I
had it set to crash/direct which might have been the problem. I've send new netmails out and sent logs to Rick Smith.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

I've got 618:* routing to 618:300/1, and arcmail set to none. Previously had it set to crash/direct which might have been the problem. I've send netmails out and sent logs to Rick Smith.

Are you using a Binkley-style outbound? If not ARCmail should be set to
yes. Do not send anything crash as Internet Rex cannot crash any nodes
unless you are using a V7+ nodelist which you have said you are not using.
All mail, including netmail, destined for other Micronet nodes, should be routed through Rick.

-- digi



--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

* In a message originally to Shurato, digimaus said:

I've got 618:* routing to 618:300/1, and arcmail set to none.

Previously

had it set to crash/direct which might have been the problem. I've

send

netmails out and sent logs to Rick Smith.

Are you using a Binkley-style outbound? If not ARCmail should be set to yes. Do not send anything crash as Internet Rex cannot crash any nodes unless you are using a V7+ nodelist which you have said you are not using.

All mail, including netmail, destined for other Micronet nodes, should be routed through Rick.

Yes, the options are "None", "Crash", "Direct", "Hold", "Crash/Direct". I'm using Binkley style outbound. I've got arcmail set to "None".

Crash should work, I'm pretty sure irex crashes nodes (just sends
immediately), but it can't send directly. I did get rid of direct though and have tried to send messages through that way. I've got 618:* routing to 618:300/1, which is Rick's Node.

--- MBSE BBS v1.1.0 (Linux-x86_64) * Origin: Outpost BBS * Johnson
City, TN (618:618/1)

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

Crash should work, I'm pretty sure irex crashes nodes (just sends immediately), but it can't send directly. I did get rid of direct though and have tried to send messages through that way. I've got 618:* routing

to

618:300/1, which is Rick's Node.

IRex will only "crash" nodes that you have in your IRex config. It won't
crash anyone else since you are not using a V7+ nodelist. So that's not an issue. What it sounds like is that somewhere, you have an issue. Be aware that FastEcho is buggy and cannot be fixed as it likes to srip the seen-by lines in a message and its Binkley support is not the best. You've patched your FE to 1.46.1, right?

The big issue is you're using buggy software (Internet Rex and FastEcho)
that may be causing issues and you may not realize it.

--digi



--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

Crash should work, I'm pretty sure irex crashes nodes (just sends
immediately), but it can't send directly. I did get rid of direct

though

and have tried to send messages through that way. I've got 618:*

routing to

618:300/1, which is Rick's Node.

IRex will only "crash" nodes that you have in your IRex config. It won't crash anyone else since you are not using a V7+ nodelist. So that's not an issue. What it sounds like is that somewhere, you have an issue.
Be aware that FastEcho is buggy and cannot be fixed as it likes
to srip the seen-by lines in a message and its Binkley support
is not the best. You've patched your FE to 1.46.1, right?

I did, but that would crash ntvdm regularly, so I went back to 1.46. The
DPMI mode FE was extremely unstable.

The big issue is you're using buggy software (Internet Rex and FastEcho) that may be causing issues and you may not realize it.

--digi

--- MBSE BBS v1.1.0 (Linux-x86_64) * Origin: Outpost BBS * Johnson
City, TN (618:618/1)

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

Shurato wrote to digimaus <=-

I did, but that would crash ntvdm regularly, so I went back to 1.46.
The DPMI mode FE was extremely unstable.

That .1 has important fixes which may fix the issue you're having.
Personally, if you can't upgrade, I'd switch to another mail tosser
post-haste. I think until you fix FE, you're going to keep having issues.

-- Sean

--- MultiMail/Linux
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

Shurato wrote to digimaus <=-

I did, but that would crash ntvdm regularly, so I went back to 1.46. The DPMI mode FE was extremely unstable.

That .1 has important fixes which may fix the issue you're having. Personally, if you can't upgrade, I'd switch to another mail tosser post-haste. I think until you fix FE, you're going to keep having issues.

Ok, I've upgraded again and am not doing the stuff that made it crash (before and after packing commands). The thing is though, this all worked just fine until recently and I hadn't changed anything other than restoring from a previously working backup. My experiences with VMs are flaky. Often I'll change something and it won't take effect. I'm using fastec16 instead of fastecho now and feutil16 instead of feutil.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

Shurato wrote to digimaus <=-

I did, but that would crash ntvdm regularly, so I went back to 1.46. The DPMI mode FE was extremely unstable.

That .1 has important fixes which may fix the issue you're having. Personally, if you can't upgrade, I'd switch to another mail tosser post-haste. I think until you fix FE, you're going to keep having issues.

Ok, trying to upgrade failed. bupdate gave me a file time comparison error.
If I ran it with -i -o, I got a file size error. I redownloaded all of the executables (and .rars) and started from scratch on that end. I've changed frontend from binkley to frontdoor instead, since I couldn't update the dos executable. Only DMPI.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

On 05 Sep 24 19:30:00, Shurato said the following to Digimaus:

Ok, I've upgraded again and am not doing the stuff that made it crash (befor and after packing commands). The thing is though, this all worked just fine until recently and I hadn't changed anything other than restoring from a previously working backup. My experiences with VMs are flaky. Often I'll change something and it won't take effect. I'm using fastec16 instead of fastecho now and feutil16 instead of feutil.

Not sure what OS you're on but just throwing this out there, that Microsoft did something to NTVDM after XP where its just not reliable for DOS stuff.

I've written about this many times in the past, I can't really "prove it" but go by the few times I've tried to migrate my BBS to anything beyond XP and things just randomly crashed. For no reason, just happened. Didn't matter of the hardware or anything that our resident Professor can chime-in on. Anything beyond XP and the NTVDM environment is unreliable... period.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

* In a message originally to Shurato, Nick Andre said:

On 05 Sep 24 19:30:00, Shurato said the following to Digimaus:

Ok, I've upgraded again and am not doing the stuff that made it crash

(befor

and after packing commands). The thing is though, this all worked just

fine

until recently and I hadn't changed anything other than restoring from

a

previously working backup. My experiences with VMs are flaky. Often

I'll

change something and it won't take effect. I'm using fastec16 instead

of

fastecho now and feutil16 instead of feutil.

Not sure what OS you're on but just throwing this out there, that
Microsoft did something to NTVDM after XP where its just not
reliable for DOS stuff.

I've written about this many times in the past, I can't really "prove it" but go by the few times I've tried to migrate my BBS to anything
beyond XP and

things just randomly crashed. For no reason, just happened. Didn't matter
of the hardware or anything that our resident Professor can chime-in
on. Anything beyond XP and the NTVDM environment is unreliable...
period.

It was the DPMI executables. I was finally (after using the command.com environment to run the commands) able to upgrade my fastecho to 1.46pl1.
It's running well now.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

On 06 Sep 24 12:13:00, Shurato said the following to Nick Andre:

It was the DPMI executables. I was finally (after using the command.com environment to run the commands) able to upgrade my fastecho to 1.46pl1. It's running well now.

Excellent...

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (618:500/24)

Hello Shurato!

Friday September 06 2024 12:13, you wrote to Nick Andre:

* In a message originally to Shurato, Nick Andre said:

On 05 Sep 24 19:30:00, Shurato said the following to Digimaus:

Ok, I've upgraded again and am not doing the stuff that made it

crash (befor

and after packing commands). The thing is though, this all

worked just fine

until recently and I hadn't changed anything other than

restoring from a

previously working backup. My experiences with VMs are flaky.

Often I'll

change something and it won't take effect. I'm using fastec16

instead of

fastecho now and feutil16 instead of feutil.

Not sure what OS you're on but just throwing this out there, that
Microsoft did something to NTVDM after XP where its just not
reliable for DOS stuff.

I've written about this many times in the past, I can't really
"prove it" but go by the few times I've tried to migrate my BBS to
anything beyond XP and

things just randomly crashed. For no reason, just happened. Didn't
matter of the hardware or anything that our resident Professor can
chime-in on. Anything beyond XP and the NTVDM environment is
unreliable... period.

It was the DPMI executables. I was finally (after using the
command.com environment to run the commands) able to upgrade my
fastecho to 1.46pl1. It's running well now.

This is working now?

Regards,

Rick

... Stress - the phone bill after BBSing
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (618:300/1)

* In a message originally to Shurato, Rick Smith said:

Hello Shurato!

Friday September 06 2024 12:13, you wrote to Nick Andre:

* In a message originally to Shurato, Nick Andre said:

On 05 Sep 24 19:30:00, Shurato said the following to Digimaus:

Ok, I've upgraded again and am not doing the stuff that made it

crash (befor

and after packing commands). The thing is though, this all

worked just fine

until recently and I hadn't changed anything other than

restoring from a

previously working backup. My experiences with VMs are flaky.

Often I'll

change something and it won't take effect. I'm using fastec16

instead of

fastecho now and feutil16 instead of feutil.

Not sure what OS you're on but just throwing this out there, that
Microsoft did something to NTVDM after XP where its just not
reliable for DOS stuff.

I've written about this many times in the past, I can't really "prove
it" but go by the few times I've tried to migrate my BBS to
anything beyond XP and

things just randomly crashed. For no reason, just happened. Didn't
matter of the hardware or anything that our resident Professor can
chime-in on. Anything beyond XP and the NTVDM environment is
unreliable... period.

It was the DPMI executables. I was finally (after using the command.com environment to run the commands) able to upgrade my fastecho to 1.46pl1. It's running well now.

This is working now?

Well, I've got 1.46pl1 running instead of 1.46 which should send netmail more reliably through a binkley frontend. I'll try again; I lost a days worth of messages accidentally. It could have been worse... Thank goodness for backups!

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)