<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.squiggly
{mso-style-name:squiggly;}
p.ecxmsonormal, li.ecxmsonormal, div.ecxmsonormal
{mso-style-name:ecxmsonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecxmsochpdefault, li.ecxmsochpdefault, div.ecxmsochpdefault
{mso-style-name:ecxmsochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecxmsohyperlink
{mso-style-name:ecxmsohyperlink;}
span.ecxmsohyperlinkfollowed
{mso-style-name:ecxmsohyperlinkfollowed;}
span.ecxemailstyle18
{mso-style-name:ecxemailstyle18;}
p.ecxmsonormal1, li.ecxmsonormal1, div.ecxmsonormal1
{mso-style-name:ecxmsonormal1;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecxmsohyperlink1
{mso-style-name:ecxmsohyperlink1;
color:blue;
text-decoration:underline;}
span.ecxmsohyperlinkfollowed1
{mso-style-name:ecxmsohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
span.ecxemailstyle181
{mso-style-name:ecxemailstyle181;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.ecxmsochpdefault1, li.ecxmsochpdefault1, div.ecxmsochpdefault1
{mso-style-name:ecxmsochpdefault1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle30
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Bill,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>With respect, I don’t think you read what I wrote.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We already send messages within our network without using the gateway. We use SMTP for all messages. We don’t use the postfix email gateway for messages within our network. We don’t use the postfix gateway for messages within all of amprnet. We only use it when sending mail to external internet e-mail users.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It is precisely the desire to CONTINUE to NOT use the gateway when it is not needed that is the root of my suggestions. Bob’s suggestion would use the gateway for ALL messages if a gateway is configured. The issue is controlling when JNOS makes use of the gateway – using it when needed and not using it when it is not necessary.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Everyone from little kids to grandparents knows how to address mail messages with smtp-style addresses. They do it multiple times a day, every day. We like that. That’s one less hurdle for users. That means pretty much zero training for addressing a message. They can use the same addressing style in our network that they use every day in email. They can mix internet and packet destinations in the same message without having a magic decoder ring. That is a good thing. We don’t want to go backwards.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I appreciate and understand your suggestion about rewriting smtp-style addresses into non-smtp style addresses for local messages. It’s a novel approach. Yes, we could use rewrite to turn smtp addresses into old-style bbs addresses and use bbs forwarding to move them around. But that’s added complication to do what already works with a much simpler configuration. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Also, there’s a big problem with old-style bbs forwarding. All of our BBSs currently have the same call-sign – our club call for the county ares/races group. They are differentiated by an SSID. So they are hosts w6xsc-1.ampr.org through w6xsc-5.ampr.org. Users don’t have to remember five unique callsigns. (w6xsc may seem obscure, but “XSC” is the official op-area designator for Santa Clara County, and appears on all types of things, such as RACES activation numbers, etc. So we all know it as the county ares/races club call sign, and it’s only one call sign to remember). <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The current hostnames work fine for internet hostnames and SMTP. But I understand from talking with you that this naming scheme won’t work for bbs forwarding since each bbs would need its own unique call sign to configure in the haddress. That’s a big turn-off. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I don’t see the value of having all of our users learn 5 different call signs when one currently works. I don’t see the value in rewriting the current standard mail address format known by everyone into an older format know by only a small and shrinking population, and using extra rules in rewrite and forward.bbs, just to recreate what already works with much more simplicity. To me, it makes much more sense to add the flexibility to JNOS to make it easily fit into various modern SMTP environments, than to try to force SMTP environments backward into something else.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Michael<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> nos-bbs-bounces@tapr.org [mailto:nos-bbs-bounces@tapr.org] <b>On Behalf Of </b>Wm Lewis<br><b>Sent:</b> Tuesday, December 06, 2011 9:22 PM<br><b>To:</b> nos-bbs@tapr.org<br><b>Subject:</b> Re: [nos-bbs] smtp gateway control<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Within your network, you can send messages directly to each other without using your gateway.<br> <br>You just want to send them address more like this :<br> <br><strong><span style='font-family:"Tahoma","sans-serif"'>SP AB6CDE @ WX6YZ</span></strong><br> <br>Where AB6CDE is the intended recipient and WX6YZ is the intended station within your network.<br> <br>In this manner you want to avoid addressing messages in a form that looks like an internet email address.<br> <br>Meaning you'd want to avoid addressing like this:<br> <br><strong><span style='font-family:"Tahoma","sans-serif"'>SP <a href="mailto:AB6CDE@WX6YZampr.org">AB6CDE</a></span></strong><span class=squiggly><b><a href="mailto:AB6CDE@WX6YZampr.org">@WX6YZampr.org</a></b></span><strong><span style='font-family:"Tahoma","sans-serif"'> </span></strong><br> <br>By addressing in the first manner, your rewrite file can and your forward.bbs file can work together to route your internal LAN/NETWORK messages around to each other and avoid internet email altogether.<br> <br>In fact, your rewrite file can have rules to catch messages addressed to the second method, and rescan them as if they were addressed to the first method.<br> <br>Doing this would seem to accomplish what you see (or what I believe you seek).<br> <br>A rewrite rule something similar to this:<br> <br><span style='color:black'> </span><a href="mailto:*%25*@wx6yz.ampr.org"><strong><span style='font-family:"Tahoma","sans-serif";color:black'>*%*@wx6yz.ampr.org</span></strong></a><strong><span style='font-family:"Tahoma","sans-serif";color:black'> </span></strong><a href="mailto:$1@wx6yz"><strong><span style='font-family:"Tahoma","sans-serif";color:black'>$1@wx6yz</span></strong></a><strong><span style='font-family:"Tahoma","sans-serif";color:black'> </span></strong><strong><span style='font-family:"Tahoma","sans-serif"'> r</span></strong><br> <br><strong><span style='font-family:"Tahoma","sans-serif"'>or simply</span></strong><br> <br> <a href="mailto:*%25*@wx6yz.ampr.org"><strong><span style='font-family:"Tahoma","sans-serif";color:black'>*%*@wx6yz.ampr.org</span></strong></a><strong><span style='font-family:"Tahoma","sans-serif";color:black'> </span></strong><strong><span style='font-family:"Tahoma","sans-serif"'> WX6YZ</span></strong><br><strong><span style='font-family:"Tahoma","sans-serif"'> </span></strong><b><br><br></b>(You'll have to excuse HOTMAIL for trying to turn those into links)<br> <br>Keep in mind that you would also want those rules to be first in your rewrite file so they can be filtered into your LAN forwarding before any other rules. This would prevent further rules from sending them someplace unexpected.<br> <br>After that, all other messages addressed to an internet address not in your LAN, you get passed over to your gateway to be sent onward.<br> <br>I already do this for one station at the RF end of my LAN. If someone from the internet were to send him a message addressed to <a href="mailto:hiscallsign@hiscallsign.amor.org">hiscallsign@hiscallsign.amor.org</a> , that message does come into my gateway POSTFIX first, scanned for garbage, passed to my JNOS, then sent over RF to his station.<br> <br>By the same token, if someone on my JNOS sends him a message ("SP hiscallsign") that message goes directly to him via RF, and never gets sent to my POSTFIX gateway.<br> <br>I hope that helps.<br> <br>Bill<br>KG6BAJ<br> <o:p></o:p></span></p><div><div class=MsoNormal align=center style='margin-left:.5in;text-align:center'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><hr size=2 width="100%" align=center id=stopSpelling></span></div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From: <a href="mailto:n6mef@mefox.org">n6mef@mefox.org</a><br>To: <a href="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</a><br>Date: Tue, 6 Dec 2011 16:11:09 -0800<br>Subject: Re: [nos-bbs] smtp gateway control<o:p></o:p></span></p><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>As I said, we have a network of JNOS systems with a gateway for mail to others. The gateway uses Postfix. But it doesn’t make sense to send everything to a gateway, when JNOS can talk directly to JNOS with a single hop.</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p></o:p></span></p><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p></div></div></div></div></div></body></html>