• Netmail

    From CloudDancer@21:3/226 to All on Fri Jan 23 11:33:53 2026
    Howdy All,

    So what is the proper way to check/send Netmail (or really, to set it up on a BBS for users)?

    I personally followed Avon's YT video on creating Netmail base-type in my fsxNet group, with Net Address 21:3/226 (my node) ... I call it "fsxNet - Private Netmail (21:*)"...

    When I select this area and post a message, after typing username, this being netmail, it asks for a netmail address (as expected) ... I enabled search, so I can type Agency and find 21:1/101 confirming I want to netmail user peconi@21:1/101 ...

    However, when I login to Agency BBS, I cannot find this message anywhere... Unlike my Silfen Path BBS, Agency does not seem to list Netmail area anywhere ...

    I go to Messages (M), then New Message Scan (N) and nothing is found waiting for me anywhere ....

    So, either Agency BBS does not support Netmail (which would strike me as odd), or I don't know what I'm doing once there :) ...

    Also, how do I send Netmail to say CloudDancer @ 21:3/226 from Agency?

    Sorry for all the possibly n00b questions, but I forgot more than I ever knew ... That should be a tag line ...

    Cheers,

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Silfen Path BBS: Columbus,Ohio: bbs.silfenpath.com (21:3/226)
  • From Accession@21:1/700 to CloudDancer on Fri Jan 23 12:51:32 2026
    Hey Clouddancer!

    On Fri, Jan 23 2026 10:33:53 -0600, you wrote:

    When I select this area and post a message, after typing username,
    this being netmail, it asks for a netmail address (as expected) ...
    I enabled search, so I can type Agency and find 21:1/101 confirming
    I want to netmail user peconi@21:1/101 ...

    This sounds correct.

    However, when I login to Agency BBS, I cannot find this message
    anywhere... Unlike my Silfen Path BBS, Agency does not seem to list
    Netmail area anywhere ...

    Did your system process the netmail, and then send it to Agency? I'd imagine this would be able to be seen in your tosser's logs, and then your mailer's logs. Unless you have it setup to poll immediately after you logoff your system, it might take a bit for your system to poll at it's scheduled interval. So the mail could have been sitting on your system still waiting to go out.

    I go to Messages (M), then New Message Scan (N) and nothing is found
    waiting for me anywhere ....

    Try an area list, and see if there's an area that looks like it would be for "Netmail".

    So, either Agency BBS does not support Netmail (which would strike
    me as odd), or I don't know what I'm doing once there :) ...

    It definitely supports netmail. I've talked back and forth with Avon plenty of times over the years.

    Also, how do I send Netmail to say CloudDancer @ 21:3/226 from
    Agency?

    You might have to look for and join the netmail area (which may or may not be in the FSXnet converence/group). Then you can probably hit (P) to post a message and it might ask you the same questions as above.

    Sorry for all the possibly n00b questions, but I forgot more than I
    ever knew ... That should be a tag line ...

    How are you ever going to learn if you don't ask?! ;)

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.35-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)
  • From CloudDancer@21:3/226 to Accession on Fri Jan 23 15:51:06 2026
    Did your system process the netmail, and then send it to Agency? I'd

    Yep, saw one mail out in the results of mutil which gets auto called.

    I looked for a Netmail-like area all over, but could not find it on Agency BBS ... If you have the ability, can you try and netmail me and I'll reply back:
    - clouddancer@21:3/262

    How are you ever going to learn if you don't ask?! ;)

    Thanks :)

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    ... Error 3032 - Recursion error. See error 3032.

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Silfen Path BBS: Columbus,Ohio: bbs.silfenpath.com (21:3/226)
  • From Accession@21:1/700 to CloudDancer on Fri Jan 23 17:07:00 2026
    Hey Clouddancer!

    On Fri, Jan 23 2026 14:51:06 -0600, you wrote:

    I looked for a Netmail-like area all over, but could not find it on
    Agency BBS ... If you have the ability, can you try and netmail me
    and I'll reply back: - clouddancer@21:3/262

    * Origin: Silfen Path BBS: Columbus,Ohio: bbs.silfenpath.com
    (21:3/226)

    I've now also sent a netmail to you at 21:3/226, since that is what your origin line says, but not what you originally wrote to me. ;)

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.35-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)
  • From Accession@21:1/700 to CloudDancer on Fri Jan 23 17:08:29 2026
    Hey Clouddancer!

    On Fri, Jan 23 2026 14:54:46 -0600, you wrote:

    Meant to say if you 21:3/226 ... I only just got the node #
    yesterday, can't remember it :)

    Saw this after the fact, but I caught it. 262 was easy for me to remember, because it's my area code. From here on out I'd probably continue entering the wrong one. ;)

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.35-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)
  • From CloudDancer@21:3/226 to Accession on Fri Jan 23 18:32:02 2026
    Accession,

    The only things in my mailin logs are:

    Jan 23 17:19:03 Netmail from Clearing Houz (21:3/100) to CloudDancer (21:3/226)

    Jan 23 17:19:03 Netmail from Clearing Houz (21:3/100) to Petar Smilajkov (21:3/226)

    So, clearly netmail of sorts is coming to me, at least from Clearing Houz. I know that works as I can send AreaFix and FileFix messages, and get replies back ...

    But, no private messages whatsoever. :(

    So odd...

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From CloudDancer@21:3/226 to CloudDancer on Fri Jan 23 18:57:14 2026
    Some troubleshooting steps for my Netmail:

    Sending Netmail to ping @ Clearing House
    - from Petar Smilajkov@21:3/226 to ping@21:3/100

    --LOG-->
    Resuming from 21 in netmailfsx
    Jan 23 18:50:26 Route (Petar Smilajkov@21:3/226 to ping@21:3/100) via 21:3/100 Jan 23 18:50:26 Export netmailfsx #21 to 21:3/100@fsxnet
    Jan 23 18:50:26 1 msgs from fsxNet - ** NETMAIL (21:*) **

    Jan 23 18:50:26 Results: 0 echo, 1 net, 0 skipped in 0.03s
    <--LOG END--

    At next mailin scan I get this in the log:

    --LOG-->
    Jan 23 18:51:09 Process: Importing EchoMail
    Jan 23 18:51:09 Waiting for BUSY nodes
    Jan 23 18:51:09 Import from /home/mystic/bbs/echomail/in/
    Jan 23 18:51:09 Importing 00002cdd.pkt (21:3/100 to 21:3/226)
    Jan 23 18:51:09 Netmail from Clearing Houz (21:3/100) to Petar Smilajkov (21:3/226)
    Jan 23 18:51:09 Import from /home/mystic/bbs/echomail/in/unsecure/
    Jan 23 18:51:09 Results: 0 echo, 1 net, 0 dupes, 0 tossed in 0.01s
    <--LOG END--

    And I receive back netmail from Clearing House, can see it in my Netmail area with the following log

    +---------------------------------------------------------[ CONTROL LINES ]-+ DATE: 2026-01-23 18:50:24
    MSGID: 21:3/226 f4f87df7
    INTL 21:3/100 21:3/226
    TID: Mystic BBS 1.12 A48 +------------------------------------------------------------------[ PATH ]-+ No path information? This would be normal if this message came directly to
    the hub
    +----------------------------------------------------------------[ ORIGIN ]-+ *NO ORIGIN* (21:3/226.0) +-----------------------------------------------------------[ END MESSAGE ]-+

    So this should mean, my Netmail works ...

    Yet, I do not receive any direct netmail from any of you guys :(

    Hmph?

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From Al@21:4/106 to CloudDancer on Fri Jan 23 16:06:08 2026
    However, since it's NetMail, will it be delivered if sent to clouddancer@?

    As long as clouddancer is your alias/handle on the BBS.

    If a message for John Doe arrives at your node it will not be listed or read by anyone other than John Doe.

    Mystic will not show a private message to anyone aside from the person it is addressed to. Even the sysop will not see/read the message unless that is their name or alias.

    --- BBBS/Li6 v4.10 Toy-7
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From CloudDancer@21:3/226 to Al on Fri Jan 23 19:14:03 2026
    Al,

    As long as clouddancer is your alias/handle on the BBS.

    Correct, that is the case ...

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From Al@21:4/106 to CloudDancer on Fri Jan 23 16:22:10 2026
    As long as clouddancer is your alias/handle on the BBS.

    Correct, that is the case ...

    Good stuff. I would netmail you directly but your node is not yet listed in nodelist. I'll route a netmail to you so hopefully you will get it.

    --- BBBS/Li6 v4.10 Toy-7
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From CloudDancer@21:3/226 to Al on Fri Jan 23 19:28:14 2026
    Al,

    Good stuff. I would netmail you directly but your node is not yet listed in nodelist. I'll route a netmail to you so hopefully you will get it.

    Everything "seems" to be working as I even sent netmail to ping@21:1/100
    (Risa HUB), and I got back a reply via Netmail that it works.

    I even send AREAFIX message to 21:1/101 - it of course tells me I am unauthorized, but clearly netmail goes out, and comes back in ...

    Stumped for the moment as to what is going on with incoming netmail ...

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From Al@21:4/106 to CloudDancer on Fri Jan 23 17:28:14 2026
    Keep an eye on your log.

    I'm going to log into Agency and try to send you a netmail from there. May work may not but once your node is listed it'll work as expected.

    I have no access to netmail on Agency BBS but I will netmail you once your node is listed.

    Best I can do for now.. ;)

    --- BBBS/Li6 v4.10 Toy-7
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From CloudDancer@21:3/226 to Al on Fri Jan 23 20:58:11 2026
    Al,

    I have no access to netmail on Agency BBS but I will netmail you once
    your node is listed.

    Thanks Al.

    I belive the setting under Configuration -> Message Settings called "Force NL Match" if set to Yes allows you to send netmail only to recognized systems.

    If set to No, it may allow you to send to my BBS before it is listed.

    Not asking you to change this, just FYI - as I was just playing with that stuff today as I was setting up the maintenance scripts for mutil, especially MergeNodeLists section ;)

    Cheers! Hopefully @ deon can add me to the list though I thought that was automated to some extend from his website into the nodelist files.

    Thanks!

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From Al@21:4/106 to CloudDancer on Fri Jan 23 18:45:32 2026
    I belive the setting under Configuration -> Message Settings called "Force NL Match" if set to Yes allows you to send netmail only to recognized systems.

    If set to No, it may allow you to send to my BBS before it is listed.

    My mailer is part of BBBS so I have no such setting. I can either turn it off or on and it's better on. That way it catches my typos!

    Cheers! Hopefully @ deon can add me to the list though I thought that was automated to some extend from his website into the nodelist files.

    I suspect deon has already done this. The master nodelist is compiled by Avon automagically I think, so your node will be listed in the next update.

    --- BBBS/Li6 v4.10 Toy-7
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From CloudDancer@21:3/226 to CloudDancer on Fri Jan 23 15:54:46 2026
    Sorry,

    I looked for a Netmail-like area all over, but could not find it on
    Agency BBS ... If you have the ability, can you try and netmail me and I'll reply back: - clouddancer@21:3/262

    Meant to say if you 21:3/226 ... I only just got the node # yesterday, can't remember it :)

    Tnx.

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Silfen Path BBS: Columbus,Ohio: bbs.silfenpath.com (21:3/226)
  • From Accession@21:1/700 to CloudDancer on Fri Jan 23 17:03:42 2026
    Hey Clouddancer!

    On Fri, Jan 23 2026 14:51:06 -0600, you wrote:

    Yep, saw one mail out in the results of mutil which gets auto
    called.

    Ok. Then at least we know it was sent.

    I looked for a Netmail-like area all over, but could not find it on
    Agency BBS ... If you have the ability, can you try and netmail me
    and I'll reply back: - clouddancer@21:3/262

    I connected over there, and looked everywhere I would think it /should/ be, and also couldn't find it. So I'm not sure what he has going on.

    Either way, I sent a netmail. I send all netmail for zone 21 to Avon, so he should forward it on to the net 3 hub (deon?) and then to you. If you don't get it, something else might be broken, like his "Y" command from his main menu on his BBS.

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.35-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)
  • From CloudDancer@21:3/226 to Accession on Fri Jan 23 18:25:21 2026
    Hey,

    I've now also sent a netmail to you at 21:3/226, since that is what your origin line says, but not what you originally wrote to me. ;)

    Thanks, smart!

    I will look to see if I receive it and let you know.

    However, since it's NetMail, will it be delivered if sent to clouddancer@?

    I wonder if Real Names must be used so Petar Smilajkov would be better ... Hmmmm ...

    Thank you for testing w/ me either way!

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From Al@21:4/106 to CloudDancer on Fri Jan 23 16:40:04 2026
    Good stuff. I would netmail you directly but your node is not yet listed
    in nodelist. I'll route a netmail to you so hopefully you will get it.

    Everything "seems" to be working as I even sent netmail to ping@21:1/100 (Risa HUB), and I got back a reply via Netmail that it works.

    OK, I did send you a netmail but my mailer bounced it back to me because your node is not yet listed.

    I even send AREAFIX message to 21:1/101 - it of course tells me I am unauthorized, but clearly netmail goes out, and comes back in ...

    Sounds like your netmail setup is good.

    Stumped for the moment as to what is going on with incoming netmail ...

    Keep an eye on your log.

    I'm going to log into Agency and try to send you a netmail from there. May work may not but once your node is listed it'll work as expected.

    --- BBBS/Li6 v4.10 Toy-7
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From deon@21:2/116 to CloudDancer on Sat Jan 24 17:27:33 2026
    Re: Re: Netmail
    By: CloudDancer to Accession on Fri Jan 23 2026 06:32 pm

    Howdy,

    So, clearly netmail of sorts is coming to me, at least from Clearing Houz. I know that works as I can send AreaFix and FileFix messages, and get replies back ...

    But, no private messages whatsoever. :(

    So odd...

    I see Accession has been helping you out, so I've not jumped in yet.

    Anyway thought I'd share a couple of things.

    * On agency, you might not have sufficent security level to use Netmail (if you cannot see that message area). But it definately supports netmail.

    * Mail to/from you is logged on the hub - look at the "Packets and Files Sent" tab of your BBS entry. When you click on a packet, you'll see what messages where in that packet was sent to you.

    You can use this hub's information, together with your tosser and mailer logs to see what is going out and coming in, and whether stuff coming in is being processed.

    If you dont see anything on clrghouz, it means you arent sending it out - or if you are expecting something, it hasnt come to the hub yet.


    ...лоеп
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From deon@21:2/116 to CloudDancer on Sat Jan 24 17:30:46 2026
    Re: Re: Netmail
    By: CloudDancer to Al on Fri Jan 23 2026 08:58 pm

    Howdy,

    Cheers! Hopefully @ deon can add me to the list though I thought that was automated to some extend from his website into the nodelist files.

    It is completely automated.

    Nodelists only come out weekly :)


    ...лоеп
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Accession@21:1/700 to CloudDancer on Sat Jan 24 07:18:35 2026
    Hey Clouddancer!

    On Fri, Jan 23 2026 17:25:21 -0600, you wrote:

    However, since it's NetMail, will it be delivered if sent to
    clouddancer@?

    I wonder if Real Names must be used so Petar Smilajkov would be
    better ... Hmmmm ...

    If you allow aliases in netmail, it should be fine. I don't remember if that's an actual setting in Mystic or not, it may just be allowed all the time.

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.35-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)
  • From Accession@21:1/700 to CloudDancer on Sat Jan 24 07:26:29 2026
    Hey Clouddancer!

    On Fri, Jan 23 2026 17:57:14 -0600, you wrote:

    So this should mean, my Netmail works ...

    It means that netmail between you and Clearing Haus is working.

    Yet, I do not receive any direct netmail from any of you guys :(

    I feed from Avon in net 1, so there is a PATH my netmail would take to get to you:

    21:1/200 (me) -> 21:1/100 (Avon) -> 21:3/100 (Deon) -> 21:3/226 (you) is the normal routing path netmail would take from me to you, and would go in reverse from you to me. Try sending me a netmail at Accession@21:1/200 and we can see if that works. Otherwise, something may be broken over on Avon's system, especially if Deon never got my netmail to forward on to you.

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.35-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)
  • From CloudDancer@21:3/226 to Accession on Sat Jan 24 13:20:36 2026
    Accession,

    in reverse from you to me. Try sending me a netmail at
    Accession@21:1/200 and we can see if that works. Otherwise, something


    Did this just now ... Not sure I will get your reply until I am in the node list, but you should at least get my message.

    Cheers,

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From Accession@21:1/700 to CloudDancer on Sat Jan 24 13:37:31 2026
    Hey Clouddancer!

    On Sat, Jan 24 2026 12:20:36 -0600, you wrote:

    Did this just now ... Not sure I will get your reply until I am in
    the node list, but you should at least get my message.

    Received, and replied. You should now be getting a response, as for some reason Golded isn't allowing me to use my nickname/alias for FSXnet netmail (which may have been the reason it didn't work before).

    FYI, nodelists are not /needed/ for netmail. They can be used, and nodelist lookups like Mystic's "nodelist browser" are just helpful if you don't actually know how to reach someone or what their node number is. Otherwise, as long as proper routing is in place, netmail goes where it should.

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.35-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)
  • From deon@21:2/116 to Accession on Sun Jan 25 09:07:59 2026
    Re: Re: Netmail
    By: Accession to CloudDancer on Sat Jan 24 2026 01:37 pm

    Howdy,

    FYI, nodelists are not /needed/ for netmail. They can be used, and nodelist lookups like Mystic's "nodelist browser" are just helpful if you don't actually know how to reach someone or what their node number is. Otherwise, as long as proper routing is in place, netmail goes where it should.

    This is mostly true, but...

    Some folks use RTNtrack (?) which will bounce a netmail addressed to a non-nodelisted system. Not sure if Paul is using it...

    Clrghouz will also bounce netmail back if you send it to a non-existant address (for addresses that it is reponsible for). Well, it should anyway... :) Its better to get a reply (no system exists), then nothing and wondering why nobody responded.


    ...лоеп
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Ray Quinn@21:3/209 to CloudDancer on Sat Jan 24 22:23:35 2026

    Hello CloudDancer!

    23 Jan 26 18:32, you wrote to Accession:

    So, clearly netmail of sorts is coming to me, at least from Clearing
    Houz. I know that works as I can send AreaFix and FileFix messages,
    and get replies back ...

    I also sent you a netmail around 8:55 PM Pacific Standard Time (UTC-8:00) to clouddancer@21:3/226 from the BBS (21:3/208) as a test and also to test the route. However, I find it is still in my outbound mail folder for my hub. Something to figure out on my end,too.


    73 de Ray
    Visalia, CA DM06ii
    W6RAY/WRKZ506

    ... Better to be judged by 12 than carried by 6!
    --- GoldED+/W32-MSVC 1.1.5-b20240306
    * Origin: Ray's Road Node | Somewhere in California. (21:3/209)
  • From CloudDancer@21:3/226 to Ray Quinn on Sun Jan 25 10:39:20 2026
    Hi Ray,

    I also sent you a netmail around 8:55 PM Pacific Standard Time
    (UTC-8:00) to clouddancer@21:3/226 from the BBS (21:3/208) as a test and also to test the route. However, I find it is still in my outbound mail folder for my hub. Something to figure out on my end,too.

    It may be because I am not yet in the weekly nodelist... Once I am it'll probably propagate at that time.

    I do believe I have everything set up now correctly as I am exchanging netmail with a few others as well.

    Thank you!

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    ... "No comment" is a comment.

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From Accession@21:1/700 to deon on Sun Jan 25 10:25:14 2026
    Hey Deon!

    On Sat, Jan 24 2026 16:07:59 -0600, you wrote:

    Some folks use RTNtrack (?) which will bounce a netmail addressed to
    a non-nodelisted system. Not sure if Paul is using it...

    Doesn't seem like Avon uses that, netmail flowed just fine in this case via proper routing.

    Clrghouz will also bounce netmail back if you send it to a non-
    existant address (for addresses that it is reponsible for). Well, it
    should anyway... :) Its better to get a reply (no system exists),
    then nothing and wondering why nobody responded.

    That's your opinion and what you choose to do with your own program. You have also mentioned that Clrghouz stops echomail from flowing in certain conditions, too. Both of which I don't agree with, but YMMV.

    If proper routing is in place, it should work just fine. If a non-nodelisted address sends a netmail, and routes /* to the hub, it should still go there, no matter if there's a nodelist in place or not. The hub would then route the netmail to the destination address via proper routing, also.

    If the /destination/ address is not known or setup properly, then this is when it would/could fail. Since I route 21:* to Avon, if his system can deal with a /999 address, it should work no matter what, with or without a nodelist. If RNTrack stops that from happening, that's RNTrack's problem. I don't use it, and it seems neither does Avon.. or maybe he does and it still doesn't require a nodelist, but instead uses his HPT config's defined links/routing table, rather than a nodelist.

    In this specific case, Avon obviously has some kind of routing for /999 in place. New systems use that address for testing purposes, so the destination's connection address changes (so I assume Avon holds the mail on his system for /999 to pick up - which can mean that /any/ system with that address setup could connect and get the netmail, which can be a point of failure if a different system connects at the right time using that same node number, but the netmail's TO field doesn't match the sysop/user name), but it did seem to work in this case.

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.35-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)
  • From CloudDancer@21:3/226 to Accession on Sun Jan 25 11:43:04 2026
    Accession,

    In this specific case, Avon obviously has some kind of routing for /999
    in place. New systems use that address for testing purposes, so the destination's connection address changes (so I assume Avon holds the
    mail on his system for /999 to pick up - which can mean that /any/
    system with that address setup could connect and get the netmail, which can be a point of failure if a different system connects at the right
    time using that same node number, but the netmail's TO field doesn't
    match the sysop/user name), but it did seem to work in this case.

    I think this is the case... It worked for me to pick up mail as I was probably the only guy testing with /999 ... If there were more, then someone else could have picked up my messages before me.

    FYI - I now have proper node on FidoNet 1:226/20 (thanks Nick Boel), and need not use /999 for anything any more ;)

    Cheers!

    -=-=-=-=-=-=-=-
    CloudDancer
    -=-=-=-=-=-=-=-

    ... Classic: A book which people praise but don't read. - Mark Twain

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)
  • From Accession@21:1/200 to CloudDancer on Sun Jan 25 10:48:26 2026
    Hey CloudDancer!

    On Sun, 25 Jan 2026 11:43:04 -0500, you wrote:

    I think this is the case... It worked for me to pick up mail as I was probably the only guy testing with /999 ... If there were more, then
    someone else could have picked up my messages before me.

    Yep. Not very often are multiple people trying to use an address like that at the exact same time these days, but it is definitely possible for it to happen.

    FYI - I now have proper node on FidoNet 1:226/20 (thanks Nick Boel),
    and need not use /999 for anything any more ;)

    Glad everything worked out smoothly! ;)

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From deon@21:2/116 to Accession on Mon Jan 26 08:24:55 2026
    Re: Re: Netmail
    By: Accession to deon on Sun Jan 25 2026 10:25 am

    Howdy,

    That's your opinion and what you choose to do with your own program. You have also mentioned that Clrghouz stops echomail from flowing in certain conditions, too. Both of which I don't agree with, but YMMV.

    Both? So when this text started, the request was to send a netmail to 21:3/262, (when the node is listed as 21:3/226).

    Had you not picked that up, the converstation would have gone:

    * sender: I sent you a netmail
    * receipient: I didnt get your netmail
    * conclusion: The network is broken somewhere

    Instead, had you sent the netmail to 21:3/262 - which clrghouz is authoritive over, it would have bounced the netmail (or rather discarded it) - and sent you a netmail back saying there is no host to collect it. [Well it should do that, and if it isnt anymore, I will fix that.]

    If this is a situation you dont agree with, then that suprises me.

    On the same topic, if a hub 3 node send a netmail to 21:1/32700, then clrghouz will happily send it to hub 1 to figure out what to do to it.

    Regarding the echomail, yes, clrghouz doesnt process echomail when the sender has set up their system correctly (ie: wrong AKA, or missing origin line from which the AKA is derived) - and again, it sends back a netmail to them with an explanation.

    Both those are intended to help the (new) sysop setup there systems correctly, and is very affective in its outcome - across multiple othernets.

    In this specific case, Avon obviously has some kind of routing for /999 in place. New systems use that address for testing purposes, so the

    We know that sending addresses to Paul's /999 addresses works without an issue, nodes have been doing that for years. I brought up the comments about rtntrack for mail originating from /999 and going the other direction (especially fidonet).

    Assuming that all gets routed, and since the sender was saying they were not getting it, I suggested that perhaps rtntrack somewhere in the network was blocking it. I dont use rtntrack, so do know if it rejects based on source AKA as well, or uplinks are using other home grown tools to interceipt mail for non-nodelisted or test AKAs.


    ...лоеп
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Accession@21:1/200 to deon on Sun Jan 25 17:34:36 2026
    Hey deon!

    On Mon, 26 Jan 2026 08:24:54 +1100, you wrote:

    Both? So when this text started, the request was to send a netmail to 21:3/262, (when the node is listed as 21:3/226).

    Had you not picked that up, the converstation would have gone:

    You must have missed this part of the conversation:

    * sender: I sent you a netmail
    * receipient: I didnt get your netmail

    * sender: Oh, I realized I used the wrong node number, here is a new reply using the correct one.
    * recipient: Received!

    * conclusion: The network is broken somewhere

    I don't think this conversation ever got to this "conclusion." Right before realizing the wrong node number was used I said there was a possibility something was broken somewhere. That didn't mean anything /is/ "broken". We (very) soon realized that was not the case, which is about the time you jumped into the conversation to try to tell me I was wrong about nodelists not being needed to route netmail, and then went on about RNTrack, which wasn't even part of the conversation to begin with.

    Instead, had you sent the netmail to 21:3/262 - which clrghouz is authoritive over, it would have bounced the netmail (or rather discarded
    it) - and sent you a netmail back saying there is no host to collect it. [Well it should do that, and if it isnt anymore, I will fix that.]

    Let's go with: (1) The first two netmails I sent were addressed wrong, and they didn't work. I don't know where they ended up after they left here and went to Avon. If they never made it to you, re-read (1). I never got anything from clrghouz, if that matters any (it really doesn't, to me).

    We know that sending addresses to Paul's /999 addresses works without an issue, nodes have been doing that for years.

    We figured that out, already. Thanks for the clarification, though!

    Assuming that all gets routed, and since ...

    Welp, it did indeed work (both ways), which we mentioned in the next few messages in the same conversation/thread.

    For the record, you jumped into the discussion to tell me "This is mostly true, but..." and then started talking about RNTrack (which was never brought up in the first place), when I simply stated a nodelist is /not/ needed for routing netmail. My statement still stands, with no ifs, ands, or buts about it. I haven't used a nodelist in.. ever.

    Honestly, I was just helping someone out. I've been doing this stuff for quite some time, and don't need a rundown on how things work (or how you think it should work). EOT.

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From deon@21:2/116 to Accession on Mon Jan 26 12:55:32 2026
    Re: Netmail
    By: Accession to deon on Sun Jan 25 2026 05:34 pm

    Howdy,

    Both? So when this text started, the request was to send a netmail to 21:3/262, (when the node is listed as 21:3/226).

    Had you not picked that up, the converstation would have gone:

    You must have missed this part of the conversation:

    * sender: I sent you a netmail
    * receipient: I didnt get your netmail

    * sender: Oh, I realized I used the wrong node number, here is a new reply using the correct one.
    * recipient: Received!

    I didnt, you quoted it above. I was talking "ifs" - by using the statement: "Had you not picked that up...". I know the (fsx) netmails were sent and received, I read that too. I also read that the fidonet ones finally worked as well when something was done to the message bases...

    jumped into the conversation to try to tell me I was wrong about nodelists not being needed to route netmail, and then went on about RNTrack, which wasn't even part of the conversation to begin with.

    I didnt say you were wrong, I used the phrase "This is mostly true, but...". I added more context to your statement "FYI, nodelists are not /needed/ for netmail.", and then you finished with "Otherwise, as long as proper routing is in place, netmail goes where it should.".

    Based on my experience, I certainly have had netmails not meet their destatination because a new node hasnt made it to the nodelist yet, as well as a node no longer listed in the nodelist. In those examples it was a tool like RTNtrack (if that is what is called) used by a system in the path, send me a netmail telling me so.

    Honestly, I was just helping someone out. I've been doing this stuff for quite some time, and don't need a rundown on how things work (or how you think it should work).

    Me too...


    ...лоеп
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)