Hello everybody!



Test without TZUTC


Thanks.


Thierry


--- FMail/386 1.60.GPL
* Origin: 386_40mhz-8MB_ram/DOS6.22/IBM_TCP-IP/Binkd-DOS/Fmail1.6/ (4:900/106)

Hello Thierry!

12 Apr 20 00:46, you wrote to all:

@CHRS: CP850 2
@MSGID: 4:900/106 5e926521

Hello everybody!

Test without TZUTC

Thanks.

Thierry

--- FMail/386 1.60.GPL
* Origin: 386_40mhz-8MB_ram/DOS6.22/IBM_TCP-IP/Binkd-DOS/Fmail1.6/ (4:900/106)
SEEN-BY: 14/5 15/0 19/36 57/0 106/201 116/18 120/302 331 123/140
153/757 7715
SEEN-BY: 218/700 220/70 222/2 226/16 17 230/150 152 240/1120 250/1
261/38 100
SEEN-BY: 261/1466 266/512 267/155 800 275/100 282/1031 1056 1060
291/100 111
SEEN-BY: 317/3 320/119 219 340/400 1000 341/66 342/13 396/45 640/1321 712/848
SEEN-BY: 770/0 1 100 330 340 772/0 1 210 220 230 500 801/161 189
2320/105
SEEN-BY: 3634/12 5020/1042
@PATH: 900/106 902/27 90/1 229/426 317/3 770/1 19/36 261/38

Jeff


--- Mystic v1.12 A46 (2020/04/11) GoldED+/LNX 1.1.5-b20170303
* Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)

I've been doing some tweaking, I've been having issues with my netmail as well.. If anybody could, send me a netmail to the address shown on my tagline please?

Thank you!




--- ENiGMA 1/2 v0.0.11-beta (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

Hello Charles,

I've been doing some tweaking, I've been having issues with my netmail
as well.. If anybody could, send me a netmail to the address shown on
my tagline please?

I have a netmail for you in my outbound but can't connect to your node. Here's a look at the log..

+ 21 Apr 20:47:33 [23162] call to 1:226/16@fidonet
21 Apr 20:47:33 [23162] trying newfrontier.net [98.124.199.3]...
? 21 Apr 20:47:33 [23162] connection to 1:226/16@fidonet failed: Connection refused

My mailer tried newfrontier.net on port 24554. Are you using a different port? If you poll 153/757 you should be able to pick it up.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Charles,

I have a netmail for you in my outbound but can't connect to your
node. Here's a look at the log..

I changed your node line to frontierbbs.net and managed to send it. You should have it now.. :)

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 21 Apr 2020, Charles Stephenson said the following...

I've been doing some tweaking, I've been having issues with my netmail as well.. If anybody could, send me a netmail to the address shown on my

Sent one. Let me know here if you would if you get it. I route almost all of
my netmail. I know the system will send/receive direct from my hosts but haven't had as much luck with folks that aren't listed in my hub config. Then again, I really haven't had much reason to test either.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A46 2020/04/17 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (1:3634/24)

Re: Enigma-Netmail test
By: Charles Stephenson to All on Tue Apr 21 2020 20:10:25

I've been doing some tweaking, I've been having issues with my
netmail as well.. If anybody could, send me a netmail to the
address shown on my tagline please?

my system has several routed netmails for your system that are stuck here because my mailer cannot connect to yours for some reason...


+ 22 Apr 14:09:04 [16747] call to 1:226/16@fidonet

22 Apr 14:09:04 [16747] trying newfrontier.net [98.124.199.3]...

? 22 Apr 14:09:04 [16747] connection to 1:226/16@fidonet failed: Connection refused

+ 22 Apr 14:09:04 [16747] holding 1:226/16@fidonet (2020/04/22 14:19:04)


is that the correct domain name and ip address?
is your mailer running on the standard binkp port or a non-standard one?
is the nodelist entry (where the above info is taken from) correct?


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello mark,

22 Apr 14:09:04 [16747] trying newfrontier.net [98.124.199.3]...

? 22 Apr 14:09:04 [16747] connection to 1:226/16@fidonet failed: Connection refused

I had this issue too yesterday when I sent a netmail his way.

His hostname is frontierbbs.net currently and that works.

I think the nodelist needs an update if Charles is going to be using that domain going forward.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Re: Enigma-Netmail test
By: Alan Ianson to mark lewis on Wed Apr 22 2020 11:29:56

22 Apr 14:09:04 [16747] trying newfrontier.net [98.124.199.3]...

? 22 Apr 14:09:04 [16747] connection to 1:226/16@fidonet failed: Connection refused

I had this issue too yesterday when I sent a netmail his way.

His hostname is frontierbbs.net currently and that works.

