[OZAPRS] VK email server

Darryl Smith Darryl at radio-active.net.au
Thu Apr 1 06:42:59 EST 2004

The simple way is not to have a continuation character, but an indicator
how many lines are to be included in the message. 

But that would only make sense if the client software on the RF side where
you would be sending email from 
	a) handled the generation of the message
	b) Sent all the messages with consecutive sequence numbers.

The other option which does not violate the spec at all is to create a
message type in the 'U' area. I have done this for some software that I am
writing to deal with GPRS mobile data terminals. 


Whilst we are on this subject, one of the things that I have toyed with is
creating an IRC Server, which is connected to the iGATE system. People can
use their IRC software to communicate with people on RF... and the
abstraction does work


Darryl Smith, VK2TDS   POBox 169 Ingleburn NSW 2565 Australia
Mobile Number 0412 929 634 [+61 4 12 929 634 International] 
www.radio-active.net.au - www.radio-active.net.au\web\tracking

-----Original Message-----
From: ozaprs-bounces at marconi.ics.mq.edu.au
[mailto:ozaprs-bounces at marconi.ics.mq.edu.au] On Behalf Of Tony Hunt
Sent: Wednesday, 31 March 2004 10:19 PM
To: vk5zty at bigpond.com; ozaprs at marconi.ics.mq.edu.au
Subject: Re: [OZAPRS] VK email server

John.. I think your going to get into an awful mess trying to use a
continuation character.. As far as I know it cant be done on the current
email servers.. Hey dont let me stop you but as you have noted there are
some pitfalls..

Tony and Eva Hunt   wavetel at iname.com

----- Original Message -----
From: "John Williams" <vk5zty at bigpond.com>
To: "Robert Bruninga" <bruninga at usna.edu>
Cc: <ozaprs at marconi.ics.mq.edu.au>
Sent: Wednesday, March 31, 2004 20:37 PM
Subject: Re: [OZAPRS] VK email server

> The way I understand it is that aprs messages contain 0 - 67 chars
> in the message field.
> If your aprs client allows you to go beyond 67 chars then it places the
additional text
> in another packet.
> The aprs email server would then need to know if the packet is a
continuation packet for the
> same email address or another message addressed to another email
> I have not tried to send an email longer than the allowed length to the
other servers. Do the
> current servers process such messages.
> Richard VK3JFK suggested the > char as an indication that more text was
> Aprs uses un-numbered info frames so the only possible way to determine
packet sequence is
> via the ack field.  This is not necessarily numeric but if it is
lexigraphically sortable then this field
> can be used to assemble received packets in sequence.
> You need to consider that packets may not arrive in order.  Packets
be sent by other
> stations and seen by the server while you are still sending your message
> What I currently do is check that the first part of the message  is an
attempt at a valid email
> address. If it is, grab it then the message text and send an ack to the
sender. The email is then
> sent.
> Anything without a valid email address in the beginning of the message
> Using a continuation character would then let the server know to expect
more text.
> Then we would need an end of message sequence. FBB uses /ex but it
could be
> anything
> unique.
> I would be interested in any ideas of way around not using a
flag and end of
> message flag.  Given that you cant guarantee the arrival order of
or the intention of the
> people sending messages.
> Cheers
> John
> On 29 Mar 2004 at 12:34, Robert Bruninga wrote:
> > >>> "John Williams" <vk5zty at bigpond.com> 3/27/04 9:50:53 PM >>>
> > >
> > >I am testing an aprs email server...
> > >The aprs spec only allows 0 - 67 characters in the
> > >message field which includes the email  address.
> >
> > I would not object in this instance, since we know that
> > the first part of the Email Message is an EMAIL address,
> > and that part of the message, after being parsed out
> > and used for addressing, is no longer part of the "message"
> > content, therefore, that the next 67 bytes AFTER the email
> > address may be retained.
> >
> > Thats a messed up wordy sentence to ssay that these
> > might be the best rules for an Email ENgine:
> >
> > 1) If APRS message is less than 67 then use as is.
> > 2) If APRS message is longer than 67, then remove the
> >     email address from the body and send what's left
> > 3) If that is still more than 67 bytes, then truncate.
> >
> > BUT wait....  hummh... at this point, the message is
> > no longer on APRS anyway, but is in Email, so
> > why do we need to truncate it at all?
> >
> > de Wb4APR, Bob
> >
> _______________________________________________
> ozaprs mailing list
> ozaprs at marconi.ics.mq.edu.au
> http://marconi.ics.mq.edu.au/cgi-bin/mailman/listinfo/ozaprs

ozaprs mailing list
ozaprs at marconi.ics.mq.edu.au

ozaprs mailing list
ozaprs at marconi.ics.mq.edu.au

More information about the Ozaprs mailing list