<HTML><HEAD>
<STYLE><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></STYLE>
</HEAD>
<BODY dir=ltr class=hmmessage>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>Hi Bill,</DIV>
<DIV> </DIV>
<DIV>Good points all. When the network was originally designed, I
understand that the use of SMTP was desired and one of the reasons why JNOS was
chosen. I have since come to understand that our current BBS naming
convention is not compatible with the requirement that the haddress not include
an SSID. I wish we had known that before. We may have to migrate
away from that if we want better integration with the traditional BBS
network. The question we will have to grapple with is how important that
is, given the shrinking population of traditional BBSs. That’s not to
malign packet in anyway. It’s just the reality of today and the question I
get from users when I bring up such issues.</DIV>
<DIV> </DIV>
<DIV>If we were to move away from all SMTP to a mixture of SMTP and BBS
forwarding, then, using the examples you provided earlier, address rewriting
could be used to avoid the use of the gateway for some cases. But I don’t
think it would be correct to say it would eliminate all cases of local use of
the gateway.</DIV>
<DIV> </DIV>
<DIV>It will still be true that, if you have a local SMTP destination that can
accept JNOS SMTP messages directly, then it’s still better to send it direct,
than to ALWAYS send it to a gateway, which must then turn around and send it
back over the air to the destination.</DIV>
<DIV> </DIV>
<DIV>Michael</DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=thunderft@hotmail.com
href="mailto:thunderft@hotmail.com">Wm Lewis</A> </DIV>
<DIV><B>Sent:</B> Monday, December 12, 2011 9:34 AM</DIV>
<DIV><B>To:</B> <A title=nos-bbs@tapr.org
href="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</A> </DIV>
<DIV><B>Subject:</B> Re: [nos-bbs] FW: smtp gateway options</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV dir=ltr>Michael:<BR> <BR>Your question asked if there was any
'objection'.<BR> <BR>I have no objection to the 'proposal', but I do pick
up a cringe at one of the <EM><U>reasons</U></EM> you mentioned for the
proposal. It revolves around if your network is going to handle messages from/to
other BBS's from around the globe.<BR> <BR>You mentioned that most people
are now just used to addressing messages in a format of internet email: <A
href="mailto:user@domain.com">user@domain.com</A><BR>I think this statement is
true, only of <U>non-packet-radio</U> people.<BR> <BR>While a mandatory
setup like that may work well for your network, and for your needs, I get
extremely nervous when it comes to packet radio messages being addressed that
way by default.<BR> <BR>My primary resistance to that thought process has
several reasons.<BR> <BR>
<UL>
<LI><U>Packet Radio messaging is not email</U>. The vast majority of packet
users who send messages from BBS to BBS, know that packet messages headed to
another packet station uses HIERARCHY format, and not email format.
<LI><U>Email addresses are like phone numbers. If it isn't 100% correct, it
isn't getting through</U>, or it gets delivered to the wrong place.
<LI>Traditional H-Addressing uses regions, so if you know the 'area' someone
is in, you don't necessarily need to be 100% accurate when addressing the
message, and the message can still have a chance at reaching the BBS where the
intended recipient calls his "Home BBS". <U>You just can't do that with 'email
addressing'.</U> (Remember the ham radio montra "When all else fails")
<LI>NOS software is the only software I am aware of that 'also' included a
module to 'export' and 'import' email as part of its 'default' functionality.
And I say export and import because again, 'email' was not initially intended
to be part of packet radio messaging. Most all other forms of packet radio
'BBS' software (like FBB) later had add-on modules developed to also
import/export email messages, but those 'non-NOS' software's were never
re-developed to handle email by default, for my #1 and #2 reasons stated
above. The core software always stayed true to H-Addressing so the messages
stood a high chance of reaching its intended target BBS. (Again, even if you
didn't know what the intended target BBS
was)</LI></UL> <BR> <BR>Again, <U>I have no objections to your
proposed type of functionality</U>, especially if your LAN <STRONG><EM><U>never
intends</U></EM></STRONG> to send or receive messages from other BBS's from
around the world. Then your local users would never need to be trained on
traditional messages using H-Addressing.<BR> <BR>But if your network
<STRONG><EM><U>intends</U></EM></STRONG> to handle messages outbound for other
BBS's around the world, then the users of your network will also need to
understand (be trained in) the H-Addressing method, so that messages headed to
'non-NOS' stations correctly traverse the world BBS network.<BR> <BR>Just
food for thought.<BR> <BR>BTW - Good job at having one of the larger
networks to support your community during disasters. You are to be
commended.<BR> <BR>Bill<BR>KG6BAJ<BR> <BR>
<DIV>
<HR id=stopSpelling>
</DIV>
<DIV>From: n6mef@mefox.org<BR>To: nos-bbs@tapr.org<BR>Date: Sun, 11 Dec 2011
09:37:36 -0800<BR>Subject: [nos-bbs] FW: smtp gateway options<BR><BR></DIV>
<META name=Generator content="Microsoft SafeHTML">
<STYLE>
.externalclass p.ecxmsonormal, .externalclass li.ecxmsonormal, .externalclass div.ecxmsonormal
{margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri","sans-serif";}
.externalclass a:link, .externalclass span.ecxmsohyperlink
{color:blue;text-decoration:underline;}
.externalclass a:visited, .externalclass span.ecxmsohyperlinkfollowed
{color:purple;text-decoration:underline;}
.externalclass span.ecxemailstyle17
{font-family:"Calibri","sans-serif";color:windowtext;}
.externalclass span.ecxemailstyle18
{font-family:"Calibri","sans-serif";color:#1f497d;}
.externalclass .ecxmsochpdefault
{font-size:10.0pt;}
@page wordsection1
{size:8.5in 11.0in;}
.externalclass div.ecxwordsection1
{page:wordsection1;}
</STYLE>
<DIV class=ecxWordSection1>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Does anyone object to the
functionality proposed below (whatever the actual syntax may end up
being)?</SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"></SPAN> </P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Bob Tenty? Bill
Lewis?</SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"></SPAN> </P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Michael</SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"></SPAN> </P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"></SPAN></P></DIV></DIV>
<P>
<HR>
_______________________________________________<BR>nos-bbs mailing
list<BR>nos-bbs@tapr.org<BR>https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs<BR></DIV></DIV></DIV></BODY></HTML>