[Xastir-dev] message bugs?
John Williams
vk5zty at bigpond.com
Wed Jan 26 00:30:38 EST 2005
Just be aware that they are other aprs email servers out there.
Someone has written another ui-view plug in and the aprs email server in Australia
replies as VKMAIL. This is also how you address the message. So it does get acknowledged
correctly.
I believe the different email servers use different calls to avoid conflicts.
These servers should really respond in a way aprs clients expect.
There is only one server that uses EMAIL that I am aware of, so your special case should not
cause problems with the other servers. Hard coding a special case is not an ideal solution though.
You could implement a retry count for messages. Perhaps configurable up to 10 attempts.
Otherwise just let the user decide when to cancel the message.
Regards
John
VK5ZTY
On 25 Jan 2005 at 18:21, Curt, WE7U wrote:
> On Mon, 24 Jan 2005, Chris Bell wrote:
>
> > 2. When using the EMAIL service, the ack and the OK message come from
> > WU2Z, and not from "EMAIL", so we never clear the outgoing message.
> > [This has been a problem forever.] Fortunately, we now have the
> > cancel button so we can kill it. Should we match up the ack with the
> > counter we sent out, ignoring the to/from calls, and not care that we
> > might be getting spoofed [intentionally or otherwise] ? I would hate
> > to add a special case that "EMAIL" ignores the returning from
> > call... but otherwise we never stop txing.
>
> I thought about adding a button that would allow looser matches, but
> then we could end up getting an ack from one of our QSO's that
> matched a different QSO, if the sequence-ID just happened to match.
> That'd get very strange in a hurry.
>
> How about this:
>
> If we're sending to EMAIL only, match on "EMAIL plus ACK" or "WU2Z
> plus ACK". I kind of hate to put in a specific callsign for the
> EMAIL match, but I can't think of a better way to do it.
>
> Comments?
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.4 - Release Date: 1/25/05
More information about the Xastir-dev
mailing list