yeah, i saw your posts... i just wanted to inquire and try to ensure that things get fixed properly before applying an override here... i'm ok with overrides until they are forgotten about and get in the way later ;)

I think the nodelist needs an update if Charles is going to be using
that domain going forward.

agreed...

one i receive a response from charles, i'll do what i need to do here to send it on or i'll wait for a nodelist update with the fixes in place and let the system deal with it automatically at that time...

FWIW: the same bug that caused my system to try to send someone else's routed netmail to a destination point system directly is also the one that caused this
message to get hung here trying to go direct/crash when it should have gone routed from here... that bug has hopefully be fixed now and i'm running the latest available code for the tosser... we're watching closely for more routed netmails arriving here with the crash bit in place to see if the tosser now properly strips/ignores that bit and follows my routing table properly ;)

FWIW2: i still need to dig up some more time and work on expanding my routing table to provide more direct routing to other zones, regions, and nets than i currently have in place... while i do not have a significant other, at this time, i still have a TODO/HONEYDO list that keeps growing for some reason LOL


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello mark,

His hostname is frontierbbs.net currently and that works.

yeah, i saw your posts... i just wanted to inquire and try to ensure
that things get fixed properly before applying an override here... i'm
ok with overrides until they are forgotten about and get in the way
later ;)

Yep, I have 5 or 10 overrides that are probably not doing anything good anymore.. ;)

FWIW: the same bug that caused my system to try to send someone else's routed netmail to a destination point system directly is also the one
that caused this message to get hung here trying to go direct/crash
when it should have gone routed from here... that bug has hopefully be fixed now and i'm running the latest available code for the tosser... we're watching closely for more routed netmails arriving here with the crash bit in place to see if the tosser now properly strips/ignores
that bit and follows my routing table properly ;)

I saw your comment about that. It looked like Mystic routed a crash netmail to your node? :)

I happen to have a Mystic I have been doing some testing with. I am going to use that setup with your node as the route-to and see if it routes a crash netmail to your node and if it does you can see what happens with it.

If that does happen we should pass that info on to James. It's a small but important detail.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Re: Enigma-Netmail test
By: Alan Ianson to mark lewis on Wed Apr 22 2020 12:36:52

[...] when it should have gone routed from here... that bug has
hopefully be fixed now and i'm running the latest available code
for the tosser... we're watching closely for more routed netmails
arriving here with the crash bit in place to see if the tosser
now properly strips/ignores that bit and follows my routing table
properly ;)

I saw your comment about that. It looked like Mystic routed a
crash netmail to your node? :)

yeah... but i haven't looked deeper to see if it was a mystic system or not... i've been thinking that RM was running sbbs but could easily be wrong about that...

I happen to have a Mystic I have been doing some testing with. I
am going to use that setup with your node as the route-to and see
if it routes a crash netmail to your node and if it does you can
see what happens with it.

ok... it is possible to route crash netmail, though... it depends on one's definition of crash...

crash means "send as soon as possible"... it doesn't necessarially mean "send it direct now"...

this distinction is why the frontdoor guys introduced DIRect and IMMediate...

DIRect means "send directly, ignoring any routing statements"...

IMMediate means "send it right now regardless of any schedule qualifications"...

a message with DIRect and CRAsh bits would mean "send as soon as possible and send directly to the destination"...

a message with DIRect and IMMediate would mean "send right now and send directly to the destination"...

a message with only IMMediate would mean "send right now following the routing table"...

a message with only CRAsh would mean "send as soon as possible following the routing table"...

If that does happen we should pass that info on to James. It's a
small but important detail.

even more important would be to ensure that HOLD, CRAsh, LOCAL, and IMMediate are stripped in the packed message so they are not mistakenly used/followed by an intermediate system... DIRect won't be seen by any intermediate systems... not without manual intervention so it should probably also be stripped from the
packed message, too...

i'm sure all of this was already properly in mystic v1.11 before things moved to another FTN... i don't understand why it has changed since then... i was very active with mystic at that time and provided a lot of input and assistance
on this stuff... i dunno...


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

On 22 Apr 2020, Alan Ianson said the following...

I saw your comment about that. It looked like Mystic routed a crash netmail to your node? :)

In the node settings (Mark is my uplink) I have it set to route netmails through him for zones 1,2,4 (3 is through Paul). I also have him set for
crash.

There are unfortunately no other settings in Mystic dealing specifically with Netmail so ALL mail for zones 1,2 and 4 go through him unless I specifically have you set up as a node in the mystic settings.

Don't know what will happen if I leave the routing blank as I've never tried that. My guess is that it would default to direct/crash. I'll ask in the
Mystic support echo.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A46 2020/04/17 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (1:3634/24)

On 22 Apr 2020, mark lewis said the following...

yeah... but i haven't looked deeper to see if it was a mystic system or not... i've been thinking that RM was running sbbs but could easily be wrong about that...

No, I switched from SBBS to Mystic a few years back.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A46 2020/04/17 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (1:3634/24)

Hello Richard,

I saw your comment about that. It looked like Mystic routed a
crash netmail to your node? :)

In the node settings (Mark is my uplink) I have it set to route
netmails through him for zones 1,2,4 (3 is through Paul). I also have
him set for crash.

There are setting for netmail in the message base settings also for Crash, Hold, KillSent and Direct that may also come into play here.

I have always left those off thinking that mail would be routed with the "Route
Info" for echomail nodes.

Do you have any of those set to yes? That may have caused the netmail to be set
to crash.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 22 Apr 2020, Alan Ianson said the following...

There are setting for netmail in the message base settings also for
Crash, Hold, KillSent and Direct that may also come into play here.

I keep Crash and Direct on and Hold/KillSent turned off.

Going to remove the route settings from /12 and see what happens both with sending to a point, as well as to a full node.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A46 2020/04/17 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (1:3634/24)

Re: Enigma-Netmail test
By: Richard Miles to mark lewis on Wed Apr 22 2020 17:24:02

No, I switched from SBBS to Mystic a few years back.

ahhhh... i might remember that at some point in the future ;)


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Re: Enigma-Netmail test
By: Alan Ianson to Charles Stephenson on Tue Apr 21 2020 08:49 pm

I have a netmail for you in my outbound but can't connect to your node. Here's a look at the log..

+ 21 Apr 20:47:33 [23162] call to 1:226/16@fidonet
21 Apr 20:47:33 [23162] trying newfrontier.net [98.124.199.3]...
? 21 Apr 20:47:33 [23162] connection to 1:226/16@fidonet failed: Connection refused

Am I listed as 'newfrontier.net' in the nodelist??

It should be frontierbbs.net

Not sure how it got changed. Now that I have most of my echomail networks working, I'm going to update my nodelists for all of them.

Can someone verify this info in the corrent nodelist?

