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">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">n6nar@aprsmail.org</a><br>FROM: <a href="mailto:gcarter@openaprs.net">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<br><br><div class="gmail_quote">On Mon, Jan 5, 2009 at 10:48 AM, Lynn W. Deffenbaugh (Mr) <span dir="ltr"><<a href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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.<br>
<div class="Ih2E3d"><br>
Lynn (D) - KJ4ERJ<br>
<br>
Gregory A. Carter wrote:<br>
</div><div class="Ih2E3d">> Thanks for looking that up Lynn...<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)<br>
</div><div><div></div><div class="Wj3C7c">> <<a href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a> <mailto:<a href="mailto:ldeffenb@homeside.to">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)<br>
</div></div><div class="Ih2E3d">> > <<a href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a> <mailto:<a href="mailto:ldeffenb@homeside.to">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<br>
</div>> > <a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a> <mailto:<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>><br>
<div class="Ih2E3d">> > <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>
</div>> <a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a> <mailto:<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>><br>
<div><div></div><div class="Wj3C7c">> <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">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">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>
</div></div></blockquote></div><br>