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 ...
Did your system process the netmail, and then send it to Agency? I'd
How are you ever going to learn if you don't ask?! ;)
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)
Meant to say if you 21:3/226 ... I only just got the node #
yesterday, can't remember it :)
However, since it's NetMail, will it be delivered if sent to clouddancer@?
As long as clouddancer is your alias/handle on the BBS.
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.
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.
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.
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 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
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
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. ;)
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 ...
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...
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.
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 ...
So this should mean, my Netmail works ...
Yet, I do not receive any direct netmail from any of you guys :(
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.
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.
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.
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.
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 ;)
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.
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
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.]
We know that sending addresses to Paul's /999 addresses works without an issue, nodes have been doing that for years.
Assuming that all gets routed, and since ...
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!
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.
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).
| Sysop: | Chris Crash |
|---|---|
| Location: | Huntington Beach, CA. |
| Users: | 632 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 58:34:34 |
| Calls: | 11,039 |
| Files: | 5 |
| Messages: | 589,835 |