1:226/16 = The Amiga Frontier BBS - frontierbbs.net:24554
1:226/17 = The New Frontier ][ BBS - frontierbbs.net:24556

I wonder if my address is right for the other networks I'm connected to as well. Going to have to check that, thanks for the heads up!
--- SBBSecho 3.10-Linux
* Origin: The New Frontier ][ BBS [frontierbbs.net:23] - OH (1:226/17)

Re: Enigma-Netmail test
By: Richard Miles to Charles Stephenson on Wed Apr 22 2020 06:08 am

Sent one. Let me know here if you would if you get it. I route almost all of my netmail. I know the system will send/receive direct from my hosts but haven't had as much luck with folks that aren't listed in my hub config. Then again, I really haven't had much reason to test either.

Thank you! I'm going to log onto my other BBS to see if I got it
--- SBBSecho 3.10-Linux
* Origin: The New Frontier ][ BBS [frontierbbs.net:23] - OH (1:226/17)

Re: Enigma-Netmail test
By: mark lewis to Charles Stephenson on Wed Apr 22 2020 02:18 pm

I've been doing some tweaking, I've been having issues with my
netmail as well.. If anybody could, send me a netmail to the
address shown on my tagline please?

my system has several routed netmails for your system that are stuck here because my mailer cannot connect to yours for some reason...
+ 22 Apr 14:09:04 [16747] call to 1:226/16@fidonet

22 Apr 14:09:04 [16747] trying newfrontier.net [98.124.199.3]...

It seems that my address is wrong in the nodelist. Who would I talk to about fixing it??
--- SBBSecho 3.10-Linux
* Origin: The New Frontier ][ BBS [frontierbbs.net:23] - OH (1:226/17)

Hello Charles,

Am I listed as 'newfrontier.net' in the nodelist??

226/16 is yes looking at my daily nodelist.

It should be frontierbbs.net

226/17 is listed as frontierbbs.net:24556.

Not sure how it got changed. Now that I have most of my echomail
networks working, I'm going to update my nodelists for all of them.

Can someone verify this info in the corrent nodelist?

1:226/16 = The Amiga Frontier BBS - frontierbbs.net:24554
1:226/17 = The New Frontier ][ BBS - frontierbbs.net:24556

Looks like 226/16 needs updating.

I wonder if my address is right for the other networks I'm connected
to as well. Going to have to check that, thanks for the heads up!

If those need updating you'll need to ask your NC for those nets to update your
info so folks can connect to your node.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Re: Enigma-Netmail test
By: Charles Stephenson to Alan Ianson on Thu Apr 23 2020 16:50:05

Can someone verify this info in the corrent nodelist?

1:226/16 = The Amiga Frontier BBS - frontierbbs.net:24554
1:226/17 = The New Frontier ][ BBS - frontierbbs.net:24556

no... your /16 has newfrontier.net in nodelist.114...


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Re: Enigma-Netmail test
By: Charles Stephenson to mark lewis on Thu Apr 23 2020 16:53:17

22 Apr 14:09:04 [16747] trying newfrontier.net [98.124.199.3]...

It seems that my address is wrong in the nodelist. Who would I talk
to about fixing it??

that would be bill, your network coordinator... he maintains the netseg for your net...


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

On Apr 22nd 3:01 pm mark lewis said...

because my mailer cannot connect to yours for some reason...

+ 22 Apr 14:09:04 [16747] call to 1:226/16@fidonet

22 Apr 14:09:04 [16747] trying newfrontier.net [98.124.199.3]...

? 22 Apr 14:09:04 [16747] connection to 1:226/16@fidonet failed: Connection refused

I sent a email to Janis about the address listed in the nodelist. For some reason it says 'newfrontier.net' and not 'frontierbbs.net' Which is kinda weird, I got both Fido addresses at the same time, and my other node is correct. Hopefully it'll be updated in the next nodelist



--- ENiGMA 1/2 v0.0.11-beta (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

On Apr 22nd 3:01 pm Alan Ianson said...

His hostname is frontierbbs.net currently and that works.

I think the nodelist needs an update if Charles is going to be using that domain going forward.

I sent Janis a email about it. I thought maybe I was having a issue with the BBS software (Enigma), It just got out of alpha recently. Now I know my problem! (Hopefully!)



--- ENiGMA 1/2 v0.0.11-beta (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

Re: RE: Enigma-Netmail test
By: Charles Stephenson to mark lewis on Wed May 06 2020 02:44:24

+ 22 Apr 14:09:04 [16747] call to 1:226/16@fidonet
22 Apr 14:09:04 [16747] trying newfrontier.net [98.124.199.3]...
? 22 Apr 14:09:04 [16747] connection to 1:226/16@fidonet failed: Connection refused

I sent a email to Janis about the address listed in the nodelist.

ok but i don't understand why... you should be speaking with your NC bill burton... or your new R11C nicholas boel... or possibly Z1C nick andre... but certainly starting with bill burton... he is usually pretty communicative... at least he was when he was here in my area...

For some reason it says 'newfrontier.net' and not 'frontierbbs.net'
Which is kinda weird, I got both Fido addresses at the same time,
and my other node is correct. Hopefully it'll be updated in the
next nodelist

i hope it gets fixed for you soon... its only been like 9 or 10 days, so far...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello mark,

On Wed May 06 2020 04:14:24, mark lewis wrote to Charles Stephenson:

+ 22 Apr 14:09:04 [16747] call to 1:226/16@fidonet
22 Apr 14:09:04 [16747] trying newfrontier.net
[98.124.199.3]... ? 22 Apr 14:09:04 [16747] connection to
1:226/16@fidonet failed: Connection refused

i hope it gets fixed for you soon... its only been like 9 or 10 days,
so far...

In case Bill doesn't read here and he wasn't contacted by the OP, I've passed on the word to Bill and ack'd it here as well.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Re: Enigma-Netmail test
By: Nicholas Boel to mark lewis on Wed May 06 2020 16:33:56

i hope it gets fixed for you soon... its only been like 9 or 10 days,
so far...

In case Bill doesn't read here and he wasn't contacted by the OP,
I've passed on the word to Bill and ack'd it here as well.

cool! glad you're in the loop :)


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Re: RE: Enigma-Netmail test
By: mark lewis to Charles Stephenson on Wed May 06 2020 04:14 am

ok but i don't understand why... you should be speaking with your NC bill burton... or your new R11C nicholas boel... or possibly Z1C nick andre... but certainly starting with bill burton... he is usually pretty communicative... at least he was when he was here in my area...

I had a heck of a time back when I was trying to actually get in the nodelist. I contacted all of the above and Andre added one node. when I wanted the other added Janis did it. I'll try again.

i hope it gets fixed for you soon... its only been like 9 or 10 days, so far...

Yeah ME too....
--- SBBSecho 3.11-Linux
* Origin: The New Frontier ][ BBS [frontierbbs.net:23] - OH (1:226/17)

Charles Stephenson wrote in a message to Bill Burton:

Re: Enigma-Netmail test
By: Bill Burton to Charles Stephenson on Thu May 14 2020 04:07 pm

Charles You should have sent me a netmail, I got the word about the problem last week and have submitted an updated nodelist segement
to Nick.
It should make in this weeks new nodelist.

Thank you, I noticed the correct address. :)
___ SBBSecho 3.11-Linux
- Origin: The New Frontier ][ BBS [frontierbbs.net:23] - OH
(1:226/17)

You are welcome.

Later,
Bill


---
* Origin: INA:fidonet.wabusa.com, IBN (1:2215/15)