Thank you all for the comments. I've tried mail to callsign@bbs.ampr.org and indeed it does work. I tested only the internet side because I do not have any ampernet users on the RF side but I assume the RF side would work. Using JNOS, this mail went out on the encap port via SMTP vs. h-addressed mail that goes out based on connects in the forward.bbs scripts. I learned something and another tool for the tool box.
Jerry, N0MR
-----Original Message----- From: Brian Sent: Saturday, July 11, 2015 9:18 AM To: AMPRNet working group Subject: Re: [44net] ampr.org mail
(Please trim inclusions from previous messages) _______________________________________________ Mail should go to whoever has the mx record in dns for (Callsign).ampr.org.
Pardon my brevity, as I'm on a smartphone. Sent through via axMail-fax by N1URO.
Sent with AquaMail for Android http://www.aqua-mail.com
On July 11, 2015 10:01:58 AM "Lakenet" n0mr@lakenet.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ One last question. If I address mail as callsign@bbs.ampr.org where callsign and bbs are active users and bbs, will this mail go anywhere in the ampernet? Providing the routing is active.
Jerry, N0MR
-----Original Message----- From: Rial Sloan Sent: Saturday, July 11, 2015 8:44 AM To: AMPRNet working group Subject: Re: [44net] ampr.org mail
(Please trim inclusions from previous messages) _______________________________________________ Sorry, gotta say it:
21st century and BBS??
There's something here about stones and glass houses. On Jul 11, 2015 8:47 AM, "William Lewis" kg6baj@n1oes.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ 21st Century and SMTP ??
Pretty wrong, so I think you don't know anything about H-Addressing.
First off, SMTP (email) is just like someones home phone number. If you dial the wrong phone number, you either get the wrong house, or you get none at all. Same with email. If you don't have the 100% correct email address, the message doesn't get through at all, or winds up in the wrong persons in-box.
With H-Addressing, YOU DON'T HAVE TO KNOW THE EXACT ADDRESS!
That's one of the many beautiful things about packet messaging forwarding.
Let me explain.... My packet address looks like this KG6BAJ@KG6BAJ.#NCA.CA.USA.NOAM.
The ".#NCA.CA.USA.NOAM" is the Hierarchical part of the address. The ".#NCA"denotes SUBSECTION of the state (in this case Northern CAlifornia), then the state "CAlifornia (.CA)", then the Country (.USA), then the continent of North America (.NOAM).
With HAddressing, Someone really doesn't need to know the precise address like you do with phone & email (The SMTP you refer too). Someone wants to send me packet mail, they really only need just a part of my address, which they could guess by running my callsign through something like QRZ. Someone could send me a packet mail addressed to "KG6BAJ@.#USA.NOAM" (notice the huge difference from KG6BAJ@KG6BAJ.#NCA.CA.USA.NOAM).
Properly configured NOS/FBB/Misc full service BBS's then can at least determine that the message is intended for USA, in North America, and forward the message along.
Since my BBS is in fact located within USA, in North America, then I'll get the message, and drop it in the correct mailbox.
Try doing that with an SMTP (email) message. Just won't work.
To those who don't fully understand the brilliants of Hierarchical I suppose it would seem antiquated. But nothing else gets that message through like packet radio and H-Addressing.
And one another note, you state all NOS stations run SMTP. Also not true. It depends on if the sysop has built it in at time of compiling it features.
And..... not all Full-Service BBS's run NOS.
Bill Lewis, KG6BAJ
At 05:51 PM 7/10/2015, you wrote:
Jerry, Are you talking about the BBS Hierarchical Addressing Protocol that is common with people running NOS BBS'es? ftp://ftp.tapr.org/bbssig/recommendations/hierarchical In all honesty from what I remember it's a lot of manual configuration, that really seems quaint to me since all the NOS programs also speak SMTP, the standard today.
It would seem the same could be accomplished using SMTP standards by setting up some mail aliases. I'm going to recommend the TAPR NOS-BBS list for (Hierarchical forwarding) things of the non 21st century: