Hi Ron,<br><br>I believe it failed because you tried to send a message to yourself... the system doesn't allow self messages to prevent it from acking to itself. I'll have to work on that... if you send a message to someone else it should work just fine. I've added an error message for self attempts for now to let people know.<br>
<br>Greg<br><br>NV6G<br>OpenAPRS.Net<br><br><div class="gmail_quote">On Tue, Jan 13, 2009 at 7:22 PM, Ron Tonneson <span dir="ltr"><<a href="mailto:ron.tonneson@gmail.com">ron.tonneson@gmail.com</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;">The <a href="http://aprsmail.org" target="_blank">aprsmail.org</a> works fine with Firefox 3.0.5<br>
<br>
I tried to send myself a message but so far it has not shown up on my UI-View system. I see it in the inbox on<br>
<a href="http://aprsmail.org" target="_blank">aprsmail.org</a>. Wonder if I did it wrong?<br>
<br>
Ron - K0QVF<br>
<div class="Ih2E3d"><br>
Gregory A. Carter wrote:<br>
> Hello All,<br>
><br>
> For those of you who have followed this thread or are interested in an<br>
> APRS->Email gateway I've created a new system that supports it. If<br>
> you'd like more information, point your web browser at <a href="http://www.aprsmail.org" target="_blank">www.aprsmail.org</a><br>
</div>> <<a href="http://www.aprsmail.org" target="_blank">http://www.aprsmail.org</a>> and check out the front page, it gives details<br>
<div class="Ih2E3d">> of how to use the system, filtering, account access and the two ways of<br>
> accessing the gateway.<br>
><br>
> The system is still being refined a bit and may still have some<br>
> unforseen bugs but it appears to work. IE6 users may have some<br>
> formatting or display issues but the page should still be functional and<br>
> unerstandable for use.<br>
><br>
> 73,<br>
><br>
> Greg<br>
><br>
> NV6G<br>
> OpenAPRS.Net<br>
><br>
> On Mon, Jan 5, 2009 at 2:40 PM, Gregory A. Carter <<a href="mailto:gcarter@openaprs.net">gcarter@openaprs.net</a><br>
</div><div class="Ih2E3d">> <mailto:<a href="mailto:gcarter@openaprs.net">gcarter@openaprs.net</a>>> wrote:<br>
><br>
> This is one of those moments when I smack myself in the forehead and<br>
> say, "I should have thought of that."<br>
><br>
> So with regard to security to prevent spam, my thoughts were to<br>
</div>> allow the <callsign>@<a href="http://aprsmail.org" target="_blank">aprsmail.org</a> <<a href="http://aprsmail.org" target="_blank">http://aprsmail.org</a>> user to be<br>
<div><div></div><div class="Wj3C7c">> able to specify a generic password/code to be given in the subject<br>
> line when a person wants to email->aprs them. This would imply that<br>
> the remote party wishing to contact would have to know the password<br>
> in order to communicate.<br>
><br>
> I suppose this feature could be optional so the more daring can<br>
> leave the door open for anyone to email them assuming they have the<br>
> correct email format. For now, my thoughts are to force a text or<br>
> html (NO MIME) email that will have the HTML auto stripped (since<br>
> some clients send in html by default this would make life easier for<br>
> the less advanced user) if present which are forced to use a format<br>
> like the following for the system to parse and know the message is<br>
> 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<br>
> similar to the way DCC parses lines. The pipe (|) character and<br>
> backslash (\) characters would have to be escaped if to be<br>
> interpreted literally.<br>
><br>
> This format would also leave tons of room for expansion if needed in<br>
> the future. When parsing this format spaces before and after the<br>
> 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<br>
> characters or less, no spaces and only letters numbers or -.<br>
><br>
> This format would be unmistakable compared to spam or any other<br>
> accidental email. <FROM CALLSIGN> would then be used as the source<br>
> in the packet and both the callsign and message would be checked for<br>
> vulgarity.<br>
><br>
> Eventually the system would be expanded to read and accept MIME<br>
> 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<br>
> (NV6G) the email would look like this.<br>
><br>
> ***BEGIN***<br>
</div></div>> TO: <a href="mailto:n6nar@aprsmail.org">n6nar@aprsmail.org</a> <mailto:<a href="mailto:n6nar@aprsmail.org">n6nar@aprsmail.org</a>><br>
> FROM: <a href="mailto:gcarter@openaprs.net">gcarter@openaprs.net</a> <mailto:<a href="mailto:gcarter@openaprs.net">gcarter@openaprs.net</a>><br>
<div class="Ih2E3d">> 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>
><br>
> On Mon, Jan 5, 2009 at 10:48 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>
> Actually, I would rely on the TCPIP as the path rather than<br>
> trying to<br>
> play catchup or guesswork on what client application they are<br>
> using. If<br>
> their path is ONLY TCPIP* (excluding the qXX code and gate),<br>
> then assume<br>
> APRS-IS. Otherwise, it is RF-limited.<br>
><br>
> Lynn (D) - KJ4ERJ<br>
><br>
> Gregory A. Carter wrote:<br>
> > Thanks for looking that up Lynn...<br>
> ><br>
> > So it may be possible to check to see if the user is actually<br>
> online<br>
> > at the time with messaging by looking at the destination<br>
> address they<br>
> > have set which would hopefully reveal what client they are<br>
> 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<br>
> 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>
> > <<a href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a> <mailto:<a href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a>><br>
</div></div><div><div></div><div class="Wj3C7c">> <mailto:<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<br>
> NTS Radiogram<br>
> > section:<br>
> ><br>
> > Each line may be up 67 characters long, including the<br>
> 3-character NTS<br>
> > format identifier. Lines in excess of 67 characters will<br>
> 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<br>
> 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<br>
> 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.<br>
> 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<br>
> 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<br>
> a 3, not 9,<br>
> > character qXX code). That would leave a maximum of 398<br>
> payload<br>
> > characters per the APRS-IS spec. Oh, but we have to<br>
> allow for the 9<br>
> > character message destination and an additional colon<br>
> 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<br>
> dest & colon<br>
> > and 6<br>
> > for {msgno per APRS spec).<br>
> ><br>
> > Seems like 382 is the upper limit of message body for<br>
> TCP/APRS-IS<br>
> > packets and 67 is the defined spec limit for APRS over RF<br>
> messages.<br>
> ><br>
> > Lynn (D) - KJ4ERJ - Thankful for Jason's suggestion to<br>
> check the<br>
> > specs...<br>
> ><br>
> > Jason KG4WSV wrote:<br>
> > > On Mon, Jan 5, 2009 at 11:48 AM, Lynn W. Deffenbaugh (Mr)<br>
> > > <<a href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a> <mailto:<a href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a>><br>
</div></div><div class="Ih2E3d">> <mailto:<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<br>
> first? I<br>
> > don't<br>
> > > know the upper limit on packet size, but it would pay<br>
> 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>
> > > <a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a> <mailto:<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>><br>
</div>> <mailto:<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>
> > <a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a> <mailto:<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>><br>
</div>> <mailto:<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>
> > _______________________________________________<br>
> > aprssig mailing list<br>
> > <a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a> <mailto:<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> <mailto:<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>
> ------------------------------------------------------------------------<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>
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>