<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)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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><div><div><div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='margin-left:.5in'>> The "smtp:" prefix *may* be used by Winlink clients to designate that the email goes out to the SMTP world. But, again, that's is for messges from Winlink *TO* SMTP, as the prefix suggests. JNOS is the REVERSE direction: from SMTP, *TO* Winlink. <o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>It depends... If JNOS is sending a message on Packet, to the Internet world, via a Winlink2000 gateway - then it is acting as a Winlink Client. Years ago, the last time I tried this, the 'smtp:' was required and the fact that JNOS did not add it when sending out through a wl2k system was a show-stopper. It meant JNOS could not take advantage of the wl2k access points as an alternate outgoing path.<o:p></o:p></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.K. *<b>THAT</b>* is clear. Thank you! If JNOS is acting as a client of Winlink, then it would need to send addresses in the format that Winlink expects from its clients. <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'>But I guess I just don’t see a real use case for that. For example, the JNOS webpage (<a href="http://www.langelaar.net/projects/jnos2/documents/practical/wl2kcms2013.html">http://www.langelaar.net/projects/jnos2/documents/practical/wl2kcms2013.html</a>) shows JNOS connecting with telnet to the CMS in order to send mail to both winlink users and other Internet users. But in order to do that, Internet connectivity must be available at both ends (at the CMS and at JNOS). And if Internet connectivity is available, it would be better to send the messages as SMTP messages and avoid the need to use this goofy address format altogether. With SMTP, there’s no difference between sending to Winlink from JNOS vs. sending to Winlink from gmail or yahoo mail or any other SMTP MTA. In fact, the only reason I can see for establishing a telnet forwarding session with the CMS is if your JNOS system doesn’t have an SMTP gateway. I suppose that situation could exist. But that sure is doing it the hard way. Better to set up an SMTP gateway and send SMTP direct to all SMTP destinations (including winlink.org) than to use BBS forwarding to send SMTP through Winlink. Am I missing something?<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'>Perhaps a more useful example would be JNOS forwarding via AX.25 packet to a nearby RMS in order to send mail to users on the local RMS because Internet is not available. If the RMS doesn’t have Internet access, it can’t really do anything except perhaps local delivery. So sending to commercial addresses through winlink wouldn’t be applicable in that scenario. And, as I understand it, the RMS relies on the CMS to know whether a user is local or not. So if it can’t reach the CMS, I don’t know what will happen. Does anyone know if an RMS will perform local delivery if it loses its Internet connection?<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>I haven't tried in some time but I believe this 'smtp:' requirement is gone. It did seem pointless. If there's an '@' in the address, then it's SMTP. If no '@' - then it's a local Winlink address.<o:p></o:p></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'>Yup<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='margin-left:.5in'>So even if JNOS needs some way to initiate a different set of handling rules when sending to Winlink, the prefix "smtp:" would not be right.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>On 'packet' it 'would' have been needed. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='margin-left:.5in'>> But even Winlink doesn't "require" the use of the "smtp:" prefix. I sent messages using Outpost connected to the CMS with telnet and they worked with and without the "smtp:" prefix. So, it's evidently not even a requirement for Winlink clients!<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>I believe this is the change I'm mentioning. There may still be different rules for Telnet vs RF access.<o:p></o:p></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'>Fair point. I haven’t tried RF client access to an RMS.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='margin-left:.5in'>> Winlink DOES impose a subject line restriction (must start with "//WL2K") but that has nothing to do with the address.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>That is a user level convention used to reduce spam. I don't believe that should be programmed into an user application like JNOS. <o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Agreed.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='margin-left:.5in'><br>> Perhaps to move this forward, I'll ask this question:<br>> What EXACTLY does JNOS do differently if I address a message as "smtp:user@domain" vs. just "user@domain"?<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Wouldn't that be a no-op for JNOS. We could use the rewrite rules to just ignore it. It might be useful to do that if folks were using Winlink client with JNOS. We need to check on the if the smtp is of any use..<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Well, the JNOS webpage (<a href="http://www.langelaar.net/projects/jnos2/documents/changes.txt">http://www.langelaar.net/projects/jnos2/documents/changes.txt</a>) says “</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>JNOS sets up the FROM<o:p></o:p></span></pre><pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> and MSGID mail headers to ensure Winlink delivers the email to 3rd parties.”<span style='color:#1F497D'> So I was trying to understand what those changes are.<o:p></o:p></span></span></pre><pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></pre><pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></pre><pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Michael<o:p></o:p></span></pre><pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></pre><pre><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></pre></div><div><p class=MsoNormal style='margin-left:.5in'> <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></div></body></html>