<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:st1="urn:schemas-microsoft-com:office:smarttags" 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 11 (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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-AU link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi Gregory,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>This is a good idea and the web site is ok
but I was wondering how verify the accounts and implement security measures to
account for varying amateur regulations around the world regarding 3<sup>rd</sup>
party traffic and non-amateurs sending amateurs emails across county boundaries
with.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Cheers<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Richard<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>VK3JFK<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span lang=EN-US style='font-size:10.0pt;font-family:Tahoma'>
aprssig-bounces@tapr.org [mailto:aprssig-bounces@tapr.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Gregory A. Carter<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, 14 January 2009
1:00 PM<br>
<b><span style='font-weight:bold'>To:</span></b> TAPR APRS Mailing List<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [aprssig] New
APRSMail (was: APRS<=>E-mail)</span></font><span lang=EN-US><o:p></o:p></span></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Hello All,<br>
<br>
For those of you who have followed this thread or are interested in an
APRS->Email gateway I've created a new system that supports it. If
you'd like more information, point your web browser at <a
href="http://www.aprsmail.org">www.aprsmail.org</a> and check out the front
page, it gives details of how to use the system, filtering, account access and
the two ways of accessing the gateway.<br>
<br>
The system is still being refined a bit and may still have some unforseen bugs
but it appears to work. IE6 users may have some formatting or display
issues but the page should still be functional and unerstandable for use.<br>
<br>
73,<br>
<br>
Greg<br>
<br>
NV6G<br>
OpenAPRS.Net<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Mon, Jan 5, 2009 at 2:40 PM, Gregory A. Carter <<a
href="mailto:gcarter@openaprs.net">gcarter@openaprs.net</a>> wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>This is one of those moments when I smack myself in the forehead and
say, "I should have thought of that."<br>
<br>
So with regard to security to prevent spam, my thoughts were to allow the
<callsign>@<a href="http://aprsmail.org" target="_blank">aprsmail.org</a>
user to be able to specify a generic password/code to be given in the subject
line when a person wants to email->aprs them. This would imply that
the remote party wishing to contact would have to know the password in order to
communicate.<br>
<br>
I suppose this feature could be optional so the more daring can leave the door
open for anyone to email them assuming they have the correct email
format. For now, my thoughts are to force a text or html (NO MIME) email
that will have the HTML auto stripped (since some clients send in html by
default this would make life easier for the less advanced user) if present
which are forced to use a format like the following for the system to parse and
know the message is not spam.<br>
<br>
--- Body of Message ---<br>
<br>
SR:<FROM CALLSIGN>|MS:<MESSAGE><br>
<br>
--- End of Message ---<br>
<br>
For those of you who have seen OpenAPRS's DCC interface this is very similar to
the way DCC parses lines. The pipe (|) character and backslash (\)
characters would have to be escaped if to be interpreted literally.<br>
<br>
This format would also leave tons of room for expansion if needed in the
future. When parsing this format spaces before and after the line would
be removed and spaces would be compressed in <MESSAGE>.<br>
<br>
<MESSAGE> would be restricted to 67 characters or less.<br>
<FROM CALLSIGN> would be restricted to a standard callsign format 10
characters or less, no spaces and only letters numbers or -.<br>
<br>
This format would be unmistakable compared to spam or any other accidental
email. <FROM CALLSIGN> would then be used as the source in the
packet and both the callsign and message would be checked for vulgarity.<br>
<br>
Eventually the system would be expanded to read and accept MIME multipart
messages and scan for the "text" body of the message.<br>
<br>
So as an example, if I wanted to send a message to N6NAR from me (NV6G) the
email would look like this.<br>
<br>
***BEGIN***<br>
TO: <a href="mailto:n6nar@aprsmail.org" target="_blank">n6nar@aprsmail.org</a><br>
FROM: <a href="mailto:gcarter@openaprs.net" target="_blank">gcarter@openaprs.net</a><br>
SUBJECT: <optional password><br>
---<br>
<br>
SR:NV6G|MS:Hello, how are you today?<br>
***END***<br>
<br>
SR: and MS: could be specified in any order the parser won't care.<br>
<br>
Thoughts, opinions?<br>
<br>
Greg<br>
<br>
NV6G<br>
OpenAPRS.Net<o:p></o:p></span></font></p>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Mon, Jan 5, 2009 at 10:48 AM, Lynn W. Deffenbaugh (Mr) <<a
href="mailto:ldeffenb@homeside.to" target="_blank">ldeffenb@homeside.to</a>>
wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Actually, I would rely on the TCPIP as the path rather than trying to<br>
play catchup or guesswork on what client application they are using. If<br>
their path is ONLY TCPIP* (excluding the qXX code and gate), then assume<br>
APRS-IS. Otherwise, it is RF-limited.<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
Lynn (D) - KJ4ERJ<br>
<br>
Gregory A. Carter wrote:<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> Thanks for looking that up <st1:City w:st="on"><st1:place w:st="on">Lynn</st1:place></st1:City>...<br>
><br>
> So it may be possible to check to see if the user is actually online<br>
> at the time with messaging by looking at the destination address they<br>
> have set which would hopefully reveal what client they are using. Of<br>
> course this would fail in the case of MIC_E packets but would<br>
> generally be useful for others. If we couldn't detect what client<br>
> they were using then we're default to the RF limit.<br>
><br>
> Greg<br>
><br>
> NV6G<br>
> OpenAPRS.Net<br>
><br>
> On Mon, Jan 5, 2009 at 10:24 AM, Lynn W. Deffenbaugh (Mr)<o:p></o:p></span></font></p>
</div>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> <<a href="mailto:ldeffenb@homeside.to" target="_blank">ldeffenb@homeside.to</a>
<mailto:<a href="mailto:ldeffenb@homeside.to" target="_blank">ldeffenb@homeside.to</a>>>
wrote:<br>
><br>
> From the APRS101 spec approved 29 August 2000 under
the NTS Radiogram<br>
> section:<br>
><br>
> Each line may be up 67 characters long, including the
3-character NTS<br>
> format identifier. Lines in excess of 67 characters will be
truncated.<br>
><br>
> Also from the Messages, Bulletins, and Announcements
section:<br>
><br>
> The message text may be up to 67 characters long, and may
contain any<br>
> printable ASCII characters except |, ~ or {.<br>
><br>
> From the APRS-IS Specification:<br>
><br>
> All "packets" sent to APRS-IS must be in the TNC2
format<br>
> terminated by a<br>
> carriage return, line feed sequence. No line may exceed 512
bytes<br>
> including the CR/LF sequence.<br>
><br>
> And that 512 bytes INCLUDES the TNC2 monitor format
"header"<br>
> information<br>
> (prior to the colon) of SENDER>DEST,PATH:rest of packet.
If I<br>
> remember<br>
> correctly, the AX.25 path can handle up to 8 hops and then
an<br>
> IGate may<br>
> add a qXX and it's own callsign, and a callsign-ssid is 9
characters,<br>
> plus the commas means that the header maxes out at 120 bytes<br>
> (sender+dest+8*path+qXX+IGate) (actually 114 if we assume a
3, not 9,<br>
> character qXX code). That would leave a maximum of 398
payload<br>
> characters per the APRS-IS spec. Oh, but we have to
allow for the 9<br>
> character message destination and an additional colon
separator<br>
> plus the<br>
> ack at the end (assuming the e-mail forwarder is doing the<br>
> decaying send<br>
> until ack routine). That'd leave us with 382 (10 for
dest & colon<br>
> and 6<br>
> for {msgno per APRS spec).<br>
><br>
> Seems like 382 is the upper limit of message body for
TCP/APRS-IS<br>
> packets and 67 is the defined spec limit for APRS over RF
messages.<br>
><br>
> Lynn (D) - KJ4ERJ - Thankful for Jason's suggestion to check
the<br>
> specs...<br>
><br>
> Jason KG4WSV wrote:<br>
> > On Mon, Jan 5, 2009 at 11:48 AM, Lynn W. Deffenbaugh
(Mr)<o:p></o:p></span></font></p>
</div>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> > <<a href="mailto:ldeffenb@homeside.to"
target="_blank">ldeffenb@homeside.to</a> <mailto:<a
href="mailto:ldeffenb@homeside.to" target="_blank">ldeffenb@homeside.to</a>>>
wrote:<br>
> ><br>
> >> To throw out numbers, I'd say 1K for non-RF users<br>
> >><br>
> ><br>
> > gack! Think maybe you should check the APRS-IS
design first? I<br>
> don't<br>
> > know the upper limit on packet size, but it would pay
to check<br>
> it out.<br>
> ><br>
> > Think "APRS messages", not "small
email".<br>
> ><br>
> > -Jason<br>
> > kg4wsv<br>
> ><br>
> > _______________________________________________<br>
> > aprssig mailing list<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> > <a href="mailto:aprssig@tapr.org"
target="_blank">aprssig@tapr.org</a> <mailto:<a
href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a>><o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> > <a
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
> ><br>
> ><br>
><br>
><br>
> _______________________________________________<br>
> aprssig mailing list<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> <a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a>
<mailto:<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a>><o:p></o:p></span></font></p>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>> <a
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> aprssig mailing list<br>
> <a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
> <a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig"
target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
><br>
<br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><o:p></o:p></span></font></p>
</div>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</div>
</body>
</html>